Integrate IVI in TestStand

Hi,
I've download form the website from Xantrex the LV drivers for those power supplies (I attach them). Is it possible to create an IVI driver for TestStand 3.1 with all those VIs? How can I manage it? Is ther some documentation on the web about this?
Thanks in advance,
Angel
Attachments:
XantrexDrivers.zip ‏1915 KB

You have to first configure MAX to use the specific driver you downloaded. I've got MAX 4.1 and when you open it, one of the options on the right side of the screen is "Configure my IVI Instrument Drivers". Follow the directions there and once that is done, you can use the IVI step in TestStand.

Similar Messages

PXI-5402 IVI in TestStand 4.2 returned "niFgen_InitWithOptions" Resource not found

Hi, i'm very new in TestStand.
I hope someone could help me.
I have a complete Sequence in which an ivi should initiate a PXI-5402.
(It's an old sequence i inherited. It's now my job to get it working again).
We have another System with an PXI-5401 (appears in MAX as Traditional-DAQ) which works fine with this Sequence.
I created a new Sequence to simplify troubleshooting with just the "IVI Fgen" step.
When in click on "Validate" and uncheck "Simulate" and hit "Init" i get:
niFgen_InitWithOptions returned an error: -1073807343 (0xbfff0011). Insufficient location information or the requested device or resource is not present in the system. If the resource descriptor is an IVI name, it must match the entry in the IVI Configuration Store in a case sensitive manner.
Source: TSIviStepTypes [Error Code: -31619]
In NI-Spy i get following Error
> Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)
I think i have configured everything correct. Please see attached Screenshot.
I tried different IVI-Logical Names...
To eliminate this as root cause, i reference direct the Driver-Session which is displayed correctly on the iviConfiguration.
Thanks in advance
Solved!
Go to Solution.
Attachments:
ivifgen-teststand.jpg ‏482 KB

Ok, i got it ...
It's the well known problem with DAQmx-Configuration within MAX.
Described under:
http://digital.ni.com/public.nsf/allkb/22CF7E6B27B6995B86256DDB0058F39B
I had to link Logical-Name with DAQmx-Device instead of PXI-Device.
Thanks anyway.

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

Adb integration with teststand

Hello All.
I am trying to integrate the android Debug Tool (adb) and Monkeyrunner with Teststand. I am quite new to Teststand, and I am unable to figure out how to use external programs and tools in teststand. Would be cool if someone can give me pointers on setting up adb with Teststand.
Thanks.
Harish
Solved!
Go to Solution.

Dear Stephan,
adb along with monkeyrunner is an API for writing script programs to control an android device. Its possible to write some python scripts that can be run via the Monkeyrunner tool which is a commandline tool to test certain packages. I am trying to integrate this with teststand so that i can migrate the already written python scripts directly to teststand and generate results based on the results.
Thanks.
Harish

Keithley 2000 DMM AC Read Overflow

I’ve been having problems controlling a Keithley 2000 DMM during AC volts measurement using IVI. When reading AC Volts the DMM will intermittently sense an ‘overflow’ and return the value NaN. I’m using IVI and TestStand 3.0 but get the same problem with IVI and LabWindows 7.0.
The set-up is as follows:
Device: Keithley 2000 DMM, GPIB device number 6
Device interface: GPIB, DMM set-up in MAX as GIPB0::6::INSTR
IVI Driver version: 3.02, downloaded from the NI web site
IVI Compliance Package version: 2.1
NI-488.2 version: 1.70
NI-DAQ version: 7.1.0f1
MAX version: 3.0.2.3005
For test purposes I’ve connected the DMM front panel input high and low and set the inputs mode on the Keithley to front, this should mean that I get a very low Voltage reading. I’ve then run the LabWindows/CVI IVI control sample code provided with the IVI driver. At the initialisation panel I’ve entered the logical name. At the configuration panel I’ve selected Volt AC measurement but left everything else as default. The second configuration panel I’ve left as default. At the Read panel I’ve left all setting as default. Pressing the read button up to about 20 times with about a second gap in between each press will eventually lead to an ‘overflow’ reading.
Any help/explantion will be appreciated
Steve

Here are the results of my investigation into this problem, it’s two fold:
1. Keithley have informed me that their engineers in the US have just seen the problem I’ve been seeing and are working on a firmware update. Currently here is no date for the release of the updated firmware but I’ll be informed when this it’s ready.
Note: I’ve found that the read AC Volts overflow problem only occurs when the read trigger delay is set to zero seconds.
2. The TestStand DMM IVI configuration step always sends a trigger delay of zero seconds regardless of the trigger delay set.
In my TestStand sequence the DMM IVI configuration sets the read trigger delay to 3 seconds but as noted above this is sent a zero seconds thus invoking the Keithley DMM AC Volts read overflow problem.
See attached VISA call log captured by NI Spy. The first 22 call are made when the DMM IVI configuration step is called form TestStand the next 22 calls are made by the IVI DMM sample code configuration provided by National Instruments when DMM configuration is run thorough LabWindows. Note call 12 (IVI DMM TestStand) has the trigger delay set to zero seconds (should be 3 seconds) and call 34 (IVI DMM LabWindows) has a delay of three seconds.
I’ve found a workaround as follows:
After each call to the TestStand DMM IVI configuration step an additional step that calls the TestStand IVI Tools step can be added. The IVI Tools step can be set-up to specifically configure the DMM Trigger Delay to 3 seconds. I’ve proven that this individual call does in fact send the correct trigger delay command to the DMM thus alleviating the AC Volts read overflow problem.
Can NI confirm that this problem does exist with the DMM IVI step and when they plan to fix it. I’ve attached the TestStand sequence file that I’ve been using to investigate the problem.
Thanks
Steve
Attachments:
DMM Overflow.zip ‏9 KB

"MAX 2.2" + "GPIB PCMCIA"

Bonjour,
Dans le but d'utiliser une alimentation HP6627 avec son driver IVI par TestStand, j'ai installé la version 2.2 de NIMAX, mais je suis incapable de voir ma carte NI GPIB(PCMCIA 186736C-01).Le driver NI-488.2 est installé (version 1.7) Dans la liste, après avoir cliqué "Créer un nouvel objet", je ne vois que "GPIB-VXI". Est-ce normal? Quelle est la marche à suivre pour configurer un instrument IVI ?
JMCe
Attachments:
CaptureEcran.jpg ‏125 KB

Il faut installer le driver VISA avec les bonnes options (GPIB bien sûr).
JMCe

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

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

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

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

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

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

IVI Configuration with PXI-4110 in TestStand

Hello All,
Set-Up:
PXI-1033 connected through MXI to a PC running Windows 7. LabVIEW 2014. TestStand 2014 (32-bit). PXI-4110 Power Supply and PXI-4070 DMM.
In MAX I can open both soft panels and control both units and they work great. In LabVIEW I can control both cards as well.
In MAX I have set up a driver and logical name for my DMM. This unit works great within TestStand using an IVI DMM step.
I then proceeded to setup the 4110 in MAX with an IVI driver and logical name. Here are my settings:
Name: ni4410_PS
Hardware: Added hardware asset and select the PS. This one is checked, no other assets are checked.
Software Module: NI-DCPower, 4110 is listed as a device that is supported.
Virtual Names: This is where I am confused, Under physical name there are four options that come up (0, 1, 2, and 3). This power supply only has 3 outputs so I am unsure why four come up. I have made 4 virtual names, one for each of the options. I named them ch0, ch1, ch2, and ch3 respectively.
When I put an IVI Power Supply step in TestStand everything seems to be working. I open the configuration window and set my values for each channel. If I try to validate the setup by unchecking simulate and click on init I do not get an error. As soon as I clic on 'Configure' or 'Show Soft Front Panel' I get the following error:
"The IVI Configure operation failed for lgical name 'NI PS 1'. Details: Extention capability not supported by instrument driver. (Base) (-30717)"
Any information would be appreciated. I tried playing with it for a couple hours yesterday and had a couple co workers try to help. We are all under the assumption that this should be working.
Thank You!!
Jesse
Solved!
Go to Solution.

Hi jesserzamora,
Have you seen this link: http://digital.ni.com/public.nsf/allkb/331F2717DBCD1F858625758200745773?OpenDocument
It discusses a similar failure with the IVI Power Supply step in TestStand.
Julia P.

Integrate IVI in TestStand

Similar Messages

Maybe you are looking for