Successfully Flashing Luminea ZX-5140-675 LED Controller with OpenBK: A Detailed Guide

Name: Successfully Flashing Luminea ZX-5140-675 LED Controller with OpenBK: A Detailed Guide
Uploaded: 2023-11-30T20:38:39+01:00
Description: Hi, i have flashed the Luminea ZX-5140-675 LED Controller with OpenBK successfully. The small Controller is based on BK7231N Here is how: 1. Open the small case from the back 2. Push out the PCB 3. Solder wires to VCC, GND, TX1, RX1 4. Connect FTDI or simmilar to the corresponding wires you just...

Question

Hi, i have flashed the Luminea ZX-5140-675 LED Controller with OpenBK successfully. The small Controller is based on BK7231N Here is how: 1. Open the small case from the back 2. Push out the PCB 3. Solder wires to VCC, GND, TX1, RX1 4. Connect FTDI or simmilar to the corresponding wires you just...

p.kaczmarek2 · Answer

Thank you for this informative post.

It seems that we can use JSON to extract GPIO information:


	"mic":"23",
	"secpin_pin":"7",
	"firstpin_pin":"6",
	"key_pin":"20",

It seems that button may be on P20. You can set the pin role to Button and it will control the power of your LEDs, can you check?
I can also see that mic may be on P23, it would make sense, it's ADC input.

I am not sure why there are two more pins specific, as it seems your device is a single color strip controler? Or is it a CW device?

Dlay_71 · Answer

Hi there,Thanks for your time in this. I have tried your suggestions, but it doesn't react to P20 as a Button. I set P23 to ADC, but I don't know how to test the Mic. I would expect a displayed voltage change when the microphone captures audio, but I don't know how to see the values.Also, the controller behaves very strangely now. Pin 7 on PWM doesn't work anymore. Setting it to REL leads to the possibility to turn it ON/OFF. Previously, with PWM, I was able to control ON/OFF and brightness.Is there a way to reset OpenBK completely?I don't understand the meaning of CW device, sorry.Attached are 100 very small LEDs on silver wire. They are organized in two channels, so with Pin7 I can only activate 50 of them. The other 50 stay dark, regardless of what I configure Pin6 to.

p.kaczmarek2 · Answer

Would you be able to sketch a schematic how are those LEDs connected? Are those transistors pairs really connected to P6 and P7?

niclauser · Answer

Hello everyone, I would like to take up the topic again because I have been thinking about implementing this anti-parallel two-wire LED light chain with an ESP8266 and Tasmota for some time, but I can't do it. Now I specifically got the light chain from Iluminea because it already contains what I want to recreate, just with a BL7231. And with OpenBK I can also understand the software, analogous to Tasmota.

The LED light chain is a two-wire LED chain in which the LEDs are alternately soldered in reverse. According to my knowledge, the control takes place via an H-bridge with 2x Y1, 2x Y2 transistors and 4x 1KOhm resistors. (see drawing) The H-bridge is controlled directly by BL7231 via its PIN 22 and 23. The control takes place via a quick switch between PIN22 and PIN23 (PIN22 - on > PIN23 - off, PIN22 - on > PIN23 - off). This creates the visual impression that the chain is flashing or the light is running. At the same time, the level of the voltage supplied by PIN22 and 23 is "changed" using PWM, which makes the LEDs appear brighter or darker. Using the button that switches PIN20 of the BL7231 directly to GND, a predefined scenario on the software side is switched to switching frequency between PIN22 and 23 and PWM brightness control (8 scenes, always in the order 1-9, 9=off).

I leave out the control via music because it doesn't interest me.

From my point of view, the problem is the permanent reciprocal control of the H-bridge from OpenBK (or from Tasmota, as I tried before). Basically I don't want running lights at all. Only the PWM PIN 22 and 23 must be activated at the same time and like a sine wave. How can I implement this?

Best regards

p.kaczmarek2 · Answer

Hello, so you want one PWM to be high when other is low? With a dead time?
Hm, it seems that you need to use a PWM group. It's should be supported in our SDK, but it's not exposed on our GUI, as I haven't tested it yet. You are the first one to ask for that. Is this really a stock Tuya device? Still, I can try to write an OBK driver for that feature, if that's needed.
Here's the required header:
https://github.com/openshwprojects/OpenBK7231...s/beken378/func/user_driver/BkDriverPwm.h#L82
Here are the function definitions you want:

Log in, to see the code

So basically you'd need to initialise a PWMs pair with bk_pwm_group_initialize and then update their respective high times with bk_pwm_update_param.
PS: See our current PWM HAL code for the reference:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/hal/bk7231/hal_pins_bk7231.c

niclauser · Answer

Hello Mr. Kaczmarek,First of all, thank you very much for this really quick answer.Yes, that is correct. Dead time, perhaps adjustable.Tuya device, no idea. The manufacturer is Pearl from Germany. But it has to be based on Tuya since your BK7231 flasher can read the Tuya binary.I have attached a short video of the function. Maybe to understand why I want to solve the problem: I have several similar fairy lights, some up to 20m long. All of them are just stupid, without WLAN control, only with a USB plug and blinking electronics. But the LED chain is constructed identically. Unfortunately, I cannot control this automatically. My plan was to recreate this control with an OpenBK or Tasmota so that I didn't have to throw away the fairy lights. A simple remote-controlled USB switch in front of it is not possible because the fairy lights start flashing wildly when switched on, and you first have to manually select a program, which is very bad.I like your solution approach. Fixed times would be enough for me. I don't need the program switches, although that would be a nice gimmick. I would like to try this out. Please help me:How do I get the required files integrated into the OpenBK after flashing? I'm not that deep in it yet.Thank you very much!

p.kaczmarek2 · Answer

The most simple and elegant way would be to create a new driver entry in drivers table, here: And then add a new driver file in drivers dir: Then in driver init function setup PWM for two GPIOs (specified as arguments or somehow else) and in quick tick update maybe map two channel values to the PWM values. You may want to take a look at the code of other drivers for the reference. Alternatively, I may later find some time to do it for you. Currently I am implementing RN8209 support for a donator.

p.kaczmarek2 · Answer

Testing with scope.


backlog startDriver PWMG; PWMG_Test

Log in, to see the code

Same settings, but:

Log in, to see the code

But I see a problem... it seems that duty2 argument is not even used in SDK:

Log in, to see the code

Added after 1 [hours] 31 [minutes]:

I am testing to see how it works....
Following code:

Log in, to see the code

gives me:

Added after 6 [minutes]:

Following code:

Log in, to see the code

results:

Added after 8 [minutes]:

Following code:

Log in, to see the code

Result:

Added after 8 [minutes]:

Code:

Log in, to see the code

Result:

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

p.kaczmarek2 · Answer

@Dlay_71 @niclauser PWM groups tutorial ready!

2ya2 · Answer

Sorry for reviving an old thread but I think my observations may be relevant. I am happy to have found this thread. I successfully flashed my Luminea ZX-5140-675 LED Controller. What worries me, though, is that under full brightness a component on the PCB gets extremely hot. I measure up to 150 degrees Centigrade at full brightness and that's with just a 1 A USB power supply.

I never noticed this before (also never measured). Is this still normal?

p.kaczmarek2 · Answer

What's getting hot - MOSFETs, BK7231 or something else? BK7231 can use power save to reduce heating (PowerSave 1 in startup command or autoexec.bat).

2ya2 · Answer

It is near the components at the LED 2 label (if you compare my heat image and the fourth image in the top post). So it is not the BK7231. I lowered the brightness to 60 and then it is ok (around 50 or 60 °C).

p.kaczmarek2 · Answer

Y2 transistor? It might mean that you have too long LED strip. Current consumption is too high. Did you get the controller in a set with a LED strip, or did you buy LED strip separately?

2ya2 · Answer

>>21336921 Thanks for the remark. It is an original strip, no modifications. Perhaps the original Tuya firmware did some limiting. Currently, I am figuring out which MQTT topics work and will make sure to keep the brightness low.

Does "PowerSave 1" in startup only work for the chip, is there another limiter I could set?

2ya2 · Answer

>>21337062
Replying to myself, providing additional info.

I bought another similar strip. With default firmware and full brightness the module also gets quite hot. So I just must make sure to not turn it all on.

p.kaczmarek2 · Answer

150 degrees, if that's a correct measurement, it's way too much for such a device. It's a bad design on Tuya part. If you want to keep full brightness, consider shorting the LED strip, so it draws less current.

[Solved] Successfully Flashing Luminea ZX-5140-675 LED Controller with OpenBK: A Detailed Guide

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

Topic summary