__     __
 \ \   / /
  \ \_/ / 
   \   /  
    | |   
    |_|   
          
          

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

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

 _   _ 
| | | |
| |_| |
|  _  |
| | | |
\_| |_/
       
       

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

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:
Some recent setups demand multitooth wheels with none missing. A typical setup is (refer to it as:) '''24+1''' * primary trigger: 24 pulse on cam (or 12 on crank is effectively the same) * secondary trigger: 1 pulse on cam Please note that N+1 where '''N<=11 requires 1.1.27 firmware''' (or newer). This is where tooth_width >=64 degrees, that is tooth_wheel_twidth2>0. Most notably relevant to * 10+1 (5cyl engine with 5 pulses on crank) ** find config (full and partial extract) examples [http://www.vems.hu/files/Firmware/config/trigger/MultiToothNoneMissing/ here] * 8+1 * 4+1 (2 pulses on crank or 4 on cam) ---- '''Pulse timing restriction''' The campulse must always come between the exact same 2 crankpulse ("no race condition"). With HALL sensor, be careful to select the right edge (for both primary and secondary trigger) that satisfies this. Since the cambelt sloppiness is usually well within +-12 crankdegrees, a 12 tooth crankwheel is practical (one tooth every 30 crankdegrees allows the sloppy campulse to be always between same two crankpulses). ---- '''How does this relate to auditrigger?''' This N+1 style is supported in 1.0.x (since appr 1.0.36, early 2006), called InputTrigger/AudiTrigger setup, with 270+1 as the primary target (commonly found on 5 cylinder audi engines). 270+1 is when you have 135 tooth on crank. Unlike the 24+1, the 270+1 needs a hardware trick so the campulse always comes between same two crankpulses: it is a "pulse timed by crank, masked by cam" (nickname "cramhome"), that is the infamous 3-input trigger system, see InputTrigger/AudiTrigger. ---- '''1.0.x Configuration''' example for 24+1 * '''tooth_wheel=87''' (decimal 135 tooth, that is "auditrigger setup). * '''another_trigger_tooth=06''' (for 24+1 setup with 4 cylinders) * trigger_tooth= with another_trigger_tooth=06, must be between 0..5 * alternate=13 # or 03 if no simultaneous injection is needed at startup * ign_tdcdelay=.. # whatever the timing needs ** h[0]=according to injectors wiring ** h[2]=according to ign wiring, eg. 20 30 20 30 .. .. .. .. (beware of new sameantcis, see GenBoard/UnderDevelopment/FirmwareChanges ) * otherwise same as the old-style InputTrigger/AudiTrigger config, just another_trigger_tooth and trigger_tooth changed as indicated above (lower than decimal 54 and 27, of course) ** secondary_trigger=1D is standard rising edge, (camsync with filtering??) secondary_trigger=19 (rising edge, camsync without filtering) could work too. But secondary_trigger=09 cannot work ** primary_trigger=FB # rising edge, coiltype (yes!), trigger filter disabled (bit2=0). Coiltype chosen. and primary trigger filter might work with 24+1 (but not with 270+1) Note that in 1.0.x (only with auditrigger setup), trigger_tooth changes in the opposite direction than you got used to (with missing tooth wheel). That is, higher value will bring the spark earlier. '''Important''' * benchtest setup (firmware+config) with ElectronicDesign/TriggerSignalGenerator and LEDs before experimenting on real engine * record both channels to see the timing restriction is satisfied ** firmware could log this somehow, in an advanced auditrigger-log format to ease verification * you will need a TimingLight to adjust base timing on the engine '''Please report your benchtest results with recent 1.0.x'''. There is some allowance for the campulse to come (eg. 1 pulse) ahead in some cases. This was desired for the original 270+1, and does not matter with a proper N+1, but with a bad camsync position (if the campulse sometimes comes slightly after crankpulse X, sometimes before), than 30 degrees retard you will feel for sure. The allowance should be configurable (like 0/1/2 tooth). ---- '''Beware: 1.1.x with auditrigger setup currently does not support N+1 if N < 270 (that is, below 135 tooth on crank)''' Because with 135 or 142 tooth at appr 7000 RPM the engine lost power (retarded 1 tooth than cut spark, as a safety mechanism when firmware thought the input pulsecount was too low), there are some specializations in 1.1.x that currently do NOT allow arbitrary N+1, like 24+1. Work in progress, so 1.1.x will handle everything supported by 1.0.x (and more). ----- == Test Results == Using a Toyota 24+1 distributor and a VEMS v3.3 Serial No.316 with VR/VR trigger. Trigger was driven using a pillar drill. Test of the 24 tooth trigger was performed by setting primary trigger type to coil-type. No RPM was seen when changed to multi-tooth. [http://vems.hu/www.vems.co.uk/VEMSTrigger/24+1Log1.zip Log One] [http://vems.hu/www.vems.co.uk/VEMSTrigger/24+1Log2.zip Log Two] [http://vems.hu/www.vems.co.uk/VEMSTrigger/24+1config.txt Config]
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.