Expansion board stopped sending status. Afteer updating to 3.5.3
-
Hi,
For some reason I'm getting an error Error: Expansion board 120 stopped sending status once I updated to 3.5.3120 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 B120M122 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 0M122 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: okM122
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 -
@charliedrums it's most likely an issue with the CAN/power cable to the SZP. Check the crimp connections, and if the SZP is mounted on the hot end, use a cable tie to anchor the cable to the hot end. Having a moving cable going directly into a connector is a recipe for getting bad connections.
Does the LED on the SZP momentarily cease to flash in sync with the main board when the warning appears?
