CONSTANT AJAX disconnect errors

dc42

I've put a temporary build (1.20beta6) of DuetWiFiServer.bin at https://www.dropbox.com/s/u7vpp2wg4rlqs8l/DuetWiFiServer.bin?dl=1. This version uses the latest SDK from Expressiv and includes a fix for the WPA2 KRACK vulnerability. It may or may not help with reliability of the WiFi connection. I've heard that the KRACK vulnerability fix may be incompatible with some routers.

I am doing further work on DuetWiFiServer to make additional diagnostics available.

KeeganB

David, does that build include the correction of the sleep mode?

Jarery

Did the "disable sleep" make it in ?

dc42

No, I didn't want to try more than one thing at a time.

patel

@dc42:

I've put a temporary build (1.20beta6) of DuetWiFiServer.bin at https://www.dropbox.com/s/u7vpp2wg4rlqs8l/DuetWiFiServer.bin?dl=1. This version uses the latest SDK from Expressiv and includes a fix for the WPA2 KRACK vulnerability. It may or may not help with reliability of the WiFi connection. I've heard that the KRACK vulnerability fix may be incompatible with some routers.

I am doing further work on DuetWiFiServer to make additional diagnostics available.

1:52:39 PM
Can't rename file or directory 0:/sys/DuetWiFiServer(1).bin to /sys/DuetWiFiServer.bin

File gg_PLA_OPTIMAL.gcode selected for printing
FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.19.2 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-09-01
1:52:39 PM
M32 gg_PLA_OPTIMAL.gcode
Can't rename file or directory 0:/sys/DuetWiFiServer(1).bin to /sys/DuetWiFiServer.bin

File gg_PLA_OPTIMAL.gcode selected for printing
FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.19.2 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-09-01
1:51:31 PM
M997 S1
Can't rename file or directory 0:/sys/DuetWiFiServer(1).bin to /sys/DuetWiFiServer.bin
WiFi Server Version: 1.20beta6 done i getting error for rename

dc42

Try removing the (1) from the filename before you upload it. If that doesn't work, I suggest you go into the System Editor in DWC, rename or delete the existing DuetWiFiServer.bin, then upload again.

patel

@dc42:

Try removing the (1) from the filename before you upload it. If that doesn't work, I suggest you go into the System Editor in DWC, rename or delete the existing DuetWiFiServer.bin, then upload again.

Thanks for replay I did and work let see i connect my laptop to duet wifi any error commigm after update.
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (17 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6J9D6-3SN6L-12ZHY
Static ram used: 21176
Dynamic ram used: 96072
Recycled dynamic ram: 1536
Stack ram used: 1304 current, 9096 maximum
Never used ram: 3192
Last reset 01:48:41 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 7408 bytes (slot 4)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 8
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.4, current 32.7, max 33.4
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-11-07 14:10:11
Slowest main loop (seconds): 0.077148; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 15, completed moves: 15
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.0
=== 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.20beta6
WiFi MAC address 2c:3a:e8:0a:f1:18
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 33368
WiFi IP address 192.168.0.144
WiFi signal strength -42dBm
Reconnections 0
HTTP sessions: 2 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)

patel

@patel:

@dc42:

Try removing the (1) from the filename before you upload it. If that doesn't work, I suggest you go into the System Editor in DWC, rename or delete the existing DuetWiFiServer.bin, then upload again.

Thanks for replay I did and work let see i connect my laptop to duet wifi any error commigm after update.
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (17 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6J9D6-3SN6L-12ZHY
Static ram used: 21176
Dynamic ram used: 96072
Recycled dynamic ram: 1536
Stack ram used: 1304 current, 9096 maximum
Never used ram: 3192
Last reset 01:48:41 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 7408 bytes (slot 4)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 8
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.4, current 32.7, max 33.4
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-11-07 14:10:11
Slowest main loop (seconds): 0.077148; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 15, completed moves: 15
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.0
=== 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.20beta6
WiFi MAC address 2c:3a:e8:0a:f1:18
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 33368
WiFi IP address 192.168.0.144
WiFi signal strength -42dBm
Reconnections 0
HTTP sessions: 2 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:21:28 PM
Disconnected. AJAX error
2:23:29 PM
=== Diagnostics ===
Used output buffers: 3 of 32 (17 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6J9D6-3SN6L-12ZHY
Static ram used: 21176
Dynamic ram used: 96072
Recycled dynamic ram: 1536
Stack ram used: 1304 current, 9096 maximum
Never used ram: 3192
Last reset 01:48:41 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 7408 bytes (slot 4)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 8
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.4, current 32.7, max 33.4
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-11-07 14:10:11
Slowest main loop (seconds): 0.077148; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 15, completed moves: 15
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.0
=== 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.20beta6
WiFi MAC address 2c:3a:e8:0a:f1:18
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 33368
WiFi IP address 192.168.0.114
WiFi signal strength -42dBm
Reconnections 0
HTTP sessions: 2 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)

dc42

Were you able to reconnect by pressing the Connect button in DWC, or not?

patel

@dc42:

Were you able to reconnect by pressing the Connect button in DWC, or not?

I try both way refresh F5 and connect button
Run time 20min to 30min max and get Ajax error

dc42

Patel, a few more questions:

1. Have you worked through https://duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors ?

2. In the AJAX error message box, is the Error Reason always given as "timeout"?

3. After a disconnection occurs, are you able to ping the Duet?

dc42

KeeganB, I recall that you are getting disconnections more frequently when your printer is printing than at other times. Please can you try simulating some prints (this is a right-click option in DWC1.19.3) and see if connections are lost more frequently during simulations than when the printer is idle.

Patel, if you too have found that the connection is much less reliable when printing, please try this too.

KeeganB

@dc42:

KeeganB, I recall that you are getting disconnections more frequently when your printer is printing than at other times. Please can you try simulating some prints (this is a right-click option in DWC1.19.3) and see if connections are lost more frequently during simulations than when the printer is idle.

Patel, if you too have found that the connection is much less reliable when printing, please try this too.

Hey David,

I can test that. I need to email you, Roland, and Tony with some of my findings over the past few days. Ill try to type that up today.

Thanks

patel

@dc42:

Patel, a few more questions:

1. Have you worked through https://duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors ?

2. In the AJAX error message box, is the Error Reason always given as "timeout"?

3. After a disconnection occurs, are you able to ping the Duet?

Error timeout. And I follow your wiki page also.
After error some time connect right way and some time I need press reset button get back

I am tried to do this thing can you accept return.

dc42

I've noticed a difference between the M122 reports from KeeganB and patel when the wifi connection has been lost and DWC won't reconnect. KeeganB's report from some time ago had this:

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)

Patel's more recent reports have this:

HTTP sessions: 2 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)

Patel's reports are intriguing, because HTTP state 1 should time out after 2 seconds if no data is received.

Patel, were M122 reports obtained by sending M122 from the USB port when DWC has disconnected? Or did you reconnect DWC and send M122 from DWC?

Also, did you have just one device (e.g. PC) connected to the Duet; or did you have a second device (e.g. smartphone, tablet or another PC) connected too, or a second browser tab?

dc42

1. I have put a build of DuetWiFiServer with sleep disabled (version 1.20beta7-nosleep) at https://www.dropbox.com/s/59s7vfkrf50fe0v/DuetWiFiServer-1.20beta7-nosleep.bin?dl=0. Please try it. The previous build (1.20beta6) is at https://www.dropbox.com/s/djs0p4beitjs60t/DuetWiFiServer-1.20beta6.bin?dl=0.

2. Patel, what make and model of wifi router are you connecting the Duet to?

KeeganB

@dc42:

1. I have put a build of DuetWiFiServer with sleep disabled (version 1.20beta7-nosleep) at https://www.dropbox.com/s/59s7vfkrf50fe0v/DuetWiFiServer-1.20beta7-nosleep.bin?dl=0. Please try it. The previous build (1.20beta6) is at https://www.dropbox.com/s/djs0p4beitjs60t/DuetWiFiServer-1.20beta6.bin?dl=0.

2. Patel, what make and model of wifi router are you connecting the Duet to?

David, I will try the beta7 build tonight.

Email sent.

Thanks

cbusillo

DC. It happens on my Ethernet Duet at idle and while printing. Tried different browsers and computers. Also WiFi and Ethernet connections. I saw you were concentrating on the WiFi server, so I wanted to let you know that might be the wrong direction! Love everything else about the board. Keep up the good work.

Oh you might want to put a warning out that Chinese Duets are out.

Dougal1957

David

Just tried to install B7-nosleep and sorry to say it failed (FW Loads fine) when trying to diagnose this I sent the usual M552 S0 but got no response back send M552 S1 and get an error saying to stop the wifi before starting it and M552 reposrts WiFi starting (Reloaded the Server fw 3 times with the same results including copying direct to the SD Card and renaming etc).

so decided to try B6 which worked and loaded the Wifi almost instantly.

Hope this helps (Not that I was suffering the Disconnects anyway)

Doug

abecker

Any tips on what I should try. I have noticed I will get the Ajax Disconnect error at random times in a print. Sometimes it is when it is probing with the G32 command, and other times it can be actually printing. Mine will completely disconnect from the network and can't ping it or anything. I will have to wait for the print to finish and then turn it off and back on and it connects back immediately. The printer is in the same room as the router.