Skip to content
noggin

CyberBrick Core radio stacks (no device touched)

Local: nothing in docs/references or docs/research greps for espnow/WLAN/aioble/webrepl (only build-notes.md L49 firmware string, L99 “Core 1 relays to Core 2 by ESP-NOW” = designer’s setup). Stock manifest lists only .py/.mpy files, no radio code. Frozen (not on FS): bbl_product, ulogger, rc_module, ble_module, shutter_module (research/2026-10-31-hooks-serial-launchd.md L75).

Upstream: github.com/CyberBrick-Official/CyberBrick_Controller_Core (last commit 2026-03-25), docs/library/index.rst L187-225 “intentionally disabled or removed” list.

Stack Available Evidence
network.WLAN (STA) YES (high) docs/library/network.WLAN.rst shipped; rotorman truck.py runs WLAN(STA_IF), config(channel=,txpower=,pm=) on a Core
espnow YES (high) docs/library/espnow.rst shipped; rotorman truck.py import espnow, ESPNow() add_peer/send/recv on a Core
bluetooth (aioble) NO for bluetooth module (doc’d removed). BLE exists only via frozen vendor ble_module (shutter remote, app_timelapse) index.rst list contains bluetooth; aioble needs it -> unavailable. Not run on device.
WebREPL NO (doc’d removed) index.rst list contains webrepl

Stock RC pairing (rc_module is frozen, source not public): docs/cyberbrick_core/lib/rc_module.rst documents rc_master_init/rc_master_data/rc_slave_init/rc_slave_data; data = tuple [L1,L2,L3,R1,R2,R3 ADC 0-4095, K1..K4 0/1]; “paired” state 0/1/2 “determined during pairing”. Channel, MAC handling, wire format: NOT visible (inside frozen module). Whether stock RC uses ESP-NOW vs another 2.4 GHz proto is not stated upstream; build-notes’ “ESP-NOW” is the designer’s claim.

Community (not stock): rotorman/CyberBrick_ESPNOW receiverPY/truck/truck.py: Wi-Fi channel fixed 1 (valid 1-11, edit constant); bind = receiver broadcasts own MAC to ff:ff:ff:ff:ff:ff every 500 ms while button held; payload CRSF 16 ch 11-bit (173/992/1811). Their README calls stock “original codebase”, i.e. alternative to it.

Unverified: import espnow on the exact build 3.4.0/e7cd27f2 (docs say removals don’t include it; one 30 s REPL check when serial is free). Bambu wiki not fetched.

WLAN.scan and connect on MicroPython 1.23 (2026-11-01, #195)

Section titled “WLAN.scan and connect on MicroPython 1.23 (2026-11-01, #195)”

Sources: docs/library/network.WLAN.rst and ports/esp32/network_wlan.c at tag v1.23.0 (github.com/micropython/micropython).

  • scan() blocks until the scan ends and returns (ssid, bssid, channel, RSSI, security, hidden) tuples, ssid as bytes (an empty ssid for a hidden network, since show_hidden is on); hidden is always False on the ESP32.
  • If esp_wifi_scan_start fails, scan() returns an empty list, no exception. ESP-IDF refuses to scan while the station is connecting, and after connect() the driver retries that network forever on every disconnect (reconnects defaults to 0 = unlimited in the C code; the docs’ “0=none” is the config() view, where -1 maps to it).
  • disconnect() clears wifi_sta_connect_requested, which stops those retries. So to change network: disconnect(), then scan(), then connect(ssid, key), which is non-blocking.
byYellow PineYellow Pine

noggin v0.2.26-6-g09bf9b7 · 09bf9b7