Teststand IVI Steptypes

hello,
i have a problem with the teststand ivi teststeps
when i try to use the dmm step i get the following errormessage: Session Manager: niDMM_InitWithOptions returned an error: -1074118656. Unknown status code (-31619).
perhaps everyone knows the error.
i have configured the dmm in max for use with ivi drivers
k.-h.

Hi Fischer,
The most common cause of this error is having an incorrect Instrument Descriptor. Is your DMM locally or on a remote PXI system? Please check the following:
http://digital.ni.com/public.nsf/websearch/22CF7E6B27B6995B86256DDB0058F39B?OpenDocument
Is it possible to use the DMM from LabVIEW, CVI or any other development envirnoment?
Let me know if you have success with that.
regards,
Nikolai

Similar Messages

  • TestStand IVI Read Numeric Limit Test

    Hey all,
    How can I turn a IVI DMM reading into a test step pass / fail based on a numeric limit test?
    I'm a TestStand newbie so be gentle.  Searches on the forum for TestStand IVI and pass fail don't return anything useful.
    I can call the DMM via IVI Read wich returns a Step.Result.Reading value but I need to turn this into a pass fail on a limit range.
    Any ideas would be very gratefully appreciated.
    Thanks,
    Solved!
    Go to Solution.

    You could insert an none_adapter numeric limit step after it and set the data source to PreviousStep.Result.Reading.
    -Doug

  • 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

  • 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

  • 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.

  • Using Offset Compensated Ohms from IVI DMM in TestStand

    I am using TestStand 3.5 with a PXI-4070 DMM and I want to be able to use the Offset Compensated Ohms function from the TestStand IVI-C DMM steps.  I cannot find this functionality from the TestStand step, even though it is shown on the front panel of the Soft Front Panel DMM, and is stated as a IVI function.
    Anybody with any ideas would be greatly appreciated.
    A.

    Good afternoon A,
    The Offset Compensated Ohms function that you are looking for is more
    specialized than what the IVI driver has to offer.  Instead of
    using IVI DMM, try NI-DMM.  This is a free download off our
    website, which can be found here:
    NI-DMM version 2.5 for Windows 2000/XP--LabVIEW Real-Time
    http://digital.ni.com/softlib.nsf/websearch/1F1A167276498327862570AC005199D5
    Regards,
    Mike Torba
    National Instruments

  • I want to call the DMM- SFP from Teststand using IVI

    Hi I have a Teststand 3.0 system with a NI-PXI 4070, and I want to call the DMM-SFP from Teststand using the IVI driver architecture. Unfortunatley I cannot figure out how to link the DMM-SFP to the Logical name.

    ADL,
    If you are using the TestStand IVI step types, after you have added the logical name in MAX, you can insert an IVI DMM step type. Then right-click on the step and choose "Edit IVI Dmm". You should be able to choose from the Logical Name Ring Control the logical name you created in MAX.
    If you haven't added the logical name into MAX, depending on what version of MAX you have, you can refer to Using Measurement & Automation Explorer 2.x to Configure Your IVI System or look in the IVI help that comes built into MAX 3.0.
    If you checked there already or have another question, please let us know!
    Regards,
    Shannon R.
    Applications Engineer
    Nati
    onal Instruments

  • Teststand 3, PXI and IVI Driver Versions

    I believe that I have a problem with the installations that were apparent when using Teststand 2 and IVI drivers.
    We have a Teststand 3 system, with a PXI chassis, and a PXI-4070 DMM and a PXI-2567 DMM.
    When I try and call the PXI DMM from Teststand through the IVI step type I get the following messge:
    Error Executing substep 'post'. An exception occurred calling 'Run Step' in 'ISubstep' of 'Teststand IVI Step Types'.
    An error occurred while executing the step.
    Component Works IVI control editor. The IVI Init operation failed for logical name 'JoyDMM'
    -31619; User-defined error code.
    Step 'IVI DMM' of sequence' Mainsequence in 'Sequence File 1'
    I have attatched the NI Software file from Max for Debug
    Attachments:
    nisupport.sif ‏67 KB

    ADL,
    Have you tried communicating with those devices in MAX using the logical names? It seems that the logical name for JoyDMM isn't recognized within TestStand which probably means they aren't recognized in MAX either.
    Let us know what you find.
    Regards,
    Shannon R
    Applications Engineer
    National Instruments

  • 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

  • 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

  • Ivi problems with niscope

    I am trying to use a NI-5112 digitizer utilizing IVI from within TestStand 2 and get the following 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 Init operation failed for logical name 'niScope'.
    Details: Session Manager: niScope_InitWithOptions returned an error: -1074118622 (0xbffa4022). Unknown status value 0xBFFA4022 Primary Error Code: -1074135028.
    Source: TSIviStepTypes
    -31619; User-defined error code.
    Step 'Ivi Scope' of sequence 'MainSequence' in 'IVItest.seq'
    I do not get this error when i try using mu niFGEN IVI instrument. My soft front pa
    nles all seem to work.
    Help!

    Craig,
    Please click on the following link to view my reply.
    IVI problems with NIScope

  • Missing IVI configuration in MAX

    Could somebody please enlighten me as to the specific combination of spells, incantations, gestures, and begging that will get the IVI configuration sub-tree to appear in NI-MAX?
    It has disappeared on me. Usually, I can reinstall stuff (MAX, the IVI Engine, etc) in various orders and eventually get it back again. But I seem to have lost the magic touch now.
    I swear to God, as soon as I find a few spare cycles, this whole IVI thing is out the window. It's just not worth the hassle. I can write my own instrument drivers. It's really not that hard.
    - Ron

    I'm running MAX 3.0.2.3005, which came with NI 488.2 2.20 (the last version I can find that doesn't have the new MAX.) I'm trying to recreate the configuration that I had working before. In particular, I'm trying to avoid the new IVI Compliance Package, because I know it doesn't let me set the voltage attribute on a power supply using the TestStand IVI Tools step.
    The file you mention does not exist. Various attempts at installing, removing, reinstalling and repairing NI 488.2 and IVI Engine 1.83 don't seem to create it. But there is no error message to report. Actually, the entire IVI Engine is apparently not being installed. Programs that use the IVI engine can't find it either.

  • Unsupported Ivi Class Driver

    We developed a new ivi class driver (for counters) and everything works well, the problem comes when we try to use the ivi tool step type to acces functions such as Reset, selftest Get/Set attributes etc. When we use this functions we get the following 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 operation failed for logical name 'SampleCounter'.
    Details: The session handle is invalid or refers to a session that is not from a supported IVI class driver.
    Source: TSIviStepTypes
    The strange thing is that the functions Close and init with options in ivi to
    ols work very well..so what's the problem with the functions reset, selftest, etc..
    With this functions we can't even access the generic driver code because the error shows up before we can get to the code in debbigging mode. Any ideas?.

    eromero,
    I sounds like there's either an error in the configuration for SampleCounter, or that the IviStepTypes only support the DMM, Scope, Switch, FGen, and DCPwr class drivers.
    If you could send/post your ivi.ini file and your driver, I'd be happy to check it out and see if there's a configuration issue. If you don't want to post it to DevZone, you can e-mail it directly to [email protected]
    As for why the init and close functions work, but not the others, I will investigate further.
    One option to get your application to work is to not use the IviStepTypes. You can still use the driver using C function calls directly through the DLL. This will still work, but may not give you all of the features
    of the step types.
    Thanks,
    Bankim Tejani
    Instrument Drivers/IVI
    National Instruments

Maybe you are looking for