ECU Scheduler Explained: How the ECU Prioritises Its Tasks

OSEK and AUTOSAR — The Foundation

Most modern automotive ECUs run on a real-time operating system conforming to the OSEK standard (or its successor AUTOSAR OS). These standards define how tasks are created, prioritised, and executed. Unlike a desktop OS, there is no "background process waiting for CPU time" — every task has a fixed priority and a defined execution time.

Cyclic Tasks — The Backbone of ECU Software

The majority of ECU functions run in cyclic tasks with fixed intervals:

1 ms task: High priority. Direct injector control, ignition timing calculation, pressure control loops (rail pressure, boost pressure). Everything that must respond time-critically to crankshaft signals.

10 ms task: Torque coordinator, boost actuator control, lambda regulation, fault monitors for fast-changing values. The bulk of control engineering runs here.

100 ms task: Diagnostic monitors (OBD II readiness), writing adaptation values, CAN communication with slow bus nodes (climate control, instrument cluster). Temperature monitoring, oil pressure monitor.

1000 ms task: Learned value updates, non-volatile memory writes (EEPROM/Flash), fault memory entry after confirmation delay.

Event-Driven Tasks and Interrupts

Alongside these are event-driven tasks triggered by hardware signals: the crankshaft sensor interrupt triggers injection calculation in sync with crank angle, the camshaft sensor synchronises cylinder identification, and incoming CAN messages trigger receive handlers.

Interrupts have inherently higher priority than cyclic tasks — they interrupt running calculations immediately. This is why interrupt handlers must be short ("interrupt service routine") and offload computation-intensive work to the next cyclic task.

Relevance for Remapping and Tuning

Task timing explains why some map changes take effect immediately while others take seconds: injection quantity maps in the 1 ms task respond almost instantly, adaptation values in the 1000 ms task may need several cycles to take hold. Understanding which task a function runs in explains why a remap behaves the way it does.