CONSTANT AJAX disconnect errors
-
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
-
on any page if you check the Temp area top left you will see an Extras label click it and the MCU temp will appears which you can add to the Line chart if you wish.
-
My Board is mounted above my delta, so bed heat has no effect. The board temp is low to mid 30's when no fan is used. (calibrated just yesterday its about 3 degrees below the PT100 temp)
Mine also disconnects while idle. -
on any page if you check the Temp area top left you will see an Extras label click it and the MCU temp will appears which you can add to the Line chart if you wish.
perfect, thanks!
32.8C at idle after being powered on for several hours.
-
Over a couple different hour long prints the MCU temp stayed right around 34 C.
-
Please can those of you who are experiencing disconnect errors and are running DuetWiFiFirmware 1.20beta1 try changing the wifi firmware to version 1.20alpha1+1, which is available here: https://www.dropbox.com/s/u7vpp2wg4rlqs8l/DuetWiFiServer.bin?dl=1. Then let me know if you think it is better or worse.
-
DuetWiFiFirmware1.20alpha1+1
- Install 6:55
- idle
- Disconnect 7:55
The log showed slightly different times. The disconnect happened at 7:55 but doesn't show on the log till 8:05. It would not connect via connect button during that time.
2017-10-12 06:56:11 Event logging started
2017-10-12 08:05:21 WiFi reported error: Lost connection, auto reconnecting
2017-10-12 08:05:22 WiFi reported error: Auto reconnect succeededafter reconnect M122:
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.20alpha1+1
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 38352
WiFi IP address 192.168.2.32
WiFi signal strength -45dBm
Reconnections 1
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 2:
Left idle it disconnected again, after waiting 30 min Im able to reconnect. Log doesn't show that it ever knew it was disconnected: The 10:10 log is me reconnecting after disconnecting 30 min or so previous
2017-10-12 06:56:11 Event logging started
2017-10-12 08:05:21 WiFi reported error: Lost connection, auto reconnecting
2017-10-12 08:05:22 WiFi reported error: Auto reconnect succeeded
2017-10-12 08:58:13 HTTP client 192.168.2.49 login succeeded
2017-10-12 10:10:20 HTTP client 192.168.2.49 login succeeded -
First print, disconnected while printing the skirt
-
Thanks for your feedback. Which country are you in?
-
Canada, Vancouver BC specificaly,
-
Ill be away from the printer for about a week, but will updated to that new version you shared David as soon as I return.
-
David, I juste realized that my WiFi signal strength is really low: -68dBm! I think I'm lucky it's working so well, despite such poor signal!
I think I will order the new ESP module, with antenna.
-
Updated to alpha1+1 - pretty much the same story for me unfortunately.
The following log is right after a disconnect when idle. I restarted the wifi module with M552 on device.[[language]] === Diagnostics === Used output buffers: 3 of 32 (17 max) === Platform === RepRapFirmware for Duet WiFi version 1.20beta1 running on Duet WiFi 1.0 Board ID: 08DAM-9K9K2-NGNSN-6JKD0-3SJ6T-15UBM Static ram used: 15128 Dynamic ram used: 96048 Recycled dynamic ram: 3512 Stack ram used: 1352 current, 4880 maximum Never used ram: 11504 Last reset 00:06:35 ago, cause: reset button or watchdog Last software reset reason: User, spinning module GCodes, available RAM 11504 bytes (slot 3) Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 41.1, current 41.6, max 42.8 Supply voltage: min 24.1, current 24.2, max 24.6, under voltage events: 0, over voltage events: 0 Driver 0: stalled standstill Driver 1: stalled standstill Driver 2: stalled standstill Driver 3: standstill Driver 4: standstill Date/time: 2017-10-15 15:01:57 Slowest main loop (seconds): 0.008844; fastest: 0.000033 === Move === MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 0, completed moves: 0 Bed compensation in use: none Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heater = 0, chamber heater = -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.3 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle 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+1 WiFi MAC address 5c:cf:7f:ef:4c:24 WiFi Vcc 3.11, reset reason Turned on by main processor WiFi flash size 4194304, free heap 35064 WiFi IP address 192.168.1.107 WiFi signal strength -58dBm 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) -
I've been leery of updating beyond 1.18.2 due to the frequent reports of WiFi issues. Today I decided to take the leap. The upgrade to 1.19.2 went well. Checking M122 my RSSI varied between -53 and -58 (the access point is one floor away in a wood framed house). I stayed connected from a web browser (Google Chrome from a Mac) for approximately 4 hours. During the middle of that 4 hour window was a single 90 minute print.
All seemed good. Not posting to gloat - but just wanted to add some data points. My access point is an Asus router running the third party Asus-Merlin firmware.
John
-
My access point is an Asus router running the third party Asus-Merlin firmware.
My setup is similar, albeit with the issues.
I have an Asus AC3100 as my main router about 3m away, and an AC66U about 12m away as an access point both with same firmware version, both Merlins. -
I experienced the same issue on a new Duet Wifi I received this week. I recalled that I had similar problems with some devices in the past with WMM mode enabled on the router. And indeed, disabling it fixed the issue. I have a router running OpenWrt based distribution, which allows to enable/disable WMM on per-SSID basis. I'm not sure about other routers, such as those ASUS devices mentioned here, but I think it should be at least possible to toggle WMM globally to try if it solves the problem.
-
As I use an OpenWRT-based router, I'll give this a try! Thanks.
