No, Media screenshots .lbl. - AndyI think it's one of yours, from the Media tab.
Mac.
Thank you for trying the download, not working is unexpected and something that needs sorting out. I have full VCDS which leaves me ignorant of the VCDS Lite file structure and somewhat unable to assist. Mac has registered Lite, best if I leave it to Mac to sort out.I did try using the FSI lbl file as it would make reading the outputs a lot easier. Unfortunately, each time I put that in the lbl directory VCDS crashed when accessing the engine module. Using licensed VCDS lite on a Windows XP machine.
Yes I did both of those things. But will double checkAre you quite certain that you changed the file type? (If any help I find it easier to to do this with right click and change using Properties).
Are you certain you placed the lbl file in the VCDS Labels subfolder?
I'll copy the lbl from my working Lite, change the suffix, and PM it to you in a while.Yes I did both of those things. But will double check
DoneI'll copy the lbl from my working Lite, change the suffix, and PM it to you in a while.
Mac.
Trying to be logical, but coming from a position of ignorance, I would say the misfires might be attributable to the fact that the fuel pressure is low which would suggest the mixture will be off. To my eyes this is fuel pressure related, the ecu is asking for a certain pressure which is often never achieved, hence the 17428, but may well cause the misfires. So logically it points to the pump, or I suppose a leak but I’m sure that would be very obvious.We took Jeremy's FSI for a drive along some twisty and undulating Cotswold lanes last night, logging measuring blocks 000 and 140 (using the .lbl file kindly supplied by Mac - no VCDS crashes with this version).
Initially the target and actual fuel pressures tracked quite well, but after a few minutes it was clear that the actual fuel pressure reading diverged downwards when we encountered a hill or anything that put load on the engine.
You can see this in the graph here:
View attachment 115135
The grey line is the target pressure, the yellow the actual reported fuel pressure.
I then took the wheel. During the initial period, there were glimpses of the sweetness and punchiness of the FSI engine briefly on acceleration before the reported actual fuel pressure fell away and the the engine bogged down. Then the car became very difficult to drive; you can see that the reported fuel pressure dropped and stayed low (3.8 bar) for the last two thirds of the circuit. In fact, 20m from the end, we came to a halt, the engine struggled to idle and any attempt to set off resulted in a stall. After 10 minutes sat in the middle of the road, we resorted to pushing it to a safe place. Here is a log of the second circuit with target pressure in blue, and reported actual fuel pressure in orange.
View attachment 115136
After 30 minutes switched off, the vehicle was able to be re-started and driven back up the hill.
The reported constant fault is 17428 Fuel Pressure Regulation Control Range Exceeded P1020, but the test drive also threw up intermittent faults (16684 Random/Multiple Cylinder Misfire Detected P0300 and 16686 Cylinder 2 Misfire Detected P0302.
I'm attached the 2 .CSV files that are the basis for the above graphs (I've changed the file type to .txt to comply with the forum upload rules)
As always, any insights or observations welcome!
Stephen
After more thought about this, I don’t think the HPFP is the only suspect. A faulty Fuel Pressure Regulator, (FPRV), is also likely to give these symptoms.We took Jeremy's FSI for a drive along some twisty and undulating Cotswold lanes last night, logging measuring blocks 000 and 140 (using the .lbl file kindly supplied by Mac - no VCDS crashes with this version).
Initially the target and actual fuel pressures tracked quite well, but after a few minutes it was clear that the actual fuel pressure reading diverged downwards when we encountered a hill or anything that put load on the engine.
You can see this in the graph here:
View attachment 115135
The grey line is the target pressure, the yellow the actual reported fuel pressure.
I then took the wheel. During the initial period, there were glimpses of the sweetness and punchiness of the FSI engine briefly on acceleration before the reported actual fuel pressure fell away and the the engine bogged down. Then the car became very difficult to drive; you can see that the reported fuel pressure dropped and stayed low (3.8 bar) for the last two thirds of the circuit. In fact, 20m from the end, we came to a halt, the engine struggled to idle and any attempt to set off resulted in a stall. After 10 minutes sat in the middle of the road, we resorted to pushing it to a safe place. Here is a log of the second circuit with target pressure in blue, and reported actual fuel pressure in orange.
View attachment 115136
After 30 minutes switched off, the vehicle was able to be re-started and driven back up the hill.
The reported constant fault is 17428 Fuel Pressure Regulation Control Range Exceeded P1020, but the test drive also threw up intermittent faults (16684 Random/Multiple Cylinder Misfire Detected P0300 and 16686 Cylinder 2 Misfire Detected P0302.
I'm attached the 2 .CSV files that are the basis for the above graphs (I've changed the file type to .txt to comply with the forum upload rules)
As always, any insights or observations welcome!
Stephen
Thank you for the analysis and effort that has gone into this, Mac. In the absence of an available HPFP, we had been considering (reluctantly) looking to fit new O rings to the existing pump. However, this analysis does seem to suggest that would be futile. Jeremy is going to have to take some difficult decisions soon as it's his only vehicle and he lives out in the sticks...I've been looking hard at this fault condition, bit sad, but gives me something to think about.
My conclusion is that it's the HPFP that's failed in the @Jeremy FSI.
Here's why:
The PRV, (Pressure Regulating Valve), is spring loaded to the closed, no bleed, position, where the full output of the HPFP, (High Pressure Fuel Pump), is applied to the Fuel Rail.
So the reference to "Closing Angle" is a bit odd, "Opening Value" would make more sense to me. The valve is controlled by a pulse width modulation, so the figures in the "Closing Angle" data block actually represents the pulse width, and, guessing here, an angle of 0 = no pulse, valve closed by spring, no pressure bleed, maximum rail pressure.
View attachment 115376
Looking at the data in the spreadsheet format from @Andrew what's very odd is that the Actual Fuel Rail Pressure never drops below 3.8 Bar, the output from the electric pump, in the tank.
If, as I previously thought, the low fuel pressure was being caused by the PRV not closing properly, and bleeding the rail pressure off, (via the return line), then the Actual Pressure would be zero, or very close to it, not 3.8 Bar.
So, it looks like the HPFP gradually loses pressure, and then delivers absolutely no pressure at all, as if it physically stops. After a while it starts again, then stops again.
This points very firmly to the HPFP as the culprit, but not O ring seals on the pistons, (as there are three separate pump assemblies, unlikely to all fail, and restart at the same time), but the shaft, cam, or lifting ring, (see pic below).
Although the HPFP is hard to come by, it is much easier to change than the PRV, which requires upper inlet manifold removal.
View attachment 115379
Mac.
If possible, taking the pump off the engine, would allow the internals to be the examined, and, just possibly, fixed.Thank you for the analysis and effort that has gone into this, Mac. In the absence of an available HPFP, we had been considering (reluctantly) looking to fit new O rings to the existing pump. However, this analysis does seem to suggest that would be futile. Jeremy is going to have to take some difficult decisions soon as it's his only vehicle and he lives out in the sticks...