Neopixel SB issue after update

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: sb2209, MantaMP8
Host / SBC CB1
klippy.log

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:

Hi after update klipper in my new voron I had issue with stealthburner led not respond correctly. After some tries today I found an user with same issue and he check the signal data with oscilloscope and the data sheet of lens and change these value in neopixel.c

  • Corrected them according to the WS2812 data sheet:
    #define PULSE_LONG_TICKS nsecs_to_ticks(700)
    #define PULSE_SHORT_TICKS nsecs_to_ticks(350)

I tried too and now it WORKS correctly.
I flashed klipper in June for first time and led on SB works well. Last week I update klipper and issue came out

klippy.log (120.6 KB)

…

2

Not sure about this. It is my understanding that

  1. The Neopixel stuff is quite a zoo of different specifications and thus there is no common truth between the different chips that are summarized under “Neopixels”
  2. Nothing was changed in the recent times that would affect this
3

yep, i understand the zoo. Maybe is possible to add these parameters in the neopixel config? I tried all thing in these days and I think to have a malfunctioning led chain. but today I found this solutions that work.

4

Where are you getting your Neopixels?

I’ve basically kept to Adafruit (from DigiKey) but I have never had a problem - I’ve bought a few off of Amazon as well as AliExpress. All of my printers are running them and, in several cases, two strings of them.

My Voron is still running with an Octopus Pro with two six NeoPixel strings (PCBs actually) and but I’m using an SB2209 toolhead controller with a two NeoPixel string without any issues since I set up the printer.

Two of my other CoreXYs are running with Manta M8Ps with multiple NeoPixel Strings as well (one uses a CM4 and one uses a CB1). No problems here either.

Could I ask that you share your klippy.log? That was asked for when you generated the post but you didn’t include it. There may be something in there that’s a clue to what’s happening.

5

Tomorrow i’ll upload log file. I’m building the voron magicphoenix kit so i not know where he gets leds.
Mp8+sb2209.

6

i uploaded log
klippy.log (120.6 KB)

7

Please always to your last post.

It can be quite tedious to scroll back just for a log.

See: supporters (and all other frequent viewers) always get the posts presented they have not seen yet.

8

Oh damn, sorry. I attached log in my last post. Sorry guys

1 Like
9

If you alter only PULSE_SHORT_TIME to 300ns does it still work?

#define PULSE_LONG_TICKS  nsecs_to_ticks(650)
#define PULSE_SHORT_TICKS nsecs_to_ticks(300)

Also, what board has the neopixel with the issue and who manufacturers it?

-Kevin

10

Hi kevin, thanks for reply.
Tomorrow i’ll test with your request and update you
Sb2209+sb0000 can with manta mp8 v2 by btt!

11

with 300nm issue persist. I ordered a new set from but and lets see