topic_solved Duet 3 + SBC: Random Freezes and Crashes
Here's a more major issue I've been having; the board randomly crashes
The symptoms at first were shown through DWC disconnecting (orange message network disconnected)
But then I started having gcode commands not going through (then orange message)
Or even the tool temp not showing up on the graph; as if it didn't exist.
But then It would also stop in the middle of a mesh leveling
Then just now in the middle of a print; now that's not good.
This time however I managed to connect to it through serial and run a M122; I hope someone can find it insightful and help me out with it:
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.01-RC10 running on Duet 3 MB6HC v0.6 or 1.0 Board ID: 08DJM-956L2-G43S4-6JTDA-3SS6L-1B76HUsed output buffers: 1 of 40 (10 max) === RTOS === Static ram: 154572 Dynamic ram: 162452 of which 56 recycled Exception stack ram used: 520 Never used ram: 75616 Tasks: NETWORK(ready,2076) HEAT(blocked,1184) CanReceiv(suspended,3824) CanSender(suspended,1432) CanClock(blocked,1432) TMC(blocked,80) MAIN(running,4740) IDLE(ready,80) Owned mutexes: === Platform === Last reset 00:05:19 ago, cause: software Last software reset at 2020-04-29 19:47, reason: User, spinning module LinuxInterface, available RAM 75632 bytes (slot 1) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 39.7, current 41.7, max 41.9 Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Driver 0: standstill, reads 51726, writes 24 timeouts 0, SG min/max 0/506 Driver 1: standstill, reads 51727, writes 24 timeouts 0, SG min/max 0/1023 Driver 2: standstill, reads 51727, writes 24 timeouts 0, SG min/max 0/345 Driver 3: standstill, reads 51728, writes 24 timeouts 0, SG min/max 0/216 Driver 4: standstill, reads 51728, writes 24 timeouts 0, SG min/max 0/455 Driver 5: standstill, reads 51733, writes 20 timeouts 0, SG min/max 0/1023 Date/time: 2020-04-29 19:52:41 Slowest loop: 5.28ms; fastest: 0.14ms === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 357, MaxWait: 93209ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 252, completed moves: 252, 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 -1 -1 -1 -1 -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 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 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon* is idle in state(s) 0 0, running macro Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 1.64ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 1251, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 97491ms ago RX/TX seq numbers: 0/6965 SPI underruns 0, overruns 0 Number of disconnects: 2 Buffer RX/TX: 0/0-0 ok
Please also post the output of this command run on the Pi
apt show duetsoftwareframework
A Former User last edited by
apt list 2>/dev/null | grep "duet\|reprap"just to make sure its all on the up and up
Of course; there you go:
pi@duet3:~ $ apt show duetsoftwareframework Package: duetsoftwareframework Version: 2.1.1 Priority: standard Section: electronics Maintainer: Duet3D Packaging Authority <firstname.lastname@example.org> Installed-Size: unknown Depends: duetcontrolserver (= 2.1.1), duetsd (= 1.0.6), duettools (= 2.1.1), duetwebserver (= 2.1.0), duetwebcontrol (= 2.1.5), reprapfirmware (>= 2.1.1-1), reprapfirmware (<= 2.1.1-999) Homepage: https://pkg.duet3d.com Vcs-Git: https://github.com/chrishamm/DuetSoftwareFramework.git Download-Size: 1,706 B APT-Manual-Installed: yes APT-Sources: https://pkg.duet3d.com unstable/armv7 armhf Packages Description: Meta package for the full Duet software framework N: There are 25 additional records. Please use the '-a' switch to see them. pi@duet3:~ $ apt list 2>/dev/null | grep "duet\|reprap" duetcontrolserver/unstable,now 2.1.1 armhf [installed,automatic] duetruntime/unstable,now 2.1.1 armhf [installed,automatic] duetsd/unstable,now 1.0.6 all [installed,automatic] duetsoftwareframework/unstable,now 2.1.1 armhf [installed] duettools/unstable,now 2.1.1 armhf [installed,automatic] duetwebcontrol/unstable,now 2.1.5 all [installed,automatic] duetwebserver/unstable,now 2.1.0 armhf [installed,automatic] reprapfirmware/unstable,now 2.1.1-1 all [installed,automatic]
Ps: I actually had to reset the PSU after the crash otherwise the Pi wouldn't show on network
Please run another system update via
sudo apt-get update sudo apt-get upgrade
from SSH or a terminal on the Pi and this problem should be gone.
RC10 with duetsoftwareframework 2.1.1 has known crashes. You want RC10 with DSF 2.1.2.
At this moment, that combo is the highest release available. Therefore, a normal
sudo apt update sudo apt upgrade duetsoftwareframework
will install this.
Chris and I posted at the same time. We are saying the same thing (commands have same end result).
Danal last edited by Danal
@bearer A (perhaps) slightly easier way to get the same thing. Note this was run on a machine with 2.0.0 installed.
apt list duet\* Listing... Done duetcontrolserver/unstable 2.1.2 armhf [upgradable from: 2.0.0] duetruntime/unstable 2.1.2 armhf [upgradable from: 2.0.0] duetsd/unstable,now 1.0.6 all [installed] duetsoftwareframework/unstable 2.1.2 armhf [upgradable from: 2.0.0] duettools/unstable 2.1.2 armhf [upgradable from: 2.0.0] duetwebcontrol/unstable 2.1.5 all [upgradable from: 2.1.3] duetwebserver/unstable 2.1.0 armhf [upgradable from: 2.0.0] apt list reprap\* Listing... Done reprapfirmware/unstable 2.1.2-1 all [upgradable from: 2.0.0-1]
Ok looks like it's much more stable now; the hotend heater still disappears from the graph and available sensor list every now and then but it doesn't stop it from running
It's just a bit nerve-racking to not have a way to monitor hotend temp at all times
RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 are now available. If the hotend heater still disappears after installing that version, please start a new thread about it.