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

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

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

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

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

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:
--- 07.09.2010 I'm trying to set up camsync on BMW M50 inline-6 engine. The engine starts and revs smooth but it shows trigger errors and tends to foul plug on cyl6. I did some triggerlogs with Vems Tune today. Maybe someone can comment my triggerlogs. Triggers: Primary - 60-2, VR Secondary - 1 tooth, Hall FW 1.1.81 VT 2010-08-19 --- Config - http://www.vems.hu/files/Reinis%20Andersons/v3.3_n002875-2010.09.03-23.33.48.vemscfg Triggerlog (.csv and .triggerlog)- http://www.vems.hu/files/Reinis%20Andersons/Camsyncm50.zip ---- '''Should I try to use secondary trigger "cam-HALL inverter" ?''' Secondary trigger most of the time gives 4.5V signal and 0V only on trigger tooth? The cam-HALL inverter only matters for the 135 (-140-142) tooth auditrigger, when the cam-HALL is used as a mask for the crankhome-VR signal. For primtrig=60-2 it is not used as a mask, simply the position of the chosen edge matters. So for 60-2, '''inverting cam-HALL in hardware should be exactly the same as chosing the other edge in software configuration''' (secondary trigger rising/falling). Unlikely to help. Maybe advance secondary trigger tooth about 3 crankdegrees? * if clearance is so big (>24 degrees) as on the triggerlog (with sectrig=falling edge), that is unlikely to help either <code> ID Prim.trig.msec Delta Ratio Sec.trig.msec Delta Comment 290 2201.648(288) 7.784 1.00 291 2209.304(289) 7.656 0.98 292 2216.652(290) 7.348 0.96 293 2223.620(291) 6.968 0.95 294 2242.756(292) 19.136 2.75 "MISSING TOOTH: 2, cycle=58" 295 2248.740(293) 5.984 0.31 296 2254.828(294) 6.088 1.02 297 2261.068(295) 6.240 1.02 298 2267.704(296) 6.636 1.06 ... ... 345 2597.284(343) 7.528 1.08 346 2604.644(344) 7.360 0.98 347 2612.064(345) 7.420 1.01 348 2619.528(346) 7.464 1.01 349 2626.872(347) 7.344 0.98 350 2633.396(2) 6.524 351 2634.264(348) 0.868 0.12 352 2641.388(349) 7.124 8.21 "MISSING TOOTH: 7, cycle=58" 353 2662.048(350) 20.660 2.90 "MISSING TOOTH: 2, cycle=1" 354 2668.928(351) 6.880 0.33 355 2676.172(352) 7.244 1.05 356 2683.532(353) 7.360 1.02 357 2690.228(354) 6.696 0.91 </code> Screenshots from Trigger Analyze: http://www.vems.hu/files/Reinis%20Andersons/camsynczoom.jpg http://www.vems.hu/files/Reinis%20Andersons/camsyncfallingedge.jpg The above shows >24 crankdeg clearance between falling edge and tooth0. Good ! ---- In this screenshot I changed secondary trigger edge from falling edge to rising edge. Logged it to show Hall polarity and how the secondary trigger tooth is positioned. http://www.vems.hu/files/Reinis%20Andersons/camsyncerrorrisingedge.jpg This, with rising edge is BAD ! Less than 12 crankdeg clearance from tooth0 (dangerous depending on cambelt sloppiness, no reason to risk it) ! So '''stick to falling edge !''' (and adjust the ign outputs accordingly)
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.