Duet 6XD "halted" and show restart , why?

FBG

Hello,

i use duet 6XD some days and everything was ok, but now while i am printing or not, the board show me the message for restart...

Emergency stop, attemping to reconnect...

I don't know why, i dont have any input config that restart the board for any alarm or similar.

This is the M122 that give me after restart.

Any idea?

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6XD version 3.4.5 (2022-11-30 19:41:59) running on Duet 3 MB6XD v1.0 or later (SBC mode)
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 151200
Dynamic ram: 65076 of which 0 recycled
Never used RAM 134396, free system stack 219 words
Tasks: SBC(ready,0.5%,511) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,343) MAIN(running,96.9%,1232) IDLE(ready,2.6%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:32 ago, cause: software
Last software reset at 2023-05-04 14:57, reason: User, none spinning, available RAM 130916, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 18465
MCU temperature: min 36.8, current 37.0, max 47.2
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, 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: ok
Driver 1: ok
Driver 2: ok
Driver 3: ok
Driver 4: ok
Driver 5: ok
Date/time: 2023-05-04 14:58:31
Slowest loop: 25.43ms; fastest: 0.04ms
=== 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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
=== CAN ===
Messages queued 165, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 165/0/0
Tx timeouts 0,0,164,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 1616/1616
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2b770
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 13
Full transfers per second: 51.67, max time between full transfers: 257.0ms, max pin wait times: 36.0ms/10.0ms
Codes per second: 1.98
Maximum length of RX/TX data transfers: 3008/844

dc42

@FBG that reset code indicates that the SBC commanded the Duet to reset. More info may be available in the DSF logs.

FBG

@dc42 Where i can find DSF logs?

oliof

@FBG

log into your Single Board Computer
run sudo journalctl -xe -u duetcontrolserver

chrishamm

@FBG E-STOP from the SBC is only triggered if it is part of a macro file or when you hit E-STOP on the UI. There is no other mechanism that calls it. Also, E-STOP on DWC restarts the board as well, it doesn't leave the machine in the "Halted" state.

Do you have any other triggers configured? A trigger can be set up to halt the machine as well, and if there is a dodgy connection to it, that could explain it.

FBG

Hello everybody,
after send the code for the dsf log this said that trigger6 do the restart...

I checked trigger6 and my config.g and is truth... i did a mistake in the config.g file...

Sorry for that, i was desperate!!

Thanks for your support!