Speed Density 2.0 (3D VE Tables, Baro)
Feb 4, 2011, 11:15 PM
#1
Speed Density 2.0 (3D VE Tables, Baro)
Updates:
Updated the IAT scaling for the all roms
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:
94171715
96531706
88591715
Notes:
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
9417 Variant:
https://www.evolutionm.net/forums/at...d-94172715.bin
https://www.evolutionm.net/forums/at...d-94172715.zip
9563 Variant:
https://www.evolutionm.net/forums/at...d-96534706.bin
https://www.evolutionm.net/forums/at...d-96534706.zip
8859 Variant Rom:
https://www.evolutionm.net/forums/at...-tephramod.bin
https://www.evolutionm.net/forums/at...d-88592715.zip
XML Pack:
http://www.norcalmotorsports.org/use...OD-XMLPack.zip
Updated the IAT scaling for the all roms
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:
94171715
96531706
88591715
Notes:
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
9417 Variant:
https://www.evolutionm.net/forums/at...d-94172715.bin
https://www.evolutionm.net/forums/at...d-94172715.zip
9563 Variant:
https://www.evolutionm.net/forums/at...d-96534706.bin
https://www.evolutionm.net/forums/at...d-96534706.zip
8859 Variant Rom:
https://www.evolutionm.net/forums/at...-tephramod.bin
https://www.evolutionm.net/forums/at...d-88592715.zip
XML Pack:
http://www.norcalmotorsports.org/use...OD-XMLPack.zip
Last edited by RoadSpike; May 11, 2011 at 09:34 AM.
Feb 4, 2011, 11:16 PM
#2
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.
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.
The following users liked this post:
Ian0611 (Oct 15, 2019)
Feb 6, 2011, 10:32 AM
#7
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.
Here is what I wrote and how it looks.
https://www.evolutionm.net/forums/8622723-post108.html
The attachment is my code. I used the original MAP-VE table and the MAP calibration table. I used memory addresses 2F40 to 3300 to define my tables.
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.
Here is what I wrote and how it looks.
https://www.evolutionm.net/forums/8622723-post108.html
The attachment is my code. I used the original MAP-VE table and the MAP calibration table. I used memory addresses 2F40 to 3300 to define my tables.
Last edited by 03whitegsr; Feb 6, 2011 at 11:03 AM.
Trending Topics
Feb 16, 2011, 01:29 PM
#10
Account Disabled
Join Date: Jan 2008
Location: Phoenix,Az
Posts: 45
Likes: 0
Received 0 Likes
on
0 Posts
3D sd tuning
I am new to tuning the sd i have not yet done the sd conversion but will be doing so wit my fully built 2.1. How would u tune the 3D maps? kind of looks confusing.
Feb 16, 2011, 01:35 PM
#11
Evolved Member
iTrader: (12)
Join Date: Aug 2009
Location: ma
Posts: 1,589
Likes: 0
Received 0 Likes
on
0 Posts
You would bring your car to a professional tuner :P
Sorry for slacking on not testing the 9417 3D rom but Im waiting on my new iat to come in. The resistances to deg was off by alot from what it should be, Im thinking it wasnt a gm iat sensor.
Sorry for slacking on not testing the 9417 3D rom but Im waiting on my new iat to come in. The resistances to deg was off by alot from what it should be, Im thinking it wasnt a gm iat sensor.
Feb 16, 2011, 02:12 PM
#12
I guess i should hurry up and finish the latest iteration of the SD tuning patch too.
going to have 3 new tables replacing most of the patch
First a calibration table for the sensor voltage to kPa/psi
Secondly a kPa to Load table replacing the map volts to load as it is now
Lastly kPa vs RPM for VE instead of load
I figure if setup up right the only table that will really change is the sensor calibration table and all the rest of them will not.
I'm also working in the SD auto tune for the patch almost finished really everything's done expect a couple tables relating kPa to baro pressure. Should help with mountain top startups.
going to have 3 new tables replacing most of the patch
First a calibration table for the sensor voltage to kPa/psi
Secondly a kPa to Load table replacing the map volts to load as it is now
Lastly kPa vs RPM for VE instead of load
I figure if setup up right the only table that will really change is the sensor calibration table and all the rest of them will not.
I'm also working in the SD auto tune for the patch almost finished really everything's done expect a couple tables relating kPa to baro pressure. Should help with mountain top startups.
Feb 16, 2011, 02:49 PM
#13
I guess i should hurry up and finish the latest iteration of the SD tuning patch too.
going to have 3 new tables replacing most of the patch
First a calibration table for the sensor voltage to kPa/psi
Secondly a kPa to Load table replacing the map volts to load as it is now
Lastly kPa vs RPM for VE instead of load
I figure if setup up right the only table that will really change is the sensor calibration table and all the rest of them will not.
I'm also working in the SD auto tune for the patch almost finished really everything's done expect a couple tables relating kPa to baro pressure. Should help with mountain top startups.
going to have 3 new tables replacing most of the patch
First a calibration table for the sensor voltage to kPa/psi
Secondly a kPa to Load table replacing the map volts to load as it is now
Lastly kPa vs RPM for VE instead of load
I figure if setup up right the only table that will really change is the sensor calibration table and all the rest of them will not.
I'm also working in the SD auto tune for the patch almost finished really everything's done expect a couple tables relating kPa to baro pressure. Should help with mountain top startups.
