Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

gpib connected to sr245, timeout error EABO

I am trying to use a GPIB-USB-HS to communicate with a SR245. When using measurement and automation explorer (version 4.2.1.3001) I am able to see the device, its primary address and I am able to write to it. I am unable to read from it. No matter what command or termination characters I use (\r, \n, EOI) I always receive the EABO timeout error. This is an older device which doesn't respond to "*IDN?". I have looked through a number of older discussion forums on this topic but so far the solutions don't work.

Thanks,
Margo
0 Kudos
Message 1 of 3
(3,968 Views)
Hi Margo,

It's very odd that you can write to the device but not read from it. Ar3 you trying to communicate using Measurement & Automation Explorer. If not we need to try it there. If so make sure you are sending a command that requires a response, check your manual for this,  and then try running NI-SPY. This Knowledge Base will show you how to get a good capture. NI-Spy can show you everything that is happening on the bus and if the device is even responding. If it isn't this may be the issue.



Regards
Krista S.
Applications Engineering
National Instruments
0 Kudos
Message 2 of 3
(3,956 Views)
I am also having problems like these with SR245. I did have the interface working perfect under Windows XP SP1/Labview 6.1. Since returning to use it now, I initially had GPIB Write errors.

On upgrading NI VISA and NI 448.2 drivers to latest versions (3.4 and 2.5) I seem to be able to write to SR245 (notably with different termination characters than previously!), but get no replies.

Checking on NI Spy shows no specific errors, only the waiting for a reply that doesn't come (I set a long timeout).

One further nail is that I had downloaded and used the SR245 GPIB Labview driver (available on the developer zone site). I remember this working well in the past, but now it suffers from the same communication problems.

This all seems to me to be some sort of driver (VISA?) issue, possibly related to Windows XP-SP2?

0 Kudos
Message 3 of 3
(3,704 Views)