@hugsy thx, good to confirm that it's normal behaviour. I'll try replacing G28 with M98 P"homeall.g" in my standard print startup code

Hi all,
I had the idea of using "if" clauses in "homeall.g" to skip homing if all the axes are already homed. I thought it'll be a no-brainer, but it appears that triggering G28 alone resets {move.axes[].homed}, before it even gets to execute any user-defined gcode(?)

This is on 3.4.0beta4, duet2 wifi, cartesian FDM - but I suspect it's just a fundamental feature of how G28 is implemented?

My goal is to make running subsequent print jobs on an "already initialised" printer faster, skipping homing/levelling. Are there any "idiomatic" takes on doing this on a duet?

Oh... I just realised that instead of having the "if" in homeall.g I could place it in my slicer gcode preamble instead, wrapping the G28 call there. Would that be the best I could do?