Uploading OpenBK7231N on the roller shutter controller FS-03W CB2S (BK7231N)

Name: Uploading OpenBK7231N on the roller shutter controller FS-03W CB2S (BK7231N)
Uploaded: 2023-10-27T13:47:47+02:00
Description: I have acquired such a controller for roller shutters: I soldered the chip, connected it to the programmer: I backed up with BK7231Flasher and started uploading OpenBK7231N_QIO_1.17.291.bin. After a while the program dumped me something like this: I tried to upload the backup - same thing. I...

Question

I have acquired such a controller for roller shutters: I soldered the chip, connected it to the programmer: I backed up with BK7231Flasher and started uploading OpenBK7231N_QIO_1.17.291.bin. After a while the program dumped me something like this: I tried to upload the backup - same thing. I...

Nargo · Accepted Answer

In view of the FREE day modifying the script from this thread I came up with something like this:

// Set up Aliases
alias Set_Stop backlog setChannel 5 0; setChannel 6 0; setButtonColor 3 red; setButtonColor 2 red; setButtonColor 1 red
alias Set_Finish backlog setButtonColor 2 blue
alias Start_Opening backlog stopAllScripts; startScript autoexec.bat openSkylight
alias Start_Closing backlog stopAllScripts; startScript autoexec.bat closeSkylight
alias Stop_All backlog stopAllScripts; startScript autoexec.bat stopSkylight

// Channel 60 is seconds for power to be applied
setChannel 60 25

// create GUI buttons for HTTP panel
startDriver httpButtons

setButtonEnabled 1 1
setButtonLabel 1 "Open"
setButtonCommand 1 Start_Opening
setButtonColor 1 red

setButtonEnabled 2 1
setButtonLabel 2 "Stop"
setButtonCommand 2 Stop_All
setButtonColor 2 red

setButtonEnabled 3 1
setButtonLabel 3 "Close"
setButtonCommand 3 Start_Closing
setButtonColor 3 red

// Hide the default GUI buttons
setChannelVisible 5 0
setChannelVisible 6 0
setChannelVisible 3 1

// Loading Event Handlers
addChangeHandler Channel1 == 1 Start_Closing
addChangeHandler Channel2 == 1 Start_Opening

// Close Skylight on power up
goto stopSkylight

// do not proceed
return

openSkylight:
setChannel 6 0
setButtonColor 3 red
delay_s 0.1
toggleChannel 5
setButtonColor 1 blue
setChannel 2 0
delay_s $CH60
Set_Stop
Set_Finish
delay_s 3
Set_Stop
return

closeSkylight:
setChannel 5 0
setButtonColor 1 red
delay_s 0.1
toggleChannel 6
setButtonColor 3 blue
setChannel 1 0
delay_s $CH60
Set_Stop
Set_Finish
delay_s 3
Set_Stop
return

stopSkylight:
Set_Stop
Set_Finish
delay_s 3
Set_Stop
return

At the moment I have raising/lowering 100% with stopping at any time from physical buttons as well as from HA

Channels 1 and 2 physical buttons
Channels 5 and 6 roller shutter relays

p.kaczmarek2 · Answer

Hello, have you tried reducing the baud rate?
And maybe hid_download_py will work?
[youtube]
https://www.youtube.com/watch?v=0V0kaRVnk18
[/youtube]

And also those wires.... It might be worth shortening them a bit. There have already been situations on the forum that it was the length of the wires that got in the way.
And the power supply on the 3.3V picture comes from some good LDO providing sufficient current or where from?

Nargo · Answer

Only on such a cobweb was it possible to upload this OpenBK7231N_QIO_1.17.11 soft

CRC matches 0x1A2FDBD2!
Writing file data to chip successs.

Then I will solder in the circuit and check if it works properly.

p.kaczmarek2 · Answer

Now it would only be useful to know whether using hid_download_py or shortening the wires helped. Hid_download_py miscounts CRC so for N the error can be ignored

Nargo · Answer

Flashing BK7231 Easy UART Flasher.

p.kaczmarek2 · Answer

So did the length of the wires cause a problem though?

Nargo · Answer

I don't know myself.
I powered from the programmer to the ESP-01, didn't go. (The previous one did.)
Powered from the power supply for the contact boards, it did not go.
Powered from the WEMOSd1Mini, it did not go.
It only worked on the programmer from the ESP and the power supply from the latter (YP-05).

And also not versions 1.17.291 and 1.17.15, but versions 1.17.11

Also black magic is at work, but I have already recently succeeded with Tasmota and the drivers for AHT20.

EDIT:
I am looking at the pictures and it appears to me that this module is a mirror image of CB2S on the power side.

p.kaczmarek2 · Answer

Wait, the lettering on the description layer doesn't match those on the Tuya documentation? If so then please check how it was soldered! I am familiar with this problem. I have seen a series of devices with CB2S where there was a bad description layer reflected, the pins were wrongly signed, so GND was not GND, and 3.3V was not 3.3V Wrong connection of such a module can damage it! Please check and verify everything with where the 3.3V and GND on the motherboard. Added after 1 [minutes]: @Nargo in my opinion you have a module with a badly bounced description layer, in Tuya's documentation there are correct leads, if you haven't burned it yet it's just a fart, thanks to the fact that GPIO has protective diodes to ground and power supply

Nargo · Answer

You don't start a sentence with So. So I soldered the chip in after programming, it fired up, updated and the relays on P6 and P7 are working, the LED on P24, the button on P26. I just can't figure out where the status of the roller shutter buttons appear.

p.kaczmarek2 · Answer

Execute and post the result:

Nargo · Answer

It doesn't go. .

p.kaczmarek2 · Answer

Then take the first backup you have and drag and drop it onto the flasher

Nargo · Answer

Code: text Expand Select all Copy to clipboardFailed to extract Tuya keys - magic constant header not found in binary It seems that dragged binary is full of 0xff, someone must have erased the flash Failed to extract Tuya keys - magic constant header not found in binary It seems that dragged binary is full of 0xff, someone must have erased the flash Failed to extract Tuya keys - magic constant header not found in binary It seems that dragged binary is full of 0xff, someone must have erased the flash Failed to extract Tuya keys - magic constant header not found in binary Failed to extract Tuya keys - magic constant header not found in binary Failed to extract Tuya keys - magic constant header not found in binary Failed to extract Tuya keys - magic constant header not found in binary .

p.kaczmarek2 · Answer

Open the file in a hex editor. It looks like it is full of 0xff itself. This is not a valid backup.

Maybe better to use GPIODoctor and by method of elimination check what of the CB2S pins are not used yet. Also delete the ones that are not soldered on the PCB. There won't be many options left.

And what device model is written on the housing of this relay?

Nargo · Answer

Smart Curtain Controller pins: { 6: Rel;1, 7: Rel;2, 10: dInput_n;1, 11: dInput_n;2, 24: LED_n;3, 26: dInput;0 }, Now still to find how to configure this as a roller shutter controller and it will be GIT.

p.kaczmarek2 · Answer

FS-03W, this is important information. Model name.

We do not have a ready-made system for roller shutters in the firmware. I do not have roller shutters at my home so I had no way to prepare it. We can either e.g. prepare it together (if you know C or at least want to test a bit) or we can use ready scripts from other users:
https://www.elektroda.com/rtvforum/topic3972935.html

Nargo · Answer

This came out of the first, first Backup. Code: text Expand Select all Copy to clipboard{ rl1_lv:1, bt1_pin:10, on_off_cnt:10, onoff_rst_m:0, rl3_pin:7, rl3_lv:1, onoff_clear_t:10, travel_calibra1:3, reverse_ctrl1:8, net_trig:4, dev_ctrl1:1, netled1_lv:0, jv:101, travel_t:10, onoff_rst_type:1, delay_t:300, total_bt_pin:26, nety_led:1, bt3_lv:0, bt1_lv:0, bt_reuse:1, reset_t:5, netled1_pin:24, travel_t1:10, net_type:0, bt3_pin:11, module:CB2S, percent_ctrl1:2, onoff_type:2, total_bt_lv:0, ch_num:1, rl1_pin:6, netn_led:0, crc:44, } ).Agw_wsm{nc_tp:0, ssid:null, passwd:null, md:0, random:0, wfb64:1, stat:0, token:null, region:null, reg_key:null, dns_prio:0 }{uuid, psk_key:c1ocYrc0oM3dvMQbOTTu5gHAP1v3HZfSjxgzt, auth_key:qGUEHBpOLMAVfZCDHaGLqalmiV6r3WvN, ap_ssid:SmartLife, ap_passwd:null, country_code:null, bt_mac:null, bt_hid:null, prod_test:false, fac_pin:enrribhu0xheehid }{nc_tp } Code: text Expand Select all Copy to clipboardDevice configuration, as extracted from Tuya:  - Button (channel 1) on P10 - Relay (channel 3) on P7 - Pair/Toggle All Button on P26 - WiFi LED on P24 - Button (channel 3) on P11 - Relay (channel 1) on P6 Device seems to be using CB2S module, which is using BK7231N. And the Tuya section starts, as usual, at 2023424 I would be happy to learn new things. I can test it as time allows. I used to write something there.

p.kaczmarek2 · Answer

So there was a first-first backup after all, just as I thought. That's good.

I would like to add this device to https://openbekeniot.github.io/webapp/devicesList.html , could you provide where you bought it, maybe some screenshots from the auction?

What about the roller shutter controller, what functionalities are needed? Are we trying to do something like in Tasmota?

Nargo · Answer

Auction photo Link to purchase I purchased together with AHT20+BMP280 modules on 14 day delivery. Purchase 8-09-2023 delivery 18-09-2023. Functionality-wise, suggesting the current roller shutter controller: Zamel SRP-02 controller Quote from manual: Flexible modes allow you to set the position of the roller shutter in a fixed position (at a fixed height) and store this position.

Nargo · Answer

Today I found that my controller is the same one from the thread [CB2S/BL2028N] Spacetronik SL-SC-01 roller shutter controller, interior and programming .

Nargo · Answer

After testing, it appears that the above code does not work as intended.
I rewrote everything

alias akcja1 backlog stopAllScripts; startScript autoexec.bat rusz1
alias akcja2 backlog stopAllScripts; startScript autoexec.bat rusz2
alias akcja3 backlog setChannel 6 0; setChannel 5 1; setChannel 10 1; setChannel 60 25 
alias akcja4 backlog setChannel 5 0; setChannel 6 1; setChannel 10 1; setChannel 60 25
alias akcja_stop backlog setChannel 6 0; setChannel 5 0; setChannel 10 0; ; setChannel 60 1
alias akcja50 setChannel 60 7


//Channel 1 - wejście 1
//Channel 2 - wejście 2

//Channel 5 - wyjście 1
//Channel 6 - wyjście 2
//Channel 10 - stan 1 jakiekolwiek wyjście ON/ stan 0 jakiekolwiek wyjście OFF

//Channel 60 - czas pełnego otwarcia 25s
//Channel 60 - czas częściowego otwarcia 8s
//Channel 60 - czas po zatrzymaniu 1s

addChangeHandler Channel1 == 1 akcja1
addChangeHandler Channel2 == 1 akcja2
//Przyciski
startDriver httpButtons

setButtonEnabled 1 1
setButtonLabel 1 "Open"
setButtonCommand 1 akcja1
setButtonColor 1 "#ff0000"

setButtonEnabled 2 1
setButtonLabel 2 "Close"
setButtonCommand 2 akcja2
setButtonColor 2 "#ff0000"

// nic nie rób 
goto start
return

rusz1:
setButtonColor 1 "#0000ff"
if $CH10==1 then akcja_stop else akcja3
delay_s 0.1
setButtonColor 1 "#ff0000"
delay_s 1
if $CH1==1 then akcja50 
delay_s $CH60
akcja_stop
return

rusz2:
setButtonColor 2 "#0000ff"
if $CH10==1 then akcja_stop else akcja4
delay_s 0.1
setButtonColor 2 "#ff0000"
delay_s 1
if $CH2==1 then akcja50 
delay_s $CH60
akcja_stop
return

start:
akcja_stop
setButtonColor 1 "#ff0000"
setButtonColor 2 "#ff0000"
return

Now it works as follows:
Short press (up to 1s) roller shutter up/down 100% (25s)
Long press (over 1s) roller shutter up/down about 40% (8s)
Second click with any key during operation stops roller shutter motor.

As soon as there is enough time before the kids return from school, I will install and check on the roller shutter.

io2345 · Answer

What I don't understand: How can the device use P10 and P11, if there are no P10 and 11 on a CB2S available (see Tuya Schematics above in #8)???

Method / tool	Result in thread	Practical note
BK7231 Easy UART Flasher	Failed at 0xE000/0xF000 first, then succeeded	Worked after setup changes and with firmware 1.17.11 [#20788010]
BK_writer	`Flash ID: 0x00000000`, `Init...FAILED`	Strong sign of communication or power problem [#20787763]
hid_download_py	Suggested as fallback	CRC can be miscounted on BK7231N, so that specific error may be ignorable [#20788018]

Uploading OpenBK7231N on the roller shutter controller FS-03W CB2S (BK7231N)

Topic summary

FAQ

Quick Facts

1. Why does BK7231 Easy UART Flasher fail around sector 0xE000 or 0xF000 when uploading OpenBK7231N to an FS-03W CB2S roller shutter controller?

2. How can I successfully flash OpenBK7231N on an FS-03W Smart Curtain Controller with a BK7231N/CB2S module?

3. What troubleshooting steps help when BK_writer shows Flash ID 0x00000000 and Init...FAILED on a BK7231N device?

4. How much do wire length, UART baud rate, and 3.3V power source quality affect flashing stability on CB2S/BK7231N modules?

5. BK7231 Easy UART Flasher vs hid_download_py: which is better for recovering or flashing a CB2S-based BK7231N module?

6. What is hid_download_py, and why can its CRC error sometimes be ignored on BK7231N devices?

7. What is GPIODoctor in OpenBeken, and how do you use it to identify unknown button or relay pins on a CB2S board?

8. How do I verify whether a CB2S module has a mirrored or incorrect silkscreen pinout before soldering 3.3V and GND?

9. Why would a CB2S board label not match Tuya documentation, and how can that damage the module during flashing?

10. How can I extract Tuya pin configuration and keys from a valid first backup, and what does it mean when the backup is full of 0xFF?

11. Which pins were identified for the FS-03W roller shutter controller in OpenBeken, including relays, buttons, LED, and the pair button?

12. How do I configure an FS-03W in OpenBeken as a roller shutter controller when there is no built-in shutter firmware mode?

13. What OpenBeken script logic is needed for short-press full travel, long-press partial travel, and stop-on-second-press for roller shutters?

14. How does the FS-03W compare with the Zamel SRP-02 in terms of roller shutter functions like comfort mode, central mode, and saved positions?

15. Why do Tuya-extracted settings for this CB2S device reference P10 and P11 when standard CB2S pin diagrams seem not to expose P10 and P11?