Heat bed turning on too early on 3.5.0-rc3

wschadow

When starting a print start.g is executed and basically doing homing and calling bed.g, where the true mesh bed leveling is done. In 3.5.0-rc3 the heatbed is tuning on already at this point. It looks like part of the print gcode is executed already, while startt.g / bed.g are still running.

This happens on Duet3Mini5+ and Duet2. I checked 3.4.6 as well which works correctly.

dc42

@wschadow I think you will find this is fixed in the latest 3.5 firmware at https://www.dropbox.com/scl/fo/yzchzlyxmxlzywjawqflu/h?rlkey=tl7dfs75yozhfgpze0jnkn32n&dl=0.

wschadow

@dc42 thanks, for the quick fix, tested on two machines.

wschadow

@dc42 I noticed some other strange thing, which is maybe related: my start.g and bed.g turn the heaters off via

M568 P0 S0 R0 A0                                                       ; turn tool 0 off
M568 P1 S0 R0 A0                                                       ; turn tool 1 off
M568 P2 S0 R0 A0                                                       ; turn tool 2 off

and the beginning. No other temperature related settings. When starting the print on 3.4.6 I see

then

while true meshbed leveling: This happens in 3.5.0-rc3+4 as well. On 3.5.0-rc3+4 even after the print I can see

. My stop.g contains the lines

M568 P0 S0 R0 A0                                                       ; turn tool 0 off
M568 P1 S0 R0 A0                                                       ; turn tool 1 off
M568 P2 S0 R0 A0                                                       ; turn tool 2 off

as well.

dc42

@wschadow I suspect DWC is reporting the tool state, not the heater state. The tool state is copied to the heater state when you release the tool or switch to the tool, but you can subsequently override it using M568, until the tool is next selected or freed.