Duet TOOL1LC Buttons stopped working
-
I just ended up wit a problem with my toolboard.
Everything is working a it should except the buttons on the tool board
They working good for about a year and just stopped.
it really puzzles me since I can't find anything wrong.
Updated firmware and still nothingthis is the config file
;Toolboard button triggers
;M950 P1 C"io1.out"
M950 J1 C"121.button0"
M950 J2 C"121.button1"
;M950 J3 C"121.io1.in"
M581 T2 P1
M581 T3 P2
;M581 T4 P3 S1
;M581 T5 P3 S0m122 b121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5beta2 (2023-02-06 18:43:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 3708, free system stack 80 words
Tasks: Move(notifyWait,0.0%,157) HEAT(notifyWait,0.4%,107) CanAsync(notifyWait,0.0%,49) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.1%,57) MAIN(running,91.6%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:23:55 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 420.0 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 113, reads 62422, 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 -5/9, peak Rx sync delay 215, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 23.9, current 23.9, max 23.9
MCU temperature: min 35.4C, current 35.7C, max 35.8C
Last sensors broadcast 0x00000002 found 1 123 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 28743, send timeouts 0, received 12939, lost 0, free buffers 37, min 37, error reg 20000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0Macro file
;Button1 trigger
M117 "Load Filament"
G4 S2
M98 P"/macros/filament/load filament"any help would be appreciated
Laz
-
@Laszlo-Kozik is this new from RRF 3.5b2 firmware? can you confirm if they still work if you switch back to 3.4.5?