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

 _     _ 
( )   ( )
`\`\_/'/'
  `\ /'  
   | |   
   (_)   
         
         

   ____ 
  / ___|
 | |    
 | |___ 
  \____|
        

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

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

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:
= Mitsubishi 6G72 page = Installing VEMS into a '''Mitsubishi Galant 2.5 V6 turbo''', engine code '''6G72''' (Cyclone V6 engine firing order: ...) Timing info on MembersPage/PeterJensenMitsubishi '''Apparently supported by any nonancient fw''' (use >=1.2.31 for other reasons) with proper config * key is '''sectrig falling to PRIMTRING FALLING''' * '''EVO valid sectrig => primtrig angle 0.. 84.4 deg''' (or 78.8) ** '''84.4 deg actually means 56 crankdeg for 6 cyl''' = 84.4/180*120 (VT assumes 4 cyl, validate might also show some tooth_wheel warning, neglect that for 6G72) ** only 1 place where sectrig to primtrig measured <56 crankdeg at TDC cyl4 => sync Trigger pattern is a bit unusual. Trigger wheel is like this: http://www.vems.hu/files/MembersPage/PeterJensen/mitsu/trigger.JPG It's very similar to the Lancer EVO trigger, but 6 cyls instead of 4. MembersPage/Fero/MitsubishiEVO Apparently Peter Jensen had experience with this engine back in 2010, but now I cannot open his old triggerlogs, or interpret those configs with currently accesible VemsTune versions: http://www.vems.hu/files/MembersPage/PeterJensen/mitsu/ ---- '''Some hints to prepare?''' '''Scope and/or Bench-test''' with the following in mind: * start from VT primtrig dialog bottom, EVO configlet, key (verify after setting) is ** primtrig normal coil with sectrig subaruspecial = EVO 6-7-8 ** bit6 of: config_secondary_trigger & _BV(strig_subaruspecial) ... '''sync condition''' '''GOOD SOLUTION:''' * sectrig falling to primtrig falling < 53 deg''' is true for ONLY ONE event (25 deg from 100 to 75) ''' ** => so no firmware mod needed apparently, just configure "EVO" and than change to 6cyl and primtrig falling''' '''NOT GOOD''' * sectrig (falling) to primtrig (rising) time < 80/180 * period''' ** threshold is 80 deg for 4 cyl (where period is 180 crankdeg) ** threshold is '''53 deg for 6cyl''' (where period is 120 crankdeg) ** Is that good or not for this 6 cyl trigger ? *** on this V6 : '''45 degrees in 3 occasions''' (=> exact same condition '''not good''' for V6) Historical note: Marcell first didn't notice that primtrig falling is the simplest and perfect soltion, he implemented a CYCLONEV6 fw mod (in effect when "EVO" with >4 cyl configured; 1.2.36 version, but not published): at primtrig (falling), NO sectrig (falling) pulse seen since last primtrig ** but looking at the pulsetrain again, it seems now that happens twice (NOT good) Proceed path: get '''scopeshot(s) or angular positions numerically''' (or verify Peter's) * can be captured with VEMS configured to simple coiltype trigger + strobe if you know what you're doing ** but better scope, or get a free USB soundcard from Marcell and fry that (NOT your notebook's mic input :-). Mix the primtrig and sectrig with DIFFERENT resistors (because most USB soundcards have only 1 channel input; only output is stereo). ** timing is everything here: precise info needed to make a good "signalgen" wav for audacity benchtesting (results are not valid if sectrig relative pos is different than real)
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.