IviSwitch looses value when sending, "configure switch" configuration = TRUE

[david_feo]

Hi all,

we are currently evaluating Teststand 4.1 with a keithley 3706 system switch multimeter.

After a first enthusiasm, thinking this tool together with the switch multimeter fits perfect our needs, real life seems some harder.

Between several other problems, we need to tell the device, that the channel "s1com1" and "s1com2" are configuration channels.

Configuring the teststand step : Edit IVI Switch Step -> IVI switching, Configure Switch : Channels "s1com1", Configuration = True

leads to two actions observable in Ni Spy:

GetAttributeViBoolean(...,"s1com1", _IS_CONFIGURATION_CHANNEL , VI_FALSE)

SetAttributeViBoolean(...,"s1com1", _IS_CONFIGURATION_CHANNEL , VI_FALSE)

manually calling this class functions from an interactive CVI fp works as expected (setting it to VI_TRUE)

Does anybody have any hint what we could do wrong? Currently we are just before writing wrappers in cvi and skipping all the wonderful IVIStep Types in teststand.

Looking forward to any feedback

David Clus

[Scott_Richardson]

David -

What OS are you running on and what is your regional settings set to?

[david_feo]

Scott,

I'm runnnig Windows XP Prof. SP2. The regional settings  are german.

David Clus

[Scott_Richardson · Accepted solution]

David -

This might the same problem that we recently discovered in our internal testing. For the problem that we found, we will likely include our fix in an upcoming maintenance release. Can you verify whether the problem still occurs if you change your regional settings to English in the control panel? If the problem no longer occurs, can you use this as a workaround for now?

Message Edited by Scott Richardson on 10-06-2008 10:48 AM

[david_feo]

Scott,

thank you this would solve the problem and could even be a solution.

Due to some other restrictions when using IVI drivers with a combined Switch and DMM we said finally goodbye to using the IVI driver and implemented some wrappers around the low level instrument driver and use them as CVI DLL calls.

Teststand seems to be a great tool, even if some of the expectations (Take teststand, buy an instrument supporting IVI drivers, and start creating testscripts....)  are not directly fulfilled.

Regards

David Clus

[Scott_Richardson]

David -

I am glad that you have moved forward on your TestStand solution. We will still likely fix the issue you reported in an upcoming maintenance release. Thank you for letting us know that you hit this.