2.05.1 restart issues
-
Hi all,
I've recently updated from 2.02 to 2.05.1 on a Duet Wifi+Duex5. (See M122 below).
With that upgrade I've started having issues with the restart of the board. Very often when I do a stop (mechanical button, web, or panel) the board fails to boot it's user interfaces again. With that I mean that it comes back to load it's config.c (fans start at programmed rate) and it connects to wifi and is pingable but both the web gui and the 7" control panel stop receiving data/update and do not allow interaction with the device.
A quick power off/on doesn't help. I need a long power off (>20 seconds; to drain all caps I suppose) before it loads the UI's again.
Is that a known thing? Didn't find much on it.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3S4-6J1D8-3S86Q-1BRHF
Used output buffers: 3 of 24 (9 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93948 of which 116 recycled
Exception stack ram used: 320
Never used ram: 10976
Tasks: NETWORK(ready,744) HEAT(blocked,1176) DUEX(suspended,160) MAIN(running,3760) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:26:40 ago, cause: power up
Last software reset at 2020-06-10 21:52, reason: User, spinning module GCodes, available RAM 10640 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 17.7, current 22.0, max 22.3
Supply voltage: min 24.1, current 24.1, max 24.2, 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-11 09:00:26
Cache data hit count 4294967295
Slowest loop: 5.63ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
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 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 ===
Slowest loop: 25.92ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address cc:50:e3:15:1a:a4
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25672
WiFi IP address 192.168.5.95
WiFi signal strength -58dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@DennisF The only idea I have is that if you reboot a short time, maybe the Wifi WLAN sessions survive and addup until you don't have enough available sessions available to access with browser or PanelDue, so you could watch whether the "HTTP sessions 1 of 8" of M122 is going up when you experience the problem, or other problems in the WiFi section of M122. Another possibility are other internet connections to Duet which eat up the connections before you try to access with the browser (e.g. monitoring tools).
-
Hi @JoergS5, thanks for the reply.
I'm quite convinced the board reboots. Everything shuts down for a little bit; fans, heating, power, lights and also the IP stack as it's unpingable for a few seconds. Still this might be interesting to look at, need to figure out how to debug this thing while it dies...
-
@DennisF said in 2.05.1 restart issues:
I'm quite convinced the board reboots.
In that case you need to get a M122 report. If the web interface won't connect, try getting one over USB.
-
Obviously while the device is under USB debugging it refuses to show the behavior. I did find something odd in my config that I fixed. It might explain it but I'm not sure, I didn't change back to investigate. The old config had the line:
M587 SMYSSID PMYPASS"
Note the trailing ". That is not part of the password.
-
You should not have a M587 line in config.g. Remove it.
