Rigol DP832 networking problem, lost connections - Page 1
Forum section: electronics / testgear

author: edgelog
author_rank: Regular Contributor
timestamp: June 06, 2017, 06:05:59 pm
content: DP832Digital: 00.01.14.00.03Analog: 03.02.04.03.02.04Boot: 01.09Serial: DP8C19xxxxxxxI'm having problems with the networking on this unit. It keeps dropping out, and every now and then reconnecting. I'm connecting over the LAN to the DP832, an MSO1104Z, and a DG1022Z. The latter two: no problem. Same network.1. Using DHCP (also tried manual IP, but it's no better). It connects, then after a few seconds to a few minutes, it loses connection again. I'm pinging constantly from a desktop, that's how I detect it. At the same time, it stops responding over telnet. This on a local net 10.x.x.x (I have two, that's why I define it here).2. Connecting all three instruments to another net instead (172.16.x.x) and the problem goes away. Rock steady. As I said above, the function gen and the scope are rock steady on both nets.When it stops responding, it still shows the same IP, subnet, gate, and DNS on the I/O config screen. When I press "Apply" it recovers again. Until the next time.So I hooked up Wireshark via a "mirror port" on the upstream switch while on the 10.x.x.x network, and what I found was that just before the DP832 stops responding, there's an MDNS broadcast from my iPhone on both IPv4 and IPv6 with "cache flush" (whatever that means). Right after that, the Rigol sends out an ARP for the iPhone v4 IP, and right after that, it stops responding to pings. I could reproduce this a couple of times.So then I disabled wifi on my phone, only to encounter the same sequence, but then as my wife's phone did the same broadcast and the DP832 did an ARP.Note that the other net, the net where everything works fine, has no iPhone traffic; there are none on that net.I can't guarantee there's a correlation, but it sure is suggestive. Anyone else seen anything like this? Anyone else having the DP832 being flaky on the LAN? With iPhones?

author: jc101
author_rank: Frequent Contributor
timestamp: June 06, 2017, 07:16:37 pm
content: Yes, I saw exactly the same issues with a DP832A on a network using mDNS (I have lots of Apple devices on the LAN), it's a firmware fault and they need to issue a fix for it.I replaced my DP832A with a different supply, partly because of this issue and also to get an upgrade. I was scripting control of the PSU as part of an automated process and it was a real problem causing things to fail.

author: edgelog
author_rank: Regular Contributor
timestamp: June 06, 2017, 07:39:37 pm
content: Quote from: jc101 on June 06, 2017, 07:16:37 pm"Good" to know it wasn't just me. I'll probably just add a firewall upstream to allow only the desktop access to the Rigols. I have a few surplus SRXs.

author: edgelog
author_rank: Regular Contributor
timestamp: June 06, 2017, 07:55:12 pm
content: Just got a much simpler idea that seems to solve the problem. I have an old 100 Mbit USB 2 Apple network dongle, which I plugged into my iMac (on the 10.x.x.x) and set up to use the other local net (172.16.x.x). That way the iMac i dual homed, but doesn't pass any broadcasts (or even any other traffic) from one net to the other.Seems to work!

author: CustomEngineerer
author_rank: Frequent Contributor
timestamp: June 06, 2017, 08:10:13 pm
content: Other people also reported similar inhttps://www.eevblog.com/forum/testgear/rigol-dp832-firmware-updates-and-bug-list/. Especially checkout the last couple of pages. Pretty sure there have also been several other threads on the same issue, but am currently unable to locate them. Mostly its been reported on the DP832A, but do seem to remember seeing at least 1 other non-A version user report the same.

author: edgelog
author_rank: Regular Contributor
timestamp: June 06, 2017, 08:14:14 pm
content: Quote from: CustomEngineerer on June 06, 2017, 08:10:13 pmYes, something similar is described there, but it isn't mentioned if Apple devices were on the same net. jc101 above came to the same conclusion about that as me.BTW, my DP832 has all options enabled, so it's similar, though not identical, to a DP832A. Could have something to do with it.

author: CustomEngineerer
author_rank: Frequent Contributor
timestamp: June 07, 2017, 05:14:00 am
content: Pretty sure most other DP832 users also have all their options enabled. I know I do on my non-A version, and I've never had any network problems. Granted I don't do much network wise with mine, however it is always connected to the network.I'm not questioning your report, just trying to give you more data.

author: edgelog
author_rank: Regular Contributor
timestamp: June 07, 2017, 07:24:40 am
content: Quote from: CustomEngineerer on June 07, 2017, 05:14:00 amDo you have any iPhones on the same net?

author: CustomEngineerer
author_rank: Frequent Contributor
timestamp: June 08, 2017, 08:06:31 am
content: No iphones, though do use Macbook Pro (only apple device in house) on same network frequently.Edit: I do my best to keep the macbook well behaved on the network the best I can, but if I get some time this weekend Ill try turning on mdns on the macbook and playing around to see if I can get similar results.

author: edgelog
author_rank: Regular Contributor
timestamp: June 08, 2017, 08:18:11 am
content: Quote from: CustomEngineerer on June 08, 2017, 08:06:31 amI don't think you'll see anything. I've got four MacBook Airs and Pros, plus an iMac, on that net and the only correlation I could see was when iPhones sent out those mDNS "flush" calls. Never correlated with anything from the Macs. I haven't tested with iPads.But if you do see something happening, it would sure be interesting.Also note that the DP832 keeps working normally otherwise, but stops responding to the network. No reboots or anything (as I've seen described elsewhere).

author: RoGeorge
author_rank: Super Contributor
timestamp: June 08, 2017, 08:44:16 am
content: I've used DP832 with this script to log I/U/P at constant intervals while charging Pb batteries (no Rigol or IVI drivers, just a TCP socket):https://github.com/RoGeorge/DP832_charger_loggerNever lost a connection, even while logging continuously for many days. FW 00.01.11. Always used it with a fix IP, 192.168.1.4. No Apple devices, it is a separate net card with a switch for Rigol instruments only. It works with win10, too, which apart from Linux sends a lot of unsoliceted requests of all kind to all the network interfaces.

author: smuebreg
author_rank: Newbie
timestamp: October 19, 2017, 03:55:16 pm
content: I'm reviving this thread to happily report that Rigol seems to have solved this problem with a beta firmware, version 1.16 (available via tech support request, at least from Rigol NA).I had the exact same symptoms as the OP using FW 1.14. After installing 1.16 I've had a ping test running overnight with no lost packets. Hesitant to say completely cured until I've used it for a while yet, but sure seems like it.If you've been having the same problem, I'd encourage you to try FW 1.16 and report your results both here and back to Rigol in order that the firmware can be tweaked and/or finalized...

author: CustomEngineerer
author_rank: Frequent Contributor
timestamp: October 20, 2017, 02:27:43 am
content: Do you have the A or non-A model?

author: smuebreg
author_rank: Newbie
timestamp: October 20, 2017, 05:19:45 pm
content: Mine is a DP832 (non-A), although my understanding is that A and non-A versions are absolutely identical except for the colours of the front panel buttons and the UI display options. Internally the PCB is the same (the DP832 is labelled DP832A!).In any case, they use the same firmware, so this new version 1.16 ought to work equally well for either flavour.

author: edgelog
author_rank: Regular Contributor
timestamp: October 20, 2017, 06:17:50 pm
content: Quote from: smuebreg on October 19, 2017, 03:55:16 pmI've sent in a support request asking for 1.16. Hopefully I'll get it and I'll report back if it solves it for me as well.

author: edgelog
author_rank: Regular Contributor
timestamp: October 24, 2017, 07:42:00 pm
content: So, got the 1.16 FW from Rigol support. Did the whole upgrade dance, including analog boards 1 & 2, went smoothly. Have to say, though, their upgrade is a bit sloppy. Turned the display setup into default (green), the language into Chinese (fun!), and the "save" to default, not "last". Probably lost all other settings as well, haven't checked.Before upgrading I confirmed that the network dropped out as usual. After the upgrade, it doesn't anymore. Or rather, it seems to recover quickly, which it didn't before (see below).For some reason, going into "display" and adjusting brightness and contrast drops the network connection. But, it recovers quickly. While adjusting the contrast (or brightness), it keeps flashing the message "LAN Connected", while pings are dropped at a frightful rate. I'm guessing the display adjust procedure is hogging the processor, maybe? Other settings screens don't seem to have this effect, but the display adjust screen has these "fancy" bars you adjust by spinning the encoder knob. That part of the software could use some attention, I figure.Except for all that, it seems they've solved the networking problem. I haven't done much more than pinged so far, though.I should add: a DP832 (non-A) with all options enabled.

author: Silveruser
author_rank: Regular Contributor
timestamp: October 24, 2017, 08:30:30 pm
content: Are there any Version notes for the .16 version (maybe .15 as well) explaining what they changed or upgraded. I've seen very rare random resets (not LAN related), just wondering if any mention.

author: Dubbie
author_rank: Unknown
timestamp: October 24, 2017, 08:32:39 pm
content: Interestingly, I was working on something else at my bench and I plugged in a mains plug. It slipped slightly in my hand as I plugged it in so as the plug made connection, it sparked and crackled a bit with the inrush current.I noticed out of the corner of my eye that my DP832 lost it's network connection at the same moment.I wonder if interference on the the mains line or through the air caused it?

author: edgelog
author_rank: Regular Contributor
timestamp: October 24, 2017, 08:45:25 pm
content: Quote from: Silveruser on October 24, 2017, 08:30:30 pmNo, just got the bare GEL file with a PDF explaining how to upgrade a DP832. No release notes. I haven't seen 1.15, don't know if it exists.

author: CustomEngineerer
author_rank: Frequent Contributor
timestamp: October 24, 2017, 10:14:40 pm
content: Quote from: smuebreg on October 20, 2017, 05:19:45 pmThey are identical hardware. Was asking just so we have as much info as possible. My non-A has never had this problem.

author: edgelog
author_rank: Regular Contributor
timestamp: October 25, 2017, 08:23:03 am
content: Quote from: CustomEngineerer on October 24, 2017, 10:14:40 pmIt's probably triggered by mDNS from iOS devices (iPhones at least) on the same net, and you said before that you don't have any.

author: savyzzyz
author_rank: Newbie
timestamp: October 25, 2017, 12:40:26 pm
content: FWIW, I was experiencing the same problem but did not have any iOS devices on the net. In fact I completely isolated the DP832 on a separate router with my Surface Pro 3 tablet and still had the problem...although less frequently.FW 1.16 is working for me. I'll have to check for LAN dropouts in the display menu...I haven't been in there since the FW update.

author: bakadave
author_rank: Newbie
timestamp: February 13, 2018, 12:45:25 pm
content: can someone please send me the 1.16 GEL file?

author: savyzzyz
author_rank: Newbie
timestamp: February 13, 2018, 03:51:58 pm
content: Just ask Rigol support, they were happy to send it to me to try out. Providing feedback to them will help to get this finalized if it isn't already. Perhaps they even have a newer version to test out...

author: HB9EVI
author_rank: Frequent Contributor
timestamp: November 28, 2018, 08:03:43 pm
content: I'm sorry to bring that up, but can somebody send me version 1.16? On my request Rigol Support sent me Version 1.15 - after my complaint that I already have that one, nothing came anymore from their side

author: JDubU
author_rank: Frequent Contributor
timestamp: November 28, 2018, 10:42:06 pm
content: Quote from: HB9EVI on November 28, 2018, 08:03:43 pmThere is a link to 1.16 firmware in the first post of:https://www.eevblog.com/forum/testgear/rigol-dp832-firmware-updates-and-bug-list/It is at the end of the list of known firmware versions where it says: "beta release (download here)"

author: Telegraph
author_rank: Newbie
timestamp: March 27, 2019, 12:31:37 pm
content: I have the non "A" version and mine drops the LAN all the time. If I leave the instrument on all night the next morning can't even ping the device. Some times I can not even go 5 minutes without the connection dropping and having to power cycle the device. I entered a ticket on line with Rigol to see if I could get 1.16. I also downloaded it from the links posted here. If I don't one direct from Rigol I will use what I down loaded. Just in case they have modified the beta in any way. One thing I did discover. If I open a telnet connection via PUTTY to the DP832 and send *IDN?, then leave that connection open, I have yet to drop the network connection. Too early to tell if this is a work around but time will tell.

author: Telegraph
author_rank: Newbie
timestamp: March 31, 2019, 12:18:17 pm
content: I got the update from Rigol. It appears to have corrected the problem.

author: noisefreak
author_rank: Newbie
timestamp: December 12, 2019, 07:27:51 am
content: Hi,I want to confirm this issue, and report, that it is not truly fixed with firmware 1.16.We have 7 pieces DP832 here in an automated testsystem, and some are very vulnerable by mDNS packets, others are not. Our PC runs Linux Mint, which has installed avahi-daemon by default (which sends these mDNS packets). We have no Apple products here. One supply failed nearly every 10 minutes of operation. Others had no proplem for days. They run all the very same firmware (same binary, updated via USB flash drive, MD5 Sum: 3ebdd0f64636b67976a5c075945dc88f DP800Update.GEL)The misbehaveour isn't the same all the time. Somtimes the device is still controllable via buttons, sometimes it freezes completely, sometimes it is pingable, sometimes not. The common problem is, that it isn't reachable any more via TCP connetions on port 5555. Our script times out after 0.3 seconds. The only workaround is a power on reset. We tried reconnecting the ethernet cable or hitting "back" twice to enter local mode with out any luck.The Solution:I uninstalled the avahi-daemon on the Linux Mint test system:sudo apt uninstallavahi-daemonFurther we kept the network clean from any devices withmDNS.Before that I saw many mDNS packets in wireshark, and the devices failed regularly. Now they ran 1 day without any single problem.Wiresharkdidn't capture a single mDNS packet.Thanks to @edgelog for that hint with the mDNS packets!Greets, KarlVery vulnerable device serial number: DP8C213603321 with officially installed RS232 and Ethernet upgrades.