K1C X-axis hits frame during homing / sensorless homing issue

Flagship K Series Creality Flagship K1 & K1C
1

Hi everyone,

I’m having a persistent problem with my Creality K1C 3D printer:

  • When I start a print, or manually move the print head left using the touchscreen controls, the X-axis hits the front-left frame.

  • This happens every time after powering on, even after performing G28 homing.

  • After the first collision, moving the head left/right works normally, but if I power off and start again, the problem repeats.

  • I have checked:

    • Firmware: latest version installed

    • Belts: properly tensioned

    • Rails: cleaned and lubricated

    • Motor: no obvious issues (moves normally in other directions)

I understand that the K1C uses sensorless homing (TMC driver detects stall), and it seems like the printer is not detecting the X-axis stop correctly at first, causing the head to slam into the frame.

Attempts to reduce the X-axis motor current via G-code (M906/M913) did not help — in fact, the collisions became stronger.

Questions:

  1. Has anyone experienced a similar X-axis sensorless homing issue on the K1C?

  2. Is this likely a faulty X-axis TMC driver or stepper motor?

  3. Are there any software/workarounds to fix this without replacing the board or motor?

Any advice would be greatly appreciated.

Thanks in advance!

2

I have the same issue, haven’t figured out how to fix it though. Came to this place for answers actually

1 Like
3

I found a simple workaround that prevents the print head from slamming into the left frame on the Creality K1C:

  1. Before starting a print, manually move the print head to the right side (centered on Y-axis).

  2. On the touchscreen, go to the menu and press X/Y Homing.

  3. After that, you can safely start your print.

:warning: Note: You need to repeat these steps before every new print, regardless of whether the printer was powered off or not.

This way, the printer homes correctly and avoids hitting the frame. Hopefully Creality will address this in a future firmware update.