Duet mini+ failing to heat hotend
-
@nightlonk42
You might have a config-override in your /sys folder, which overwrites the PID settings of config.g.
The best way to store PID results, is to send M500 after the tuning and also add a M501 at the end of config.g to call the override at startup. -
@o_lampe said in Duet mini+ failing to heat hotend:
@nightlonk42
You might have a config-override in your /sys folder, which overwrites the PID settings of config.g.
The best way to store PID results, is to send M500 after the tuning and also add a M501 at the end of config.g to call the override at startup.I did not have an override but I tried this and am still getting the fault. Only thing I can think of is that I WAS using a toolboard 1.0 but upgraded to the 1.1 (built in accell) and this started happening. I also updated to version 3.3 while upgrading the toolboard... Oddest thing to me is that theres zero console errors, just faults when heating up from too far away from the target temp.
I ran another PID and inputted the results, and verified with M307 H1 and they are exactly what I put in, even after power cycling
M307 H1 Heater 1 model: heating rate 3.255, cooling time constant 211.5/80.3, dead time 6.31, max PWM 1.00, calibration voltage 28.3, mode PID Computed PID parameters: setpoint change: P8.7, I0.238, D38.4, load change: P8.7, I0.583, D38.4And just in case.....
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: LYWS8-K296U-D65J0-40KM8-2503Z-HQWMB Used output buffers: 10 of 40 (32 max) === RTOS === Static ram: 102724 Dynamic ram: 106704 of which 16 recycled Never used RAM 34260, free system stack 198 words Tasks: NETWORK(ready,15.3%,240) HEAT(delaying,0.0%,379) Move(notifyWait,0.1%,338) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,347) TMC(notifyWait,0.7%,115) MAIN(running,83.1%,426) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:09 ago, cause: software Last software reset at 2021-07-04 03:12, reason: User, GCodes spinning, available RAM 34260, slot 0 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 69179, completed 69178, timed out 0, errs 0 Step timer max interval 957 MCU temperature: min 27.3, current 27.3, max 28.7 Supply voltage: min 27.9, current 28.0, max 28.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, SG min/max 2/2, read errors 0, write errors 0, ifcnt 50, reads 2780, writes 0, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 2/2, read errors 0, write errors 0, ifcnt 50, reads 2779, writes 0, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 2/2, read errors 0, write errors 0, ifcnt 50, reads 2780, writes 0, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 39, reads 2780, writes 0, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 39, reads 2780, writes 0, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-07-04 03:14:06 Cache data hit count 129211930 Slowest loop: 4.26ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1, chamberHeaters = -1 -1 === 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. === Filament sensors === Extruder 0: no data received === CAN === Messages queued 476, received 660, lost 0, longest wait 1ms for reply type 6013, peak Tx sync delay 3, free buffers 17 (min 16), ts 264/264/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 201.11ms; fastest: 0.06ms 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 connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.26 WiFi MAC address f0:08:d1:02:b5:c4 WiFi Vcc 3.34, reset reason Power up WiFi flash size 2097152, free heap 24720 WiFi IP address 192.168.1.65 WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0``` -
@nightlonk42 can you check the firmware on the toolboard as well?
M115 B121 -
@jay_s_uk said in Duet mini+ failing to heat hotend:
M115 B121
Sure thing!
7/4/2021, 3:43:07 AM M115 B121 Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58) -
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!!!
