Well hasn't this been a long time coming? Current roms are still in testing and being debated
Success in the patch for 3d VE maps however the persistant jitter bug still currently exists which I'm working on but likely will take a while to fix. Its more an annoyance than a real problem only happening on low loads cruising in certain situations which can if really needed driver choice avoided. It is assumed you have the xml's from the previous tephra v7 patches if not download them as marked here.
Current Roms I plan to patch:
I've given up on the live tuning thing as I can't really grasp how the patch and the program sync up. Since it seems to be easily done by other people I'm going to leave it up to those experts to patch in live tuning.
Testing nearly complete still need some more testing
Clearly some people are having trouble grasping this relatively simple patch so i'll just draw it out for them picture are worth a thousand words right?
As you should be able to tell the Map volts vs kpa should always be 1:1 so you don't screw up the other table axis. What will happen is you'll measure 40kpa or something and it wont match to the point on the table because its not aligned.
If you want to effect load you do that with the kPA vs Load table while this should have been obvious I guess its not.
Last edited by RoadSpike; May 11, 2011 at 09:29 AM.
Great work. I would suggest a new number for these roms though to prevent xml issues as this will represent a fairly significant change in tuning method.
96534706 and 96535706 for non-live tune and live tune version, respectively?
Also, as for an idea, I would highly suggest a slight break in the current methodology. Currently we try to make MAP pressure into Load using a xml scaling parameter that has to be adjusted depending on what MAP sensor you are using. This does a couple things all in one map.
First, obviously it allows various map sensors to be used, however it requires changing xml settings to make it happen. Second, it allows rescaling for engine displacement to take place. For example, if you go up to a 2.4L, you can simply increase VE in this map by 20% and it will compensate for it. Third, you tune MAP based VE by it.
My suggestion is break this map apart into separate functions. Use a MAP-Voltage table to program for different MAP sensors then there is no need to change xml scaling values depending on MAP sensor. This way, ANYBODY can simply take predetermined numbers for a given MAP sensor and plug them in and know that they will be in the ball park right away. Then include an engine displacement variable. Going from a 2.0L to a 2.4L? Simply type in 2.4 into the box and it is accounted for. The MAP VE is then taken care of completely in the 3D table. You could potentially do this for a fuel change as well. Putting in E85? Change this variable from 14.7 for gasoline to the appropriate AFR for stochiometric AFR of that fuel. This of course wouldn't change load, but you could use it as a nice little feature to adjust injector sizing.