Thermostatically controlled fan, sensor on different board
-
I have a BMG-X2 that I setup with two toolboards and I'm only using one heatsink cooling fan connected to one toolboard. The fan doesn't function unless I have it controlled by a sensor on the same toolboard.
M308 S1 P"21.temp0" Y"thermistor" T100000 B4680 C6.455513e-8 M950 F0 C"22.out2" Q500 M106 P0 S255 T45 H1:2 C"Heatsink Fan"
According to the release notes though, it should work:
"[Duet 3 with expansion/tool boards] Expansion boards now track the temperatures of all sensors in the system. This means that a thermostatic fan connected to an expansion board can now be controlled by sensor(s) on different expansion boards(s)."
-
Can you post your full config.g and the results of sending M98 P"config.g" and M122 and M122 B# where # is the can address of your expansion boards?
-
@p8blr this is a known bug, fixed in the imminent 3.4.2rc3 release.
-
My config file is a text file attachment on my original post.
M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-9P63L-DJ3T0-6JKD0-3S46K-TU1R8 Used output buffers: 6 of 40 (22 max) === RTOS === Static ram: 151000 Dynamic ram: 96564 of which 288 recycled Never used RAM 102820, free system stack 188 words Tasks: NETWORK(ready,26.8%,209) ETHERNET(notifyWait,0.0%,168) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,65.3%,925) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:08:46 ago, cause: power up Last software reset at 2022-08-30 16:15, reason: HardFault undefInstr, GCodes spinning, available RAM 102860, slot 1 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00010000 ICSR 0x00400803 BFAR 0x00000000 SP 0x2041b508 Task MAIN Freestk 1672 ok Stack: 00000000 2042c2f8 00000000 00000000 000001cd 00457c9b 0045c898 610f0000 20419a8c 2042bf54 00000000 00000001 00000000 00484687 2042bf54 00000000 00000000 004849cf fffbfff0 00484ba7 2042c2f8 20429f48 00000000 2041b5a4 a5a5a5a5 0045c897 ffffffff Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 151 MCU temperature: min 19.7, current 36.7, max 36.9 Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 8, reads 62152, writes 17 timeouts 0 Driver 1: standstill, SG min 0, mspos 8, reads 62152, writes 17 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 62152, writes 17 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 62159, writes 11 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 62159, writes 11 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 62159, writes 11 timeouts 0 Date/time: 2022-08-31 08:17:24 Slowest loop: 10.47ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 5.7ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 4794, received 18972, lost 0, boc 0 Longest wait 3ms for reply type 6026, peak Tx sync delay 6, free buffers 50 (min 49), ts 2633/2632/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 13.24ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 1 0 0 Socket states: 5 2 2 2 2 0 0 0
M122 B21 Diagnostics for board 21: Duet TOOL1LC rev 1.1 or later firmware version 3.4.1 (2022-06-01 21:16:39) 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%,113) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.9%,341) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0% Last reset 00:08:53 ago, cause: power up Last software reset data not available Driver 0: pos 0, 415.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 4516, writes 15, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x72, 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/6, peak Rx sync delay 211, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.7, current 24.7, max 24.7 MCU temperature: min 21.9C, current 39.1C, max 39.1C Last sensors broadcast 0x00000002 found 1 148 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 8561, send timeouts 0, received 6947, lost 0, free buffers 37, min 37, error reg 0 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 0
M122 B22 Diagnostics for board 22: Duet TOOL1LC rev 1.1 or later firmware version 3.4.1 (2022-06-01 21:16:39) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 2624, free system stack 88 words Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,101) 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%,341) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0% Last reset 00:08:55 ago, cause: power up Last software reset data not available Driver 0: pos 0, 415.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 5341, writes 15, 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 1/6, peak Rx sync delay 210, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.0, current 24.1, max 24.1 MCU temperature: min 22.5C, current 37.7C, max 37.7C Last sensors broadcast 0x00000004 found 1 38 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 10734, send timeouts 0, received 6983, lost 0, free buffers 37, min 37, error reg 0 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 0
-
@dc42 Oh good to know! I'll give that version a try and see if it fixes the issue.
-
@p8blr The new firmware fixed the issue! However, now I'm getting weird PID autotune errors, so I may make a new thread for that topic. Thank you for your help!