Reverse engineering vehicle data guides
Find the data you need in a vehicle without its documentation: standard OBD-II PIDs, manufacturer data behind UDS identifiers, broadcast CAN signals, and the counters and CRCs that protect them. Every guide includes code you can run.
11 guides Read them in this order
- How to reverse engineer vehicle data: CAN, LIN, Ethernet and OBD-II Where the data you want lives in a vehicle, which method finds it, and which tools to use on each bus. A map of CAN, CAN FD, LIN, FlexRay, Automotive Ethernet, OBD-II and UDS for reverse engineering, with links to step-by-step guides.
- OBD-II port pinout, buses and secure gateways: what you can reach Which pins of the OBD-II connector carry CAN, K-line, J1850 and DoIP Ethernet, why many cars show no traffic on the port, how secure gateways limit aftermarket tools, and how to tell a live bus from a filtered diagnostic port. With a tested Python check.
- OBD-II PIDs explained: supported-PID bitmaps, formulas, trouble codes and VIN How to find out which OBD-II PIDs a car supports, decode the common ones, read trouble codes with service 03 and the VIN with service 09. Real frame layouts, a formula table and a tested Python scanner.
- Finding OEM data with UDS: how to scan DIDs with service 0x22 How to find manufacturer-specific data in an ECU when you have no documentation. Find the ECUs, scan data identifiers with ReadDataByIdentifier, read the negative responses, and work out what the bytes mean. Includes a tested Python scanner.
- Which ECU sends which CAN ID? Five ways to map a CAN bus How to find out which ECU transmits each CAN message when you have no DBC: disconnecting ECUs, start-up order, diagnostic identification, and fingerprinting senders by their clock drift. With a tested Python script that groups CAN IDs by sender.
- How to find counters, checksums and CRCs in CAN frames Identify alive counters, simple checksums and CRC-8 bytes in CAN messages from a log alone. Covers sum, XOR and nibble checksums, CRC-8 SAE J1850 and CRC-8H2F, hidden Data IDs as used by AUTOSAR E2E, and a tested Python search.
- Reverse engineering J1939 proprietary messages (PGN 0xEF00 and 0xFF00–0xFFFF) How to find and decode manufacturer-specific J1939 data on trucks, buses and off-highway machines. Proprietary A and B PGNs, grouping by source address, transport protocol, and using standard PGNs such as EEC1 engine speed as a built-in reference. With tested Python code.
- Reverse engineering LIN bus traffic and building an LDF How to sniff a LIN bus safely, check protected IDs and checksums, tell classic from enhanced checksums, recover the schedule and frame lengths, and write a starting LDF. With tested Python code and an LDF that parses in ldfparser.
- Reverse engineering automotive Ethernet: from capture to SOME/IP signals How to tap into an automotive Ethernet link, list every SOME/IP service from service discovery, and find signals in SOME/IP payloads without ARXML. Includes a standard-library Python pcap reader, a service lister and a payload survey, tested on a generated capture.
- Automated CAN reverse engineering: what the research shows A practical review of published methods that recover CAN signals automatically, from bit-flip statistics (READ, TANG) to complete DBC pipelines (CAN-D), reference matching (LibreCAN), frame reuse (CANMatch), byte-level clustering (ByCAN) and LLM agents, with what each one contributes and how to use the ideas.
- Reverse engineering CAN signals with AI: a pipeline you can test How automated CAN reverse engineering works, from bit-flip statistics to correlation with an OBD-II reference, and where an LLM agent fits. Includes a standard-library Python pipeline, a synthetic log with a known DBC, and measured results.