Vehicle diagnostics involve much more than reading fault codes. Modern engine management systems continuously monitor a wide range of operating parameters, and not every abnormal condition immediately triggers a diagnostic trouble code. A vehicle may have no warning lights on the dashboard yet still suffer from inconsistent acceleration, reduced performance or unstable turbocharger boost control.

At AUTOCHIP.LV, detailed engine diagnostics include data logging — recording live engine parameters while the vehicle operates under load. In this article, we explain how this approach works and examine real diagnostic examples involving Mercedes and Audi vehicles.

Why is reading fault codes not enough?

Conventional computer diagnostics can identify stored fault codes associated with components such as the mass airflow sensor, glow plugs, pressure sensors and other engine systems. This is an essential part of troubleshooting, but the absence of fault codes does not necessarily mean that every system is operating correctly.

Data logging provides a more detailed view of engine behaviour. Diagnostic equipment records selected operating parameters while the engine runs at different speeds and loads. These tests can be carried out on a chassis dynamometer or during controlled road testing under appropriate safety conditions.

One of the most useful aspects of data logging is comparing the values requested by the engine control unit with the values actually measured. For example, the ECU may request a certain turbocharger boost pressure while the actual pressure is either too high or too low. The recorded data shows when the deviation occurs, how long it lasts and how the control system responds.

Which engine parameters can be monitored?

The available information depends on the vehicle and its engine management system. Typical diagnostic data includes:

• Engine speed and accelerator pedal position.
• Requested and actual turbocharger boost pressure.
• Variable geometry turbocharger control parameters.
• Requested and actual fuel rail pressure in Common Rail systems.
• Engine, engine oil and intake air temperatures.
• EGR system operating parameters.
• DPF-related pressure readings, calculated soot loading and regeneration information.
• Exhaust system temperature sensor readings.

Analysing these values together helps technicians understand not only how individual components behave, but also how different engine systems interact under load.

Mercedes diagnostic example — turbocharger overboost

One of the Mercedes data logs revealed a noticeable difference between requested and actual boost pressure. During the test, the accelerator pedal was fully depressed, providing a 100% pedal input and allowing the engine to be evaluated under high load.

At approximately 2,700 rpm, the ECU was requesting around 1.5 bar of boost pressure, while the actual value approached 1.7 bar. The turbocharger was therefore producing more boost than requested in that operating range.

As engine speed increased, the requested and actual pressure readings gradually moved closer together. However, the actual pressure subsequently dropped below the target before rising again. The recorded data also showed irregular changes in the turbocharger geometry control parameters.

This behaviour may indicate sticking variable geometry vanes or a problem with the turbocharger control mechanism. However, this remains a possible explanation based on the data rather than a confirmed mechanical fault. Further inspection may be required to assess the actuator, control system, pressure sensors and intake system integrity.

It is also important to distinguish between absolute and gauge pressure. Diagnostic software may display absolute pressure in millibars, while turbocharger boost is commonly discussed as gauge pressure in bar. These values cannot be compared directly without accounting for atmospheric pressure.

Monitoring the DPF, EGR and exhaust temperatures

The same Mercedes test included an analysis of exhaust system parameters. With the accelerator fully depressed, the recorded EGR control data indicated that the valve was being closed. This provided additional information about how the exhaust gas recirculation system responded under the tested operating conditions.

The DPF-related backpressure reading reached approximately 200 mbar under high load. According to the technician's assessment, this was acceptable for the particular vehicle in those test conditions. However, a single pressure reading cannot establish the condition of every DPF. Engine speed, load and vehicle-specific characteristics must also be considered.

The ECU data indicated that approximately 248 kilometres had been driven since the previous DPF regeneration. The calculated soot mass was around 0.86 grams. These values provide useful information about filter operation, although they should be interpreted alongside other diagnostic results.

Temperature channels were also examined. The recorded values included approximately 618–619, with brief readings of 775 and 711, followed by lower values of 650 and 534. Interpreting these figures correctly requires knowledge of the individual sensor locations and engine operating conditions. Based on the technician's assessment, the tested Stage 1 configuration showed acceptable temperature behaviour during this particular run, with the exhaust aftertreatment systems still present.

Audi example — reduced performance several years after tuning

Another diagnostic case involved an Audi that had undergone an engine performance upgrade approximately three years earlier. Figures of around 300 hp and approximately 600 Nm of torque were mentioned for the previous tuning result. These were historical figures, not fresh power measurements confirmed during the diagnostic session discussed here.

The owner had recently noticed that the vehicle no longer delivered the same performance as before. The car was therefore examined on a chassis dynamometer while engine operating parameters were recorded.

The data revealed unstable turbocharger boost regulation. At approximately 2,300 rpm, actual boost pressure exceeded the requested value. Around 2,500 rpm, the readings moved closer together, but further deviations appeared as engine speed increased. Actual boost repeatedly fell below the target before rising again.

This pattern indicates inconsistent boost regulation. It does not, however, automatically establish an ECU software problem. Similar symptoms may result from mechanical issues, turbocharger control faults or leaks in the intake system.

During the inspection, signs of a possible air leak were noticed near the throttle body area. The technicians could hear a characteristic airflow noise, and the owner had also noticed changes in the vehicle's behaviour. Oil traces were visible around the connections. These observations justify further intake system leak testing, but they do not confirm the exact location of a leak without additional checks.

An existing thick-metal gasket from the EGR assembly was also removed and inspected. No visible signs of burning through were found. This observation describes the condition of that particular gasket and does not establish the condition of the entire EGR or intake system.

Why are data logs important before and after ECU tuning?

Professional ECU tuning should begin with an assessment of the vehicle's mechanical condition. Before increasing engine output, it is important to establish whether the turbocharger, fuel system and other critical components are operating reliably under load.

If boost regulation is already unstable or the fuel system cannot maintain the required pressure, increasing engine demands may make an existing problem worse. Identifying such issues before modifying the ECU calibration is therefore an important part of the tuning process.

After a Stage 1 remap or another calibration change, data logging allows technicians to recheck requested and actual boost pressure, fuel rail pressure, temperatures and other key operating parameters. This provides a broader assessment of engine behaviour than a peak horsepower figure alone.

At AUTOCHIP.LV, these diagnostic recordings are saved and can be shared with customers when required, including through WhatsApp. Vehicle owners can review the recorded graphs and gain a clearer understanding of how their engines behave under different operating conditions.

Conclusion

Engine data logging is a valuable part of advanced vehicle diagnostics. It can reveal operating problems that may not trigger conventional fault codes. In the Mercedes example, the data showed boost control deviations and signs of a possible variable geometry turbocharger issue. In the Audi case, unstable boost pressure and observations around the intake system indicated areas requiring further inspection.

Data logs do not always provide an immediate final diagnosis, but they help technicians identify the next diagnostic steps, assess vehicle condition and verify engine behaviour after ECU tuning. The accompanying video provides a closer look at the diagnostic process and the recorded graphs.