Error: Heater 1 fault: exceeded allowed, when cold booting
-
Every time I star my printer, I get this message:
"Event Notification"
"Heater 1 fault: exceeded allowed temperature excursion: target 220.0°C actual 53.0°C"After I close the message and reset the nozzle heater everything is as expected.
Duet 2 WiFi 2.5.1
DWC 3.5.1M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SD-6J9DL-3S46N-1TNRM Used output buffers: 1 of 26 (14 max) === RTOS === Static ram: 23256 Dynamic ram: 73344 of which 12 recycled Never used RAM 16532, free system stack 184 words Tasks: NETWORK(1,ready,13.7%,220) HEAT(3,nWait 5,0.1%,280) Move(4,nWait 5,0.0%,359) MAIN(1,running,85.9%,743) IDLE(0,ready,0.2%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:06:51 ago, cause: power up Last software reset at 2024-10-20 20:26, reason: User, Gcodes spinning, available RAM 14088, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 24.2, current 30.3, max 30.6 Supply voltage: min 11.6, current 11.8, max 12.3, 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 Events: 1 queued, 1 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-11-06 06:17:17 Cache data hit count 4294967295 Slowest loop: 12.22ms; fastest: 0.18ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === 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 -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Network === Slowest loop: 15.71ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 1.26 MAC address dc:4f:22:6e:70:65 Module reset reason: Turned on by main processor, Vcc 3.37, flash size 4194304, free heap 25088 WiFi IP address 192.168.10.151 Signal strength -44dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@TomasL best post your config.g
-
@jay_s_uk
Here they are
config (1).g -
The M307 values in your config.g are quite different from those in config-override.g.
when did you last tune the heaters? And how did you save the results?
-
@Phaedrux
Tuned them them with M303 a couple of weeks ago and M500 to save -
@TomasL said in Error: Heater 1 fault: exceeded allowed, when cold booting:
Every time I star my printer, I get this message:
"Event Notification"
"Heater 1 fault: exceeded allowed temperature excursion: target 220.0°C actual 53.0°C"Do you mean when you start a print, or when the printer powers up?
-
@Phaedrux Turned on, or reset
-
What does your temp graph actually show?
