Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Lift Z relative to layer height #774

AxTheB opened this Issue Nov 1, 2012 · 8 comments


None yet
3 participants

AxTheB commented Nov 1, 2012

It will be great if we can set Lift Z to xx% and have the lift based on actual layer height.
Lifts then will be automatically optimal at all times - even for configurations like --layer-height=0.1 --first-layer-height=0.4 --infill-every-layers=3


alexrj commented Nov 23, 2012

That's a good idea.
I will do it after next release, and after writing some unit tests about lift to make sure we don't break anything.

@lordofhyphens lordofhyphens added this to the 1.3.0 milestone May 28, 2016


lordofhyphens commented May 28, 2016

Looking at this again, seems like we'd need a new vector version of ConfigOptionFloatOrPercent, liftZ is stored as vector (because different extruder configs).

Is this still desirable as an option (I know I use firmware retract myself).


alexrj commented Dec 21, 2016

Hm, noone else ever requested this feature... also I wonder why I thought it's a good idea. Why would the amount of Z lift change according to layer height?

@alexrj alexrj removed this from the 1.3.0 milestone Dec 21, 2016


lordofhyphens commented Dec 21, 2016


lordofhyphens commented Dec 22, 2016

That's already in the codebase though.

The other thing I can think about is maybe there was an assumption that if you did combined infill you'd somehow get into a situation where you'd knock into perimeters? The algorithm for drawing perimeters and infill though means that isn't going to happen, unless you're using combined infill and doing the infill first and you had a really small (~1 perimeter layer height) z lift.


alexrj commented Dec 22, 2016

Combined infill is printed like: perimeter --> perimeter --> infill --> perimeter --> perimeter --> infill, so the nozzle is always free in the XY plane. No collisions can ever happen...

AxTheB commented Dec 22, 2016

Well I actually fuzzily remember why I opened this issue, and I think it can be safely closed as "fixed by fixing the printer"


lordofhyphens commented Dec 22, 2016


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment