Configuring BK7231N LSC Multi Color Light Bar - Firmware and Driver Issues

Question

Hi all, i bought today this game bar at Action store. It fits 16 RGB leds, i didn't find any drivers on the led bar pcb nor on the main circuit . I've dump the fw directly as the pins are exposed, and reflashed with latest OBK . I'm a bit stuck for now as i can't find any valid config to get...

p.kaczmarek2 · Answer

Hello, can you check if SM16703P driver works for you? We have a PR to enable it for DDP as well and we have an idea how to improve the SPI driver stability in general, I think it could work good.

snakesrules94 · Answer

Hello,I've tried the driver but no luck:Code: text Expand Select all Copy to clipboard Info:CMD:[WebApp Cmd 'startDriver SM16703P' Result] OK Info:CMD:Register driver with 16 LEDs Info:CMD:Set Pixel 1 to R 255 G 0 B 0 Info:CMD:Raw Data 0xee 0xee 0xee 0xee - 0x88 0x88 0x88 0x88 - 0x88 0x88 0x88 0x88 Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 1 255 0 0 ' Result] OK Info:CMD:Set Pixel 2 to R 0 G 255 B 0 Info:CMD:Raw Data 0x88 0x88 0x88 0x88 - 0xee 0xee 0xee 0xee - 0x88 0x88 0x88 0x88 Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 2 0 255 0 ' Result] OK Info:CMD:Set Pixel 3 to R 0 G 0 B 255 Info:CMD:Raw Data 0x88 0x88 0x88 0x88 - 0x88 0x88 0x88 0x88 - 0xee 0xee 0xee 0xee Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 3 0 0 255 ' Result] OK Error:CMD:before enable tx 0x0000c20c Error:CMD:enable tx 0x0000c20d Info:CMD:[WebApp Cmd 'SM16703P_Start ' Result] OK I have tried with the SM16703P_DIN on pins 16 and without in the module config but it's not working. No lights on the bar.Rdgs.

p.kaczmarek2 · Answer

Then it's not WS2812B, because WS2812B works for me, altough there is still little instability that we need to fix:

Is the power reaching the strip at all? Maybe you need to enable something more?

PS: setting SM16703P_DIN role will not change anything, it always uses P16 now, as it's the hardware SPI out pin

snakesrules94 · Answer

I will solder the LED bar on a D1 mini and test with WLED to identify the LED type. I will let you know.

Edit: You're right, I've just checked the voltage on the bar and I have 0V on GND/VCC, so it seems one pin is used to power the LED bar.

Edit 2: By switching P6 to 1, now I got some answers and LEDs are lighting with SM16703P_Start command.

p.kaczmarek2 · Answer

Maybe it's P6? Can you try setting P6 to relay?

snakesrules94 · Answer

Yes , indeed , P6 is ok ton control power on leds bar :

here is my actual conf :

and the autoexec.bat with your test script i'm using :

// start driver
startDriver SM16703P
// delay 1s
delay_s 1
//enable power on P6
SetChannel 1 1
// use channel 10 as variable to store number of LEDs
setChannel 10 16
// initialize the driver
SM16703P_Init $CH10
// set iteration variable (channel 11)
setChannel 11 0

// loop setting R G B
again:
SM16703P_SetPixel $CH11 0 255 0
addChannel 11 1
SM16703P_SetPixel $CH11 0 0 255
addChannel 11 1
SM16703P_SetPixel $CH11 255 0 0
addChannel 11 1
if $CH11<$CH10 then goto again
// apply changes
SM16703P_Start

for now, only 12 leds on 16 are on, the 4 latests stays off .

snakesrules94 · Answer

Hello,I've just tried with a more basic script like this:Code: text Expand Select all Copy to clipboard startDriver SM16703P SM16703P_Init 16 SM16703P_SetPixel 0 0 255 0 SM16703P_SetPixel 1 0 0 255 SM16703P_SetPixel 2 255 0 0 SM16703P_SetPixel 3 0 255 0 SM16703P_SetPixel 4 0 0 255 SM16703P_SetPixel 5 255 0 0 SM16703P_SetPixel 6 0 255 0 SM16703P_SetPixel 7 0 0 255 SM16703P_SetPixel 8 255 0 0 SM16703P_SetPixel 9 0 255 0 SM16703P_SetPixel 10 0 0 255 SM16703P_SetPixel 11 255 0 0 SM16703P_SetPixel 12 0 255 0 SM16703P_SetPixel 13 0 0 255 SM16703P_SetPixel 14 255 0 0 SM16703P_SetPixel 15 0 255 0 SM16703P_StartBut the result is the same, only 12 leds on 16 are ON, the 4 latest keep definitively off.Rgds.

p.kaczmarek2 · Answer

Are the colors displayed correctly? Do you have a scope?

snakesrules94 · Answer

It seems okay for the color:I have a very basic Chinese scope kit, not sure if it can be helpful but tell me anyway if you want me to monitor something.Added after 14 [minutes]:If I rerun the script after first start, all the LEDs are on but with false colors this time:

p.kaczmarek2 · Answer

I will try to add a stability improvement today or tomorrow, can you help with testing? What happens if you set first, second and third LED to red? Maybe there is some kind of shift in indexes?

snakesrules94 · Answer

Ok, so with this script:Code: text Expand Select all Copy to clipboardstartDriver SM16703P SM16703P_Init 16 SM16703P_SetPixel 0 0 255 0 SM16703P_SetPixel 1 0 255 0 SM16703P_SetPixel 2 0 255 0 SM16703P_SetPixel 3 0 255 0 SM16703P_SetPixel 4 0 0 255 SM16703P_SetPixel 5 255 0 0 SM16703P_SetPixel 6 0 255 0 SM16703P_SetPixel 7 0 0 255 SM16703P_SetPixel 8 255 0 0 SM16703P_SetPixel 9 0 255 0 SM16703P_SetPixel 10 0 0 255 SM16703P_SetPixel 11 255 0 0 SM16703P_SetPixel 12 0 255 0 SM16703P_SetPixel 13 0 0 255 SM16703P_SetPixel 14 255 0 0 SM16703P_SetPixel 15 0 255 0 SM16703P_StartJust after reboot, the first 4 LEDs are red, the next 8 are in the right color, and the last 4 are off.If I rerun the script just after, all the LEDs are ON but with false colors, mainly blue and green.

snakesrules94 · Answer

@p.kaczmarek2: I've compiled a test version with the changes mentioned here: https://www.elektroda.com/rtvforum/topic4031475.html#20949043

Unfortunately, the result is not better than with the original FW with this LED bar.

As for now, I have pressure for my son to get his light bar working so I will drop the 7231N with a D1mini & Wled for now and I will try to get another LED bar in action store to continue debugging if needed.

Added after 37 [minutes]:

OK, while scrapping the original LED system, I replaced the original LED bar with a genuine 16 LED band of WS2812B.
Now, every time I run the script:

startDriver SM16703P
SM16703P_Init 16
SM16703P_SetPixel 0 0 255 0
SM16703P_SetPixel 1 0 0 255
SM16703P_SetPixel 2 255 0 0
SM16703P_SetPixel 3 0 255 0
SM16703P_SetPixel 4 0 0 255
SM16703P_SetPixel 5 255 0 0
SM16703P_SetPixel 6 0 255 0
SM16703P_SetPixel 7 0 0 255
SM16703P_SetPixel 8 255 0 0
SM16703P_SetPixel 9 0 255 0
SM16703P_SetPixel 10 0 0 255
SM16703P_SetPixel 11 255 0 0
SM16703P_SetPixel 12 0 255 0
SM16703P_SetPixel 13 0 0 255
SM16703P_SetPixel 14 255 0 0
SM16703P_SetPixel 15 0 255 0
SM16703P_Start

Colors R V B are good, but not in the right order, I got this result:

R B V R R B G R B G R B G R B G

Added after 3 [hours] 22 [minutes]:

I've continue to experiment with this bar fitted now with WS2812b leds , i've added some script to react to the IR remote and execpt the colors are bad , it seems to work OK.
Now i'm trying to dim the LEDS but if i change the P6 to PWM instead of REL , it does not work anymore .

I would think about reflashing the original FW and test to see the behaviour but not sure about the original config as if i extract it from the bin file, it seems that some conf are missing.
Maybe i would have more luck by finding another bar in Action store .

Added after 2 [hours] 56 [minutes]:

Ok , i've checked quickly with the original FW and indeed , the +5V to power the strip stays always at 5V .
Unfortunatly, my scope is not accurate enough to trace the timing on PWM line and get the timings for color control / animation / brightness and so on :-(

Is there a way to modulate the pwm on P16 to enable brightness control with the SM16703 driver ?

dingsundbums · Answer

Sorry for hijacking this.Also facing the same problem and it seems the difficulty is very similar.Bought a few weeks ago a Battletron monitor strip. managed yesterday to flash it with ESPHome.Drivers are not compatible. So switched this morning to OpenBeken and can tell at least:P6/P24/P7 are the button inputs from the box. So Power/Music/Mode Button.P7 = Power for the LED Strip.After setting this to high, the strip reacts to the SM16703P Driver.So the driver commands in fact work and the strip lights up in white.Didn't manage to get much further right now.....

p.kaczmarek2 · Answer

Everything boils down to one issue currently - for some reason, our SPI code (we are using SPI DMA to send pixels) has a strange, random lag spike that occurs sometimes when transferring pixels. I really don't know why it happens, but I observed it on my scope as well. This is the single issue we need to solve to have full, reliable support of such WS2812-like devices, but I am currently unable to fix it, I just straight up don't know what's wrong. Here is our SPI DMA code: I am using: Code: C / C++Log in, to see the code to send the pixels, I've tried even doing a NOP loop until DMA transfer is done, but no matter what I do, there is sometimes a random lag spike in the DMA transfer.... Do anyone have any ideas how to fix it? I can do the rest of LEDs handling code along with dimming once this issue is solved

DevilDuck · Answer

I had exactly the same issue with an LED Strip that contains 25 elements.If the script starts withSM16703P_Init 25,some elements were missing (off).However, starting the script withSM16703P_Init 30will correctly turn on all LEDs with the defined colors.Running the script a 2nd time unfortunately will result in wrong and unpredictable colors.

dingsundbums · Answer

Also, I have tested a bit more after figuring out that I must set pin 7 on my strip to always high and how to do an autoexec.bat.

My strip has 72 LEDs.
If I set the LED init to 76, the strip always shows correct colors after a boot.

If I run the autoexec.bat manually a second time, the colors will be incorrect and not shown at all.

So I changed the always high bin to a controllable one.
Even if I cut power to the strip and rerun the autoexec, the strip lights up again but colors will not change.

So just a guess:
Maybe it's not only a timing problem but maybe something in the direction of not flushing the output buffer for the data pin correctly?

p.kaczmarek2 · Answer

We've applied a fix on Github, can you try now? See related PR:

snakesrules94 · Answer

Hi, this is good news! I will have a try tomorrow morning with this new release. Added after 11 [hours] 53 [minutes]:Hello, quickly checked the release 462 this morning and it seems to works fine . Colors are now OK , each led is ON with the correct color when invoking script . for your info, i'm using right now 16 WS2812B on the controller, i will try later with the original leds bars of this game bar . Anyway , good job to all the peoples involved in this mod .

p.kaczmarek2 · Answer

So it's stable now? Wow, that's really good news! It seems it's a good time to make some kind of animation system for OBK. What kind of LED sequences would you like to get?

snakesrules94 · Answer

Would it be possible for you in a first time to manage the brightness control?Then a simple animation like rainbow or color scanner could be helpful to check the stability of the whole thing.Regards.

dingsundbums · Answer

Was just checking and it seems to be consistent now.

About that dimming:
As those are digital no special stuff is required to dim.
Just send 32/64/128 or so instead of 255.
Works for me.
Can control the brightness and color per led.

Also this is working for my strip.
Pay Attention that on the Battletron Monitor Strip the Power Pin for the LEDs is P7:


// start driver
startDriver SM16703P

// delay 1s
delay_s 1

//enable power on P7
SetChannel 56 1

// use channel 10 as variable to store number of LEDs
setChannel 10 72

// initialize the driver
SM16703P_Init $CH10

// set iteration variable (channel 11)
setChannel 11 0

// loop setting R G B
again:
SM16703P_SetPixel $CH11 0 32 0
addChannel 11 1

SM16703P_SetPixel $CH11 32 0 0
addChannel 11 1

SM16703P_SetPixel $CH11 0 0 32
addChannel 11 1

if $CH11<$CH10 then goto again
// apply changes
SM16703P_Start

PS: Just to mention that:
Those strips are GRB ordered. Was a bit confused about that at frist.
So first color is GREEN and not RED

snakesrules94 · Answer

@dingsundbums: So simple! Thanks for the hint about dimming!

dingsundbums · Answer

You're welcome :)Yeah, sometimes it's that simple and not digital (like on/off)PS: Just as a test for stability, I did some kind of silly LED effect:Code: text Expand Select all Copy to clipboard// start driver startDriver SM16703P // delay 1s delay_s 1 // enable power on P7 SetChannel 56 1 // use channel 10 as a variable to store the number of LEDs setChannel 10 72 // initialize the driver SM16703P_Init $CH10 // set iteration variable (channel 11) setChannel 11 0 // loop setting R G B again: SM16703P_SetPixel $CH11 0 32 0 addChannel 11 1 delay_s 0.2 SM16703P_Start SM16703P_SetPixel $CH11 32 0 0 addChannel 11 1 delay_s 0.2 SM16703P_Start SM16703P_SetPixel $CH11 0 0 32 addChannel 11 1 delay_s 0.2 SM16703P_Start if $CH11

p.kaczmarek2 · Answer

I am open to any suggestions for improvements. I am going to look into brightness command today or tomorrow. And soon, we need an animation system. How are LED animations handled in WLED or other software? Is there some kind of binary format for animations?

dingsundbums · Answer

Can't really tell how LED works.Sorry for that, but personally I use esphome with lambda functions to achieve some effects and I am relatively new to the openbeken world.Personally, I use an ESP8266 (D1 Mini) with a WS2812 1m/144 LEDs strip to show some values from my PV plant with an addressable lambda function.Think of it like fuel gauges.Due to the esphome in Home Assistant integration, I can get sensor values like PV power.So I can calculate out of those values how many LEDs should turn on in which colors and set the strip accordingly.At the moment, the strip is logically cut into 2 partitions with 72 LEDs each.One side showing PV power, the other the positive/negative battery power.PS: Just as an example, of course.But the effects are nice but sometime getting boring.And we all know the WAF.If it's colored and showing actual interesting values caused by the amount of sun that's shining, you have the WAF bigger than 1

snakesrules94 · Answer

To control brightness, I've just added a dummy channel as Dimmer256 and use that value inside the script to dim light, seems to work fine:Code: text Expand Select all Copy to clipboardsetChannelType 13 Dimmer256 setChannelLabel 13 BrightnessthenCode: text Expand Select all Copy to clipboardSM16703P_SetPixel $CH11 0 $CH13 0

dingsundbums · Answer

What a cool idea!I will copy that to my autoexec.bat :)Maybe it slowly makes sense to have our own thread for those addressable light things in general?

p.kaczmarek2 · Answer

Yes, sure. I've did a basic writeup and added some more commands and fixes. Please update your devices. For scripting configuration, please see:
OpenBeken WS2812B driver (compatible with SM16703P, etc) - short scripting presentation
We can continue discussion there. The more advanced animation will be added soon, stay tuned!

Configuring BK7231N LSC Multi Color Light Bar - Firmware and Driver Issues

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Topic summary