Can anyone help with an explanation of what is DFC 19667 - P3211.

It comes up as a second code to 16825 - P0441 and has occurred 3 or 4 times at reducing intervals - 2 months - 3weeks - 9 days - 25 miles ?

TIA

emjay13 :confused:

The search facility gives -

16825 P0441 EVAP Emission Contr.Sys.Incorrect Purge Flow

What are you reading them with?

My mate has a Snap-On and the dealers use some ancient Skoda steam driven thing. I was able to determine the 16825 Ok, but all I can find for 19667 is

"Abgas- Bank 1, Soude 1 Heizerruckkopplung" and I cannot locate that in my Dutch dictionary.

That ancient Skoda steam driven thing may have given a more descriptive code.

P3211 is Oxygen Sensor and oxygen sensor control before Three Way Catalytic Converter.

Check the wiring of the front Lambda Sensor.

Dealers should be using VAS 5051 (or 5052) or VAS 5051B. Nothing steam powered about them.

The dealers are waiting for Skoda to tell them what 19667 means. The wait is now 10 days !!

:really:

I told you above what it relates to.

Please post a complete diagnostic print out (e.g. vag-com auto-scan), I have an idea what's up but need additional information.

Thanks Stu, for that pointer, I had been laid low with a bug for a week or so, and have not yet had a chance to investigate further.

But the whole game has altered ! 2 days ago the fault warning light went out and has stayed off for 3 trips covering about 50 miles in toto.

I am sure that the fault indication is associated with TOO MUCH GENTLE DRIVING.

The first time (August) I had driven round the M25 in a very slow but not quite stop and start mode and the light fault warning light came on on the same journey about 10 miles off the motorway. The dealers checked it out and changed the purge valve.

The second time (November) I was getting a take-away on my wife's birthday after driving her for 2 hours round beautifull countryside so slowly I was nearly nodding off. My friend reset the codes .

Third time was 1 mile after restarting after 30 miles slow processional bad weather driving in December christmas traffic coming back from the dealers who had done a full fault test that had found no fault. The light stayed on, I posted the question, and waited until ...

On Friday last I had to collect one tin of paint - a 16 mile round trip - what a waste of petrol for one item, so I concentrated on using as little fuel as possible and returned 41.5 mpg for the combined lanes/main road/town traffic. On Friday evening trip the waring light did NOT come on.

I am as baffled as before, if not more, I do not know whether there is any defect trace information stored in the car. But even so Sebastian, I would be very interested to hear of your ideas on this.

I think for Sebastian's advice he would like to see a VAG-COM printout as they generally support genuine Ross Tech tools only.

You have stated that you use a Snap On Scanner.

Doesn't matter much if it would be a VAG-COM or VAS scan - I'd just like to see some more data on the actual ECU.

However, in the meanwhile you may want to check these pages...

16825/P0441/001089 - Ross-Tech Wiki

19667/P3211/012817 - Ross-Tech Wiki

Many thanks for these last replies, I had decided, in the absence of a continuing malfunction indicator light to just run on until something happened. Since my first posting the warranty period has expired, but the dealers are being as helpful as they can withing the constraints of extended defect diagnosis.

They (dealers) have said they will look out their disgnostic printout this weekend, so I may have more information on Monday.

I had my friend try his snap-on device to check here (25 miles from dealers), he has not had it long and did not save any results. Since then the dealers have done a fairly lengthy diagnostic run.