You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying this simple sequence of commands sometimes hangs the LAN interface of the Rigol DP832(A) with firmware version 00.01.14.00.03 and resets the connection:
Sometimes the connection seems to be only half closed so that further commands or a reconnection to the device fails until the DP832 is power-cycled. In this state the web interface does not work as well.
Doing the same directly via telnet 192.168.1.15 5555 does not cause any problems.
The text was updated successfully, but these errors were encountered:
And here I was thinking Rigol only screwed up their USBTMC implementation on basically all of their devices. This is likely a firmware bug, but I don't have access to one of those supplies so there's not much I can do about it. If you can send me a pcap file, I'll take a look at it, but the answer will probably end up being "don't use *RST on DP832 with firmware version XYZ."
I've hit something similar with a DP821A. I find that after about 15 minutes of doing nothing (after opening a connection) - it stops responding and a reboot of the power supply is all that I can do to make it work.
If you give me instructions to provide debugging information, i can add it.
Trying this simple sequence of commands sometimes hangs the LAN interface of the Rigol DP832(A) with firmware version 00.01.14.00.03 and resets the connection:
Sometimes the connection seems to be only half closed so that further commands or a reconnection to the device fails until the DP832 is power-cycled. In this state the web interface does not work as well.
Doing the same directly via
telnet 192.168.1.15 5555
does not cause any problems.The text was updated successfully, but these errors were encountered: