klipper-macros VS print_area_bed_mesh

Custom G-Code: derived from stuff here: https://github.com/jschuh/klipper-macros

Klipper macros are amazingly powerful, and one of my favorite things about the firmware. Learn how they work, and the world is your oyster.

Very bad, as I have installed a macro library https://github.com/jschuh/klipper-macros and cannot edit the macros which are read-only.Even if I edit them they update themselves from the reporitory, so it would be useless

After that install klipper-macro script by following this YouTube video.

i installed and configured klipper for my printer, i installed a macro pack (https://github.com/jschuh/klipper-macros) but the thing i don't know how to do is set the start Gcode of ideamaker. The creator just explains how to set it on prusa slicer and cura.For example on prusa slicer it would be like this:

Using klipper-macros has been super useful

In https://github.com/jschuh/klipper-macros/blob/main/layers.cfg they have a "gcode_at_layer" macro but I don't want to necessarily import all those macros into my Klipper.

I thought the Klipper version was outdated or missing feature when I tried installing this : https://github.com/jschuh/klipper-macros It simply would not work. I tried a few thing (like implanting some command that were missing) it worked at first until the purge line was finished, then it would pop an error and stop mid way.

I ended up using the klipper macros here: https://github.com/jschuh/klipper-macros rather than writing my own as they're pretty full featured, well documented and allow for some level of acceleration control from the slicer (not Klipper's intention, but useful sometimes).

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.