First Klipper Build Actuator Help

General Discussion
1

Basic Information:

Printer Model: SV08
MCU / Printerboard: Octopus Max EZ
Host / SBC: Ubuntu 22.04 Server
klippy.log
klippy.log (1.0 MB)

Issue: Aborting quad_gantry_level required adjustment 1319983851176.633789 is greater than max_adjust 10.000000

Have recently finished swapping out my dead mainboard for an octopus max ez, have flashed mainline to it, to the toolhead, have comms and control of the machine. However Quad Gantry Level is giving some absolutely ridiculous Actuator Positions and then stopping the cycle with the error below. Have homed first that is working right, QGL i cant figure out whats going on. I would like to add this is my first Klipper install, but i have built the configs by following both the Rappetor mainline github for the sv08, and BTT’s for the octomax, have had help along the way to undertstand bits but im stumped by this one and so has everyone i asked so far. Figured this would be the best place to ask.

Have added Config Zip so all cfg’s available.

config-20250505-143617.zip (20.1 KB)


Aborting quad_gantry_level required adjustment 1319983851176.633789 is greater than max_adjust 10.000000
14:07
Aborting quad_gantry_level required adjustment 1319983851176.633789 is greater than max_adjust 10.000000
14:07
Average: 2899890158.271362
14:07
Actuator Positions:
z: -1317083961018.362305 z1: 256099659101.094238 z2: -258899553029.452148 z3: 1331483415579.805664
14:07
Gantry-relative probe points:
0: 6.672031 1: 9.728984 2: 3.569492 3: 4.815664
14:07
probe at 24.000,50.000 is z=0.182344
14:07
probe at 24.000,50.000 is z=0.184219
14:07
probe at 24.000,50.000 is z=0.184687
14:07
probe at 24.000,50.000 is z=0.186094
14:07
probe at 296.000,60.000 is z=1.430625
14:07
probe at 296.000,60.000 is z=1.430625
14:07
probe at 296.000,60.000 is z=1.430625
14:07
probe at 296.000,60.000 is z=1.430156
14:07
probe at 24.000,340.000 is z=-4.731094
14:07
probe at 24.000,340.000 is z=-4.728750
14:07
probe at 24.000,340.000 is z=-4.726406
14:07
probe at 24.000,340.000 is z=-4.729688
14:07
probe at 296.000,340.000 is z=-1.677188
14:07
probe at 296.000,340.000 is z=-1.673906
14:07
probe at 296.000,340.000 is z=-1.669688
14:07
probe at 296.000,340.000 is z=-1.667344
14:07
Bed heating...
14:07
The bed target temperature was not reached!
14:07
Check Heating!
14:07
QUAD_GANTRY_LEVEL
14:05
SET_HEATER_TEMPERATURE HEATER=heater_bed TARGET=60
14:00
Homing Z
14:00
Homing X
14:00
Homing Y
14:00
G28

Any Help would be greatly appreciated.

2

Hello @jorrek !

[quad_gantry_level]
gantry_corners = 
	-60,-10
	410,420
points = 
	296,340
	24,340
	296,60
	24,50
speed = 350
horizontal_move_z = 5
retry_tolerance = 0.0075
retries = 5
max_adjust = 10

Have you tried to setup the quad_gentry_level according to this? Configuration reference - Klipper documentation

1 Like
3

yes i did thank you bud altered it as was having issues with out of bound realised why had the z and z2 swapped without realising, qgl fixed now, just working on getting bed meshing to work now :smiley: i seem to have missed something else somewhere on that one

4

ok so the Bed_mesh_calibrate command seems to ignore toolhead position and assume its at the first probe point, the of cours crash into the sides :sweat_smile:

5

Have you taken the X/Y probe offsets


[probe]
pin = extra_mcu:PB6
x_offset = -17
y_offset = 10
speed = 5.0
samples = 4
sample_retract_dist = 3.0
lift_speed = 35
samples_result = average
samples_tolerance = 0.012
samples_tolerance_retries = 5
z_offset = 0

in consideration to the bed mesh?

[bed_mesh]
speed = 500
horizontal_move_z = 5
mesh_min = 10,10
mesh_max = 333,340
probe_count = 9,9
algorithm = bicubic
bicubic_tension = 0.4
split_delta_z = 0.016
mesh_pps = 3,3
adaptive_margin = 5
fade_start = 0
fade_end = 10
fade_target = 0

see: Understanding X and Y Axes Limits and Homing

Always use a safety margin of 5mm or so.

6

have done now though it isnt going out of bounds, but this produces a better mesh area imo anyways, the issue i have is the BED_MESH_CALIBRATE command just starts the bed mesh from wherever the toolhead is at when the command is triggered, it doesnt first move the head to the min position, just starts as if it were already there. BED_MESH_CALIBRATE_BASE however works and produces a mesh

7

Note that your macros are overwriting BED_MESH_CALIBRATE and BED_MESH_CALIBRATE_BASE is Klipper’s default behavior. The overwritten version always uses ‘adaptive’ meshing, so it only makes sense in combination with an actual print.

1 Like
8

So do i just need to alter the mainsail somehow so the bed mesh calibrate uses BED_MESH_CALIBRATE_BASE instead of BED_MESH_CALIBRATE?

Edit: Doesnt matter for some reason BED_MESH_CALIBRATE_BASE is now doing the same thing and i havent changed anything

9

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