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

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

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

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

 ___   
(  _`\ 
| |_) )
| ,__/'
| |    
(_)    
       
       

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:
Car: 1984 Porsche 911 3.2 Carrera, 3.2liter 6cyl boxer aircooled, from factory Motronic 1.0 with 35pin connector, currently VEMS plug and play using factory harness (TPS, MAT, WB added), batch fire (two banks of 3 injectors, low-z), stock coil (max dwell 2,1 ms stock) and distributor. Q: EC36/13 with cam-HALL inverter ? *connected or left open ? A: No CAM inverter, left open, EC36/13, can take photo of sectrig hardware setup. '''129+1 auditrigger (but with separate tooth ring and pin not reading starter ring).''' The auditrigger was made by audi to read the starter ring (sectrig also timed from pin on crankshaft ), that setup is supported by VEMS (proven, works reasonably reliably). * Why using 129 tooth if not reading starter ring ? * why not using 60-2 or 36-2 or 24-2 tooth in that case (with separate tooth ring) ? A: 129+1 is factory setup and preferred way to have plug and play kit to work. Bosch was using all kind of peculiar triggers before 60-2 patent was expired (iirc 1986) and then started using this. Here's photo of how stock setup looks like: http://forums.pelicanparts.com/uploads20/Reference+and+Speed+Sensors1332680796.jpg * What is the exact sectrig setup ? ** how precisely timed relative to the crankshaft ? (eg. reading pulse from the camshaft will not work). ---- Problem: shows trigger error ("tooth length bad" and occasionally doubles RPM causing VEMS to hit RPM revlimiter. Very dangerous situation and need to resolve it. Here are log and vemscfg, '''engine runs otherwise nicely'''. http://www.vems.hu/files/PeepPaadam/911.vemscfg http://www.vems.hu/files/PeepPaadam/911_3.2_v3.3_u019379-2020.07.06-14.59.51.vemslog '''IMPORTANT : triggerlog also needed to reproduce and verify setup''' see InputTrigger/TriggerLog * secondary_trigger=0x19 Is there a chance the cam-HALL window (rising or falling edge) is very close to the crankhome-VR pulse (sometimes before/after)? * if cam-HALL is used, scopeshot would be needed to verify that. (if constant GND with camhall inverter, or constant +5V without cam-HALL inverter, than cam-HALL scopeshot not needed) ** sectrig scopeshot still needed
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.