Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Second Instrument issues EADR (3) when our device is connected as an instrument

Using the NI PCI-GPIB we have connected our device (a part handler) to a teradyne test system and we have addressed our software to be a listener ie not a bus controller.  When the Teradyne system test software runs it is able to communicate with our device but we are apparently blocking communications to other devices.  Attached is the NI SPY log and the error is seemingly straight forward as if we are addressed to the same address as the the device that can no longer communicate but we quickly verified that we are set to different primary addresses.  I am unsure what other settings we are missing here or what might cause this error to generate when we are connected into the system but any advice/information would be most helpful.  I have also attached a jpg of the LabVIEW software we use to initialize the GPIB communications and it is pretty straight forward ie only a few command calls.

 

Some more info:  previously we were setting the SRQ line to tell the tester that we have a device ready for test and we initially thought that the SRQ line might be stuck and causing this error so we recently modified our code to respond a polling command to circumvent setting the SRQ to no avail.

 

 

Download All
0 Kudos
Message 1 of 2
(3,023 Views)

What leads you to think that you are blocking communication to other devices?

 

How did you verify that you are set to different primary addresses?

 

Can you create a smaller simple use case that is reproducable?

0 Kudos
Message 2 of 2
(2,977 Views)