v2-2566config VS print_area_bed_mesh

Klipper macros use parameters to pass arguments. Check out my print_start macro here for how it works: https://github.com/simplisticton/v2-2566config/blob/main/print_start.cfg -- as you can see, my macro accepts BED or BED_TEMP, EXTRUDER or EXTRUDER_TEMP, and MATERIAL as parameters which can be passed in from the slicer. Logical defaults are provided if the value isn't supplied. The reason it allows for X or X_TEMP is to make it compatible with an automated gcode generator script, so that's not relevant for everyone.

Take a look at my config. I have a temperature monitor routine that turns on fans in certain situations. https://github.com/simplisticton/v2-2566config

You can see my print_start (along with the rest of my config) here to get some ideas: https://github.com/simplisticton/v2-2566config

Hey, I've got the same sensor working correctly, you can see my config here: https://github.com/simplisticton/v2-2566config

Take a look at my print_start macro: https://github.com/simplisticton/v2-2566config/blob/main/print_start.cfg -- the line to include in the slicer is in the comment at the top.

Yes -- I wired a passive speaker to the 12864 display port (since I wasn't using it for anything else). Here's the config for the Octopus: https://github.com/simplisticton/v2-2566config/blob/main/beeper.cfg (one leg of the speaker is wired to EXP1_1, the other to GND).

Yes indeedy. If you want to see my config, it's in GitHub: https://github.com/simplisticton/v2-2566config but it's for a Voron 2.4 so I don't know how useful it'll be for you. It shows how I have things configured though, for inspiration.

If you want an example of how to manage macros with LEDs and a bunch of other plugins and custom stuff, take a look at my configs: https://github.com/simplisticton/v2-2566config. I'm not saying I did anything right or special, but my config does work :)

If you're interested, my config is posted to Github, feel free to take a look and ask questions: https://github.com/simplisticton/v2-2566config

You can check out my config at https://github.com/simplisticton/v2-2566config -- I don't use a slicer routine other than to call print_start.

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.