Frozen + Restart + WiFi Errors
Today, after a 1h print, I removed the part and heated the hotend to start a new print, and when the temperature was around 180ºC (of 210º), the screen just froze (no more temperature updates) and the web didn't respond, a few seconds later, the leds and the thermostatically controlled fan went off and on (I'm controlling the leds using the fan2 output, connected to a Mosfet), and the printer just restarted.
In the console at the paneldue, I saw this:
And the M122 was this:
[[language]] M122 === Diagnostics === Used output buffers: 3 of 32 (9 max) === Platform === RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0 Board ID: 08DDM-9FAM2-LW4SD-6JTD6-XXXX-XXXXX Static ram used: 15448 Dynamic ram used: 98992 Recycled dynamic ram: 248 Stack ram used: 1392 current, 4504 maximum Never used ram: 11880 Last reset 00:02:26 ago, cause: software Last software reset at 2018-01-25 00:44, reason: Stuck in spin loop, spinning module Network, available RAM 7944 bytes (slot 0) Software reset code 0x4041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f80f, BFAR 0xe000ed38, SP 0x2001f9ac Stack: 0042c995 00008096 0043c277 00008096 ffffffe9 00001000 00081111 40080000 00008096 20002d8c 00437273 0043ab8c 41070200 00000000 00000000 00000009 00000009 3e178897 3e1cd04f 41200000 bddf53fe 3e3a38a1 3e6393d6 43700000 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 52.3, current 53.2, max 55.3 Supply voltage: min 23.9, current 24.1, max 24.5, under voltage events: 0, over voltage events: 0 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 Date/time: 2018-01-25 00:47:28 Cache data hit count 326334318 Slowest main loop (seconds): 0.014180; fastest: 0.000042 === 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 heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.5 === 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 state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.20 WiFi MAC address 5c:cf:7f:XX:XX:XX WiFi Vcc 3.44, reset reason Turned on by main processor WiFi flash size 4194304, free heap 16880 WiFi IP address 192.168.1.120 WiFi signal strength -58dBm, reconnections 0, sleep mode modem 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)
This is the second time I had this issue, though last time I just saw the "Error cannot read file" in the screen and forgot to get the diagnostic.
Regarding the wifi error shown in the screen, most of the times when I turn on the printer, the wifi just fails (as shown in the screen) due to "bad password", then I enter "M552 S1" (without changing the password) and works again perfectly until next reboot. This is happening since I updated to 1.20, and is happening even though I've reinstalled both wifi and board firmware, but doesn't always fails (it fails around 70% of the boots).
I still have the printer on, in case anything is needed for diagnostic, though if I need to connect the laptop, I won't be able until I come back home… Oh! and this time, debug is off (M111 S0 at the beginning of my config.g file).
What can be happening?
The "bad password" error suggests a fault in the wifi module, or that the flash memory where the password is stored isn't returning a consistent result. Re-sending the M587 command to set up the SSID and password may fix it. If it doesn't then the WiFi module will need to be replaced.
The "Cannot read file" suggests a problem with the SD card or the SD card interface. The software reset data also indicates that the firmware got stuck waiting for a SD command to complete. Please try a new SD card. Also try firmware 1.21RC1 when I release it, which may be later today.
Thanks for answering.
I will then forget the wifi with M588 and add it again with M587, and will try a new SD card.
Interestingly, both times that I got that error, the printer was not printing.
I will try the RC once is available and report back
I've found something interesting while doing the procedure, initially I thought it was a bug, but it's in Pronterface and not in duet
- I've deleted all the networks (M588 S"*"), verifying with M587 that no network was stored
- Then I setup the network again:
M587 S"WLAN_Oker" P"SuperPassword" (Please note the capitals and regular letters)
- Printrun answered:
SENDING:M587 S"WLAN_OKER" P"SUPERPASSWORD" (Please note all letters are now in capitals)
- Wifi is not working, as nor SSID nor password are the right ones… I had to change my settings, then upload a gcode file with the right ones, and execute the file from the paneldue, and go back to the original wifi settings...
Regarding the original issue with wireless, I still have it, wifi module reports wrong password when booting, and after M552 S1 is issued through paneldue, wifi comes to live again...
I'm gonna test the RC firmware to see if it works better...
Testing wifi so far…
Restarted duet 10 times, 5 worked, 5 failed (50% of the time...).
Interestingly, 1 fails, 1 works, always doing more or less the same (turn on, wait until connects or fails, wait ~20s, turn off, wait ~10s, turn on...). At least, works more often than before...
I moved back to 1.19.2 (both, firmware and wifi), and repeated the testing 6 times: 100% connection success
It shows "Connected", then "Wifi Module Started" (this is not shown in 1.20), then "Wifi Module connected to Access point" (ping start answering), then 5 seconds after this, ping start to fail, and screen shows "Error retrieving wifi status message" and then connects again with "Wifi Module connected to access point" and don't fail anymore. After the third reboot, "Error retrieving wifi status message" didn't show again, and wifi works perfectly fine.
Moved to 1.21RC1 and again, one works, one fails... so I don't think this is hw related :S
Can I give you anything else for diagnostics?