NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

IVI call fails with a bad channel name that is in fact OK

Hi all,

In my ATE system I operate a Agilent double power supply E3646 with IVI calls from TestStand 3. All operated for a long time. After summer vacation I get an error indicating that a virtual channel name was bad. In fact both MAX as well as the IVI step configuration showed this virtual channel name and exactly with the same spelling.
A similar virtual name for the first channel of the device is still working properly.
Any ideas?

Here's what TS reports:
------------------------
Error executing substep 'Post'.
An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types'
An error occurred while executing the step.
TestStand IVI Step Type Error: The channel name 'Ch2(&1!)' is not
configured for logical name 'Netzteil1_Mains'.
Source: TSIviStepTypes
---
-17304; Unrecognized value.
---
Step 'PwrSrc_measM' of sequence 'GTM_PS_GetPortVoltage' in 'getemedParallelModel.seq'
------------------------
0 Kudos
Message 1 of 3
(3,465 Views)
Hello Lul,

Has anything changed on your system? In particular regarding your drivers? There have been 2 driver CD releases since feb this year.
If the virtual channel name seems to be the problem, remember that IVI names are now case sensitive.
Please post some more info if this does not help.
0 Kudos
Message 2 of 3
(3,465 Views)
Hello nschdllb,

as far as I remember, nothing changed. Thats why I wrote '...and exactly with the same spelling...'.
I think I found a misbehaviour of either those IVI drivers or my sequences ;-)) :
1. One needs to have commands to those devices in a defined sequence. For instance one cannor read a power supply actual voltage setting before this power supply was initialised and configured. This is quite easy in normal runs, but sometimes hard during exceptions or when testing code.

2. There's a bug in the drop-down-lists of the IVI call steps. Those list fields tend to loose the values chosen by the operator. Ome has to 'cut' the value and repaste it in order to ensure this setting.
At this time everything is fine again.

Enjoy NI-week!

Greetings from Ge
rmany!
0 Kudos
Message 3 of 3
(3,465 Views)