All work

Carver engine sound and CAN bus

An engine sound for a small electric vehicle that follows its own CAN bus: a team project in my embedded-systems minor.

Developer in a student teamSep 2026 – nowTeensy 4, ESP32, CAN bus, SavvyCAN, FlutterWork in progress

Carver Lab, my Flutter app for the engine sound, on the Drive tab with a car profile and volume control.

The problem

The vehicle’s CAN bus is undocumented. To make the engine sound follow speed and throttle, we first had to find out which messages carry which signal.

What I built

  • A map of the CAN bus. I logged the bus in listen-only mode, one log per driving situation. Comparing idle against action pointed to candidate bytes, which were checked against a second source. The result is a DBC file with a confidence level per signal. The data also showed where the vehicle limits its torque, around 75 km/h, and when it brakes regeneratively.
  • Advice on sound from a phone. I tested whether the phone could play the sound. Bluetooth audio adds about 120 to 330 ms of delay against a 30 ms requirement, so I advised keeping the sound on the microcontroller, with a phone app as a remote control over Bluetooth Low Energy.
  • Carver Lab, that app, in Flutter. It connects to an ESP32 over Bluetooth Low Energy, shifts automatically or by hand, and keeps car profiles with their cylinders, idle and rev limiter, and exhaust tone.
Two charts: the same throttle signal found in two CAN messages, and a demand value that follows the pedal with a delay.
The throttle pedal, decoded from two different CAN messages, and the demand that follows it with a delay.

My part

In the team I did the CAN bus analysis and the research into sound from a phone, and I built the Carver Lab app.

Status

Work in progress. A detour from backend work: I enjoyed it, but my focus stays on software.