_______ 
(  ____ \
| (    \/
| (__    
|  __)   
| (      
| )      
|/       
         

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

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

  _     
 | |    
 | |    
 | |___ 
 |_____|
        

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

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:
'''Current configuration''' Using factory 60-2 crankshaft mounted wheel and block mounted VR sensor. VW 2.0 liter (ABA code) block. Pin 1 on sensor is VR+ Pin 2 on sensor is VR- Pin 3 on sensor is shield VemsTune config: TDC after trigger: 54 degrees Number of teeth on wheel: 58 First trigger tooth: 4 Next trigger tooth: 30 Angular width of tooth: 6 Minimum crank period: 768 us Reference tooth config: 0: 0 1: 30 2: 0 3: 30 4...8 disabled Distributor was removed. Hall sensor inside went with distributor. In the future I may reinstall a secondary trigger. ---- '''Old configuration''' '''36-1 crank wheel''' and crank trigger setup on spare (and dirty) engine block: http://proton.shadowflux.com/vems/crank_sens_mtd_small.jpg http://proton.shadowflux.com/vems/sens_block_small.jpg http://proton.shadowflux.com/vems/sens_gap_small.jpg http://proton.shadowflux.com/vems/crank_trigger_machined_small.jpg http://proton.shadowflux.com/vems/crank_trigger_mounted_small.jpg {{```[http://proton.shadowflux.com/vems/crank_sens_mtd.jpg]```}} [http://proton.shadowflux.com/vems/crank_sens_mtd.jpg] {{```[http://proton.shadowflux.com/vems/sens_block.jpg]```}} [http://proton.shadowflux.com/vems/sens_block.jpg] {{```[http://proton.shadowflux.com/vems/sens_gap.jpg]```}} [http://proton.shadowflux.com/vems/sens_gap.jpg] {{```[http://proton.shadowflux.com/vems/crank_trigger_machined.jpg]```}} [http://proton.shadowflux.com/vems/crank_trigger_machined.jpg] {{```[http://proton.shadowflux.com/vems/crank_trigger_mounted.jpg]```}} [http://proton.shadowflux.com/vems/crank_trigger_mounted.jpg] Here you can see the TDC mark in the pulley aligned with the missing tooth. You are looking at the back of the pulley, so from this angle it would rotate counter-clockwise. The TDC is 15 degrees after the center of the missing tooth. ..so we set up the sum of trigger_tooth + ign_tdcdelay for 195 degrees. Offsetting 180 degrees is absolutely reasonable because max ignition advance is limited by ign_tdcdelay. 15 degrees of max ignition advance is not enough. Actually, ign_tdcdelay should be at least 30 crank degrees larger than ignition advance at cranking. Common ign_tdcdelay values are 55..65 degrees. igntdc_delay=0x1e (30 decimal, that is 15 crank degrees) is very bad, see above. trigger_tooth=00 and igntdc_delay=0x1e, at n[]=0, the coil would fire at TDC, but you might not be happy with max advance of 15 degrees, and timing from previous tooth would be active even for very low RPMs (where RPM variations are significant => BAD for dwell precision at low RPM). * let's assume a normal tooth=10 crank degrees (=360/36 if it's 36-1) We are using 36-1, so tooth-tooth spacing is 10 degrees. * trigger_tooth=0d (decimal 13), that is 13*10=130 crank degrees because one tooth is 10 degrees. trigger_tooth=00 means the '''tooth after the missing tooth''' will act as the trigger. Please correct it wherever you see it wrong. * ign_tdcdelay=82 (decimal 130, which is 65 degrees) This results in realistic n[] values, if TDC is 130+65 (=195=180+15) degrees after the first tooth after missing tooth. Adjust trigger_tooth in the first place, and only fine-tune with ign_tdcdelay (you can keep it in 60..70 degrees range, which is ideal) ---- Ignition h[2] sequence questions: In the manual there are two tables describing what should be used in the h[2] array, but I don't see how they could possibly be correct. h[2] is different than h[0], see GenBoard/Manual/DigitalOut/Table. Basically, h[0] allows to fire 0..8 injector channels at the same time (any values are valid). h[2] is simpler, only allows exactly one at a time and valid values are * <h[2] value> <mdh to activate> <mdh to inactivate> * 00 mdh82 / mdh02 * 01 mdh92 / mdh12 * 02 mdha2 / mdh22 * 03 mdhb2 / mdh32 * 04 mdhc2 / mdh42 * 05 mdhd2 / mdh52 * 06 mdhe2 / mdh62 * 07 mdhf2 / mdh72 The same values in h[2] that are used for GenBoard/Manual/DigitalOut would actually make more sense (72 instead of 07) but it's currently not implemented that way.
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.