Happy Hare now can drive LEDs (NeoPixel/WS2812) on your MMU to provide both functional feedback as well as to add a little bling to your machine. Typically you would connect a string of neopixels (either descrete components or an LED strip, or combination of both if compatible contollers) to the neopixel output on the MCU that drives your MMU although this can be changed. What is important is that the first N LEDs of the chain must relate to the N gates of you MMU.
Typically the first LED would be for gate 0 but the order can be reversed by setting reverse_gate_order:1 in mmu_software.cfg. The optional N+1 LED is designed to drive an "exit" light. I.e. an indicator on or near the bowden output from your MMU. You can also add additional LED's after N+1 because they will be ignored by Happy Hare, but if you do, make sure you restrict your effects to that segment of the chain - don't try to control the first N+1 LEDs.
If you have run the Happy Hare installer it should have added a section to the end of your mmu_hardware.cfg that starts like this:
# MMU OPTIONAL NEOPIXEL LED SUPPORT ----------------------------------------------------------------------------------------
#
# Define neopixel LEDs for your MMU. The chain_count should match or be greater than your number of gates.
# Requires the installation of Julian Schill's awesome LED effect module: https://github.com/julianschill/klipper-led_effect
# LED index 1..N should be connected from gate #0 to gate #N
# LED index N+1 can optionally be connected to exit from MMU (like encoder in ERCF design)
#
[neopixel mmu_leds] # Cabinet neopixels (2x18)
pin: mmu:MMU_NEOPIXEL
chain_count: 10 # Number of gates + 1
color_order: GRBW # Set based on your particular neopixel specification
#
# Define LED effects for MMU gate. 'mmu_led_effect' is a wrapper for led_effect
...This section may be all commented out, if so and you wish to configure LEDS, uncomment the entire section and ensure that the MMU_NEOPIXEL pin is correctly set in the aliases in mmu.py and that the color_order matches your particular LED (don't mix type). Note that you must also install "Klipper LED Effects" plugin.
Note
Careful to note the [mmu_led_effect] definition. This is a simple wrapper around [led_effect] that will create the effect on the specified LED range (typically 1-N; N=number of gates) but also duplicate on each LED individually. This is especially useful on the MMU where you want per-gate effect.
Happy Hare LED effects are 100% implemented in mmu_software.cfg as macros so you can tweak if you desire. I would caution that you make sure you understand the logic before doing so, and in most cases you may just want to tweak the effects defined in mmu_hardware.cfg to customize. The macros work by intercepting changes of the Happy Hare's print state machine, changes in actions it is performing and changes to the gate_map containing gate status and filament color.
The default effects which are both functional as well as adding a little color are summerized here:
| State | LED at each Gate | Filament Exit (E.g. Bowden tube) |
|---|---|---|
| MMU Disabled | OFF | OFF |
| MMU Print State "initialization" | Bling - shooting stars (for 3 seconds) |
OFF |
| MMU Print State "ready" | default_gate_effect: - gate_status - filament_color - off |
default_exit_effect: - filament_color - on (white) - off |
| MMU Print State "printing" | default_gate_effect: - gate_status - filament_color - off |
default_exit_effect: - filament_color - on (white) - off |
| MMU Print State "pause_locked" (mmu pause) |
Strobe | Strobe |
| MMU Print State "paused" (after unlock) |
OFF except current gate Strobe |
Strobe |
| MMU Print State "completed" | Sparkle (for 20 seconds) |
default_exit_effect: - filament_color - on (white) - off |
| MMU Print State "cancelled" | default_gate_effect: - gate_status - filament_color - off |
default_exit_effect: - filament_color - on (white) - off |
| MMU Print State "error" | Strobe (for 20 seconds) |
Strobe (for 20 seconds) |
| MMU Print State "standby" | OFF | OFF |
| Action State "Loading" (whole sequence) |
OFF except current gate: Slow Pulsing White |
Slow Pulsing White |
| Action State "Unloading" (whole sequence) |
OFF except current gate: Slow Pulsing White |
Slow Pulsing White |
| Action State "Heating" | OFF except current gate: Pulsing Red |
Pulsing Red |
| Action State "Selecting" | Fast Pulsing White | OFF |
| Action State "Checking" | default_gate_effect: - gate_status - filament_color - off |
Fast Pulsing White |
| Action State "Idle" | default_gate_effect: - gate_status - filament_color - off |
default_exit_effect: - filament_color - on (white) - off |
Note
- MMU Print State is the same as the printer variable
printer.mmu.print_state - Action State is the same as the printer variable
printer.mmu.action - These are built-in functional "effects":
- filament_color - displays the static color of the filament defined for the gate from MMU_GATE_MAP (specifically
printer.mmu.gate_color_rgb). Requires you to setup color either directly or via Spoolman. - gate_status - dispays the status for the gate (printer.mmu.get_status): red if empty, green if loaded, orange if unknown
- filament_color - displays the static color of the filament defined for the gate from MMU_GATE_MAP (specifically
To change the default effect for the per-gate LEDs you edit default_gate_effect in the macro variables in mmu_software.cfg and for the default exit LED, you can edit default_exit_effect. These effects can be any named effect you define, the built-in functional defaults, "on", "off", or even an RGB color specification in the form red,green,blue e.g. 0.5,0,0.5 would be 50% intensity red and blue with no green.
Happy Hare also has an empirical command to control LEDs:
> MMU_LED
LEDs are enabled
Default exit effect: 'filament_color'
Default entry effect: 'gate_status'
Default status effect: 'filament_color'
ENABLE=[0|1] EXIT_EFFECT=[off|gate_status|filament_color|custom_color] ENTRY_EFFECT=[off|gate_status|filament_color|custom_color] STATUS_EFFECT=[off|on|filament_color|custom_color]You can change default effect or enable/disable. E.g. MMU_LED ENABLE=0 will turn off and disable the LED operation. Please note that similar to MMU_TEST_CONFIG changes made like this don't persist on a restart. Update the macro variables in mmu_software.cfg to make changes persistent.
The custom_color is not persisted and can be set with the command MMU_LED GATE=.. COLOR=... The color can be a w3c color name or RRGGBB value. One interesting use case is to set these colors to those defined in the gcode but the slicer using the example "placeholder" logic described in the gcode preprocessing section
The Happy Hare version of Klipperscreen has buttons to quickly "toggle" between gate_status and filament_color for the default gate effect...