Unable to Home Printer after Latest Klipper Update

General Discussion
1

Basic Information:

Printer Model: RatRig V-Core 3.1
MCU / Printerboard: BTT Octopus V1.1 (F446)
Host / SBC: Raspberry Pi 4B/
klippy.log
klippy.log (160.2 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…
I updated Klipper on my printer today as I saw there were some commits to it on 01/21/2025. Since then, I am unable to home the printer without first spoofing the X, Y, and Z Coordinates. The error message I receive, no matter whether I try to home all axes or a single axis is, Must home axis first: 0.000 0.000 7.000 [0.000].

I’ve posted the screenshot below of the console and also attached the klippy log file.

image
image2556×810 128 KB

This error message makes no sense… How can I home an axis before homing it?

Is there a way for me to roll back to a stable version of klipper?

2

The SET_CENTER_KINEMATIC_POSITION is a custom macro that sets the axes kinematic position to 1/2 the max printer dimensions, essentially spoofing the printer into thinking the toolhead is at X=150, Y=150, Z=150. Here’s the macro:

[gcode_macro SET_CENTER_KINEMATIC_POSITION]
description: FOR DEBUGGING PURPOSES ONLY. Sets the internal printer kinematic state to the center of all axes regardless of actual physical position.
gcode:
	RESPOND MSG="WARNING: ONLY USE SET_CENTER_KINEMATIC_POSITION FOR DEBUGGING PURPOSES. YOU'RE OVERRIDING THE INTERNAL POSITIONING STATE OF THE PRINTER. PROCEED WITH CAUTION AND DO A PROPER G28 WHEN DONE."
	SET_GCODE_VARIABLE MACRO=MAYBE_HOME VARIABLE=is_kinematic_position_overriden VALUE=True
	SET_KINEMATIC_POSITION X={printer.toolhead.axis_maximum.x / 2} Y={printer.toolhead.axis_maximum.y / 2} Z={printer.toolhead.axis_maximum.z / 2}
3

I used KIAUH to roll back 3 commits and now homing works. Once the three commits pertaining to homing were rolled back things worked just fine. These are the commits I rolled back:

image
image720×188 10.9 KB

I’m not Github savvy, so not sure how to report this as an issue on the klipper Github. Any advice?

1 Like
4

You are running a highly modified Klipper with unknown extensions.
Probably there is something with klippy/extras/ratos_homing.py

I tested those patches before the merge and they work.
btw, I also have RatRig.

If you are able to reproduce it on vanilla Klipper - you can definitely report an issue.

5

Thanks. I figured it had to do with the RatRig version of klipper. The ratos_homing.py extension is the RatOS homing extension that combines both the Klipper homing_override and safe_z_home sections into one. I’ve raised an issue on the RatOS Github for this.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.