LED Status Actions
Regarding the LED status control built into RatOS, can anyone point me to the portion of code where the status changes are triggered? I see the variables ( https://os.ratrig.com/docs/configuration/led/#status-colors ) which seem to be driven from the led_control.cfg ( https://github.com/Rat-OS/RatOS-configuration/blob/v2.1.x/macros/led_control.cfg ), but I'm not quite sure about those _LED* gcode macros... are they some type of default status changes that just happen in the background in Klipper?
In case the big "why" question comes up - I'm running a VERY old version of RatOS (v2.0.0.8) and don't want to rebuild a new config from the ground up since I have so many customizations, and the printer is running very well as it is. I just added some LED strips and want to utilize them for some visual feedback, so I just want to understand how the event triggers occur and how I can tap into them.
4 Replies
I'm also thinking that maybe I should just ignore all this and that the Klipper-LED_Effect scripts would take care of it all? https://github.com/julianschill/klipper-led_effect/tree/master
They are called from the macros that are relavent to the status color. for example in macros.cfg under [gcode_macro START_PRINT] there is an entry of # visual feedback
_LED_START_PRINTING.
Ahhh, thanks for the info... now that I look into macros.cfg, I see that all of the LED actions are called from those other macros rather than inherited from Klipper
Guess I'll have to either edit all that into my setup or look into the LED_Effect add-on and see if that monitors statuses on it's own...
https://github.com/julianschill/klipper-led_effect
GitHub
GitHub - julianschill/klipper-led_effect: LED effects plugin for kl...
LED effects plugin for klipper. Contribute to julianschill/klipper-led_effect development by creating an account on GitHub.