klipper-led_effect VS Klipper-Adaptive-Meshing-Purging

Hello group. I have a question about neopixels. On my Marlin setup I defined Neopixel and Neopixel2. All LEDs ran off of the same pin. I was looking at this example. https://github.com/julianschill/klipper-led_effect/blob/master/docs/LED_Effect.md On this it shows 3 separate pins. So now I am confused. Can someone please explain to me how this works. I am just a beginner at this.

Neopixel Led’s: https://github.com/julianschill/klipper-led_effect

However, it is possible using klipper_led-effect

I'd suggest playing around with that until you feel like you are comfortable with it, and then if you want to start looking into animations and such you can check out klipper-led_effect. Just be warned (IMO) it's kind of confusing to configure.

These macros

LED Effects GitHUB

Yeah as a matter of fact klipper-led_effect literally just added this option yesterday.

Ok cool. What I'm trying to do is to add a Neopixel ring to the underside of my build plate (don't worry, I've already sorted out thermal insulation so they don't burn) and have it change colour automatically based off certain parameters. I want it white and breathing slowly when it turns on, changing from blue to red while it's heating and between 30⁰ and 60⁰, then breathing red while it prints. Finally it would turn green upon the print completing, and then go in reverse order from red to blue and back to white as the bed cools and lands below 30⁰. I've been researching this shit all day and have started to build a led_progress.cfg as instructed by this page, however, according to this page I can have all kinds of control over the lights.

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