______ 
| ___ \
| |_/ /
|  __/ 
| |    
\_|    
       
       

     #   
         
    ##   
     #   
     #   
     #   
 #   #   
  ###    

_________
\__   __/
   ) (   
   | |   
   | |   
   | |   
___) (___
\_______/
         

 ___   
(  _`\ 
| (_(_)
`\__ \ 
( )_) |
`\____)
       
       

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

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:
''' Cam sync near missing teeth ''' I tried enabling cam sync on a early BMW M50 non-VANOS engine with bad results. I used a '''Honeywell GT1 Hall sensor since this engine has a VR sensor''', only the VANOS engines have a Hall sensor but we had none of those and the GT1 is a drop-in replacement (needs a 4 mm shim to get 1 mm distance to tooth). * the VR wheel is different from a HALL wheel. ** It is very possible that it can cause signal detection problem at a few thousand RPM. The adaptive threshold of the GT1 will adjust to the middle between the normal teeth high/low : but the magnetic amplitude at the missing teeth is different. First off, to the believers in "keep it simple stupid" : If we ignore the fact that this engine can run perfectly fine with dual-out and "wasted spark", I feel this is an irritating issue that should have a solution or anwer. Is this related to what's written in this forum thread : * [http://www.vemssupport.com/forum/index.php/topic,1906.msg19691.html#msg19691 vemssupport.com forum thread] * see post by fphil on 2nd page Here is a log file, triggerlogs (rising + falling) and the pictures below. * http://www.vems.hu/files/MembersPage/MattiasSandgren/Trigger/bmw-m50-non-vanos-triggerlogs-fw1.2.0.zip Right at about 3500 rpm the sync just goes crazy. I might have a hardware problem here with the sensor not detecting it properly, but the sectrig position doesn't make much sense. It's rock solid at 26.7 or 28.1 degrees at all other times up to that point. I have a hard time seeing that there is suddenly a lot of slop in the cam chain drive. So it could possibly be something with the sensor. * I guess a scope shot of the problem would say a lot but I would like to know what the developers have to say and what others have seen might confirm what's going on. ** yes, a scope shot is essential in this case ** if you take triggerlog, set higher baudrate (115200) Here are the triggerlog pictures from cranking the engine that show that the camsync tooth appears right at the missing teeth gap on this engine. Falling edge (the better choice: more than 4*6 degrees from tooth0) http://www.vems.hu/files/MembersPage/MattiasSandgren/Trigger/bmw-m50-non-vanos-camsync-falling.png Rising edge http://www.vems.hu/files/MembersPage/MattiasSandgren/Trigger/bmw-m50-non-vanos-camsync-rising.png
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.