Printer don't heat after longer in IDLE state 3.4b7+1

SIam

Hi,

I have an issue with firmware RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta7+1 (2021-12-22) when I'm printing one job at a time i have no problem but when the printer stays in idle mode for a longer time I can't heat up the bed / hotend. The only thing which helps is to reset the Printer.
Here you can see the issue in this small video: https://kleinersonnenschein.eu/video/heatingproblem.mp4

and in the second video, you can see what's happens when I start a print job:
https://kleinersonnenschein.eu/video/startjob.mp4

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta7+1 (2021-12-22 18:48:09) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-95BNL-MGPSJ-6J9FD-3SJ6N-K1W3Y
Used output buffers: 3 of 24 (14 max)
=== RTOS ===
Static ram: 23804
Dynamic ram: 76772 of which 40 recycled
Never used RAM 8008, free system stack 102 words
Tasks: NETWORK(ready,35.0%,228) ACCEL(notifyWait,0.0%,348) HEAT(notifyWait,3.0%,311) Move(notifyWait,16.0%,275) DUEX(notifyWait,0.0%,24) MAIN(running,42.5%,440) IDLE(ready,3.5%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 10:18:11 ago, cause: power up
Last software reset at 2022-01-06 18:53, reason: User, GCodes spinning, available RAM 8296, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 15.0, current 31.2, max 32.2
Supply voltage: min 24.0, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/1204/1204, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 31520, standstill, SG min 0
Driver 1: pos -15680, standstill, SG min 0
Driver 2: pos 12447, standstill, SG min 0
Driver 3: pos 0, standstill, SG min 0
Driver 4: pos 0, standstill, SG min 0
Driver 5: pos 0, standstill, SG min n/a
Driver 6: pos 0, standstill, SG min 0
Driver 7: pos 0, standstill, SG min n/a
Driver 8: pos 0, standstill, SG min n/a
Driver 9: pos 0, standstill, SG min n/a
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2022-01-07 22:13:59
Cache data hit count 4294967295
Slowest loop: 149.89ms; fastest: 0.11ms
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 10.8ms, write time 8.5ms, max retries 0
=== Move ===
DMs created 83, segments created 25, maxWait 32247376ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 15146, completed 15146, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 12], 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 -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = nan
Heater 1 is on, I-accum = nan
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== DueX ===
Read count 1, 0.00 reads/min
=== Network ===
Slowest loop: 153.15ms; 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 connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 2c:3a:e8:0b:06:33
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22960
WiFi IP address 192.168.188.142
WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0

I was playing around with the accelerometer and my printer suddenly restarted. here is the result of the m122 after the software crash

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta7+1 (2021-12-22 18:48:09) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-95BNL-MGPSJ-6J9FD-3SJ6N-K1W3Y
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23804
Dynamic ram: 76708 of which 40 recycled
Never used RAM 11528, free system stack 184 words
Tasks: NETWORK(ready,10.8%,232) ACCEL(notifyWait,0.0%,348) HEAT(notifyWait,0.0%,336) Move(notifyWait,0.0%,364) DUEX(notifyWait,0.0%,24) MAIN(running,85.1%,442) IDLE(ready,4.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:23 ago, cause: software
Last software reset at 2022-01-07 23:54, reason: HeatTaskStuck, GCodes spinning, available RAM 8008, slot 1
Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200123cc Task ACCE Freestk 324 ok
Stack: 0045ce93 0045da14 010f0000 00000000 40900d60 369dc3a0 3edc7360 3331bb4c 40000000 b5ddc655 388ab355 3f000000 3f000000 486c9be0 3f800000 43818000 4354c416 44800000 3f838000 00000000 2000ce3c 20011d70 20011d70 00000001 0045a527 44000000 00434863
Error status: 0x00
Step timer max interval 0
MCU temperature: min 32.0, current 33.1, max 34.7
Supply voltage: min 24.2, current 24.3, max 24.5, 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: 0 queued, 0 completed
Driver 0: pos 0, standstill, SG min n/a
Driver 1: pos 0, standstill, SG min n/a
Driver 2: pos 0, standstill, SG min n/a
Driver 3: pos 0, standstill, SG min n/a
Driver 4: pos 0, standstill, SG min n/a
Driver 5: pos 0, standstill, SG min n/a
Driver 6: pos 0, standstill, SG min n/a
Driver 7: pos 0, standstill, SG min n/a
Driver 8: pos 0, standstill, SG min n/a
Driver 9: pos 0, standstill, SG min n/a
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2022-01-07 23:54:42
Cache data hit count 850927046
Slowest loop: 27.28ms; fastest: 0.19ms
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 2.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== DueX ===
Read count 1, 2.57 reads/min
=== Network ===
Slowest loop: 80.81ms; 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 connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 2c:3a:e8:0b:06:33
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23128
WiFi IP address 192.168.188.142
WiFi signal strength -53dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Alex.cr

@SIam Similar problem but mine is on a Duet 3 platform.

@dc42 I can confirm a similar issue. In my case I have a 6HC+3HC+1LC. The only board effected is the 1LC. I am getting the exact same behavior as described above, except that a reset will not solve the problem.
I can check with and M105 and everything will show correct, but my hotend on the 1LC will not heat. I get the same behavior from Beta7, 7+1, and 7+2. I do not see this issue running Beta6.

In my case the only way to fix the problem is to use an M303 command to get the heater running above idle. Then I perform a reset and can send the heating commands as usual and everything will work.

With the 1LC heater on and commanded to reach 150C (heater 1):
M105

M105
T:19.5 /150.0 T0:19.5 /150.0 B:21.8 /0.0

M122 commands
6HC

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7+2 (2021-12-30 17:36:30) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S4-6J1FD-3SJ6T-TB6QH
Used output buffers: 1 of 40 (28 max)
=== RTOS ===
Static ram: 150728
Dynamic ram: 97576 of which 20 recycled
Never used RAM 98628, free system stack 130 words
Tasks: NETWORK(ready,24.5%,229) ETHERNET(notifyWait,0.1%,165) HEAT(notifyWait,0.0%,324) Move(notifyWait,0.0%,248) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,338) CanClock(delaying,0.0%,339) TMC(notifyWait,7.6%,58) MAIN(running,67.7%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 10:28:49 ago, cause: software
Last software reset at 2022-01-07 13:17, reason: User, GCodes spinning, available RAM 99708, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 148
MCU temperature: min 23.8, current 24.5, max 25.1
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/43, heap memory allocated/used/recyclable 2048/1702/810, gc cycles 4770
Events: 0 queued, 0 completed
Driver 0: pos 71120, standstill, SG min n/a, mspos 260, reads 35308, writes 0 timeouts 0
Driver 1: pos -39120, standstill, SG min n/a, mspos 612, reads 35308, writes 0 timeouts 0
Driver 2: pos 14440, standstill, SG min n/a, mspos 120, reads 35307, writes 0 timeouts 0
Driver 3: pos 0, standstill, SG min n/a, mspos 200, reads 35307, writes 0 timeouts 0
Driver 4: pos 0, standstill, SG min n/a, mspos 840, reads 35307, writes 0 timeouts 0
Driver 5: pos 0, standstill, SG min n/a, mspos 776, reads 35308, writes 0 timeouts 0
Date/time: 2022-01-07 23:46:43
Slowest loop: 3.71ms; fastest: 0.07ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 36, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 82403, completed 82403, 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
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122 " 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 doing "G4 P1000 " 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 1743, received 6970, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 362, free buffers 50 (min 50), ts 968/968/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 3.69ms; 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

1LC M122

M122 B20
Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7+1 (2021-12-22 18:45:45)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2540, free system stack 2745 words
Tasks: Move(notifyWait,0.0%,99) HEAT(notifyWait,0.4%,93) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.6%,351) IDLE(ready,0.0%,26) AIN(delaying,5.0%,142), total 100.0%
Last reset 10:29:35 ago, cause: power up
Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 0
Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task  Freestk 129 bad marker
Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7
Driver 0: pos 778167, 406.0 steps/mm,standstill, SG min 2, read errors 0, write errors 0, ifcnt 13, reads 21326, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 77807, completed 77807, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 5/16, peak Rx sync delay 213, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.2, current 24.2, max 24.2
MCU temperature: min 33.7C, current 38.8C, max 67.1C
Last sensors broadcast 0x00000004 found 1 15 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 6135, send timeouts 0, received 3971, 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 0, other errors 0

Fred-Y

This is the same error we reported here: https://forum.duet3d.com/topic/26463/bed-heater-stops-working-after-being-idle-for-some-time

For me it is happening on both Duet 2 wifi and Duet 3 Mini 5+; I'm pretty sure it was not always both heaters (Bed & hotend).
I don't remember having the issue on b6.

MikeDC

Its also happening to me with firmware Beta7+2 using duet3 + 3HC

I just finished one print job, loaded up another, had a cup of coffee and then clicked start.

20 mins later it still wasnt started and the bed was cold yet the print status was in printing state

kr15_uk

Same here, after one print is done I can not heat up hotend nor bed (from drop down menu and/or sending M104/M140)

Duet 2 WiFi fw3.4b7

Quite convinced I didn't had this issue with fw3.4b6, to confirm this I've downgraded now and will print a thing or too. Will report back.

Also I'll upgrade my Duet 2 Ethernet tomorrow or so and see if that's the case with Ethernet variant too.

dc42

All those of you experiencing this issue, please can you answer the following:

Does this issue only occur after you have done a print and then left the machine idle for some time?
Does it affect the bed heater, the tool heater, or both?
How does your GCode print file end? In particular:

Does it turn off the bed heater using M140 ?
Does it turn off the tool heater(s) using M104 ? Or does it set the temperatures low using G10? Or neither?
Does it use M0 ?

What (if anything) do you have in your stop.g file?

MikeDC

@dc42

no, it has happened to me if i have left the printer on for a long time without printing and it has happened after a print if left powered on for a long time before starting a 2nd print
its only affected the bed heater for me
end g-code
M122 ; debug following print
M104 S0
M140 S0
;Retract the filament
G92 E1
G1 E-10 F50
G28 X0 Y320
my stop.g

G91                       ; relative moves
M140 S0                   ; turn off bed
M106 S0                   ; part cooling fan off
G1 E-1 F300               ; retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+10.0 E-2              ; move Z up a bit and retract filament even more
M104 S0
G28 X0                    ; move X to min endstops, so the head is out of the way
G90
G1 Y300 F2000
M84                       ; steppers off
M42 P2 S0                 ; set heatbed contactor off
M300 P300 S4000           ; play beep sound

Also,
I have a macro to turn on off my heatebed contactor, even turning the heatebed contactor off/on with m42 it still will not heat the bed.
i have to power off/on the machine.

SIam

@dc42 said in Printer don't heat after longer in IDLE state 3.4b7+1:

Does this issue only occur after you have done a print and then left the machine idle for some time?

Yes, but I have to say that I don't have tested it without a print this I can do today I will post the result this evening

Does it affect the bed heater, the tool heater, or both?

in my case, Both

How does your GCode print file end? In particular:

G90 ; Switch to relative mode
G1 E-5 f3600 ; retrac filamnet
G91 ; Switch to absolute mode
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
G91 ; use relative coordinates
G1 Z5 F1200 H2; lift nozzle by 5mm
G90 ; use absolute coordinates
G28 X0 ; home X axis
G1 Y195 ; move Y axis to end position
M106 P0 S0 ; Bauteilkhler aus
M106 P2 S0 ; beleuchtung aus
M107 ; turn off fan

Does it turn off the bed heater using M140 ?

Yes

Does it turn off the tool heater(s) using M104 ? Or does it set the temperatures low using G10? Or neither?

Yes

Does it use M0 ?

No

What (if anything) do you have in your stop.g file?

stop.g is empty

ÖrjanE

@mikedc M140 S0 and M104 S0 will not turn the heaters off; only change the target temperature to zero. Could it be that this generates a heater fault when it fails to reach that temperature? The release notes mention that earlier versions did set the heaters to the "off"-state after a finished print while the current (beta) version does not if there is a stop.g file present.

kr15_uk

@dc42

Haven't tried to do next job earlier than 30mins after 1st finished, I'll see if I can spot next print finish to test straight away.
Both, although I haven't tried cold bed print, always both heaters are on.
Just M104 and M140 to zero, XY home and M84
This is fairly new build so it's as generic as it gets out of online configurator.

On the previous post of mine, after downgrade to 3.4.0b6 on Duet 2 WiFI it works fine and 3.4.0b7 Duet 2 Ethernet has the same issue.

Ta

Kris

SIam

@dc42 My printer was 9 hours in idle state without a print job and the heating works

Alex.cr

@dc42

Basically, if the temp of the hot end goes below 18C or so. If I remove power for 24+ hours and then fire the machine up it will occur.
Mine just effects my hot end on my 1LC. My bed heater on my 6HC works fine.
Yes to all 3 questions.

4.stop.g

G1 E-3.0  F1500              ; clear extruder
G91                     
G1 Z5.0  F20000               ; move Z from part
G90
M104 S0 		; Extruder heater off
M140 S0 		; Bed heater off
M141 S0         ; Chamber heater off
M106 P3 S0      ;turn off lights
M106 P2 S0      ;turn off MCU fans
M106 P0 S0      ; Turn part fan off
M106 P6 S0 ; turn off Nevermore fan

M220 S100		; Set speed factor back to 100% in case it was changed
M221 S100		; Set extrusion factor back to 100% in case it was changed

M98 P"/macros/print_scripts/goto_bucket.g"    ;go to park position over bucket

MikeDC

I finished a long print around 3 hours ago today and left the printer idle afterwards.
I have just tried another print,
My main contactor does switch on but the bed is not heating.
i cancelled the print and thought i would do a couple of tests.
I can heat the nozzle manually and disable the nozzle heater
I have full control of it from both paneldue and dwc

the bed heater no control on temperature
i can manually turn the contactor on and off both by the paneldue and dwc
i can appear to enable / disable the bed heater
but it just doesnt heat up.

Only a full power reset will allow it to work again

dc42

@mikedc This is fixed in 3.4.0beta7+4, see https://forum.duet3d.com/topic/26787/unofficial-rrf-3-4-0beta7-2-files.

MikeDC

@dc42
is this a different b7+2 to what i am on ?
I used b7+2 to fix the z on expansion card issue but i still have this issue with bed not heating up after idle

jay_s_uk

@mikedc yes. the latest builds on that thread are now 3.4b7+5

MikeDC

@dc42
ahh now b7+4 thankyou :)))

I will install after my print has finished

SIam

@dc42 It looks good ! Thanks for fixing this issue

bastien

for me, b7+4 don't resolve problem

Fred-Y

@bastien New version have been published since b7+4, I believe the last one is +7
I don't remember having this error lately.

You should be able to download b7+7 from here:
https://forum.duet3d.com/topic/26787/unofficial-rrf-3-4-0beta7-4-files/17?_=1642785164011
Need to scroll to get the link.