LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Generic file i/o error using VI's from the Keithley 2182A (v6) .llb

Solved!
Go to solution

Background description of system:

 

  • Operating system: Windows 7
  • Labview version: 2012 SP1 (32-bit)
  • Other hardware: Keithley 2182A Nanovoltmeter (via GPIB), controlled by these VI's

The problem:

 

A few days ago, I could run the program shown in the JPG perfectly fine. Now, I am always obtaining these generic file i/o errors. I used to be able to output files without a hitch, but now the program is always stuck in the loop attempting to get a measurement. I have already looked at potential timing issues, hard drive space issues, and path name length issues, but none of those seem to be the problem. Between now and the time when the program was working perfectly fine, no changes were made to the computer besides creating more .txt files for data.

 

I'm at a loss as to what to do right now. If there is anything else I could provide that you think would help, let me know and I will do that as soon as possible.

 

Thanks for reading!

0 Kudos
Message 1 of 3
(2,896 Views)
Solution
Accepted by topic author pbnjeff

Look at that error window a little closer.  You will see that the GPIB I/O was aborted.  This means that the communication with the instrument is having issues.  Common problems here include 1) using the wrong address, 2) the instrument not configured to talk over GPIB, or 3) the instrument is not hooked up the the GPIB bus.  First make sure you can communicate with the instrument through MAX and troubleshoot from there.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 2 of 3
(2,891 Views)

I just went in and made sure that the 2182A had the correct address and allowed GPIB control (both of which were yes). I also made sure the the GPIB cables were in there nice and tight. Everything seems to be working well now, so I think it was the cables themselves. I think this issue has been solved for now. If it happens again, then I will return so that the problem could be further diagnosed.

 

Thank you! And kudos to you...

0 Kudos
Message 3 of 3
(2,870 Views)