SAVE_Z_OFFSET always saves to beacon model offset
Machine Info: V-Core 4 400 IDEX
I am trying to calibrate my z offset as my first seems to be slightly off. I decided to recalibrate my beacon following the steps listed here: https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/beacon_contact.md
The only step I did not do is step 5 (scan compensation).
I get to step 6 and print the the first layer test strip. I babystep the z until I have a good first layer. Then while the print is still going I type SAVE_Z_OFFSET into the console and hit enter. I then get a console message stating that the beacon model offset has been updated with the new value. However, it has not been updated (not in printer.cfg at least).
From what I've read (which may be wrong), after I have done the thermal expansion calibration, any z offset should be calculated into the expansion coefficient (as long as I have used SAVE_Z_OFFSET by typing it into the console).
However, I can't seem to make that happen no matter what I do. Any help would be greatly appreciated.
I am trying to calibrate my z offset as my first seems to be slightly off. I decided to recalibrate my beacon following the steps listed here: https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/beacon_contact.md
The only step I did not do is step 5 (scan compensation).
I get to step 6 and print the the first layer test strip. I babystep the z until I have a good first layer. Then while the print is still going I type SAVE_Z_OFFSET into the console and hit enter. I then get a console message stating that the beacon model offset has been updated with the new value. However, it has not been updated (not in printer.cfg at least).
From what I've read (which may be wrong), after I have done the thermal expansion calibration, any z offset should be calculated into the expansion coefficient (as long as I have used SAVE_Z_OFFSET by typing it into the console).
However, I can't seem to make that happen no matter what I do. Any help would be greatly appreciated.
GitHub
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - HelgeKeck/RatOS
Solution
No, it's during the first layer. If you end up having to adjust your g-code z_offset so that it's below zero, that's a strong indication that something most likely went wrong. It can be as simple as a dirty or loose nozzle or something more complex like your z couplers (the ones that couple the leadscrew to the motor shaft) aren't tight enough and thus your Z movements are inaccurate.





