Hands-On: Vehicle Network Design - System Architecture

Lab: Vehicle Network Design

Deliverable	Specification	Constraint
Network topology	Zone architecture; 3 zones + HPC + GW	All ECU pairs connected; no orphaned ECUs
Bus load table	CAN-FD loads for each bus segment	All segments < 60% load
Routing table	All inter-domain signals with source/dest	No missing signals; no duplicate IDs on same bus

Exercise 1: Bus Assignment

YAMLnetwork_design.yaml

# Zone vehicle network design
network:
  backbone:
    type: "1000BASE-T1 Ethernet"
    nodes: [HPC_ADAS, GATEWAY_ECU, TELEMATICS]
    load_target_pct: 50

  eth_zone_fl:
    type: "100BASE-T1 Ethernet"
    nodes: [HPC_ADAS, ZONE_ECU_FL]
    load_target_pct: 50

  eth_zone_fr:
    type: "100BASE-T1 Ethernet"
    nodes: [HPC_ADAS, ZONE_ECU_FR]

  eth_zone_rear:
    type: "100BASE-T1 Ethernet"
    nodes: [HPC_ADAS, ZONE_ECU_REAR]

  can_chassis:
    type: "CAN-FD 500k/2M"
    nodes: [GATEWAY_ECU, ABS_ECU, EPS_ECU, BRAKE_ECU]
    load_target_pct: 60
    frames:
      - {name: WheelSpeeds,    id: 0x1A4, dlc: 8, cycle_ms: 5}
      - {name: SteeringAngle,  id: 0x2B1, dlc: 8, cycle_ms: 10}
      - {name: BrakePressure,  id: 0x3C1, dlc: 4, cycle_ms: 5}

  can_body:
    type: "CAN 500k"
    nodes: [GATEWAY_ECU, BCM, HVAC_ECU, LIGHT_ECU]
    load_target_pct: 60

  lin_seats:
    type: "LIN 19.2k"
    master: ZONE_ECU_REAR
    slaves: [SEAT_MOTOR_FL, SEAT_MOTOR_FR, SEAT_MOTOR_RL, SEAT_MOTOR_RR]

Summary

The vehicle network design lab integrates three separate analyses (topology, bus load, routing) into a coherent design that can be handed to an NRE tool (PREEvision, CONA) for formal harness design. The most common lab finding is that the chassis CAN-FD bus exceeds 60% load when all safety-critical signals are assigned to it at their required cycle times -- requiring either migration of some signals to Ethernet or increasing cycle times of non-safety-critical chassis signals. The routing table exercise typically reveals missing signals (a function was allocated to an ECU on one network but its input signals are only published on a different network with no routing entry) -- the type of gap that would cause a silent malfunction in integration testing.

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