FAQ
TL;DR: 120 LEDs per 5 m strip; "Your LEDs are 6 per string." Use SM16703P tests, dump 2 MB before flashing. [Elektroda, alfakenzo, post #20906416]
Why it matters: This FAQ helps BK7231N/OpenBeken tinkerers identify drivers, test output, and avoid dead-ends when bringing LSC Smart Connect RGBIC strips online.
Quick Facts
- 5 m RGBIC strip: 120 LEDs; groups of 6 per segment for effects. [Elektroda, alfakenzo, post #20906416]
- Driver focus: SM16703/SM16703P on BK7231N; current builds show DMA instability. [Elektroda, p.kaczmarek2, post #20906555]
- Before development, attach a full 2 MB flash dump; maintainer tests on CB3S. [Elektroda, p.kaczmarek2, post #20854319]
- Autoexec demo sets R/G/B on first three pixels using SM16703P_Init and _SetPixel. [Elektroda, p.kaczmarek2, post #20888487]
- Some designs wire SM driver control to pin 16; verify your JSON mapping if nothing responds. [Elektroda, alfakenzo, post #20889212]
Which driver does the Action.com LSC Smart Connect RGBIC 5 m strip use?
Developers target SM16703/SM16703P for this family. Provide a full 2 MB flash dump to enable analysis on CB3S. "We're working on SM16703 currently." This lets maintainers validate timing, pin mapping, and segmentation without risking your hardware. It is the fastest path to working support and repeatable tests. Share the dump before flashing alternative firmware, so baseline behavior remains preserved for comparison. [Elektroda, p.kaczmarek2, post #20854319]
How many LEDs and segments are on the 5 m RGBIC strip?
Expect 120 LEDs total on a 5 m strip. The design groups LEDs in six-LED segments. Each six-LED group changes together, then the next group follows. This matters for effects and for verifying the driver’s pixel indexing. If colors repeat in blocks of six, segmentation is working. Use this to validate pixel order and to tune animations. [Elektroda, alfakenzo, post #20906416]
Where is the driver IC, and how do I identify it?
Look for a SOIC package on the LED strip itself. Check if the chip is marked, as the marking helps identify the protocol family. If you can read it, note the code for driver selection. If not, follow the dump-and-test approach referenced elsewhere here. Visual inspection is step one before firmware changes. [Elektroda, p.kaczmarek2, post #20854513]
How do I quickly test SM16703P output in OpenBeken?
Use the maintainer’s minimal script to light three pixels:
- Add to autoexec.bat: startDriver SM16703P; SM16703P_Init 3; SM16703P_SetPixel 1 255 0 0; SM16703P_SetPixel 2 0 255 0; SM16703P_SetPixel 3 0 0 255; SM16703P_Start.
- Run the script or reboot so it executes.
- Verify the first three segments show red, green, then blue. [Elektroda, p.kaczmarek2, post #20888487]
The autoexec runs, but colors seem random. What’s happening?
The driver works, but the DMA code still shows instability. "There is still some instability in the DMA code." The maintainer is porting LN882HK and will revisit stability. Expect intermittent artifacts until the fix lands. Keep tests short and note any repeatable patterns when reporting. This helps isolate timing issues and segment handling. [Elektroda, p.kaczmarek2, post #20906555]
My 2x5 m RGBCW set didn’t react to the script. What should I check?
That test produced no response on a 2x5 m RGBCW set. Re-check LED type, wiring, and JSON mapping before proceeding. If the LEDs aren’t SM16703P-compatible, the script will not drive them. Confirm your controller’s pin assignments match the target driver. Then retry the minimal test. [Elektroda, alfakenzo, post #20888830]
Do I need to provide a firmware dump before flashing OpenBeken?
Yes. Attach a full 2 MB flash dump first. The maintainer can flash it on a CB3S module and investigate behavior. This preserves a reference for regression checks and simplifies driver bring-up. It also reduces risk of bricking while features evolve. Share the file in-thread for review. [Elektroda, p.kaczmarek2, post #20854319]
Are these LEDs definitely SM16703P?
Confirm the LED type before assuming SM16703P. A maintainer explicitly asked whether the LEDs are SM16703P during troubleshooting. If they differ, the demo script will not work. Gather chip details or provide the dump so the team can validate the protocol. [Elektroda, p.kaczmarek2, post #20889057]
Is the SM driver controlled on pin 16?
Some setups reference pin 16 for the SM driver control. If nothing responds, verify your JSON maps the SM driver to pin 16. Update the mapping and retest the minimal script. Document any change in behavior for the thread. [Elektroda, alfakenzo, post #20889212]
Why do I see solid colors in blocks of six LEDs?
That reflects the hardware segmentation. The strip drives six-LED groups together, then repeats across the length. Use this to confirm addressing and expected color order. If segments don’t align, revisit SM16703P initialization and pixel indexing. It’s normal for effects to repeat every six LEDs on this model. [Elektroda, alfakenzo, post #20906416]
Is there something I can test today?
Yes. Run the provided autoexec.bat sequence to initialize SM16703P and set three pixels to R, G, and B. Observe segment behavior and report outcomes. This baseline confirms power, wiring, and basic timing. Keep logs and your JSON mapping for maintainers. [Elektroda, p.kaczmarek2, post #20888487]
Who is maintaining development, and what’s the current status?
The maintainer confirmed driver functionality with DMA instability and is porting LN882HK. "You have to wait, sorry." Expect updates after porting tasks conclude. Testing with the minimal script remains useful. Share structured feedback to accelerate fixes. [Elektroda, p.kaczmarek2, post #20906555]
What if the LED driver IC has no visible marking?
One user reported no visible marking on the strip’s SOIC chip. In that case, rely on software-based identification and shared dumps. Then test with the minimal script to observe behavior. Document results and any pin mapping used. [Elektroda, alfakenzo, post #20855628]
How can I share schematics or dumps for analysis?
A contributor shared a 2 MB dump and has the device schema available. Post your dump and any schematics in-thread. This speeds verification, pin mapping, and driver tweaks for everyone. Include controller model and wiring notes. [Elektroda, alfakenzo, post #20857329]
