Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamHalliHallo wrote:Any updates here?
HalliHallo wrote:
I will aks a Friend, they have familie in Poland... I think they know how to send to Poland.
p.kaczmarek2 wrote:
startDriver SM16703P
SM16703P_Init 5
again:
SM16703P_SetRaw 1 0 FF000000000000000000739CE71F00
delay_s 1
SM16703P_SetRaw 1 0 0000FF00000000000000739CE71F00
delay_s 1
SM16703P_SetRaw 1 0 00000000FF0000000000739CE71F00
delay_s 1
SM16703P_SetRaw 1 0 000000000000FF000000739CE71F00
delay_s 1
SM16703P_SetRaw 1 0 0000000000000000FF00739CE71F00
// offf
delay_s 1
SM16703P_SetRaw 1 0 00000000000000000000739CE71F00
goto again
startDriver SM15155E
LED_Map 0 1 3 2 4
TL;DR: Scope captures show 350 ns/1 150 ns pulses at 800 kbps for SM15155E control, and “driver works on my side” [Elektroda, p.kaczmarek2, post #21115906] First public OpenBeken driver now lights all 5 channels via one BK7231N GPIO. Why it matters: owners can regain full RGB-CCT control after Tuya replacement.
• IC combo: BK7231N Wi-Fi MCU + SM15155E 5-channel constant-current LED driver [Elektroda, HalliHallo, post #20778346] • Protocol: Return-to-Zero, 800 kbps, 80-bit pixel + 32-bit current frame [Elektroda, femboozle, post #20983095] • Pulse timing: logic ‘1’ ≈350 ns high, 1 150 ns low (±50 ns) [Elektroda, p.kaczmarek2, post #20789559] • Channel current: 10–300 mA selectable in 5-bit steps [Elektroda, femboozle, post #20989648] • Firmware memory: 2 MB flash dump available for recovery [Elektroda, HalliHallo, post #20778847]
startDriver SM15155E.LED_Map 0 1 3 2 4 then save. LEDs respond immediately [Elektroda, p.kaczmarek2, post #21115906]flashmem_write over UART or OTA to restore it. Pairing button is absent, so enable pairing via cloudcutter script before flashing back [Elektroda, HalliHallo, post #20778872]SM15153E_Init 3, but white channels won’t work. Add external MY9291 if you need CCT [Elektroda, femboozle, post #20983095]