@dc42 I print hand drums to play Plena music from Puerto Rico. The drum is 3d printed and I cut, form, weld and paint the metal hardware and the lugs myself. Mainly use goat skin but also some cow , buffalo and camel skin are used. I have an LED version where when you hit it the leds change color. For that I use an adafruit feather RP2040. I also make the guiros to play Plena music.

Edit:
I mainly use a custom 24x24x24inches printer I built with duet. The drums are mainly printed on PETG some are PLA and the guiros are PLA

After many weeks of testing, I figured out the problem. I started re-wiring every cable to eliminate any problem with the harnesses. Once I got to the power from the Mainboard 6HC to the tool distribution board. I measured the power from this cable with a multimeter and everything was reading normal. For some reason once I rewired this harness everything seems to be working now.

I’ve done dozens of 20–50-hour prints with no problem so far. Updating this post in case someone is having the same issue. Check the power from the main board to the tool distribution board.

@phaedrux Reprinted the housing and assembled everything. My agc was a little low so I had to take it apart an shim it with a piece of paper. Now I have an agc within the range (59)

Duet3D rotating magnet filament monitor v3 on pin 121.io1.in, enabled, sensitivity 24.84mm/rev, allow 35% to 130%, check printing moves every 15.0mm, version 3, mag 131 agc 59, measured sensitivity 25.12mm/rev, min 98% max 101% over 781.5mm

I'm wating on some filament to start a couple of 15 to 17 hour prints to see if I keep getting the issue.

O and I updated to the RRF3.4 stable release.

Just if anyone was wondering, I make hand drums to play Plena (music from Puerto Rico) and I built a 24inx24inx26in printer to be able to print the drums in one go using the duet. That's why I have so many 15 to 20 hour prints to do.

@gloomyandy said in Scanning Z probe G31: invalid Z probe index:

@charliedrums said in Scanning Z probe G31: invalid Z probe index:

uet SZP firmware version 3.5.0-rc.1+ (2023-11-20 12:50:20)

Your SZP does not seem to be running 3.5.0-rc.3. Probably best to make sure all of the boards are using the same version.

Totally brain farted, this was the issue. I was trying to update the SZP board trough putty with sudo apt update but it kept saying everything was updated. Fetched the rc3 update bin file for the SZP from the github directory and uploaded it trough DWC and installed it from there. That seemed to be my problem. I don't get the G31: invalid Z probe index at start up anymore. Thanks everyone for the help.

@micaheli Right now I'm using the Scanning z probe with EZABL from th3dstudio but once the full release of 3.6 comes out I'm going to give it a try with just the scanning z probe in touch mode to see If I can get away from using two sensors. I have a 600mm^3 printer with 4 independent z motors for the gantry. How I run it is in the starting gcode I run G32 which calls bed.g. bed.g goes to all four corners and probes each one. once it finishes the fourth corner it levels out the gantry to those four corners:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Feb 16 2022 21:57:55 GMT-0500 (Eastern Standard Time)
G28 						; home

M561 ; clear any bed transform
G29 S2 ;
G90                    		; absolute positioning
G30 P0 X29 Y40 Z-99999 			; probe near Z belt 1 (drive 3) front left
G30 P1 X609 Y40 Z-99999 		; probe near Z belt 2 (drive 4) front right
G30 P2 X29 Y601 Z-99999 		; probe near Z belt 3 (drive 5) back left
G30 P3 X609 Y601 Z-99999 S4 	; probe near Z belt 4 (drive 6) back right
G1 X335 Y325 F15000     		; go to center of the bed
G30                    		; home Z by probing the bed
M291 P"Automatic bed compensation complete!" R"Your bed is leveled!" S1 T5

after this in the starting gcode I do a G29 ;Run file sys/mesh.g. In mesh.g it just does a M558.1 and G29 S0 K1 to use the scanning z probe to do the scan:

M150 E0 R0 U255 B0 P255 S3 F0 ; set extruder leds to green
G29 S2
M98 P"homez.g"
M558.1 K1 S1.5
G29 S0 K1
M150 E0 R255 U255 B255 P255 S3 F0 ; set extruder leds to white

I also have some lights on the extrude which change color during scanning.

For the scanning itself I run it at a 600mm/s in a 31x31 grid giving me a total of 961 points. For the 600mmx600mm ish bed it takes shy of 1 minute to do the whole scan. This way I get a perfect first layer every time.

Here is how I have my probes configured in config.g

; Z-Probe
M558 K0 P5 C"!io5.in" H3 F900:120 T36000                    ; set Z probe type to EZABL Pro and the dive height + speeds
G31 K0 P500 X-31.27 Y-46.64 Z2.064                          ; set Z probe trigger value, offset and trigger height
M557 X29:609 Y40:603 P31:31                                 ; define mesh grid

; Scanning Z probe
M558 K1 P11 C"120.i2c.ldc1612" F36000:36000:36000 T36000 B1             ; configure SZP as probe 1, type 11, on CAN address 120
M308 A"SZP coil" S10 Y"thermistor" P"120.temp0"             ; thermistor on SZP coil
G31 K1 X-25.00 Y0 Z1.964                                   ; define probe 1 offsets and trigger height
M558.2 K1 S13 R152893                                       ; set drive current and reading offset
M557 X29:609 Y40:603 P31:31                                 ; Define mesh grid for probe 1 (overwrites probe 0 mesh grid)

of course this is just for my particular printer and these values should not be used for your printer, but it might shed some light on how it roughly goes. Hope it helps.

This just happened to me on a 14 hour print. I updated to RRF3.4. Came here to see what it could be. I resumed the print and is printing fine now. the print is still going as I write.

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc2 (2022-02-22 17:04:17) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTD0-3SJ6S-1V82V
Used output buffers: 10 of 40 (40 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 66520 of which 28 recycled
Never used RAM 129804, free system stack 114 words
Tasks: SBC(resourceWait:,0.7%,494) HEAT(notifyWait,0.0%,321) Move(notifyWait,1.7%,248) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,346) CanClock(delaying,0.0%,339) TMC(notifyWait,8.4%,58) MAIN(running,89.1%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 15:54:21 ago, cause: power up
Last software reset at 2022-03-09 01:00, reason: HardFault, GCodes spinning, available RAM 130308, slot 1
Software reset code 0x4063 HFSR 0x80000000 CFSR 0x00000000 ICSR 0x00400803 BFAR 0x00000000 SP 0x2041b4f8 Task MAIN Freestk 1672 ok
Stack: 20429f28 2042c2d8 2041b594 00000001 0000002e 0045c81b 0045c676 61070000 20419a7c 2042bf34 00000000 00000001 00000000 004844d7 2042bf34 00000000 00000000 0048481f 003ffff0 004849f7 20429860 ffffffff 0934d918 2042bf34 20419a7c 2042c2dc ffffffff
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 135
MCU temperature: min 47.3, current 47.5, max 47.7
Supply voltage: min 23.9, current 24.0, max 24.1, 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 99/1, heap memory allocated/used/recyclable 2048/160/126, gc cycles 0
Events: 2 queued, 2 completed
Driver 0: pos 60689, ok, SG min 0, mspos 928, reads 41145, writes 0 timeouts 0
Driver 1: pos 14056, ok, SG min 0, mspos 616, reads 41145, writes 0 timeouts 0
Driver 2: pos 50096, standstill, SG min 0, mspos 72, reads 41145, writes 0 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 664, reads 41146, writes 0 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 152, reads 41146, writes 0 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 104, reads 41145, writes 0 timeouts 0
Date/time: 2022-03-09 16:28:53
Slowest loop: 31.03ms; fastest: 0.05ms
=== 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 20, maxWait 796ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 678710, completed 678677, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is doing "M122" in state(s) 0 0, running macro
Telnet is idle in state(s) 0
File* is doing "G1 X453.419006 Y257.640015 E-0.570000" 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: no data received
=== CAN ===
Messages queued 15065, received 12407, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 268, free buffers 50 (min 47), ts 3026/3026/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 15043/15043
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b8b0
Buffer RX/TX: 1520/2544-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc2
File /opt/dsf/sd/gcodes/Pandero11in_Escalas_0.6n_0.3mm_PLA_13h57m.gcode is selected, processing
HTTP:
Executing macro 0:/macros/Diagnostics, started by M98 P"0:/macros/Diagnostics"
> Next stack level
File:
Buffered code: G1 X453.419 Y257.64 E-.57
Buffered code: G1 E-.03 F2400
Buffered code: G1 Z63.02 F720
Buffered code: G1 X457.643 Y264.663 F10800
Buffered code: G1 Z62.62 F720
Buffered code: G1 E.6 F2400
Buffered code: G1 F4200
Buffered code: G1 X458.599 Y265.619 E.09391
Buffered code: G1 F8640
Buffered code: G1 X457.643 Y264.663 E-.35695
Buffered code: G1 E-.24305 F2400
Buffered code: G1 Z63.02 F720
Buffered code: G1 X459.911 Y269.805 F10800
Buffered code: G1 Z62.62 F720
Buffered code: G1 E.6 F2400
Buffered code: G1 F4200
Buffered code: G1 X460.905 Y270.799 E.09959
Buffered code: G1 F8640
Buffered code: G1 X459.911 Y269.805 E-.37085
Buffered code: G1 E-.22915 F2400
Buffered code: G1 Z63.02 F720
Buffered code: G1 X463.158 Y276.331 F10800
Buffered code: G1 Z62.62 F720
Buffered code: G1 E.6 F2400
==> 992 bytes
Code buffer space: 1552
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.36, max time between full transfers: 44.0ms, max pin wait times: 29.1ms/8.3ms
Codes per second: 18.47
Maximum length of RX/TX data transfers: 3928/1628

Finished downgrading the 6hc and 1lc to 3.3. Going to start a 17 hour print and see how it goes will report back with findings

@phaedrux Brought it up to 70. Going to do some test prints to see if I get the error again.

M591 D0
Duet3D rotating magnet filament monitor v3 on pin 121.io1.in, enabled, sensitivity 24.84mm/rev, allow 35% to 130%, check printing moves every 15.0mm, version 3, mag 132 agc 70, measured sensitivity 24.82mm/rev, min 98% max 101% over 556.6mm

@droftarts
It was not grounded but it is now. Since it takes a couple of days to get here I went and ordered a 1LC v1.3 board to see if that changes anything.

I updated the bootloader on the 1LC and I have grounded the bracket and now the screws and the hemera are grounded. This time I started a print and it started over extruding right from the start. Maybe now with the updated bootloader and grounded everything, updaye everything to 3.5.2 and see what happens? I'll keep trying stuff until the new 1LC gets here. I'll keep the thread updated to my findings.

@PetrKroupa said in SBC RAM Amount?:

@charliedrums - I use Rpi5 with 8Gb and it works perfectly. But I recommend throwing away the SD card and going the SSD route. It works absolutely sensationally. Compared to Rpi4 + SD card, the system boot is many times faster.

O I never thought of that. If I go with the M.2ssd to burn the image do I use just a regular NVMe to USB Adapter and then use an nvme hat for the pi 5?

I'm building a printer with a Duet 3 6HC and a SBC. I'm going with a raspberry pi 5. Is it beneficial to use the 8gb ram model or will the 4gb ram model be sufficient. Is there any benefit of more ram like the 16gb model?

@micaheli Right now I'm using the Scanning z probe with EZABL from th3dstudio but once the full release of 3.6 comes out I'm going to give it a try with just the scanning z probe in touch mode to see If I can get away from using two sensors. I have a 600mm^3 printer with 4 independent z motors for the gantry. How I run it is in the starting gcode I run G32 which calls bed.g. bed.g goes to all four corners and probes each one. once it finishes the fourth corner it levels out the gantry to those four corners:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Feb 16 2022 21:57:55 GMT-0500 (Eastern Standard Time)
G28 						; home

M561 ; clear any bed transform
G29 S2 ;
G90                    		; absolute positioning
G30 P0 X29 Y40 Z-99999 			; probe near Z belt 1 (drive 3) front left
G30 P1 X609 Y40 Z-99999 		; probe near Z belt 2 (drive 4) front right
G30 P2 X29 Y601 Z-99999 		; probe near Z belt 3 (drive 5) back left
G30 P3 X609 Y601 Z-99999 S4 	; probe near Z belt 4 (drive 6) back right
G1 X335 Y325 F15000     		; go to center of the bed
G30                    		; home Z by probing the bed
M291 P"Automatic bed compensation complete!" R"Your bed is leveled!" S1 T5

after this in the starting gcode I do a G29 ;Run file sys/mesh.g. In mesh.g it just does a M558.1 and G29 S0 K1 to use the scanning z probe to do the scan:

M150 E0 R0 U255 B0 P255 S3 F0 ; set extruder leds to green
G29 S2
M98 P"homez.g"
M558.1 K1 S1.5
G29 S0 K1
M150 E0 R255 U255 B255 P255 S3 F0 ; set extruder leds to white

I also have some lights on the extrude which change color during scanning.

For the scanning itself I run it at a 600mm/s in a 31x31 grid giving me a total of 961 points. For the 600mmx600mm ish bed it takes shy of 1 minute to do the whole scan. This way I get a perfect first layer every time.

Here is how I have my probes configured in config.g

; Z-Probe
M558 K0 P5 C"!io5.in" H3 F900:120 T36000                    ; set Z probe type to EZABL Pro and the dive height + speeds
G31 K0 P500 X-31.27 Y-46.64 Z2.064                          ; set Z probe trigger value, offset and trigger height
M557 X29:609 Y40:603 P31:31                                 ; define mesh grid

; Scanning Z probe
M558 K1 P11 C"120.i2c.ldc1612" F36000:36000:36000 T36000 B1             ; configure SZP as probe 1, type 11, on CAN address 120
M308 A"SZP coil" S10 Y"thermistor" P"120.temp0"             ; thermistor on SZP coil
G31 K1 X-25.00 Y0 Z1.964                                   ; define probe 1 offsets and trigger height
M558.2 K1 S13 R152893                                       ; set drive current and reading offset
M557 X29:609 Y40:603 P31:31                                 ; Define mesh grid for probe 1 (overwrites probe 0 mesh grid)

of course this is just for my particular printer and these values should not be used for your printer, but it might shed some light on how it roughly goes. Hope it helps.

@dc42 I print hand drums to play Plena music from Puerto Rico. The drum is 3d printed and I cut, form, weld and paint the metal hardware and the lugs myself. Mainly use goat skin but also some cow , buffalo and camel skin are used. I have an LED version where when you hit it the leds change color. For that I use an adafruit feather RP2040. I also make the guiros to play Plena music.

Edit:
I mainly use a custom 24x24x24inches printer I built with duet. The drums are mainly printed on PETG some are PLA and the guiros are PLA

I think I figured it out. I bought the A type cable which the ends are in line and I need the B type cable which the ends are opposite?
Is this it?

So I accidentally broke the ribbon cable on my scanning z probe. I got some replacement from amazon (uxcell Flexible Flat Cable, 4 Pins 0.5mm Pitch 76mm FPC FFC Flexible Ribbon Cable for LCD TV Car Audio DVD Player Laptop 10Pcs (A Type) ) but now my scanning z probe does not calibrate. Did I get the wrong flex cable?

I get constant

M558.2 K1 S-1
Error: M558.2: failed to calibrate sensor drive current

M558.2 K1
Sensor drive current is 31, offset is 144968

Before the cable changed drive current read 14. Everything worked fine up until the cable changed. Maybe these cables are not the ones? any help will be appreciated. Thank you.

@droftarts Thanks for the reply. I'll switch it to a 31x31 then.

So I have a scanning z probe on a duet 3 6hc on FW 3.5.3. A bed that is 24 x 24in and I was wondering what is the maximum amount of points I can configure the probe to read? I have it set to 900 points. Can I go higher than 900?

M557 X29:609 Y40:603 P30:30  

I was reading the wiki under M557 but it states "There is a firmware-dependent maximum number of probe points supported. Currently this is 441 for the Duet 2 and Duet 3 (enough for a 21x21 grid), and 121 on the Duet 06/085 (enough for a 11x11 grid)."

Hi,
For some reason I'm getting an error Error: Expansion board 120 stopped sending status once I updated to 3.5.3

120 is the z scanning probe. It happens a couple of ours into the print. It doesn't seem to affect the print what so ever but I have no Idea why I'm getting the error code all of the sudden.
I'm running in SBC mode with a raspberry pi 5
M122 B120

M122 B120
Diagnostics for board 120:
Duet SZP firmware version 3.5.3 (2024-09-17 14:34:54)
Bootloader ID: SAMC21 bootloader version 2.10 (2023-11-16)
All averaging filters OK
Never used RAM 13756, free system stack 110 words
Tasks: HEAT(2,nWait 6,0.1%,128) CanAsync(5,nWait 4,0.0%,50) CanRecv(3,nWait 1,0.0%,70) CanClock(5,nWait 1,0.0%,58) ACCEL(3,nWait 6,0.0%,52) MAIN(1,running,71.9%,394) IDLE(0,ready,0.0%,26) AIN(2,nWait 4,27.9%,72), total 100.0%
Owned mutexes: I2C(AIN)
Last reset 06:18:30 ago, cause: software
Last software reset at 2024-03-12 06:08, reason: StackOverflow, available RAM 14136, slot 0
Software reset code 0x0100 ICSR 0x0041a00e SP 0x20007f34 Task ACCE Freestk 5138 ok
Stack: 20002e70 20002ea4 00014913 200029a4 20002ac0 20002998 000139f1 20002ac0 fffffffd 0000002a 00000000 20007f8c 00000000 20007f8c 00014677 00000000 200010a4 20001028 00013eb7 20001028 200010a4 00000032 454c4449 00019000 00012683 200011c0 200011c0
Peak sync jitter 2/6, peak Rx sync delay 213, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 4.9, current 4.9, max 5.0
MCU temperature: min 31.0C, current 40.5C, max 43.5C
Last sensors broadcast 0x00000400 found 1 23 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 3265, send timeouts 0, received 5265, lost 0, errs 13, boc 0, free buffers 18, min 18, error reg 150000
Accelerometer: LIS2DW, status: 00
Inductive sensor: raw value 38352142, frequency 3.57MHz, current setting 14, ok
I2C bus errors 0, naks 0, contentions 0, other errors 0

M122 B121

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.3 (2024-09-17 14:35:31)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 2948, free system stack 69 words
Tasks: Move(3,nWait 7,0.3%,84) HEAT(2,nWait 6,0.3%,106) CanAsync(5,nWait 4,0.0%,54) CanRecv(3,nWait 1,0.1%,70) CanClock(5,nWait 1,0.0%,58) ACCEL(3,nWait 6,0.0%,52) TMC(2,delaying,3.7%,52) MAIN(1,running,90.7%,314) IDLE(0,ready,0.0%,26) AIN(2,delaying,4.9%,112), total 100.0%
Owned mutexes:
Last reset 06:19:45 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 405.0 steps/mm, ok, SG min 0, read errors 2, write errors 0, ifcnt 89, reads 5398, writes 0, timeouts 3, DMA errors 0, CC errors 0, failedOp 0x6a, steps req 0 done 1093428
Moves scheduled 326562, completed 326561, in progress 1, hiccups 129, segs 34, step errors 0, maxLate 0 maxPrep 348, maxOverdue 111, maxInc 48, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 1.00
Peak sync jitter 1/7, peak Rx sync delay 244, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 23.9, current 24.0, max 24.6
MCU temperature: min 41.3C, current 60.6C, max 63.5C
Last sensors broadcast 0x00000002 found 1 140 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 21797, send timeouts 0, received 29511, lost 0, errs 84, boc 0, free buffers 18, min 17, error reg 5f0000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 406, adv 36059/74667
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0
=== Filament sensors ===
Interrupt 1 to 105us, poll 22 to 1614us
Driver 0: ok

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.3 (2024-09-18 11:27:36) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTD0-3SJ6S-1V82V
Used output buffers: 12 of 40 (34 max)
=== RTOS ===
Static ram: 155352
Dynamic ram: 91836 of which 3104 recycled
Never used RAM 92124, free system stack 122 words
Tasks: LASER(5,nWait 7,0.0%,169) SBC(2,rWait:,1.1%,821) HEAT(3,nWait 6,0.0%,321) Move(4,nWait 6,2.2%,211) CanReceiv(6,nWait 1,0.0%,771) CanSender(5,nWait 7,0.0%,327) CanClock(7,delaying,0.0%,346) TMC(4,nWait 6,10.3%,53) MAIN(2,running,86.3%,101) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 06:20:06 ago, cause: software
Last software reset at 2024-10-15 14:32, reason: User, Gcodes spinning, available RAM 92532, slot 2
Software reset code 0x6803 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 52.6, current 60.5, max 61.1
Supply voltage: min 23.7, 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
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/72/72, gc cycles 0
Events: 2 queued, 2 completed
Driver 0: ok, SG min 0, mspos 843, reads 20644, writes 17 timeouts 0
Driver 1: ok, SG min 0, mspos 793, reads 20644, writes 17 timeouts 0
Driver 2: ok, SG min 0, mspos 376, reads 20644, writes 17 timeouts 0
Driver 3: ok, SG min 0, mspos 968, reads 20644, writes 17 timeouts 0
Driver 4: ok, SG min 0, mspos 824, reads 20645, writes 17 timeouts 0
Driver 5: ok, SG min 0, mspos 808, reads 20645, writes 17 timeouts 0
Date/time: 2024-10-15 20:52:58
Slowest loop: 91.49ms; fastest: 0.04ms
=== Storage ===
Free file entries: 20
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 30, maxWait 92107ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
next step interrupt due in 20 ticks, disabled
Moves shaped first try 30486, on retry 15394, too short 35040, wrong shape 199834, maybepossible 8649
=== DDARing 0 ===
Scheduled moves 365344, completed 365314, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== DDARing 1 ===
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 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X416.789001 Y435.783997 E0.016750" 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 1, axes/extruders owned 0x80000007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 0
Extruder 0 sensor: no data received
=== CAN ===
Messages queued 533765, received 650864, lost 0, errs 37341, boc 270
Longest wait 7ms for reply type 6024, peak Tx sync delay 2917, free buffers 50 (min 48), ts 114031/113904/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 58887/58887
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x24d04
Buffer RX/TX: 2432/3720-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.3 (2024-09-21 10:23:58, 64-bit)
HTTP+Executed:
> Executing M122
File 0:/gcodes/Panderos/12in/Pandero_Panal_12in_0.6n_0.3mm_PETG_EXOCUBE_19h56m.gcode is selected, processing
Failed to deserialize the following properties:
- Board -> BoardState from "timedOut"
File:
Buffered code: G1 X416.789 Y435.784 E.01675
Buffered code: G1 X423.25 Y443.993 E.72489
Buffered code: G1 X423.46 Y444.35 E.02874
Buffered code: G1 X423.463 Y444.475 E.00868
Buffered code: G1 X423.464 Y444.565 E.00625
Buffered code: G1 X423.365 Y444.852 E.02107
Buffered code: G1 X423.068 Y445.256 E.03479
Buffered code: G1 X421.701 Y446.316 E.12003
Buffered code: G1 X419.858 Y447.685 E.15931
Buffered code: G1 X419.496 Y447.9 E.02922
Buffered code: G1 X419.135 Y447.995 E.0259
Buffered code: G1 X418.751 Y447.966 E.02672
Buffered code: G1 X418.514 Y447.789 E.02053
Buffered code: G1 X412.403 Y439.273 E.72732
Buffered code: G1 X412.265 Y439.004 E.02098
Buffered code: G1 E-.6 F2400
Buffered code: G1 F28800
Buffered code: G1 X412.224 Y438.924 E-.00712
Buffered code: G1 X412.229 Y438.699 E-.01782
Buffered code: G1 X412.392 Y438.333 E-.03172
Buffered code: G1 X412.751 Y437.954 E-.04133
Buffered code: G1 X415.58 Y435.84 E-.27959
Buffered code: G1 X416.038 Y435.612 E-.0405
Buffered code: G1 X416.282 Y435.588 E-.01941
Buffered code: G1 X416.599 Y435.635 E-.02537
Buffered code: G1 X416.789 Y435.784 E-.01912
Buffered code: G1 X417.711 Y436.955 E-.11802
Buffered code: G1 Z20.6 F720
Buffered code: G1 X417.907 Y441.929 F36000
Buffered code: G1 Z20 F720
Buffered codes: 1400 bytes total
Code buffer space: 2344
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.95, max time between full transfers: 76.7ms, max pin wait times: 71.8ms/7.1ms
Codes per second: 16.97
Maximum length of RX/TX data transfers: 4524/1308

After many weeks of testing, I figured out the problem. I started re-wiring every cable to eliminate any problem with the harnesses. Once I got to the power from the Mainboard 6HC to the tool distribution board. I measured the power from this cable with a multimeter and everything was reading normal. For some reason once I rewired this harness everything seems to be working now.

I’ve done dozens of 20–50-hour prints with no problem so far. Updating this post in case someone is having the same issue. Check the power from the main board to the tool distribution board.