Hands-On: CAN Bus Analysis with CANalyzer - Vehicle Networks

CANalyzer Setup and DBC Import

Step	CANalyzer Action	Verification
New config	File → New Configuration	Empty workspace opens
Add network	Insert → Network Block → CAN	CAN channel block appears
Hardware assign	CAN block → Properties → Channel → Vector VN1610	Hardware LED goes green when connected
Set bit-rate	CAN block → Properties → Bit Rate → 500 kbps	Matches target network
Import DBC	CAN block → right-click → Assign Database → powertrain.dbc	Signal names appear in Symbol Explorer
Start	Measurement → Start (F9)	Trace window populates with decoded frames

CAPLsetup_trigger.can

/* CANalyzer CAPL: trigger and log on error frames */
variables {
    int error_count = 0;
}

on errorFrame {
    error_count++;
    write("ERROR FRAME #%d at t=%.3f ms — TEC may be rising",
          error_count, timeNow() / 100000.0);
    /* timeNow() returns 100ns ticks */
}

on start {
    write("CAN monitor started. Watching for error frames...");
}

Trace Window Analysis Techniques

Analysis Goal	Trace Configuration	What to Look For
Find all error frames	Filter → Error Frames → Show	Red error frame rows; time-clustered errors = EMC burst
Decode physical values	Assign DBC → right-click signal → Add to Symbol Window	Live bar/graph of EngineSpeed, CoolantTemp, etc.
Check message timing	Right-click message ID → Show Delta Time	Delta should match DBC GenMsgCycleTime ±5%
Identify missing transmitters	Statistics window → Message ID filter	Message count = 0 → ECU not transmitting
Isolate fault to one node	TEC/REC monitor (via Diagnostics)	Rising TEC = fault originates at that transmitter

CAPL Scripting: Stimulus and Response Testing

CAPLengine_test.can

/* Simulate absent ECU and verify Gateway response */
variables {
    message EngineStatus eng_msg;
    msTimer periodicTimer;
}

on start {
    /* Start sending simulated EngineStatus at 10 ms */
    eng_msg.id = 0x100;
    eng_msg.dlc = 8;
    setTimer(periodicTimer, 10);
    write("Simulating ECU_Engine (0x100) at 10 ms");
}

on timer periodicTimer {
    /* Ramp EngineSpeed 800–3200 rpm over 30 seconds */
    float rpm = 800.0 + (timeNow() / 1e8) * 80.0;  /* 80 rpm/s ramp */
    if (rpm > 3200.0) rpm = 800.0;

    /* Pack to raw: raw = physical / factor = rpm / 0.25 */
    word raw_speed = (word)(rpm / 0.25);
    eng_msg.byte(0) = raw_speed & 0xFF;
    eng_msg.byte(1) = (raw_speed >> 8) & 0xFF;
    output(eng_msg);
    setTimer(periodicTimer, 10);
}

/* Verify Gateway forwards to CAN1 (body bus) */
on message CAN1.0x200 {  /* forwarded EngineSpeed on body bus */
    float fwd_rpm = (this.byte(0) + (this.byte(1) << 8)) * 0.25;
    write("Gateway forwarded: EngineSpeed = %.1f rpm", fwd_rpm);
}

Bus Load Measurement and Injection

CAPLbusload_test.can

/* Inject test traffic to verify network at 70% load */
variables {
    message TestLoad_0x300 load_msg;
    msTimer loadTimer;
    float target_load_pct = 70.0;  /* % */
}

on start {
    /* Calculate required injection rate for 70% load */
    /* Production bus = 40% load from DBC → inject 30% more */
    /* One 8-byte CAN frame ≈ 130 bits × 1 µs/bit = 130 µs */
    /* 30% of 1 Mbps = 300 kbps → 300000/130 ≈ 2307 frames/s ≈ 0.43 ms per frame */
    load_msg.id = 0x300;
    load_msg.dlc = 8;
    setTimer(loadTimer, 1);  /* 1 ms → ~100 extra frames/s ≈ 13 kbps */
    write("Injecting test load. Watch Statistics window for bus %% and error frames.");
}

on timer loadTimer {
    output(load_msg);
    setTimer(loadTimer, 1);
}

Summary

CANalyzer with a DBC assigned provides decoded physical-unit signals instantly — no manual bit manipulation needed. The three most valuable analysis workflows are: error frame triggering (find burst sources), delta-time measurement (verify cycle times against spec), and CAPL stimulus scripts (simulate absent ECUs or inject overload to stress-test the network). Always verify bus load stays below 60% under injection before network sign-off.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.