_______ 
(       )
| () () |
| || || |
| |(_)| |
| |   | |
| )   ( |
|/     \|
         

    #    
         
   ##    
    #    
    #    
    #    
   ###   
         

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

 _    _ 
( )  ( )
`\`\/'/'
  >  <  
 /'/\`\ 
(_)  (_)
        
        

   ___ 
  |_  |
    | |
    | |
/\__/ /
\____/ 
       
       

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:
'''Odd fire 90,150,90,150,90,150 degree V6''' Now even the factory 30,90,30,90, ... factory maserati trigger is supported even with the dual camsync pulse (1.1.90 firmware). See below. ---- '''Non-maserati triggers''' Common denominator is 30 deg, which '''suggests 12 teeth on crank''' (also called 24+1 pattern with Tools/Play-trigger type c024) '''Bench tested configs''' using '''per cylinder spark delay''': * [http://www.vems.hu/files/MembersPage/OddFireSixCyl/11+1_with_spark_delay.vemscfg 12-1] * [http://www.vems.hu/files/MembersPage/OddFireSixCyl/60-2_with_spark_delay.vemscfg 60-2] triggers ---- '''Maserati factory trigger setup''' primtrig pattern 30,90,30,90,30,90, 30,90,30,90,30,90 with double camsync pulse [https://docs.google.com/leaf?id=0Bzteg8lQJZdWYmQ3ZTA3YjctZGY5Yy00NTc5LWE1OWQtOTljMmY5YjRkYTg1&hl=en&authkey=CJTa1IoG Maserati biturbo .wav] made by Phil. * '''Bench tested OK with 1 campulse even with 1.1.88''', using this [http://www.vems.hu/files/MembersPage/OddFireSixCyl/v3.3_s001212-A-2011.04.19-17.31.14.vemscfg config ] ** '''same config with 1.1.90 now works with dual camsync pulse''' ** easy way to configure: at the bottom of "primary trigger" dialog: used configlet: Maserati Z012 (after VemsTune ini update or VemsTune newer than 2011-04-19 ) ** note: a similar trigger (but 10 cyl instead of 6 and 1pulse camsync) is the Viper engine: MembersPage/PeepPaadam/BMWwithViperEngine VemsTune Tools / Play trigger: "Z020" ** obviously ignition '''outputs must be configured''' (according to wiring), and TDC-delay adjusted with strobe. ** It's a good idea to strobe just one ignition output first and note which cyl each slot belongs to (the rest ignouts disabled, or disconnected, also with injectors and/or fuelpump off) ** only install the WBO2 sensor in the exhaust after the engine started (for longer WBO2 sensor life) For the curious: * similar to Fiat Stilo, triggering from short-gap (neglecting the 90 deg gap and timing from every 30deg pulse, but using per cylinder spark delay) * but advanced filtering enabled and 125% threshold (eg. Normal tooth 20-'''125%''', missing tooth '''125%'''-425%) * to get odd fire output with this setup (and proper timing), per cylinder spark delay is needed ** Could you elaborate this spark delay?, 2 delays should be needed ? ** What about sequential injection ? * '''needs strobing to find ign_tdcdelay''' (TDC after the trigger) value. ** Any idea (speculation or measurement) about the '''pulse position wrt TDC ?''' *** from the workshop manual it is 10° before TDC, also the Microplex firmware substracts 10° from the ignition map value after reading it. ---- '''Reftooth-based solution might be another option''' WARNING: not yet passed testing with missing tooth + uneven odd-fire reftooth table ! * '''12-1''' teeth on crank is another rational pattern (3,5,3,5,3,5 differences in reftooth because tooth width=30 degrees). * or '''36-1''' (9,15,9,15,9,15 differences in reftooth because tooth width=10 degrees) * or '''60-2''' (15,25,15,25,15,25 differences in reftooth because tooth width=6 deg) also makes sense. With the missing-tooth primary trigger even the multiple-tooth camsync is no problem for recent firmwares using proper "sectrig ignore" value as on MembersPage/DamirMuha/MagnetMmarelliCamSensor As you see, that method is about * the '''reftooth table.''' ** but '''firmware mod required''' (in avoid_tooth() function) for uneven reftooth table otherwise it would attempt timing from nonexistant tooth * obviously the '''secondary trigger must be enabled as camsync''' * also, enabling the odd-fire bit might be needed so the RPM does not fluctuate up/down according to 90/150 degree time, but measures every second event (240 degrees) ** maybe some cheating with the cyl number also needed to show correct RPM (the cyl number has no other effect currently) ---- '''Page needs to be cleaned up''' * also we'll make index page to different odd fire engines (and some generic instructions). * Generic information will come to this page, and specific to the Maserati biturbo goes to MembersPage/FPhil (started with very similar content) ---- '''SOMEWHAT OBSOLETE SPECULATION: Another chance''' to get 1.1.x working on this trigger is using divby2 with the "auditrigger" (because that is a pre-divider: divides before the pulses are considered giving 120,120,120,120,120,120 pattern). But than quite extreme per-cylinder ignition trimming (60 deg delay every 2nd cyl) is needed for the 90,150,90,150,90,150 result. ** as 1.1.x firmware tries to time from the last tooth and expects constant spacing between teeth (except at the missing tooth, or missing teeth). The InputTrigger/SubaruThirtySixMinusTwoMinusTwoMinusTwo and the uneven old-lancia/fiat and subaru has separate implementation in 1.1.x (while the maserati still does not have a dedicated handler) * with 1.0.x the effective spark-tooth is "frozen" (not trying to time from the last possible tooth) The solution to set 30 crankdegree teeth on the crank pulley was also recommended by Matthias on [http://www.vemssupport.com/forum/index.php/topic,1648.0.html Vems uk] This is the reply I have posted "The sensors are VR but it is not a big problem to make a Hall signal from them" * indeed, there is also a VR=>HALL (LM1815 based) converter in DSUB9 housing now (with divider option for multitooth ABS sensors). I can filter out one of the crank trigger or even I can divide the triggers by two to make 2 x (1cam trig +3 crank trig) each for one even fire 3 cylinders, for respectively the left bank and the right bank of the engine . But in this last case I need 2 GenBoards !!! This is what Maserati has done for the late biturbos: 2 triggers + one ecu (ignition+injection) for each bank The 30,90,30,90,30,90, 30,90,30,90,30,90 arranged according to ign events, trigger tooth marked '''bold''': * 30, 90, '''30''' * '''90''' * 30, 90, (next crankrot: ) '''30''' * '''90''' * 30, 90, '''30''', * '''90''' The good news is that if firmware userspace "triggertooth" calculation can be taught about the uneven tooth-times (modifying the userspace easier than the interrupt timing code state machine), that might provide an 1.1.x solution without the per-cylinder spark delay tweak. * config: ** coil-type ** odd-fire bit enabled * toothwidth=30 deg ** AND nr of tooth=6 (not 12 !)... this special value together with toothwidth=30 could mark this Maserati trigger for now.
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.