Using IVI-C attibutes in TestStand

Hi,
While using LabWindows/CVI IVI-C drivers in Test Stand, we found a difficulty in giving the value to the attribute parameter for the functions. For e.g., With ividmm.dll in C:\Program Files\IVI Foundation\IVI\Bin, choosing IviDmm_ConfigureMeasurement as function name, found very difficult to find the value to the "measurementFunction" parameter. We need to go to the header IADdmm.h, calculate the value of the attribute value and pass here.
Is there any better way of doing this in Test Stand?
Thanks
Selva

Why dont you use the IVI step type for DMM?
Regards
Ray Farmer

Similar Messages

Agilent 34980A simulation using IVI-drivers in Teststand?

Hello! I am unable to simulate 34980A in TestStand and here are some results based on testing:
Agilent 34980A is linked to logical name SampleDmm. Simulate With: Specific Driver.
IviStepTypes.seq used with only DMM and Switch steps.
Using IviDMM IVI-C causes runtime-error in Ivi DMM Configure Single Point: Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'. Details: Extension capability not supported by instrument driver. (Base)
Using IviDMM IVI-COM causes runtime-error in Ivi DMM Read Single Point: Component Works IVI Control Error: The IVI Read operation failed for logical name 'SampleDmm'. Details: Attribute ID not recognized. [IVI Error Code: BFFA000C] Source: TSIviStepTypes
Skipping Ivi DMM SFP -step removes that error but next one waits in Ivi DMM Configure Multi Point: Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'. Details: Attribute or property not supported. [IVI Error Code: BFFA0012] Source: TSIviStepTypes
Skipping multi point steps helps until Ivi Switch Connect where another error hits: Component Works IVI Control Error: The Connect operation failed for logical name 'SampleDmm'. Details: No path was found between the two channels. [IVI Error Code: BFFA2011] Source: TSIviStepTypes
I find some similarities in forum post that involves HP 34401A and IVI .
According to IVI-C Class Driver Support for IVI-COM Specific Drivers the fault might be in 64 bit system (the note in the end). Is this the case? I can't use IVI-COM-drivers in 64bit system?
Example's default DMM Hewlett-Packard 34401A Digital Multimeter simulation works perfectly in unmodified example(it has IVI-C). It even shows simulated numbers in the SFP which is zero all the time with Agilent.
Has anyone succeeded to simulate 34980A properly in TestStand? Any knowledge about how to solve this thing? Any help is welcome. Thank you.
Setup:
-Teststand 5.1
-Windows 7 64bit
-IVI shared components 2.2.1
-Visa shared components 1.5 64bit
-Agilent IO libraries suite 16.3 Update 1
-Agilent 34980A IVI Driver 1.5.3
-MAX/Agilent 34980A published APIs:
-IviDmm 4.1 IVI-COM (IVI-C tried with less success)
-IviSwtch 4.0 IVI-C & IVI-COM

Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
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.

Accessing IVI-COM Driver through TestStand ActiveX Steps

Hello
I need to control a Agilent 6691 PowerSupply with TestStand. For this PowerSupply only an IVI-COM Driver exists, no IVI-C Driver. I tried to access it with the ActiveX Adapter Step. But when I try to create a IAgilent66xx object it produces an error without an meaningfull error message.
Is there any way to get this working ?
Thanks
Olli

Hi !,
- I am working on similar need (using Tek scope IVI-COM driver) and currently facing some problems, I was looking for help and saw this thread of discussion almost two year old. Is there any solution to this problem that is now found within two years ?
- I am trying to use IVI-COM driver for scope using ActiveX/COM adapter in TestStand (Ver. 3.5) and when I try to execute sequence I get message as ""Attach to Active Object" in automation call failed. Operation unavailable". Attached is sequence file I am working on.
Attachments:
Tek_scopeIVI.seq ‏21 KB

How to use IVI Driver in Labwindows

I want to use IVI drivers in LabWindows/CVI, but I don't know how! I know that it necessary to load the class driver. But how can I include the specific driver??? It is possible to add functions into a class driver? And what I have to do when the instrument should change?
Thanks for your help!!!

Hi Chris,
If your goal is to create an interchangeable application, you do have to use a class driver. National Instruments provides Measurement and Automation Explorer (MAX), a Graphical User Interface for configuring IVI. MAX is usually installed with one of NI's Application Development Environments such as LabVIEW or Measurement Studio, or with one of NI's hardware product drivers such as NI-488.2 or NI-DAQ.
The IVI configuration utility allows you to interchange instruments without recompiling or relinking your application source code by configuring logical names. The user defines which specific instrument he wants to associate with a logical name and IVI takes care of the rest. If at a later time, the user decides to swap the instrument and use a diff
erent one, all he has to do is change the entry in the configuration utility so the logical name points to a different specific instrument driver (driver session).
So, the important point is that you have to have both, IVI class and specific driver installed on your system, and then you need to configure them in MAX. MAX 3.0 now has a built-in help to guide you through the configuration process. In the case that you still do not have MAX 3.0, you can find an application note about the IVI configuration in MAX 2.x on NI's Developer Zone: http://zone.ni.com/devzone/devzone.nsf/webproducts/E2947DB2FF0DD9FE862569FD006EB939?opendocument.
As for the adding functions into the class driver, the answer is no, that is not possible. You can certainly use the specific driver functions in the application which is written using the class driver functions but then your application will not be completely interchangeable in the future. However, this way you will just isolate a small portion of y
our code that you will need to change later on when you decide to change the instrument.
I hope this makes sense.
Regards,
Vesna Jadric
Instrument Drivers/IVI

Using IVI drivers in LabView 5.1.1

Hi,
We have a set of IVI drivers ( class specific and custom specific ) developed in LabWindows/CVI 7 and IVI Compliance package 2.2 version. We want to use these drivers in a new application in LabView 5.1.1 version. I want to use the class specific drivers through the IVI class drivers in LabView 5.1.1 so as to cater for the interchangeability aspect configuring the logical names in MAX. Finally I would be creating an Installer with executable and distributing it.
I want to clarify few issues.
1. Please let me know whether I need to install any other software's apart from NI DAQ, IVI compliance package 2.2 and the Installer in the User PC. Does the IVI engine, Tool set, Class drivers for LabView 5.1.1 come with the compliance package?
2. Does MAX 2.1 support IVI drivers, interchangeability through class drivers and compliance package 2.2 or should I use MAX 3.0 for best results?
3. When I import a IVI driver (developed using IVI compliance package 2.2) to LabView 5.1.1 and try to use the functions there are some problems in the functions. As per the IVI specifications 3.2, functions GetErrorInfo and ClearErroInfo are changed to GetError and ClearError. But it shows error in the functions at those points and we have to go to IVI Error Converter.vi and change the configuration of the library node and direct it to the GetError function. Do we have an alternative to avoid this process?
It would be of great help if somebody can clear these issues.
Thanks & Regards,
Siddu

1. The IVI Compliance Package (ICP) 2.2 installs the IVI Engine and Class Driver support for LabVIEW 7.0 and 7.1. It does not install Class Drivers for LabVIEW 5.1.
2. ICP 2.2 requires MAX 3.0 to get the IVI interchangeability provider in MAX.
3. LabVIEW 5.1 was released before the official IVI specifications 3.2 were approved. Prior to 3.2, the function names were GetErrorInfo and ClearErrorInfo. Those changed to GetError and ClearError. The LabVIEW wrapper generation tool that shipped with LabVIEW 5.1 is not aware of these changes. Therefore, my suggestion is to upgrade to a later version of LabVIEW so that you will have support for the current IVI specifications and class drivers.

Use .cs & .vb files in teststand

Hi
I have lot of code in C# and VB i can use with this code in TestStand ?
please send me information and example how i can doit
Thank you
Ran s

Ran,
C# should be compiled as DLL and then used in the .NET adapter.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Using IVI driver for reading delay in MSO6104A

Hi,
I have the NI IVI driver for the MSO6104A scope. The driver is functional and I manage to use it.
My scope has a function of measuring delay between two different channels. But, how can I read the Delay measurement using IVI scope step?
Is there any other way of reading this measurement?
Thanking in advance
Solved!
Go to Solution.

As far as I know, interchannel delay is not a supported IVI measurement function. So, you can complain to ivifoundation.org first of all. Or, in a code module, you can use the instrument specific driver to get the measurement. This would make the application 'non-IVI' so most of the reasons for using IVI in the first place are gone. Or, retrieve the waveforms from each channel and calculate the delay in a code module.

Using IVI driver for Keithley 6485

I am trying to learn how to use IVI drivers. I installed IVI drivers for two instruments, an HP34401A and a Keithley 6485. I was able to get the HP to work in simulation mode (I don't have the hardware). I am also trying to get the 6485 working in simulation mode. The attached vi was provided by Keithley. I configured a logical name in MAX, but this name doesn't show up as an option when I edit the "logical name" control on the front panel. I changed the Initialize vi to Initialize with Options and added a command string control to set the mode to simulation, manually entered the correct name in the control, and ran the program. No error was indicated in the Initialize vi. After the configuration vi runs, however, the following error was flagged:
Error -1074135023 occurred at IviDmm IVI Error Converter.vi
Possible reason(s):
Primary Error: (Hex 0xBFFA0011) Function or method not supported.
Elaboration: FunctionId: 46, FunctionName: ConfigureMeasurement
Complete call chain:
     IviDmm IVI Error Converter.vi
     IviDmm Configure Measurement.vi
     KE6485_ZeroChk_LV86.vi
This error is being generated by IviDmm Configure Measurement.vi, which is apparently installed NI code. Specifically, the error appears to be thrown when Call Library Function Node is invoked and IviDmm.dll is called. I wasn't able to track down any further info as to the meaning of these error codes.
Thanks for your assistance.
Attachments:
KE6485_ZeroChk_LV86.vi ‏14 KB

Hello,
3rd party devices will show in MAX only when that device is listed at a specific place within your computer's registry. Non-NI hardware may not show up in MAX.
As far as the logical name is concened, unfortunately, you will have to contact Keithley to get a better understanding of their code.
You could download our IVI driver from the link below as you might have better luck with it. You can find any of our 3rd party drivers at www.ni.com/idnet.
Keithley 6485
http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=238
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

Problems in using Ivi driver ke230y in "IviDCPwr Measure [MSR].vi"

Hello all,
I have a problem in using IVI driver (ke230y) to control keithley2303 powersupply with LABVIEW 2013.
After I initialize and config ke2303 well and run to "IviDCPwr Measure [MSR].vi", it ocurrs errors. While lasting about 15 seconds and then reports errors as attached:
The code (attached) when I test with other powersupplies such as agilent66309d and keithley2306(with ivi driver ke230x), it runs well.
So I've no idear about this problem with keithley2303 powersupply, can you guys ever meet this problem and may reply for me to fix it.
thank you for your reading and help!
best wishes,
Phil
Solved!
Go to Solution.
Attachments:
error.jpg ‏36 KB
code.jpg ‏43 KB

I don't have the any driver's source code (such as ividcpwr.dll source code), how can I modify the specific driver through labwindows.
Follow your advice I use I/O trace to get trace as follows:
1 IviDCPwr_InitWithOptions ("ke2303", VI_FALSE, VI_TRUE, "", 0x0C913064) VI_SUCCESS 14:45:10.675
2 IviDCPwr_ConfigureVoltageLevel (ke2303, "CHANNEL1", 3.8) VI_SUCCESS 14:45:11.405
3 IviDCPwr_ConfigureCurrentLimit (ke2303, "CHANNEL1", 0, 3) VI_SUCCESS 14:45:12.104
4 IviDCPwr_ConfigureOutputEnabled (ke2303, "CHANNEL1", VI_TRUE) VI_SUCCESS 14:45:12.824
5 IviDCPwr_Measure (ke2303, "CHANNEL1", 1, 0) VI_ERROR_TMO 14:45:16.207
6 IviDCPwr_GetError (ke2303, -1073807339, 0, "") 0x00000037 14:45:32.991
7 IviDCPwr_GetError (ke2303, -1073807339, 55, "Primary Error: ..................") VI_SUCCESS 14:45:32.991
8 IviDCPwr_close (ke2303) VI_SUCCESS 14:45:33.847
I cannot see any GPIB command in the trace but some IviDCPwr functions.
Besides, if I know any bug (eg. some wrong GPIB command) in ividcpwr.dll, how can I modify it before I get it's source code.
Pls teach me anytime in your conveneince.
thanks!

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

Who can help me using IVI powersupply in Teststand!

Hi there,
I'm newly in working with Teststand and IVI drivers and
have a little simple question.
I have a step to configure the powersupply.
The logical name is "SamplePowerSupply", the operation
is "configure". If I change to the "Validate IVI Configuration" form, uncheck the simulate checkbox
and press the button "Init" I get the following errormessage:
....returned an error: -1073807343 ... Insufficient location information or the requested device or resource is not present in the system (-31619).
But in MAX I see my powersupply and it seems to work correct.
Thanks for any answer !!
Mr.Pe

Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
Scott Richardson (NI)
Scott Richardson
National Instruments

NI-FGEN Problems in TestStand using IVI Calls

Hello:
I have a problem. When using a 5411 under TesStand, making IVI calls the 5411 O/P is distorted when I configure it to O/P a simple Waveform ( 1.544 MHz, 5Vp-p 0V DC Offset). The same setup using either a CVI application utilizing the function panel or the soft front panel yields a fantastic O/P. If I can not make IVI calls from TestStand then what is the use?
Help.... Very fruntrared and on a deadline
cheers...

Hello Craig -
I've quickly looked over the CVI IVIclass demos including the quick bit of Fgen code, if you run this project and monitor the output in MAX you are seeing good results? If so, yes I'd check the settings in your IVI steps in TestStand. (If you haven't seen it yet try \CVI\samples\iviclass\fgen.prj)
CVI also ships with function-by-function class help files which on my machine are located at C:\vxipnp\winnt\niivi\Help, I point this out since the demo sequence for IVI in TestStand makes a direct DLL call to set up the soft front panel as a non-interactive window... there are a few other cases where features of the driver are not accessible just by editing the step properties, but that is across the board, so again if it worked in CVI it should work here.
I'm going to attach a quick little TestStand sequence (written for TS 2.0.1f1 the current release) to this project as a way of you just loosely troubleshooting, all it will do is launch the soft front panel and use the controls to try and set up your waveform... Try it once with the simulated instrument, or just go straight to altering the FileGlobal variable to point to your logical name and tell me if you get better or worse response?
To alter the internals of the call to hardware right-click on the second step and choose 'edit Fgen'... you may want to examine your clock, the channel settings and extensions to make sure anything you configured in your code is configured here... The only thing I am still unsure of is whether you were using the default sine waves or if you were definining something arbritrary, the 5411 does have the ability to set sample counts/ waveform size /sampling rate. You may want to try setting your Arb SampleRate higher, or fall back on a quick DLL call to set some attributes manually if you can't access them any other way.
You can use the IVI operation "get Information" on a particular logical name to aquire the current/default settings of your instrument.
Below is some text I extracted from a LabVIEW example (I don't know how useful the actual code will be, but perhaps this is the cause of your undersampled data?) Jitter can also be a symptom of undersampling. I will try and check with the hardware team for you and post if I have any other ideas...
-Regards
Elaine R.
National Instruments
http://www.ni.com/ask
--Extracted from an example "Generating Segments of Larger Waveforms with the NI 5411" --
>>To set up sample counts, pass the array of sample counts you want to use to create a new arbitrary sequence. The array must have at least as many elements as the value you specify in the Sequence Length parameter. Each Sample Counts array element corresponds to a Waveform Handles array element and indicates how many samples of the given waveform to generate. Each element of the Sample Count array must be larger then the minimum waveform size and a multiple of the waveform quantum. You can obtain these values by calling niFgenQueryArbWfmCapabilities.
For the NI 5411, you can use a minimum of 256 Sample Counts, with a quantum of 8, which is the same as creating a waveform for the NI 5411. The other restriction is that you cannot use a number greater than the number of samples in the waveform.
In terms of use, the NI 5411 only generates the number of samples that are indicated by the Sample Count number regardless of how many actual samples are in the waveform array downloaded to the NI 5411.
Attachments:
fgen.seq ‏50 KB

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

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

Using IVI-C attibutes in TestStand

Similar Messages

Maybe you are looking for