Recent content by Hagbard

Apparently due to some internal Klipper changes the endstops now have to be called "stepper_x, stepper_y and stepper_z" instead of just "x, y and z". "probe" stays unchanged. So define your effect like this and it should work: [led_effect sb_bed_homing] autostart: false frame_rate: 24 endstops...

It might be broken with the current Klipper version. Will look into it and come back to you.

Hi @Mr.P1nky1989, For an effect that reacts on the endstop you have to use the "homing" effect. This will light up when the endstops are pressed during homing or probing. Make sure the effect is active before you start homing (set autostart or use SET_LED_EFFECT) To test maybe try putting only...

Doesn't even have to be a Neopixel, can be any LED. you can even use a strip connected to a Heater output. Just configure it as [led]

I released version v0.0.10. Check it out and report any problems.

It is probably because you have a mesh active and moving in X and Y would need the Z axis to move then. Add a BED_MESH_CLEAR before the G0 and it should work.

'Neopixel update didn't succeed' most certainly is coming from too much load on the MCU. It means that it couldn't finish sending out the whole frame in time or it was interrupted by e.g. motor commands. For long chains or a lot of LEDs I recommend reducing the frame rate and using a dedicated...

Klipper LED effect This is the thread for the Klipper Plugin to run RGB effects on neopixels & co from within Klipper Check it out here. Latest release: Pre-Release v0.0.10 Highlights: Effects can now be stopped more easily Effects can now replace effects runnning on the same LEDs New...