For developers
Planned work
Implementation and hardware acceptance tasks for contributors.
View source ↗Controller and phone acceptance
- [ ] Test WFB and wheel-e discovery and telemetry against the intended controller firmware; compare speed, voltage and angle with the phone app.
- [ ] Confirm the inferred WFB telemetry tail and live command encodings, including LOCK (12), against hardware. Check lock/unlock acknowledgement and persistence across power cycles.
- [ ] Exercise encrypted VESC Express pairing, failed PINs, retry and re-pairing after an upstream PIN change.
- [ ] Check phone proxy interoperability, MTU differences, sustained traffic, lease release and upstream loss over BLE, CAN and UART.
- [ ] Confirm proxy bond revocation after bike PIN changes/removal, PIN persistence, boot unlock and locked-screen timeout/wake behavior.
- [ ] Commission CAN/UART wiring with the required transceiver, controller discovery and multiple-controller routing.
Device and release acceptance
- [ ] Soak touch, scrolling and both orientations with concurrent radio traffic; investigate intermittent idle touch I2C NACKs.
- [ ] Measure sustained display responsiveness, internal heap minima and task-stack headroom under realistic load.
- [ ] Exercise USB and battery cold boots, reconnect/stale-data behavior and preference persistence.
- [ ] Test Wi-Fi/OTA success, interruption, cancellation, rollback and first-boot acceptance on the device.
- [ ] Confirm the GitHub Pages deployment and generated screenshots on the default branch.
Protocol coverage
- [ ] Resolve signature, argument order and scaling uncertainties in the supplied protocol notes before enabling persisted tuning or additional feature/horn commands.