Connecting a diagnostic scanner, reading fault codes and clearing them is not the same as performing a complete engine diagnosis. A vehicle can have significant performance problems without displaying an obvious warning on the dashboard. It may still drive normally in everyday conditions while failing to develop the power it was designed to produce.

At AUTOCHIP.LV, we investigated a BMW equipped with two turbochargers that was producing considerably less power than expected. By recording and analysing detailed engine data logs, the technician identified irregularities in both the fuel system and turbocharger boost control.

BMW power loss — comparing expected and measured performance

According to the manufacturer's specifications quoted in the demonstration, this BMW engine should produce approximately 313–316 hp and 630 Nm of torque.

However, the initial measurements showed only 277 hp and approximately 552 Nm.

Compared with the expected figures, that represents a shortfall of around 36–39 hp and 78 Nm. This is a substantial difference and a good reason to investigate the engine's operating conditions before considering further performance modifications.

Several systems can contribute to reduced engine output. Insufficient boost pressure, fuel delivery limitations, incorrect actuator operation and ECU protection strategies can all affect performance. Identifying the actual issue requires more than simply checking whether diagnostic trouble codes are stored.

What makes data logging different from a basic fault-code scan?

A conventional diagnostic scan provides fault codes, sensor readings and information stored by the engine control unit. This is useful, but it does not always reveal how the engine behaves under real operating loads.

Advanced diagnostics with data logging involve recording multiple engine parameters simultaneously while the vehicle is driven or tested under controlled load conditions. The resulting data can then be reviewed as graphs, allowing the technician to compare requested and actual operating values.

For example, the ECU may request a particular fuel pressure or turbocharger boost level. If the actual value consistently falls short, responds too slowly or exceeds the target, this difference becomes valuable diagnostic evidence.

However, a data log does not necessarily identify a failed component by itself. It reveals the behaviour of the system and helps determine which mechanical or electronic checks should follow.

Fuel system analysis — actual pressure becomes unstable under load

The first part of the investigation focused on the fuel system while the engine was operating with its original ECU software.

The technician compared the requested and actual fuel pressure readings. On the graph, the blue line represented the ECU's target, while the red line showed the measured response.

As engine load increased, the requested value remained high, but the actual reading began to fluctuate. Rather than following the target consistently, the fuel system repeatedly approached the requested level and then dropped away from it.

This behaviour suggests a possible fuel supply or pressure regulation limitation. However, it does not prove that a particular fuel pump, regulator or other component is defective. Additional tests would be required to isolate the cause.

The same fuel system parameters were then reviewed using data recorded with a modified ECU calibration.

Under the higher load conditions, the fluctuations became more pronounced. The actual pressure response moved further away from the requested value, particularly towards the upper end of the tested operating range.

This illustrates an important consideration for performance tuning: if a fuel system is already struggling to meet the engine's demands in its original configuration, increasing engine load may make the existing limitation more apparent.

No specific fuel system component replacement or completed repair is confirmed in the demonstration. The established finding is the discrepancy visible in the recorded data.

The main problem — incorrect boost control on a twin-turbo BMW

Although the fuel system showed irregular behaviour, the AUTOCHIP.LV technician identified the air supply and turbocharger boost control system as the main reason for the engine's reduced initial power output.

This BMW uses two turbochargers. Depending on the configuration of the charging system, the turbochargers work together across different engine speeds and load conditions to provide the required intake air pressure.

The diagnostic data recorded with the original ECU calibration showed a clear mismatch between requested and actual boost pressure.

Several issues were visible:

• Low engine speeds: actual boost pressure developed with a considerable delay. The technician associated this with a slow response from the first turbocharger.
• Mid-range operation: around 3,000 rpm, the graph showed a significant drop in actual boost relative to the requested value.
• Higher engine speeds: at approximately 3,600 rpm, actual boost exceeded the ECU target. The vehicle was travelling at around 134 km/h during the demonstrated measurement.
• Further into the tested range: the tendency towards excessive boost remained visible.

In other words, the boost control system was initially failing to achieve the requested pressure and then overshooting the target under different operating conditions.

The technician interpreted this behaviour as delayed boost development from the first turbocharger and excessive pressure in the operating range of the second turbocharger.

Possible explanations for this pattern can include actuator problems, turbocharger control mechanisms, vacuum or pressure line faults, sensor issues or other control system defects. However, the data shown does not establish that either turbocharger has a specific mechanical failure.

What happened with the modified ECU calibration?

The next comparison involved the same engine running with modified ECU software.

Although the calibration produced more power, the boost control irregularities remained visible in the data logs. Boost was still insufficient at lower engine speeds, while the transition between turbocharger operating ranges showed pressure overshoot followed by a drop. Excessive boost also appeared in another part of the tested range.

This is a particularly important finding: an ECU remap can increase measured engine output without resolving an underlying boost control problem.

Software calibration and mechanical system condition are related, but they are not interchangeable. Increasing a torque request or adjusting engine control parameters does not automatically repair a faulty actuator or restore a restricted fuel supply.

That is why a successful increase in peak power should never be the only criterion used to evaluate an engine's condition after tuning.

BMW performance results with the modified software

With the modified ECU calibration, the engine produced 317 hp and 666 Nm.

The gain is significant, particularly in terms of torque. However, the result needs to be considered in the context of the engine's original underperformance.

The manufacturer's expected power output was approximately 313–316 hp, but the vehicle initially produced only 277 hp. After the software modification, the measured output reached 317 hp — only slightly above the quoted standard power range.

The technician suggested that if the engine had been producing its full expected factory power before tuning, a similar additional power gain could potentially have resulted in a considerably higher final figure.

That remains a hypothetical comparison. No such higher output was measured on this vehicle, and correcting the underlying mechanical or control issues would require further assessment before any future tuning result could be established.

The technician also confirmed that the vehicle's emissions control equipment was retained. Separate emissions measurements were not presented.

Why proper diagnostics should come before performance tuning

This BMW demonstrates why a lack of fault codes does not necessarily mean that an engine is performing correctly.

A vehicle can still accelerate and respond to a modified ECU calibration while having significant discrepancies in turbocharger boost control or fuel system operation.

Detailed data logging helps answer three essential questions: what the ECU is requesting, what the engine is actually delivering and under which operating conditions the two begin to differ.

These findings make it possible to direct further diagnostic work towards the relevant systems rather than replacing parts based on guesswork.

For a vehicle that is already producing less than its expected factory output, investigating the reasons for that shortfall is particularly important before considering additional engine load.

Advanced BMW diagnostics at AUTOCHIP.LV

In this case, advanced diagnostics revealed substantial boost control irregularities and unstable fuel system pressure response under load. The technician considered the boost control behaviour the main contributor to the BMW's initial power deficit.

The modified software increased measured power from 277 to 317 hp and torque from 552 to 666 Nm. However, the demonstration does not confirm that the underlying mechanical or control system issues were fully repaired.

The vehicle's owner travelled from Liepāja and reported being pleased with how the BMW drove after the software modification. Nevertheless, improved driving impressions are not a substitute for assessing the diagnostic irregularities found during testing.

AUTOCHIP.LV in Riga provides advanced engine diagnostics, ECU data log analysis, turbocharger system assessment, chip tuning and ECU programming.

The accompanying video shows the actual diagnostic graphs, comparisons between the original and modified ECU software, and the detailed reasoning behind the technician's findings. It demonstrates why professional engine diagnostics involve much more than reading and clearing fault codes.