"Must home Axis first" When trying to home after fresh 2.0.2 Install
Just updated to a fresh install of 2.0.2, made all the updates and did not have any errors in Mainsail anymore.
I verified all end stops work and axis move correctly with "SET_CENTER_KINEMATIC_POSITION", the BL-Touch failed homing (my fault: triggered at a different height by me) and I tried rehoming all axis. But whenever I try to rehome all Axis I get the error "Must home axis first: 0.000 0.000 15.000 [0.000]". Happens also after a restart.
I also added my old printer.cfg which I migrated some settings from.
EDIT: When I send a "SET_CENTER_KINEMATIC_POSITION" command first, the homing works afterwards until I disable all motors or restart.
11 Replies
I also tried inserting this from my old printer.cfg but no luck
Safe Z Home (Physical endstops only)
[safe_z_home]
home_xy_position: 150,150 # 300mm printer
#home_xy_position: 200,200 # 400mm printer
#home_xy_position: 250,250 # 500mm printer
So you get "must home axis" when you press Home after a fresh restart?
You should have gone with 2.1...
let me check the files
can´t see anything that can mess homing sequence...
do you mind giving a try at 2.1? 2.x is not in development anymore.
Use the current printer.cfg to correct motor directions and you can also save some of the overrides (like skew correction) if you only did RatOS flashing and the machine has nothing different.
That was my initial thought but didn't want to reflash again as soon as the full release is out.
I will try 2.1 on sunday and mark this as solved if it works.
I need to rerun the skew correction since I upgraded to the 3.1 movement system (bed arms are still 3.0, they will be swapped next week). But everything worked after the mechanical upgrade, I just needed to upgrade to 2.0.2 because upgrading to the latest 1.x version bricked klipperscreen for me.
It was just strange to me since it didn't let me home because it was not homed... thats odd
Same problem here after the last Klipper update (running RatOs 2.0)
maybe a bug?
I’m not sure. There were not many bug changes on 2.0 since 2.1 is on the making…
i think is related to klipper only
and last commits
Commits on Jan 21, 2025
force_move: Use strings for axes to clear in clear_homing_state()
toolhead: Pass set_position() homing_axes parameter as a string
stepper_enable: Directly call clear_homing_state() on motor off event
but i m not sure, could you please check?
Also this one maybe
force_move: Implement CLEAR for SET_KINEMATIC_POSITION (#6262)
@miklschmidt if you have a minute, please…
thank you
I did nothing… just asking for God to help 🤪
maybe it is a rare error but can help people that found it
i temporary fixed with set kinematic position command and then the printer can home like before