CONSTANT AJAX disconnect errors

MiR

I just upgraded to 1.19.2 and I see the same issues as described in callil's comment above.

Does it help if I do Airtraces with my Mac? If yes, should I do this with 1.19.2 or should I upgrade to 1.20 beta?

The interesting thing I am seeing is that the duett is still associated to the AP but it is not answering to pings.

dc42

The next DuetWiFiServer release I do will be designed to work with 1.20beta1, or possibly a later 1.20 beta release.

MiR

I upgraded anyway, it took a little longer until I was unable to use the connection.

Fun thing is that I still see packet exchange between AP and duet:

RSSI: -40 dBm
TXPacketCount
176423
RXPacketCount
20352

a little later:

TXPacketCount
176799
RXPacketCount
20744

I can also still access station stats of the duet:

/cfg/system/root # wlctl -i wl0 sta_info 5C:CF:7F:37:8A:E3
[VER 4] STA 5C:CF:7F:37:8A:E3:
aid:5
rateset [ 1 2 5.5 6 9 11 12 18 24 36 48 54 ]
idle 1 seconds
in network 1857 seconds
state: AUTHENTICATED ASSOCIATED AUTHORIZED
flags 0x1e13a: WME PS N_CAP AMPDU AMSDU
HT caps 0x112c: SGI20 STBC-Rx
tx total pkts: 177054
tx total bytes: 47635359
tx ucast pkts: 23995
tx ucast bytes: 3712620
tx mcast/bcast pkts: 153059
tx mcast/bcast bytes: 43922739
tx failures: 1
rx data pkts: 21124
rx data bytes: 6136443
rx ucast pkts: 21112
rx ucast bytes: 6134771
rx mcast/bcast pkts: 12
rx mcast/bcast bytes: 1672
rate of last tx pkt: 72222 kbps - 19500 kbps
rate of last rx pkt: 6000 kbps
rx decrypt succeeds: 17064
rx decrypt failures: 88
tx data pkts retried: 0
per antenna rssi of last rx data frame: -47 -40 -41 0
per antenna average rssi of rx data frames: -46 -40 -40 0
per antenna noise floor: -94 -97 -96 0
tx total pkts sent: 23994
tx pkts retries: 2400
tx pkts retry exhausted: 1
tx FW total pkts sent: 64
tx FW pkts retries: 0
tx FW pkts retry exhausted: 0
rx total pkts retried: 2116

Are you able to turn of Powersave on the esp? I see in the stats that PS flag is set, I have seen numerous errors with Powersave on WiFi

KeeganB

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 string

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

KeeganB

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.

dc42

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.

KeeganB

David,

Where in DWC can I see the board temp?

Thanks

Dougal1957

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.

Jarery

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.

KeeganB

@Dougal1957:

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.

KeeganB

Over a couple different hour long prints the MCU temp stayed right around 34 C.

dc42

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.

Jarery

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 succeeded

after 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

Jarery

First print, disconnected while printing the skirt

dc42

Thanks for your feedback. Which country are you in?

Jarery

Canada, Vancouver BC specificaly,

KeeganB

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.

fma

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.

callil

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)

JohnOCFII

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