AJAX timeout error during a print
-
Sorry, forgot to attach M122 logs after reconnect:
[[language]] M122 === Diagnostics === Used output buffers: 2 of 32 (8 max) === Platform === Memory usage: Program static ram used: 19284 Dynamic ram used: 83012 Recycled dynamic ram: 104 Current stack ram used: 2768 Maximum stack ram used: 3868 Never used ram: 24804 Last reset 01:58:35 ago, cause: power up Error status: 0 Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 31.6, current 33.3, max 36.7 Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0 Slowest main loop (seconds): 0.004883; fastest: 0.000000 === Move === MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0 === Heat === Bed heater = 0, chamber heater = -1 Heater 1 is on, I-accum = 0.0 === GCodes === Move available? no Stack pointer: 0 of 5 macro is idle http is ready with "M122" telnet is idle serial is idle aux is idle file is idle === Network === WiFiServer is running SPI underruns 0, overruns 0 === Webserver === HTTP sessions: 1 of 8 -
Hmm, just as I suspected. It looks like the WiFi module actually sends a non-empty response, but Firefox never receives and processes it. I'll look into the WiFi Server firmware later. Could you send me the Wireshark pcap file though?
-
Yes, as I said before. For some unknown for me reasons Duet sends valid response, but Firefox "receives" empty response. This is freeze/hangup bug. But also sometimes DWC shows me AJAX error and properly shows disconnected state if it receives invalid or empty response. I don't yet know why sometimes DWC is just freezes and why sometimes it shows proper AJAX error.
I still think about big pause between last valid request and next empty request. Can it be that AJAX request timeout is interpreted as empty response?
I will ask your email in PM to send logs.
-
Two hours without disconnects or connection freeze using latest 1.16 release firmware with @chrishamm web-server 1.03-ch firmware. Still looking at error logs, but it seems that this release is much stable.
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.16 (2016-11-08)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.13 -
Seems like DWC connection freeze issue fixed. Three hours yesterday and one hour today without any connection freezes. Thank you!
-
That's great, thanks for confirming that my latest improvements are working well!
-
Hi
I'm new here and building 3d printer in my free time.
I just set up a Duet v0.6 with the latest firmware and Web Control:
Firmware Name: RepRapFirmware for Duet-0.6-0.8.5
Firmware Version: 1.16 (2016-11-08)
Web Interface Version: 1.13After connecting to the duet via Web Control I'm getting the same error like appjaws after ~55 secconds while doing nothing:
Communication Error
An AJAX error has been reported, so the current session has been terminated.
Please check if your printer is still on and try to connect again.
Error reason: timeoutI reestablished the connection several times and got the error message every time after 55 secconds.
Thanks for every hint and help. Just tell me if you need further information.Edit: I'm using windows 7 pro and the error appears in Firefox and Chrome
-
I recommend you try to reset your TCP/IP stack once and restart your computer, see https://support.microsoft.com/en-us/kb/299357
-
Well that solved the problem fast and perfect. Thank you!
-
@dc42 : spam?
-
