02-19-2022 06:18 AM - edited 02-19-2022 06:40 AM
Only happens on read, regardless of the command, they can be two different commands, the second and any following will timeout. The device was functioning perfectly for 4/5 months. If I close and reopen the session I can read the result of a previous session, but I can never read anything past the first '\n' character. This applies to reading bytes one by one as well. I have another GPIB device on a different hub that is functioning as expected.
02-21-2022 12:17 PM - edited 02-21-2022 12:19 PM
It appears that you are clicking on the WRITE then READ buttons in NI-MAX. If you click on READ again, you should expect a timeout. By clicking on WRITE, you inform the piece of equipment to perform a particular task (Provided the command is correct) and stores the result in the buffer (if the command ends with a "?"). When clicking on READ, the data in the buffer is extracted from the buffer and sent across to the system controller. When another READ occurs, there is nothing in the buffer to send and as such will not send anything and timeout.
Instead, click on the QUERY button. It acts by performing the WRITE followed by the READ command and should be able to be performed repetitively once the data is acquired from the buffer.