NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

I want use IVI in TestStand, but a ClassType does not exist for that instr.

I want use the IVI Drivers of an AC-Powersupply 61601 from Chroma ATE in TestStand 3.5.
There is a IVI driver available form Instrument Driver Network or direct at Chroma ATE.
I have successfully installed:
- the latest Devicedrivers (shipping with TestStand3.5)
- "NI USB-GPIB HS"
- and the IVI Drivers for the AC-Powersupply 61601
 
Now the Problem:
None of the IVI Steps in TestStand fits with that class of instrument
(e.g. IVI-Dmm, IVI-Scope, IVI-Fgen, IVI-Power Supply, IVI-Switch)
I try to select the Logical Name and then the IVI Warning Message will show:
"There is no IVI Logical Names or IVI Driver Sessions defined...."
BUT I HAVE defined that in MAX!
 
Advanced Info:
In MAX i added all "Published APIs" which were available. (IVI Drivers=>Advanced=>Instr.Driver Softw.Modules)
Then the IVI Warning Message disappeared and i can select a logical name.
Filling in in some (default) values and click "Validate".
With Simulation ON or OFF - i always get errors like " ... not supported..."
 
None of the available IVI 'classType' like 'ClassType_Dmm' will work.
So what can i do?
Thank You for Help
0 Kudos
Message 1 of 7
(4,622 Views)
hello martin greil,

the step types in TestStand were designed for ease of use. of course, often with ease of use, customization and performance is slightly sacrificed. thus, issues like this arise where these step types simply do not fit.

so basically it would be better to use a code module to access the IVI driver for your powersupply. the IVI driver for the programming environments are much more powerful, than the IVI steps in TestStand.

kind regards,
Robert H
NI germany
0 Kudos
Message 2 of 7
(4,583 Views)
well, the existing driver works also with LabVIEW, but the big problem is the LabVIEW_to_Driver interface!
It has only one method to get measurements from the instrument.
This routine will get always all 12 measurements and this will always take 9.5 seconds !!!
(unusable for fast production mode)
 
In the meantime i have written a new editor and a TestStand step typedefinition that looks and feels exact like the IVI-Tools Editor.
So my editor can handle the correct IVI-Attributes and the user will not recognize my workaround.
None of the IVI-Attributes were documented, so i scanned them with a text editor in the Driver DLL.
 
Anyway, thank you for try to help
greetings
Martin
0 Kudos
Message 3 of 7
(4,575 Views)

I had this same problem a while ago. Basically, Teststand IVI functions are for  IVI class drivers (Power Supply, DMM, Scope, etc). The power supply IVI class driver is actually for DC power supplies. That Chroma PSU is a AC/DC power supply and it uses a IVI custom specific driver, it does not use the DC power supply IVI class driver. I ended up using the Chroma drivers in Labview & called that code in Teststand.

For more information on the IVI definitions of class drivers and such, see http://www.ivifoundation.org/.

 

 

 

0 Kudos
Message 4 of 7
(4,555 Views)

HI,

 

I wanted help on creating IVI drivers for Chroma DC power supply.

 

I have the .dll file for this supply, but when i take the address and send the command using VISA, I get an error  saying invalid session.

So is there any procedure to follow for IVI class drivers. Cant we send command using VISA Write and Read?

 

Regards,

Sailesh 

0 Kudos
Message 5 of 7
(4,062 Views)

What do you mean by 'creating IVI drivers'? You say that you have the dll which implies that you already have the IVI driver.

 

No, the IVI resource is not the same thing as a VISA resource. Why are you trying to use VISA Write and Read with the class driver?

0 Kudos
Message 6 of 7
(4,045 Views)

Hey Dennis,

 

It shows the IVI driver for this particular instrument in MAX.

I would like to know how to go ahead with creating softpanel with the help of these drivers.  

0 Kudos
Message 7 of 7
(4,013 Views)