IVI usage

[basha]

Hi,

I am trying to control the Power supply(TTi QL355TP) i did all the prerequisite tasks like installing proper drivers , had proper VI , now i am able
to communicate to my device using labview by reading & writing the voltages & currents to the device (using ...GPIB0::7::INSTR)
Up to this point its clear to me.

1. I was wondering what is the difference between IVI instrument usage(Scope, DMM,Supply etc)  in Teststand & the labview  VI that i had built for controlling the supply(i.e. for communicating with the power supply unit). I hav  constructed by initilazing the device, configuring. reading & closing the device(i.e. using sub VI's when the driver was installed).
Actually i tried to communicate to the power supply unit that i was  using  by IVI -C to find out what was the difference but i havn't  succeeded in that.

2. I was continously getting the below mentioned error:

An exception occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'
The specified IVI logical name is not defined in the Measurement and Automation Explorer.
Warning: All IVI names, such as logical names or virtual names, are case-sensitive. If you use logical names, driver session names, or virtual names in your program, you must make sure that the name you use matches the name in the IVI Configuration Store file exactly, without any variations in the case of the characters in the name. 'IVI::"TQLP"' is not a driver session name
Source: TSIviStepTypes

I have checked the other threads for solution  but it hasn't solved the problem.

Please kindly  pour your ideas which helps to get out of the above mentioned 2 problems. Thanks for your time.

Bash

[Dennis_Knutson]

As explained here, an IVI driver is a vry special type of instrument driver. If you have an actual IVI driver (and from a previous post, it does not apear that you do), then it has to be installed and configured in MAX. Whether in LabVIEW or TestStand, you would then use a class driver (i.e. IviDCPwr) instead of an instrument specific driver. When you use the class driver, you can then substitute an instrument from one vendor with an instrument from a different vendor without changing your program. You just have to reconfigure MAX.

[SengPoh]

By using the IVI driver, it has to be configured in MAX by defining the logical name, mapping the logical name with the available driver sessions in MAX. If the driver session does not have the dedicated functional driver, a new driver has to defined and mapped with the advanced simulated driver sessions.

The error message is generated due to no specific driver chosen or non-simulated driver. I spent two hours to figure out the functionalities, yet it has quite a number of parameters to be configured after I passed the first initialization. Yet the soft panel is not instrument specific, and not user-friendly at all to a normal programmer. 

In conclusion, it is better to put your tested VI into TestStand instead of exploring the IVI driver.