Some Audi PNP Config Files.
This is files taken from car`s I`ve been tuning. These can be used as startup files and could probably be useful for some. All files are from 1.1.77 or later using VemsTune.
Audi RS2: PNP, ADU Engine, Siemens Deka 630cc injectors@4bar, Fully built engine with 8.5 to 1 comp. Turbonetics super60 0.68ar, 98oct fuel, ported head with 7A cams, Standar vems MAT sensor. Hall-inverter 034 high output coils
http://www.vems.hu/files/Reidar/Memberspage/Audi%20RS2%202.2L.vemscfg
Audi RS2: PNP, 7A head with LongBlock, bigger valves, 8.5 to 1 Comp, Precision 6262 0.68ar, MTM cams. Standar Vems MAT sensor, This car is dynoed at 98oct fuel to 670hp and 760nm at 1.8 bar boost. RC injectors 750@3bar running 4bar. boose controlled by N75 valve, 034 high output coils, None Hall-inverter
http://www.vems.hu/files/Reidar/Memberspage/Audi%20RS2%202.5L.vemscfg
AUDI S2: PNP, 3B engine, precision 6262 0.68ar, 9.3 to 1 comp, stock cams, siemens deka 630cc running at 4bar, boost controlled by n75 (High boost 2.3bar), Standar vems MAT sensor, stock coil, Hall-inverter
http://www.vems.hu/files/Reidar/Memberspage/Audi%20S2%202.2L%203B.vemscfg
Audi S6: PNP, AAN engine, Ported, schrick cams, 8.5 to 1, GT35R turbo, dynoed 634hp and 732nm, siemens deka 630 running at 4bar, standar vems MAT sensor. Boost by N75, 1.8T coils, Hall inverter
http://www.vems.hu/files/Reidar/Memberspage/Audi%20S6%202.2L.vemscfg
Audi S6: PNP, AAN, STANDAR AUDI PTC MAT SENSOR, Longblock 2.5L with ported head and 7A cams, GT3071 0.63ar Turbo. 8.5 to 1 comp. Dynoed 478hp, siemens deka 630cc running at 4bar. Boost by N75, 034 high output coils.Hall inverter
http://www.vems.hu/files/Reidar/Memberspage/Audi%20S6%202.5L.vemscfg
Did you checked the primary trigger Pin BTDC with a timing light? On the second RS2 with 2.5liter and 670 hp you have 67 there while i have checked with a timing light and have 64. Does this mean that i have to extract 3 degrees in order to compare them 1:1 ?
Thanks for sharing
Triggerlog basics - with audi trigger:
- the shown triggerlog pulses are after the internal divider: 90 (not 270) if divby3, 10 pulses (not 270) if divby27 (possible via divby-any) is configured
- if the camhall signal is connected properly (for masking every 2nd crankhome-VR pulse), then there is a sectrig pulse for every 270 primtrig pulse (so every 2nd crankhome-VR pulse shows up in the triggerlog)
- IMPORTANT: if the camhall signal position is bad, it might completely mask off both crankhome-VR pulses (there is just one pin on the crank, but that is 2 pulses per engine cycle)
- a guy thought his crankhome-VR sensor was bad because he didn't see sectrig pulses in triggerlog. While he saw camhall on scope. Yes, camhall was there, but at bad position (not around crankhome-VR)
- if the HALL sensor is disconnected, and camhall signal is pulled to ground with a wire (assuming camhall inverter inside the box) or camhall signal left open or pulled to +5V (without camhall inverter) than every crankhome-VR pulses go through (one per 135 primtrig pulses). Very good method for testing !
- auditrigger does not even try to detect missing tooth.
- VemsTune tries to help the user by marking long gaps. That's what you see in the grid. Read about the triggerlog RPM limit below.
If the ecu miss one tooth on the 135tooth trigger wheel, what happens?
- misfire for ~1 rev
triggerlog RPM limit
- in this case, RPM is too high for auditrigger for 19200 baud (that is 1920 bytes per sec ~ 900 primtrig pulses per sec because CRC and framing also consumes some bandwidth). Primtrig pulse every 0.8 msec (1200 /sec), so some pulses are silently lost and than apparently 1.6 msec is seen (which is in reality 2*0.8 msec). This does not indicate a real problem with the engine.
- try lower RPM (remember triggerlog is mostly to debug cranking problems) or higher baudrate
Ford Escorth Cosworth 1994 (EDIS-4) 36-1 trigger.
Problem:
Tachometer jumps around when cranking. I`ve seen this on a lot of cars running vems. At this Ford it became a problem, since the tacometer needle jumpst all the way around and get stuck.
This is a problem since we need to remove so much from the dashboard to get it fixed, and it only jumps around after a few startups.