Skip to content

Bring your own car

The bundled Ioniq profile is an example. The tooling of canair works with any vehicle. This journey takes you from nothing to decoded, verified diagnostic signals for your car. You store the result in a profile that you can share.

You do not need to know the PIDs of your car in advance. The discovery and scan commands are a write path. They add what they find to the profile, so the profile grows while you work.

The arc

%% pele: horizontal flowchart LR A["Set up<br/>steps 1–4"] --> B["Capture<br/>step 5"] B --> C["Analyze<br/>step 6"] C --> D["Define & verify<br/>step 7"] D --> E["Share<br/>step 8"] C -.->|more data needed| B

In words: you set up the profile in steps 1 to 4. Then you capture data (step 5), analyze it (step 6), define and verify the signals (step 7), and share the result (step 8). If the analysis shows that you need more data, you go back and capture again.

Step You do Result
1. Create a profile canair profile create An empty, valid profile bundle
2. Discover ECUs canair discover --register Every responding ECU written into ecus/
3. Read identity canair identity / discover --identify Part numbers, versions, VIN
4. Scan for data canair scan Which PIDs/DIDs each ECU answers
5. Capture canair read … --save Real payloads with driving/charging context
6. Analyze decode / correlate / hunt / investigate Which byte is which signal
7. Define & verify canair pids upsert-param, coverage Named signals in ecus/
8. Share canair wican autopid write WiCAN AutoPID JSON and a profile to contribute

There is an optional side journey. 9. Broadcast CAN frames decodes signals that the car broadcasts on its internal bus, such as drive mode, regen and wheel speeds. The ECUs do not answer these on request. The side journey is a parallel import, analyze and define arc. Use it when you have a raw frame log. See also Broadcast CAN frames.

It's a loop, not a line

Reverse engineering is iterative. You often capture data and analyze it. Then you find that you need different conditions, for example accelerating or coasting, and plugged in or charging. Then you capture again. This is normal. The dashed arrow in the diagram shows it.

The rule: read and capture freely, define conservatively. Mark new signals --unverified. Promote a signal only after you confirm it against a known reference, or across enough captures. See Define & verify.

Before you start

Complete Getting started first. canair must be installed, your dongle must be configured, and canair status must report a reachable device. Every step below needs this.


Next: 1. Create a profile →