New test firmware 1.19+4 and DuetWiFiServer 1.19+1
-
heres whats the serial connection reports after after a disconnect :
HTTP connection accepted
Found responder
Received 394 bytes
Sending reply, file = no
HTTP req, command words { GET /rr_status HTTP/1.1 }, parameters { type=3 }
New conn on socket 0 for local port 80
HTTP connection accepted
Found responder
Received 394 bytes
Sending reply, file = no
HTTP req, command words { GET /rr_status HTTP/1.1 }, parameters { type=3 }
New conn on socket 0 for local port 80
HTTP connection accepted
Found responder
Received 394 bytes
Sending reply, file = no
HTTP req, command words { GET /rr_status HTTP/1.1 }, parameters { type=3 }
Class Network spinning.
Class Network spinning.
Class Network spinning. -
According to that, the Duet appears to be behaving correctly. Can you get a Wireshark trace of the network traffic?
-
That is beyond my current level of network troubleshooting ability…
Once it disconnects, My web browser just repeatedly states it cannot connect, and the serial output is :
Class Network spinning.
Class Network spinning.
Class Network spinning.
Class Network spinning.
File DuetWifi_Wiring_Box.gcode print time was 5h 8m
Class Network spinning.
Class Network spinning.
Class Network spinning.
Class Network spinning. -
Sounds like the WiFi module has stopped responding. Sending M552 S-1 to reset it followed by M552 S1 to reconnect may get it working again, but that doesn't solve the problem.
-
Noticed that my PanelDue 7 flashes now every second or so. didnt do this before.. not sure whats causing it.
-
If you mean the backlight flashes on and off, or isn't a steady brightness, that's common if you try to power a 7" PanelDue from USB power only. A standard 500mA USB port can't provide enough current for the 7" display.
-
Sounds like the WiFi module has stopped responding. Sending M552 S-1 to reset it followed by M552 S1 to reconnect may get it working again, but that doesn't solve the problem.
This helps occasionally.
After initial power on, once connected it seems to remain connected until I print. I have yet to have a print go beyond 15-20 min and stay connected since the update from 1.18I have a macro that disconnects wifi and reactivates so after it loses connection I can attempt to reacquire. I have maybe 50-50 success rate. Many times, doing this still I am unable to require web browser. The only sure fire way is to power completely off, unplug serial if connected, and power back up. Even if i do reacquire connection mid print using this method (macro not reboot) it disconnects again after a period of time.
My router shows ip assigned the entire time.
Safari, chrome, etc, browser has no change.
-
If you run M122 after a print, what MaxReps value does it give?
-
Tested during a print last night.
Disconnected 5 or 6 times I believe. Near the end of the print after I reconnected (by using M552 S-1, M552 S1) it stated MaxReps 5.
After print completed when I connect and do a M122 it says MaxReps 4. -
That value is nice and low, so it looks like excessive step pulse rate isn't a factor.
