Problem with Fan Settings Across 3HC and Mini 5+
-
Can you send M98 P"config.g" and see if any errors are generated?
-
@Phaedrux i dont see any related errors. i have to resolve my Daemon issue.
M98"config.g"
5/25/2023, 12:20:47 PM Error: bad model parameters Accelerometer 20:0 type LIS3DH with orientation 14 samples at 1344Hz with 10-bit resolution Warning: the height map was loaded when the current Z=0 datum was not determined by probing. This may result in a height offset. Warning: Macro file config-override.g not found Error: in file macro line 219 column 20: meta command: variable 'daemonLoop' already exists -
@RogerPodacter to add more details, if i physcally swap the 2 fans, the 3HC continues to run 100%. so the fans hardware are ok, its something wrong with the configuration or the sensor number assignments etc. whichever fan is on the 3HC, that one doesnt work.
-
What's the can address on the 3HC? 1?
Can you send M122 and M122 B1 and report the results here?
-
@Phaedrux yes the 3HC is address 1 default.
Mainboard M122
5/26/2023, 6:14:09 AM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: J6RFD-NR6KL-K65J0-409NN-LK02Z-7M5YU Used output buffers: 1 of 40 (34 max) === RTOS === Static ram: 103684 Dynamic ram: 113580 of which 308 recycled Never used RAM 21284, free system stack 174 words Tasks: NETWORK(notifyWait,64.4%,215) HEAT(notifyWait,0.8%,342) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,1.9%,772) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.1%,339) TMC(notifyWait,20.0%,106) MAIN(running,113.0%,419) IDLE(ready,113.1%,30) AIN(delaying,14.7%,263), total 328.2% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 23:39:51 ago, cause: software Last software reset at 2023-05-25 06:33, reason: StuckInSpinLoop, GCodes spinning, available RAM 21204, slot 1 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044f80f BFAR 0xe000ed38 SP 0x20003df4 Task MAIN Freestk 771 ok Stack: 0009159f 00090b7c 61070000 421d8000 409b5800 369dc3a0 426ff5c3 42adf895 3b34e113 3b4ba16c 3a03b8df b9fd72b5 3f800002 00000005 00000000 00000000 00000000 00000000 3f800000 20000010 00090b65 421d8000 ffffffff 00000000 00057376 42adf895 2002a654 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 85192032, completed 85192032, timed out 0, errs 0 Step timer max interval 1487 MCU temperature: min 38.1, current 39.8, max 40.9 Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/648/616, gc cycles 106635 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11370, writes 48, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11370, writes 48, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11368, writes 48, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x01 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11369, writes 48, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11369, writes 48, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6a Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11369, writes 48, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 11369, writes 48, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2023-05-26 06:14:07 Cache data hit count 4294967295 Slowest loop: 89.15ms; fastest: 0.09ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 8.4ms, write time 61.5ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: mesh, 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, chamber heaters 2 -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 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 767731, received 4771867, lost 0, boc 0 Longest wait 7ms for reply type 6013, peak Tx sync delay 392, free buffers 18 (min 17), ts 425959/425958/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 63.60ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is providing access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address ea:68:e7:e5:63:f4 WiFi Vcc 3.39, reset reason Power up WiFi flash size 2097152, free heap 25248 WiFi IP address 192.168.1.10 Connected clients 1 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 03HC M122
5/26/2023, 6:15:11 AM M122 B1 Diagnostics for board 1: Duet EXP3HC rev 1.02 or later firmware version 3.4.2 (2022-09-13 15:05:23) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 158256, free system stack 178 words Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.4%,88) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.3%,82) CanClock(notifyWait,0.1%,71) TMC(notifyWait,14.1%,99) MAIN(running,63.8%,399) IDLE(ready,0.0%,40) AIN(delaying,21.2%,263), total 100.0% Last reset 23:47:12 ago, cause: power up Last software reset data not available Driver 0: pos 0, 690.0 steps/mm,standstill, SG min 0, mspos 8, reads 54219, writes 107 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 690.0 steps/mm,standstill, SG min 0, mspos 8, reads 54219, writes 107 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 54300, writes 27 timeouts 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 -12/13, peak Rx sync delay 183, resyncs 0/1, no step interrupt scheduled VIN voltage: min 21.0, current 24.2, max 29.0 V12 voltage: min 12.3, current 12.3, max 12.3 MCU temperature: min 28.0C, current 32.1C, max 33.9C Last sensors broadcast 0x00003000 found 2 158 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 1370453, send timeouts 0, received 1456049, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 -
@RogerPodacter there must be some conflict with how i have my fans setup. when i change H16 to H4, the fan works just fine. but when using H16 as a sensor monitor, it runs 100%.
if i set both fans to H-1, both work normally and i can manually control them with 0-100 slider bar.
-
What is the temperature difference between H4 and H16? Your set temp is only 30c, so if one is higher than the other, it will run faster.
-
@Phaedrux both are reading 21.6 and 21.7. these TC's have been in use for many months. the only difference is i have now added a 3HC trying to use the fan. so its definitely a config.g setup issue.
it allows me to use my hand heat to trigger 30C and challenge the fans easily.
to be clear the mode is on or off, so there is no variable temperature gradient. using H4, the fan turns on at 30C. using H15 or H16, the fan runs 100% non-stop.
-
@RogerPodacter is it because you’ve defined fan0 as part of tool 4 and 5? I just did a quick scan, so that might be intentional.
Ian
-
@RogerPodacter please upgrade to the latest stable firmware, which is 3.4.5, and test again.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
thanks all, unfortunately the issue remains. i've upgrade all components to 3.5.0 beta 3, but it just seems that a fan running from a 3HC wont accept thermocouple sensor from a Mini 5+. i dont know what else it could be. the best i can understand is a thermocouple on the mainboard cannot be used as a sensor monitor for a fan on the 3HC. but thermistors work fine, so its something related to the daughterboard perhaps.
M122
5/27/2023, 7:52:33 AM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.3 (2023-04-14 11:28:00) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: J6RFD-NR6KL-K65J0-409NN-LK02Z-7M5YU Used output buffers: 13 of 40 (35 max) Error in macro line 77 while starting up: bad model parameters === RTOS === Static ram: 102968 Dynamic ram: 124060 of which 276 recycled Never used RAM 11896, free system stack 186 words Tasks: NETWORK(ready,19.5%,228) HEAT(nWait,0.1%,336) Move(nWait,0.0%,358) CanReceiv(nWait,0.1%,774) CanSender(nWait,0.0%,336) CanClock(delaying,0.0%,350) TMC(delaying,1.2%,108) MAIN(running,72.5%,454) IDLE(ready,5.8%,29) AIN(delaying,0.8%,266), total 100.0% Owned mutexes: === Platform === Last reset 00:03:28 ago, cause: software Last software reset at 2023-05-27 07:49, reason: User, Gcodes spinning, available RAM 12380, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 208820, completed 208820, timed out 0, errs 0 MCU temperature: min 38.8, current 39.8, max 40.4 Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/1300/1232, gc cycles 273 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 107, reads 18942, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 107, reads 18941, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 107, reads 18941, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 101, reads 18941, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 103, reads 18941, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 2, read errors 0, write errors 1, ifcnt 105, reads 18941, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 2, read errors 0, write errors 1, ifcnt 105, reads 18941, writes 16, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2023-05-27 07:52:32 Cache data hit count 372944678 Slowest loop: 89.07ms; fastest: 0.10ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 6.2ms, write time 31.4ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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, chamber heaters 2 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, 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 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 2014, received 11765, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 6, free buffers 18 (min 17), ts 1044/1043/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 47.89ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active Module is providing access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta4 MAC address ea:68:e7:e5:63:f4 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 40124 WiFi IP address 192.168.1.10 Connected clients 1 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0M122 B1
5/27/2023, 7:53:05 AM M122 B1 Diagnostics for board 1: Duet EXP3HC rev 1.02 or later firmware version 3.5.0-beta.3 (2023-04-13 18:42:24) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 157516, free system stack 202 words Tasks: Move(nWait,0.0%,162) HEAT(nWait,0.0%,90) CanAsync(nWait,0.0%,63) CanRecv(nWait,0.0%,79) CanClock(nWait,0.0%,70) TMC(nWait,6.1%,105) MAIN(running,92.5%,431) IDLE(ready,0.0%,40) AIN(delaying,1.3%,265), total 100.0% Last reset 00:04:01 ago, cause: software Last software reset data not available Driver 0: pos 0, 690.0 steps/mm,standstill, SG min n/a, mspos 920, reads 21635, writes 23 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 690.0 steps/mm,standstill, SG min n/a, mspos 616, reads 21636, writes 23 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 80.0 steps/mm,standstill, SG min n/a, mspos 8, reads 21647, writes 13 timeouts 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 -7/9, peak Rx sync delay 183, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 24.2, current 24.3, max 24.3 V12 voltage: min 12.3, current 12.3, max 12.3 MCU temperature: min 32.2C, current 32.4C, max 32.9C Last sensors broadcast 0x00003000 found 2 194 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 3903, send timeouts 0, received 4117, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0M122 B20
5/27/2023, 7:54:35 AM M122 B20 Diagnostics for board 20: Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.3 (2023-04-13 18:44:05) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 5012, free system stack 92 words Tasks: Move(nWait,0.0%,155) HEAT(nWait,0.3%,100) CanAsync(nWait,0.0%,57) CanRecv(nWait,0.0%,76) CanClock(nWait,0.0%,67) ACCEL(nWait,0.0%,53) TMC(delaying,3.0%,57) MAIN(running,91.6%,344) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0% Last reset 00:05:31 ago, cause: software Last software reset data not available Driver 0: pos 0, 690.0 steps/mm,standstill, SG min 14, read errors 0, write errors 1, ifcnt 111, reads 34519, writes 18, 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 -3/8, peak Rx sync delay 218, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 24.0, current 24.1, max 24.2 MCU temperature: min 27.8C, current 29.0C, max 29.1C Last sensors broadcast 0x00000312 found 4 15 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 6669, send timeouts 0, received 5659, 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 0M122 B21
5/27/2023, 7:55:03 AM M122 B21 Diagnostics for board 21: Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.3 (2023-04-13 18:44:05) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 5044, free system stack 92 words Tasks: Move(nWait,0.0%,155) HEAT(nWait,0.2%,83) CanAsync(nWait,0.0%,57) CanRecv(nWait,0.0%,76) CanClock(nWait,0.0%,67) ACCEL(nWait,0.0%,53) TMC(delaying,3.0%,57) MAIN(running,91.8%,346) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0% Last reset 00:05:59 ago, cause: software Last software reset data not available Driver 0: pos 0, 690.0 steps/mm,standstill, SG min 2, read errors 0, write errors 1, ifcnt 114, reads 48483, writes 18, 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 -3/8, peak Rx sync delay 215, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 24.3, current 24.3, max 24.5 MCU temperature: min 34.7C, current 34.8C, max 35.1C Last sensors broadcast 0x00000c08 found 3 192 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 7222, send timeouts 0, received 6129, 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 -
@RogerPodacter are you saying that using a thermistor connected to the main board to control a fan connected to the 3HC works, but using a thermocouple connected to the main board via the Duet3D thermocouple daughter board does not?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 yes precisely, that is what i thought. but now that i just looked closer, its a bit different. the H4 thermistor which is my "working" example is actually on one of the toolboards 1LC 20.temp1, not on the mainboard as i thought. so it seemed that my H4 thermistor could control a fan on a 3HC or a fan on the mainboard. however now that i am on v3.4.5, it appears that H4 is no longer working for either of them. now i'm very confused or perhaps the underlying code has changed in the new firmware.
i guess just ignore my topic at this point because i am confused. maybe there was a CAN bus thing which allowed the toolboard but not the 3HC to control over CAN bus, but none seem to work now so its ok.
my original intention was to use the daughterboard thermocouples and have TC0 control a fan on the mainboard, and TC1 control a fan on the 3HC.
-
@RogerPodacter said in Problem with Fan Settings Across 3HC and Mini 5+:
my original intention was to use the daughterboard thermocouples and have TC0 control a fan on the mainboard, and TC1 control a fan on the 3HC.
That should work, provided all boards are running firmware 3.4.2 or later.
