Audi S2 (1992) Suspected misfire

   #1  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
Friday,24,February,2017,17:53:34:28420
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 17.1.3.0 (x64) HEX-NET CB: 0.4334.4
Data version: 20170203 DS267.2
www.Ross-Tech.com




Chassis Type: 8C - Audi 80/S2 B4 (1992 > 1996)
Scan: 01 02 03 08 15 25

-------------------------------------------------------------------------------
Address 01: Engine Labels: 895-907-551.lbl
Part No: 895 907 551 A
Component: 2,2l R5 MOTR.RHV HS D01
VCID: A208B9DA2CA075515F-4A84

1 Fault Found:
00513 - Engine Speed Sensor (G28)
03-00 - No Signal
Readiness: N/A

-------------------------------------------------------------------------------
Address 03: ABS Brakes Labels: 4A0-907-379.lbl
Part No: 4A0 907 379
Component: Bremsen-Elektronik
Shop #: BB 23836
VCID: E89CEBF28A1C5F01C1-4B3C

No fault code found.

End----------(Elapsed Time: 02:07, VBatt start/end: 11.7V/11.7V)-----------

I'm still reasonably new the VCDS game, currently trying to assist my girlfriends father with his 1992 Audi S2 (ABY). An auto-scan doesn't yield much in the way of useful information, that G28 fault was thrown purely on account of us not having the engine fired up during the initial scan. There was an earlier lambda probe fault, cleared some time ago and which has never returned since.

Current symptoms are a poor lumpy/misfiring idle, extremely strong smell of fuel from the exhaust. It is possible to rev the engine (unloaded), at which point it'll run relatively smoothly for a time. Left to idle it will invariably bog down and ultimately stall, under load I understand there to be very little/no power. Increased coolant temperature sees some improvement, but ultimately it still runs lumpy and is generally undriveable.

Given the limitation of the ECU I am looking for advice, specifically with regards how I can best utilise my Hex-Net interface to help identify whatever the underlying issue is.
 
Last edited:
   #2  

Rekked

Verified VCDS User
Verified
Joined
Sep 14, 2014
Messages
29
Reaction score
11
Location
Australia
VCDS Serial number
C?ID=224535
ABY engine, i would start by pulling the top cover off to expose the coilpacks, being very gentle, and inspecting all the wiring to the coils which quite often disintergrate!
I also beleve MAF's fail on these also
 
   #3  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
ABY engine, i would start by pulling the top cover off to expose the coilpacks, being very gentle, and inspecting all the wiring to the coils which quite often disintergrate!
I also beleve MAF's fail on these also

Many thanks for the advice, should we expect to see a MAF fault or might such a failure be hidden from VCDS?

With regards those coil packs, I understand there has been some earlier patchwork due to perished cables, indeed we had speculated that might be an area to explore ...although it remains as yet uninvestigated (it was getting a little dark)!
 
   #4  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
Sitrep Many components changed, original symptoms persist.

New components: Spark plugs, leads/connectors, idle stabilisation valve, fuel pressure regulator & fuel filter.

It would be great to hear from anyone on what to tackle next, is there anyway in which to utilise VCDS to narrow in on the faulty component? Regarding the MAF, nothing was highlighted during the scan.
 
   #5  

MartinsX

Verified VCDS User
Verified
Joined
Sep 5, 2016
Messages
1,229
Reaction score
1,311
Location
Riga, Latvia
VCDS Serial number
C?ID=268515
Check for flywheel teeth damage. There are two sensors and one is reading the same teeth where starter engages, another one is for reference point, probably G4.
Sorry if I'm not correct in some point, last time I repaired ABY was 3 or 4 years ago...
 
   #6  

Jack@European_Parts

Gone But Not Forgotten
Professional VCDS User
Joined
Jan 29, 2014
Messages
21,923
Reaction score
9,308
Location
Montgomery, NY, USA
VCDS Serial number
C?ID=57337
G28 fault before cranking/running is normal in this controller before starting....!

Compression check .........what are the readings in this pile?
 
   #7  

Rekked

Verified VCDS User
Verified
Joined
Sep 14, 2014
Messages
29
Reaction score
11
Location
Australia
VCDS Serial number
C?ID=224535
I had an AAN engine with rough running and low on power which was very intermittent, ended up scoping the cam sensor (sitting behind the cam pulley) and the signal was intermittently dropping off - never threw a fault code though. Replaced the sensor and fault never came back.

Might be worth investigating!
 
   #8  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
Thanks everyone! We're revisiting this issue tomorrow morning, I'll feedback on progress.
 
   #9  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
We're not making much headway unfortunately, and so I've logged some live data in the hopes that someone here will spot something.

LOG-01-010-001-003.CSV
LOG-01-01F-023-038.CSV

From what we can tell this seems to be an over fuelling issue, rather than a misfire. Any thoughts and/or comments are welcome!
 
   #10  

Jack@European_Parts

Gone But Not Forgotten
Professional VCDS User
Joined
Jan 29, 2014
Messages
21,923
Reaction score
9,308
Location
Montgomery, NY, USA
VCDS Serial number
C?ID=57337
Have you tried swapping injectors to isolate the miss and while doing so check the condition of the injectors?
What is the compression for all zylinders when compared?
Have you veified the FPR is not leaking fuel right through the vacuum line on the intake directly causing this rich running condition?
 
   #11  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
...I also beleve MAF's fail on these also

Well, in the end it was the MAF! But as mentioned before no error were thrown by the ECU, which has half surprised me.
 
   #12  

JohnnyFiama

Verified VCDS User
Verified
Joined
Mar 14, 2017
Messages
38
Reaction score
13
Location
UK
VCDS Serial number
C?ID=288500
Just a quick "thank you!" to everyone who posted on this thread, your collective input was very much appreciated.
 
   #13  

Jack@European_Parts

Gone But Not Forgotten
Professional VCDS User
Joined
Jan 29, 2014
Messages
21,923
Reaction score
9,308
Location
Montgomery, NY, USA
VCDS Serial number
C?ID=57337
Awesome .......this story never gets old at all........
Now did you compare VCDS blocks of the sensors, so you know what to look for the next time as a deviation & that the PC cant?
 
Back
Top