Scope
The NefMoto 5120 discussion describes software-specific approaches for representing higher absolute pressure in ME7. The name is community shorthand for a scaling approach, not proof that every pressure channel, limiter or vehicle reaches 5.12 bar. Identify the ECU software, patch, calibration, pressure sensor, sensor transfer function and logger definition before comparing values.
A physical pressure sensor's measuring range and the ECU's internal numerical representation are separate constraints. A higher-range sensor alone does not establish that every model, diagnostic and protection function can represent or correctly use the intended range. Conversely, a rescaled internal representation does not extend the range of a sensor that has reached its limit.
Implementations in the long forum thread include changed conversions and calibration data as well as software code changes. They are file- and application-specific. Establish which functions, axes, limits, diagnostics and logger factors the actual implementation changes; do not assume a map-only edit or that settings for an M-box or another engine transfer unchanged.
Illustration: absolute, scaled and gauge pressure
Suppose a particular implementation stores a pressure channel at half physical scale, and its uncorrected logger shows 1000 mbar. For that channel, physical absolute pressure would be 2000 mbar if the logger has not already applied the corresponding factor. With independently measured local ambient pressure of 1000 mbar absolute, the illustrative gauge pressure is 2000 − 1000 = 1000 mbar. These are arithmetic examples, not pressure targets.
First determine whether each displayed channel is raw, converted to physical absolute pressure or already expressed as gauge pressure. Do not double an already corrected value, and do not subtract an uncorrected or differently scaled ambient channel. The thread includes examples of altered ME7Logger pressure definitions, but the correct conversion is specific to the exact signal and implementation.
Reported adaptation near a range limit. In a NefMoto discussion, an owner reported overboost emerging after boost-control adaptation and disappearing after a reset. They suspected that a pressure channel reaching its limit hid part of the actual error and encouraged one-sided adaptation; participants advised checking sensor range and ECU scaling. This was a hypothesis in a modified setup, not a verified universal mechanism. The author also experimented with limiting adaptation, which is not evidence that the underlying measurement or control issue was fixed. Record the learned state before resetting it, and compare the correctly scaled channel with independent pressure evidence.
The separate pressure-sensor scaling and validation guide works through a hypothetical voltage-to-pressure transfer and a reported sensor-replacement case. Sensor output, ECU representation and logger conversion each need checking.
Check before interpreting a pull
- Keep the ECU software and image identity, sensor part and calibration, patch description and logger definition together. Establish the units, source and conversion of requested pressure, measured pressure and ambient pressure separately.
- With the engine stopped, ignition on and pressures equalised, compare appropriate absolute-pressure sensor readings against a reliable local barometer. Values near half the barometer can point to a missing logger conversion, but also check the sensor, its transfer and the implementation. Not every modelled or commanded channel is expected to equal ambient.
- Compare corrected pressure against an independently checked sensor or gauge at appropriate operating points. A gauge normally reads relative pressure; add local ambient before comparing it with an absolute channel. Examine clipping and disagreement rather than extrapolating beyond either sensor's valid range.
- Review request, actual pressure, throttle, load, wastegate command, relevant limit or fault status and enrichment together. Trace all affected functions for the specific file; a sensible-looking boost plot alone cannot validate the whole calibration.
Related pages: ME7 boost and load log review, map axes and torque-model consistency and torque, load and boost control. The linked forum contains community experiments and file-specific reports, not a universal implementation.