Hello,
We are using several N5768A power supplies in one application which monitors the instrument state by polling the voltage output level, current output level, output state and protect flags. These parameters are requested individually by the related SCPI request, sent to the instrument through the LAN/VISA API. The response to each request is read 100ms later.
This way to communicate seems fine for most of our power supplies, as we are able to monitor them during hours/days without having any glitch. One of the power supply reacts differently however : after a few hours (4 hours seems the average), one response to one of the SCPI request is not read by our application. We are able to communicate again with the instrument after closing/reopening the connection but this workaround is not acceptable for production code.
SCPI sequence :
viPrintf : MEAS:VOLT?
Sleep : 100ms
viScanf : MEAS:CURR?
Sleep : 100ms
viScanf : OUTP:STAT?
Sleep : 100ms
viScanf : STAT:QUES?
Sleep : 100ms
I have looked through the documentation for some clue, and haven't find any for now. Do you ?
Thanks,
Frederic
We are using several N5768A power supplies in one application which monitors the instrument state by polling the voltage output level, current output level, output state and protect flags. These parameters are requested individually by the related SCPI request, sent to the instrument through the LAN/VISA API. The response to each request is read 100ms later.
This way to communicate seems fine for most of our power supplies, as we are able to monitor them during hours/days without having any glitch. One of the power supply reacts differently however : after a few hours (4 hours seems the average), one response to one of the SCPI request is not read by our application. We are able to communicate again with the instrument after closing/reopening the connection but this workaround is not acceptable for production code.
SCPI sequence :
viPrintf : MEAS:VOLT?
Sleep : 100ms
viScanf : MEAS:CURR?
Sleep : 100ms
viScanf : OUTP:STAT?
Sleep : 100ms
viScanf : STAT:QUES?
Sleep : 100ms
I have looked through the documentation for some clue, and haven't find any for now. Do you ?
Thanks,
Frederic
That seems strange to me. The wait time for the response is very generous so it cannot be that.
Does this happen on the same unit every time or is it a different unit each time you run it? What IO Library are you using? Can you check the MAC addresses of the units that you have?
Thanks!