Heater fault but not accurate
-
M122 B1 Diagnostics for board 1: Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41) Bootloader ID: not available Never used RAM 159104, free system stack 4400 words Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,118) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.2%,63) MAIN(running,91.5%,438) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0% Last reset 00:01:07 ago, cause: software Last software reset data not available Driver 0: position 0, 80.0 steps/mm, standstill, reads 64796, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0 Driver 1: position 0, 80.0 steps/mm, standstill, reads 64797, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0 Driver 2: position 0, 80.0 steps/mm, standstill, reads 64797, writes 11 timeouts 0, SG min/max 0/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/10, peak Rx sync delay 177, resyncs 0/0, no step interrupt scheduled VIN: 24.0V, V12: 12.2V MCU temperature: min 35.6C, current 35.6C, max 35.8C Ticks since heat task active 64, ADC conversions started 67687, completed 67687, timed out 0, errs 0 Last sensors broadcast 0x00000000 found 0 69 ticks ago, loop time 0 CAN messages queued 25, send timeouts 0, received 619, lost 0, free buffers 37, min 37, error reg 10000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
-
Was a mismatched version on the expansion board. Need to update the how to update firmware wiki as it doesn't mention M997 B1 for the expansion board I had to find it in the depths of getting started with duet 3.
-
How did you perform the firmware update?
I think 3.4 is supposed to have improvements to automate the update on expansion board firmware update process.
I'll see about adding a note to the firmware update wiki regarding M997 B1
-
@wdenker now my E drive isn't honoring the microstepping and steps per mm.
-
Can you share your config.g?
-
@phaedrux I had to load the firmware into the new firmware folder then M997 B1 but even the getting started documentation shows that it should be in the sys folder. I am guessing the firmware folder is just that new since none of my other machines have it yet.
-
-
Yes the firmware folder is new as of 3.3 and was added in an effort to tidy up the /sys folder now that there are many firmware files for all of the expansion boards, etc.
-
@wdenker said in Heater fault but not accurate:
@wdenker now my E drive isn't honoring the microstepping and steps per mm.
If you send M92 and M350 by themselves in the gcode console, what do they report as? How are they not being honored?
Can you also send
M98 P"config.g"
and report any errors? -
@phaedrux I lost the 120 hour print on it and rebooted and now it is all working as expected.