CONSTANT AJAX disconnect errors
-
John, when you get the disconnect, are you locked out or can you just click connect to get back?
-
Hi all,
Here are two new builds of DuetWiFiServer:
https://www.dropbox.com/s/5cp3w947vonp36s/DuetWiFiServer-1.20b8.bin?dl=0
https://www.dropbox.com/s/8k83pw56gefezqm/DuetWiFiServer-1.20b8-nosleep.bin?dl=0
Those of you having issues maintaining a wifi connection, please try the first one (needs DuetWiFiFirmware 1.20b4 or 1.20b6). If that doesn't improve things, try the second one. The recommended way to install these is to download the one you want, rename it to DuetWiFiServer.bin, then upload it through the Settings->General page of DWC.
If for any reason you can't reconnect after installing it, please try re-installing it by sending M997 S2 via USB or PanelDue. I had to do this once on one of my test systems.
Please report your findings here. As a bonus, access point mode is working in this build.
-
M997 S0
Error: M997: Firmware binary "DuetWiFiFirmware.bin" is not valid for this electronicsFirmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20beta6 (2017-11-03)
WiFi Server Version: 1.20beta7-nosle
Web Interface Version: 1.19.3- Install worked via panel due.
-
Jarery, I'm sorry, I should have said rename it to DuetWiFiServer.bin. I have corrected the text. You are still running beta7, so you'll need to do it again.
-
John, when you get the disconnect, are you locked out or can you just click connect to get back?
I've seen both types of disconnects, but only the last disconnect was one where I had to power cycle the printer. It was also the only disconnect I've seen since upgrading to 1.19+. The previous disconnects (same timeout AJAX message) I was just able to hit reconnect from the DWC web page.
-
John, when you get the disconnect, are you locked out or can you just click connect to get back?
Of course just after posting that, I had a disconnect.
This occurred after the printer had been running for 2.5 hours. I had done one 1 hour print during this time. I was able to reconnect just by pressing the Connect button in DWC.Perhaps it is time to try that newer firmware, but my disconnects don't seem to happen near as frequently as yours.
John
-
Here's another thought/question? For those (like me) that only have very sporadic disconnections, could it be a something that DWC is watching for, and disconnects if the web page senses no activity for some period of time? So - if you clicked a button every 3 minutes, would it stay connected?
Just a thought…
-
John, have you worked through https://www.duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors ?
-
Here's another thought/question? For those (like me) that only have very sporadic disconnections, could it be a something that DWC is watching for, and disconnects if the web page senses no activity for some period of time? So - if you clicked a button every 3 minutes, would it stay connected?
Just a thought…
I can rule that out.
I had just entered M122, and about 6 seconds later it disconnected. That time, I could not ping the IP of the DuetWifi, and the router had lost it's entry for the printer. I restarted the printer.
-
John, have you worked through https://www.duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors ?
Yes, I have worked through those steps. Again, for me, the disconnects are slightly above an amusement, not yet reaching to the level of annoyance, but if I can help troubleshoot, I will try.
When reading through the list just now, I see that my Maximum number of AJAX retries was set to 1. I thought I had increased that, but perhaps that was on 1.18 and it didn't carry over – or maybe I never did set it. I just raised it to 3.
My RSSI is hovers around -58db to -60db.
Thanks,
John
Listed below is the M122 output as well as the rest of the console log from just before the last disconnect today:
[[language]] 1:44:07 PMDisconnected. 1:43:54 PMM122 === Diagnostics === Used output buffers: 3 of 32 (9 max) === Platform === RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0 Board ID: 08DAM-999TL-MQ4S8-6JKDJ-3SJ6K-16BVW Static ram used: 21176 Dynamic ram used: 96176 Recycled dynamic ram: 1432 Stack ram used: 1304 current, 9096 maximum Never used ram: 3192 Last reset 04:39:00 ago, cause: power up Last software reset reason: User, spinning module GCodes, available RAM 3192 bytes (slot 1) 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: 567.6ms MCU temperature: min 26.6, current 37.2, max 41.9 Supply voltage: min 11.4, current 12.3, max 12.5, 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-11-11 13:43:52 Slowest main loop (seconds): 0.569336; fastest: 0.000000 === Move === MaxReps: 4, StepErrors: 0, FreeDm: 240, MinFreeDm 120, MaxWait: 6821249ms, Underruns: 7, 0 Scheduled moves: 0, completed moves: 0 Bed compensation in use: none Bed probe heights: 0.054 -0.032 0.039 -0.088 0.008 === Heat === Bed heater = 0, chamber heater = -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.7 === 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.19.2 WiFi MAC address a0:20:a6:16:eb:66 WiFi Vcc 3.10, reset reason Turned on by main processor WiFi flash size 4194304, free heap 37944 WiFi IP address 192.168.62.118 WiFi signal strength -59dBm 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) 1:21:04 PMFile Models/Joelbot_Final_3_50p_KMR3.gcode print time was 1h 20m 12:02:29 PMCalibrated 6 factors using 10 points, deviation before 0.043 after 0.038 12:00:59 PMM32 Models/Joelbot_Final_3_50p_KMR3.gcode File Models/Joelbot_Final_3_50p_KMR3.gcode selected for printing 11:53:49 AMConnection established! 10:58:35 AMDisconnected. 10:00:47 AMFile Calibration Tests/xyzCalibration_cube_KMR3.gcode print time was 0h 33m 9:29:57 AMCalibrated 6 factors using 10 points, deviation before 0.166 after 0.040 9:28:13 AMM32 Calibration Tests/xyzCalibration_cube_KMR3.gcode File Calibration Tests/xyzCalibration_cube_KMR3.gcode selected for printing 9:24:43 AMG32 Calibrated 6 factors using 10 points, deviation before 0.043 after 0.042 9:19:52 AMG32 Calibrated 6 factors using 10 points, deviation before 0.376 after 0.040 9:18:30 AMConnection established! 9:18:29 AMPage Load complete! -
Looking back I think everyone with issues reported using routers with Merlins firmware? Perhaps anyone with Ajax disconnect issues who is running stock firmware on their router could confirm/deny.
Researching Asus routers that drop wireless clients, one thread had success turning off beamforming. In Merlins firmware there are two beamforming settings under "Professional" tab, Explicit and Universal.
Another thread reported wireless client issues dropping with both Merlins and stock firmware but problem cleared when they used DD-WRT firmware.Last night I turned off both beamforming options. My system has stayed connected overnight. I wont be able to run it through any prints till tomorrow, but perhaps some others with the issue capable of printing sooner could also test and let us know prior to that.
If this route fails I'll start messing with other router firmware. If anyone with issues is using dd-wrt firmware please let me know so i don't go down that path unnecessarily.
the router connected to the duet is running dd-wrt and yes i'm also having the Ajax disconnects since a couple of versions. it seems that after the Ajax disconnect the router and connection is still alive (or back) since i can ping and nmap shows the open port. however the when connecting via http i get an instant disconnect (see my post earlier in this thread)
-
I'm closing this thread because it is becoming impossible to navigate and different users are running different firmware versions, and starting a new one called "WiFi disconnect errors". If you are having wifi disconnection issues, please see that thread.
