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

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

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

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

 _____ 
/  ___|
\ `--. 
 `--. \
/\__/ /
\____/ 
       
       

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. '''Engine Type''' * SR-20 DET, Nissan GTI-R, Pulsar in USA "Nissantrigger 360+4" 4cyl * '''secondary trigger: 360 pulse''' ** '''HW divider was NOT used''', simply connected the 360 pulses to sectrig HALL input. * '''primary trigger: 4 pulse''' ** the length of pulses on this engine is something like '''2,2,2,8''' which DIFFERS from the original specs (the wheel we got and the patent) the 360 tooth trigger was made for originally . Primtrig polarity also differs ! ** So we were lucky that we could still get 1.1.x '''firmware to sync: even without sectrig HW divider, we had to enable the "divby 4"''' flag in config which means "sync to a primtrig tooth that is longer or equal >= 3 sectrig pulses" even though we did not use divider on sec ** the sectrig divider is not used from 1.1.99, secignore is used instead (see below) [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). ---- Most likely '''edge related''' * Either the choice of primary trigger edge (we know now: primtrig must be rising) * 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 was uncertain (actually wrong in the orig spec we received). primtrig scopeshot reveiled that rising edge must be used, the primtrig=hi window length must be measured ---- Now that proper specs (eg. primtrig polarity) was given for Nissan '''[http://cell.dyndns.ws/f/v3_firmware_1.1.99.zip 1.1.99 2012-03-15] has firmware mod to apply for all known types of 360 sectrig-pulse nissan triggers''' * polarity ** primtrig=rising must be configured of course ** always count sectrig pulses when primtrig=high * '''secignore to adjust window-toothcount threshold'''. ** recommended threshold values: '''>4''', >9, >13, so start with secignore=4 for this engine ** because max window can be '''8''', 12 or 16 ** in safe mode (eg prohibit byte screwed or ibutton not touched), corr.air shows the detected peak window-length+128 to aid the user count window-length without scope (VemsTune developers might make a wizard for it). '''Important: ignition output might have slipped one entry''' (strobe would show immediately) * VT, ignition outputs visual dialog, click shift up once, then burn
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.