Skip to content
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 still is not saving #32

Open
JozephSchmoe opened this issue Jul 4, 2024 · 1 comment
Open

Z offset still is not saving #32

JozephSchmoe opened this issue Jul 4, 2024 · 1 comment

Comments

@JozephSchmoe
Copy link

Running "Set Z-offset" or "Auto Bed Leveling" on the X-Plus 3 does not save. Factory reset twice. Please tell us where in the config to store this value. I avoided this firmware for months due to this known, unresolved issue. As it is unresolved, what is the workaround?

@CChen616
Copy link
Contributor

CChen616 commented Jul 4, 2024

For the Max3 Plus3 series machines, the Z offset value is stored in the config.mksini file under the babystep section.
image

When the machine detects a connection to Klipper, it reads the value from the file and uses the command SET_GCODE_OFFSET Z={z offset} MOVE=0 to apply the Z offset value to Klipper's runtime variable, gcode offset. You can see this on the Fluidd interface.

image

When Klipper restarts, the variable is reset. Generally, the machine detects Klipper reconnecting and sends the command. However, if Moonraker has been restarted, it might cause the system to lose the connection to Klipper, and the command won't be sent when Klipper starts up. Power off and on the printer can get the connection back.

If there's an error in the mksini file, it can also lead to a failure in reading the Z offset. A proper configuration file looks like this:

image

Factory reset will reset the config.mksini file.

The above explanation assumes operations are performed using only the screen. To avoid conflicts, the Klipper file has been modified so that after running PROBE_CALIBRATE, the saved offset value in printer.cfg will be zero.

We apologize for any inconvenience this has caused. The design of the early system had some flaws, we will work to optimize this logic and include updates in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants