I grabbed this from Ali curious about what might be inside. I'm also keen to test out the new OBK individually-addressable LED support and the pixel animations in this PR https://github.com/openshwprojects/OpenBK7231T_App/pull/1205
More on OpenBeken's WS2812B support here https://www.elektroda.com/rtvforum/topic4036716.html
The listing mentions WS2811 and the connector looks like a standard 3-pin male SPI LED strip type.
Surely it'll be a CBU using P16 for MOSI to drive the data line? Yes. it is. After popping the bottom of the unit up, which was easy, we see the main PCB, complete with microphone, which I hadn't clocked was mentioned on the product page
Although I have other devices with a CBU that could be adapted, this unit seems especially suited, being already designed for SPI LED support. The one down-side is that the VCC on the output connector is 12V for WS2811.
Conveniently the device has a push button and unused IR DATA, VCC and GND. All 3 are connected. IR to P20. This should make adding an IR send/receiver easy I believe. Eg
I have spare IR components from other LED controllers
Also, you could remove the microphone, which is currently of no use within OBK, to replace with something else. Another button?
I traced as much as I could for the main module pads, those that were visibly soldered anyway. There'll be more GND and VCC that I did not check for,
It seems the missing component pads in the U2 space do not trace anywhere except for GND. I'm not sure what this shaped space could be used for.
That 6-pin chip labelled RDA2L 3 <something> 0x.1 I think is a Rychip RY8310 (going by the silkscreen on the PCB anyway) or clone. This looks to be what converts the 12-24v to 3.3v for the CBU module. Datasheet attached.
Moving on, here is the factory fw boot log
and a firmware dump attached. Although firmware version 1.0.18 is in the Cloudcutter known patched list, that appears to be for a different device. There are two 1.0.18 LSC LED strip controllers exploitable https://github.com/tuya-cloudcutter/tuya-clou...mmit/29b3a33750d5ca5cd3a59028ba4ad1ac48fc9724
Easy UART Flasher extracts this information
Template import of the json will only set the button on P6 which doesn't seem to be listed in the extracted pins
I assume the same firmware was used on devices with more features, those with infra-red for example.
After flashing with the latest OpenBeken BK7231N firmware I hooked up my 120 LED WS2812B strip to the DIN (data) pin of the connector on the controller (green cable), 5V external PSU to red power injection cable of LED strip, white power injection ground to the ground of my PSU. And lastly the ground from the CBU module to the other grounds to create a common ground. The CBU will be powered by 12v mains-powered AC/DC adaptor with barrel connector for now.
With both powered and this in the autoexec.bat (Full-strip RGB sample taken from guide linked above). The second value on "setChannel 5 120" being the number of LEDs in my strip.
We get:
which is cool.
These pull ~1A at full brightness. This can be reduced with the dimmer slider in the web GUI
More recently some animations have been added. These can be tried by flashing the build from this pull request https://github.com/openshwprojects/OpenBK7231T_App/pull/1205
with an autoexec of
The GUI will look like this
and your strip will do this with one of the animations
Like my exploration of this device, I understand the PixelAnim driver will develop yet further in due course.
I look forward to playing with whatever's next!
More on OpenBeken's WS2812B support here https://www.elektroda.com/rtvforum/topic4036716.html

The listing mentions WS2811 and the connector looks like a standard 3-pin male SPI LED strip type.

Surely it'll be a CBU using P16 for MOSI to drive the data line? Yes. it is. After popping the bottom of the unit up, which was easy, we see the main PCB, complete with microphone, which I hadn't clocked was mentioned on the product page







Although I have other devices with a CBU that could be adapted, this unit seems especially suited, being already designed for SPI LED support. The one down-side is that the VCC on the output connector is 12V for WS2811.
Conveniently the device has a push button and unused IR DATA, VCC and GND. All 3 are connected. IR to P20. This should make adding an IR send/receiver easy I believe. Eg
I have spare IR components from other LED controllers

Also, you could remove the microphone, which is currently of no use within OBK, to replace with something else. Another button?
I traced as much as I could for the main module pads, those that were visibly soldered anyway. There'll be more GND and VCC that I did not check for,

It seems the missing component pads in the U2 space do not trace anywhere except for GND. I'm not sure what this shaped space could be used for.
That 6-pin chip labelled RDA2L 3 <something> 0x.1 I think is a Rychip RY8310 (going by the silkscreen on the PCB anyway) or clone. This looks to be what converts the 12-24v to 3.3v for the CBU module. Datasheet attached.


Moving on, here is the factory fw boot log
Code: Text
and a firmware dump attached. Although firmware version 1.0.18 is in the Cloudcutter known patched list, that appears to be for a different device. There are two 1.0.18 LSC LED strip controllers exploitable https://github.com/tuya-cloudcutter/tuya-clou...mmit/29b3a33750d5ca5cd3a59028ba4ad1ac48fc9724
Easy UART Flasher extracts this information
Code: Text
Code: Text
Template import of the json will only set the button on P6 which doesn't seem to be listed in the extracted pins

I assume the same firmware was used on devices with more features, those with infra-red for example.
After flashing with the latest OpenBeken BK7231N firmware I hooked up my 120 LED WS2812B strip to the DIN (data) pin of the connector on the controller (green cable), 5V external PSU to red power injection cable of LED strip, white power injection ground to the ground of my PSU. And lastly the ground from the CBU module to the other grounds to create a common ground. The CBU will be powered by 12v mains-powered AC/DC adaptor with barrel connector for now.
With both powered and this in the autoexec.bat (Full-strip RGB sample taken from guide linked above). The second value on "setChannel 5 120" being the number of LEDs in my strip.
Code: Text
We get:

which is cool.
These pull ~1A at full brightness. This can be reduced with the dimmer slider in the web GUI

More recently some animations have been added. These can be tried by flashing the build from this pull request https://github.com/openshwprojects/OpenBK7231T_App/pull/1205
with an autoexec of
Code: Tcl
The GUI will look like this

and your strip will do this with one of the animations
Like my exploration of this device, I understand the PixelAnim driver will develop yet further in due course.
I look forward to playing with whatever's next!