_   _ 
 | \ | |
 |  \| |
 | . ` |
 | |\  |
 |_| \_|
        
        

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

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

 _____ 
|  ___|
| |__  
|  __| 
| |___ 
\____/ 
       
       

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

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:
This project is in a serious hurry, since they want to race on Oct 12, but the trigger is not supported yet !!! First we need to find out the trigger arrangement. So it's VR, with gaps: * 60 * 90 * 30 degrees. The multitooth.c code should fire a "trigger_tooth" (with the assumption we are 70 degrees BTDC) when the gap=30 degrees is detected. This is not very complex, actually very close to what the multitooth.c tooth_relative_length() ( which is called "multitooth advanced filter", that I use on my daily driver, probably noone else uses it at the moment), it might just take a tiny change and matching config. http://www.vems.hu/files/MembersPage/Fero/Fiat_stilo_cranksensor_90_30_60_degree_m.jpg Correct trigger drawings: http://www.vems.hu/files/Fero/stilo_drawing.JPG As you see, the trigger tooth is 70 deg BTDC. And there are two other tooth. So the trigger tooth must be the tooth that is approximately 30 degrees(and +/- some degrees hysteresis)distance after any other tooth. Unfortunately i didn't see the wheel myself. The guy who made the engine has took this photo, and the drawing. And i've checked it with him on phone. So i hope that the round direction is good. Actually, this is the only arrangement and direction that makes sense: inter-tooth gaptimes of 60,90,30 degrees, and trigger-tooth being after the 30degrees gap. Nice! ---- '''Configuration''' firmware revision 1.0.27 (or newer required). MegaTune that matches 1.0.23 or even 1.0.19 should match. Just don't adjust primary_trigger variable from MegaTune (it could change for the bad), leave it alone after uploading the correct value from mtt file. If you change anything from MegaTune, that is on the same page as primary_trigger, verify on LCD or mcd that primary_trigger variable is not screwed. * primary_trigger=29 ** 1: multitooth is on ** 8: advanced filter is on ** 0x20=32: fiatstilo is on * secondary trigger=.. ** distributor does not need camsync ** without distributor, camsync must be used! GenBoard/Manual/InputTriggerCamSync ** wasted spark is OK, use h[2]=00 01 00 01 .. * rel.. * ... * trigger_tooth=00 * another_trigger_tooth=03 # yes, very tricky '''No change:''' * ignchmax=03 # for 4cyl * rpmk[0]=0b # for 4cyl * rpmk[1]=b8 # for 4cyl I commited a fiat-stilo trigger wav-generator to firmware SVN, but haven't had time to test it in operation.
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.