Audi urS4 1992 with the AAN engine
 |  |
My goal is for now:
- use all original sensors
- replace the MAF with a MAP
- replace the original Lambda with a WideBand Bosch LSU4.2 (7200) if possible
- make my own electrical loom/harness for the engine, using VAG OEM connectors and Econoseal connectors on the Vems.
- Make the engine run nice and good.
- make it work with COPs from 1998-2007 VAGs, 06B905115L, logic-level
- Guide for conversion from original POS/coil to COP here:
- http://www.bonnquattro.se/aan/18tCoilPackConversionInstructions.pdf
What I know:
- I will buy the assembled vems with econoseal connectors
- I need 5 logic outputs for the ignition, would like a 3+5 version
- The extra flyback 30v diode seems like a good choice
- I will buy a wideband lambda
- I will buy a EGT sensor
- I want the LED (4x20?)
- I want a special lambda display
- EGT and knock sensors(would like to use the stock knock sensors)
- onboard MAP sensor 400 kpa
- I will buy some econoseal connectors 18+36
- Primary trigger Is VR
- Secondary trigger would be "audi trigger"
What I dont know:
Q: Shall I order 2+6 version, what can I use the 2 high current outputs for ?
A: Lots of things. Relay, solenoid, NOS, ...
Q: How about firmware and sensors, do I need to compile something myself ?
A: no need to compile anything. See VemsTune
Q: I suppose I should choose PS2 connector as well
A: useful eg. for wheel-speed input (but we can connect PS2 clock signal to an unused pin as well
VEMS info (I have bought a VEMS that came with this info:)
Board_version=v3.3
Serial_nr= 2267
pump-= 4.05V
wbo2_pump_pw_zero=0x64
wbo2_nernstdc_target=0x87
pump+= -1.0mV/200 Ohm
AREF=4.9V
(C103=1nF, no D100)
Other project info
I have bought a engine loom from a -02 VW passat that will fit the COPs.
Purchased a used WBO Bosch LSU 4.2 7090/91 as per below.
Will start making the new COP work with the OEM ECU to begin with.
Time frame:
2016-01-18
I have begun installing this now. I will make an adapter cable to fit the Motronic 55 connector at first. When I have it all working I will make a new wireloom. Maybe I will wait until next engine takes it place in the car.
Detail your motronic55 adapter. (especially GND-s)
I started out connecting the Vems on bench to my PC so I could update FW. It turned out I needed to "lock" the CPU with direct ISP programming. It worked nice but now I cannot update bootloader further because of "access denied".
I have got the password from VEMS, thanks! Upgrading the FW was no problem when having that :-)
2016-06-19:
I need to update my config files from the old maps 12x12 to new ones 16x16 and maybe some other stuff. Im researching this topic right now.
Was it tuned very well ? (or just OK, or not really well ? It might be easier to start from some generic config; in any case, check ignouts anyway, update your paper and web docs)
I have put together cable for the LCD and tested it out.
I also fixed Bluetooth connection so I can connect to it in the car later on.
I also bought a cheap android pad and tested VEMSdisplay, very good! I like it alot! :-)
Questions
2016-06-26
I have no trigger input at all using triggerlog! :-(
I have Firmware v1.2.31
- that is not special, but auditrigger is a bit special
- [VT help] should be primary source of info
- InputTrigger/TriggerLog next
- anything else after those
And this is taken from configfile:
primary_trigger=C3
secondary_trigger=19
tooth_wheel=1E
trigger_tooth=00
another_trigger_tooth=06
lcd_analin=67
tooth_wheel_twidth[0]=00
tooth_wheel_twidth[1]=60
cam_sync_r_edge_phase=01
cam_sync_f_edge_phase=02
reset_engphase_after=F0
Is that correct?
- We reproduce with full vemscfg.
- Auditrigger divby9 or divby3 is special (especially if old config was uploaded without a new VemsTune without / or before "update ini files from web"
- Save old config
- remove igncoil primary conn+fuses ; and inj connectors and/or fuses upload a 60-2 config (primary trigger dialog bottom, select and "Send"), for cranking triggerlog ; better in this case anyway as it should show all teeth
Also used built in help in vemstune (newest VemsTune version ?).
The most likely reason for not seeing VR pulses (other than trivial: VR signal not going below 0V or not reaching +200mV) is if device was powered with insufficient grounding and P259 blown.
Detail your motronic55 adapter. (especially GND-s)