[FEATURE REQUEST] New Gcode to set the minimum safe Z height for crash detect rehome.

[ggppjj]

Please, before you create a new feature request, please make sure you searched in open and closed issues and couldn't find anything that matches.

If it makes sense, enter what type of printer or upgrade the feature request applies to.
Printer type - MK3S+
MMU Upgrade - MMU2

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I was printing an MMU print with no sparse layers enabled, and had a crash detect on the wipe tower after it was lower than the printed object in the bottom left of the build plate. It entered a crash detect loop after incorrectly rehoming against the print.

Describe the solution you'd like
A clear and concise description of what you want to happen.
A Gcode that allows the slicer to inform the printer of the minimum safe z-height for rehome would allow the printer to rehome correctly when objects are printed individually.

[mmalecki]

I've also ran into this problem. Another approach I've pondered is recording maximum Z-height visited during print, and then moving to that + MMU pause Z-lift, but there doesn't appear to be a clean way to approach that.

Alternative solution that could work, that doesn't involve custom Gcode, would be to implement G60 and G61 (save and restore position). After layer change, we'd then G60 S0 (save position in slot 0), and on MMU error, before moving to MMU pause position, we'd G61 S0 Z (move to saved position in slot 0, limited to Z axis).

[mmalecki]

I hacked this together. Will test it over the coming days - initial test was a failure (print didn't resume after MMU OK), but I think the idea may be sound.
Edited to add: second test was a failure as well, with the same failure mode. I've yet to compare to just MK3 branch - it could be something there, and not my patch, but I doubt it.

[Prusa-Support]

Hello! Thank you @ggppjj for the request and @mmalecki for sharing the possible solution for this. I brought this to our devs attention, so that they can further review and evaluate this. We'll update here in case of more info from our side - of course, any more feedback anyone might have is absolutely welcome and appreciated!

Alessandro Pantaleo
Prusa Research

[ggppjj]

Thank you Alessandro!

It is my hope that this can be evaluated for inclusion on the still-forming 3.13.0 milestone, I am of the opinion that it would be a nice polish to an otherwise excellent feature that would fit nicely into the overall theme of MMU fixes that 3.13.0 appears to target, and also have the added benefit of shoring up the "print objects individually" functionality and could more reliably allow print farm operators to keep automatic crash detection enabled for example (although I admit that the last point is only a hypothetical on my part, not operating or working with anyone operating a print farm myself or knowing their settings preferences).

[github-actions]

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

[3d-gussner]

@gudnimg Please have a look at this feature request and the approach by @mmalecki #3419 (comment)