LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

"visa_utils.c" line 97. col 14 ... A timeout occurred

I have a LabWindows/CVI 10.0.0 program that used to run and is now giving the titled error message.  I am using VISA 5.2 on a Windows XP machine.  I am trying to take some readings with an Agilent 34970A with a 34901A multiplexer card.  I am using an NI GPIB-USB-HS to interface with the Agilent DAQ.  This is being submitted with a FireFox browser (if it works) because IE keeps crashing.  I did forget to mention that I had uninstalled LabWindows and then installed it.  It stopped working after the reinstallation.  The uninstall was because IE kept crashing and when it crashed LabWindows would open up offering a debug.  Is any of this connected? 

0 Kudos
Message 1 of 5
(3,514 Views)

Hello Ccreiss,

 

I would like to check some things first:

 

Are you using the Agilent Technologies hp34970a driver?

You said this program used to work fine until you reinstalled the software. Did it never give any issues?

Can you communicate at all with it?

Are you running Agilent VISA and NI VISA simultaneously (since Agilent VISA could have control of the VISA resource)?

 

Please let me know.

 

Best Regards,

 

Alina M

Applications Engineering

National Instruments 

0 Kudos
Message 2 of 5
(3,498 Views)

I am using a home grown driver dating back to 2008 with a revision in 2010.  This would be the AG34970A.c program.  It is 365 lines long.  I copy can be provided upon request.  Correct.  No prior issues.  When I hit the green right pointing triangle, the error light on the 34970A comes on.  So there is some communication.  Recently installed VISA 5.2 had been running 5.0.  Upon installation got a window that said the existing visa32.dll will be renamed to “visa32.Agilent Technologies.dll”. 

 

 

0 Kudos
Message 3 of 5
(3,495 Views)

Hello Ccreiss,

 

It seems there is some kind of conflict between drivers. I recommend uninstalling NI VISA and Agilent VISA, and reinstall first NI VISA and then the Agilent I/O Libraries. After that, ensure you can see and communicate properly with the device. And then let’s try to use the CVI program. It should look as the pictures in this post.

 

Best Regards,

 

Alina M

Applications Engineering

National Instruments

0 Kudos
Message 4 of 5
(3,482 Views)

Interesting

I thought I owed people the end result

The plugIn for the 34970A is a 34901A.  My program for the DAQ had been calling channels 101, 102, etc.  There are three plugin slots.  The molded in identifier call them 100, 200 and 300.  The unit had gone out for calibration and when it was returned The 34901A had been moved to slot 300 and the blank plugin had been moved to slot 100.  So the call for the "empty" slot had nothing to report and hence timed out. 

0 Kudos
Message 5 of 5
(3,190 Views)