-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
ChangeAtZ - Fix #8574 and #8886 #21316
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
base: main
Are you sure you want to change the base?
Conversation
…not properly apply (or change back) certain values. Z targeting now works by determining the target layer based on the minimum Z for a given layer. Added support for layer and Z ranges. Added support for reading layer height from project settings. Kept backwards compatibility with older configs of ChangeAtZ.
|
@novamxd could you take a look at the current "TweakAtZ". The thought was to obsolete "Change At Z" in due time. It was left in Cura as project files might include it. Tweak at Z currently has "Start/End layers" and "Start/End heights. If you could see if your changes can apply to Tweak At Z it would be helpful. |
Hey @GregValiant I already saw TweakAtZ. Personally I'm disappointed it exists and is the reason I decided to push my changes through. There is and was nothing preventing you from updating the existing ChangeAtZ plugin to support the new features without breaking backwards compatibility, and yet you chose otherwise. Now customers of Cura are left with old projects that won't work right requiring a migration and any existing tutorials or documentation now invalid. This was a terrible decision, in my opinion. If anything I will slowly port the TweakAtZ functions missing from ChangeAtZ into ChangeAtZ, making TweakAtZ no longer required. I hope this clarifies! |
|
I started out updating Change at Z but when I got finished it was very different. Tweak at Z has the same (I think) functionality, but it is 700 lines of code shorter and it is WAY faster. I thought one of the problems with Change At Z was the way speed changes were handled. Using M220 affects any speed. I went a different way and adjusted the individual speed "F" parameters in the Gcode. That allows Print, Travel, Retract/Prime, and Z-hop speeds to be handled separately. The fan commands were no longer needed as "Advanced Cooling Fan Control" covered that. The settings for Change At Z just didn't fit well anymore and a project that called Change at Z could well have had "unexpected consequences". |
Description
Type of change
How Has This Been Tested?
I pulled the file given by GhostKeeper (here) and validated that it properly targets the expected heights. Also tested ranges with this file.
I also pulled the 25x25 Cube given by AbeFM (here) and that the fan speed is properly switched back to 30% after the desired layer.
Test Configuration:
Checklist:
25x25Cube (1).zip
change_at_z_temperature (1).zip