CONSTANT AJAX disconnect errors
-
Dare I say it?
24mins into a print and no disconnects, this is a record for me.
Ill be kicking myself if it was some network quirk on my network.
Hopefully it'll fix things for you. If it does, though, that begs the question of what is different about the WiFi board on the Duet Wifi (or it's firmware) in comparison to the other devices on your WiFi network that (I assume) continued to work well when the DuetWiFi was having issues.
I haven't yet upgraded past 1.18.2 yet. I used to have regular timeouts when I connected to the printer via it's DNS entry. Someone here suggested I connect to it via IP address, and it has been much more stable for me that way. I do still get the occasional disconnect, usually after a print has been completed and the system has been idle for 10 or more minutes.
John
-
Yeah, that will be the odd part. All my other devices have been perfectly fine. This includes several devices set up for remote access, via ports and etc, wireless printers, mobile devices, airplay stuff, etc…
My network hardware was getting pretty old, and I had been considering an upgrade so this was as good a time as any.
Print finished in 50 mins and I'm still connected. 2 hours of connection: 50mins print, and 70 mins idle. This is feeling pretty good.
-
Router believes its dropped and no longer shows it on the client list.
M552 shows it still connectedThanks, that's very useful information. It sounds like we can't trust the status call of the ESP8266 SDK to tell us whether the WiFi is still connected to the AP. This is going to be a problem for us because the SDK is closed source. We may need to ping the router regularly to determine whether the connection is still alive.
Please confirm that you are running version 1.19.2 of both DuetWiFiFirmware and DuetWiFiServer, by looking at the Settings/General tab in DWC.
-
I’m at work and not in front of my printer to screenshot the data, but I can confirm both are displaying 1.19.2
-
Feel bad piling on here, but same timeout issues in 1.19.2 for me. I've checked everything with M122. Slightly poor connection (-58db) but otherwise there is nothing outstanding I can find. My experience sounds very similar to Keegan's.
Some other details:
• Disconnects when not printing
• Always a timeout error
• Stays connected for about 30 seconds on average
• Uploading or sending commands often causes it to disconnect (CPU issue?)
• Cannot re-connect after (requires hard reset on board)I was already getting a bunch of disconnects in 1.18 but I chalked that up to signal strength, but its gotten worse.
Let me know if there is any way I can help. -
Jumping in here, I thought I was having problems with my Duet Ethernet after accidentally giving the ethernet cord a hard yank on moving it but I've been having problems since upgrading to 1.19.x with disconnects. It could still be a hardware problem but starving the CPU is just as likely.
Is it safe to presume that this problem could affect Duet Ethernet, too?
-
AHHHHHHHH!!!! Last night with the new router everything went great! Then, without changing anything on the network today, I just started a print and got the exact same behavior I was having….
pertinent M122 within minutes of the disconnect:
=== Move ===
MaxReps: 9, StepErrors: 0, FreeDm: 183, MinFreeDm 120, MaxWait: 344041ms, Underruns: 0, 0
Scheduled moves: 1069, completed moves: 1054
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19.2
WiFi MAC address 5c:cf:7f:ef:51:6f
WiFi Vcc 3.11, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39880
WiFi IP address 10.0.1.158
WiFi signal strength -39dBm
Reconnections 0
HTTP sessions: 1 of 8
Socket states: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
M552 via pronterface reports still connected
Pings to the IP address all fail. -
Thanks for that report. Net time it happens, please log on to your router and see whether it still shows the Duet as a connected client, and post the relevant bits of the M122 report again. The M122 says that the Duet is connected to the router, but I want to know whether the router agrees.
Are you using a static IP address, or DHCP?
-
Don't know if this will help you but whenever I can no longer access the web I can not ping the duet. I have been following this thread on and off and got the same (or very similar) issue. I have to verify what the router says.
-
I have reviewed the wifi server project and found an issue which could explain some of the problems you are seeing. I hope to have an updated DuetWiFiServer by tomorrow. It will be compatible with DuetWiFiFirmware 1.20beta1, so I suggest you upgrade to that (along with DuetWiFiServer 1.20alpha1) to provide a baseline.
-
That is very exciting David! (the update)
I just upgraded to a new router and I am still learning the GUI for it. The pings make me believe it was not connected to the router, but when going to the web GUI for the router it still showed the Duet on the connected clients list. I am inclined to not believe that though, and I may have been reading the page wrong. I will test that again next time I get a disconnect.
EDIT: I will try to get updated the the respective 1.20 beta/alpha firmwares tonight.
-
Loaded the new software
Firmware Version: 1.20beta1 (2017-10-02)
WiFi Server Version: 1.20alpha1
Web Interface Version: 1.19.3 (this dint show at first even with reboot)Ran well for 2 hours then disconnect, bottom line with reason not on the popup. Just the same AJAX error.
Unable to reconnect with connect button
M522 shows still connected to access point
Router shows disconnected
Unable to pingReset wifi with paneldue
M522 S0, pause, M522 S1
Connect button reconnects.M122 after reconnect then shows:
=== Move ===
MaxReps: 12, StepErrors: 0, FreeDm: 120, MinFreeDm 120, MaxWait: 230003ms, Underruns: 0, 0
Scheduled moves: 127412, completed moves: 127383http is idle in state(s) 0
telnet is idle in state(s) 0
file is doing "G1 X-67.592 Y56.469 E0.06335" in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.20alpha1
WiFi MAC address a0:20:a6:10:55:89
WiFi Vcc 3.16, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 38816
WiFi IP address 192.168.2.32
WiFi signal strength -46dBm
Reconnections 0
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)Edit: second disconnection, same print, reconnected after 2nd press of connect without having to cycle wifi module. Router showed it as not connect prior to using connect button.
After it reconnected, a M122 showed Reconnections 1 (first time I've ever seen reconnections not be 0) -
Thanks for that report. Net time it happens, please log on to your router and see whether it still shows the Duet as a connected client, and post the relevant bits of the M122 report again. The M122 says that the Duet is connected to the router, but I want to know whether the router agrees.
Are you using a static IP address, or DHCP?
This is a bit odd.
Currently I can't load DWC.
Pronterface shows connected to my network
Router shows connected but access type is "wired"Edit:
After running M552 S-1 and then M552 S1, the router now shows the Duet access type as "2.4G", as expected.I will keep an eye on this to see if it always changes to "wired" when the issues happen.
-
I just upgraded to 1.19.2 and I see the same issues as described in callil's comment above.
Does it help if I do Airtraces with my Mac? If yes, should I do this with 1.19.2 or should I upgrade to 1.20 beta?
The interesting thing I am seeing is that the duett is still associated to the AP but it is not answering to pings.
-
The next DuetWiFiServer release I do will be designed to work with 1.20beta1, or possibly a later 1.20 beta release.
-
I upgraded anyway, it took a little longer until I was unable to use the connection.
Fun thing is that I still see packet exchange between AP and duet:
RSSI: -40 dBm
TXPacketCount
176423
RXPacketCount
20352a little later:
TXPacketCount
176799
RXPacketCount
20744I can also still access station stats of the duet:
/cfg/system/root # wlctl -i wl0 sta_info 5C:CF:7F:37:8A:E3
[VER 4] STA 5C:CF:7F:37:8A:E3:
aid:5
rateset [ 1 2 5.5 6 9 11 12 18 24 36 48 54 ]
idle 1 seconds
in network 1857 seconds
state: AUTHENTICATED ASSOCIATED AUTHORIZED
flags 0x1e13a: WME PS N_CAP AMPDU AMSDU
HT caps 0x112c: SGI20 STBC-Rx
tx total pkts: 177054
tx total bytes: 47635359
tx ucast pkts: 23995
tx ucast bytes: 3712620
tx mcast/bcast pkts: 153059
tx mcast/bcast bytes: 43922739
tx failures: 1
rx data pkts: 21124
rx data bytes: 6136443
rx ucast pkts: 21112
rx ucast bytes: 6134771
rx mcast/bcast pkts: 12
rx mcast/bcast bytes: 1672
rate of last tx pkt: 72222 kbps - 19500 kbps
rate of last rx pkt: 6000 kbps
rx decrypt succeeds: 17064
rx decrypt failures: 88
tx data pkts retried: 0
per antenna rssi of last rx data frame: -47 -40 -41 0
per antenna average rssi of rx data frames: -46 -40 -40 0
per antenna noise floor: -94 -97 -96 0
tx total pkts sent: 23994
tx pkts retries: 2400
tx pkts retry exhausted: 1
tx FW total pkts sent: 64
tx FW pkts retries: 0
tx FW pkts retry exhausted: 0
rx total pkts retried: 2116Are you able to turn of Powersave on the esp? I see in the stats that PS flag is set, I have seen numerous errors with Powersave on WiFi
-
And this is tonight's error….
This was loading DWC about 1 min after a fresh power up of the printer:
Error reason: SyntaxError: JSON Parse error: Unterminated stringThen after hitting refresh for the web browser I got a different error that I wasn't able to copy before it disappeared, but I think it ended in "invalid digits."
after M552 S-1 and S1, this is the new error:
Error reason: SyntaxError: JSON Parse error: Expected '}'EDIT:
updated to all the latest firmwares from the edge GitHub, disconnects continue. That was expected, but just as an FYI for those following along.
-
Hey David,
Just checking in on the new firmware. I continue to have disconnects, but haven't done much or posted any further on them in the past few days.
-
I recall that some of you report that the WiFi is reliable when the printer is idle, but it disconnects a little while after printing starts, even though you are not using high microstepping. It occurs to me that this could be temperature-related. The WiFi module gets warm in normal use, and when the stepper drivers are generating heat as well it could be getting too hot to function properly. So please try the following:
- Monitor the CPU temperature in DWC until the point at which it disconnects. Is there a significant rise in temperature?
- Try cooling the Duet with a fan, if you don't already.
-
David,
Where in DWC can I see the board temp?
Thanks
