FAQ
TL;DR: The W600-based TW02 SmartPlug draws 80 mA idle and can peak at 230 mA [Elektroda, iprak, post #20239610]; “you’re the first one in the world to flash custom IoT firmware” [Elektroda, p.kaczmarek2, post #20241602] Serial flashing, then HTTP OTA keeps updates simple.
Why it matters: Knowing the exact pins, power draw and update path prevents bricking and speeds deployment.
Quick Facts
• SoC: WinnerMicro W600, 80 MHz ARM Cortex-M3 [WinnerMicro Datasheet].
• Idle current ≈ 80 mA; FCC lists 230 mA max [Elektroda, iprak, post #20239610]
• Operating rail: 3.3 V and GND are silk-screened on Side-A header [Elektroda, iprak, post #20239610]
• Relay & red LED: PB15; blue LED: PB8 [Elektroda, iprak, post #20239610]
• Fastest reported flash: 460 800 baud, <8 s [Elektroda, omelchuk890, post #20251927]
• Stable firmware builds: OpenW600 v1.15.514 (serial) and v1.14.69 (OTA) [Elektroda, jtauscher87, #20463539; omelchuk890, #20256479].
What chipset is inside the “generic” TW02 SmartPlug?
The module is a TW-02 carrying the WinnerMicro W600 Wi-Fi MCU, an 80 MHz ARM Cortex-M3 with 1 MB flash and 288 KB SRAM [Elektroda, iprak, #20239610; WinnerMicro Datasheet].
How do I open the enclosure without damage?
Insert a sharp spudger into the seam, work around the rim, then desolder the recessed power tabs with a wick; nothing fragile sits near the edge [Elektroda, iprak, post #20239610]
Which pins control the relay and indicator LEDs?
PB15 drives the relay and the red LED simultaneously; PB8 drives the blue status LED. The momentary button pulls PA5 high when pressed [Elektroda, iprak, post #20239610]
What is the SmartPlug’s power consumption?
Serial logs show 80 mA during idle testing, well under the FCC-declared 230 mA ceiling [Elektroda, iprak, post #20239610]
Can I flash custom firmware, and which tools work?
Yes. Use wm_tools.exe or w600tool.py. Users succeeded at both default speed and 460 800 baud [Elektroda, omelchuk890, post #20251927]
Three-step flashing guide?
- Hold BOOT, tap RESET to enter UART mode.
- Run
wm_tools -p COMx write_flash firmware.fls.
- Power-cycle; connect to the new AP for setup. [Elektroda, iprak, post #20275572]
How do I perform OTA updates on W600?
Use the basic HTTP OTA field in the web Config page: host the .img on a local server (XAMPP, Node-RED, or IIS), paste the URL, and press Update [Elektroda, iprak, post #20252832]
My OTA failed with versions 1.14.70/71—why?
Those builds lacked Wi-Fi initialisation for W600; after update the AP never appears, forcing serial rollback to 1.14.69 [Elektroda, omelchuk890, post #20256479]
What’s an edge-case failure to watch for?
Using the web-app drag-and-drop OTA won’t work on W600/W800; only the direct HTTP method is implemented [Elektroda, iprak, post #20252812]
Where can I download current binaries?
Releases live under OpenBK7231T_App and OpenW600 repositories—choose the “W60x” builds such as OpenW600_1.15.xxx.fls [Elektroda, iprak, post #20275572]
Is Micropython still a viable alternative on W600?
Yes. A maintained fork tracks MicroPython 1.20, offers 85 KB free RAM and neopixel support [Elektroda, rkompass, post #20608032]
What if wm_tools reports “Failed to transmit file”?
Omit the baud-rate parameter; auto-detect worked when specifying 460 800 caused errors [Elektroda, jtauscher87, post #20463539]
Does the W600 run hot in normal use?
Users noted the module feels warm but stays within spec; no thermal shutdown reported after continuous 80 mA draw [Elektroda, iprak, post #20239610]
Can I control WS2812/Neopixel strips?
Not yet in OpenBK, but developers are open to adding it when real W600 lighting hardware is available [Elektroda, p.kaczmarek2, #20275822; iprak, #20278005].
