Bus Load Analysis & Optimization - System Architecture

Bus Load: Concept and Limits

Bus Load Definition

Bus load is the fraction of available bus capacity consumed by scheduled traffic. A CAN bus running at 500 kbit/s with 300 kbit/s of signal traffic has 60% bus load.

Why limits matter:

CAN: bus errors and retransmissions are counted as load; 60% target leaves 40% for error recovery and future signals
CAN-FD: 60% nominal / 80% peak; arbitration phase load and data phase load calculated separately
Ethernet: 50% sustained target; TSN credit-based shapers need headroom to work correctly

Bus Load Calculator

Pythonbus_load_calc.py

"""CAN/CAN-FD bus load calculator."""
from dataclasses import dataclass
from typing import List

@dataclass
class CanFrame:
    name:       str
    can_id:     int
    dlc_bytes:  int
    cycle_ms:   float
    extended:   bool = False  # 29-bit vs 11-bit ID

    def bit_length_classic(self) -> int:
        """CAN 2.0 frame size in bits (worst case with bit stuffing)."""
        id_bits  = 29 if self.extended else 11
        overhead = 1+id_bits+1+1+1+4+15+1+1+1+7  # SOF+ID+RTR+IDE+r0+DLC+CRC+CRC_delim+ACK+ACK_delim+EOF
        data_bits = self.dlc_bytes * 8
        # Worst-case bit stuffing: +20% for classic CAN
        return int((overhead + data_bits) * 1.2)

    def utilisation_pct(self, bitrate_kbps: int) -> float:
        """Fraction of bus capacity used by this frame."""
        bits_per_s  = self.bit_length_classic()
        frames_per_s = 1000.0 / self.cycle_ms
        load_kbps   = bits_per_s * frames_per_s / 1000.0
        return load_kbps / bitrate_kbps * 100

def analyse_can_bus(frames: List[CanFrame],
                     bitrate_kbps: int = 500,
                     limit_pct: float = 60.0) -> dict:
    total_load = sum(f.utilisation_pct(bitrate_kbps) for f in frames)
    for f in sorted(frames, key=lambda x: -x.utilisation_pct(bitrate_kbps)):
        print(f"  {f.name:<30} {f.utilisation_pct(bitrate_kbps):.2f}%")
    print(f"  Total: {total_load:.1f}%  (limit {limit_pct}%)  "
          f"[{'OK' if total_load <= limit_pct else 'OVER LIMIT'}]")
    return {"total_pct": total_load, "ok": total_load <= limit_pct}

CHASSIS_CAN = [
    CanFrame("VehicleSpeed",     0x1A3, 8, 10.0),
    CanFrame("WheelSpeeds",      0x1A4, 8,  5.0),
    CanFrame("SteeringAngle",    0x2B1, 8, 10.0),
    CanFrame("BrakeRequest",     0x3C2, 4,  5.0),
    CanFrame("EngineStatus",     0x4D0, 8, 20.0),
    CanFrame("TransmissionData", 0x5E1, 8, 20.0),
]
analyse_can_bus(CHASSIS_CAN)

Summary

Bus load analysis is one of the few architecture activities that can definitively prove a design is infeasible before any hardware is built. A chassis CAN bus with 15 signals at 5ms cycle time at 500 kbit/s will exceed 80% load -- this is calculable from the signal database before a single ECU is designed. The calculator reveals which frames contribute most to load (high-frequency, long-frame signals), enabling targeted optimisation: increasing cycle times for non-safety-critical signals, moving high-frequency signals to CAN-FD or Ethernet, and splitting signals across multiple buses. The worst architectural mistake is discovering the CAN bus is overloaded during integration testing when all the ECUs are already built and the wiring harness is manufactured.

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