we think that's just limited to the experience on WG236A modules used in testing. There are several people with ECR6600/BL0937 EU plugs now using OpenECR6600 seemingly without issue.
>>21523865 Transmission power / dbm was more or less ok even on WG236.
It's the reception that is the problem. I had once seen -75dbm on router, but -90 on device (in log, because http stopped working already)
ECR6600 with v2.1.23.16 firmware size increased from 850kb to 920kb. (When i tried v2.1.24.11, it was 1222kb. Perhaps some optimization flags were missing?)
Added ECR6600 and BL602 deepsleep (ECR6600 - unknown if it works with new sdk, it didn't in the old one).
BL602 pindeepsleep (GPIO7/8 only)
ESP-IDF sdk from v5.5-beta1 to v5.5
Powersave for ECR6600
ESP deepsleep argument from ms to s
ECR6600 reset reason
reboot reason ✅
Excellent RSSI only because I have MHF4 + aerial now ✅
powersave 1 doesn't crash but don't know if it's effective
Code: Text
Log in, to see the code
deepsleep 30
Code: Text
Log in, to see the code
wakes at 30s but is weird. won't join wifi again until hard power off/on
Code: Text
Log in, to see the code
Added after 7 [minutes]:
yes weird. I get Windows device disconnect sound when it wakes too and no wifi join. but then a minute later it'll device-disconnect sound again, reboot and join wifi, then:
I'll try non-PC USB port
Added after 4 [minutes]:
on mains-powered USB 2A port it did join wifi 9s after wake and:
Added after 12 [minutes]:
divadiow wrote:
powersave 1 doesn't crash but don't know if it's effective
forgot i just bought this
powersave 0
powersave 1
Added after 16 [minutes]:
not really sure what's happening with deepsleep. this is it on mains USB, no powersave, then deepsleep 10 which you can see kicking in and dropping to 0, but then it draws too quickly again, drops and rises. hmm
So it can connect after deep sleep? Even if not, this is still better, that what i've had with older sdk. It failed to even find AP, stuck at scanning.
There is also powersave 2.
The discussion centers on the teardown and firmware development efforts for the LSC Connect Smart Wall Dimmer (model 3207304), which uses the AXY2S module based on the ESWIN ECR6600 chip. The ECR6600 is not currently supported by OpenBK firmware, but an SDK and flashing/backup tools (RDTool) are available on GitHub. The chip is similar to the TR6260, and ongoing porting efforts are documented in repositories such as jasperro/OpenECR6600 and OpenBK7231T_App. Users successfully extracted firmware backups via UART0 and analyzed boot logs, revealing TuyaOS V3 firmware with some changes in configuration storage compared to earlier versions. Challenges include unstable Wi-Fi reception, OTA update issues due to bootloader and OTA tool version mismatches, and limited documentation with only partial datasheets available. Various SDK versions have been obtained, including newer releases (v2.1.22 and v2.1.23.3), but integration and stability improvements remain in progress. Hardware variations include WG236 and WG236A modules, some with IPEX antenna connectors requiring modification for proper signal reception. Wi-Fi performance varies, with some users reporting poor reception and others achieving stable connections through walls and distance. Tools and code for UART, GPIO, PWM, ADC, and IRQ support are being developed and tested. The community is working on improving OTA functionality, MAC address modification, and partition management. Additional resources and SDKs have been shared from sources like SkyLab and Hi-Flying. Overall, the project is in active development with partial success in firmware porting and hardware support, but Wi-Fi stability and OTA remain key issues to resolve. Summary generated by the language model.