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

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

 _     
| |    
| |    
| |    
| |____
\_____/
       
       

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

  ____  
 |  _ \ 
 | |_) |
 |  _ < 
 | |_) |
 |____/ 
        
        

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:
Auditrigger on a inline 5 cylinder Audi engine,but now only with distributer,and 1 coil. After 16 hours of hard work we tried to start the engine.Everything looked great,we had RPM signal during cranking,we had spark (at the right cylinders),and injectorclicking too.Unfortunately the engine did not fired up,after 4 hours of continous problem searching,we did not found the cause of our sadness.We tried different ignition and fuel settings.I also realised that the car dont really want to pull vacuum under cranking (in the vems,map sensor),tough i can feel it with my hand.(no plumbing,only throttle body).Note that the car was running in the past with dual K-jet without problems.We also checked Compression in the cylinders,and they are good. * firmware 1.0.30 * [http://www.vems.hu/files/MembersPage/NanassyPeter/ClonInstallStartUp/mct.txt tables ] * [http://www.vems.hu/files/MembersPage/NanassyPeter/ClonInstallStartUp/mcd.txt config] * mdd0c logs (zipped together) http://www.vems.hu/files/MembersPage/NanassyPeter/ClonInstallStartUp/mdd0c_logs.zip I formatted the binary logs with /svn/firmware/utilities/vemslogger/auditrigger_logformatter <mdd0c_3.log >mdd0c_3.txt and watch: <code> P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d 9c 9b 9a 99 98 97 96 95 94 93 9 2 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 81 P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d 9c 9b 9a 99 98 97 96 95 94 93 9 2 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 81 P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d _ 9c x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x _ x P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d 9c 9b 9a 99 98 97 96 95 9 4 93 92 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 81 P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d 9c 9b 9a 99 98 97 96 95 9 4 93 92 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 81 P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d _ 9c x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x _ x P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d 9c 9b 9a 99 98 97 9 6 95 94 93 92 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 81 P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d 9c 9b 9a 99 98 97 9 6 95 94 93 92 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 _ 81 P b5 b4 b3 b2 b1 b0 af ae ad ac ab aa a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 9f 9e 9d _ 9c x x x x x x x x x x x x x x x x </code> The '''offending crankhome VR pulse''' typically '''comes after 1 crank rotation''' (==0.5 cam rotation, 2.5 events) instead of 2 crank rotations. So that means : '''check your cam-HALL !''' that is responsible to mask every second crankhome VR pulses * does the HALL get supply ? * Is it connected at all ? * '''maybe cam-HALL position is rotated so the crankhome VR signal is not masked out ?''' The cam-HALL should be active (pull down to GND) at the same time when the crankhome VR comes! This is important to check * what voltage do you measure on EC36pin13 ? ** when engine off, but power on: likely 4V or so (0V also possible if the HALL is just at the window) => goes in between when engine rotates. Measured mean (DC) voltage should change something like 4V => 3.9V when engine starts to rotate because the HALL pulls down 1/40 of the time. * Don't try HALL 5-window yet. Make the 1-window CAM-HALL work. * Don't invert crankhome VR polarity. It's likely good. When the CAM-HALL is working, we can tell for sure It's good that you published config and mdd0c logs. After trigger hammered, don't forget * '''take logs with MegaTune''' (remember to say bye after fiddling in Man mode, taking mdd0c log for example). ** we'll watch for fuel pulsewidth (possible fuelcut due to TPS>60% floodclear at cranking or kPa fuelcut, whatever...). '''I checked this,there is PW''' * is the ignition right where you like ? Do you have a lamp? I remember this engien has a custom crankhome VR position, a few degrees off. ** if it's just 2 degrees or so, the normal procedure of varying trigger tooth or ign_tdcdelay should work well * is the fuel system working ? fuel pump, fuel pressure ? ** '''Sure, its working,there is a LOT OF fuel i the cylinders'''
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.