Chat Purchased a 1.6 FSI

[PlasticMac]

So today I snatched a drive with VCDS running. Measuring blocks for 14, 15 and 140 concurrently.
All the 1450+ entries are appended with "SYSTEM OK" however the engine seems to be holding back very slightly, possibly a minor misfire. I can't attach the .csv file but here is a snippet:

I'm not sure what Columns F & K relate to but the entries are mainly "Enabled" with a few "Disabled" !

It would be easier if you could use the new lbl file. The column headers would make sense.
The fuel pressures look good, with requested and actual, (wrongly headed absolu
te bar etc), very close.
The "enabled" column is miss fire count, (for cylinder 1,2&3), with no miss fires detected. Cylinder 4 is in the next group, 016, which is not logged.
@Andrew may see something I've missed, as it's a bit late for me.
Have you got the new lbl? It really would make things easier, and a lot of effort went into creating it.
An engine scan may be useful too, see if there are engine faults logged after the drive.
Edit: Did you log any data with engine rpm above 3,000 rpm?
Mac.

 

[Andrew]

Good Evening Andy,

Nothing untoward in the screenshot of the log, but it was only the first 17,seconds with the engine idling. Any evidence later (post) of errant behaviour?

Agree with Mac on Autoscan, good to see what that produces.

Still a little concerned over the engine earth. When you were cleaning it up did you inspect/test the cable? This cable is known to fail within in its length, hidden from view by its outer sleeve. If possible before starting from cold add a supplementary earth with hefty jump leads and/or meaty earth lead.

Andy

 

[AndyBa]

It would be easier if you could use the new lbl file. The column headers would make sense.
The fuel pressures look good, with requested and actual, (wrongly headed absolu
te bar etc), very close.
The "enabled" column is miss fire count, (for cylinder 1,2&3), with no miss fires detected. Cylinder 4 is in the next group, 016, which is not logged.
@Andrew may see something I've missed, as it's a bit late for me.
Have you got the new lbl? It really would make things easier, and a lot of effort went into creating it.
An engine scan may be useful too, see if there are engine faults logged after the drive.
Edit: Did you log any data with engine rpm above 3,000 rpm?
Mac.

Hi Mac, thanks for your response. I thought I had loaded the new file tbh. I have 3 versions on my laptop previous versions renamed - I'll move them to a different folder. Let me upload again.
I did do a check prior to running the scan and there were no error codes. However I didn't do a post scan.
Yes I do have captures from a drive where rpm was over 3k.

 

[PlasticMac]

The lbl file that @Andrew has posted on here is not compatible with the Lite version of VCDS, I have a version that is.
If you have the correct lbl file, you'll see the file name in the top left corner of the screen.
I've PM'd @AndyBa a copy of the Lite lbl file
Mac.

 

[AndyBa]

Hi Mac, I see what you mean about the file name. I do wonder if it is the way I have saved the file?
Ordinarily when I change filenames I "right-click" and alter the file extension, however it is still showing as a text document.
I also tried saving as a .lbl under all files, no change !
I maybe doing something obvious wrong !

 

[PlasticMac]

Hi Mac, I see what you mean about the file name. I do wonder if it is the way I have saved the file?
Ordinarily when I change filenames I "right-click" and alter the file extension, however it is still showing as a text document.
I also tried saving as a .lbl under all files, no change !
I maybe doing something obvious wrong !

I see what you mean, it does seem see it as a text file. I do the same as you, right click, Rename, backspace txt then type lbl.
Try opening the original .txt file in Notepad, then Save it with the .lbl extension.
Then copy and paste into the lable folder.
Mac.

 

[L162LZ]

Hi Mac, I see what you mean about the file name. I do wonder if it is the way I have saved the file?
Ordinarily when I change filenames I "right-click" and alter the file extension, however it is still showing as a text document.
I also tried saving as a .lbl under all files, no change !
I maybe doing something obvious wrong !

Have you got "extensions" visible in Windows explorer, sometimes if you havent you might still have the file suffix as txt ie "filename.lbl.txt" check here in windows explorer

 

[AndyBa]

Try opening the original .txt file in Notepad, then Save it with the .lbl extension.
Then copy and paste into the label folder.
Mac.

Yup that worked. Just need to do another test.
Many thanks.

 

[AndyBa]

So today I connected the laptop and logged a few captures;

First one was as below, summary shows excessive misfire on Cylinder 2. Although there is misfire across all cylinders.

I swapped the new Coilpack on cylinder 4 for the replaced one in cylinder 2 and did another capture. Interestingly the misfire disappeared on cylinder 2 with the new coilpack installed and there weren't any misfires on cylinder 4 either. However starting was even more difficult from warm.

I've taken other captures but can't share the files.

FYI attachment 2 confirms I only have one 036-096 file in the VCDS Labels folder. I did check the file name when taking the 14, 15 and 140 group capture was 036-906-013-BAD in the top left corner.

I haven't tested starting from cold but I doubt there will be any change.

 

[PlasticMac]

Take a look at Group 141, Block 03. Check it with ignition on, engine not running. You'll see the fuel pressure from the electric tank end pump. When starting, fuel pressure is very reliant on the electric pump as the engine driven HPFP is running at low pressure, as engines revs, driven by the starter motor, are low until the engine catches and revs rise, and with it the Rail Pressure.
LBL file looks OK.
Mac.

 

[AndyBa]

Been out for a drive around today. Didn't have the laptop so no scans taken. Starting still poor so need to get the HPFP readings. From the info provided by @PlasticMac the HPFP may be the issue.
Not sure if I can detect any further misfire, will probs reseat coilpack 3 which has been untouched since I bought it.
Hopefully take some more scans this weekend.

 

[PlasticMac]

Been out for a drive around today. Didn't have the laptop so no scans taken. Starting still poor so need to get the HPFP readings. From the info provided by @PlasticMac the HPFP may be the issue.
Not sure if I can detect any further misfire, will probs reseat coilpack 3 which has been untouched since I bought it.
Hopefully take some more scans this weekend.

Poor starting is, imo, more likely the electric pump in the tank, not the HPFP.
The electric pump pressure is seen in Group 142, Block 3, with ignition on, but engine not running.
Mac.

 

[PlasticMac]

Poor starting is, imo, more likely the electric pump in the tank, not the HPFP.
The electric pump pressure is seen in Group 142, Block 3, with ignition on, but engine not running.
Mac.

Also, scan the engine, we need to confirm the flaps are moving correctly. They are down, during starting, maximising air flow, to match rich fuelling to get the engine to fire. As soon as it starts, the flaps move to the up position, and the mixture weakens.
Mac.

 

[AndyBa]

...and time goes by...
This evening I took a capture of Group 142, but I don't think it's showing the expected results?

 

[PlasticMac]

I've had a bad day, so take my answer with a whole salt cellar, but I think it shows your inlet flaps are in good fettle.
Mac.

 

[AndyBa]

Poor starting is, imo, more likely the electric pump in the tank, not the HPFP.
The electric pump pressure is seen in Group 142, Block 3, with ignition on, but engine not running.
Mac.

Thanks Mac, good news about the flaps
Is there a different group that shows the tank pump is working. I seem to recall I was shared a summary listing of what the different groups show but I think I need to have a folder seach to find it!

 

[AndyBa]

Looked back at this post and unearthed the groups listing.
Can only see Groups 140 and 141 relating to fuel so will get a capture of them.
Incidents have noted more misfires on cylinder 2 after doing the coilpack swap (about 19 in 5mins). These don't seem to be affecting pick-up at junctions as before tho.

 

[Andrew]

...and time goes by...
This evening I took a capture of Group 142, but I don't think it's showing the expected results?

Good Evening,

I tend to agree with Mac's comment, flaps not stuck at some intermediary position and Adapted OK so looks good but it would be good see flaps moving. Beside Group 142 add a block to show revs and post some screenshots of the log as the revs move past 3000rpm, say 2500-3500rpm.

Andy

 

[PlasticMac]

Thanks Mac, good news about the flaps
Is there a different group that shows the tank pump is working. I seem to recall I was shared a summary listing of what the different groups show but I think I need to have a folder seach to find it!

Group 141 is fuel pressure.
To check the electric pump, monitor Block 003, with the ignition on, but before starting the engine. You'll then see the pressure of the electric pump on it's own.
Mac.

 

[PlasticMac]

Good Evening,

I tend to agree with Mac's comment, flaps not stuck at some intermediary position and Adapted OK so looks good but it would be good see flaps moving. Beside Group 142 add a block to show revs and post some screenshots of the log as the revs move past 3000rpm, say 2500-3500rpm.

Andy

If you run the same log as before, (142), but start logging with ignition on, but before starting the engine, you'll be able to capture the full arc of flap movement.
This is because, when you turn the key to first position, the flap actuator vacuum vents, to ensure the flaps are down, (inlet fully open). Wait a few seconds, then start the engine. As soon as the engine is running, vacuum is applied to the actuator, and the flaps move to the up, (stratified), position, which is what your log, (post 74), shows.
If you log Group 141 & 142, starting with ignition on, engine off, you'll check the flaps and electric fuel pump at the same time.
Mac.