topic_solved Network device stops responding minutes after initial power-on
LazyMegaMan last edited by
I'm sorry if this isn't the right place to post this, but I'm having an issue with my new Duet 2 Wifi and I've truly failed to find an existing answer to this issue online. I've categorized this post as "Firmware installation", but I'm not convinced that's the best place to put it.
I began installing a newly-purchased Duet 2 Wifi yesterday evening. I followed the steps starting at https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7?lang=en to set it up, including a firmware update to 3.2. However, while attempting to test endstop connections, I noticed that the web server just suddenly stopped responding. I tried to find an answer online as to why this occurred, and found recommendations to unplug everything except the USB cable and test again. The issue persists. I redownloaded the firmware .ZIP file, confirmed file size matched what was stated online, and attempted to reflash the firmware (first by quickly uploading the .ZIP through web UI, then by manually adding the files to the SD card and executing commands M997 S0 and M997 S1). The issue still persists after both firmware flash attempts. I even went so far as to completely erase the firmware and manually push the firmware using BOSSA, but the issue still persists. I've confirmed that my wifi access point wasn't forcing any weird settings, but it's not; I have other ESP8266-based devices connected on the same wifi network long-term without any issues at all, but I checked the settings anyways.
The issue presents itself by the web server suddenly no longer responding to HTTP requests from the web UI. The web UI works perfectly fine for 1-5 minutes after initial power-on, but then suddenly disconnects from the server component and fails to ever reconnect. I can restore communication to the web server by executing M552 S0, then M552 S1, though this just restarts the 1-5 minute window of time that it'll respond before suddenly failing to respond any more.
It seems to be somewhat random in timing. On some reboots, the web server will remain accessible for almost 5 minutes. Other times, it'll only last a minute before becoming unresponsive. I attempted to check the debug log messages (connecting via USB and using M111 to enable debug messages for anything that seemed network- or web-server-related), and it seems that the last line written to debug prior to the web server no longer responding is this: "Released gcodeReply, free buffers=24"). The device appears to still be connected to the network, as the blue LED on the network board is lit blue and not flashing. The device remains responsive via USB and has no trouble outputting responses to M122, which (to me) doesn't seem to contain any obvious error messages. M115 indicates I'm running a v3 firmware, as anticipated.
What should I do to diagnose and fix this issue? I'm a full stack programmer by day with some hands-on experience with ESP8266 and derivatives, so feel free to make use of that if needed. Otherwise, I'd be happy to go through a return/exchange process if you think it's a hardware issue.
Please post the results of M122.
LazyMegaMan last edited by
I'm very happy to say that everything appears to be working correctly now! Though I'm not sure why it's suddenly working after consistently failing for hours just one day prior. I didn't so much as look at it, much less tweak anything. My best guess is that Chrome might have been using a cached version of the web UI files that was somehow only slightly incompatible with the version of the web server that the Duet 2 Wifi was running? I really don't know. Sorry to waste your time! I was able to use the web UI to fully configure all endstops, motors, run M303 for all three heater elements, and reset the board multiple times while configuring, all without so much as a hiccup, so I'm fairly confident that the issue is gone. However, if it does rear its ugly head again, I'll make a new post within this thread and include the results of the M122 then.
Thanks for your time!