Understanding KFMIOP and KFMIRL is one of the most important steps any serious Smart Roadster tuner can take. These two maps sit at the heart of the Bosch MEG 1.1’s torque-based control strategy, and they are inseparable: one defines what the engine should produce at its best, the other converts that torque ambition into a real load signal the ECU can act upon. Get either one wrong and you end up with flat spots, protective cut-outs, or power that simply fails to materialise. This article explains how both maps are structured, why they must be calibrated together, and what happens inside the ECU when a tuner changes only one half of the pair.
What Is Torque-Based Engine Management?
Older ECU architectures controlled engines directly through ignition timing and fuelling tables referenced against RPM and throttle position. Bosch’s torque-based strategy, introduced progressively from the late 1990s, adds a conceptual layer: the ECU thinks in torque first, then works backwards to decide how much air, fuel and spark are needed to achieve that torque. The driver’s throttle pedal is no longer a direct fuel request — it is a torque request. Every subsystem, from the gearbox controller to the traction control logic, communicates in Newton-metres.
This architecture is why the Bosch MEG 1.1 fitted to the Smart Roadster 452 behaves so differently from a carburettor-era tune. Changing boost or ignition advance without accounting for the torque model can cause the ECU to actively clamp output, because its internal calculations produce values that contradict its structural limits. The KFMIOP and KFMIRL maps are the two most critical tables within that torque model, and they must be understood as a system rather than as isolated numbers.
For context on how physical boost translates into actual torque figures within this system, the relationship is worth studying before diving into the maps themselves — understanding how boost pressure becomes usable torque on the 698cc engine gives you the physical foundation that makes the following calibration logic much clearer.
KFMIOP: The Optimal Torque Map
KFMIOP stands for Kennfeld Moment Indiziert Optimal — roughly, the indicated optimal torque map. It is a two-dimensional lookup table indexed against engine RPM on one axis and relative air charge (load) on the other. For any given operating point, KFMIOP returns the maximum torque the engine is deemed capable of producing efficiently and safely under those conditions. Think of it as the engine’s performance ceiling: a map of what is physically achievable at every RPM and load combination.
In the stock 60kW Smart Roadster calibration, KFMIOP values are conservative. They respect thermal margins, the limits of the stock clutch, and the mechanical tolerances of the 698cc block. When a tuner increases boost, the physical torque output at a given RPM and load point rises — but unless KFMIOP is updated to reflect the new ceiling, the ECU will interpret the additional torque as an anomaly and may pull timing or limit fuelling to bring the engine back within its modelled limits.
KFMIOP is therefore not a request map. It is a permission map. Raising its values tells the ECU that higher torque at a particular operating point is structurally acceptable. A detailed breakdown of how KFMIOP is structured in the MEG 1.1 covers the axis scaling, value units and the common pitfalls when editing this table in isolation.
KFMIRL: Converting Torque Into Load
KFMIRL — Kennfeld Moment Indiziert Reibung Last in its full form, though interpretations vary slightly — performs the inverse operation. Where KFMIOP defines how much torque the engine can produce, KFMIRL converts a torque request into a normalised engine load value (rl) that the fuelling, ignition and boost control loops can use as their reference input. It is the bridge between the abstract torque domain and the physical actuator domain.
In practical terms: when the ECU receives a torque demand from the driver, it consults KFMIRL to determine what relative load (typically expressed as a ratio of actual to maximum cylinder filling) corresponds to that demand at the current RPM. The resulting rl value then propagates through the injection duration maps, the ignition advance tables, and the boost target maps. Every downstream map that uses rl as an axis is ultimately governed by the conversion KFMIRL performs.
This is why a mismatched KFMIRL causes symptoms that seem unrelated to torque management: unstable idle, incorrect injection pulse widths, ignition timing that does not follow the expected advance curve. The ECU is working from a corrupted translation, and the errors cascade. How KFMIRL converts torque requests into engine load signals explores the precise mechanics of this conversion and the axis ranges used in the MEG 1.1 implementation.
Why the Two Maps Must Be Calibrated Together
The interdependence of KFMIOP and KFMIRL is the central lesson of torque-based tuning. KFMIOP defines the ceiling; KFMIRL defines the pathway. If you raise KFMIOP to allow 160 Nm at 4,000 RPM but leave KFMIRL unchanged, the ECU will calculate a load value appropriate for the stock torque level, feed that understated rl into the fuelling maps, and deliver less fuel and advance than the engine actually needs to produce 160 Nm. The physical boost may be present, but the combustion management will not support it.
Conversely, if KFMIRL is scaled upward without a corresponding increase in KFMIOP, the ECU’s torque model will see requested loads that exceed its permitted ceiling and may invoke torque reduction strategies — the engine management’s equivalent of a governor.
The Load Signal Cascade
The rl value produced by KFMIRL feeds a long chain of downstream tables. Among the most significant are the injection base map (KFKHFM), the ignition advance map (KFZW), and the boost target map (KFLDRL). Each of these uses rl as a primary axis. Changing KFMIRL therefore simultaneously shifts where every engine operating point sits within all of those tables. This is why experienced tuners scale KFMIRL carefully, in small increments, verifying the downstream map behaviour at each step rather than simply copying values from another platform.
Matching the Maps to Physical Hardware
When hardware changes are made — a larger intercooler, a ported head, a higher-flow injector — the physical relationship between load and torque changes. KFMIOP must reflect the new torque capability, and KFMIRL must reflect the new load-to-torque conversion. Tuners who perform cylinder head flow work and then wonder why the ECU does not deliver proportional gains frequently have mismatched torque maps as the root cause.
Practical Tuning Workflow for the MEG 1.1
A coherent approach to editing KFMIOP and KFMIRL in the Smart Roadster’s MEG 1.1 follows a logical sequence. First, establish your target torque curve across the RPM range, informed by your hardware and safety margins. Second, update KFMIOP to match those targets, ensuring no cell exceeds the structural capability of your engine and drivetrain. Third, rescale KFMIRL so that the load values produced correspond accurately to the new torque points. Fourth, verify that every downstream map (ignition, fuelling, boost) remains coherent at the new operating points.
Choosing the right software environment matters too. Some platforms expose KFMIOP and KFMIRL with their correct axis labels and unit scales; others present them as anonymous 8×8 arrays requiring manual identification against a DAMOS definition file. Comparing TunerPro and WinOLS for MEG 1.1 work covers which environment gives you the clearest visibility of these maps and the best tools for verifying axis consistency.
It is also worth considering the mechanical limits that torque increases impose on the drivetrain. The Softouch gearbox is not a passive recipient of whatever torque the engine produces — its actuator logic responds to torque signals from the ECU, and abrupt changes in the torque model can produce unexpected clutch behaviour. How the Softouch actuator responds when engine torque is increased through remapping is essential reading before finalising any calibration that pushes significantly beyond stock torque levels.
Common Mistakes and How to Avoid Them
The most frequent error is editing KFMIOP alone, assuming that raising the ceiling automatically raises output. It does not. Without a corresponding KFMIRL update, the load signal pathway remains calibrated for the old torque level, and the engine effectively underperforms relative to its boost setting. The boost is doing physical work; the ECU is just not translating it correctly.
A second common mistake is copying KFMIRL values wholesale from a higher-power variant — say, the Brabus calibration — without understanding that the Brabus map was calibrated against a different injector flow rate, a different wastegate spring, and different ignition timing. The rl values in that KFMIRL are correct for the Brabus system as a whole. Inserted into a partially modified 60kW calibration, they produce a mismatched translation that affects fuelling and timing accuracy across the entire operating range.
Finally, some tuners overlook the importance of the DAMOS reference when working with MEG 1.1 files. Without a reliable map definition, it is easy to mistake KFMIRL for a related but distinct friction torque map, leading to edits in entirely the wrong table. Understanding what a DAMOS file contains and why it is indispensable for accurate map identification can prevent hours of diagnostic frustration.
What Good Calibration Looks Like on the Road
When KFMIOP and KFMIRL are correctly matched to each other and to the supporting maps, the result is a torque curve that builds smoothly from low RPM, reaches its peak without any plateau or step caused by torque clamping, and tapers gracefully toward the rev limit. In a well-tuned Smart Roadster 452, the 698cc engine should feel linear and progressive rather than peaky. There should be no hesitation at the point where stock KFMIOP values previously imposed a ceiling, and no rich or lean excursion caused by a miscalibrated load signal.
Logging is essential for verification. A wideband lambda sensor referenced against the load value the ECU is actually reporting — not just manifold pressure — will immediately reveal whether KFMIRL is producing accurate translations across the operating range. Any zone where the reported load diverges from what the physical conditions should produce points to a cell that needs correction.
The KFMIOP and KFMIRL torque structure is not optional knowledge for anyone tuning the Smart Roadster’s MEG 1.1 seriously. These two maps define the language the ECU uses to understand and control the engine, and calibrating them in isolation produces results that range from mediocre to actively harmful. Treat them as a matched pair, update them in sequence, verify downstream coherence, and respect the mechanical limits of the drivetrain — and the 698cc engine will reward you with a torque curve that is both broader and more usable than anything the factory ever delivered.
