LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR CODE 6 GPIB READ

Solved!
Go to solution
Highlighted

Hello,

I attach a VI that measures and displays Capacitance as a function of voltage swept at a "keithley 590" meter.  In the llb file attach, i am using the vi called "590-CV Measurement.vi"

I get the error "Error code 6 in GPIB Read  in 590-CV Meaurement.vi".

 

The VI is supposed to display data as a table and as a graph. I see the keithley instrument sweeping the voltage but no data is displayed and the error code 6 which means "I/O operation aborted" as per

http://zone.ni.com/reference/en-XX/help/371361B-01/lverror/gpib_error_codes/

 

is displayed. Could anyone please help me on what is wrong?

Thanks a lot

poli

0 Kudos
Message 1 of 5
(3,706 Views)
Highlighted
Are there any other GPIB function calls being made whenever the 590-CV Measurement.vi is being called?  You can verify this by using NI-Spy to monitor the GPIB bus and see what all calls are being made.  Also, you could try using highlight execution with the 590-CV Measurement.vi open to see where in the subVI it's being help up, timing out, or erroring.  These would give you a better idea on where exactly the problem is occurring.  Let me know once you have more information about what part of the 590-CV Measurement.vi is causing the problem.
David Pratt
Group Manager for Application Engineering Specialists | Automated Test
NIC
0 Kudos
Message 2 of 5
(3,674 Views)
Highlighted

Hello,

i monitored the error message using NI Spy and it is attached below here.

Please help me to take the next step to fix this error code 6 in GPIB Read in  590 CV-Measurement.vi

Regards

Neel

 

0 Kudos
Message 3 of 5
(3,652 Views)
Highlighted
Solution
Accepted by topic author poli

Hey Poli,

 

Thanks for the files.  I've been looking through the intrument driver and the spy file to correlate the behavior we're seeing with the function calls being made.  I would like you to try two things and let me know the results. 

 

First open the 590 CV-Measurement.vi and view the block diagram.  In the Event Structure, select the "Run" event.  In here, on the second line of function calls you'll fine one labeled GPIB Read.  The top of this VI has a terminal for Timeout.  Create a numeric constant of value 0 and wire it to this terminal.  Run your program and see what behavior you see.

 

Once that test is done, delete the changes you made (the addition of the numeric constant).  Then change the numeric value connected to the same GPIB Read command to any value less than the 20000 it's set to (i.e. 10000 or something).  This will change the number of bytes the function is trying to call and hopefully prevent it from timing out.

 

Let me know what results you get.

David Pratt
Group Manager for Application Engineering Specialists | Automated Test
NIC
Message 4 of 5
(3,627 Views)
Highlighted

thanks  a ton david,

the problem is solved.

the first approach of setting timeout to 0 s  fixed the bug.

Thanks once again

poli

 

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