Bed mesh not leveling first layer

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 350mm
MCU / Printerboard: BTT Octopus
Host / SBC: RPI 4B

klippy (3).zip (1.6 MB)

Describe your issue:

Hello, as the title says I’m running into an issue with the bed mesh.

I have a Voron 2.4 equipped with Voron Tap, which I’ve built and set up recently. During my first prints I noticed that the bed mesh is not compensating the first layer. I don’t see the Z motors moving at all during the first layer—neither the motors nor the belts show any adjustment.

I’m going crazy trying to understand what the problem could be.

I’m attaching my PRINT_START as well.

[gcode_macro PRINT_START]

#   Use PRINT_START for the slicer starting script - please customise for your slicer of choice

gcode:

    G90 ; use absolute coordinates
    M83 ; extruder relative mode
    G21
    M140 S{params.BED_TEMP}; #set bed temperature
    M190 S{params.BED_TEMP}; #wait bed temperature
    Gantry_Level 
    BED_MESH_CLEAR
    BED_MESH_CALIBRATE ADAPTIVE=1;
    M104 S{params.EXTRUDER_TEMP}
    Smart_Park
    M109 S{params.EXTRUDER_TEMP}
    VORON_PURGE
    G92 E0;




[gcode_macro PRINT_END]

#   Use PRINT_END for the slicer ending script - please customise for your slicer of choice

gcode:

    SAVE_GCODE_STATE NAME=STATE_PRINT_END
    G92 E0
    G91
    G1 Z2 
    G90
    G28 X Y
    TURN_OFF_HEATERS
    M106 S255
    G4 S60
    M107                                     ; turn off fan
    RESTORE_GCODE_STATE NAME=STATE_PRINT_END

[gcode_macro Gantry_Level]
gcode:
    G28
    QUAD_GANTRY_LEVEL
    G28 Z

The adaptive bed mesh is executed after homing; then QGL runs and performs a Z-only home again; after that, the previously loaded mesh is cleared with the appropriate command, and finally the adaptive mesh is generated over the necessary points. However, the first layer is always inconsistent compared to the test sheet result (I calibrated with a first layer sheet and it was perfect, but on the next print it was no longer correct).

I can’t understand where the issue is coming from. I also tried running axis twist compensation.

Could someone help me? Thank you very much in advance!

2

What is in the start gcode within the slicer?

3

thid for material

image
image882×420 15 KB

and this for printer

image
image859×540 12.5 KB

4 
Args: ['/home/pi/klipper/klippy/klippy.py', '/home/pi/printer_data/config/printer.cfg', '-I', '/home/pi/printer_data/comms/klippy.serial', '-l', '/home/pi/printer_data/logs/klippy.log', '-a', '/home/pi/printer_data/comms/klippy.sock']
Git version: 'v0.13.0-403-gb4c7cf4a3-dirty'
Untracked files: klippy/extras/autotune_tmc.py, klippy/extras/gcode_shell_command.py, klippy/extras/motor_constants.py
Branch: (HEAD detached at b4c7cf4a3)

You should, at minimum turn off interpolate, for the Z steppers.

I’d rip out all the “extras” and get the core functions working THEN add “extras” back one at a time and TEST to see if they have any benefit. At some point 3db quieter without any improvement in print quality is more trouble than it’s worth.

5

Ok, mate i’ll give a try, disabling autotune for z motors, adding to this, i updated klipper and some extras where broken, in next days i’ll upload the klippy log, my printer is currently in my workplace.