Always have Move out of range on bed mesh calibrate

General Discussion
1

Basic Information:

Printer Model: Enderwire
MCU / Printerboard: BTT SKR E3 mini v2
Host / SBC

klippy.log (46.6 KB)

Hi!
I always have move out of range on bed mesh calibrate. Can somebody help me to found a way to make it work? Thanks! :slight_smile:

2

You bed is 0,0 to 216,215.

You mesh is -3,2 to 186,217.

You can’t do the mesh beyond the bed’s limits.

3

I don’t know why on the .log there are that values, but on printer.cfg I have:

[stepper_x]
step_pin: PB13
dir_pin: PB12
enable_pin: !PB14
rotation_distance: 40
full_steps_per_rotation: 200
microsteps: 32
endstop_pin: ^PC0
position_endstop: 216
position_min: 0
position_max: 216
homing_speed: 70
homing_positive_dir: true
homing_retract_dist: 0

[stepper_y]
step_pin: PB10
dir_pin: PB2
enable_pin: !PB11
microsteps: 32
rotation_distance: 40
endstop_pin: ^PC1
position_endstop: 208
position_min: -27
position_max: 208
homing_speed: 70
homing_positive_dir: true

[probe]
pin: ^PC2
z_offset: 0 #Measure per your specific setup
x_offset: 0 # negative = left of the nozzle
y_offset: 29 # negative = in front of of the nozzle
speed: 1.0
lift_speed: 15.0
sample_retract_dist: 2
samples: 2
samples_tolerance_retries: 6

##[(7x7)-1] / 2 = 24
##[(5x5)-1] / 2 = 12
[bed_mesh]
speed: 300
horizontal_move_z: 2
mesh_min: 0, 0
mesh_max: 216, 179
probe_count: 5,5
zero_reference_position: 117.5, 117.5
algorithm: bicubic
fade_start: 1
fade_end: 10

Could it be that klipper is reading those values anywhere else?

4

Ok, I think I have it duplicated so the one I pasted should work :stuck_out_tongue:

5

Ok, still don’t work :stuck_out_tongue: this is the correct klippy.log.
Thanks :slight_smile:

klippy.log (37.9 KB)

6

Solved, moved the y_offset to 28 and it’s working :slight_smile:

1 Like
7

I’m not sure that I understand your solution.
If you have modified:

[probe]
...
y_offset = 29

Then it is very wrong to do so. The *_offset values must exactly match the actual hardware distance from your nozzle to the probe tip.

To prevent the MOOR error, the correct way is to adapt the starting points of the mesh in:

[bed_mesh]
...
mesh_min = 0, 0
mesh_max = 216, 179
8

Thanks Sineos! I already tried that values, they gives Move out of range

9

Then likely you made a mistake. It will lead to unpredictable result if your offsets do not match the reality.
See Understanding X and Y Axes Limits and Homing and in particular the last chapter in this article.

10

Thanks for your support Sineos.
I fine tuned the bed size and the endstops.

This is the config that’s working, the probe microswitch is at at 0,29

the following is working and is covering the bed pretty at all:

[stepper_x]
step_pin: PB13
dir_pin: PB12
enable_pin: !PB14
rotation_distance: 40
full_steps_per_rotation: 200
microsteps: 32
endstop_pin: ^PC0
position_endstop: 216
position_min: 0
position_max: 216
homing_speed: 70
homing_positive_dir: true
homing_retract_dist: 0

[stepper_y]
step_pin: PB10
dir_pin: PB2
enable_pin: !PB11
microsteps: 32
rotation_distance: 40
endstop_pin: ^PC1
position_endstop: 208
position_min: -27
position_max: 208
homing_speed: 70
homing_positive_dir: true

[probe]
pin: ^PC2
z_offset: 0 #Measure per your specific setup
x_offset: 0 # negative = left of the nozzle
**y_offset: 27** # negative = in front of of the nozzle
speed: 1.0 # era 5
lift_speed: 25.0
sample_retract_dist: 2
samples: 2
samples_tolerance_retries: 6

[bed_mesh]
speed: 300
horizontal_move_z: 2
**mesh_min: 0, 0**
**mesh_max: 216,208**
probe_count: 9,9
zero_reference_position: 108, 104
algorithm: bicubic
fade_start: 1
fade_end: 10

But If I only change to:

y_offset: 28

and

mesh_min: 0, 0
mesh_max: 216,207

I have Move out of range :frowning:

1 Like
11

One tiny request:

When you upload code snippets, please Preformatted Text to bring that in a proper form. It is more easy to read and information is not formatted away.

Format

When you made changes to the printer.cfg, it is always better to upload the klippy.log.

12

Sure, thanks!
It’s a clean klippy.log, with 2 tries, the first is with the non working config, the second one with the working.

Thanks!

klippy.log (31.8 KB)

13

I do not know your printer, but I somehow doubt that this:

[bed_mesh]
...
mesh_min = 0, 0
mesh_max = 216,208

is correct. Also, I do not know if your offsets are correct:

[probe]
...
x_offset = 0
y_offset = 27

Both go hand in hand and especially the *_offset needs to be as precise as possible.

I propose you go through the relevant steps to make sure that everything is correct here:

14

The 27mm y offset is the one is working, the real is 29mm and I’d like, as you told it’s important, to fix this issue. So I will investigate and I will also read your kindly linked articles. I tuned the bed with two YouTube videos:

But I will follow your links and I will back, for now thanks :slight_smile: