> […] and trigger a hardware interrupt when the signal is received. That is the definition of event driven. The same is not only true for the CAN-based, and C

> […] and trigger a hardware interrupt when the signal is received. That is the definition of event driven. The same is not only true for the CAN-based, and CAN FD-based communication, but also for the Automotive Ethernet-based communication. There were tries with Time-triggered protocols like TTP/C (used by Daimler for exactly one model) and FlexRay which had cyclic communication. The communication cycle required that the ECUs are synced to the communication cycle because they needed to have to correct data available at exactly their time slot. If they missed the time slot, the data got marked as stale. The same problem on the receiving side.