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

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

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

 _______ 
/ ___   )
\/   )  |
    /   )
   /   / 
  /   /  
 /   (_/\
(_______/
         

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

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:
'''FUTURE FIRMWARE FEATURE REQUESTS''' ---- '''ON/OFF VVT mapping under camshaft control''' I'm thinking it would be nice to be able to more accurately map even on/off style VVT by using the actual Camshaft Control tables under Motorsports group... but with a simple option of 0 and 1 (off and on) in the MAP/RPM table, and a '''non PWM option''' in the setup page. Right now using Misc 1 to control VANOS is just ok, but being able to map VANOS more like a stock ECU would be much, much better obviously. *Is this not already possible by selecting extreme ends of the angle range? I.e the cam is idle at 200° and advanced at 212° , so in the map you put in 190 for idle and 220° for advanced, the ecu will then simply switch on the single wire output in an attempt to achieve those targets? **Of course that requires camsync, so I do agree with Sacsha that 0/1 should be implemented, and the switch point is the perimiter value. i.e if 1 is at 3000rpm and 50% throttle, and next axis value is 3000rpm and 60% throttle and that value has a zero the switch point should be 50.1% and not 55% or 59.9% - GunnarReynisson ---- '''Fuel Pressure feedback & failsafe''' ** Using fuel pressure sensor to actively monitor and compensate for primary fueling (inj pw). Using this we can compensate for failing FPR (lost boost reference/clogged lines/etc) or weak/failing fuel pump(s) (especially on multi-pump scenario). Also useful for Ethanol trimming! **Also fault monitoring/threshold for boost reduction/check engine light/full ign/fuel cut if set threshold is passed (optional). **Similar to this implementation from Pro-EFI > http://www.spracingforum.com/forums/showthread.php?28-ProEFI-Fuel-Pressure-Compensation-Review-Video **And here on the AEM Infinity: https://www.youtube.com/watch?v=LkdEGeVWZgk ---- '''High Priority - Real Flex fuel control/strategies''' *Real inputs required and both types should be supported for flex fuel strategy: 0-5V for external controller (zeitronix for eg.) and a freq. input (can we use 3rd VR trigger instead of using up 2nd wheel speed?) for using a direct connection to a content analyzer. *When directly connected to freq. input, sensor is able to share content and fuel temp and failure mode: **'''Flex Fuel FCS Output''' The frequency of the signal indicates the ethanol percentage. The output frequency is linear with respect to the percentage of ethanol content in the fuel. The fuel composition sensor normally operates between 50-150Hz, where 50Hz represents 0% ethanol and 150Hz represents 100% ethanol. If the output frequency goes up to 170Hz, the sensor has gone into a fail safe mode as it has indicated a fuel contamination such as methanol, water, salt, etc. ***The pulse width indicates the fuel temperature and normally operates between 1-5mS where 1mS indicates -40°C (-40°F) and 5mS indicates 125°C (257°F). Linear output! *Avoid the use of Anytrim - dedicated strategy is required here, for fuel, ignition and boost, accel, starting, etc. Currently no options for dealing with fuel contamination/failure mode of sensor (170 Hz), freezing measured content during WOT, etc. Dedicated page: http://www.vems.hu/wiki/index.php?page=GenBoard%2FVerThree%2FFlexFuel ---- '''Basic CAN output interface''' Just basic programmable output/bus for driving more modern OEM dashes/cluster for basic info, speed, RPM, temperatures, etc. This is a big hindrance currently where VEMS need to be serious about for newer vehicle integration. ----
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.