Duet mini+ failing to heat hotend
-
Can you use M500 to save the PID results and then post your config-override.g so we can see what values it has saved?
What command are you using to PID tune?
-
M303 T0 S205 is what I'm using for the hotend.
I wiped the override, ran another PID, saved the values in config file, restarted the board, then did a M500.
[19_1625425463232_tpre0.g](Uploading 100%) [18_1625425463232_tpost0.g](Uploading 100%) [17_1625425463232_tfree0.g](Uploading 100%) [16_1625425463231_stop.g](Uploading 100%) [15_1625425463231_sleep.g](Uploading 100%) [14_1625425463231_retractprobe.g](Uploading 100%) [13_1625425463231_resume.g](Uploading 100%) [12_1625425463230_pause.g](Uploading 100%) [11_1625425463230_homez.g](Uploading 100%) [10_1625425463230_homey.g](Uploading 100%) [9_1625425463230_homex.g](Uploading 100%) [8_1625425463230_homeall.g](Uploading 100%) [7_1625425463229_heightmap.csv](Uploading 100%) [6_1625425463229_dwc-settings.json](Uploading 100%) [5_1625425463229_DuetWiFiServer.bin](Uploading 100%) [4_1625425463229_deployprobe.g](Uploading 100%) [3_1625425463228_config-override.g](Uploading 100%) [2_1625425463228_config.g.bak](Uploading 100%) [1_1625425463228_config.g](Uploading 100%) [0_1625425463228_bed.g](Uploading 100%)
; config-override.g file generated in response to M500 at 2021-07-04 14:58 ; This is a system-generated file - do not edit ; Heater model parameters M307 H0 R0.374 C501.700:501.700 D18.02 S1.00 V28.0 B0 I0 M307 H1 R3.255 C211.500:80.300 D6.31 S1.00 V28.3 B0 I0 ; Workplace coordinates G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00 -
@nightlonk42 said in Duet mini+ failing to heat hotend:
I wiped the override, ran another PID, saved the values in config file, restarted the board, then did a M500.
You must send M500 immediately after the PID tuning completed, not after restarting the board.
-
@phaedrux said in Duet mini+ failing to heat hotend:
@nightlonk42 said in Duet mini+ failing to heat hotend:
I wiped the override, ran another PID, saved the values in config file, restarted the board, then did a M500.
You must send M500 immediately after the PID tuning completed, not after restarting the board.
I'll try that. One moment
(Sorry about the weirdness on the post above. I was trying to upload all the files and it marked it as spam and won't let me edit it anymore)
-
@nightlonk42 said in Duet mini+ failing to heat hotend:
[5_1625425463229_DuetWiFiServer.bin]
It probably didn't like the bin file either.
-
Tuning complete and M500 put in right after. I'll let it cool off and try again.
I enabled M929 as well to see if it catches anything. If nothing shows, and if it's still happening, I'll put it into debugging (M111) and see if I can catch what's happening.
Thank you so much for your help so far! Very much appreciated!
I'll post when I have new results
New override:
; config-override.g file generated in response to M500 at 2021-07-04 15:16 ; This is a system-generated file - do not edit ; Heater model parameters M307 H0 R0.374 C501.700:501.700 D18.02 S1.00 V28.0 B0 I0 M307 H1 R3.254 C281.751:107.008 D6.43 S1.00 V28.3 B0 I0 ; Workplace coordinates G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00 -
Heater still faulting. Event log not giving any info. I'll hardwire into it and run debugging to see if I can catch anything.
Only other thing I can think of is the board is bad somehow or it's an issue with 3.3. If I can't catch anything hooked directly in I'll try to downgrade everything to 3.2.2
power up + 00:00:01 [info] Event logging started at level debug power up + 00:00:01 [info] Running: Duet 3 Mini5plus WiFi: 3.3 (2021-06-15 21:46:11) power up + 00:00:01 [warn] Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 212C power up + 00:00:01 [warn] Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 941C power up + 00:00:01 [info] G10 L2 P1 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P2 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P3 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P4 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P5 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P6 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P7 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P8 X0.00 Y0.00 Z0.00 power up + 00:00:01 [info] G10 L2 P9 X0.00 Y0.00 Z0.00 power up + 00:00:01 [debug] Done! power up + 00:00:01 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:01 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point AdventurousPanda, IP address 192.168.1.65 power up + 00:00:08 [warn] HTTP client 192.168.1.115 login succeeded 2021-07-04 15:26:00 [warn] Date and time set at power up + 00:00:08 2021-07-04 15:26:52 [info] G10 P0 S220 -
Downgraded to 3.2.2, same thing.
Ran debugging to USB with all settings enabled, nothing shows up when it faults
-
@nightlonk42 said in Duet mini+ failing to heat hotend:
M563 P0 S"Hemera" D0 H1 F0:2
Are fans 0 and 2 both part cooling fans? Your fan definition says that fan2 is a cpu fan. So maybe you should change F0:2 to just F0.
Can you try tuning the hotend with M303 H1 S205 instead of T0?
@nightlonk42 said in Duet mini+ failing to heat hotend:
Supply voltage: min 27.9, current 28.0, max 28.1,
Also I think you may be over volting your heaters
-
@phaedrux said in Duet mini+ failing to heat hotend:
@nightlonk42 said in Duet mini+ failing to heat hotend:
M563 P0 S"Hemera" D0 H1 F0:2
Are fans 0 and 2 both part cooling fans? Your fan definition says that fan2 is a cpu fan. So maybe you should change F0:2 to just F0.
Can you try tuning the hotend with M303 H1 S205 instead of T0?
@nightlonk42 said in Duet mini+ failing to heat hotend:
Supply voltage: min 27.9, current 28.0, max 28.1,
Also I think you may be over volting your heaters
Made the CPU fan change, lowered voltage back down to 24v and testing again using H1.
Will update with results
-
@phaedrux said in Duet mini+ failing to heat hotend:
@nightlonk42 said in Duet mini+ failing to heat hotend:
M563 P0 S"Hemera" D0 H1 F0:2
Are fans 0 and 2 both part cooling fans? Your fan definition says that fan2 is a cpu fan. So maybe you should change F0:2 to just F0.
Can you try tuning the hotend with M303 H1 S205 instead of T0?
@nightlonk42 said in Duet mini+ failing to heat hotend:
Supply voltage: min 27.9, current 28.0, max 28.1,
Also I think you may be over volting your heaters
That did it! I'm not sure if it was the CPU fan setting or running it with H1 but it's working as expected now.
Thank you so much! This was driving me crazy for days now!!!
