Unsolved upgrading to 3.1.1. WiFi reset reason Unknown
-
Re: Software bundle 3.1.1 now available
Hello
After upgrading to 3.1.1 the web control disconnecting.
M122 i found "WiFi Vcc 3.38, reset reason Unknown"
Before the upgrade I had no any disconnecting iisues.
Please help.
Thank you.M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4SD-6J9FD-3S06Q-9MXZW
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93484 of which 520 recycled
Exception stack ram used: 264
Never used ram: 8824
Tasks: NETWORK(ready,488) HEAT(blocked,1456) DUEX(suspended,160) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:21 ago, cause: software
Last software reset at 2019-10-04 16:59, reason: User, spinning module GCodes, available RAM 10256 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 8
MCU temperature: min 33.1, current 34.7, max 36.1
Supply voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-06-19 16:06:45
Cache data hit count 135652214
Slowest loop: 5.28ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.6ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 40.39ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:3a:e8:0b:34:de
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 23544
WiFi IP address 192.168.1.7
WiFi signal strength -45dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
=== DueX ===
Read count 1, 0.73 reads/min
6/19/2020, 4:05:37 PM Connected to 192.168.1.7
- WiFi -
-
Please try reflashing the wifi module with the wifi server firmware.
Download this: https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWiFiServer-1.23.bin
Rename to
DuetWiFiServer.bin
and place in the /sys/ folder.Then send
M997 S1
in gcode console or via USB terminal.Also ensure that your DWC files have been updated in the /www folder.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/DuetWebControl-SD-3.1.1.zip
Download and manually extract to the /www/ folder on the SD card.
-
Hello
Thank you for your response.
I did all the advised steps but doesn't help.
The interface still disconnecting.
At the timing ping to the host still stable, no time outs. -
While we investigate this can you continue to provide M122 reports after the disconnections?
-
6/23/2020, 9:13:39 AM Connection established 6/23/2020, 9:13:27 AM Connection interrupted, attempting to reconnect... HTTP request timed out 6/23/2020, 9:13:26 AM Failed to get file list HTTP request timed out 6/23/2020, 9:13:18 AM Connection established 6/23/2020, 9:12:46 AM Connection interrupted, attempting to reconnect... HTTP request timed out 6/23/2020, 9:08:41 AM M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DDM-9FAM2-LW4SD-6J9FD-3S06Q-9MXZW Used output buffers: 3 of 24 (12 max) === RTOS === Static ram: 27980 Dynamic ram: 95072 of which 44 recycled Exception stack ram used: 312 Never used ram: 7664 Tasks: NETWORK(ready,268) HEAT(blocked,1168) DUEX(suspended,160) MAIN(running,1720) IDLE(ready,80) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 09:40:30 ago, cause: software Last software reset at 2020-06-22 23:28, reason: User, spinning module GCodes, available RAM 7724 bytes (slot 3) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 19.3, current 21.8, max 22.7 Supply voltage: min 12.1, current 12.2, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-06-23 09:08:35 Cache data hit count 4294967295 Slowest loop: 6.09ms; fastest: 0.13ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 2.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = 4 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 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 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 82.82ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address 2c:3a:e8:0b:34:de WiFi Vcc 3.38, reset reason Unknown WiFi flash size 4194304, free heap 22792 WiFi IP address 192.168.1.7 WiFi signal strength -46dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: no filament === DueX === Read count 1, 0.00 reads/min 6/23/2020, 9:08:34 AM Connection established 6/23/2020, 9:08:22 AM Connection interrupted, attempting to reconnect... HTTP request timed out 6/23/2020, 9:08:13 AM Connection established 6/23/2020, 9:07:45 AM Connection interrupted, attempting to reconnect... HTTP request timed out
-
What browser are you using? Can you try clearing the cache and trying a different browser?
-
I have had a similar issue, however when I try to ping the IP address the terminal is listing I get a timeout. I've checked the info on my router and it has assigned this same IP address to the duet so I have no idea why it is not locating it. I am on a mac and have tried the above recommendations, also to no avail. Any ideas on what else I could try to diagnose the problem further? Apologies if this is in fact a different issue or something obvious I have missed.
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-05-19b2
USB is ready with "M122" in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 1179.23ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 0 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address f4:cf:a2:5b:0e:d9 WiFi Vcc 3.38, reset reason Unknown WiFi flash size 4194304, free heap 25944 WiFi IP address 192.168.0.32 WiFi signal strength -66dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 ok
-
@Phaedrux Im using Chrome and Firefox - same disconnections. I'm trying to use MS Edge - less disconnections, very rarely.
-
I don't think the "wifi reset reason unknown" is anything to worry about, because I am getting the same message from the RRF 3.2 beta build, and the connection to the machine is working reliably. But I will investigate the reason for it.
@04mike40, your WiFi signal strength reported by M122 -66dBm, which is quite low.
-
I've found the reason for the "reset reason unknown" message, and it's nothing to worry about. Somehow one of the lines in the reset reason table got deleted. I will fix this in release 3.2 and also in 3.1.2.
-
This post is deleted! -
@dc42 Hi. Ok, thank you for your help!