# Must Home Axis after just Homed

**URL:** <https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203>\
**Category:** General Discussion\
**Created:** [August 10, 2024, 10:33pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203 "2024-08-10T22:33:22Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![adk\_eric](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@adk\_eric](https://klipper.discourse.group/u/adk_eric)\
**Post date:** [August 10, 2024, 10:33pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/1 "2024-08-10T22:33:22Z")

</div>

### Basic Information:

Printer Model: K1 Max  
 MCU / Printerboard: Stock  
 Host / SBC: Mac Sonoma 14.5  
 klippy.log  
[klippy.log](https://klipper.discourse.group/uploads/short-url/3w7dvqtYZGOywCYBIib32bN0CYk.log) (1.8 MB)

_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:

Iam modding a K1 Max with the Linear Gantry and have replaced the motors, etc. I have connections and belts set. If I home XY through Klipper, all works as expected. But when I try to move the toolhead (either through Klipper, or using G1, or one the K1 Max panel) I receive the error

!! {“code”:“key95”,“msg”:“Must home axis first: 294.000 9.000 0.002 [0.000]”, “values”:[294.000, 9.000, 0.002, 0.000]}

As if it is not retaining that it has already been homed. Any suggestions or pointers on where to look for info?

…

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [August 11, 2024, 1:43pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/2 "2024-08-11T13:43:02Z")

</div>

Hello @adk_eric !

With the requested klippy.log it may be more easy.

Have you used `M18` or `M84` after homing or did Klipper just a idle timeout?

---

<div class="post-metadata">

**Author:** ![adk\_eric](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@adk\_eric](https://klipper.discourse.group/u/adk_eric)\
**Post date:** [August 11, 2024, 7:09pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/3 "2024-08-11T19:09:11Z")

</div>

Thank you for your reply. I had some trouble downloading the log file through orca but switched to browser and was able to do it. It is attached now.

The most recent events were homing (correctly) and then trying to move the head with the resulting errors.

I have previously used M84 to stop the motors when I was moving the head to tune the sensorless homing values. But learned it discards the homing info so I am not using that command between homing and trying to move the head.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [August 12, 2024, 5:08pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/4 "2024-08-12T17:08:35Z")

</div>

Creality and the K1 is using a modified Klipper version and the number of macros loaded in this config is beyond what anyone (at least I) will be willing to analyze to find any bug.  
The best thing is to revert to Creality for support.

---

<div class="post-metadata">

**Author:** ![adk\_eric](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@adk\_eric](https://klipper.discourse.group/u/adk_eric)\
**Post date:** [August 12, 2024, 5:13pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/5 "2024-08-12T17:13:35Z")

</div>

I have rooted the machine and am running Klipper via Guilkouz’s Helper Script.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [August 12, 2024, 5:16pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/6 "2024-08-12T17:16:51Z")

</div>

This does not change the statement above. It just gives you more opportunity to mess up things.

---

<div class="post-metadata">

**Author:** ![adk\_eric](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@adk\_eric](https://klipper.discourse.group/u/adk_eric)\
**Post date:** [August 12, 2024, 5:31pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/7 "2024-08-12T17:31:23Z")

</div>

I’m sorry. I am confused. I have used the K1 Max as a platform for open source software. If this forum is for developers only, I apologize. Is there another for users of the software?

---

<div class="post-metadata">

**Author:** ![flowerysong](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/flowerysong/32/10214_2.png) [@flowerysong](https://klipper.discourse.group/u/flowerysong)\
**Post date:** [August 12, 2024, 5:38pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/8 "2024-08-12T17:38:36Z")

</div>

This forum is for users of the open source Klipper project, and does not provide support for Creality’s modified version. Please contact Creality support for questions about their software.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [August 12, 2024, 5:42pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/9 "2024-08-12T17:42:22Z")

</div>

> [@adk\_eric](#):
>
> I have used the K1 Max as a platform for open source software.

Unfortunately, Creality and Open Source are two things that do not really go well together. Creality is in constant violation of Klipper’s license and due to their heavy modifications of the Klipper code, Klipper’s behavior is massively changed.

For example, they have some hard-coded (at least last time I checked) start up routine with fixed temperatures. There is a thread here that discusses this behavior.

---

<div class="post-metadata">

**Author:** ![adk\_eric](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@adk\_eric](https://klipper.discourse.group/u/adk_eric)\
**Post date:** [August 12, 2024, 5:58pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/10 "2024-08-12T17:58:00Z")

</div>

I think I understand and I appreciate your time. I’d like to echo back to make sure I got it.

The helper script I used (from Guilous) installs Fluidd, Moonraker, etc. But does not install a new (open source) version of Klipper and instead retains the Creality version and runs the other services on top so it’s more accessible. But it is still Creality version on the machine.

And thanks again for your time.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [August 12, 2024, 6:18pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/11 "2024-08-12T18:18:26Z")

</div>

> [@adk\_eric](#):
>
> But does not install a new (open source) version of Klipper and instead retains the Creality version and runs the other services on top so it’s more accessible. But it is still Creality version on the machine.

Correct. In fact, it is Creality themselves who are providing this “root” means and it is nothing more than pseudo freedom since you are still bound to “their” Klipper.

Once they decide to drop their support for the K1 you will be f§$!§d unless some interested developer steps up and make the mainline Klipper or some fork compatible with the respective Creality model.  
If you are interested some more blurb on this topic here: [Importance of Open Source in 3D Printing and the Consequences of OSS License Infringement](https://klipper.discourse.group/t/importance-of-open-source-in-3d-printing-and-the-consequences-of-oss-license-infringement/12624)

---

<div class="post-metadata">

**Author:** ![adk\_eric](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@adk\_eric](https://klipper.discourse.group/u/adk_eric)\
**Post date:** [August 12, 2024, 6:41pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/12 "2024-08-12T18:41:39Z")

</div>

Thank you for helping me get it. If that point comes, are there supported MCU boards that I could use to replace the Creality board where the porting is already done? I’m a retired engineer so I cover basic changes.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [August 12, 2024, 7:05pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/13 "2024-08-12T19:05:38Z")

</div>

This is purely a software question. AFAIK, the Creality boards are nothing special.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [October 11, 2024, 7:05pm UTC](https://klipper.discourse.group/t/must-home-axis-after-just-homed/18203/14 "2024-10-11T19:05:53Z")

</div>

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