01-12-2011 02:34 AM - edited 01-12-2011 02:35 AM
Hello,
I'm getting "An error occurred while performing the switch operation 'Connect' for the following device 'VirtualDevice1'.
Could not perform the switching operation:
Details:An error has occurred while attempting to access device sw
Agilent34980A: IO error: .(Error = -1074118124)" while trying to switch a route from Teststand.
I am using Teststand 4.2 and NISE 3.0
I also want to mention that Switch configuration validation is Pass and if I use TestPanel it works. It doesn't work only from Teststand.
Please help,
Regards,
crsz
01-13-2011 11:28 AM
It appears you are making Switch Executive calls, but can you please explain how you are calling the switch functions in Test Stand (ie. LabVIEW calls, etc.). Also ,can you run a NI Spy capture to see what VISA commands are sent out and the errors returned as well when you run the Test Stand code.
It could be that the Agilent Switch does not like the calls that are being made. How is the Agilent Switch connected to your controlling PC (GPIB, USB, etc)? Can you try to make the switch calls using LabVIEW calls (if this is an option for you)?
Best,
01-13-2011 03:27 PM
Hello,
Thank you for replying,
I make the switch calls using Teststand Switching panel (Step properties)
It works from Labview (switch_executive_getting_started.vi) and Switch Executive API
Route Validation is Pass (in MAX) and it works from MAX - Switch Executive Test Panel
I am using a GPIB-HS USB interface and Windows 7
I will post ASAP NI Spy capture - if I remember correctly it fails only at the step nise(switch....)
Best regards,
Cristian
01-14-2011 01:22 AM
And NI Spy capture...
01-14-2011 05:54 PM - edited 01-14-2011 05:56 PM
Hi crsz,
Thank you for the reply. This has been documented before encountered with Agilent switches when using the GPIB interface with SwitchExec Calls in TestStand. Can you connect your device via USB to your host machine, or serial? This has been known to be a workaround, and is worth a shot.
See this post as well: http://forums.ni.com/ni/board/message?board.id=320&message.id=1006&requireLogin=False
Best,
01-18-2011 02:44 PM
Hi crsz,
Another follow-up question. Can you validate that the switch is able to work with the driver listed here: http://www.home.agilent.com/agilent/editorial.jspx?cc=US&lc=eng&ckey=1628832&nid=-34438.779160.02&id...
Best,
01-24-2011 06:12 AM
Hello Adam,
Sorry for my late reply, I had a few days off...
I will try it with the this drivers, but aren't they labview drivers? I intend to use IVI drivers...
Best regards,
Cristian Szabo
01-25-2011 01:35 PM
Indeed they are LabVIEW drivers. Can you provide a link to the IVI driver you are using? Further, can you try to use your device via USB or serial?
Best,
01-26-2011 07:40 AM
Hello Adam,
I have tried it connecting 34980A directly to USB and it's working indeed.
Currently I am using IVI-COM, IVI-C Version 1.4.2.0 for 34980A because in my configuration I have a 34939A not supported by previous drivers. I have also tried IVI-COM, IVI-C Version 1.3.10.0 for 34980A for NI Switch Executive but it was still not working.
Important thing is that when connecting 34980A directly to USB it works!
Another question - hope it is ok to ask in this post - not necessarily related to this error but related to 34980A IVI drivers. In my configuration I have a 34921A MUX card in slot 1. Why can't I see Channels "1043" and "1044" (in switch executive) for current measurements and why do I have "slot1com3" channel for this 34921A ? Channels "1041" and "1042" do exist though...
Driver setup is: dmm=true, slot1=34921A-2W, slot2=34932A, slot3=34939A
Thank you and regards,
Cristian
01-27-2011 04:21 PM
Hi Cristian,
Let's proceed by filing this question in a new post. This will help to better document the threads for future reference.
Best,