Solved Toolboard V1.1 issue
I have an issue with TB v1.1. I think is overheating.
The printer is inside the chamber which heats up to 60C more less.
My question is, does TB can be affected by a temperature that high?
The reason for my question is that after proper heat up, the toolboard gives me different reading each time ( clicky probe - Z_probe based on microswitch)
@dan1990 what does M122 Bnn where nn is the CAN address of the toolboard report for MCU temperature?
oozeBot last edited by oozeBot
@dan1990 there is an old thread where dc42 confirmed the toolboard should be fine up to 85c. We have verified our printers up to 80c in heated chambers, but mostly print in ABS and keep the chambers at 60c and have never had any issues with the toolboard.
Dan1990 last edited by Dan1990
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2624, free system stack 2762 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,115) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.8%,57) MAIN(running,92.0%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 01:01:59 ago, cause: software
Last software reset data not available
Driver 0: position 0, 422.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 23, reads 44706, writes 0, 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 0/7, peak Rx sync delay 214, resyncs 0/0, no step interrupt scheduled
MCU temperature: min 44.9C, current 58.0C, max 67.9C
Ticks since heat task active 245, ADC conversions started 3719987, completed 3719985, timed out 1, errs 0
Last sensors broadcast 0x00000002 found 1 0 ticks ago, loop time 0
CAN messages queued 39538, send timeouts 0, received 29562, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0
@dan1990 that does not appear to be getting hot enough that it should be faulting. what is the issue with the microswitch reading?
Well, the probe gives me different values after when the chamber is heated, or sometimes I will even get a measurement error ( measurement inconsistent or something similar ).
I thought that the probe is the issue but I have changed a few of them already and always end up with the same issue.
The probe is OMRON MICROSWITCH (D2F-5L).
What issues are you seeing with the chamber at temperature. Please copy in the output of your probing sequence.
S1lencer last edited by
It is also possible that the switch suffers from the heat. The springs inside are mostly out of metal and the dimensions of these an thus also the springrate changes with temperature slightly. Is the reapeated reading under the same temperature the same?
I have fixed the problem.
My measurement was taken too quickly and the probe wasn't giving correct data.
@dan1990 thanks for confirming what the issue was.