Solved tool board connection problem
Hi, my tool board sometimes doesn't seem to lose its setting and i have to do an emergency stop for it to come back. I can tell this as the thermistor reading is wrong when it is not connected. It does not seam to lose its CAN connection more its settings, if that makes sense. Is there a nicer way to reset it, I have tried M999 B121, but that doesn't work. Or is there something else I can look at?
@javajoeuk What toolboard firmware version are you using? You can send
M122 B121to check the version and the reset reason of your tool board. Perhaps check the power wiring to that board as well.
Hi, its powered through a distribution board and the power is ok to it. When I do m81 to turn my power to the 24v transformer that also turns the power off the tool distribution board but when i do a m80 to turn it back on it powers up but the end stop which is connected to the board won't enable, and the thermistor reads 2000c.
M122 B121 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 2680, free system stack 2789 words Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,117) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,2.8%,57) MAIN(running,92.0%,350) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0% Last reset 00:02:41 ago, cause: power up Last software reset data not available Driver 0: position 0, 415.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 5290, 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/9, peak Rx sync delay 204, resyncs 0/0, no step interrupt scheduled VIN: 24.5V MCU temperature: min 33.3C, current 36.6C, max 36.9C Ticks since heat task active 98, ADC conversions started 161592, completed 161592, timed out 0, errs 0 Last sensors broadcast 0x00000002 found 1 103 ticks ago, loop time 0 CAN messages queued 1733, send timeouts 0, received 1286, 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 ok
@javajoeuk That explains it then. When you turn the power back on, you need to rerun config.g to configure the expansion board again (
I knew it would be me. I take it the heater warning will go away one i start to tune it? But what is the other warning?
Is there any way to alter the atx power switch in the DWC to also send that when I turn it on?
Warning: Board 121 does not have input handle 3000 Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
I take it the heater warning will go away one i start to tune it?
it probably won't, depends on what the max forecast temperature of the heater is if it was left on full power. Many hotend/ heater cartridge combinations generate those warnings because in order to get rapid heatup and good response to high filament flow rate changes, the heaters used have enough power to get way above a "safe" level if they were to heat in an uncontrolled manner. The warning is there to make you aware of this so you can take appropriate, outside of firmware control, steps to mitigate the risk. Like not leaving the printer unattended, installing a thermal fuse, smoke detections, fire suppression etc.
Board 121 does not have input handle 3000
I have not seen that warning before. @chrishamm any ideas?
Warning: Board 121 does not have input handle 3000
That warning is produced when a M574 or M950 J command is run (normally from config.g) and the main board thinks that the endstop or input being defined currently exists on a CAN-connected expansion board (so it tries to delete it); but it doesn't exist there. For example, if you reset the expansion board using M999 B# (where # is the CAN address) or you upgrade the firmware on an expansion board, and then you run config.g without resetting the main board, you will see that warning.