Why it matters
Most integration problems in an ECU are communication problems: a signal arrives late, in the wrong format or not at all. Knowing the path a signal takes makes them findable.
What the layers are
| Module | Role |
|---|---|
| COM | Packs signals into PDUs, handles timeouts, update bits, transmission modes |
| PduR (PDU Router) | Routes PDUs between COM, transport protocols, SecOC and bus interfaces — and between buses on gateways |
| SecOC | Adds/verifies authenticators for selected PDUs |
| CanTp / LinTp / DoIP | Transport protocols for long messages (e.g. diagnostics) |
| CanIf / LinIf / SoAd | Bus-specific interfaces |
| Drivers | Hardware access (MCAL) |
How a message flows
An application writes a signal → the RTE passes it to COM → COM packs it into a PDU and triggers transmission → PduR sends it (via SecOC if configured) to CanIf → the CAN driver puts it on the bus. Reception runs the same path upward, with timeout monitoring in COM.
Simplified CAN transmit path; configured SecOC protection adds authentication processing along the PDU routing path.
Best practices
- Generate stack configuration from one communication database for all ECUs.
- Configure timeouts and substitute values explicitly for every received signal.
- Keep gateway routing in PduR simple and documented.
Common pitfalls
- Inconsistent PDU layouts between sender and receiver after a database change.