ECU Basics & Internal Structure
An engine control unit (ECU) is an electronic control module that reads information from sensors and sends commands to actuators. This lesson introduces that input-and-output role and simplified calibration-map terminology. It does not describe a procedure for changing or validating a real vehicle’s calibration.
What is an ECU?
An ECU is an embedded computer: hardware and software designed to carry out control tasks within a larger system. An engine ECU may receive measurements such as engine speed or air pressure and control outputs such as fuel injection. The exact sensors, software and division of tasks vary between vehicles; “the ECU” may also refer loosely to one of several related modules.
Inputs, processing and outputs
A simplified ECU input and output model
A generic sequence from sensor or module signals, through software control logic, to commands or communication.
A high-level control sequence
- Receive inputsSensors or other modules provide information.
- Apply control logicSoftware evaluates inputs and state against programmed rules.
- Send outputsA module commands actuators or communicates with another module.
Text equivalent
Inputs such as sensor measurements are received by one or more modules. Software evaluates those inputs and its state against programmed rules. A module may then command actuators or communicate with another module. Actual systems may include multiple modules, diagnostics, feedback loops and safety strategies.
Tables and calibration data
Some control software uses lookup tables to choose a value from inputs such as speed or load. A table is a useful mental model, but a byte sequence in a file does not label itself as a table. Identifying a table requires format knowledge and context such as dimensions, data type, byte order, scale and surrounding structure.
The small table below is invented solely to show a rectangular lookup-table shape. Its values are not vehicle data or a recommended calibration.
| Illustrative input A / input B | 1 | 2 | 3 |
|---|---|---|---|
| A | 12 | 14 | 16 |
| B | 13 | 15 | 17 |
Key ideas
- An ECU is an embedded control module; its exact responsibilities vary.
- Inputs, software logic and outputs are a simplified way to describe control.
- Tables are one possible data structure. A pattern in bytes alone does not establish that a map has been found.
- Hex Labs’ educational examples explain representations; they do not establish a real vehicle’s calibration, compatibility or safety.
For an optional example of a program applying simplified calculations to synthetic tables, see the ECU Remap Simulator guide and simulator. It is an illustrative model, not a prediction of a real vehicle.
What does a byte pattern by itself tell you about an ECU table?
Related Tools
Progress is self-reported and stored in this browser.