Applicability and evidence
This guide concerns BMW B58 petrol engines discussed as MG1 applications. Hardware evidence comes from BMW's B58TU training; calibration evidence comes from bootmod3 and EcuTek documentation and public tuning discussions. These sources answer different questions. No binary, definition or vehicle has been validated by this wiki for this article.
| Source/application | What it establishes | Boundary |
|---|---|---|
| BMW B58TU training, July 2018 | B58B30M1 and B58B30O1 hardware context, revised direct injection and DME 8.6T0 designation. | Factory training, not a software-specific map definition or current repair instruction. BMW source. |
| bootmod3 BMW MG1 guide | The vendor groups B58 Gen 1 under PPC and Gen 2 under Aurix; its worked example is a Z4 M40i B58D. | Check the actual ECU, ROM and tool version; those group names do not identify every vehicle. Vendor source. |
| NefMoto B58 resource discussion, September 2023 | Discussion of definitions, strategy knowledge and logging. | Contributor observations, not a verified Bosch function description. Discussion. |
The fuel-system generation matters
BMW describes a revision from 200 to 350 bar, with a revised high-pressure pump and injectors. Its comparison distinguishes HDEV5, HDEV5 EVO and the Bosch HDEV6 used on Bx8TU. The DME generation has a common external appearance while internal hardware varies. See printed pages 28 and 31–33 of the training document.
The 350 bar figure describes that factory system's design. It is not a request to enter into every B58 calibration. Identify the fitted pump, injectors, pressure sensor and matching calibration before considering pressure changes. An upgraded pump alone does not establish compatibility of the complete earlier system with a later pressure specification. This is the practical inference from BMW's documented hardware changes.
Read the BMW strategy before following another MG1 platform
In the bootmod3 example, requested torque is related to load through reference-torque calibration. The guide documents separate filling constraints associated with operating conditions, plus Aurix logging of filling-limit reasons and a torque-limit status channel. ROM-dependent differences matter. This supports diagnosing the active path before increasing more limits; it does not establish common addresses or status-bit meanings across BMW software.
Some vendor example settings involve very high limits or monitor changes. They are not verified component ratings or a general prescription for this wiki. Retain a documented reason for each change and investigate an intervention before deciding whether its calibration is wrong.
What the discussions add
The 2023 NefMoto thread contains disagreement about learning from other platforms. One contributor specifically argues that BMW petrol application software differs from other manufacturers' MG1 implementations and has continuity with earlier BMW petrol software. Treat that as a contributor's architectural claim, not proof that any two binaries match. The useful research rule is to establish the function in the BMW file rather than transfer a Porsche or Audi map name.
The public BMW-XDFs repository separates B58gen1 and B58gen2 directories. That organisation illustrates the need for matching definitions. Only the repository overview was reviewed here; individual definitions were not audited for addresses, completeness or suitability.
A separate 2025 torque/boost-limiter question reports a plateau and receives a request for better logging and examination of torque demand. The reviewed indexed discussion establishes no verified remedy. Its reported numbers should not become B58-wide torque or boost ceilings. A complete software identity was not established from the reviewed posts.
A useful investigation record
The following is a proposed evidence workflow, not a tested calibration sequence:
- Identify the combination. Record engine variant, ECU hardware and software/calibration identifiers, transmission software, installed fuel and turbo hardware, fuel composition and any custom code. Keep the original file identifiable.
- Match the definitions. Document each signal's units, reference and update rate. Decode active-limit flags using documentation for that ROM and logger; a familiar numeric flag is insufficient.
- Separate demand from delivery. Where exposed, compare pedal/torque demand, permitted torque, filling request and actual filling, throttle, pressure request/actual, wastegate control and active-limit status on a common time base.
- Check combustion and fuel delivery. Compare lambda request/measurement, fuel trims, requested/actual rail pressure, injection timing or duration where available, ignition corrections and temperatures. A falling pressure trace needs diagnosis before further demand.
- Retest the explanation. Change one justified calibration relationship, document the expected trace change, and compare repeatable conditions. Include part-load response and shifts alongside full-load output.
For the general concepts see MG1 torque, air and fuel basics. This page supplies no universal pressure, lambda, ignition, torque or protection settings.
Injection monitoring can become the active load limit
EcuTek's B58g1-onwards injection-monitoring note describes protection of both pump delivery and the available injection window. A pump-control angle reaching its limit, an excessive rail-pressure shortfall, or the calculated pump-flow ceiling can each trigger intervention. The flow calculation includes pump capacity, efficiency and fuel-temperature correction. Consequently, an angle below its maximum does not rule out this path.
The source describes a fast reduction and slower restoration of permitted filling. It also warns that raising the minimum filling permitted by this monitor can conceal the restriction while allowing substantial pressure loss. For a changed pump, establish the correct capacity model for that hardware rather than treating the minimum-load setting as pump calibration.
Diagnostic inference: Capture the first pressure/flow or window restriction and the subsequent filling-limit change. A later log may show pressure recovered because demand has already been reduced. Recovered pressure alone does not establish that the pump was never restrictive. Check low-pressure supply, fuel and operating conditions alongside the high-pressure system.
Use a limit-reason channel only where it is defined
EcuTek's limit-state reference defines the cylinder-filling reason monitor for B58g2/Supra and S58, and explicitly excludes B58g1, N55 and S55 from that monitor's availability. The following is a selection from that reference, not a Bosch-wide enumeration:
| Value | Meaning in this EcuTek reference |
|---|---|
| 0 | Normal torque-demand-derived filling without another restriction. |
| 2 | Turbocharger component protection involving pressure ratio. |
| 3 | High-pressure fuel-system control limit. |
| 4 | Electric lift-pump capacity. |
| 5 | Intake-temperature, knock or driving-behaviour retard contribution. |
| 6 | Turbocharger exhaust-temperature protection. |
| 8 | Available injection window cannot accommodate the requested fuel. |
Confirm the ROM and logger definition before decoding a value. An unavailable monitor does not establish that its underlying function is absent. The reason code is a starting point for investigating a restriction, not a reason to disable that restriction.
Separate the boost model from the final actuator command
EcuTek's B58 guide describes a path from required airflow and compressor pressure ratio to shaft-power demand, then turbine/exhaust relationships and wastegate position. Its logging definitions distinguish base, corrective and final turbo-power quantities from the wastegate command. It also separates pre-throttle pressure from manifold pressure and identifies positive boost error as being below target in that tool.
The practical interpretation is to locate the discrepancy. If the filling request has already fallen, more wastegate command does not restore the missing request. If the pressure request remains high while measured pressure falls short, examine delivery, actuator behaviour and model accuracy. If the base estimate is wrong and feedback is compensating heavily, changing feedback gains alone can leave the underlying mismatch. These are diagnostic hypotheses to test with the matched signals.
Put injection duration and angle on the same basis
For an arithmetic check, crank-angle travel is duration in milliseconds × rpm × 0.006. At 6,000 rpm, one millisecond spans 36 crank degrees. This does not define the usable injection window: the software's start/end references, pulse splitting and relevant limits still determine which part of the cycle is available. A displayed duration, an end angle and a pump-control angle are different quantities.
For example, if a log indicates a window restriction, compare all relevant pulses and the applicable angle limits before concluding that rail pressure alone is the problem. Avoid transferring start/end-angle sign conventions from another engine or logger.
Sources and review limits
- BMW Service Training: B58TU Engine, information status July 2018; printed pages 27–33. Manufacturer-authored document on an independent mirror.
- bootmod3: Tuning Guide — MG1 PPC / Aurix, introduction and Load and Torque sections. First-party tuning-tool documentation; its worked example and recommendations are application dependent.
- NefMoto: B58 engine on MG1, tuning resources, September 2023.
- NefMoto: B58 MG1 torque/boost limiters?, February–March 2025. Unresolved discussion in the reviewed material.
- dmacpro91: BMW-XDFs, public repository overview.
- EcuTek: Injection Monitoring (B58g1 onwards), updated 17 June 2022. Pump/window monitoring and filling-limit behaviour.
- EcuTek: BMW Limit Flags & States. Tool-specific reason values and monitor availability.
- EcuTek: B58 Tuning Guide, updated 13 September 2023. Model-based boost control and logging definitions. EcuTek sources reviewed 17 November 2026.
Sources reviewed 17 November 2026. NefMoto material was available through public search indexing; direct forum access was blocked. No forum attachments or confidential function documents were retrieved.