3.5.0-b2: Bed shut off during print

CCS86

I just updated from beta1 to beta2 and ran a print job I have ran many times before.

Everything started normally, the bed heated, probed, and began printing. But then shortly after I heard the noise of my prints coming loose and came back to find the bed at idle temp. No errors that I can see. It just turned off.

Here is the console of that print and an M122 after cancelling it. Still not sure what happened:

2/10/2023, 7:11:58 AM	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.5beta2 (2023-02-08 17:43:40) running on Duet Maestro 1.0
Board ID: 08DJM-956DU-LLMS4-7J9F6-3SN6Q-KBM2Q
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 22148
Dynamic ram: 70368 of which 0 recycled
Never used RAM 19268, free system stack 160 words
Tasks: NETWORK(ready,51.0%,229) ACCEL(notifyWait,0.0%,349) HEAT(notifyWait,1.9%,336) Move(notifyWait,6.4%,308) TMC(notifyWait,17.1%,110) MAIN(running,22.9%,496) IDLE(ready,0.8%,31), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 11:02:18 ago, cause: software
Last software reset at 2023-01-28 08:45, reason: User, Gcodes spinning, available RAM 18740, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Step timer max interval 1866
MCU temperature: min 36.1, current 36.9, max 42.7
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/3, heap memory allocated/used/recyclable 2048/288/256, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, read errors 0, write errors 1, ifcnt 67, reads 60499, writes 18, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, read errors 0, write errors 1, ifcnt 67, reads 60499, writes 18, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, read errors 0, write errors 1, ifcnt 68, reads 60498, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, read errors 0, write errors 1, ifcnt 41, reads 60505, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, read errors 0, write errors 1, ifcnt 13, reads 60511, writes 6, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-02-10 07:11:55
Slowest loop: 1499.96ms; fastest: 0.16ms
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: 10.0MBytes/sec
SD card longest read time 2.5ms, write time 159.0ms, max retries 0
=== Move ===
DMs created 83, segments created 31, maxWait 5543437ms, bed compensation in use: mesh, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 145434, completed 145434, hiccups 25, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== 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
=== Filament sensors ===
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 1499.71ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
2/9/2023, 10:40:49 PM	M0
Cancelled printing file 0:/gcodes/Cold Plunge/Filter-Plug2 x12 315.gcode, print time was 0h 53m
2/9/2023, 10:40:47 PM	Printing paused at X102.6 Y35.0 Z1.4
2/9/2023, 10:40:44 PM	M25
Resume state saved
2/9/2023, 9:52:36 PM	225 points probed, min error -0.016, max error 0.066, mean 0.028, deviation 0.017
Height map saved to file 0:/sys/heightmap.csv
2/9/2023, 9:47:27 PM	M32 "0:/gcodes/Cold Plunge/Filter-Plug2 x12 315.gcode"
File 0:/gcodes/Cold Plunge/Filter-Plug2 x12 315.gcode selected for printing

T3P3Tony

@CCS86 are there commands in the print file that could impact this? Is it repeatable, as in does it happen at the same point in a print?

CCS86

@T3P3Tony said in 3.5.0-b2: Bed shut off during print:

@CCS86 are there commands in the print file that could impact this? Is it repeatable, as in does it happen at the same point in a print?

I don't see any commands. No M140 or M190 after my start gcode.

I'm running a quick test print right now and no issue so far.

After it's done, I'll run the same print job that failed.

CCS86

The issue has not repeated. Hopefully, it was just a fluke.

CCS86

Well, after many successful prints, it just happened again.

feet2.gcode

edit:

I may have just figured out the cause. If I select the file for print. Then, I cancel it, obviously it shuts off the heaters. Then I select "print again", it never reestablishes the bed heater. I have a conditional clause for my bed temp, that basically just asserts a longer dwell for stabilization if the bed was cold. But for either condition, it issues an M190.

dc42

@CCS86 regarding this:

if heat.heaters[0].current < 60-1
	M190 R60                                ; Wait for cold bed
	G4 S240                                 ; Cold Pause
else M190 R60                               ; Wait for hot bed      <<<<<<<
	G4 S1                                  ; Hot Pause

The M190 command with the "Wait for hot bed" comment wil be ignored because it needs to be on a separate line, not on the same line as the 'else'. I will change the parser to generate an error message when there are unexpected characters after 'else'.

CCS86

@dc42 said in 3.5.0-b2: Bed shut off during print:

@CCS86 regarding this:
if heat.heaters[0].current < 60-1
	M190 R60                                ; Wait for cold bed
	G4 S240                                 ; Cold Pause
else M190 R60                               ; Wait for hot bed      <<<<<<<
	G4 S1                                  ; Hot Pause
The M190 command with the "Wait for hot bed" comment wil be ignored because it needs to be on a separate line, not on the same line as the 'else'. I will change the parser to generate an error message when there are unexpected characters after 'else'.

Great, thank you for that correction!