Signal Gateway & Multi-Bus Routing - AUTOSAR Classic BSW

CAN-to-CAN Raw PDU Gateway

CAN-to-CAN Gateway Path

  CAN1_Rx PDU (0x321)
       │  CanIf_RxIndication
       ▼
  PduR: CAN1_EngineStatus → CAN2_EngineStatus routing path
       ▼
  CanIf_Transmit(CAN2_EngineStatus_TxPduId)
       ▼
  CAN2_Tx PDU (0x321) — identical payload forwarded

CAN-to-LIN Gateway

XMLPduR_Gateway_CAN_LIN.arxml

<PDU-R-ROUTING-PATH>
  <SHORT-NAME>EngineRPM_CAN_to_LIN</SHORT-NAME>
  <PDU-R-ROUTING-PATH-SOURCE>
    <SRC-PDU-REF>/CanIf/RxPdus/EngineRPM_Rx</SRC-PDU-REF>
  </PDU-R-ROUTING-PATH-SOURCE>
  <PDU-R-ROUTING-PATH-DESTINATIONS>
    <PDU-R-ROUTING-PATH-DESTINATION>
      <DEST-PDU-REF>/LinIf/TxPdus/EngineRPM_LinTx</DEST-PDU-REF>
    </PDU-R-ROUTING-PATH-DESTINATION>
  </PDU-R-ROUTING-PATH-DESTINATIONS>
</PDU-R-ROUTING-PATH>

⚠️ CAN-to-LIN Timeout

LIN (max 20 kbps) is slower than CAN (500 kbps). If a CAN PDU arrives faster than the LIN schedule table can transmit it, the PduR FIFO fills. Configure PduRQueueDepth ≥ 2 and include the forwarded PDU in the LIN schedule at least every 20 ms.

PduR FIFO Buffering

Parameter	Purpose	Typical Value
PduRQueueDepth	Number of PDU buffers per routing path Tx queue	2–4 for gateway ECUs
PduRDefaultValue	Byte substituted when Rx PDU times out	0x00 or signal invalid value
PduRTxConfirmationTimeout	Max wait for Tx confirmation before declaring failure	2 × PDU transmission time

Gateway Latency Budget

Path Segment	Typical Latency
CAN frame reception + CanIf_RxIndication	0.1–0.2 ms
PduR routing table lookup + FIFO enqueue	0.05–0.1 ms
CanIf_Transmit (BasicCAN queue)	0.1–0.5 ms
CAN frame transmission (500 kbps, 8-byte)	~0.128 ms
Total CAN→CAN gateway latency	0.4–1 ms typical

Summary

Gateway latency budgets must be included in every E2E deadline supervision window that spans a gateway ECU. Raw PDU forwarding is fastest; signal-based gateway adds COM processing time. FIFO depth and transmission queue priorities directly affect worst-case gateway latency under bus load.

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