-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Z Offset is not saved/applied correctly in printer.cfg #1758
Comments
Thanks for your bug report, but Mainsail only send the G-Code to Kipper. The calculation and config editing happens only in Klipper. So this could only be a Klipper issue. |
Are you sure it sends the correct gcode though? |
you dont upload a log or a screenshot from your console, but i think so, because you wrote, that it comment out the original offset:
but i think more it is an issue with your config file itself. klipper is very strict with the SAVE_CONFIG part in the config. if you just need help, feel free to use our discord or our discussions area. |
Ahoi! It looks like this ticket is a request for help (or similar). We use the Github Issue-Tracker only for development related This ticket will be automatically closed. Fair wind and a following sea! PS: I'm just an automated script, not a real sailor. |
If you correct the z-offset during printing, it will be saved incorrectly or not at all. If you go to + 0.005 for the z-offset, then this value is not added but subtracted. And if you go to -0.005, then this is added. Assuming you have a Z-offset on the end stop of 4.220, if you go to +0.005, it becomes 4.215, if you go to -0.005, it becomes 4.225 In other words, it leads to confusion if you adjust the z-offset during printing. In addition, if you have set the z-offset and you click Save Config after printing, this value is not saved in the printer.cfg. You have to click on Save in the Z-Offset window or enter this command in the console, then the Z-offset will also be saved in the Printer.cfg |
Thats right. you dont change the "hardware offset", because you just change the "gcode offset" and if you add your "gcode offset" to the "hardware offset", it looks wrong at the first moment, but its right. A higher endstop position is a lower nozzle.
Thats normal, because you have to click on the "save" button in the offset panel (it just execute the @TMTYD Mr. Yel told you the exact same things already on the Mainsail Discord. So please don't waste our time! We are doing all these things in our spare time! |
Ok thanks for the answer |
Mainsail Version:
v2.9.1
Browser:
Firefox
Device:
Mobile device (Phone, Tablet or similar)
Operating System:
Android
What happened?
Changed the Z offset with the UI elements either before or during a print and press "save". Then after the print finished or is canceled press save config on top of the screen (as instructed) to apply the new Z offset to the printer.cfg and to restart klipper.
After the restart the new Z offset is not applied but instead reset to 0. Starting a print again confirms this as the offset is clearly wrong during the first layer.
When looking in the (new) printer.cfg it just automatically commented out "position_endstop" of the Z axis but didn't apply a new one.
What did you expect to happen instead?
Adjust position_endstop of the Z stepper in printer.cfg to the new value.
How to reproduce this bug?
5) Look at printer.cfg -> position_endstop was commented out but no new position_endstop or other way of offest was applied.
Additional information:
I use manual bed leveling. No Probe, just endstop.
The text was updated successfully, but these errors were encountered: