White smoke and misfire on 2.0 TDI engine

Hello,
I'm having a problem with my 2.0 TDI CR 140PS CBBF engine. Occasionally, it takes a bit longer to start when the engine is cold, and then there's white smoke. This also happens while driving until the engine is somewhat warm. Very rarely, there's also a slight hesitation when accelerating gently at low RPMs.
It only occurs when the car has been parked for more than about 5 hours, and also at warmer temperatures (above 5°C). The car has 58,000 km and was manufactured in 2010. It had a chip tuning modification approximately six months ago.

I'd like to read the injector values now. Can anyone explain to me how to do that exactly?

Thank you in advance!

Hello,

Can you tell what the white smoke smells like? You can usually distinguish between motor oil and diesel fuel quite well with your nose.
Is coolant consumed?

You can find the injector timing at different pressure levels in the long list of advanced measurement data.

Generally speaking, about CR injectors:
/viewtopic.php?t=26829&highlight=injectors+testing
/viewtopic.php?t=26307&highlight=injectors+testing

Best regards, Rainer.

It smells like diesel. Also, the coolant level isn't decreasing.
Thanks for the links, but do I need to do this with a warm or cold engine? Or with the engine turned off?

The calibration times for the zero-quantity calibration are "historical" values, meaning they were determined during normal operation under specific environmental conditions. They should always be readable.
Depending on the type of timing deviation, even at the current operating point, i.e., while the engine is running.

Please also check the idle speed control values using VCDS.

Best regards, Rainer.

Are these the correct readings? The engine is cold. And where can I find the values for the idle speed control?

Yes, that's correct! The "idle speed control" refers to the upper values of "fuel injection deviation."

It looks okay to me - I don't think the injectors have any issues.

"The problem with sporadic errors is that, without the actual error occurring, you wouldn't expect to see any unusual readings. You should save the measurement data (by clicking on the icon for the VCDS measurement list, located to the right of the VCDS program window) and try to re-check the values while the error is actively occurring."

Is the error memory empty?

Best regards, Rainer.

OK, thank you for the quick help!