I want to use variables for quad_gantry_level points. Is it possible?

[quick cobalt]

I am attempting to create an adaptive QGL macro, but do not see a way to replace the points with variables due to the lack of syntax for the points-

points:
50,50
50,300
300,300
300,50

Is this possible?

[long folio]

Is it possible? No idea. But you could start by looking at KAMP, and seeing how it gets in there to override values...

https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging/blob/main/Configuration/Adaptive_Meshing.cfg

[jagged mirage]

Not that I know of. But why? Qgl in the middle third somehow better?

[quick cobalt]

Why not? LOL. Not only to learn, but I want to reduce the print start time and believe that I can get a better QGL by only levelling close to the boundaries of the current print rather than at the outer corners of the bed plate. - just like the adaptive bed meshing.I would also like to randomize the QGL points to reduce the wear on the bed plate from probing.

[quick cobalt]

This is where I got the idea. Initially I just wanted to randomize "fuzz" the QGL points, but took it to the next level!

Forgive me if my terminology is poor - The problem with QGL versus meshing is that there is no syntax to add the variable to. For example if you have a code to move the printhead: G0 X10 Y10 variables can be used: G0 X{minx} Y{miny} The quad_gantry_level points are just the coordinates: 50,50 I cannot figure out how to use variables for those points: {minx},{miny} does not work for me.

[jagged mirage]

id think the klipper docs or source code would be the best place to look. ive never seen anyone use variables there

[long folio]

You can't use variables for any of that.

But nor does kamp

It accesses them on the fly via the printer object

And I don't see why you wouldn't be able to do the same

The only place you can use variables is inside gcode blocks, since they're the only part that gets run through jinja

[drifting current]

You can try it, the gcode command may take a "points: " parameter. Im not sure how you separate the point pairs in the parameter though.

Kamp just uses its variables, config details and print details to figure new bed mesh parameters. It then send a bed_mesh_calibrate min_mesh:x,y max_mesh:x,y points:x#,y# to klipper. Nothing super fancy.

You'll need to create a gcode call quad_gantry_level points:x1,y1 x2,y2 x3,y3 x4,y4 ...if that can work at all.

[neon bridge]

QGL does not take any parameters and you can't change the probe points on the fly.

[vagrant talon]

QGL can now take at least some parameters, but I'm not sure about the probe points.
e.g.

rename_existing: QUAD_GANTRY_LEVEL_BASE
gcode:
    QUAD_GANTRY_LEVEL_BASE horizontal_move_z=10 retry_tolerance=1.000
    QUAD_GANTRY_LEVEL_BASE horizontal_move_z=2```
works fine on my Beacon-enabled V2.

[drifting current]

That's a slick macro to speed up qgl with beacon. Love when it zooms the corners.

[vagrant talon]

All credit for it to Matt the designer of Beacon.