klipper-led_effect VS sonar

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.

[server] host: 0.0.0.0 port: 7125 klippy_uds_address: /home/biqu/printer_data/comms/klippy.sock [authorization] trusted_clients: 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 cors_domains: *.lan *.local *://localhost *://localhost:* *://my.mainsail.xyz *://app.fluidd.xyz [octoprint_compat] [history] [update_manager] channel: dev refresh_interval: 168 [update_manager mainsail-config] type: git_repo primary_branch: master path: ~/mainsail-config origin: https://github.com/mainsail-crew/mainsail-config.git managed_services: klipper [update_manager mainsail] type: web channel: stable repo: mainsail-crew/mainsail path: ~/mainsail [update_manager crowsnest] type: git_repo path: ~/crowsnest origin: https://github.com/mainsail-crew/crowsnest.git install_script: tools/install.sh # Sonar update_manager entry [update_manager sonar] type: git_repo path: ~/sonar origin: https://github.com/mainsail-crew/sonar.git primary_branch: main managed_services: sonar install_script: tools/install.sh [update_manager timelapse] type: git_repo primary_branch: main path: ~/moonraker-timelapse origin: https://github.com/mainsail-crew/moonraker-timelapse.git managed_services: klipper moonraker [update_manager KlipperScreen] type: git_repo path: ~/KlipperScreen origin: https://github.com/jordanruthe/KlipperScreen.git env: ~/.KlipperScreen-env/bin/python requirements: scripts/KlipperScreen-requirements.txt install_script: scripts/KlipperScreen-install.sh managed_services: KlipperScreen

Mainsail has a daemon tool to help fix the issue after which I used seemed to make thing much better… it’s called sonar https://github.com/mainsail-crew/sonar

I actually used sonar (https://github.com/mainsail-crew/sonar) and have not been disconnected for days... Kinda a hacky way to do it, but it works.

Set up Sonar, it will keep your wifi connection active so this doesn't happen.

Sonar

[server] host: 0.0.0.0 port: 7125 # The maximum size allowed for a file upload (in MiB). Default 1024 MiB max_upload_size: 1024 # Path to klippy Unix Domain Socket klippy_uds_address: ~/printer_data/comms/klippy.sock [file_manager] # post processing for object cancel. Not recommended for low resource SBCs such as a Pi Zero. Default False enable_object_processing: False [authorization] cors_domains: https://my.mainsail.xyz http://my.mainsail.xyz http://*.local http://*.lan trusted_clients: 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 # enables partial support of Octoprint API [octoprint_compat] # enables moonraker to track and store print history. [history] # this enables moonraker announcements for mainsail [announcements] subscriptions: mainsail # this enables moonraker's update manager [update_manager] refresh_interval: 168 enable_auto_refresh: True [update_manager mainsail] type: web channel: stable repo: mainsail-crew/mainsail path: ~/mainsail [update_manager mainsail-config] type: git_repo primary_branch: master path: ~/mainsail-config origin: https://github.com/mainsail-crew/mainsail-config.git managed_services: klipper ### moonraker-timelapse ### Don't forget to include timelapse.cfg to your printer.cfg ### Uncomment to enable moonraker-timelapse #[update_manager timelapse] #type: git_repo #primary_branch: main #path: ~/moonraker-timelapse #origin: https://github.com/mainsail-crew/moonraker-timelapse.git #managed_services: klipper moonraker #[timelapse] ### Directory where the generated video will be saved #output_path: ~/timelapse/ ### Directory where ffmpeg is installed #ffmpeg_binary_path: /usr/bin/ffmpeg # Crowsnest update_manager entry [update_manager crowsnest] type: git_repo path: ~/crowsnest origin: https://github.com/mainsail-crew/crowsnest.git managed_services: crowsnest install_script: tools/install.sh # Sonar update_manager entry [update_manager sonar] type: git_repo path: ~/sonar origin: https://github.com/mainsail-crew/sonar.git primary_branch: main managed_services: sonar install_script: tools/install.sh [update_manager timelapse] type: git_repo primary_branch: main path: ~/moonraker-timelapse origin: https://github.com/mainsail-crew/moonraker-timelapse.git managed_services: klipper moonraker [timelapse] ## Following basic configuration is default to most images and don't need ## to be changed in most scenarios. Only uncomment and change it if your ## Image differ from standart installations. In most common scenarios ## a User only need [timelapse] in there configuration. #output_path: ~/timelapse/ ## Directory where the generated video will be saved #frame_path: /tmp/timelapse/ ## Directory where the temporary frames are saved #ffmpeg_binary_path: /usr/bin/ffmpeg ## Directory where ffmpeg is installed

Unparsed config option 'origin: https://github.com/mainsail-crew/sonar.git' detected in section [update_manager sonar]. 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.

Otherwise, you can use a tool like Sonar to keep the wifi connection alive.