NeonPocket Ultimate Companion RCC6 v2.2.0 RC1
Pre-releaseNeonPocket Ultimate Companion RCC6 v2.2.0 RC1
Ultimate 2.2 is an experimental RCC6-L62/SX1262 + 220×128 NV3001B prerelease. It keeps every earlier release available and must not be flashed to RC32, RC52, or another RadioCore layout.
Choose exactly one image
- BLE:
NeonPocketMC-RCC6-Ultimate-v2.2.0-rc.1-BLE-app.bin - Web:
NeonPocketMC-RCC6-Ultimate-v2.2.0-rc.1-Web-app.bin - signed Web OTA:
NeonPocketMC-RCC6-Ultimate-Web-v2.2.0-rc.1.npu
Normal USB flashing writes the app-only binary at 0x10000. Use a separately named merged recovery image at 0x0 only for bootloader/partition recovery. Neither path reaches SPIFFS; do not erase the whole chip.
What 2.2 adds
- A rebuilt Web experience with five plain-language areas: Dashboard, Messages, Map, Radio, and Device.
- Grouped 24-hour and seven-day RX/TX/failure bar charts, alongside the existing live signal and two-hour telemetry.
- A local mesh map that plots only contacts carrying valid advertised coordinates. Contacts without location remain visible in the list and are never assigned a guessed position.
- At-a-glance delivery, message-history, packet, memory, storage, battery, display-transfer, and queue health.
- Cleaner human-facing labels throughout; diagnostic implementation terms stay in the detailed Device view.
- A persisted battery-size setting in the authenticated WebUI and USB CLI Rescue. For a 420 mAh pack, enter
set.batterysize 420ornp battery size 420; enter0to clear it.
RCC6 does not expose raw charger VBUS to firmware, but ESP32-C6 can detect an enumerated live USB host. A live-host disconnect clears charger-biased samples and starts a clean discharge-learning window; wall chargers and power banks fall back to at least ten minutes of sustained falling-voltage samples. Battery size is descriptive metadata; ADC calibration remains the separate multimeter-derived np battery offset <mV> setting.
The firmware source uses official MeshCore 1.17.0 plus the relevant post-release SX126x boosted-RX-gain persistence fix. There is no official upstream MeshCore 1.17.1 tag at the time of this release.
TCP/5000 remains always enabled in Web mode and carries the unrestricted MeshCore companion/admin protocol. Any trusted-LAN client can use it; HTTP authentication does not protect it.
Release proof
- exact source/tag:
ef5a16d2fa1987934ae2752ffd64bd3a437c5366 - exact-main GitHub Actions: run 31579070019
- upstream tests, deterministic WebUI verification, stable BLE/Web regressions, Ultimate BLE/Web builds, budgets, markers, manifests, and signed NPU checks all passed
- exact Web app SHA-256
96931e7d3bd54562f829ec9d4738642bdfcd17c712c3a2792cbee5bc45d1efcfwas app-only flashed and flash-verified on the connected RCC6 - the device re-enumerated with its preserved USB identity, booted the authenticated dashboard at its saved LAN address, and exposed TCP/5000
The on-device gallery in the repository was captured from the connected RCC6 framebuffer; it is device-rendered output, not a browser mockup.