MembersPage/BrianWeldon (2007-10-10 14:44:57)

Audi AAN 5cyl 20VT engine

Modifications:

Eurospec 2.6L Block (Carillo rods, Arias pistons)

ported and polished/flow matched cylinder head

GT30R .82 A/R Turbo (4" anti-surge inlet)

60 lb/hr Injectors w/ Bosch 044 Fuel Pump

Stromung 3" exhaust w/ custom 3" downpipe

RS2 exhaust manifold

Greddy Oil Catch Can

Samco boost hoses

Apikol Gen.2 Intercooler

custom charge pipe w/ HKS SSQV blow-off valve

034 Motorsports High Output Coil Kit

RS2 6-speed transmission

South Bend FE Series Clutch

JB Racing 11 lb. flywheel

2Bennett full coilover suspension (track spec)

OZ Racing Ultraleggera 17" x 8" wheels

Porsche 996TT brakes

Please measure the MAF pins in the harness

We recognized that the MAF connector is simply unsuitable, because we need 4 pins (neither must be connected to GND or +5V) which is simply not available in the MAF connector. If we find 3, that, together with the NBO2 nernst signal might be enough.

Anyway, finalized pins to use for WB02 LSU4 sensor:

Using these pins we wouldn't use the MAF plug, but would allow there to be enough inputs for the WB02.


In the meantime, review VemsAudiAan

You can do the verification measurements,


I am testing this ECU for Brian on my stock 93 S4 and am having major problems trying to interface with megatune. I downloaded the latest megatune from this site, uploaded (and verified) the 1.1.23 firmware and loaded the config posted by marcel but the config will not verify. An error message comes back on the verify stating that there is a flood of charachters on the serial line. this is with or without a reboot of the ECU inbetween firmware flash....

Further update:

Still having issues, but at least now I think I understand _why_, but will need help in figuring out how to correct the problem. I tried loading the msq config into megatune but the problem is that the software will not communicate with the ecu. I think it has to do with the configuration of the version of megatune I'm running rather than a problem with the ecu or actual communications.. here's why:

I've got two versions of the VEMS upgrader tool on my hard drive, only ONE of them will connect to the ecu and allow me to do a firmware upgrade/verify: V3GUI-audi-1.1.24 ... the V3GUI-release WILL NOT talk to the ECU.

What to do next?