Ivi step 34410

 I have been using  the ivi step for a DMM step in Teststand. When using a NI dmm to read a voltage the ivi steps works ok, but when using a Agilent 34410A DMM it does not give the correct reading back. I have downloaded the 34410a driver from NI and used this rather than the one from Agilent.
Is it the case that the NI_ivi_DMM step only works for a NI dmm and not any other manufacturer?

No, the ivi step should work for any instrument with an ivi driver. How different are the readings? Is the configuration correct? You should be able to set a breakpoint before the read and check the setup on the 34410 front panel.

Similar Messages

  • 5112 in Teststand using IVI step

    I am trying to configure with options and set the 5112 to average but get an error. I also can not validate any of my niscope settings. The step seems to work when I execute it, and I only find out what is not supported when it fails.
    Error executing substep 'Post'.
    An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types 1.0 Type Library'
    An error occurred while executing the step.
    Component Works IVI Control Error: The IVI Configure operation failed for logical name 'niScope'.
    Details: Extension capability not supported by instrument driver. (AverageAcquisition)
    Source: TSIviStepTypes
    Please help.

    If you are running TestStand 2.0, you will need to upgrade to 2.0.1. You can get information about this at www.ni.com/upgrade. If you are currently using 2.0.1 then I need to know what version of NI-Scope and what version of the IVI engine.
    Michael

  • When i run a sequence with ivi step types in simulation mode i get the error code number BFFA0015 - Types do not match.

    When i run the sequence with ivi step types in simulation mode i get the error Types do not mathc. The step that generates this error is an IviScope step type and is configured as a measurement. Th weird thing is that in real mode is working perfectly. I have three measure steps and i get the error in all of them. The exact error message is:
    UUT Result: Error, Error executing substep 'Post'. An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types 1.0 Type Library' An error occurred while executing the step. Component Works IVI Control Error: The IVI Read operation failed on channel '1' for logical name 'SampleScope'. Details: (1
    ) Types do not match. [IVI Error Code: BFFA0015] Source: TSIviStepTypes [Error Code: -30721, User-defined error code.]
    Can someone tell me how to fix this problem?. It seems to me that the simulation generates a diferent type of measurement of that generated in real mode.

    Update:
    The simulation driver appears to be raising the error. By switching to specific driver simulation the error does not occur. This may be a problem in either the class simulation driver or the specific driver.
    Scott Richardson
    National Instruments

  • Execution time of IVI Steps

    Hello,
    We have made some benchmarks to decide the usefulness of TestStand IVI steps versus Labview ones with a PXI 4070 ( DMM ).
    The Labview steps ( using also IVI access !!! ) are 30% faster than direct TestStand IVI steps.
    May someone help us to understand such difference ?
    Thanks a lot.

    Oliver -
    The TestStand step types have additional overhead because all the configuration information stored on the TestStand step must be evaluated and passed to the a VB component.  Because the TestStand execution is multi-thread apartment and the VB component must be single thread apartment, some marshalling of data is necessary via COM.  Lastly the VB component is not optimized as the IVI VIs that you are using.  The TestStand IVI steps are not intended for speed, more easy of use. Hope this helps. 
    Scott Richardson
    National Instruments

  • The type library information for 'TestStand IVI Step Types' was not found (Error code: -18351)

    Hi,
    I get the error in the message subject when I add an IVI-C step (no matter IVI Power Supply, IVI Dmm or others) and try to edit the step by pressing Ctrl+E (or double-click the step and click "Edit IVI Power Supply" for instance).
    I have installed 2 IVI-C libraries that I downloaded from 'NI idnet' both with IVI technology (namely agn330xa_MS.msi and agn6700_MS.msi). They can both be seen in Add/Remove programs under "NI IVI Specific Drivers" group.
    The error message says "Make sure the server is registered".
    Does anybody know what server is it complaining about and how can the registration be done?
    Regards,
    S. Eren BALCI
    www.aselsan.com.tr
    Attachments:
    error 18351.jpg ‏66 KB

    Hi ebalci,
    I believe this error is occurring because the ActiveX components that are used by the IVI step types are either not properly installed or not properly registered.  I would recommend first making sure that the IVI compliance package and NI-VISA are installed on the system.  If both of these are already installed, I would recommend running the TestStand Version Selector because this should re-register the ActiveX components used by the IVI step type.  The TestStand Version Selector can be found by going to the Start Menu>>Programs>>National Instruments>>TestStand 3.5.  You will need to select the version of TestStand you want to use and click the "Make Active" button.  I have also pasted links below to VISA and the IVI compliance package.  Hope this helps!
    NI-VISA
    IVI Compliance Package
    Pat P.
    Software Engineer
    National Instruments

  • Does IVI Step Type support NI PXIe-4112?

    Hello, Guys
    I have a PXIe-4112 and four of PXI-4130. When I try to configure my PXIe-4112 with the PowerSupply IVI Step Type, an error occurred.
    An error occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'
    An error occurred while executing the step.
    Component Works IVI Control Error: The IVI Configure operation failed for logical name '4112'.
    Details: Attribute or property not supported. Attribute: NIDCPOWER_ATTR_OVP_ENABLED, Channel: 0 [IVI Error Code:  BFFA0012]
    Source: TSIviStepTypes
    Surely I disabled the 'OVP Enabled' check box at the Edit IVI Power Supply Step Dialog. My system configuration is,
    IVI Compliance Package 4.6
    NI-DCPower 1.8.6
    NI TestStand 2012 SP1
    My PXI-4130s are working well with the IVI Step type. Does IVI Step Type support NI PXIe-4112? Or am I doing something wrong about it?
    Regards,
    Joonam
    CTA, CLA
    SuninCNS
    Solved!
    Go to Solution.
    Attachments:
    4112.png ‏17 KB

    Hi Joonam,
    The PowerSupply IVI step will not currently work with the 4112.  
    The 4112 does not support OVP.  If the NIDCPOWER_ATTR_OVP_ENABLED attribute is set to True, the error that you described is expected.  If it is set to False, no error should be generated.  However, an error is generated when it is set to false.  This is incorrect behavior in the driver and has already been documented under Corrective Action Report (CAR) #437105.  This issue will likely be rectified in a future version of NI-DCPower.
    The PowerSupply IVI step is hard-coded to set the attribute to true or false, based on the value of the check box in the Limit tab.  The workaround to this problem is to replace your PowerSupply IVI step with a step based on a code module that doesn't try to set the OVP_ENABLED attribute at all.
    I apologize for any trouble that this has caused you.  Let me know if you would like any further clarification.
    Regards,
    Jared R.
    Precision DC Product Support Engineer
    National Instruments

  • Measure waveform rise time with IVI step

    I'm trying to simulate measurement of wafeform rise time through IVI step TS 4. How should I  feed the Scope IVI step with waveform and then get the calculated rise time in simulation mode(I do not have the Scope yet.
    Thank you.
    Elik

    Hi,
    Thank you. So far it is simple, but I wonder if there is a way to feed to the IVI step through simulation waveform like square wave and different frequencies. I've tried using TDS 2000 series but I get the same data results.
    I configure it as Normal Acquisition
    Advance Tab Low Reference 10, Middle 50 and High 90.
    Channels Tab, left the defaults except Maximum input frequency which I configure with variable
    Trigger Tab Type Edge, Source Channel 1, Coupling DC, Slope Positive, Level 0.5
    Extension Tab, Waveform Measurement.
    I also set a step Read and set one of the channels to read Rise Time.
    Although the waveform change The data from step results which I suppose give you the rise time stay the same.
    Is there any way to change the waveform type and the rise time through the IVI step?
    Thank you.
    Elik

  • Got 17300 error when execute IVI step in TestStand

    Hi all
    This is a PCBA test platform,, a 4072 card is used for two sockets, I locked the DMM blocks in order to have just a socket access it at same time.
    but the DMM read step type still often has 17300 error, value invalid or out of range, if run only one socket, did not see same problem.
    Confused on this.
    *The best Chinese farmer*
    Attachments:
    dmmerror.JPG ‏153 KB

    Hi Farmer
    The DMM is configed to immediately trigger mode, see attachment, according to the help, immediate means DMM dose not wait for any trigger signal, just read it as soon as the "Read DMM" running.
    帖子被paulbin在09-12-2007 10:17 PM时编辑过了
    帖子被paulbin在09-12-2007 10:27 PM时编辑过了
    *The best Chinese farmer*
    Attachments:
    DMMConfigWindow.PNG ‏55 KB

  • Add an IVI Step Type

    I would like to use an iviRFSigGen with teststand (Currently using ver 2.0). Can I add a step type to do this or is there a step type already available to do this.

    Hi,
    We have a beta version of the custom step "IviRfSigGen".
    Unfortunately, it was not tested so well, it seems like starting exsample for you.
    Please see the attached zip. file and Your comments and suggestions are very welcomed.
    Br,Sergei
    "Only a life lived in the service to others is worth living..." - Albert Einstein
    Attachments:
    IviRFGen.zip ‏444 KB

  • Teststand 4.0 IVI-DMM Step error

    I have Teststand 3.5 and 4.0 installed on a computer and a NI-4060 in a PXI chassis.  When I try running a sequence that has an IVI-DMM step in it in 3.5 everything runs fine.  When I try the same sequence opened in 4.0 it gives me the following attached error (both attachments are the same error one is just scrolled down so you can see the whole thing.)  I have tried adding a simple IVI step from scratch in teststand 4.0 and I get the same error.
    Any ideas?
    Brian
    Attachments:
    untitled1.JPG ‏107 KB
    untitled2.JPG ‏106 KB

    Ok, I used the version selector, went back to 3.5, and ran the sequence and it ran fine like I expected.  When I switch back to 4.0 and ran it it worked (first time in a dozen tries.)  So I switched back to 3.5 ran it and then ran it 4.0 again and it failed.  I attached a spy capture from 3.5, 4.0 worked, and 4.0 didnt work.
    Brian
    Attachments:
    DMMConfig_TS40_Capture_Didnt_Work.spy ‏1 KB
    DMMConfig_TS35_Capture.spy ‏11 KB
    DMMConfig_TS40_Capture_Worked.spy ‏12 KB

  • Failed to acquire a wave using ivi dmm step with a FlexDMM NI-4070

    I tried to acquire wave with a FlexDMM NI_4070 and a Read Multipoint ivi step from TestStand, it didn't went thru. Configuration step is: DC volts, 0.01 resolution, immediate trigger source, auto once range mode, 0 trigger delay, 100 multipiont sample count, 10 sample interval, 1 trigger count, interval sample trigger, none meas complete dest; Read step is: wave data type, Step.Result.Reading meas dest, 5000 time out, "failed" status on time out. What I get is failed status due time out.

    Try setting your Timeout to 30000. The Timeout is in milliseconds, while the Sample Interval on the Advanced tab of the Configure step is in seconds. You have this interval set to 10. Setting your timeout to 30 seconds will give your Read operation time to complete.
    Regards,
    Eric M.

  • Latest IVI Class Step Types in TestStand

    IVI instrument classes have recently been defined for RF Signal Generator, Spectrum Analyzer and Power Meter. There are IVI drivers for these classes available for download from the Instrument Driver network. However, TestStand3 does no contain step types for accessing these drivers. Does anyone know when NI plans to add support for these to TestStand? Has anyone created step types for these classes, or have an example of how to do this?

    David -
    There is no documentation on the low-level workings of the TestStand IVI step types. As with many of the step types that have source code, it is available as examples of developing a step type in various languages.
    The additional work to add the a new class to the TestStand IVI step types is not small, that is why to date we have not done it. The amount of work could be divided into the following areas:
    * Update the TsIviStepTypes to add the new class to the enumeration.
    * Create the new step type definition (subproperty structure) based on the IVI spec.
    * Upcate the TSIviStep and TSIviSFP code to allow you to edit and perform the work to process the expressions and initiate the various IVI class operations.
    * Add low level
    IVI class layer logic to talk to the IVI class driver. This piece was previously done in a VB ActiveX control written by the Measurement Studio group in NI.
    The last two items are the biggest and they would take some time. That is why I was suggesting creating specific Action steps that call into custom code modules to talk to IVI directly, that is, no edit dialog box, no SFP, etc.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • Error when editing IVI Scope Step in TestStand 3.1

    When I open the edit box for an IVI Scope Step in TestStand 3.1 I get the following error: Method '~' of object '~' failed (-2147417851).  I get the same error again when I click on the Logical Name dropdown box in the edit window.  I have an IVI logical name of 'TekScope' in MAX that was created when I installed the IVI drivers for a Tektronix DPO7000.
    Software Installed: TestStand 3.1, NIMax 4.3, NI IVI Compliance Package 3.2, Windows XP Pro. SP2
    It seems that TestStand is unable to communicate with MAX.  I don't think it is a version compatibility problem because I had the same problem when using MAX 3.1.1.

    Nick,
    Thanks for the reply.  This problem went away when I opened the IVI example sequence that is installed along with TestStand.  It has not repeated since.  I can now access my defined 'TekScope'.
    I am having a problem getting the IVI code to run in simulation mode.  I modified the TestStand 3.1\Examples\IVI\IviStepTypes.seq file to change the Fileglobals.ScopeLogicalName value to TekScope which is the scope name in the dropdown box for edit IVI tools.  I then selected the scope steps and selected Run Selected Steps.  I get the following error:
    An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types'
    An error occurred while executing the step.
    IVI Error: The IVI instrument failed to initialize for logical name 'TekScope'.
    Details: TekScope_InitWithOptions returned an error: -1074134964 (0xbffa004c). The option string parameter contains an entry with an unknown option value.
    Source: TSIviStepTypes
    -1074134964; User-defined error code.
    In MAX the TekScope.DriverSession - Simulate With setting is nisScope, Driver Setup is blank.

  • Error from IVI switch step in Teststand

    We have the following issue when using Teststand. A reboot sometimes clears the problem, but other times it requires many reboots.
    When starting our test sequence, we undertake a Disconnect All using the IVI Step type to ensure the switches are all disconnected.
    We then get the following message:
    An error occurred while executing the step. Unexpected Error: Switch Executive failed to initialize for virtual device 'Joyswitch'
    Details: Joyswitch_init returned an error -1074118644 (0x%3)
    Source: TSIviStepType
    Any help would be gratefully appreciated
    I have attatched the actual run-time error.
    Attachments:
    Switch_Exec_error.jpg ‏122 KB

    The suggestion to try the validate option under MAX for Switch Executive would be a good idea. The error that you are seeing appears to be coming back from the IVI driver.
    Question that come to mind are:
    - You say that the Disconnect All fails, but does a Connect work?
    - What hardware and IVI driver is the Joyswitch using?
    - It appears that you are using TestStand 3.0, but what version of the Switch Executive are you using?
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • How do I make Step Types in the Type palette be "master" versions which all sequence files on a particular should use? (since this only seems to "half work")

    The situation I would like is to have a library of step types which sequence developers can use. Therefore if new step types need to be added, or existing ones modified - all that needs to be done is to roll out a new MyTypes.ini (for example), and the code modules/substeps.
    Scenarios:
    If I create types in MyTypes.ini (make sure "Attach to this file" is checked, so they get saved here). I can then create a sequence file using these step types. No problem so far.
    I can open the type palette, modify the step properties, and save. When I go back to my sequence file an asterisk appears (saying it needs to be saved, even if I have opened it from scratch). The properties have been updated to reflect what is in the Type Palette. Still no problem (Type versions are the same in the sequence file and type palette).
    This is where the problem appears:
    If I change a step type (in the Type Palette) from using a code module to using a Post-Step substep instead (changing the module adaptor to "None") - any instances do NOT update when you open sequence files. (The same happens vice versa also).
    Please note that the "Type version" listed in the sequence file DOES match that listed in the Type Palette - the properties are the same but the manner in which the code modules are called is DIFFERENT! This then can lead to to runtime errors if the old code module has been deleted for example.
    The only way around this is to open EVERY sequence file that contains an instance of the step type, and make sure that you have "Apply changes to all loaded instances of this type" checked in the step type properties dialog. This is is not a good solution since files could be missed, and is very time consuming if you have hundreds of sequence files!
    What I need is that the Type Palette on any particular station contains the MASTER copies of each type. These are loaded whenever a sequence file is loaded and NOT retreived from the sequence file. As discussed above this seems to work when you modify properties - but doesnt work fine if you change the way in which code modules are called.
    Am I doing something wrong or is this a limitation?

    I had a system recently containing seven sequence files, approx 20 subsequences in each, and around 10-20 steps in each sub-sequence. Every step (except for the NI non-code module types) was an instance of a step type.
    Each one of these steps had an Edit sub-step and a code module called through the code module adapter.
    In order to make these into "wrapped up" step types it was decided to move the code module to a Post-Step substep (as also done in the NI-IVI step types) - so that developers cannot fiddle with the code prototype or module.
    In order to do this I had to open all 7 of the sequence files, make the changes and then ensure that "Apply changes in this dialog to a loaded instances" was checked. This seems to sort of work, but some steps started causing Error 17502 (System Error) when you configure them (call the Edit substep). Over the course of the past few months I have had to effectively check every instance of a type to see if it works (deleting the step and replacing it when it doesnt). Other strange things happened like some of the step type instances now have the "None" (adapter) icon associated with them - but both still work.
    The idea of creating a type-def of a step type is a good one, but frustrating that it doesnt seem to fully work. Why should the sequence file also store a version of the step-type - which is what is effectively causing this problem - why not make it so that if you dont have the step types installed in the type palette - TOUGH! Message Edited by RichM on 03-15-2005 06:55 AM

Maybe you are looking for