______  
(  __  \ 
| (  \  )
| |   ) |
| |   | |
| |   ) |
| (__/  )
(______/ 
         

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

   _____ 
  / ____|
 | (___  
  \___ \ 
  ____) |
 |_____/ 
         
         

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

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

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:
'''Porsche 911 3.3 Turbo''' This car came to a friend of mine for mapping as he knows the specifics of these cars. But it was soon clear that the car needed more then mapping, it showed signs of trigger problems. '''Specification''' The spec is VEMS v3.2, 1.0.36 firmware, MSD DIS-4, proper waste spark coils, copy of original 911 turbo triggerwheel from a late model car. BMW VR sensor. The problem is that the triggerwheel is badly positioned, the missing teeth is around #1 TDC. ''More to come.'' '''Problem''' At high loads it banged and shot very violently, when going through the register at lower loads it just showed some hesitation. This is pretty common. '''Tests and results''' '''Full indexing (Strobe light)''' When strobing the car on each coil it seem to fire at least one of the coils 120 degrees off now and then at idle. It's impossible to see how often but it happens. '''Wheel error counter''' The wheel error counts up to 1-2 during initial cranking and can count up when the cars idle is let down low enough for it to almost stall (3-500rpm). When the bang and cutout problem occur the wheel error counter _does not_ count up. '''Is the wheel error counter a reliable way to make sure that there are no false triggs or can some types of errors sneak through?''' '''Scoping triggersignal''' Redundant as the wheel error counter said everything was ok but as this is the only chance I have to scope the car I did it. The trigger signal was marginal in the missing tooth area, this is what made me doubt the wheel error diagnostics. It looks like it could almost arm the trigger for doing a false trigg in the missing tooth area. check my_make, if it has ''MY_CONF += -D ALLOW_SLOPPY_TOOTHWHEEL'' (uncommented), than it tolerates 1 less toothcount (eg. 34 instead of 35). This is because it assumes that the tooth after the missing tooth was not sensed and everything was delayed 1 tooth (10 degree for a 36-1). There is no reason to completely cut power in this case (someone in Estonia claimed his engine needs ALLOW_SLOPPY_TOOTHWHEEL to run). Idle: http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/idle_10X_0.15v.gif Around 2k: http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/2kish_10X_0.15v.gif Around 3k: http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/3kish_10X_0.15v.gif 5-6k: http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/high_rpm_10X_0.15v.gif This wheel is useless, at least with VR sensor. Do you have a drawing, or picture of the missing tooth area to educate the future generation ? '''I know the flywheel trigger is badly designed and that the triggersignals is dangerously close to a false trigg but the wheelerror counter does NOT count up when the missfire problem occur! Does this mean that the wheelerror counter can't be trusted?''' The bad triggerwheel design: http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/bad_flywheel_trigger.jpg ---- http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/config.txt http://www.vems.hu/files/MembersPage/JorgenKarlsson/TomasPorsche/tables.txt The signs of communication corruption in the config.txt file makes me suspect that the communication with the ecu is not reliable and that corruption might have occured when the end user upgraded the firmware and uploaded config and tables. * MembersPage/PhatBob Are you using a recent megaloader executable? I had to re-write the downloader because of a similar problem. * MembersPage/JorgenKarlsson I have asked the owner to download the latest 1.0.36 package from http://www.vems.se/UserFiles/File/VemsMT1.0.36.zip, it sounded like he used a mix of sources for the tools when he uploaded the firmware. * MembersPage/JorgenKarlsson I have recived config downloaded with fresh tools and it's still corrupt. I manually repaired it, created the mtt files and sent it back with instructions. Keeping my fingers crossed. * MembersPage/PhatBob Is it possible that the old megaloader has crept back into the release? I know that it happened once before. You can tell if you have the correct megaloader as it prints the config to screen as it uploads. This highlights the potential hazzard caused by us not having a properly defined release proceedure. ---- But is the problem in the bad missing tooth location? If not, maybe using Honeywell 1GT101 Hall sensor could cure the false trigger signal problem? PeepPaadam We have tested the Honeywell sensor a bit with multitooth triggerhweels lately and it will not read a wheel that is similar to this. It self calibrates until it doesn't see the wheel, then it calibrate until it see the wheel again. This continues in 1-4 second intervals. I can't say for this particular wheel but it is pretty similar to the ford sheetmetal triggerwheeel we tested. On the wheel we tested it worked after we removed half of the teeth to make it a 18-1 triggerwheel.
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.