strayr-k-macros VS print_area_bed_mesh

I use this macro to do square the gantry against the top frame You should only do this if you have adjustable current for your stepper drivers ([tmcxxxx] sections in your config for stepper_z and stepper_z1 drivers) You'll also want to make sure your stepper_z.position_max is just before the gantry would contact the frame.

I've added it into my LCD menu https://github.com/strayr/strayr-k-macros/blob/main/improved_menu.cfg, but beware, some of the menuitems pull in macros from other parts of the package. You may find the whole lot useful, read the docs. it needs some updating and perhaps the probe menu splitting into a standalone file.

I use u/strayr-k's macro for this: mechanical_level_tmc2209.cfg

I always use strayrr-k's mechanical gantry calibration macro to tram the gantry against the frame before using screws_tilt to level the bed.

Last note, the G34 macro I use is this one. Works really well on my dual Z setup (one driver for both steppers). I've noticed my Ender3 X gantry likes to set itself just a bit off-kilter when steppers are disabled, so I run a G34 at every startup to ensure it stays level as long as the motors are enabled.

you can try this https://github.com/strayr/strayr-k-macros/blob/main/M204.cfg but it can cause crashes if you have gcode with lots of accel changes, I encountered this on small mmu prints with lots of very short perimeters but it might be ok.

I use mech_gantry_cal.cfg a lot, but that only applies if you use dual z steppers and dual z drivers. This macro will bump the gantry against the z_max to straighten it against the frame and eliminate any drift between the drivers.

A macro that only probes the bed area that you are printing in aka dynamic bed mesh probing! https://github.com/Turge08/print_area_bed_mesh

Well i just wanted to use this bed mesh plugin https://github.com/Turge08/print_area_bed_mesh

print_area_bed_mesh GitHUB

Unparsed config option 'origin: https://github.com/Turge08/print_area_bed_mesh.git' detected in section [update_manager print_area_bed_mesh]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Gives this a try, it wont fix your problem but auto adjust your probed area to your print area. https://github.com/Turge08/print_area_bed_mesh

If you want to get fancy with it, check out this little gem: print_area_bed_mesh

By print_size_mesh, do you mean this macro? https://github.com/Turge08/print_area_bed_mesh

My main reason to start using it was because of a macro (not this one, but it's a better one) that only generates a mesh for the area you will be printing in. It can also reuse meshes if the new mesh is the same size or smaller than the last. Of course you can just generate one mesh and run with it for awhile, but I like having as fresh a mesh as I can and this saves time.