gpib_drv should have a way of not waiting on a reply for commands that have no expected reply
In the non-GPIB, TCP connected RR damper amplifiers, some of the setting commands to not generate any reply or acknowledgement to the command (e.g. POWER:ON).
But the driver waits for a reply anyway, times out, and resets things, wasting time and an unnecessary reset.
The driver should implement an option for a no-reply command where it knows not to expect or wait for a reply.
#2 Updated by Richard Neswold 5 days ago
I don't know if your GPIB devices can do this, but my networked power-supplies have a few commands that don't return anything. To get around this, I tack on a query command. So, for instance, when I turn on/off the supply, I add a command to read the on/off status:
io_lib:format("OUTP ~s;OUTP?\r", [bool_to_cmd(V)])
In these supplies, a semicolon separates multiple commands. The above command will set the output and then ask for the state. That's how I get all my commands to generate replies.