Mobile Menu

Benefits

Using the CAN Bus block in VisualSim provides:

  • Early System Validation: Test ECU communication strategies before hardware deployment.
  • Performance Analysis: Measure latency, bus utilization, and arbitration effectiveness.
  • Standards Compliance: Explore Classical CAN vs. CAN FD trade-offs.
  • Fault Tolerance Evaluation: Simulate error detection, retransmission, and fault recovery.
  • Scalability: Add more nodes to evaluate bus load and bandwidth allocation.
  • Cross-Domain Flexibility: Apply to automotive, industrial, aerospace, and healthcare systems.

The CAN (Controller Area Network) Bus block in VisualSim models a serial communication protocol extensively used in automotive, industrial, and aerospace systems. It enables multiple Electronic Control Units (ECUs) or nodes to communicate over a shared bus using a priority-based arbitration mechanism.

Each message on the CAN bus carries an identifier, which determines its priority. During simultaneous transmission attempts, the arbitration process ensures that the highest-priority message wins, preventing collisions. The model simulates bit-level arbitration, error detection, and frame timing, making it suitable for both functional and performance analysis.

This block is key for evaluating reliability, latency, and bandwidth utilization in distributed embedded systems before hardware implementation.

Overview

  • CAN Segments: Model different sections of a CAN network.
  • CAN Nodes: Represent ECUs or devices that generate and receive messages.
  • Arbitration Mechanism: Identifier-based system ensures collision-free message transmission.
  • Message Databases: Store signal IDs, cycle times, and payloads for structured simulation.
  • Filtering Mechanism: Prioritizes, routes, and discards messages as per application needs.
  • Error Handling: Detects bit errors, acknowledges lost frames, and ensures retransmission.

Supported Standards

The CAN block aligns with widely recognized CAN specifications:

  • Classical CAN (ISO 11898-1): 11-bit and 29-bit identifiers.
  • CAN FD (Flexible Data-Rate, ISO 11898-7): Higher payload (up to 64 bytes) and faster data phase.
  • CAN-XL standard: Extended bandwidth and frame size for next-generation systems.
  • ISO 11898-2: High-speed CAN physical layer.
  • ISO 11898-3: Low-speed, fault-tolerant CAN.
  • CANopen: Higher-layer industrial automation protocol.
  • SAE J1939: Heavy-duty vehicle and machinery communication standard.
  • ARINC 825: Aerospace adaptation of CAN for avionics.

Key Parameters

Configurable parameters include:

  • Arbitration_Bit_Rate_Mbps: Bit rate during arbitration phase (e.g., 500 kbps, 1 Mbps).
  • Data_Bit_Rate_Mbps: Bit rate during data transmission phase (CAN FD allows >2 Mbps).
  • Base_Rate: Defines the base cycle rate for messages.
  • Identifier Type: 11-bit vs. 29-bit IDs.
  • Payload Size: Classical CAN (8 bytes) vs. CAN FD (up to 64 bytes).
  • Error Models: Bit error probability, error frame handling.
  • Message Filtering Rules: Accept/reject based on ID ranges.
  • Bus Utilization Tracking: Reports percentage bandwidth consumed.
  • Retry Count: Defines how many times a message can be retransmitted.

Parameter Snapshots

  • Parameter 1
  • Parameter 2

Simulation Results

  • Latency Reports: End-to-end timing for different message priorities.
  • Utilization Analysis: Percentage of bus usage under different workloads.
  • Error Detection Reports: Lost frames, retries, and recovery metrics.
  • Throughput Studies: Compare Classical CAN vs. CAN FD bandwidth efficiency.
  • Plot 1
  • Plot 2

Application

The CAN block is widely applied across industries:
Automotive

  • Automotive
    • Powertrain and Engine Control
    • Safety-Critical Systems: Airbags, ABS, and ESC.
    • Diagnostics: Supports OBD-II and UDS protocols.
    • Infotainment & Body Electronics: Enables communication between ECUs for comfort and entertainment systems.
  • Industrial Automation
    • Real-Time Control: Synchronization of PLCs, sensors, and actuators.
    • Industrial Automation: Communication between robotics and factory equipment.
  • Aerospace & Defense
    • Flight control and avionics data sharing.
    • Military ground vehicles requiring deterministic communication.
  • Medical Devices
    • Embedded systems for patient monitoring and imaging equipment.

Integrations

  • Integrates with processor, memory, and sensor models for complete ECU simulation.
  • Can be used with Ethernet, FlexRay, and LIN models for mixed-network automotive systems.
  • Supports CAN-Ethernet gateways for modern automotive architectures.
  • Enables system-level co-simulation of control algorithms and communication delays.

View Demo

Schedule a consultation with our experts

    Subscribe