RRF 2.05.1: full freeze - no web, no PanelDue, no USB-Serial
resam last edited by
I just had a very odd failure of my DuetWifi 1.04 with RRF 2.05.1:
it was printing (and also finished successfully), but about 85% through, the printer stopped responding:
- not reachable on the Wifi: no route to host
- no DWC/HTTP
- no Telnet
- PanelDue stopped receiving status
- USB-serial to Printrun/Pronterface failed to open the connection, but the tty device showed up and the USB interface correctly identified as "Duet3D"
PanelDue just displayed the last status of ~85% and "Printing", even though the print finished 2h ago. In its Console it only showed "Wifi reported error: Lost connection, auto reconnecting" - which seems to have failed, as it never recovered.
Because even USB-serial failed, I was not able to get a M122 while the failure was present. The red LED on the board was on.
The print finished successfully - so even after some major firmware glitch (?) the printing routines still functioned and continued correctly.
After pressing the reset button everything was working again within seconds - as usual. PanelDue finally updated again, my Telnet session established successfully, Pronterface connected with the same connection settings as it previously failed.
I've never seen such a failure - so at least for me this is not a common thing (yet?).
Here is a M122 a few minutes after resetting:
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later Board ID: 08DDM-9FAMU-JWNSW-6J9F2-N64S3-XXXXX Used output buffers: 1 of 24 (11 max) === RTOS === Static ram: 25712 Dynamic ram: 94016 of which 116 recycled Exception stack ram used: 312 Never used ram: 10916 Tasks: NETWORK(ready,676) DHTSENSOR(blocked,144) HEAT(blocked,1232) MAIN(running,3728) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:08:11 ago, cause: reset button or watchdog Last software reset time unknown, reason: User, spinning module GCodes, available RAM 10828 bytes (slot 0) 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 40.8, current 41.1, max 41.7 Supply voltage: min 24.1, current 24.3, max 24.5, 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 Date/time: 2020-04-25 19:41:13 Cache data hit count 1435941408 Slowest loop: 16.89ms; 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: 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 === Slowest loop: 80.99ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(1) 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 ec:fa:XX:XX:XX:XX WiFi Vcc 3.33, reset reason Turned on by main processor WiFi flash size 4194304, free heap 22368 WiFi IP address 192.168.1.42 WiFi signal strength -65dBm, reconnections 0, sleep mode modem Socket states: 2 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: ok
- not reachable on the Wifi: no route to host
StAnZ-007 last edited by StAnZ-007
I have exacly same problem on my printer, then I try to remove my PanelDue for the moment, and no more problems...
Same FW version on the Duet Board, and last FW of the PanelDue, but it was same with the old FW of the Panel.
The Duet2 board (v1.04) can stay serveral days connected and used without any problems when the PanelDue is disconnected, but when I connect the screen, after several hours using the panel, all the system freeze and I lost connection with the Duet Web Control (v2.0.7)
Each time, the printer finish the job without problems, but if the machine switch to pause mod (to change the filament for exemple) when system is freezed, it's impossible to restart the print, and that bad because you lose time and money with bad parts...
In this case, how to reset ? OFF + ON, or Emergency button...
Hope have an answer about this problem to be able to use my PanelDue again...
@resam Please keep us posted if this re-occurs.
@StAnZ-007 Your issue sounds a bit different. Sounds like you're able to reproduce it as long as the PanelDue is connected?
StAnZ-007 last edited by
e it as long as the PanelDue is connected?
Yes, on my printer, the system does not freeze all the time, but very regularly... It happens several times before I find the solution to disconnect the panel.
@StAnZ-007 Please create a separate post with more details on your issue as I think it may be unrelated. Include an M122 report config files, etc.