CONSTANT AJAX disconnect errors

number40fan

I thought I had some good google fu, but I can't find anything. Mythological creature, maybe?

elmoret

I've seen 0.8.5 clones, but nothing for Duet Wifi/Ethernet yet.

patel

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?

Devid I try my iPhone it same
An AJAX error has been reported, So the current session has been terminated.
HTTP sessions : 1 of 8
Socket states:- 2 0 0 0 0 0 0 0
Responder states:HTTP(1) HTTP(0)…......

I connect to the duet to USB ( My desktop )
this is the summery .
USB CONNECT TO DUET

m122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (15 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: 96040
Recycled dynamic ram: 1568
Stack ram used: 4048 current, 5920 maximum
Never used ram: 6368
Last reset 02:34:02 ago, cause: power up
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: 0
[ERROR] 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 34.6, current 35.4, max 36.4
Supply voltage: min 12.0, current 12.0, max 12.2, 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-11-09 13:48:43
Slowest main loop (seconds): 0.224121; fastest: 0.000000
=== Move ===
MaxReps: 8, StepErrors: 0, FreeDm: 240, MinFreeDm 239, MaxWait: 5259148ms, Underruns: 0, 0
Scheduled moves: 9, completed moves: 9
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 ready with "M122" 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 33592
WiFi IP address 192.168.0.144
WiFi signal strength -42dBm
Reconnections 0
HTTP sessions: 2 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)

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

m122
SENDING:M122
=== Diagnostics ===
Used output buffers: 10 of 32 (15 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: 96040
Recycled dynamic ram: 1568
Stack ram used: 4048 current, 5920 maximum
Never used ram: 6368
Last reset 02:36:37 ago, cause: power up
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: 0
[ERROR] 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 35.3, current 35.5, max 35.9
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: standstill
Driver 4: standstill
Date/time: 2017-11-09 13:51:18
Slowest main loop (seconds): 0.079102; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 10, completed moves: 10
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 ready with "M122" 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 33592
WiFi IP address 192.168.0.144
WiFi signal strength -43dBm
Reconnections 0
HTTP sessions: 2 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)

Jarery

12:35:24 PMConnection established!
10:51:05 AMDisconnected.
9:46:14 AMConnection established!
9:46:14 AMPage Load complete!

Went for lunch, came back, and disconnected….it did reconnect with connect button but it had bene disco'd for over 90 min which usually is long enough for it to reconnect

Firmware 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

edit: Made a change to config, rebooted printer....and the below is the printer sitting idle

1:14:26 PMDisconnected.
12:54:22 PMConnection established!
12:54:17 PMDisconnected.
12:38:44 PMConnection established!
12:38:44 PMPage Load complete!

Jarery

My system has disconnected again, 8 min after disconnect I can ping it via terminal fine and it still shows as connected in my router page. Connected via connect button.

Will test again when i get one of the locked out disconnects.

dc42

Jarery, thanks for your report. What make and model of router are you using?

Patel, thanks for your reports too. have you tried with DuetWiFiServer 1.20beta7-nosleep yet? Also, what make and model of router are you using?

Jarery

I have 2, an Asus RT-AC3100 as my main and located 3m away, and an Asus RT-AC66U used as a access point located about 12m away. I get similar results with and without the AP router turned on.

Running latest Merlin Firmware, 380.68_4

Edit:
last disconnect at 2:56, its now 4:03 and connect button will not reconnect. Will take a reboot ~~or reset of wifi module~~. Cannot ping via terminal

edit 2: wifi reset (M552 S-1, G4 S1, M552 S1) showed a reconnect on the paneldue screen but could not connect web browser, a power cycle to the printer did work.

KeeganB

I have updated to DuetWiFiServer 1.20beta7-nosleep and am testing it now.

Curiously, I am not sure that they "print simulation" is working. Its been going for 33mins on a print file that should have taken less than 10mins.

I gave up on the print simulation issue. I guess Ill sort that later.

I have been connected since 8:42pm.
I printed a 14 min calibration cube. Success.
Started a 6.5 hour print at 10:45pm

Fingers crossed for the morning.

dc42

Keegan, which main firmware version are you running? Simulation mode was broken in 1.20b2 and b3 but fixed in b4.

KeeganB

@dc42:

Keegan, which main firmware version are you running? Simulation mode was broken in 1.20b2 and b3 but fixed in b4.

You know what? That is it! I am running 1.20beta2.

I am still connected this morning. It has been over 10hrs now. I am starting the third print now.

JohnOCFII

@Jarery:

I have 2, an Asus RT-AC3100 as my main and located 3m away, and an Asus RT-AC66U used as a access point located about 12m away. I get similar results with and without the AP router turned on.

Running latest Merlin Firmware, 380.68_4.

Just as a related data point – I have two routers also running Asus Merlin 380.68_4. Once is an RT-N66R (https://www.asus.com/us/Networking/RTN66R/) running just as an AP, and the main router/AP is an RT-AC68P (https://www.asus.com/us/Networking/RTAC68P/).

The DuetWiFi usually connects to the RT-N66R.

I've stayed connected for up to 4 hours. I've not left the printer on longer than that yet.

I've had occasional disconnects, but not enough to bother me yet. If I did longer prints on this printer, it might crop up as an issue more often. If my printer is typically on for 3 hours, I might have one disconnect every third session.

I'm running 1.19.2.

John

KeeganB

John, when you get the disconnect, are you locked out or can you just click connect to get back?

dc42

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.

Jarery

M997 S0
Error: M997: Firmware binary "DuetWiFiFirmware.bin" is not valid for this electronics

Firmware 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.

dc42

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.

JohnOCFII

@KeeganB:

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.

JohnOCFII

@KeeganB:

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

JohnOCFII

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…

dc42

John, have you worked through https://www.duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors ?

JohnOCFII

@JohnOCFII:

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.