Log in

Docs

Getting started.

The short version for both apps. Full reference documentation is being written; until it is published, write to sales with questions.

Online app

  1. Sign in. Open app.candataextract.com and sign in with Google, Microsoft Entra ID, a password or a passkey.
  2. Open a namespace. Access is by invite. Your private namespace, or a team namespace you were invited to, appears in the namespace selector after you open it once.
  3. Import a trace. Add a candump log, PCAN TRC, VCDS, ODIS or MF4 file to a collection. The frame table loads it with ISO-TP streams reassembled.
  4. Decode. Select a row to open the byte decoder. Hover a field to see its bytes.
  5. Add a transform. Write a CEL expression that picks a value out of a payload, check the highlighted matches, and save it to the namespace.

Desktop app

  1. Connect an adapter. SocketCAN on Linux (can0), PCAN on macOS and Windows (PCAN_USBBUS1). Set the bus bitrate, usually 500 kbit/s for diagnostics on passenger cars.
  2. Record. Start a capture, run your diagnostic tool or the built-in scan, and stop. Save the capture locally or stream it to a namespace.
  3. Scan. Read the VIN, discover the manufacturer's ECUs, and read their data identifiers and fault codes.
  4. Simulate. Build a simulator config from a capture and run it on a CAN interface, so a diagnostic tool can talk to the car without the car.

Reading frames

CAN Data Extract writes data the way the tools you already use do.

  • Hex is uppercase, two digits per byte, one space between bytes: 02 10 03. The 0x prefix appears only for a single value in prose, as in "service 0x10".
  • Frames are written ID#DATA, the cansend form. IDs are three digits for 11-bit (7E0) and eight for 29-bit (18DA10F1).
  • Direction is a glyph: → request, ← response. A request is written before its response.
  • Services use the standard's names with their hex value: DiagnosticSessionControl (0x10), ReadDataByIdentifier (0x22).
  • Negative responses name the NRC on first mention: NRC 0x78 (requestCorrectlyReceived-ResponsePending), 7F 10 78 inside a payload.
  • Time is ISO 8601 with a zone, 2024-10-22T09:40:26.489Z. Deltas in tables have six decimals: +0.000124 s.
→ 7E0#02 10 03                DiagnosticSessionControl (0x10), extended session
← 7E8#06 50 03 00 32 01 F4    positive response, P2 = 50 ms, P2* = 5000 ms

Formats and adapters

Protocols
UDS (ISO 14229), KWP2000, OBD, ISO-TP, CAN FD, 11-bit and 29-bit IDs
Trace formats
candump log, PCAN TRC, VCDS, ODIS, MF4
Adapters
SocketCAN on Linux, PCAN on macOS and Windows
Sign-in
Google, Microsoft Entra ID, password, passkey