Details:
1993 Audi 80/90 Quattro
1997 Audi A8 4.2 liter V8 engine with sequential injection and coil-on-plug ignition.
Using a 60-2 trigger wheel on the crank with a (I think) VR sensor from the 1993 12v V6 and the stock A8 4.2 cam position sensor (Hall).
-- I would recommend to unplug the sensor completely, or at the best fix the problem, a WBO2 sensor doesnt like to be in the exhaust without heat, especially when trying to get the engine started, you will likely see a very rich mixture before getting it running completely
The motor runs (badly) much the same as before.. It will fire up and then die unless I hold some throttle. When I do this the motor surges up and down repeatedly but will respond hesitantly to heavier blips on the pedal.
-- Here i suspect that your engine is running lean, try to raise "injector opening", by 100uS for each try. It might be a bit tricky to get these injector characteristics correct, You know that you have a too high opening setting when you cant get it to run lean enough on idle and extremely low load. You can also just try to raise fuel in the VE table.
For about 5 seconds - maybe 45sec-1min after starting - it will smooth out and seem to run like a real engine but then it's back to surging and then it's harder to keep running so it usually dies.
-- Check your warmup enrichments, You might have enough fuel after a minute and then its back to a lean condition again.
Hope something i wrote is useful, //Emil Larsson
11 Oct - Here is the tables file that megatune has made for my ECU. SO far it starts and occasionally responds (with a 1 sec lag) to throttle blips, but dies immediately.
j[0]=6680 6680 6780 6980 6E80 7180 7180 7380 7380 7380 7380 7380
j[1]=6780 6980 6B80 6F80 7580 7980 7A80 7980 7980 7980 7980 7980
j[2]=7080 6E80 7180 7880 8380 8880 8680 8280 8280 8280 8280 8280
j[3]=7280 7580 7D80 8480 9180 9880 9880 9280 9280 9280 9280 9280
j[4]=8080 8680 8880 8D80 9B80 A480 A880 A180 A180 A180 A180 A180
j[5]=8580 8980 9080 9380 A880 B380 B980 B380 B380 B380 B380 B380
j[6]=8D80 9080 9780 9C80 AF80 B880 BF80 BE80 BE80 BE80 BE80 BE80
j[7]=9280 9580 9A80 A080 B080 BA80 C580 C280 C280 C280 C280 C280
j[8]=9280 9580 9A80 A080 B080 BA80 C580 C280 C280 C280 C280 C280
j[9]=9280 9580 9A80 A080 B080 BA80 C580 C280 C280 C280 C280 C280
j[A]=9280 9580 9A80 A080 B080 BA80 C580 C280 C280 C280 C280 C280
j[B]=9880 A080 A280 A880 B080 BA80 C580 C280 C280 C280 C280 C280
l[0]=3F 36 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
l[1]=39 34 31 31 31 31 31 31 31 31 31 31
l[2]=39 36 32 32 32 32 32 32 32 32 32 32
l[3]=39 39 39 39 39 39 39 39 39 39 39 39
l[4]=39 39 43 47 4F 4F 4F 4F 4F 4F 4F 4F
l[5]=44 44 4F 55 5A 5A 5A 5A 5A 5A 5A 5A
l[6]=66 66 66 66 66 66 66 66 66 66 66 66
l[7]=6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B
l[8]=6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B
l[9]=6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B
l[A]=6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B
l[B]=6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B 6B
n[0]=20 24 50 77 A0 B4 B4 B4 B4 B4 B4 B4
n[1]=24 28 50 78 A0 B1 B2 B1 B1 B1 B1 B1
n[2]=28 2C 50 77 99 AA AB A9 A9 A9 A9 A9
n[3]=2C 30 50 76 95 A1 A2 A1 A1 A1 A1 A1
n[4]=30 34 50 75 8D 99 9B 9A 9A 9A 9A 9A
n[5]=34 38 50 6F 83 8E 8F 8F 8F 8F 8F 8F
n[6]=38 3C 50 67 7A 81 83 84 84 84 84 84
n[7]=3C 3F 50 5F 6F 78 78 78 78 78 78 78
n[8]=3F 3C 50 5F 6F 78 78 78 78 78 78 78
n[9]=3A 3C 50 5F 6F 78 78 78 78 78 78 78
n[A]=3A 3C 50 5F 6F 78 78 78 78 78 78 78
n[B]=3A 3C 50 5F 6F 78 78 78 78 78 78 78
k[0]=14 1E 28 32 3C 4B 5A 69 6A 6B 6C 6D
r[0]=05 0A 0F 14 1E 28 32 40 41 42 43 44
h[0]=10 04 01 08 02 20 40 80
h[1]=00 00 00 00 00 00 00 00
h[2]=07 05 03 01 07 05 03 01
b[0]=28 30 38 40 48 50 58 60 FF FF FF FF
t[0]=21 40 60 80 A0 C0 E0 FF
28 September 2005//
Ok, I got my wiring hooked up and the board says Hello
Here are the steps I have just taken with the new software. I will now head over to the car and see what happens:
1) Erased everything on the hardrive having to do with mt/vems (Vems ECU still has .18 firmware on it).
2) downloaded firmware .18, firmware .18 ignition dual output files, mtr024, mtr025 ini.
3) unzipped mtr024 and mtr025 ini. Replaced the r024 .ini with r025 .ini in MegaTune2.25b602/mtcfg folder
4) unzipped firmware .18 and .18 dual ignition output files, inserted dual ignition files into firmware .18 directory
5) deleted the .15 firmware native to the the megatune folder and replaced with the new .18 firmware folder.
6) deleted the pre-existing config.mtt and tables.mtt files in the firmware/ect folder
7) converted the existing config.txt and tables.txt to .mtt files with:
perl bin\make_table.pl tables.txt tables.mtt
perl bin\make_conf.pl global.h config.txt config.mtt
And put them in the firmware/etc folder
8) now I am ready to burn the firmware to the VEMS ECU again, right? I don't see why it would be needed, if you already have the newest (1.0.18 at this time). You can verify first. (but burning again is not a big deal either)
IT WORKS!!!
- Now that we know how to wire the CPS I just need to somehow see where it is with the crank at TDC? Still a little fuzzy on what I am looking for there...
- after the sensor sees the first tooth after the missing tooth (gap), count the number of teeth to the first TDC event. Place a wire in a sparkplug hole if you are unsure about cylinder position. With a manual gearbox, use gear5 so the engine can be moved easily by rolling the car a little.
IGN_DUALOUT
(ben writes) This info below is a little fuzzy to me. Is this a hack so I can run without the second trigger wheel for a while?
I guess we might as well make it go with wasted spark if possible since it sounds like I need to make a new trigger wheel for the cam.
(/ben)
On Jorgen's request, Marcell compiled a firmware with IGN_DUALOUT: http://www.vems.hu/files/Firmware/release/v3_firmware_1.0.18_IGN_DUALOUT.zip
I added the note to GenBoard/UnderDevelopment/FirmwareChanges that MegaTune vemsv3.ini needs a small change. With the old definition of "42 bytes of runtime-vars", MegaTune will beep like hell.
It is untested (but compiled with the same compiler as other releases, that all passed testing).
IGN_DUALOUT means, that
- in h[2] you configure channel 01, and 00 is also fired at the same time.
- in h[2] you configure channel 03, and 02 is also fired at the same time.
- in h[2] you configure channel 05, and 04 is also fired at the same time.
- in h[2] you configure channel 07, and 06 is also fired at the same time.
So a sane configuration is:
- ignchmax=03
- h[2]=01 03 05 07 01 03 05 07
With a 60-2 wheel, and another_trigger_tooth=0x0F (decimal 15) only the first four element of h[2] is actually used (but with IGN_DUALOUT, each fires 2 channels). Eg. if you configure trigger_tooth=03,
- timed from tooth 3: ch7 and ch6
- timed from tooth 18: ch5 and ch4
- timed from tooth 33: ch3 and ch2
- timed from tooth 48: ch1 and ch0
are fired. The exact time is (ign_tdcdelay/2 - actual_ignadv) crankdegrees after the tooth. ( ign_tdcdelay is 0.5 degree resolution, but MegaTune does the conversion for you IIRC)
- Does this mean that I'm not using tooth #2 anymore? Please clarify...
- you can configure any trigger_tooth you like. According the image on MembersPage/BenNesbitt/InputTrigger you're still triggering from teeth 2,17,32,47 and assume that TDC is 60 degrees later (that is teeth 12,27,42,57)
Fill in these pages with all the required info and watch your config be pretty much built for you
MembersPage/BenNesbitt/IgnitionPage
MembersPage/BenNesbitt/WBsensor
MembersPage/BenNesbitt/FuelPage
MembersPage/BenNesbitt/InputTrigger
MembersPage/BenNesbitt/IdleControl