I’m getting an intermittent hang on GPIB Reads and Writes
with an Agilent 82357A USB-GPIB connected to an SR760. I have enabled the Agilent 488 and Tulip, and
have communication between my VI and the SR760.
However, GPIB Read or Write eventually fail to return and do not
timeout. I have adjusted the Agilent
GPIB timeout, as well as set the LabVIEW global timeout and fed a timeout value
directly into the GPIB Read and Write VI’s, with no change in behavior. The timeout just never occurs no matter how
short it is set. It would not be a big
problem if the function call at least returned after the timeout instead of
hanging the entire program.
Other VI’s operating in the same LabVIEW process still run
after a hang, until I attempt to close the hung GPIB VI. At which point a small window pops up saying
it is Resetting VI: <filename>.vi, and all VI’s in the process become unresponsive until it is killed in the Task Manager.
Is there a workaround for using GPIB Read and Write reliably
with the Agilent system?
Is there a way to wrap the GPIB Read or Write VI’s into separate
and killable threads so that I can try to make the calls, then timeout and kill
the calls/calling threads when they don’t return? This is a hack I've used in c++ with unreliable hardware/3rd party software.
Thanks for your help, please let me know if you need more
detailed information.
Message Edited by Nazgul on
01-22-2008 01:01 PM
