Nozzle Crash due to X axys issues

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 r2
MCU / Printerboard: mcu (stm32h723xx)

Version: v0.12.0-179-g434770ea

Load: 0.00, Awake: 0.00, Freq: 400 MHz,

mcu EBBCan (rp2040)

Version: v0.12.0-179-g434770ea

Load: 0.02, Awake: 0.00, Freq: 12 MHz,
Host / SBC - pi4 I think
Host (aarch64, 32bit)

Version: v0.12.0-179-g434770eaf-dirty

OS: Raspbian GNU/Linux 11 (bullseye)

Distro: MainsailOS 1.2.1 (bullseye)

klippy.log
klippy_nozzle_crash-negative_x_offset.zip (161.5 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:

…
The nozzle misses the Z endstop by 5-10mm, randomly.It happened 5 times or so during the last year, but this caused me damaging revo nozzles and they are not cheap.

The X and Y end stops are at: 355.00Y and 351.00X. The Z end stop is located at: switch_xy_position: 120.00, 355

When the nozzle misses it, each time it was on the right side by about 5mm or so, which is closer to the end stop, phisically at around 129.00 on the X axys. I am not sure about the location the printer thinks it has at that time to be honest.

2

Hello @Hannibal_King !

Have you tried with a presion Klipper?

Git version: 'v0.12.0-179-g434770eaf-dirty'
Untracked files: klippy/extras/z_calibration.py

We do not know what has been changed there.

Please see: The "dirty" Flag and the Team's Position

I can’t see in the log how you manage to reach that point.

You may try: Configuration reference - Klipper documentation

3

what’s that a pression Klipper? I just made a backup of everything in the config location and wiped the card again using the pi image tool

4

Sorry, typo. I meant pristine (as like genuine)

5

oh, ok. thank you! I have no idea how I made it dirty. I flashed it with the pi imager tool the first time too

6

You have installed a Klipper code modification called z_calibration.py. In the settings block of this modification, you have set:

[z_calibration]
nozzle_xy_position = 120.00, 355
switch_xy_position = 120.00, 327.5
bed_xy_position = 175, 175

Based on your description of the unwanted behavior, it is almost 110% certain that this issue stems from this third-party modification.

Also see the link @EddyMI3D already posted for an explanation why such modifications are often not just “a file more” or some lines of modified code.

7

You think that was the reason the host was “dirty”?

8

See The "dirty" Flag and the Team's Position

9

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