Neopixel LED help

Basic Information:

Printer Model: Voron
MCU / Printerboard:Octopus
Host / SBC RPi 4
klippy.log
klippy.log (586.5 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I’ve been trying to get the Neopixel to light up on the tool head of the Voron without much luck.
The question do you need to uncomment the STATUS_READY line etc to activate it? I have tried this but give s an error’unable to parse!
[stealthburner_leds.cfg|attachment]
The toolhead is connected via Canbus ebb sb2209. All other functions work as expected!

(upload://i4spw0nmWiz034jBpw7rPZZQgpd.cfg) (10.0 KB)


klippy.log (586.5 KB)

Can I ask why you didn’t attach you klippy.log to your post, even when you were clearly instructed to and didn’t bother to delete the template message to do so?

I took a quick look at your stealthburner_leds.cfg and you seem to a toolhead controller (EBBCan) which isn’t included in your description of your 3D printer so there’s no way to analyze your system and give you an answer. There’s also a ton of macros in the file that I haven’t bothered going through that may affect the initial operation.

Could you please go back, provide ALL the information that you were asked for as well as anything else that would held describe your 3D printer.

We can’t psychically reach out and examine your 3D printer, we need you to provide the information requested as well as anything that isn’t obvious.

Very sorry I’ve now included the klippy.log

You have something funny happening in your stealthburner_leds.cfg file.

When I look at the start of stealthburner_leds.cfg I see:

[neopixel sb_leds]
pin: EBBCan:gpio16 #   The pin connected to the neopixel. This parameter must be provided.
chain_count: 3
#   The number of Neopixel chips that are "daisy chained" to the
#   provided pin. The default is 1 (which indicates only a single
#   Neopixel is connected to the pin).
color_order: GRBW
#   Set the pixel order required by the LED hardware. Options are GRB,
#   RGB, GRBW, or RGBW. The default is GRB.
initial_RED: 1.0
initial_GREEN: 0.6
initial_BLUE: 1.0
initial_WHITE: 0.6
#   Sets the initial LED color of the Neopixel. Each value should be
#   between 0.0 and 1.0. The WHITE option is only available on RGBW
#   LEDs. The default for each color is 0.#

# Most configuration for the macros can be done by modifying the variables in the _sb_vars macro
# at the start of this file.

##########
# MACROS #
##########

# The following status macros are available (these go inside of your macros):
#
#    STATUS_READY
#    STATUS_OFF
#    STATUS_BUSY
#    STATUS_HEATING
#    STATUS_LEVELING
#    STATUS_HOMING
#    STATUS_CLEANING
#    STATUS_MESHING
#    STATUS_CALIBRATING_Z
#
# With additional macros for basic control:
#
#    SET_NOZZLE_LEDS_ON
#    SET_LOGO_LEDS_OFF
#    SET_NOZZLE_LEDS_OFF
#
# Contributed by Voron discord users wile.e, Tetsunosuke, and etherwalker


[gcode_macro _sb_vars]

Which looks fine, but when I look at your klippy.log for the same section (at the end of the klippy.log there is:

[neopixel sb_leds]
pin = EBBCan:gpio16
chain_count = 3
color_order = GRB
initial_red = 1.0
initial_green = 0.6
initial_blue = 1.0
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	STATUS_READY

[gcode_macro _sb_vars]

For some reason, your initial_WHITE: 0.6 statement gets trashed and STATUS_READY, which should be commented out appears.

I think you have an invalid (non visible) ASCII character somewhere in your stealthburner_leds.cfg file after the initial_BLUE: 1.0 statement. The other issue might be that you can’t access linked pins (ie the EBBCan:gpio16) from inside an included file (that rings a bell in the back of my brain as a potential problem).

I’d recommend comenting out the [include stealthburner_leds.cfg] in your printer.cfg and then putting in the statement:

[neopixel sb_leds]
pin: EBBCan:gpio16 #   The pin connected to the neopixel. This parameter must be provided.
chain_count: 3
#   The number of Neopixel chips that are "daisy chained" to the
#   provided pin. The default is 1 (which indicates only a single
#   Neopixel is connected to the pin).
color_order: GRBW
#   Set the pixel order required by the LED hardware. Options are GRB,
#   RGB, GRBW, or RGBW. The default is GRB.
initial_RED: 1.0
initial_GREEN: 0.6
initial_BLUE: 1.0
initial_WHITE: 0.6
#   Sets the initial LED color of the Neopixel. Each value should be
#   between 0.0 and 1.0. The WHITE option is only available on RGBW
#   LEDs. The default for each color is 0.#

# Most configuration for the macros can be done by modifying the variables in the _sb_vars macro
# at the start of this file.

and see what happens. From there you can check to see if the EBBCan:gpio16 parameter in an included file is a problem and then go from there.

Sorry for the late reply. I tried your suggestion, but still no ‘light’
I did start a print with the original setup this morning and the ‘voron’ light lit up whilst the hotend was heating but then went off and never lit again nor did the other two lights at the workface?

Did you look at the updated klippy.log and see if the blank area after initial_blue is still there?

It has a value of 1.0
klippy.log.zip (1.5 MB)

Just looked at the new klippy.log - the [neopixel sb_leds] statement looks right:

[neopixel sb_leds]
pin = EBBCan:gpio16
chain_count = 3
color_order = GRBW
initial_red = 1.0
initial_green = 0.6
initial_blue = 1.0
initial_white = 0.6

[gcode_macro _sb_vars]
variable_colors = {
	'logo': {

Can you describe exactly what happened?

From you previous post:

I did start a print with the original setup this morning and the ‘voron’ light lit up whilst the hotend was heating but then went off and never lit again nor did the other two lights at the workface?

That sounds like it worked initially and then turned off when the print/homing started - correct?

If that’s the case, then you’re going to have to start looking through the macros and figure out where the problem lies. To do that, my recommendation would be to comment out the macros until you see the Neopixels staying on and figure out what’s happening from there.

Sorry, that’s a really labour intensive process but I don’t think there’s a better one.

Yes, the ‘voron’ light lit up only in red then went out after heating. After that no other lights came on during the mesh or printing process.
I did run another print but that time the light never came on during the initial heating process

Then you’re going to have to go through the macros and figure out what’s going on.

Where did you get them? Does the author offer any kind of support?

My suggested process for you:

  1. Comment out the [include stealthburner_leds.cfg] statement and see if the NeoPixel LEDs come up and stay up through the print.
  2. Go through and individually comment out specific macros (status_leveling would probably be a good one to start at if the LEDs are going out after heating) and see what happens.
  3. When you seem to have a macro that is exhibiting a problem, reply back here and we’ll see if we can help you.

As I said, it’s gonna be a labour intensive process unless the author of the macros can offer support. Sorry.

I have now sorted the problem. I’ve ran 3 wires from the boards bltouch header using the gnd/5v/pb6(100ohm resistor) through the umbilical to the head to the original 3 neopixels on the stealthburner.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.