-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't handle prints with Cura's cool_lift_head
#13
Comments
Hi @richfelker Can you attach a gcode sample file? I took an ultra quick look and from what I can tell Cura will insert a Is this correctly understood? I'm weary of adding stuff for handling special sequences because it's one of those "never ending chases" things. We could add a Best regards, |
Here is a sample: mintime_test_bad.gcode.txt Yes, it inserts Personally I'd be okay wth the "single sequence" option since I don't do any timing of multi-sequences anyway. But I think an automatic solution would be nicer here since Z-hop is a fairly widely used feature (even if lift head for cooling isn't) and knowing the precise time spent on "hops" would be useful. |
Sorry fat fingers! Didn't mean to close :) I'll implement a sequence limit, as it's a more general option people can use. Normal z hops don't show this behavior because it's dwells that cause a new sequence to be created. Successive dwells are also combined, such that each segment contains at least one move. Best regards |
Ah, would it make sense for dwells just not to cause a new sequence anyway, as they're a sort of "travel" rather than "print" move? |
The reason dwells cause a new sequence is actually mainly for temperature waits and such. The idea was that "unbounded waits" in the print start gcode would be counted outside of the "main run". I reckon we could probably separate I'd probably consider this a breaking change compared to the current behavior, so we'd need to do a major bump but that's not an issue. Let me look it over in the code, I don't think it'll be much work to change. Best regards, |
Thanks! |
Released in 2.0.0. The test file looks to give correct output, and also, wow, that's a lot of time used just waiting 😅 Best regards, |
If Cura's
cool_lift_head
(lift head when minimum layer time can't be met within minimum speed constraint) feature is enabled, the estimator treats each layer as a distinct print (due to Z motion back down after the lift). I'm not sure if the same happens with normal Z hop, but there probably should be some way to get the estimator to treat the pattern "increase in Z, no extrusion, return to original Z" as a hop (and account for time of hops) rather than as starting a new print.The text was updated successfully, but these errors were encountered: