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

 ___   
(  _`\ 
| (_) )
|  _ <'
| (_) )
(____/'
       
       

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

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

 _    _ 
| |  | |
| |  | |
| |/\| |
\  /\  /
 \/  \/ 
        
        

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:
'''Audi 2.2L 5cyl 20V Turbo''' As you know, this is the most powerful type of engine under 6 cyl. [http://www.vems.hu/files/MembersPage/NanassyPeter/NanassyP-2005-07-24.zip Starting config] * MembersPage/NanassyPeter/Status * MembersPage/NanassyPeter/PC_VEMS communication * MembersPage/NanassyPeter/PinOut * MembersPage/NanassyPeter/Config * MembersPage/NanassyPeter/TriggerSetup * MembersPage/NanassyPeter/Ignition * MembersPage/NanassyPeter/FuelFeed - injectors * MembersPage/NanassyPeter/AirFeed - idle air * MembersPage/NanassyPeter/BoostControl * MembersPage/NanassyPeter/LCD * MembersPage/NanassyPeter/OldStatus Its in a 1985 90 Quattro (4000Q or 4kQ in the US). 200m 8.0sec 400m 12.9sec That's awesome. You should log on to ChatViaIRC and we could talk. My nick is natn0. ---- '''TODO:''' from the symptoms you specified (via telephone) it seems that your MegaTune (at least vemsv3.ini) is incompatible with your firmware * Manmcdmct => save result so it can be negotiated later (likely full of bad values, if MegaTune trashed your config; so name the file in a way that warns about this) * see MegaTune page, download new megatune * upgrade to latest released firmware: GenBoard/UnderDevelopment/FirmwareChanges * if the latest released firmware is newer than the firmware in MegaTune release, replace the vemsv3.ini (files) under the MegaTune with the vemsv3.ini file that you find in firmware * '''publish your old known-good config.txt and tables.txt''', and update config (see the .bat files distributed with the MegaTune). ** If you publish your config, we can make config.mtt and tables.mtt that matches the global.h in the recent firmware => therefore just needs to be sent to the firmware ** we can review it for sanity ---- related to your friend's broken efi034: * as a next try, you might want to cut the pin3 (+5V) of the original MPX4250AP. ** If the misbehave is caused by the original MAP sensor pulling down the 4.98V supply, than this will fix it ** if you have a chance to see the baro in the log, during the misbehave. If the baro also drops when MAP refuses to climb back to 100kPa, that makes it likely that the problem is around the 4.98V supply ** as a last chance, the new MAP could be powered from 12V (soldering the regulator, of course). Thanks Marcell, i remembered wrong,there is no datas from the baro in the log of the 034efi. Here is the problematic session: http://www.motorgeek.com/~nstuart/plotter.php?file=pnanassy_lancia_mapprobl.CSV&dir=./plotter&logmode= ---- '''Important links''' * GenBoard/VerThree/PinOut
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.