klipper-led_effect VS common-macros

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.

You can override the base PAUSE with rename_existing and customize your PAUSE to your hearts content. You can see mine here: https://github.com/simplisticton/common-macros/blob/main/pause.cfg -- I wouldn't recommend using it verbatim, you'll want to understand what it is you're doing -- but that gives you the format of how to customize a macro.

The problem is in your relative move -- you need to do a little math to make sure your move isn't past the max. Check out my print_end macro for an example: https://github.com/simplisticton/common-macros/blob/main/print_end.cfg

You can check out the print_end macro for my printers here: https://github.com/simplisticton/common-macros/blob/main/print_end.cfg -- you can ignore most of the stuff at the bottom about checking & turning off particular fans, it's the movement stuff that's interesting.

When i had this issue it was a bad wire making intermittent contact. I wrote a gcode macro to print the probe status out every second so i could watch it trigger as i played with the cabling to help pinpoint the issue. You can see the macro here: https://github.com/simplisticton/common-macros/blob/main/equery.cfg

If you’re interested in a different approach, feel free to check out my heatsoak macro: https://github.com/simplisticton/common-macros/blob/main/heatsoak.cfg

If you don't have the proper macros, you can take a look at my configuration (the macros you need are pause.cfg and resume.cfg): https://github.com/simplisticton/common-macros

Feel free to check out my config for some useful macros (at least useful for me): https://github.com/simplisticton/common-macros