######  
     #   
   ##    
  #      
 ######  
         

  _     
 | |    
 | |    
 | |___ 
 |_____|
        

 __  __
 \ \/ /
  \  / 
  /  \ 
 /_/\_\
       

 _   _ 
( ) ( )
| |_| |
|  _  |
| | | |
(_) (_)
       
       

         
 ##      
 ##      
 ## ##   
 ####    
 ## ##   
 ##  ##  
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
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). http://www.ubernugen.com/vems/4.2installed1.jpg **************************** 25 September 2005// Ok, I got my wiring hooked up and the board says Hello I uploaded firmware 1.0.18 using perl and tested it with terminal. Deleted the 'firmware' directory in the Megatune release 024 build and replaced it with the above. Megatune loads and gives me good temp readings but apparently there are no real .mtt files. I cannot for the life of me figure out how to make the .mtt files from the config.txt and tables.txt *Follow this [http://www.vems.hu/wiki/index.php?page=MembersPage%2FJohanEriksson%2FVerThreeFirmForDummies guide], step 4 I beleive goes into detail quite well on how to do it. Thats where I go when I upload new firmware and need to upload my tables and config. ***GOT IT!!! Thanks to Richard Barrington for clarifying some of the perl commands and reminding me to copy the relevant text files into the firmware directory. Too many hours working on the project and not enough experience with perl... :P I also seem to have a crappy v3.2 board since EC36pin8 and EC36pin17 injector drivers failed the diode test with the pin 23 flyback. I don't know what to do about that since I did not build the board and planned to avoid that part of the "fun". I notified Jason about the problem. You can install 2 diodes (ES2J SMB, or BY399 throughole recommended) in series (for each driver that needs it) between the injdriver line ( cathode to EC36pin23 in every case; anode to the injdriver line, EC36pin8 for one diode-set and EC35pin17 for the other diode-set), - until you receive a new controller. Please '''order assembled v3.x controller from the WebShop''', so you can select the right options (don't pay for the assembled controller! select check/money order payment method). *ok, cool hack. I will hook those diodes up and see what happens. * 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) Bloody bollocks, this has gone and broken my software completely. I have tried every combination of install/burn/delete/comvert, etc. And I either get the megatune screen beeping and dials flipping all over or I get this: controller code version does not match signature in vemsv3.ini expected "0x32" Received "" I have spent 6 hours re-burning, deleting, etc, etc... and it's totally shagged. I even unplugged the EC36 and ran just power to the ECU to see if it was a sensor short or something. Nope. Um, what have I done? 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 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) ---- 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 MembersPage/BenNesbitt/SensorPage MembersPage/BenNesbitt/ConfigPage
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.