WiFi disconnect errors

MiR · 20 Nov 2017, 07:14

I have good WiFi connectivity, RSSI -43dBm, Broadcom chipset based router. Have upgraded to latest firmware and beta9 server, could do two small prints of 30 minutes without issue, this morning I could not reconnect. Unfortunately i accidentally turned off the pc i used for usb logging, will retry tonight.

tomasf · 20 Nov 2017, 11:18

@k3lag:

I think at least one other person has mentioned that they use an Apple router. It would be interesting to see if there is any correlation between what routers people use and the disconnects.

I've had various problems with Duets and WiFi for a long time, and I'm also using an AirPort Extreme. It mostly works fine nowadays, but I'm still having problems from time to time. I recently updated to 1.20b, but it's too early to determine whether that has made a difference.

zlowred · 20 Nov 2017, 20:29

I've replaced my Apple router with Google WiFi today, and it still disconnects, so I don't think it is related to particular router model.

k3lag · 20 Nov 2017, 23:23

@zlowred:

I've replaced my Apple router with Google WiFi today, and it still disconnects, so I don't think it is related to particular router model.

If it is router related I wouldn't necessarily expect it be limited to a single brand but it could be related to a particular WiFi chipset or chipset family. It's hard to say without a fair bit of data.

KeeganB · 21 Nov 2017, 03:03

I haven't updated to the newer firmwares yet b/c this current setup has been working so well for me compared to really horrible results previously. BUT over the past few days I have started getting some disconnects an also getting locked out. It is still really good compared the past, with only probably 4-5 disconnects over the past 3 days. Here is my latest M122 immediately following a disconnect. I will upgrade the firmwares after this current print.

SENDING:M122
=== Diagnostics ===
Used output buffers: 2 of 32 (11 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta7 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6JTF0-3S86N-TLWZX
Static ram used: 15472
Dynamic ram used: 99192
Recycled dynamic ram: 4120
Stack ram used: 3992 current, 9144 maximum
Never used ram: 3144
Last reset 04:34:43 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7296 bytes (slot 3)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
[ERROR] Error status: 0

Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 42.8ms
MCU temperature: min 23.3, current 35.1, max 36.0
Supply voltage: min 12.2, current 12.6, max 12.9, under voltage events: 0, over voltage events: 0
Driver 0: ok
Driver 1: ok
Driver 2: open-load-B
Driver 3: ok
Driver 4: standstill
Date/time: 2017-11-20 22:00:32
Cache data hit count 4294967295
Slowest main loop (seconds): 0.080215; fastest: 0.000041
=== Move ===
MaxReps: 5, StepErrors: 0, FreeDm: 136, MinFreeDm 120, MaxWait: 2289273250ms, Underruns: 0, 0
Scheduled moves: 221848, completed moves: 221818
Bed compensation in use: none
Bed probe heights: -0.162 -0.151 -0.081 -0.058 -0.041
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 1
Stack records: 2 allocated, 0 in use
Movement lock held by file
http is idle in state(s) 0
telnet is idle in state(s) 0
file is doing "G1 X0.401 Y8.421 E0.0067" 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
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20b8-nosleep
WiFi MAC address 5c:cf:7f:ef:51:6f
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 29144
WiFi IP address 10.0.1.161
WiFi signal strength -37dBm, reconnections 4, sleep mode none
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)

dc42 · 21 Nov 2017, 10:05

It's interesting to see that you had 4 successful reconnections.

k3lag · 21 Nov 2017, 22:57

I've now been on my new WiFi network for 3 days and I have had no unexpected disconnects. I can reconnect immediately after any expected disconnects (laptop goes to sleep or I close my iPad) and the response is very quick.

ukflyer · 2 Dec 2017, 12:31

Been following this thread for a while now.

What is the current consensus for stable WiFi ?

I have updated to the latest stable firmware and server releases. My printer is 300mm from the WiFi router and there are no other WiFi networks available and yet the network connection is currently dropping within seconds of starting the printer up.

I have managed to start one print in the last 2 days before the WiFi connection dropped and that ran to completion so it can only be an issue with the WiFi module.

Really beginning to wish I had paid the extra for an ethernet electronics board

dc42 · 2 Dec 2017, 12:40

@ukflyer:

…
What is the current consensus for stable WiFi ?

I have updated to the latest stable firmware and server releases. My printer is 300mm from the WiFi router and there are no other WiFi networks available and yet the network connection is currently dropping within seconds of starting the printer up.

I have managed to start one print in the last 2 days before the WiFi connection dropped and that ran to completion so it can only be an issue with the WiFi module.

Please work through https://duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors first, in particular check the signal strength.

If the problem isn't signal strength, then the reports I have are that RepRapFirmware 1.20beta11 with DuetWiFiServer 1.20beta10 are more stable than the 1.19 versions in the stable release folder. So please try them. We have further work under way on DuetWiFiServer which we hope will resolve a remaining issue that some users experience.

ukflyer · 2 Dec 2017, 20:37

Okay I have the recommended Beta's installed -

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20beta11 (2017-11-28)
WiFi Server Version: 1.20b10
Web Interface Version: 1.19

And I have MacPronterface, connected via a USB cable, monitoring the WiFi debugging messages - fingers crossed.

dc42 · 2 Dec 2017, 21:29

Thanks, let us know how it goes.

ukflyer · 3 Dec 2017, 15:13

Suffered a disconnect during a print but print still running

Output of M122

m122
SENDING:M122
=== Diagnostics ===
Used output buffers: 2 of 32 (14 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0
Board ID: 08DGM-95BNL-MGPSN-6JKDJ-3S46N-1LWHW
Static ram used: 15488
Dynamic ram used: 97768
Recycled dynamiWiFi:
c ram: 1432
Stack ram used: 4328 current, 9212 maximum
NeWiFi: LINK
ver used ram: 7172
Last reset 18:45:25 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7400 bytes (slot 2)
Software reset code 0x0003, HFSR 0x00000000, CFWiFi: xmit: 0
SR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 1
[ERROR] Error status: 1

Free file entrieWiFi: recv: 0
s: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 347.2ms
MCU temperature: min 36.8, current 42.3, max 42.6
Supply voltaWiFi: fw: 0
ge: min 11.5, current 12.5, max 13.1, under voltage events: 1, over voltage events: 0
Driver 0: ok
Driver 1: ok
Driver 2: ok
DriverWiFi: drop: 0
3: standstill
Driver 4: standstill
Date/time: 2017-12-03 15:10:06
Cache data hit count 4294967295
Slowest main loop (secondsWiFi: chkerr: 0
0.349178; fastest: 0.000040
=== Move ===
MaxReps: 5, StepErrors: 0, FreeDm: 163, MinFreeDm 137, MaxWait: 50818999ms, Underruns: 11, 1
Scheduled moves: 157311, completed moves: 157281
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.0WiFi: lenerr: 0
00 0.000
=== Heat ===
Bed heater = 0, chamber hWiFi: memerr: 0
eater = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle WiFi: rterr: 0
in state(s) 0
file is doing "G1 X47.277 Y63.098 F9000" in state(s) 0
serial isWiFi: proterr: 0
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 sWiFi: opterr: 0
tate is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi: err: 0
WiFi firmware version 1.20b10
WiFi MAC address a0:20:a6:2f:bb:fe
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, freWiFi: cachehit: 0
e heap 28904
WiFi IP address 192.168.1.15
WiFi signal strength -27dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket statWiFi:
es: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
WiFi: ETHARP
WiFi: xmit: 4
WiFi: recv: 1637
WiFi: fw: 0
WiFi: drop: 1923
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 1923
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 24039
WiFi:
WiFi: IP
WiFi: xmit: 24104
WiFi: recv: 36990
WiFi: fw: 0
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 0
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 0
WiFi:
WiFi: IGMP
WiFi: xmit: 7
WiFi: recv: 39
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: proterr: 0
WiFi: rx_v1: 0
WiFi: rx_group: 0
WiFi: rx_genet 17033
WiFi: recv: 33948
WiFi: fw: 0
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 0
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 0

dc42 · 3 Dec 2017, 15:55

Are you able to reconnect?

ukflyer · 4 Dec 2017, 13:10

Not without issuing an M552 S-1 & M552 S1.

The logs are being taken from MacPronterface which is connected via USB

ukflyer · 4 Dec 2017, 13:25

If I had to guess I would say that it is almost as though the Web Server has shutdown rather than the WiFi connection.

Just started a print which is predicted to run for 2 hours plus so will keep an eye on it.

BMMal · 4 Dec 2017, 18:33

A M122 diagnostic report produced when WiFi was connected

=== Diagnostics ===
Used output buffers: 3 of 32 (17 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0 + DueX5
Board ID: 08D6M-91AST-L23S4-7JTD8-3S86K-1PX1K
Static ram used: 15488
Dynamic ram used: 98920
Recycled dynamic ram: 280
Stack ram used: 1368 current, 9220 maximum
Never used ram: 7164
Last reset 01:51:24 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 3032 bytes (slot 0)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 2
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 28.0, current 28.2, max 28.7
Supply voltage: min 24.3, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0
Driver 0: ok
Driver 1: ok
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Driver 5: standstill
Driver 6: ok
Driver 7: standstill
Driver 8: standstill
Driver 9: standstill
Expansion motor(s) stall indication: no
Date/time: 2017-12-04 11:26:10
Cache data hit count 4294967295
Slowest main loop (seconds): 0.119764; fastest: 0.000112
=== Move ===
MaxReps: 7, StepErrors: 194, FreeDm: 215, MinFreeDm 159, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 12230, completed moves: 12221
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 4 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
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 doing "G1 X163.249 Y162.84 E0.01646" 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 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20b10
WiFi MAC address a0:20:a6:16:e6:c6
WiFi Vcc 3.26, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27952
WiFi IP address 10.0.0.115
WiFi signal strength -29dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 0 2 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
[[language]]

```- The make and model of your WiFi router
**Asus RT AC56U**
- Does the problem occur mainly (or only) during printing, or does it occur equally frequently when the printer is idle?
**Both but more so when printing**
- When the problem occurs, are you able to reconnect by pressing the Connect button in DWC?
**Rarely. I have been issuing the wifi module reset command from Paneldue as a work around most of the time.**
- If you are unable to connect, are you still able to ping the IP address of the Duet WiFi?
**No. Timesout**
- Anything else that you think may be correlated with disconnections occurring
**It seems that mine is more likely to lose connection if I leave the focus on the Web Control tab in Chrome. I don't know if this is because fewer things are updated when Web Control is not the focus?**

KeeganB · 5 Dec 2017, 02:26

I get these all the time, but here is a recent longer log both the wifi debugging output and then the M122 from a few mins after the final disconnect.

[c]WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start…
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0
WiFi: state: 5 -> 2 (7c0)
WiFi: rm 0
WiFi: pm close 7
WiFi reported error: Lost connection, auto reconnecting
WiFi: reconnect
WiFi: state: 2 -> 0 (0)
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 3
WiFi: cnt
WiFi:
WiFi: connected with Virus 2.0, channel 4
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
WiFi: pm open,type:2 0[/c]

M122:

[c]>>> M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 3 of 32 (19 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6JTF0-3S86N-TLWZX
Static ram used: 15488
Dynamic ram used: 97952
Recycled dynamiWiFi:
c ram: 1248
Stack ram used: 4328 current, 9364 maximum
Never used ram: 7020
Last reset 142:06:05 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7296 bytes (slot 3)
Software reset code 0x0003, HFSR 0x00000000, CWiFi: LINK
FSR 0x00000000, ICSR 0x00400000, BFAR 0xe000edWiFi: xmit: 0
38, SP 0xffffffff
Error status: 1
[ERROR] Error status: 1

Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 35.2ms
MCU temperature: min 29.3, current 34.3, max 35.4
Supply voltaWiFi: recv: 0
ge: min 12.2, current 12.5, max 12.9, under voltage events: 4, over voltage evenWiFi: fw: 0
ts: 0
Driver 0: ok
Driver 1: ok
Driver 2: ok
Driver 3: ok
Driver 4: standstill
Date/time: 2017-12-04 21:25:50
Cache data hit count 4294967295
Slowest main loop (seconds): 0.115WiFi: drop: 0
319; fastest: 0.000041
=== Move ===
MaxReps: 5, StepErrors: 0, FreeDm: 127, MinFreeDm 120, MaxWait: 31071115ms, Underruns: 0, 0
Scheduled moves: 446029, completed moves: 445999
Bed compensation in use: none
Bed probe heights: -0.053 -0.047 0.022 0.040 -0.0WiFi: chkerr: 0
10
=== Heat ===
Bed heater = 0, chamber heater WiFi: lenerr: 0
= -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 1
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in staWiFi: memerr: 0
te(s) 0
file is doing "G1 X-4.645 Y-19.013 E0.14745 F1787.3" 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.
NetWiFi: rterr: 0
work state is running
WiFi moduWiFi: proterr: 0
le is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20b10
WiFi MAC address 5c:cf:7f:ef:51:6f
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 419430WiFi: opterr: 0
4, free heap 28520
WiFi IP address 10.0.1.161
WiFi signal stWiFi: err: 0
rength -46dBm, reconnections 31, sleep mode modem
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)
WiFi: cachehit: 0
WiFi:
WiFi: ETHARP
WiFi: xmit: 97
WiFi: recv: 420
WiFi: fw: 0
WiFi: drop: 7246
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 7246
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 48603
WiFi:
WiFi: IP
WiFi: xmit: 48776
WiFi: recv: 65007
WiFi: fw: 0
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 0
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 0
WiFi:
WiFi: IGMP
WiFi: xmit: 76
WiFi: recv: 168
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: proterr: 0
WiFi: rx_v1: 0
WiFi: rx_group: 0
WiFi: rx_ge: 21563
WiFi: recv: 61223
WiFi: fw: 0
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 0
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 0[/c]

dc42 · 5 Dec 2017, 08:11

Thanks. It looks like we have two issues, possibly related. We'll have a new build of DuetWiFiServer soon which may resolve one or both of them.

dc42 · 8 Dec 2017, 10:49

Hi all,

Please can anyone who is running main firmware ~~1.20beta10~~ 1.20beta11 and DuetWiFiServer 1.20beta10 and still experiencing WiFi disconnection problems try DuetWiFiServer 1.20b11, available here https://www.dropbox.com/s/ttoa6d9l9d0lrqe/DuetWiFiServer-1.20b11.bin?dl=1.

As before, if possible connect a PC running a host program via USB too and send M111 S1 P14 to enable WiFi module debugging.

darookee · 8 Dec 2017, 12:27

After installing DuetWifiServer 1.20b11 I could not connect to the Duet over Wifi and got these messages in Repetier-Host:

13:24:06.852 : WiFi: Fatal exception (0):
13:24:06.864 : WiFi: epc1=0x40100004, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
13:24:06.868 : WiFi: Fatal exception (0):
13:24:06.880 : WiFi: epc1=0x40100004, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
13:24:06.882 : WiFi: Fatal exception (0):
13:24:06.895 : WiFi: epc1=0x40100004, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

Reverting to DuetWifiServer 1.20b10 for now…

I'm running "Firmware Version 1.20beta11 (2017-11-28)", could this be the issue? I did realize too late that you said '...running 1.20beta10...'