[3.4beta6] Toolboard missing extrusion and M122 error

T3P3Tony

@pakue thanks that's an interesting result! now you have it working and returning the full result can you try the following:

try the firmware upgrade again
then try upgrading the mainboard to 3.4b6

Pakue

@t3p3tony Upgrading the toolboard to the beta6 works, but after upgrading the MB6HC the M122 issue persists:

m122 b20
Error: Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta6 (2021-11-06 11:56:11)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2752, free system stack 2788 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.1%,101) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,67) MAIN(running,92.0%,350) IDLE(ready,0.0%,27) AIN(delaying,4.9%,148), total 100.0%
Last reset 00:00:20 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 655.0 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 92, reads 10344, writes 11, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 3/6, peak Rx sync delay 186, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 23.8, current 24.0, max 24.1
MCU temperature: min 37.9C, current 38.1C, max 38.2C
M122: Last sensors broadcast 0x00000002 found 1 246 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 264, send time
Response timeout: CAN addr 20, req type 6024, RID=17

T3P3Tony

@pakue thanks. I will need some input from @dc42 on this one!

Pakue

@dc42 Did you have success recreating the issue on your machine? On 3.4b7 the issue still persists.

dc42

@pakue I did not succeed in recreating this. Please test with 3.4.0rc2.

Pakue

@dc42 The issue still persists with 3.4rc2. I've also tried shortening the CAN cable without success.

M122 B20

m122 b20
Error: Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0rc2 (2022-02-22 10:15:02)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2800, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.9%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:02:11 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 655.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 243, writes 11, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 2/6, peak Rx sync delay 198, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 23.8, current 24.0, max 24.1
MCU temperature: min 22.7C, current 31.4C, max 31.4C
M122: Last sensors broadcast 0x00000002 found 1 113 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1956, send tim
Response timeout: CAN addr 20, req type 6024, RID=18

M122 B20 (after a print)

m122 b20
Error: Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0rc2 (2022-02-22 10:15:02)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
M122: Response timeout: CAN addr 20, req type 6024, RID=210

Pakue

@dc42 Would it be any help to record the CAN bus transmission with a scope, or run a firmware version with more verbose logging?

Phaedrux

I'm not sure it will help, but 3.4 final has just released, can you test with that?

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0

Pakue

@phaedrux Unfortunately, it still shows the same problems.

dc42

@Pakue, is this still a problem? If so:

@pakue said in [3.4beta6] Toolboard missing extrusion and M122 error:

@dc42 I do indeed have a ~300W 24V heated bed, but the wires are >2mm^2, 30cm in length and split at the PSU between heated bed and the rest of the electronics. I can measure the GND offset/noise at the toolboard when everything is heating up to double check.

If the bed heater is being driven directly from the Duet (not via a SSR or mosfet switch) then it's still possible that ground noise caused by the bed heater PWM is causing the problem, because the bed heater ground and main ground are commoned at the Duet. In which case, I suggest you provide the tool board power by daisy-chaining the tool board power cable from the main board power terminals, instead of directly from the PSU.

Pakue

@dc42 I'll try that, but I don't think that is the issue in that case, as the M122 error also happens after the print is done and the heater is off.