Bug report: [safe_z_home] z_hop, z-axis force-move inoperative

General Discussion
1

Basic Information:

Printer Model: Creality Ender 3 S1
MCU / Printerboard: Stock Creality
Host / SBC: x64 VM
klippy.log: klippy-szh.log (115.3 KB)

Describe your issue:

So I guess there’s no-longer a dedicated channel for reporting bugs with Klipper? The project’s repo is locked down, with instructions to post here, but the developer’s New Post template just says “Don’t post bug reports here”… I guess here will do?

Anyhow, Klipper no-longer functionally z-hops when homing. There is a pause when the printer should be moving, and on the web UI (Mainsail), the reported height can be seen increasing to the set hop value, with no stepper movement. My [safe_z_home] config is unchanged since this worked a few months ago (I haven’t used the printer for a while). In addition, FORCE_MOVE on the Z axis also does not function when the axis isn’t homed.

I suspected a hardware fault, but on inspection all is fine. The printer otherwise behaves correctly, with the Z axis moving freely in both directions, starting from the downward movement of the homing function. Also, FORCE_MOVE STEPPER=stepper_z works when the axis is homed.

This is of course sub-optimal, as Klipper thinks it’s at a safe distance above the bed when in reality it’s still at an arbitrary Z height and is vulnerable to crashing into the bed.

Potentially related:

Edit: Further homing weirdness; with the z-hop options in [safe_z_home] removed, the Y axis does not home – after about 10 seconds the error No trigger on y after full movement appears, despite no movement from the Y axis.

1 Like
2

I currently have no idea, what could be causing this on your side and I do not see anything obviously amiss in your configuration.
BUT:

  • The exact same setup works for me on latest Klipper sources and it does z-hop
  • A Command like FORCE_MOVE STEPPER=stepper_z DISTANCE=3 VELOCITY=10 works without homed steppers
  • Both above are very commonly used, so this place would be full of similar reports
3

Hi @Sineos , apologies for the delayed response – I wished to test whether this was an issue dependent on firmware version as I saw seemingly relevant commits within this year. However, I borked the downgrade procedure and had to wait until I was able to get an ST-Link to reinstall a bootloader and get my board working again.

On further inspection it seems that, while in storage, the solder joints on the UART mod I performed on the Creality motherboard had come somewhat loose. While I haven’t visually confirmed this, downgrading to release v0.12.0 did not fix the problem, while removing the previously functioning TMC blocks from my config did.

When making this report, I had completely forgotten that the TMC functionality was a modification I made to the board, as it had been so long. I apologise for not mentioning this earlier, and thank you for taking the time to look over the report and reply.

All my best.

4

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