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

Unable to home after latest klipper update #179

Closed
greatguitartist opened this issue Jan 24, 2025 · 2 comments
Closed

Unable to home after latest klipper update #179

greatguitartist opened this issue Jan 24, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@greatguitartist
Copy link

What happened

I updated the Klipper service on my V-Core 3.1 running RatOS 2.0 and since then, when I try to home the printer, I get an error message "Must home axis first 0.000 0.000 7.000 [0.000]. This error message pops up no matter whether I try to home an individual axis or all axes. The only way I am currently able to home the printer is by first running the command SET_CENTER_KINEMATIC_POSITION and then running the home commands.

What did you expect to happen

The printer should home without errors without having to run SET_CENTER_KINEMATIC_POSITION

How to reproduce

Update Klipper to the latest commits, restart the printer, and try to home the printer (try a single axis or all axes). When the error is received, run macro SET_CENTER_KINEMATIC_POSITION and then try to home.

Additional information

Klippy Log:

klippy.log

Screenshot of error message:

Image

@greatguitartist greatguitartist added the bug Something isn't working label Jan 24, 2025
@greatguitartist
Copy link
Author

greatguitartist commented Jan 24, 2025

I used KIAUH to roll back to a stable version of Klipper and things are working now. The commits that I rolled back are shown below. I should not need to do this on my printer, so please let me know how this can be fixed without working around Klipper commits.

Image

@greatguitartist
Copy link
Author

Upgraded to RatOS2.1-RC3, so this issue no longer applies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant