Reverse engineering my e-scooter and rewriting the firmware in Rust

📝 Discussion Summary (Click to expand)

Safety concerns about modified firmware
Users widely expressed worry that bypassing manufacturer restrictions (e.g., speed limits) could lead to real-world dangers, especially if modifications introduce unpredictable behavior.

"From what I've seen on the streets, people bypassing the restrictions will not, and there will be injuries." – TheChaplain
Debate over LLMs/AI in development ("vibe coding")
The discussion split on whether LLMs genuinely enable innovation or merely produce superficial results without deep understanding, with critics arguing they skip essential learning.

"Just because you can pull the lever on an LLM enough times and get something that works doesn’t mean you’ve done the work." – nearlyepic
Open vs. closed hardware ecosystems
Many debated the trade-offs between manufacturer lock-in (for safety/IP) and the benefits of open, interoperable components for innovation, cost reduction, and repairability.

"I believe one of the feasibilities we have with electric locomotion is the standardization of components: electric motors, motor controllers, batteries and battery chargers. These being interchangeable will lead to lower costs through competition and more innovation." – hn_submit

🚀 Project Ideas

Automatically analyzes CAN/log dumps from e-scooter firmware to infer message IDs, payload structure, and semantics.
Generates Rust struct definitions, documentation, and example code to speed up custom firmware development.
Core value proposition: reduces tedious reverse‑engineering work from hours to minutes using LLMs.

Key	Value
Target Audience	Embedded hobbyists, scooter modders, firmware engineers
Core Feature	LLM‑driven extraction of CAN bus specifications from raw trace files (CSV, PCAP, UART logs)
Tech Stack	Python backend, FastAPI, LLM API (e.g., Llama 3 via Ollama), React frontend, optional WASM for local processing
Difficulty	Medium
Monetization	Revenue-ready: SaaS subscription $10/mo per user or pay‑per‑analysis credits

HN commenters wished LLMs could “eat this kind of stuff for lunch” (tverbeure) and wanted help with the tedium of reverse engineering (IshKebab).
Provides a shareable database of decoded messages, encouraging community collaboration and safer custom firmware.
Could be extended to other buses (UART, SPI) and integrated into IDE plugins.

Defines an open, vendor‑neutral CAN‑based protocol for battery‑to‑controller communication (state‑of‑charge, voltage, temperature, auth).
Provides a ready‑to‑run Rust library and example firmware for both scooter side and battery side.
Core value proposition: breaks vendor lock‑in, enables safe third‑party batteries and chargers, fosters competition.

Key	Value
Target Audience	E‑scooter/e‑bike manufacturers, DIY builders, battery pack vendors
Core Feature	Reference stack: CAN transport, message definitions (SoC, current limits, error codes), cryptographic handshake, safety shutdown logic
- Tech Stack	Embedded Rust (no_std), Zephyr RTOS optional, Cargo, CI with GitHub Actions
Difficulty	High
Monetization	Hobby (open source) – optional paid support/consulting for companies

Commenters lamented Bosch’s closed battery ecosystem and wanted an open protocol (hn_submit, surajrmal).
An openly spec’d protocol would let users mix‑and‑match batteries without safety fears, addressing concerns raised by awakeasleep and Aurornis about liability.
Could become a de‑facto standard, spurring discussion on HN about open hardware ecosystems.

Runs custom firmware in a cycle‑accurate emulator (Renode/QEMU) with virtual CAN, ADC, PWM peripherals.
Executes property‑based tests and fuzzing to detect unsafe behavior (e.g., unintended throttle lock, brake inversion, over‑current).
Generates safety reports and CI badges.
Core value proposition: gives developers confidence before flashing hardware, reducing risk of bricking or accidents.

Key	Value
Target Audience	Firmware engineers, hobbyists writing custom e‑scooter/Rust firmware
Core Feature	Automated safety verification suite: threat model checks, fault injection, coverage reporting
Tech Stack	Rust test harness, Renode emulator, Python scripts for test generation, optional WASM UI for report viewing
Difficulty	High
Monetization	Revenue-ready: tiered CI service – free for open‑source, $20/mo for private repos

HN users expressed fear of “instantly locking the engine” and “burning the motor out” (binary0010) and wanted a way to test without bricking (quietraster).
Provides concrete safety feedback that addresses the legal/insurance worries raised by BrandoElFollito and tverbeure about malicious mods.
Encourages sharing of verified firmware patches, fostering trust in the modding community.