Posts made by Woheho

@phaedrux Its a Sandisk Ultra 64GB Class 10 (1) Red-Grey.

@tidofelder Yeah, should not be an issue. This line is not used any more.

@jay_s_uk I skrewed everything down in the beginning of my built and never touched it again. So i dont think that the cable is sitting loose or something. Could i shield the cable with tin foil or something ?

@chrishamm I am a little bit confused about the versions. When i was at 3.3 i had the 5.10.17-v7l+ kernel with buster 10. Then i updated via sudo apt-get upgrade and i am now on 5.10.103-v7l+, which is also Debian 10 (buster). So i never had the bullseye-based image on my pi right ?

@jay_s_uk So i tried with 3.4 and it stopped again.
Here is the log file:
Syslog2.txt

@jay_s_uk Ok i will give it a try.

Hello Duet3d,
i have the problem that my printer is stoping randomly in mid print. Usually i start longer prints for 4 to 5 days and its sad to see it stopping after 3 days or so. The printer aborts the job and the nozzle stops right over the print.
I am using a Duet 3 MB 6HC with a RPI and 3.3 Firmware in a E3D Toolchanger.

This is the M122 log: M122 Log.txt

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6JKD8-3SC6N-TV439
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 65264 of which 0 recycled
Never used RAM 133112, free system stack 114 words
Tasks: SBC(ready,168.0%,312) HEAT(delaying,1.5%,325) Move(notifyWait,19.2%,245) CanReceiv(notifyWait,4.4%,774) CanSender(notifyWait,1.1%,362) CanClock(delaying,0.7%,339) TMC(notifyWait,9.5%,59) MAIN(running,83.7%,922) IDLE(ready,0.0%,29), total 288.2%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 96:17:19 ago, cause: software
Last software reset at 2022-04-04 14:03, reason: User, GCodes spinning, available RAM 135632, slot 1
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 295
MCU temperature: min 34.2, current 40.5, max 43.0
Supply voltage: min 23.8, current 24.0, 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 99/72, heap memory allocated/used/recyclable 4096/1540/256, gc cycles 147232
Driver 0: position 24891, standstill, reads 38302, writes 43 timeouts 0, SG min/max 0/1023
Driver 1: position -7440, standstill, reads 38302, writes 43 timeouts 0, SG min/max 0/1023
Driver 2: position 194196, standstill, reads 38302, writes 43 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 38334, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 38334, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 38303, writes 43 timeouts 0, SG min/max 0/1023
Date/time: 2022-04-08 14:21:14
Slowest loop: 160.40ms; 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, maxWait 670924ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4063605, completed moves 4063605, hiccups 0, stepErrors 0, LaErrors 7740, Underruns [20, 2, 149], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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, chamberHeaters = 0 -1 -1 -1
=== 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 6645108, received 11100711, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 402, free buffers 49 (min 31), ts 1733200/1733199/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 4, checksum errors: 9999
Last transfer: 1ms ago
RX/TX seq numbers: 55816/31862
SPI underruns 9999, overruns 9999
Disconnects: 3, timeouts: 2, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 46.43, max wait times: 547.6ms/0.0ms
Codes per second: 13.08
Maximum length of RX/TX data transfers: 3988/1792

On the Pi I found this error message: Syslog.txt

see uploaded txt file otherwise post is too long

Is it a problem with the SPI cable or is the duet crashing ? How can i stop these ghost stops ?