Printer ignores Mesh / no longer working

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 R1
MCU / Printerboard: Fysetc Spider, EBB42 via CAN bus, Expander
klippy.log
klippy.log.zip (1.4 MB)

Describe your issue:

I own a Voron 2.4 R1 with a klicky probe which has been running great for the past year. Now I wanted to print a part (gcode had it twice on the plate) which worked perfectly as usual. I needed the part four times so I reran the same gcode again and the print failed at a certain height. The printer made scrapping noises in that location and would no longer extrude any filament. I can narrow the issue down to the front left region of the heat bed. Mesh looks good, yet it will try to print way too close to the bed. My parts were located in the center of the bed, first layer still looking ok but the issue would always appear on the front left corner. If i position a part to the front left first layer starts to get way too close up until the point that nothing is being extruded anymore.

I recently updated klipper, changing the config from the relative_reference_index to zero_reference_position. I am at a loss here, to me it seems like the mesh is ignored / ABL is no longer working.

bed mesh 2
bed mesh 21199×590 36.1 KB

2

Where / how do you load or generate the mesh to be used? From the log it seems nowhere.

1 Like
3

My print start macro:
[gcode_macro PRINT_START]
gcode =
G32
G1 Z20 F3000
BED_MESH_CALIBRATE ADAPTIVE=1 ADAPTIVE_MARGIN=5

That should generate the mesh (at least the printer probes the bed before printing)

edit:
Just reread the documentation:
BED_MESH_PROFILE LOAD=default seems to be required now. My guess: I updated from a fairly old klipper version where the default behaviour was to load the mesh. So now I generate a mesh but don’t use it…
Added the load command and will check if that was it. Thanks for pointing me down that road

4

Still scrapping the bed, despite the load command being added
klippy(1).zip (535.3 KB)

5

If you use adaptive meshing then you do not need to load a profile.

I can’t see any Klipper reason or misconfiguration. Could be a mechanical issue.

6

Thanks for having a look.
I am really at a loss here. Can’t seem to find anything wrong with the printer. Z Motors move normally, belts got tension, buzzing the motors works.
Got a slightly cracked front idler which I will replace.
Besides that I got no idea what to look for

7

Check if Axis Twist Compensation - Klipper documentation changes anything.

8

Thanks for the suggestion. I checked and realigned everything, Problem still persists.
My best guess is that it has something to do with the zero_reference_position.
175.000,155.250 is the Point being probed during mesh creation but I specified 175,175 as the reference because that is where I do my paper tests and calibration (or auto calibration which is currently off). Could that be the issue?

eDIT: Changed the position but no luck.
Still getting way to close.

9

A zero_reference_position is only valid if you combine it with an endstop and when you calibrated your offset with the help of this endstop and not with the probe.

10

I had it in there because the auto-z calibration recommended it:
When using a bed mesh, it is recommended to configure it with a zero reference position which used to be the relative reference index (“bed_mesh:zero_reference_position” setting).

Will try without it. Really at a loss here :frowning:

Edit:
Tried without it → no luck. Nozzle scrappes the bed in some places.

11

I have a similar problem with the anicubic cobra 2 pro. I completely went over and adjusted all the gaps, but after the mesh is formed, the first layer turns out to be unsatisfactory. If you are interested, here is a little information about this that I could find.

12

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