Hi,
The log for "Meine" is messed up. Please don't use the CSVConv for this, as it produces garbage in some cases and is, frankly, pointless. Does the original log also indicate a jump from 44 seconds to 78 seconds?
Open the original log file with KDataScope - as a customer, you have access to that - and then you won't need to "convert" anything or similar.
If you only look at the last part of "Meiner," you'll notice that the target pressure reading is stuck at 2601 mbar. It's possible that this is how it's programmed, or it's possible that something else is programmed and that the conversion factors for the diagnostic values in the engine control unit were missed: In that case, you would only see the maximum value that can be displayed with the corresponding factor.
-> Check which boost pressure curve is desired here (values).
Assuming the target value for the boost pressure is indeed 2601 mbar, the overshoots could be caused by the following:
- Incorrect programming of the smoke limitation (other characteristic curves are used because the torque limitation is implemented differently).
- Incorrect VTG (Variable Turbine Geometry) pre-tax characteristic curve (other characteristic areas are used because the torque limitation is different).
- electrical problems with the turbocharger pressure sensor and its wiring.
- Is there a jump in the log, is the diagnostic connection stable, and is the engine control unit not rebooting occasionally?
- The usual suspects when it comes to boost pressure regulator differences: sticking variable turbine geometry (VTG) (turbocharger overheated or carbonized due to improper tuning), stuck magnetic valve for boost pressure regulation, faulty vacuum system venting...
Overall, I believe it's best to have the tuning file with the respective tuner, because only they can see what has been programmed, as the diagnostic values in the file may not be informative, and only they can know whether the displayed values are actually programmed that way or not.
Best regards, Rainer.