Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Diagnostics
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Time-triggered CAN, ISO 11898-4, adds a timetable to ordinary CAN. The frames on the wire are still CAN frames. The bit rate does not rise. What changes is who is allowed to start a frame at a given moment, so a chosen message has a reserved window instead of having to win arbitration against whatever else is waiting. The event-driven bus this sits on is described on the CAN page.

The basic cycle

One node is the time master. It sends a reference message, and that message starts a basic cycle. The cycle is a row of windows. An exclusive window is reserved for one message from one node. An arbitration window is ordinary CAN: anyone may start, and the identifier decides who continues. The pattern of windows is fixed when the network is designed. It can be any mix of the two kinds of window, and it stays fixed while the car is driving. At the end of the cycle the next reference message starts the next one.

Because the exclusive window is reserved, the message assigned to it has a known latest start time. On a busy event-driven bus the lowest identifiers get through and the rest wait. TTCAN spends some of the bus on reserved slots so that a particular frame, not merely the lowest identifier, has a bound. The throughput in bits per second is the same CAN throughput. The reserved slots are capacity that other frames leave alone.

If the time master goes quiet

The reference message is itself a CAN frame, so the usual error handling still applies. Up to seven further nodes may be potential time masters. If the current one stops sending the reference, the others compete to send it, and CAN arbitration picks the winner. The cycle continues under that node. A network with a single time master and no fallback stops being time-triggered when that node fails, and the wire stays quiet until something transmits again.

Where it sits among the other buses

ISO 11898-4 is a published extension, and it is uncommon on the diagnostic socket. Cars that needed a stricter timetable than event-driven CAN, for chassis or safety traffic, generally added a different network for that traffic. FlexRay was the network built for that job in that generation. The diagnostic conversation on the 16-pin socket stays the event-driven CAN described on the CAN page, carried by ISO-TP or, on Volkswagen Group modules of that era, by TP 2.0.

Sources

  • ISO 11898-4. Time-triggered communication on CAN: the reference message, the basic cycle, exclusive windows and arbitration windows, and potential time masters.
  • CAN FD, the basic idea. CAN in Automation. The underlying frame and the arbitration limit that a timetable does not change. Accessed 2026-11-12.