______ 
| ___ \
| |_/ /
|  __/ 
| |    
\_|    
       
       

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

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

 ___   
(  _`\ 
| (_(_)
|  _)  
| |    
(_)    
       
       

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

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:
'''BMW triggers''' I plan to summarize common BMW trigger info on this page. Crank trigger on BMW engines from the 80's is 60-2 teeth inductive (VR). Engine codes are M10, M20, M30 First generation of camshaft pulse sender is an inductive pickup on the HV ignition cable for cylinder #1. This appeared on later M20, M30 engines. Second generation of cam pulse senders is inductive (VR) pickup on the camshaft end, single pulse before cyl #1 TDC. Apparently pulse is at the same time when the missing teeth are on the crank trigger. Engine codes: S38, M50 Scope printout of an S38 signal: http://quasar.dynaweb.hu/~lezsi/vems/bmwtrigger/s38-trigger-scope.jpg Apparently this coincidence of cam signal and missing teeth is problematic to synchronize on current VEMS firmwares. The cause is that secondary (cam) pulse is sometimes processed earlier than the first crank pulse, but sometimes later. Triggerlog of this situation (from M50B25 non-vanos engine): http://quasar.dynaweb.hu/~lezsi/vems/bmwtrigger/v3.3_u006408-2013-10-19-14.23.17.triggerlog AFAIK the only solution with current firmware is running crank-trigger only, and wasted spark. (ignoring secondary trigger). This results in a simple 60-2 setup, running fine. However triggerlog-recording also has some problem: http://quasar.dynaweb.hu/~lezsi/vems/bmwtrigger/v3.3_u006408-2013-10-19-16.28.17.triggerlog This is a log of an engine startup and running fine without missing events or trigger errors in vemstune. Probably communication failed? This should be controlled in triggerlogging it's very controversial when analyzing logs.
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.