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

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

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

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

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

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:
'''Misc output switched by battery voltage''' I would like at least one of the misc outputs to be switched based on battery voltage. Hysteresis (like the fan and water pump controllers have) on all parameters would be nice, but is very much not essential. This will enable "smart" alternator control - ie the field in the alternator can be switched off at high TPS and MAT (MAT or MAP?) as long as the battery voltage remains above a threshold. * Is it not dangerous to fiddle with alternator excitation at high power ? If the injector parameter batt_fac is not set correctly (too low), this can change mixture, possibly lean out. With such uncertainty, for safety, it might need richer tune than otherwise => the loss of performance due to fuel can be worse than the gain due to lower alternator input torque. * OEMs do it, so it can't be that difficult ;) We can PWM the alternator to control the battery voltage, so that over a number of load cells, the batt_fac parameter can be properly estimated. In reality, you'd never let too much of a drop in battery volts happen. All you're really trying to do is not dump loads of energy as heat from the alternator regulator. ---- '''PWM type output for controlling evaporative emissions (carbon can) solenoid''' This is discussed elsewhere on my pages [need to add link], and would allow the standard emissions control and tank vents to remain in the car. '''Some changes to improve knock control''' Will be discussed at much greater length when I am not at work! 1. Create table of knock reading to table (RPM vs MAP) of average knock readings from the last n seconds. (Probably easiest if this is a fading memory smoothing algorithm) * this is a very good idea. We plan to rip VE-learning from firmware (PC software like megalogviewer will still help in VE-learning, but with much better manual overview and control). Runtime knock-retard table would be more useful than simple retard-samevalue-everywhere. *good plan to remove VE learn. The ECU based system cannot ever get enough information to make good decisions - it can't see into the future - You can do better from datalogs and a clever datamining algorithm. 2. Use m*table_values as threshold for declaring knock 3. Retard timing as appropriate 4. Record table (again RPM vs MAP) of [average or max - not sure!] knock retard so that this can be used next time knock occurs, or simply as a tuning aid. ---- '''Dual WBO2 sensors''' This page is concerned with the firmware mods required to enable dual wideband lambdas for those of us with v8 engines with 2 cats. It would appear that dual WB02 is all done and dusted. I have fitted the "missing" resistors and capacitors to my Genboard. R137, R140, R28, R29 and C83 I used firmware 1.2.11 to test readings on the 2nd sensor out of the exhaust. All worked as expected. Firmware 1.2.13 should allow the 2nd wideband to control closed loop fuelling. This requires setting which injector bin belongs to each bank. Seeing as no VemsTune config was available, I hacked one together, using the LCD backlight byte setting as the ego bank control. The injectors are connected up in numbered order to the injector drivers, and the firing order is configured as 2-1-8-4-3-6-5-7 due to the position of the missing tooth on the trigger disc. I believe the ego bank uses firing order, so this means I need to set ego bank to 0x2D. By firing order: ||Injgroup||Cylinder||Ego bank|| ||0||2||1|| ||1||1||0|| ||2||8||1|| ||3||4||1|| ||4||3||0|| ||5||6||1|| ||6||5||0|| ||7||7||0|| * that is 0010 1101 (starting with bit7, as injgroup 7, ending with bit0 as injgroup 0, also coming last in the real sequence) * Can anyone confirm please? '''Cylinder numbering''' https://dl.dropboxusercontent.com/u/8968424/Firing_Order.jpg '''Mapping in VEMSTune configuration''' [placeholder] NB: VEMSTune screenshots will not show the ego bank selection in any detail because it is based on a hacked config file where a raw byte is specified. ----
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.