Creality sprite extruder ABL; move out of range

General Discussion
1

got klipper running on my ender 3 v2 with a sprite extruder and CR touch
got everything mostly working but I continue getting a “move out of range” error even after tons of tinkering with settings

relevant config file settings:
[bltouch]
sensor_pin: ^PB1
control_pin: PB0
x_offset: -31.8
y_offset: -40.5
z_offset: 3.82
#z_offset: 3.82

[safe_z_home]
home_xy_position: 117.5, 117.5
speed: 50
z_hop: 10
z_hop_speed: 5

[bed_mesh]
speed: 120
horizontal_move_z: 10
mesh_min: 30,40
mesh_max: 230,230
probe_count: 4,4
algorithm: lagrange
fade_start: 1
fade_end: 10
fade_target:0
mesh_pps: 3,3

2

More is relevant: Please always attach the complete klippy.log (includes: please do not delete the template): To analyte your issue completely we need the dimensions that are stored in the stepper sections.

And for code snipptes please use the code formatting:

Format

Guess to your issue: Take the BLtouch offset into calculation for the bed mesh.

1 Like
3

here is the rest of the config file, how should i calculate the size for the mesh using the offset?



[stepper_x]
step_pin: PC2
dir_pin: PB9
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA5
position_endstop: 0
position_max: 235
homing_speed: 50

[stepper_y]
step_pin: PB8
dir_pin: PB7
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA6
position_endstop: 0
position_max: 235
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_endstop: 0.0
#position_max: 250

[stepper_z]
step_pin: PB6
dir_pin: !PB5
enable_pin: !PC3
microsteps: 16
rotation_distance: 8
endstop_pin: probe:z_virtual_endstop
#position_endstop: 0.0
position_max: 250

[bltouch]
sensor_pin: ^PB1
control_pin: PB0
x_offset: -31.8
y_offset: -40.5
z_offset: 3.82
#z_offset: 3.82

[safe_z_home]
home_xy_position: 117.5, 117.5 
speed: 50
z_hop: 10            
z_hop_speed: 5


[bed_mesh]
speed: 120
horizontal_move_z: 10
mesh_min: 30,40
mesh_max: 230,230
probe_count: 4,4
algorithm: lagrange
fade_start: 1
fade_end: 10
fade_target:0
mesh_pps: 3,3

[extruder]
max_extrude_only_distance: 100.0
step_pin: PB4
dir_pin: PB3
enable_pin: !PC3
microsteps: 16
rotation_distance: 34.406
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: PA1
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PC5
control: pid
# tuned for stock hardware with 200 degree Celsius target
pid_Kp: 21.527
pid_Ki: 1.063
pid_Kd: 108.982
min_temp: 0
max_temp: 250

[heater_bed]
heater_pin: PA2
sensor_type: EPCOS 100K B57560G104F
sensor_pin: PC4
control: pid
# tuned for stock hardware with 50 degree Celsius target
pid_Kp: 54.027
pid_Ki: 0.770
pid_Kd: 948.182
min_temp: 0
max_temp: 130

[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: 3000
max_z_velocity: 5
max_z_accel: 100







[include mainsail.cfg]


[virtual_sdcard]
path: ~/printer_data/gcodes

[display_status]

[pause_resume]

#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*#
#*# [bltouch]
#*# z_offset = 7.640
4

You bed is 235 x 235. and has no negative area below 0/0

Your bltouch offset is at -31.8/-40.5

You start the bed mesh at 30/40

In that moment the bltouch is at position 30 - 31.4 = -1.4 / 40 - 40.5 = -0.5

This is out of the bed’s area.

BTW: When I say klippy.log, I mean klippy.log. There are more information inside to help analyse.

1 Like
5

sorry, i misread what file you wanted

i have now attached the klippy.log file
klippy.log (2.5 MB)

1 Like
6

i changed the minimum position to 33,42 as you suggested and attempted to generate a mesh. the error message i received said that the target position had an x value of 260 which is way outside the max value of 230 i have set.

7

The log stated this:

Move out of range: 237.800 41.500 10.000 [0.000]

You also may check the maximum values of the bed mesh area.

And much more.

There are some macros that poke around inside some important parameters. If not called with the proper values, obscure things can happen.

E.g.:

[gcode_macro _TOOLHEAD_PARK_PAUSE_CANCEL]

Why a macro that creates things depending on a certain kinematic you use.
Usually you do not swap your kinematics on the fly (you even can’t: It’s hardware). So such macros make no sense at all. Just a macro that is dedicated for the kinematic you use.

1 Like
8

Max values are both at 230, i have tried making them much lower but it doesn’t help

9

I’ll try setting up some macros and see if that changes anything

10

Sure, you can set up your Klipper environment by trial and error, but you end an a huge mess and you have to start over again.

The better way is to get familiar with how it all works to reach the aim as straight as possible.

I can recommend these:

https://www.klipper3d.org/Overview.html

1 Like
11

thank you for all your help, I believe I have found the issue. from what I have observed I believe the position_min and position_max refers to the position of the probe so if the probe was at the maximum position (230,230), the position of the nozzle would be 261.8,270.5 which is the exact position of the error message.