V6 TDI: Adjust Injection Timing with VAG-COM

Hello everyone,

I'm new here and I've already thoroughly searched the site, but unfortunately, I haven't found what I'm looking for.

I replaced the belts and camshaft on my Audi (AKE, 132 kW), and afterwards, I initially positioned the timing belt pulley for the VE in the middle position on the camshaft pulley (as determined by the alignment marks).

The engine is running perfectly, it uses less diesel, so it's a complete success so far.

Now, as a conscientious hobby mechanic, I also want to correctly adjust the fuel injection timing, and for that, I have a VAG-COM version 409-1 available.

1. Problem: This version only works with TDI Graph 1.3, and it doesn't offer my specific vehicle identification number (VIN) as an option.

2. In the table "Troubleshooting with VAG-COM" that I downloaded here, the expected values in measurement block 4 for the AKE engine are all empty fields.

Can one of the professionals briefly and clearly explain how to adjust the injection timing using this block? (My engine isn't listed in the TDI-Graph.)

The following functionality works: After switching to the base state in the MWBl. 4, the switch between "late" and "early" occurs, displaying "late" as 0.5 degrees and "early" as 12 degrees.

In normal mode, the target timing shifts from early to late as the engine speed increases (shouldn't it be the other way around?), and the actual timing remains fixed at 12 degrees before top dead center (TDC) and doesn't change at all.
If the vehicle isn't running properly, one should suspect a complete misconfiguration in this case.

Who can help?


Regards,

The adjustment of the dynamic injection timing on the V6 TDI engine has only been supported since VAG-COM 607 or TDI-Graph 1.4. However, the adjustment on the V6 TDI is generally so straightforward that a TDI-Graph is actually not necessary.

Current versions of VAG-COM state the following regarding this issue...

Setpoint (late): 0.0...4.0 °n.OT.
Set point (early): minimum 12.0 °V.OT.

What does it mean that he is still very close to being within the target values ?

Thank you very much.

"Today, I managed to adjust the overtravel to 1.8...2 (it's a bit fiddly to do on the assembled car), but I haven't noticed any change in the driving behavior yet."
After that, a test drive was conducted, and the mileage (MWBl. 4) was recorded, and everything was fine.

The VAG COM 4.9-1 likely doesn't recognize the correct temperature reading for the AKE (Acoustic Kick-off), which is why the TDI graph doesn't start, even when set to "80 degrees."

If I ever feel inspired, I'll post a guide here on how to replace the camshaft; it's not really a big deal.

Regards,

Jinro Soju wrote:

The VAG COM 4.9-1 probably doesn't recognize the correct temperature at the AKE, which is why the TDI graph doesn't start, even when set to "80 grd".

"No, as you may have noticed, the basic settings for the V6 TDI are not found in control module 000, but rather in control module 004. Furthermore, the system doesn't evaluate pure decimal values, but rather values with units directly. In other words, neither VAG-COM nor TDI-Graph were designed to handle this, VAG-COM because it doesn't pass the data on, and TDI-Graph because it couldn't make sense of the data."

Sometimes, software updates are actually a great thing.

Hmm,

I performed the basic configuration on the MWB 004, and it worked.

The graph could be accessed in the MWB000 (as described in the VAG COM manual) and also displayed the yellow lines. This indicates that data transfer must have taken place.

However, I consistently received the message "engine not warm enough" while the water temperature displayed a seemingly unchanged 73.6 degrees Celsius, even though I had set it to 80 degrees (hot) and the engine was definitely around 90 degrees.
The only message I received was that I should keep my foot off the accelerator, even though I was using it.

Anyway, I just drove about 600 km today, and the vehicle is running perfectly. I'm happy with it.

I have already returned the software and the laptop, so I can no longer test the MWB 005.

Thank you again for the information.