Jump to content

A good tutorial for installing chamber lights?


Recommended Posts

Has anyone found a good tutorial for installing chamber lights?

I want to put chamber lights in my 2.4 R2. I have a BTT octopus board and would like to use the Neopixel port so I can control the leds via Klipper.

I read somewhere that I need to put a 100 ohm resistor between the board and the first string of led's

I am looking for a tutorial so I don't screw my board up. I hate replacing parts that I don't need to.

 

Thankx.

Link to comment
Share on other sites

Depends on what type of LED you are installing. If it is a plain 24V white LED strip, then you can connect it to Octopus board via HE1 and use it as a pin configuration to turn it on or off , or even the brightness. )This in my opinion is the easiest way of configuring chamber lights that just turn on or off)

As example this is the configuration for my Chamder lights connected this way:

 

############################################
#  Chamber LED
###########################################

## Chamber Lighting - HE1 Connector (24V)
[output_pin caselight]
pin: PA3
pwm:true
shutdown_value: 0
value:0.25                             #the brightness at startup (0-1)
cycle_time: 0.01

#############################################

 

If you are using a neo pixel chain, it needs to be attached to 5V, GND and a signal pin - either your neopixel port (J37 ) - pin PB0

 

image.thumb.png.ec97ae3fd8bfd904dcdc1f645358a264.png 

 

 or one of the spare diagnostic ports. (J28 - pin PG12) Note the diagnostic pins only supply 3.3V, thus if you use this you need to get 5V from a spare pin on the board.(eg J43 which is the BLTouch connector) You can obviously also use the BLTouch port (J43) to connect 5V, GND and signal if it is not used- will be Pin PB6 in this case)

image.thumb.png.4b8f43175a3f9c02e8ad02e692045f89.png

However the 5V power is the important part not to damage your board or Neopixel strip. Make triple sure you do NOT swap 5V and Gnd - this will damage your board.

This would be an example of connecting a neopixel strip:

 

#####################################################################
#   Neopixel cotrol
####################################################################

#[neopixel Chamber_lights]
pin: PB6                             # the diagnostic pin on the Octopus board it is connected to (BLTouch port - connector J43)
chain_count: 16                 # The amount of neo pixels in the strip
color_order: GRB               # The type of neo pixel strip, e.g. RGBW GRB, RGB
initial_RED: 0.0                  # The next 4 values are for the color you want the lights to start up with. 
initial_GREEN: 0.0             # Setting all the lights to 0, will turn them off
initial_BLUE: 0.0
initial_WHITE: 1.0             # Lights will be white when printer turns on

 

Hope this helps

Happy Holidays

 

 

  • Voron FTW! 1
Link to comment
Share on other sites

Do you have the Stealthburner with LEDs also?

I have my SB tool head LEDs on the Octopus NeoPixel port, and my case lights using the BL Touch port. It's perfect for the use, a 5V, GND, and signal pin. Go check my Github config file. caselight is on the BL Touch port, sb_leds is on the NeoPixel port. You cna see the definitions & how they are called. BTW, I am using the klipper-led-effect library.

Link to comment
Share on other sites

On 12/25/2022 at 10:13 PM, mvdveer said:

Depends on what type of LED you are installing. If it is a plain 24V white LED strip, then you can connect it to Octopus board via HE1 and use it as a pin configuration to turn it on or off , or even the brightness. )This in my opinion is the easiest way of configuring chamber lights that just turn on or off)

As example this is the configuration for my Chamder lights connected this way:

############################################
#  Chamber LED
###########################################

## Chamber Lighting - HE1 Connector (24V)
[output_pin caselight]
pin: PA3
pwm:true
shutdown_value: 0
value:0.25                             #the brightness at startup (0-1)
cycle_time: 0.01

#############################################

If you are using a neo pixel chain, it needs to be attached to 5V, GND and a signal pin - either your neopixel port (J37 ) - pin PB0

image.thumb.png.ec97ae3fd8bfd904dcdc1f645358a264.png 

 or one of the spare diagnostic ports. (J28 - pin PG12) Note the diagnostic pins only supply 3.3V, thus if you use this you need to get 5V from a spare pin on the board.(eg J43 which is the BLTouch connector) You can obviously also use the BLTouch port (J43) to connect 5V, GND and signal if it is not used- will be Pin PB6 in this case)

image.thumb.png.4b8f43175a3f9c02e8ad02e692045f89.png

However the 5V power is the important part not to damage your board or Neopixel strip. Make triple sure you do NOT swap 5V and Gnd - this will damage your board.

This would be an example of connecting a neopixel strip:

#####################################################################
#   Neopixel cotrol
####################################################################

#[neopixel Chamber_lights]
pin: PB6                             # the diagnostic pin on the Octopus board it is connected to (BLTouch port - connector J43)
chain_count: 16                 # The amount of neo pixels in the strip
color_order: GRB               # The type of neo pixel strip, e.g. RGBW GRB, RGB
initial_RED: 0.0                  # The next 4 values are for the color you want the lights to start up with. 
initial_GREEN: 0.0             # Setting all the lights to 0, will turn them off
initial_BLUE: 0.0
initial_WHITE: 1.0             # Lights will be white when printer turns on

Hope this helps

Happy Holidays

My next question is: How many Led's can you have in a chain?

I have 79? Is that going to be a problem?

 

Thanbx for all you help.

 

Link to comment
Share on other sites

5 hours ago, Raymond-Canada said:

My next question is: How many Led's can you have in a chain?

Don’t think there is a limit.

see https://forums.adafruit.com/viewtopic.php?f=47&t=87117

5 hours ago, Raymond-Canada said:

I have 79? Is that going to be a problem?

Don’t think so from what I have researched

Link to comment
Share on other sites

22 minutes ago, mvdveer said:

Don’t think there is a limit.

Everything has a limit 😉 Power is probably the most likely limit. Each LED will consume about 60mA (that's an estimate as different colours consume varying amounts of power). So the  79 LEDS will draw around 4.7A  if they were all turned on simultaneously. That's not excessive but given the other power draws on the board it might be a challenge (think fans, hotends, beds, etc).

  • Like 1
Link to comment
Share on other sites

I tried to do this as simple as I could. Disconnected all but 20 led's.

I double checked everything and it is all wired up correctly.

As soon as I save the printer.cfg and restart I get a error. And it will not let me continue until I go back into the Printer.cfg and comment out the led control. Is there something that I missed? All I did was copy and paste the above script. Change the amount of led's and the type of led's. The error I am getting says something about mcu temp. But as you can see I have the max temp set to 100. I can't tell if it is hitting the max temp and shutting down, I don't get that far. Any idea what I am doing wrong?

IMG_4009.JPG

IMG_4008.JPG

Link to comment
Share on other sites

It looks like Klipper is complaining about your temperature sensor on the mcc and not the LED's. Your [temperature_sensor mcu_temp] references a pre-defined sensor "temperature_mcu". What is under that section. I suspect the issue may be there. 

Another issue may be that the line [output_pin caselight] section may not have been active and the pin for this was read by Klipper as belonging to [temperature_sensor mcu_temp] or the pin in [neopixel Chamber_lights] is read. In the above you do not have [neopixel Chamber_lights] uncommented as there is still a # in front of it.

What we can try:

Ensure [output_pin caselight] , if you use this and [neopixel Chamber_lights]  has no # in front of it.

If that fails,

As a trial, comment out both the defined sensor temperature-mcu as well as the [temperature_sensor mcu_temp], leave the LED controls uncommented and see how the LED's react. 

Let me know how you go

  • Like 1
Link to comment
Share on other sites

It's definitely the '#' infront of the [neopixel Chamber_lights] section. That's basically commented out so Klipper is not realising there is a new section and is interpreting the lines below (pins:, chain_count:, etc) as being part of the previous section which defined the MCU temperature.

Link to comment
Share on other sites

4 hours ago, smirk said:

It's definitely the '#' infront of the [neopixel Chamber_lights] section. That's basically commented out so Klipper is not realising there is a new section and is interpreting the lines below (pins:, chain_count:, etc) as being part of the previous section which defined the MCU temperature.

all-of-this-pointing.gif.bc615a31ef3012b63eab0b3b946a770f.gif

Link to comment
Share on other sites

21 hours ago, smirk said:

It's definitely the '#' infront of the [neopixel Chamber_lights] section. That's basically commented out so Klipper is not realising there is a new section and is interpreting the lines below (pins:, chain_count:, etc) as being part of the previous section which defined the MCU temperature.

Thank you so much... That was the problem. After reading your post it made sense on why I was getting that error. Sometimes it just needs another persons point of view to point out the obvious.

Now the next thing I want to try and do is be able to turn them on and off via  the front screen. I don't really care about changing the color. They just don't need to be on 24/7. That I think will require a lot more digging for answers. I know I can turn it down via the color control with in Fluid. But I don't see an option to just flip a switch and turn the off.

 

Link to comment
Share on other sites

2 hours ago, Raymond-Canada said:

Now the next thing I want to try and do is be able to turn them on and off via  the front screen.

Mainsail has this build in - see attached:

image.thumb.png.8478cc5ed783eb35fae40890f2788a52.png

This shows my Chamber LED's are turned off (black dot)  and the SB LED's are red (red)  - which is my printing status.

Once I turn them on by clicking on the black dot and sliding it all the way to white, the lights are on:

image.thumb.png.6a12bbfcf35939b570dbdd505023b614.png

Hope this helps

 

Link to comment
Share on other sites

4 hours ago, mvdveer said:

Mainsail has this build in - see attached:

image.thumb.png.8478cc5ed783eb35fae40890f2788a52.png

This shows my Chamber LED's are turned off (black dot)  and the SB LED's are red (red)  - which is my printing status.

Once I turn them on by clicking on the black dot and sliding it all the way to white, the lights are on:

image.thumb.png.6a12bbfcf35939b570dbdd505023b614.png

Hope this helps

Thankx, I got that part figured. Fluidd is the same. My printer is in the basement and the computer is on the second floor. I was hoping to be able to control through the printer. That way if i was down stairs I could just turn them on and have a look at what is printing then turn them off. I guess that is what a phone is for.

 

Thank you all for the help and suggestions. This community is great!

 

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...
On 12/26/2022 at 12:13 PM, mvdveer said:

Depends on what type of LED you are installing. If it is a plain 24V white LED strip, then you can connect it to Octopus board via HE1 and use it as a pin configuration to turn it on or off , or even the brightness. )This in my opinion is the easiest way of configuring chamber lights that just turn on or off)

As example this is the configuration for my Chamder lights connected this way:

############################################
#  Chamber LED
###########################################

## Chamber Lighting - HE1 Connector (24V)
[output_pin caselight]
pin: PA3
pwm:true
shutdown_value: 0
value:0.25                             #the brightness at startup (0-1)
cycle_time: 0.01

#############################################

If you are using a neo pixel chain, it needs to be attached to 5V, GND and a signal pin - either your neopixel port (J37 ) - pin PB0

image.thumb.png.ec97ae3fd8bfd904dcdc1f645358a264.png 

 or one of the spare diagnostic ports. (J28 - pin PG12) Note the diagnostic pins only supply 3.3V, thus if you use this you need to get 5V from a spare pin on the board.(eg J43 which is the BLTouch connector) You can obviously also use the BLTouch port (J43) to connect 5V, GND and signal if it is not used- will be Pin PB6 in this case)

image.thumb.png.4b8f43175a3f9c02e8ad02e692045f89.png

However the 5V power is the important part not to damage your board or Neopixel strip. Make triple sure you do NOT swap 5V and Gnd - this will damage your board.

This would be an example of connecting a neopixel strip:

#####################################################################
#   Neopixel cotrol
####################################################################

#[neopixel Chamber_lights]
pin: PB6                             # the diagnostic pin on the Octopus board it is connected to (BLTouch port - connector J43)
chain_count: 16                 # The amount of neo pixels in the strip
color_order: GRB               # The type of neo pixel strip, e.g. RGBW GRB, RGB
initial_RED: 0.0                  # The next 4 values are for the color you want the lights to start up with. 
initial_GREEN: 0.0             # Setting all the lights to 0, will turn them off
initial_BLUE: 0.0
initial_WHITE: 1.0             # Lights will be white when printer turns on

Hope this helps

Happy Holidays

Why when I follow this setup instead getting white light in every led in the chain. I got Blue, Reb, Green, Blank in order.

In order to have white light I have to set all color to 1.0.

I set to WRGB, RGBW, WGRB, GRBW. There is no different only order of the color changed.

I have 36 chain_count and set to pin: PB0.

Link to comment
Share on other sites

7 minutes ago, Pradit said:

Why when I follow this setup instead getting white light in every led in the chain. I got Blue, Reb, Green, Blank in order.

In order to have white light I have to set all color to 1.0.

I set to WRGB, RGBW, WGRB, GRBW. There is no different only order of the color changed.

I have 36 chain_count and set to pin: PB0.

Now when I change to RGB, I could set entire stripe with the same color. Again with white i have to set all rgb to 1.0.

The initial_white I had no effect what value I put.

Link to comment
Share on other sites

Your case light strips are WS2812B type, correct? Those are RGB lights with no white element. The round PCB ones that are specced for the Stealthburner are RGBW with the white element. That probably explains the issue you were seeing until you defined them as RGB. To get white, just set all three to 1.0

As a point of reference, here's the hardware setup I currently have:

[neopixel caselight]
pin: PB6
chain_count: 36
color_order: GRB
initial_RED: 0.0
initial_GREEN: 0.0
initial_BLUE: 0.5

[neopixel sb_leds]
pin: PB0
chain_count: 3
color_order: GRBW
initial_RED: 0.0
initial_GREEN: 0.0
initial_BLUE: 1.0
initial_WHITE: 0.0

caselight are typical WS2812B RGB strips on the BL Touch port. The sb_leds are the spec round PCB NeoPixels on the NeoPixel port.

 

  • Like 1
Link to comment
Share on other sites

2 minutes ago, claudermilk said:

Your case light strips are WS2812B type, correct? Those are RGB lights with no white element. The round PCB ones that are specced for the Stealthburner are RGBW with the white element. That probably explains the issue you were seeing until you defined them as RGB. To get white, just set all three to 1.0

As a point of reference, here's the hardware setup I currently have:

[neopixel caselight]
pin: PB6
chain_count: 36
color_order: GRB
initial_RED: 0.0
initial_GREEN: 0.0
initial_BLUE: 0.5

[neopixel sb_leds]
pin: PB0
chain_count: 3
color_order: GRBW
initial_RED: 0.0
initial_GREEN: 0.0
initial_BLUE: 1.0
initial_WHITE: 0.0

caselight are typical WS2812B RGB strips on the BL Touch port. The sb_leds are the spec round PCB NeoPixels on the NeoPixel port.

Yes its we2812b. I have pb0 available on my octopus pro.

Im checking your github and installing the lib.

 

Thank you.

Link to comment
Share on other sites

No problem, have fun with setting up the effects.

I mainly set mine up on different strips for convenience and because at the time Klipper could not run RBG and RGBW on the same definition. That's changed since then. In my upgrades coming soon (final parts--I think--arriving today), I'm adding the Rainbow Barf Stealthburner logo to the new toolhead along with the spec ones for the nozzle.

  • Voron FTW! 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...