Remove diffusing filter.
Undo 3 screws.
Unplug ribbon cable from LED board.
Gently pry off back cover with small flat tool. Plastic is very soft/brittle.
CB2L module is soldered to power board.
I don't know this system much. Maybe Python's hid_download_py can work. You can see CB2S (very similar to CB2L) dumping in this video: https://www.youtube.com/watch?v=PKkiqDNFIx8
Issue was with forms.
System.Windows.Forms.dll
"The Carbon driver has not been ported to 64bits, and very few parts of Windows.Forms will work properly, or at all"
Was able to get the app working in VM.
Continuing breakdown and UART flashing -
Wire up power to extension pins and grab TX, RX, and CEN off the back of the board.
CEN can be grounded to the large ground pad on the board.
Below is the dump information:
Device configuration, as extracted from Tuya:
- LED Green (Channel 2) on P24
- LED Cool (Channel 4) on P8
- LED Blue (Channel 3) on P6
- LED Warm (Channel 5) on P7
- LED Red (Channel 1) on P26
Device seems to be using CB2L module, which is using BK7231N.
And the Tuya section starts, as usual, at 2023424
Just got a single pack of one of these and it uses a different module. There isn't consistency. Configuration values are the same. Module firmware from Lumary before flashing was 2.3.x in the Tuya app.
Selected by firmware and it flashed OTA like normal.
Can you post Tuya Config? So you got BK7231T version that time?
Already flashed it. Yes it was WB2L with newer firmware.
Manufacturer date was sept. 21. Manf date on others was Dec. 21
Added after 1 [hours] 29 [minutes]:
Plot thickens. Manf date 2022, Aug. Completely new revision of the board. Could not configure the pins the same. Light wouldn't work. Opened it to see what was going on.
Module CB2L
Had to cut the board to expose the back of the module for the pins.
And cannot find tuya config
Backup 2MB created, now will attempt to extract Tuya config.
Failed to extract Tuya keys - magic constant header not found in binary
Sorry, failed to find Tuya Config in backup binary.
There are PWM-SDA and PWM-SCL markings on the board. This indicates a "I2C-like" LED driver such as BP5758, SM2135, etc. Please see where are the SDA/SCL signals going. What is the name of the chip? It should be in SOIC8 case or similiar.
KP18058 looks like one of those "I2C-like" LED driver chips, where only two digital lines (SDA and SCL) are used to control 5 channels of LEDs. The problem is, KP18058 doesn't seem to be well known. There are only few google results for that. It seems it has a product page here:
http://www.kiwiinst.com/productinfo/1248723.html It seems that only full datasheet is available per request:
http://www.kiwiinst.com/productinfo/1248723.html
That basically means we don't have KP18058 support in OpenBeken and currently don't know how to add it.
But, maybe, it has the same protocol as SM2135, or BP5758, SM2235, or BP1658CJ:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/drivers.md So I've been thinking maybe you can try to check if any of those drivers are working for your chip. For SM2135, set the two pin roles in config module, then reboot your device, and check if RGB control works. Do the same for other LED drivers.
If KP18058 is indeed a separate chip with yet another protocol ,then we need to either get the datasheet or two wire communication capture sample for analysis, so I can write a driver for that.
Can you provide more information where was your device bought?
More info on this setup - (third revision with SDA). I had a wiring issue in original read.
Read @ 115200
Write @ 921600
Other rates fail.
I corrected and the results of read are below:
Code: json
Log in, to see the code
Device configuration, as extracted from Tuya:
- UnknownDAT on P8
- UnknownCLK on P7
- LED remap is 1 2 0 3 4
Device seems to be using CB2L module, which is using BK7231N.
And the Tuya section starts, as usual, at 2023424
But, maybe, it has the same protocol as SM2135, or BP5758, SM2235, or BP1658CJ:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/drivers.md So I've been thinking maybe you can try to check if any of those drivers are working for your chip. For SM2135, set the two pin roles in config module, then reboot your device, and check if RGB control works. Do the same for other LED drivers.
I have tried the three available drivers and none work. If I can assist let me know. I do not have a spectrum analyzer.
Please stand by @swpharis , we will need your help with testing once @DeDaMrAz does packets capture. I wonder how the protocol looks like. Some such LED drivers are using 8 bits per channel, giving us 256 possible options per color, but others are also 10-bit (1024 options per color).
Google translated from Chinese.:
KP18058 is a high-precision five-channel full-pressure LED linear constant current moderation chip, which can be independently set by the I2C (Inter-Integrated-Circuit Bus) interface 5 street currents to support various modes of light adjustment. The CW channel is an analog light-tuning method. The RGB channel supports analog lighting and chopping wave lighting, while supporting 1024 gray-order lighting per road to meet the lighting needs in various settings.
It finally arrived!! Can confirm CB2L module inside and that KP18058ESP driver IC is inside. It will take some time to get to it and figure out the protocol but now we can at least work on this
Looking forward to figuring this out - just reporting some progress, please be patient.
Very good job with drawing the schematic, @DeDaMrAz . It looks like a classic Tuya IoT device circuit, though.
A fusible resistor at the input, sadly (as often) without a varistor, not much interference filters except their classic "inductor between two 400V caps" filter, then a step down (non isolated) converter (again, usual, I have never seen Tuya product with capacitive dropper, it seems those droppers are less and less used), and finally, CB2S with I2C lines (with pull up resistors) connected to the "I2C" LED controller.
My best guess is because this is a 110-120V ONLY device that is why 200V but bad design overall, regardless of it being a "classic" and low cost I don't like it at all.
Were you able to get it to work with the BP5758 driver? I am not able to get it to function. Maybe I am doing something wrong?
It was just a thought, because they looked very, very similar. Thanks for trying but unfortunately you will have to wait for the protocol to be decoded - we will try probably this weekend.