MG1 Cylinder Fill and Torque Limitation States
Cedar reference tables for selected MG1 cylinder-fill and torque-limitation monitors.
Cylinder-fill limit reason
Use this table only when the exact controller, software, and logger channel match this cylinder-fill-reason map. Read the value as one state, then compare related log data at the same timestamp.
Swipe horizontally for all columns.
| Value | Interpretation | Check |
|---|---|---|
| 0 | No separate cylinder-fill restriction | This channel is not reporting a separate cylinder-fill restriction at this sample. Other controls can still limit output. |
| 1 | Condensation protection | Compare intake-air temperature and operating conditions. |
| 2 | Turbo pressure-ratio protection | Compare pressure ratio and the relevant turbo-ratio limits. |
| 3 | High-pressure fuel-pump control | Compare fuel pressure, pump control, load, and boost at the same timestamp. |
| 4 | In-tank fuel-pump capacity | Compare low-pressure supply and related thermal/load data. |
| 5 | Ignition-retard / temperature response | Compare ignition correction, intake temperature, and relevant torque requests. |
| 6 | Turbo EGT protection | Compare exhaust-gas temperature and EGT target. |
| 7 | Particulate-filter protection | The particulate-filter strategy is active where fitted. |
| 8 | Injection-window limit | Compare rpm and commanded fuel delivery. |
Torque-limitation bit-position map
Use this table only when the exact controller, software, and logger channel are documented to use this torque-limitation bit-position map. Do not apply it to similarly named RAM flags or discrete states.
Swipe horizontally for all columns.
| Bit | Decimal | Hex | Mapped state |
|---|---|---|---|
| 0 | 1 | 0x000001 | Traction-control request |
| 1 | 2 | 0x000002 | Engine-drag-control request |
| 2 | 4 | 0x000004 | Transmission torque reduction |
| 3 | 8 | 0x000008 | Transmission torque increase |
| 4 | 16 | 0x000010 | Speed-control torque reduction |
| 5 | 32 | 0x000020 | Speed-control torque increase |
| 6 | 64 | 0x000040 | Longitudinal-dynamics / cruise-control request |
| 7 | 128 | 0x000080 | Stability-system operating-loss response |
| 8 | 256 | 0x000100 | Fuel-temperature limit |
| 9 | 512 | 0x000200 | Cooling-system limit |
| 10 | 1,024 | 0x000400 | Variant-specific torque cap |
| 11 | 2,048 | 0x000800 | Engine-speed limit |
| 12 | 4,096 | 0x001000 | Vehicle-speed limit |
| 13 | 8,192 | 0x002000 | Adaptive-cruise-control request |
| 14 | 16,384 | 0x004000 | Parking-brake protection |
| 15 | 32,768 | 0x008000 | Rear-axle / differential protection |
| 16 | 65,536 | 0x010000 | Emergency-running strategy |
| 17 | 131,072 | 0x020000 | Torque-to-cylinder-fill coherency limit |
| 18 | 262,144 | 0x040000 | Motor-protection limit |
| 19 | 524,288 | 0x080000 | Second-controller limitation |
| 20 | 1,048,576 | 0x100000 | Transmission gear-protection request |
| 21 | 2,097,152 | 0x200000 | Drive-axle load protection |
| 22 | 4,194,304 | 0x400000 | Autonomous gearbox-protection request |
| 23 | 8,388,608 | 0x800000 | Clutch-protection request |
| 24 | 16,777,216 | 0x1000000 | Controlled differential-lock limit |
Questions
What does “cylinder fill” mean in plain language, and why does the ECU track it?
In plain language, cylinder fill describes how much fresh charge the ECU calculates is entering a cylinder on a combustion event. It is a modeled operating value, not simply boost pressure. The ECU tracks it because air charge affects predicted torque, fueling, ignition, and protection strategies. Its scale and interpretation depend on the exact controller, software, and logged channel.
What is the difference between requested cylinder fill and actual cylinder fill?
Requested cylinder fill is the air charge the ECU is asking for to support the current torque target. Actual cylinder fill is the result reported by the applicable channel after the air path and active control strategies respond. A difference can occur during normal operation. Interpret both values together, at the same timestamp, using the matching controller, software, and channel definitions.
What is the difference between a torque request and a torque limitation?
A torque request is the amount of engine output the driver or another vehicle system is asking for. A torque limitation is a separate control condition that can reduce or reshape the output the ECU allows. The engine can therefore receive a high request while delivering less torque. Confirm the definitions on the exact controller, software, and logger channels.
What is the difference between a cylinder-fill reason and a torque-limitation state?
A cylinder-fill reason reports the category associated with the cylinder-fill control path on a specific monitored channel. A torque-limitation state reports a torque-side status on a separate channel. They may be related during the same event, but they do not describe the same thing. Use the controller, software, and logger definitions for both before comparing them.
Can a torque-limitation value be normal during a pull, or does it always mean there is a problem?
Yes. A torque-limitation value can be normal during a pull, depending on the exact controller, software, and logger channel. It may reflect ordinary torque management, thermal protection, traction or transmission coordination, or another active strategy. Check the channel definition, duration, repeatability, requested versus delivered values, and related log data before treating it as a problem.