3DPrinting

15583 readers

145 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful, especially when disagreeing. Everyone should feel welcome here.
No porn (NSFW prints are acceptable but must be marked NSFW)
No Ads / Spamming / Guerrilla Marketing
Do not create links to reddit
If you see an issue please flag it
No guns
No injury gore posts

If you need an easy way to host pictures, https://catbox.moe/ may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago

MODERATORS

andypiper@lemmy.world

j4k3@lemmy.world

henry_rowengartner@lemmy.world

GrayBackgroundMusic@lemm.ee

Klipper keeps deleting my Z offset instead of saving it (lemmings.world)

submitted 1 year ago by moody@lemmings.world to c/3dprinting@lemmy.world

5 comments fedilink hide all child comments

Every time I use calibrate_probe, I get the message "The SAVE_CONFIG command will update the printer config file with the above and restart the printer."

When I click Save Config, it restarts the firmware, and then I get the warning "Option 'z_offset' in section 'bltouch' must be specified."

If I go check my printer.cfg, the [bltouch] section now has z_offset commented out with the old value and I have to remove the comment and copy in the new value.

Am I missing something? What am I doing wrong?

you are viewing a single comment's thread
view the rest of the comments

[–] fhein@lemmy.world 2 points 1 year ago

Any possibility that you've accidentally modified something in the automatically generated part of the config, so its failing to read the saved value? Perhaps you could attach your entire printer.cfg?