#Klipper bed_mesh_calibrate seems to move out of boundaries

13 messages · Page 1 of 1 (latest)

ember jungle
#

Hi people, unfortunately my plan to figure everything out by myself isn´t working. Better said the automatic bed leveling isn´t.

I am quite new to the hobby, bought an Ender 3 S1, did some prints first but wanted to go for Klipper anyways. That also worked in general, raspberry has octoprint, is connected, gets commands, well. I think what i only need to do from now on is to get mesh, calibrate a little, get the mesh saved and used when printing.

But bed_mesh_calibrate command is moving in y axis too far. It bumps a little, making a sound when going to the last line of mesh points. I somehow cant imagine that this is the standart behaviour. Has anyone had similar problems? I would be glad for any help as this is really making me nervous damaging my hardware while also thinking being so close to the end, ah.

I read and checked for so many hours by now. No idea. Printer config is the default from official repository (besides the z offset for BL touch). My printer profile has the correct volume (220 220 270). Maybe it is not beeing used, could that be?

Would be very happy if anyone has an idea, thanks in advance.

#

Config just in case:

[stepper_x]
step_pin: PC2
dir_pin: PB9
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: !PA5
position_endstop: -10
position_max: 235
position_min: -15
homing_speed: 50

[stepper_y]
step_pin: PB8
dir_pin: PB7
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: !PA6
position_endstop: -8
position_max: 238
position_min: -13
homing_speed: 50

[stepper_z]
step_pin: PB6
dir_pin: !PB5
enable_pin: !PC3
microsteps: 16
rotation_distance: 8
endstop_pin: probe:z_virtual_endstop
position_max: 270
position_min: -4

[extruder]
step_pin: PB4
dir_pin: PB3
enable_pin: !PC3
microsteps: 16
gear_ratio: 42:12
rotation_distance: 26.359
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: PA1
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PC5
control: pid
pid_Kp: 23.561
pid_Ki: 1.208
pid_Kd: 114.859
min_temp: 0
max_temp: 260 # Set to 300 for S1 Pro

[heater_bed]
heater_pin: PA7
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PC4
control: pid
pid_Kp: 71.867
pid_Ki: 1.536
pid_Kd: 840.843
min_temp: 0
max_temp: 100 # Set to 110 for S1 Pro

[heater_fan hotend_fan]
pin: PC0

[fan]
pin: PA0

[mcu]
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method: command

[printer]
kinematics: cartesian
max_velocity: 300
max_accel: 2000
max_z_velocity: 5
max_z_accel: 100

[bltouch]
sensor_pin: ^PC14
control_pin: PC13
x_offset: -31.8
y_offset: -40.5
z_offset: 1.95
probe_with_touch_mode: true
stow_on_each_sample: false

[bed_mesh]
speed: 60
mesh_min: 20, 20
mesh_max: 200, 197
probe_count: 4,4
mesh_pps: 2,2
algorithm: bicubic

[safe_z_home]
home_xy_position: 147, 154
speed: 75
z_hop: 10
z_hop_speed: 5
move_to_previous: true

[filament_switch_sensor e0_sensor]
switch_pin: !PC15
pause_on_runout: true
runout_gcode: PAUSE

[pause_resume]
recover_velocity: 25

[bed_screws]
screw1: 20, 29
screw2: 195, 29
screw3: 195, 198
screw4: 20, 198

tame basin
#

Your Y limit for the bed mesh is too high; it's reaching 237.5 out of 235mm the stepper has available according to your config

#

(197 limit for the mesh, plus 40.5mm Y offset for the probe)

#

Would recommend lowering it to something like 190 at most, would personally go a little lower though my bed mesh settings might be strange

ember jungle
tame basin
#

Idk, seems like the Y values were an oversight. Does the Y axis actually allow movement to 235mm, or only up to 220?

ember jungle
tame basin
#

Was the config you downloaded for the E3 S1 specifically? Because then I'd agree that it is strange

ember jungle
# tame basin Was the config you downloaded for the E3 S1 specifically? Because then I'd agree...

Yes, it is the one

https://github.com/Klipper3d/klipper/blob/master/config/printer-creality-ender3-s1-2021.cfg

I had many strange ideas.... like: Did I assemble some parts turned around? Did I override some commands without understanding anything... because that could be. I am quite a tech interested person, but not too experienced in either 3D printing or raspberries in general.

And some tutorials and reads were also confusing, especially one where it said G Code doesnt work on Klipper which made me think i never installed it and i am just using octoprint for marvin or so.... while my display has another issue by coincidence 😄

GitHub

Klipper is a 3d-printer firmware. Contribute to Klipper3d/klipper development by creating an account on GitHub.

tame basin
#

Klipper works with most Gcode just fine, although it's got a good few commands that are different from Marlin's

#

But I agree that the documentation for getting it set up is... Lacking, still ^^

ember jungle
#

Ah... finally back to a running printer... so happy. i had more the time invested in finding the issues with y axis than for the whole rest and i really started by almost zero (only had one pi project before).