v2-2566config VS Klipper-Adaptive-Meshing-Purging

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.

Try KAMP: https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging/tree/main

2) I am trying to install KAMP which I have working, but again this does not surive a reboot because the Klipper-Adaptive-Meshing-Purging folder (in the root directory) is deleted each time.

As far as I know, the KAMP is configured correctly. The installation was successful, I've followed the steps from the Github page, but I'm fairly certain that I'm missing something from my START_PRINT macro that's keeping it from working.

gcode: # KAMP https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging EXCLUDE_OBJECT_DEFINE SETUP_KAMP_MESHING DISPLAY_PARAMETERS=1 BED_MESH_CALIBRATE

I combined KAMP (https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging) with the MAX_DEVIATION option to SCREWS_TILT_CALCULATE and now before every print my printer checks the bed screws, and if they are off by more than 0.05mm it aborts the print. It then does an adaptive bed mesh and then purge. All together it doesn’t usually add much time, and I’ve been getting consistently good first layers.

This is what I use for my adaptive purge (and mesh) - https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging

But then again, just TAP with KAMP is already fine enough for pretty much everyone.

That is the one I used to use for a long time until KAMP came around.

taken from here: Klipper-Adaptive-Meshing-Purging/Adaptive_Mesh.cfg at main · kyleisah/Klipper-Adaptive-Meshing-Purging · GitHub and bed mesh config is the standard config found here Secondary Printer Tuning | Voron Documentation (vorondesign.com) with the uncomments made for the 350 build