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

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

 _____ 
(  _  )
| ( ) |
| | | |
| (('\|
(___\_)
       
       

 _       
( \      
| (      
| |      
| |      
| |      
| (____/\
(_______/
         

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

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:
Engine runs, but config needs review. "Nissantrigger 360+4" 4cyl * primary trigger: 4 pulse * secondary trigger: 360 pulse [http://www.vems.hu/files/Fero/NissanTrigger/ config and triggerlog] * was triggerlog captured with primtrig rising or falling ? (write rising or falling in the filename next time). symptoms: * RPM-reading fluctuates. * cyl1,4 ign is OK, ** but cyl2,3 ign is 20 degrees off (advanced?) ** with per cyl spark delay it can be fixed, but RPM-reading still fluctuates To check: * primtrig rising or falling edge ---- Most likely '''edge related''' * Either the choice of primary trigger edge * or the assumption (from available descriptions and patent) at the time of implementation was wrong ** even with a real disk, the direction of rotation can be wrong and the polarity of nissan HALL also could be uncertain. We're investigating this but still no proper info: * primtrig scopeshot would be highly welcome ** even with soundcard * even DVM voltage measurement of primary trigger (with running engine) would be some info about polarity.
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.