Random reboot

[Amagatth]

Hi all,

I have Lot of random reboot on one of my printer ,

Duet 6hc + 3hc

The m122 give this result

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3S0-7JTDL-3S06R-K8KV8
Used output buffers: 1 of 40 (7 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67908 of which 0 recycled
Never used RAM 130004, free system stack 200 words
Tasks: SBC(ready,0.2%,694) HEAT(notifyWait,0.0%,326) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.6%,91) MAIN(running,91.9%,1231) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:38 ago, cause: power up
Last software reset at 2023-08-04 18:01, reason: User, GCodes spinning, available RAM 126236, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 125
MCU temperature: min 43.7, current 45.5, max 46.4
Supply voltage: min 24.9, current 24.9, max 24.9, 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
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 4, reads 26574, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 4, reads 26574, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 4, reads 26574, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 4, reads 26574, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 2, reads 26574, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 2, reads 26574, writes 14 timeouts 0
Date/time: 2023-08-04 18:49:10
Slowest loop: 0.21ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 2 4 3 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
=== CAN ===
Messages queued 911, received 1643, lost 0, boc 0
Longest wait 2ms for reply type 6053, peak Tx sync delay 6, free buffers 50 (min 49), ts 494/493/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 2, checksum errors: 6
RX/TX seq numbers: 48187/3957
SPI underruns 3, overruns 3
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
File /opt/dsf/sd/gcodes/BOARDS/DIAMOND/DIAMOND_7.0_3Futures_MS_90_09_3001_FatandBM_quali1.gcode is selected, paused
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 31
Full transfers per second: 39.70, max time between full transfers: 536.1ms, max pin wait times: 74.6ms/19.5ms
Codes per second: 3.22
Maximum length of RX/TX data transfers: 3052/1452

Anyone have an idea of the problem ??

[dc42]

@Amagatth said in Random reboot:

Last reset 00:01:38 ago, cause: power up

Looks like you either had a power brownout or you have problems with your PSU.

[Amagatth]

@dc42 it’s random reboot during print we build lot of printers with this psu you think is a default of one ?

[dc42]

@Amagatth I suggest you try replacing the PSU and/or the cables connecting it to the Duet. A faulty mains cable is another possibility.