how does the "SD MAP Sensor VE and Calibration" table work?
#1
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
how does the "SD MAP Sensor VE and Calibration" table work?
I'm playing around with the "SD MAP Sensor VE and Calibration" table so i can adjust how the car moves across the maps(what sort of pressure is needed to hit specific load points)
also, ive got an OP 4bar MAP sensor on the car, and Ive added in the code and made the needed adjustments.
but my question is, this SD MAP Sensor VE and Calibration table references some KPa number to make up its load number. Is it pulling this directly from the MAP sensor, or calculating it?
When i convert my MAP PSI to KPA at a point, the load number doesn't line up but when i look at the "Boost (MAP)" in EVOScan, everything lines up.
do i need to change the formula in that item to the same one i'm using for logging the 4bar?....the more i think about it, the more of a stupid question this seems but verification is never a bad thing!
also, ive got an OP 4bar MAP sensor on the car, and Ive added in the code and made the needed adjustments.
but my question is, this SD MAP Sensor VE and Calibration table references some KPa number to make up its load number. Is it pulling this directly from the MAP sensor, or calculating it?
When i convert my MAP PSI to KPA at a point, the load number doesn't line up but when i look at the "Boost (MAP)" in EVOScan, everything lines up.
do i need to change the formula in that item to the same one i'm using for logging the 4bar?....the more i think about it, the more of a stupid question this seems but verification is never a bad thing!
#3
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
Any idea as to why load would reset mid pull? Ive set the 1byte correction factor to 2.0 feom 1.2 and its still does it......soooo lost!
#5
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
Any chance you can fill me in on how to do that? Like how i convert back to 2byte with a tephra ecu?? Wont yoy be limited to 160 like stock ecu?
Better yet, and yes i know its easter, any chance i could spend 10min on the phone with you? Id absolutely pay you for your time.
I've got that question to ask, and im looking for more info on min IPW control. Its a strech, but always woth asking!!
#6
Evolved Member
iTrader: (30)
2 byte-
https://www.evolutionm.net/forums/ec...te-thread.html
Min IPW-
https://www.evolutionm.net/forums/ec...nimum-ipw.html
Shouldnt need to play with min IPW even if you are on 2150s though. Cant talk today, possibly tomorrow.
https://www.evolutionm.net/forums/ec...te-thread.html
Min IPW-
https://www.evolutionm.net/forums/ec...nimum-ipw.html
Shouldnt need to play with min IPW even if you are on 2150s though. Cant talk today, possibly tomorrow.
#7
Former Sponsor
iTrader: (31)
as far as 1byte load resetting.. you set "2byte to 1byte Load Factor" the same as your evoscan equation and the problem never appears again.
IE.. 1.4 = 1.4x255 = covers up to 357 load..
keep adding more load factor and you keep raising the load threshold..
also if you ever log a car on v5 then v7 .. 2byte vs 1byte you will see that you get 2-3x more data with v7 big maps and 1byte load.
Trending Topics
#8
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
I can promise you that i set the load factor to 2.0 in both evoscan and the tune file at the end of the night and it did the same thing.
if you look at my actual thread on it i posted up another screenshot from last night.
if you look at my actual thread on it i posted up another screenshot from last night.
#10
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
I know ive got the scaling factor set to 2.0 and it still does this nonsence!
as you can see better here....
https://www.evolutionm.net/forums/at...loadissue2.jpg
even if the correction factor was stock (1.2) it wouldn't reset until 306%
attached is screenshot of the table just so you can see the axis.
would you be willing to look over the tune file just to see if i am missing something here??
#12
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
whats so scary about the timing curve? the car doesn't knock a bit under WOT, and it has just a bit of transient KR (less then 2-3 counts) but with the fairly minimal cylinder pressures under those transient conditions I'm OK with it as i work towards dialing in the VE table and then refine the ign advance/ fuel maps.
the big batch of 10* is there so i can play with how the car moves across the load axis and not run into issues. I'm still very much dialing things in before i start doing power pulls.
As far as your fuel cut issue, I assume its not as Ive got the fuel cut multiplier set to '2x" and the fuel cut % table all set at 619%....I'm no where close to that load number.
stock motor, custom 62mm turbo, custom front facing manifold, custom IC, ID2k's, e85.
once I'm past this issue and can start making progress on the car Ive got a hell of a fuel system going on and then a built 2.4 sometime before September.
the big batch of 10* is there so i can play with how the car moves across the load axis and not run into issues. I'm still very much dialing things in before i start doing power pulls.
As far as your fuel cut issue, I assume its not as Ive got the fuel cut multiplier set to '2x" and the fuel cut % table all set at 619%....I'm no where close to that load number.
stock motor, custom 62mm turbo, custom front facing manifold, custom IC, ID2k's, e85.
once I'm past this issue and can start making progress on the car Ive got a hell of a fuel system going on and then a built 2.4 sometime before September.
#13
Evolving Member
Thread Starter
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
Daily Activity: 5.8%
I think ive found my issue.....
Is there a rom that has both the omnipower 4bar MAP sensor and 3D VE tables tested/verified on it?
for the 3D VE (by Roadspike) i only see these rom ID's
Speed Density 2.0 (3D VE Tables, Baro)
94171715
96531706
88591715
but none of those show up in the omnipower 4bar write up by mrfred
Omni 4 bar MAP sensor ROM compatibility settings for USDM Evo 8/9
he only worked with
94170008, 94170014, 94170015, 96420007, 96420008, 96940011, 88590013, 88590014, 8859001
HELP!
I think ive found my issue.....
Is there a rom that has both the omnipower 4bar MAP sensor and 3D VE tables tested/verified on it?
for the 3D VE (by Roadspike) i only see these rom ID's
Speed Density 2.0 (3D VE Tables, Baro)
94171715
96531706
88591715
but none of those show up in the omnipower 4bar write up by mrfred
Omni 4 bar MAP sensor ROM compatibility settings for USDM Evo 8/9
he only worked with
94170008, 94170014, 94170015, 96420007, 96420008, 96940011, 88590013, 88590014, 8859001
HELP!
#14
Former Sponsor
iTrader: (31)
dont use 3d just use the regular v7 SD.. 3d is buggy imo.. i stay away from 3d. https://www.evolutionm.net/forums/ec...hramod-v7.html
that timing map is asking for trouble.. im just saying.. start with a generic one.. what you did there is crazy.
that timing map is asking for trouble.. im just saying.. start with a generic one.. what you did there is crazy.
Last edited by tscompusa; Apr 9, 2012 at 06:23 PM.