_       _ 
( )  _  ( )
| | ( ) | |
| | | | | |
| (_/ \_) |
`\___x___/'
           
           

______ 
|  ___|
| |_   
|  _|  
| |    
\_|    
       
       

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

  ______
 |___  /
    / / 
   / /  
  / /__ 
 /_____|
        
        

  _______ 
 |__   __|
    | |   
    | |   
    | |   
    |_|   
          
          

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:
I use VEMS V3.6 on my dragcar powered by a cbr1100xx engine. Until now the engine was running on four carburetors plus nitrous and the performance was very good (8.7sec@402m). I turned to fuel injection and VEMS in order to use all the extra racing features (like launch control, shift cut, etc) and be able to have a more precise engine control. SOFT/FIRM In the past (1.0.73 firmware) I was using MegaTune software with no problem. At the moment I use the VemsTune0.10.20(2010.03.08) and the firmware uploaded on VEMS V3.6 is 1.0.73. ---- '''TRIGGER''' I use the original trigger wheel and VR sensor of the cbr1100xx with no problem. The cbr1100xx (carburated model) uses a 9teeth trigger wheel with one big missing tooth (later injection model had a 12teeth trigger wheel with no missing teeth). http://www.vems.hu/files/AutoVeltiosis/cbr1100_trigger.jpg '''It's a 12-3''' pattern (toothwidth=30 degrees). Unfortunately this is not supported with 1.1.x firmware, you can only use N-2 or N-1 pattern as set in the primary trigger options. You might need to use '''1.0.x firmware for now with this pattern.''' The following Trigger Setting were tested as long as I use the Megatune and were proven to work fine with 1.0.x firmware. It's not a MegaTune / VemsTune issue. '''It's an 1.0.x / 1.1.x issue. 1.1.x times from the last possible tooth. ''' The closest you could go with 1.1.x is N-2 with toothcount=10 (but even that unlikely to work, and extremely unlikely to work well). With N-2 firmware would decide to trig/start dwell from 0..9 (whatever is last) but only 0..8 tooth exist here, so at certain RPM/load it would wait indefinitely for nonexistant tooth, (until reboot). Trigger Edge: Rissing Trigger Type: Missingtooth Missing Tooth Type: N-1 Special Trigger Type: Normal TDC After The Trigger: 45.0 Number Of Teeth On Wheel: 9 First Trigger Tooth: 1 Next Trigger Tooth: 6 Filtering: Disabled Advanced Filtering: Disabled The ignition is DUMMY type. The ignition outputs are set to 01..00 and invert driver output and dual output mode are disabled. One coil is nonnected on ec36-pin34, the other one is connected on ec36-pin36. The problem is that the ignition outputs are not firing as they should (I use the test function through VemsTune). Sometimes both coils fire together sometimes they don't fire at all. I belive the config file http://www.vems.hu/files/AutoVeltiosis/v3.3_n002710-2010.03.17-14.28.02.vemscfg should be checked and corrected. I found out that while I was trying to test the InjGroup 7 the shifter was activated. So the outputs are all messed up. I get the message OUTPUT COLLISIONS.
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.