Hi Albert,
e.g. I use "GPIB Write" to send "UPDATE"+CRLF to the device. I tested both having a string constant
"UPDATE
"
and sending it with mode "0" , and removing the newline from the constant and using mode "3" or "6" of the GPIB Write vi.
The write succeeds this way. (And if I use another command instead, e.g. "PAUSE 1", I see the corresponding LED go on on the (hardware) front panel of the device accordingly. So the device receives and processes the command.)
Now, UPDATE should according to the manual give a lot of text. So immediately afterwards (next page of a stacked sequence) I call "GPIB Read" with the same GPIB address, number of bytes 200, timeout e.g. 1000ms.
For any "mode" parameter to "GPIB Read" except "2" and "10" I get a timeout and no data read (empty string).
For "mode" equal "2" or "10", a string containing a single linefeed (1 character) is returned.
This is how far I got, any further experimenting did not help...
Could it be that the device first outputs a blank line and then something else? I dont think so, since I tried also multiple subsequent read commands (copied the page of the stacked sequence), but they all give blank lines, or sometimes errors if the commands follow each other too fast (I think).
Best, Andreas