Hands-On: CAN-FD Communication Setup - Vehicle Networks

Vector VN1610 FD Configuration in CANoe

CANoe Configuration Step	Value	Verification
Channel type	CAN FD (not CAN 2.0)	FD indicator in channel icon
Nominal bit-rate	500 kbps	Prescaler=8, Ph1+Prop=31, Ph2=8 @ 64 MHz
Data bit-rate	2000 kbps	Prescaler=2, Ph1=15, Ph2=4, SJW=4 @ 64 MHz
Transceiver	TJA1044 (2 Mbps capable)	Hardware catalog entry shows FD support
Termination	120 Ω at each bus end	Measure bus idle differential = 0 V ± 50 mV

CAPLfd_frame_inject.can

/* CANoe CAPL: transmit CAN-FD frame with BRS, 64-byte payload */
variables {
    message FDTestMsg test_fd;
    msTimer fdTimer;
}

on start {
    test_fd.id = 0x123;
    test_fd.fd = 1;     /* FD frame */
    test_fd.brs = 1;    /* Bit Rate Switch */
    test_fd.dlc = 15;   /* DLC=15 → 64 bytes */
    setTimer(fdTimer, 10);
}

on timer fdTimer {
    int i;
    for (i = 0; i < 64; i++) {
        test_fd.byte(i) = i & 0xFF;  /* pattern 0,1,2,...,63 */
    }
    output(test_fd);
    setTimer(fdTimer, 10);
}

ARXML/FIBEX Network Description Import

Shellcanoe_arxml_import.sh

# CANoe command-line: import ARXML network description and verify signal decoding
# First generate ARXML from DaVinci or EB tresos:

# 1. Export system description from DaVinci
davinci_cli.exe -project ECU_Powertrain.dpj -gen-arxml -output ECU_Powertrain_SysDesc.arxml

# 2. Import into CANoe (CANoe command-line interface)
canoe_cli.exe -config Powertrain_Test.cfg     -import-arxml ECU_Powertrain_SysDesc.arxml     -assign-channel CAN0

# 3. Verify signal definitions match DBC
python3 -c "
import cantools, capl_logger
db_dbc  = cantools.database.load_file('powertrain.dbc')
db_arxml = cantools.database.load_file('ECU_Powertrain_SysDesc.arxml')
for msg_dbc in db_dbc.messages:
    msg_arxml = db_arxml.get_message_by_name(msg_dbc.name)
    for sig_dbc in msg_dbc.signals:
        sig_arxml = msg_arxml.get_signal_by_name(sig_dbc.name)
        assert sig_dbc.start == sig_arxml.start, f'{sig_dbc.name}: bit pos mismatch'
print('ARXML signal positions match DBC')
"

Bus Stress Test: 90% Load with Termination Mismatch

CAPLbus_stress_test.can

/* Inject 90% CAN-FD bus load and verify zero error frames */
variables {
    message StressMsg_0x7FF stress;
    msTimer stressTimer;
    int error_frame_count = 0;
    long test_start_time;
}

on start {
    stress.id  = 0x7FF;
    stress.fd  = 1;
    stress.brs = 1;
    stress.dlc = 15;  /* 64 bytes = max payload */
    test_start_time = timeNow();
    setTimer(stressTimer, 1);  /* 1 ms interval = ~90% load at 2 Mbps FD */
    write("Stress test started. Target: 90%% load, 0 error frames.");
}

on timer stressTimer {
    output(stress);
    setTimer(stressTimer, 1);
}

on errorFrame {
    error_frame_count++;
    write("ERROR FRAME at t=%.1f ms (count=%d)",
          (timeNow() - test_start_time) / 100000.0, error_frame_count);
}

on stop {
    if (error_frame_count == 0)
        write("PASS: Zero error frames under 90%% FD load");
    else
        write("FAIL: %d error frames — check termination and timing", error_frame_count);
}

AUTOSAR CanIf Verification Checklist

CanIf Config Parameter	Correct Value	Symptom if Wrong
CanIfTxPduCfg.CanIfTxPduCanId	Must match DBC/ARXML CAN ID exactly	ECU transmits on wrong ID — receiver never sees frame
CanIfCtrlDrvCfgRef → FD prescaler	Must match hardware timing config	Bit timing mismatch → all FD frames generate error frames
CanIfRxPduCfg acceptance mask	0x7FF for standard, 0x1FFFFFFF for extended	Too-narrow filter drops valid frames; too-wide receives unintended ones
CanIfCtrlDrvCfg.CanIfCtrlCanFDSupport	TRUE for FD frames	FD frames not generated; DLC limited to 8
DLT log on RxIndication	Should trigger on every received matching frame	If silent: filter mismatch or wrong CAN ID in CanIfRxPduCfg

Summary

CAN-FD setup validation requires four sequential checks: hardware timing (oscilloscope BRS transition), protocol decode (CANoe trace with ARXML showing correct signal values), stress test (90% load, zero error frames), and AUTOSAR CanIf filter verification (RxIndication triggered on every expected frame). Skipping any step leaves a class of failure undiscovered until vehicle integration.

🔬 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.