Vehicle Networks & Communication

CAN integration for difficult network behavior

Diagnose and integrate CAN communication when messages disappear, gateways route data incorrectly, ISO-TP exchanges fail, or signal meaning is unclear. The work can start from recordings, CAN data, DBC definitions, and a clear problem description.

Discuss a CAN Project

Problems I can investigate

Find the behavior behind the symptom

  1. 01

    CAN gateway issue

    Trace messages across network boundaries to assess whether they are missing, modified incorrectly, or routed to the wrong CAN network.

  2. 02

    ISO-TP communication failure

    Examine segmented diagnostic communication for addressing, flow-control, and timing behavior that may prevent a complete exchange.

  3. 03

    CAN message missing

    Compare expected communication with live traffic or a recording to identify where an expected CAN frame is absent.

  4. 04

    Unknown CAN signal

    Use available CAN data and DBC definitions to investigate the meaning, encoding, scaling, and context of an undocumented payload field.

What I can help with

Focused engineering work in Vehicle Networks & Communication

CAN and CAN-FD integration analysis

Review messages, signals, nodes, and network behavior across CAN and CAN-FD communication, using available definitions and observed traffic.

  • CAN
  • CAN-FD
  • DBC

Gateway and message-path investigation

Follow message presence and content across a network gateway to isolate routing or modification behavior that warrants further debugging.

  • CAN
  • CAN-FD
  • CANoe
  • CANalyzer

ISO-TP and diagnostic transport analysis

Inspect segmented communication over CAN, including addressing, flow-control, and timing behavior relevant to ISO-TP exchanges.

  • ISO-TP
  • UDS
  • CanTp

Recorded traffic decoding

Decode CAN recordings and raw frames against DBC definitions, then compare signal values and message behavior with the reported symptoms.

  • DBC
  • CANalyzer
  • BLF
  • cantools

Focused CAN simulation and analysis workflows

Build repeatable analysis or restbus simulation workflows for missing network nodes and communication that needs controlled reproduction.

  • CANoe
  • python-can
  • cantools

What to send

Start with the evidence you already have

How the analysis works

From recorded data to engineering findings

  1. 01

    1. Establish the communication scope

    Review the problem description and available recordings, CAN dumps, and DBC data to define the affected messages, signals, nodes, and network path.

  2. 02

    2. Decode and compare evidence

    Decode the relevant frames and compare expected communication with observed traffic, including message presence, payload changes, signal values, and segmented exchanges.

  3. 03

    3. Reproduce the focused behavior

    Where useful, create a controlled analysis or restbus simulation workflow to examine missing-node communication and narrow the conditions associated with the issue.

  4. 04

    4. Document findings and next actions

    Separate observed evidence from interpretation, record remaining uncertainty, and provide maintainable analysis outputs or integration artifacts.

What you receive

Deliverables matched to the investigation

Engineering analysis

A documented technical analysis with evidence, findings, affected communication, and remaining questions.

CAN decoding results

Decoded CAN frames, signals, and interpretation notes based on the supplied recordings, CAN data, and DBC definitions.

DBC file

A CAN database describing messages, signals, scaling, and nodes where the available evidence supports those definitions.

Python analysis script

A maintainable Python workflow for repeatable engineering-data analysis and CAN decoding.

Restbus simulation

A simulation of missing network nodes and their communication for focused investigation or testing.

Technologies & formats

Automotive data and analysis environments

FAQ

Practical questions before an investigation

What is needed to start a CAN integration investigation?
A problem description plus any available BLF recording, ASC recording, CAN dump, and DBC. The work can begin with incomplete data, with gaps recorded as part of the analysis.
Can you investigate a missing CAN message?
Yes. The investigation can compare expected communication with a recording or live-traffic evidence, then assess message presence, routing context, and available signal definitions.
Can you work on ISO-TP communication failures?
Yes. The analysis can focus on addressing, flow-control, timing behavior, and segmented communication over CAN without assuming undocumented ECU behavior.
Will the result include a repeatable analysis workflow?
Where appropriate, the deliverables can include a Python analysis script, decoded results, or a restbus simulation for repeatable examination of the reported behavior.

Discuss the evidence

Discuss a CAN Project

Send the available recording, DBC, CAN dump, and problem description. I can review the evidence and outline a focused CAN integration investigation.