CONSTANT AJAX disconnect errors

dc42 · 18 Sept 2017, 20:11

Have you tried increasing the number of retries in the DWC settings?

RGN01 · 18 Sept 2017, 20:16

Thanks, David.

I increased it to 5 earlier this evening and it seems to be OK so far on the desktop PC (about 90 minutes) - but the printer and PC are effectively idle.

It was set to one initially, is there a recommended larger setting, or is it trial and error?

I'll monitor this as I start adding and testing functionality to the printer - and report back.

dc42 · 18 Sept 2017, 20:31

1 is rather low, I think 3 would be a better default.

KeeganB · 19 Sept 2017, 13:11

At this point I can confidently say mine fits the pattern I mentioned earlier. Every print it starts fine and after a few minutes it disconnects. After probably 30 mins or so, it reconnects without issue and stays connected until I start the next new print.

David, I am considering downgrading to 1.19. Is there any reason not to?

Jarery · 19 Sept 2017, 15:25

Interesting yours reconnects. Mine never has, retries I've changed to 5, 10, to no effect.

KeeganB · 19 Sept 2017, 15:59

Jarery,

It may just be that the webpage is auto reloaded by the browser when I come back to the computer and pull it up.

RGN01 · 19 Sept 2017, 18:59

Thanks, David. I've dropped it to 3 and am testing that. SO far, so good!

snomon · 21 Sept 2017, 06:57

Hi guys, I'm having the same problem..Im trying to tell it to print something but it keeps giving me AJAX errors..ctrl+r a few times, i get in at some point. The print then keeps messing up and having me to reset it, not sure why

2:55:56 AMM122
=== Diagnostics ===
Used output buffers: 3 of 32 (15 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3S46N-12X7W
Static ram used: 21176
Dynamic ram used: 96104
Recycled dynamic ram: 1504
Stack ram used: 1304 current, 5920 maximum
Never used ram: 6368
Last reset 00:12:18 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 3136 bytes (slot 4)
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: 9.7ms
MCU temperature: min 51.1, current 53.7, max 55.9
Supply voltage: min 23.4, current 24.1, 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-09-21 02:55:52
Slowest main loop (seconds): 0.167053; fastest: 0.000034
=== Move ===
MaxReps: 6, StepErrors: 0, FreeDm: 240, MinFreeDm 234, MaxWait: 10780ms, Underruns: 0, 0
Scheduled moves: 5, completed moves: 5
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: 2 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 60:01:94:34:40:06
WiFi Vcc 3.14, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 36896
WiFi IP address 192.168.20.81
WiFi signal strength -57dBm
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)
2:55:49 AMConnection established!
2:55:24 AMDisconnected.
2:55:16 AMConnection established!
2:55:11 AMDisconnected.
2:55:03 AMConnection established!
2:55:01 AMDisconnected.
2:54:53 AMConnection established!
2:54:15 AMDisconnected.
2:52:10 AMConnection established!
2:46:32 AMDisconnected.
2:43:49 AMConnection established!
2:41:46 AMDisconnected.
2:39:46 AMConnection established!
2:38:11 AMDisconnected.
2:33:01 AMConnection established!
2:32:52 AMDisconnected.
2:32:40 AMCalibrated 6 factors using 13 points, deviation before 0.028 after 0.014
2:31:48 AMM32 Enclosure bracket v10(1).gcode
File Enclosure bracket v10(1).gcode selected for printing
2:30:54 AMM0 H1
File Enclosure bracket v10(0).gcode print time was 0h 9m
2:30:07 AMM25
Printing paused
2:25:29 AMConnection established!
2:24:55 AMDisconnected.
2:21:20 AMCalibrated 6 factors using 13 points, deviation before 0.091 after 0.024
2:20:42 AMM32 Enclosure bracket v10(0).gcode
File Enclosure bracket v10(0).gcode selected for printing
2:20:14 AMM0 H1
File Enclosure bracket v10(0).gcode print time was 0h 9m
2:19:53 AMM25
Printing paused
2:11:17 AMCalibrated 6 factors using 13 points, deviation before 0.071 after 0.014
2:10:35 AMM32 Enclosure bracket v10(0).gcode
File Enclosure bracket v10(0).gcode selected for printing
2:10:08 AMM122
=== Diagnostics ===
Used output buffers: 1 of 32 (14 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3S46N-12X7W
Static ram used: 21176
Dynamic ram used: 96200
Recycled dynamic ram: 1408
Stack ram used: 4048 current, 9104 maximum
Never used ram: 3184
Last reset 00:31:37 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 3136 bytes (slot 4)
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 54.7, current 55.3, max 55.6
Supply voltage: min 23.4, current 24.0, max 24.4, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-09-21 02:10:06
Slowest main loop (seconds): 0.176147; fastest: 0.000000
=== 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.245 0.225 0.020 -0.266 -0.374
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is ready with "M122" 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 60:01:94:34:40:06
WiFi Vcc 3.14, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 32424
WiFi IP address 192.168.20.81
WiFi signal strength -57dBm
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)
2:10:00 AMM0 H1
File Enclosure bracket v10.gcode print time was 0h 14m

mhackney · 21 Sept 2017, 13:36

My update…

I installed a wifi extender on my network to get a better signal to my Duet WiFi. I'm in the range of about -45dBm now, much better than the -79 I had before.

I've been on a business trip for 3 days but have some additional observations.

I've done 10ish prints before the trip and a few yesterday and did not have any disconnects during the print. The disconnects while idle still occur but they are farther between. The reason is
"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."

M122 shows:
MaxReps: 117, StepErrors: 0, FreeDm: 240, MinFreeDm 120, MaxWait: 3180388ms, Underruns: 0, 1
Scheduled moves: 1, completed moves: 1

The good news is, when this happens, I am able to Connect without restarting the Duet. I did read the new wiki on disconnects and found my AJAX retries was set to 1 so I've changed that to 3 and I'll keep watching.

bot · 21 Sept 2017, 15:38

Just a note, to anyone who is questioning whether their signal strength is sufficient, here is a great article I found:

https://support.metageek.com/hc/en-us/articles/201955754-Understanding-WiFi-Signal-Strength

Notice the chart at the end that gives general guidelines for required signal strength.

Jarery · 22 Sept 2017, 02:20

Currently I cannot connect at all anymore via web. Ive tried clearing cache, safari and chrome, rebooted the printer 3 times, cycled the wifi on/off.
Consol says it connects to my network and lists assigned ip, but unable to connect.

Edit : connected after about 20min of throwing things at it

Via USB my M122 network is :

Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19.2
WiFi MAC address 5c:cf:7f:a4:a1:64
WiFi Vcc 3.13, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39944
WiFi IP address 192.168.2.54
WiFi signal strength -33dBm
Reconnections 0
HTTP sessions: 0 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)

KeeganB · 23 Sept 2017, 03:18

Ok, after a few more nights of testing, I can confidently say the following:

1. It will stay connected forever at idle.
2. It seems to stay connected forever running G32 commands, and other manual control commands
3. Within minutes of starting a new print, it disconnects. EVERY SINGLE TIME. The same AJAX error every time.
4. After approximately 30-60 mins, it can be reconnected fine and will stay connected forever or until I start a new print.

I am still on 1.19.2, but may downgrade as this is really annoying.

dc42 · 23 Sept 2017, 07:14

Is the "Error reason:" given in the Ajax disconnect message Timeout, or something else?

KeeganB · 23 Sept 2017, 14:40

@dc42:

Is the "Error reason:" given in the Ajax disconnect message Timeout, or something else?

Sorry, I should have included that. Yes, I believe that is the error message. It’s the same message every time.

Jarery · 24 Sept 2017, 00:44

my Ajax error is the same, doesn't say what the cause is whether timeout or other.

Just states "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 "

I also disconnect every print but mine do not reconnect.

Edit:
I'm just commissioning a second DuetWifi delta, it has :
Firmware Version: 1.18.1 (2017-04-09)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.15a

And if I force a disconnect, the warning message has at the bottom "Reason: Timeout". This bottom line is not present at all in the 19.2 firmware disconnects issue. Cannot print yet so unable to tell if the issue is board related or wifi network.

Jarery · 24 Sept 2017, 23:01

Comissioned my 2nd duet wifi printer.
Board came with 1.18.1 firmware. No disconnects when printing. Although only did few prints, 10 min long or so.

Upgraded to 1.19.2, disconnected a coulee min into my first print. Ajax error message again has no line on the bottom stating reason.

So i have 2 new Duet wifi's, both disconnect from my Asus RT-AC3100 wifi network on every print.

The chances its a "bad board" or slim as it happens on both boards.
The chances its my network settings are low as Ive set everything to set channel, etc, and it works on 1.18 without disconnects.

There is something in 1.19 that just makes it appear to timeout

KeeganB · 25 Sept 2017, 01:35

I've never downgraded a Duet. Is it the same process as the update from 1.18 to 1.19.2 was, but in reverse?

dc42 · 25 Sept 2017, 07:17

I really wish there was some way I could reproduce the problem you are experiencing. AFAIK you are the only user who finds 1.19.2 less reliable than 1.18.

Downgrading to 1.18 you will need to do a simultaneous install of both DuetWiFiFirmware and DuetWiFiServer. If the board was shipped with 1.19 firmware originally then you will also need to install DuetWiFiFirmware.bin on the WiFi module.

Then you will need to follow the connection instructions for 1.18 and earlier.

lolorc · 25 Sept 2017, 07:55

i also find 1.19.2 less reliable than 1.8 with regard to the wireless/ajax issue. (sorry I'm not really helping with the debugging at the moment, house for sell, can't use my printer as often as I wish)

KeeganB · 25 Sept 2017, 15:15

Thanks David.

My board was shipped with 1.18.

I understand that network issues are near impossible to replicate. I wish there was more detailed log info or something I could get to you. I am able to force a reconnect via USB with M552 S-1/S1

The real frustration comes when doing calibration prints and etc. It disconnects so quickly I can't make any adjustments easily; baby stepping, extrusion, temp etc to do on-the-fly adjustments. That, and every time I want to start a new test print I have to go through the reconnect process every time.

I feel pretty confident my network is not the issue, but I have been toying with the idea of upgrading my router and other network equipment, so maybe I will do that now just in case. I've also considered taking on my my extra routers and setting up a clean dummy network to test.

David, is there any possible advantage in doing a "clean" install of 1.19.2. Meaning, could/should I format the SD card and do a completely clean install of everything, and then just paste in my config values as needed?