Data Point on WiFi stability

Danal

Long print. Two DWC sessions open:

DWC running on Chrome on Windows 10. This stayed connected throughout (and after) the print. No issues of any kind. Continued to update, including the percentages in the tab, whether the tab was foreground or background. In fact, I used this to cancel the print at about hour six or seven, because a part came loose from the bed.
DWC running on Chrome on an Android Tablet. Tablet configured to never sleep, and plugged into power. DWC stayed connected for about four or five hours, then lost connection. Once it lost connection, it would not re-connect. Tried reload (circular arrow), close tab, manually enter IP address, completely close chrome and re-open. No connection. After print, power cycled Duet, and tablet now connects (no other changes on tablet, just pressed reload).

Unfortunately, I failed to get a debug log, and have since power cycled the printer. If this happens again, what would be most useful for me to gather?

Network is Google WiFi "Mesh" with six nodes spread across two buildings. Nearest node is about 20 feet from printer. Because my house has absolutely no CATx wiring, I am highly aware of WiFi reliability. My desktop's only connection to the outside world is via the mesh; there is literally not an Ethernet cable plugged into it. Network was rock solid throughout print.

T3P3Tony

@danal Thanks for the report. I am assuming that if the PC had disconnected it would reconnect properly? If that is the case it appears there is something different with the way that the android tablet and duet connect vs the PC and duet. Its also not likely solvable with the DWC reconnect things that @chrishamm has added (because it would not connect even after you closed and reopened the browser). Sounds to be something at the IP level (if you had a ping app on the tablet then maybe try pinging the duet IP after the next disconnect?).

Danal

@t3p3tony said in Data Point on WiFi stability:

@danal Thanks for the report. I am assuming that if the PC had disconnected it would reconnect properly? If that is the case it appears there is something different with the way that the android tablet and duet connect vs the PC and duet. Its also not likely solvable with the DWC reconnect things that @chrishamm has added (because it would not connect even after you closed and reopened the browser). Sounds to be something at the IP level (if you had a ping app on the tablet then maybe try pinging the duet IP after the next disconnect?).

Correct, during that incident, the Chrome/Win browser can connect/disconnect/connect at will.

I will give ping from the Android tablet a try.