logo elektroda
logo elektroda
X
logo elektroda

Artika SkyShade (FLP14-SSWTR-C1WH) - CBU (BK7231N) using OpenBeken: RGB working, Infrared/white not

phormix 1428 5
ADVERTISEMENT
  • #1 20844082
    phormix
    Level 2  

    This device - an Artika SkyShade LED Ceiling light Panel - uses a CBU (BK7231N) based chip and is purchasable from Costco.

    It features a 115x25cm panel containing multiple LEDs to offer RGB and tunable white (warm/cold) light output, and comes with an infrared remote for additional control.

    What works:
    Firmware overwrite: Overwriting the firmware / wOpenBeken using leads attached to the pins and a USB-serial adapter worked fine.
    RGB Lighting: I was able to deduce the outputs for R G B lights as
    P7: PWM 2 (Green) output wire
    P6: PWM 3 (Blue) output wire
    P26: PWM 1 (Red) output wire

    What doesn't work:

    Infrared Input:
    I've managed to trace P5 back to what I assume is the Infrared receiver (which sits on the same central board as the CBU chip) and thus set this pin to "IRRecv". However, when pointing the remote at the device and clicking buttons, I see no events for infrared input in the logs (and nothing happens).

    Warm/Cold white lighting:
    There are four additional wires off the device from the chip, which are labeled:
    P14 (3v3)
    P13 (ground)
    P8: Label is fuzzy, possibly BRG
    P24: Appears to be labeled "CCT"

    My assumption is that the CCT output (P24) along with P8 should control the white light output and cold/warm balance. However, as of the current attempt, assigning a PWM to either of these and then attempting to change the "warmth" setting will result in all light output turning off completely until the PWM config is removed from those outputs and the chip is restarted.

    Pictures of the board with the chip as well as the interface/power board are as follows:


    Close-up of a circuit board with a CBU module and multi-pin connector. Close-up of the PCB of the Artika SkyShade LED panel with visible components. Close-up of a circuit board with electronic components and wires.
  • ADVERTISEMENT
  • #2 20844974
    p.kaczmarek2
    Moderator Smart Home
    Hello. For a start, can you provide a 2MB firmware dump or at least a Tuya JSON data from a config partition, as exported by our video tutorial here:


    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 20845243
    phormix
    Level 2  

    Yes of course. I'm surprised at such a quick reply :-)


    The attached is the Tuya config and full dump (compressed with GZIP).

    I've also got a backup of the original data taken before the device was reflashed to OpenBeken if that might be somehow useful, however the flashing utility didn't find any pin data at the time of backup.

    Thanks!
  • ADVERTISEMENT
  • #4 20845273
    phormix
    Level 2  

    Update:

    I decided to mess about with this a bit more while I had a few moments, and got the white light working.
    It seems that whatever P24 is, setting it as a PWM will just cause everything to fail which is what was tripping me up the previous night.
    P8 does however work to supply white (it also adds a temperature slider, though this seems to actually affect white-brightness rather than warmth) if it's the last PWM so long as P24 is disabled and the device has been rebooted after any attempt to use such.

    So far a working RGBW configuration is
    P6 PWM 2
    P7 PWM 1
    P8 PWM 3
    P26 PWM 0
    P24 Current unset or no lights work

    P5 IRRecv but still does not appear to do anything as of yet. I'm fairly sure I've got the correct pin for this. P14 (3v3) has a shared trace split off and running through some resistors up to (what I assume is) the IR receiver, which in turn has three pins with the leftmost appearing to run down to P5. Not a big loss if this doesn't work but it would be cool to manage full functionality

    Added after 1 [hours] 2 [minutes]:

    Update #2
    PWM24 does work but only if PWM9 is enabled. It also needs to be set to PWM_n in order to map hot/cold properly (otherwise it is reversed)
    Lighting configuration is now function with hot/cold white and RGB
    P6 = PWM 3
    P7 = PWM 2
    P8 = PWM 4
    P9 = PWM 6
    P24 = PWM_n 5
    P26 = PWM 1

    This leaves just the infrared to fiddle with. Likely not P5 as I re-checked the datasheet and realized that "5 != actual "physical pin 5" which is where the trace runs to. Tuya datasheet says this is ADC but also no luck with P23 (ADC3)

    Added after 9 [minutes]:

    Update #3

    Found the infrared
    P23 = IRRecv (requires reboot after setting this one)
  • ADVERTISEMENT
  • #5 20845635
    p.kaczmarek2
    Moderator Smart Home
    Yes, P5 is not the pin 5 on the TQFP package. This can be misleading.

    I see you've done a good progress yourself, good job.

    I will just ask - it seems that your device is using alternate CW mode, have you set the proper flag for that?
    Quote:

    8 [LED] Alternate CW light mode (first PWM for warm/cold slider, second for brightness)

    See more at:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/flags.md

    Have you seen our video tutorials?
    https://www.youtube.com/@elektrodacom
    Maybe that one about IR:




    Added after 24 [seconds]:

    Can you post here the OBK template from the Web App, once you got all the GPIOs?
    Helpful post? Buy me a coffee.
  • #6 20846990
    phormix
    Level 2  

    > I will just ask - it seems that your device is using alternate CW mode, have you set the proper flag for that?

    Nice. With this, I can use PWM1-5 and it passes the correct parameters for RGBCW to HomeAssistant, so another issue fixed.

    > Have you seen our video tutorials?

    I looked at some of the ones about Flashing and connecting to MQTT/HASS. I hadn't looked at the IR one yet, so I'll check that one out next.

    > Can you post here the OBK template from the Web App, once you got all the GPIOs?

    Absolutely. Once I figured out the last bit with the IR, I'll post that up along with perhaps a more detailed teardown. This is only my second OpenBeken device, so I'm getting used to some of the differences from the Tasmota stuff I'm more accustomed to.
ADVERTISEMENT