CAN Bus Reverse Engineering & Vehicle Electronics Engineering

CAN Bus reverse engineering is the process of capturing vehicle network traffic, correlating messages with physical actions or vehicle states, and identifying how useful information is encoded. The result may include CAN identifiers, byte positions, bit fields, scaling, offsets, update rates and state definitions. We validate the decoded signals through repeatable tests on the vehicle and document them so they can be integrated into firmware, software or a connected product.

Yes. We analyze undocumented CAN traffic by combining controlled vehicle tests, synchronized data capture, message filtering, statistical comparison and repeated validation. Typical targets include ignition state, doors, locks, lights, speed, RPM, battery status, controls and other application-specific events. Feasibility depends on the vehicle architecture, access to the relevant network and whether the required information is present on the bus.

Yes. We analyze LIN Bus communication between local controllers, switches, sensors and actuators. LIN analysis can be useful when a required function is not exposed directly on the main CAN network or when a product needs to interact with a specific door, lighting, seat, climate or body electronics module. The work may include frame capture, schedule analysis, signal identification and validation of module behaviour.

Deliverables are adapted to the project and can include raw capture files, a signal matrix, CAN IDs, LIN frames, decoded values, state tables, scaling and offset information, test procedures, technical reports, example code, firmware, integration libraries and validation results. The objective is to provide information that your engineering team can reproduce, understand and use.

Yes. We can continue from signal discovery into embedded firmware, CAN or LIN gateways, data loggers, test tools, APIs, dashboards and backend integrations. This avoids the loss of context that often occurs when reverse engineering and implementation are handled by separate teams. Development can target platforms such as ESP32, STM32 and custom interfaces depending on the technical requirements.

Yes. Real vehicle validation is central to our process. A signal that appears correct in one capture may behave differently during startup, sleep, diagnostics, changing operating modes or under other network conditions. We perform controlled functional tests, repeat captures and verify the expected behaviour before documenting a result or delivering an integration.

We support companies developing fleet management systems, telematics and GPS devices, vehicle security products, dashcams, ADAS integrations, OEM retrofit solutions, diagnostic tools, commercial vehicle electronics, camper systems and connected vehicle prototypes. We can also apply vehicle network and embedded engineering methods to industrial, agricultural and special-purpose machinery.

Our vehicle electronics work is based in Barcelona, Spain, and we support engineering teams across Europe. Some phases can be completed remotely using captures, hardware and technical documentation, while projects requiring direct access to a vehicle can be performed in our lab or coordinated according to the vehicle and project needs.