Duet 3 6HC losing network connection
-
Hi guys, I'm having an issue with my MB 6HC apparently losing network connection and stopping mid print. Attached is an m122 report. Also note that the rpi is connected to ethernet and not wifi. Any help would be greatly appreciated!
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJMSS-6JTDA-3SS6J-1BG7B
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 67860 of which 0 recycled
Never used RAM 127252, free system stack 154 words
Tasks: ACCEL(notifyWait,0.0%,234) SBC(resourceWait:,71.6%,466) HEAT(notifyWait,2.5%,321) Move(notifyWait,11.9%,248) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,356) CanClock(delaying,1.2%,333) TMC(notifyWait,50.3%,58) MAIN(running,86.0%,1231) IDLE(ready,0.1%,30), total 223.7%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 168:18:44 ago, cause: software
Last software reset at 2023-07-06 10:53, reason: User, GCodes spinning, available RAM 127204, slot 2
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 815
MCU temperature: min 28.0, current 30.8, max 35.2
Supply voltage: min 24.0, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/96/96, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 808, reads 8175, writes 119 timeouts 0
Driver 1: standstill, SG min 0, mspos 984, reads 8211, writes 83 timeouts 0
Driver 2: standstill, SG min 0, mspos 104, reads 8263, writes 31 timeouts 0
Driver 3: standstill, SG min 0, mspos 488, reads 8235, writes 59 timeouts 0
Driver 4: standstill, SG min 0, mspos 488, reads 8235, writes 59 timeouts 0
Driver 5: standstill, SG min 0, mspos 488, reads 8235, writes 59 timeouts 0
Date/time: 2023-07-13 11:11:49
Slowest loop: 403.80ms; fastest: 0.03ms
=== 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 71, maxWait 519395576ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 582890, completed 582890, hiccups 0, stepErrors 0, LaErrors 0, Underruns [1267, 0, 8], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.5
=== 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 5453296, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 3029625/0/0
Tx timeouts 0,0,3029624,0,0,2423670 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 2, checksum errors: 239
RX/TX seq numbers: 26018/26018
SPI underruns 263, overruns 0
State: 5, disconnects: 4, timeouts: 4, IAP RAM available 0x2b880
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 14082
Full transfers per second: 39.47, max time between full transfers: 194.2ms, max pin wait times: 63.4ms/9.9ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 3160/44 -
@AlecSanchez that's a lot of transfer ready pin glitches.
How do you have the cable routed between the pi and the 6HC?
Probably worth updating to the latest stable too -
@AlecSanchez I agree with @jay_s_uk, that's way too many TfrRdy glitches and too many checksum errors. You should check the ribbon cable and make sure there is no source of interference next to it (power cables for example). If there is none, consider replacing the cable or put some shield wrap around it and check if that improves things.
