How To: Speed Density on the evo8 using tephra v7/Phenem pre-patched roms
Evolving Member
Joined: Dec 2005
Posts: 419
Likes: 0
From: Bristol, England
Has anyone had the issue with 9417 SD where on a cold start, it'll fire right up and idle perfect, then shut off 15-20 seconds later? Once you start it after dying, it will not idle on its own for 2 minutes or so once semi warm. Also die right away from free rev.
I played with the Post Primer Enrich Decay in the problem area's where its cold but really didn't do anything.
I'm trying to see if I can fix this on my own before Tom has some time and fixes it with his eyes closed once we actually tune my car...
I played with the Post Primer Enrich Decay in the problem area's where its cold but really didn't do anything.
I'm trying to see if I can fix this on my own before Tom has some time and fixes it with his eyes closed once we actually tune my car...
Last edited by tscompusa; Dec 11, 2012 at 03:42 PM.
Can someone correct me if I am wrong on my understanding of how to tweak the ve tables to match my maf rom?
If you're running less than 36psig (350kpa), do you need to alter the map ve tables to get your afr's and timing to match my current rom? My understanding of the map ve table is that it is a tool alter the resolution of the map if your load exceed's the map's range.
So if my current configuration keeps me within the original range, the main table I should be concerned with in getting my afr's in line with the current tune is the rpm ve, and possibly asynch_vs_tpsdelta? Keep the map ve at a 1:1?
I played with the idle some tonight to get the o2 feedback within +/- 2%, as well as up to 2.5k, before switching back to my maf V7 rom. I plan on doing some crusie logging tomorrow afternoon to begin testing that portion of the conversion.
***EDIT: After further reading and playing around with the tables I have answered my own question and have a better understanding of how it works.
If you're running less than 36psig (350kpa), do you need to alter the map ve tables to get your afr's and timing to match my current rom? My understanding of the map ve table is that it is a tool alter the resolution of the map if your load exceed's the map's range.
So if my current configuration keeps me within the original range, the main table I should be concerned with in getting my afr's in line with the current tune is the rpm ve, and possibly asynch_vs_tpsdelta? Keep the map ve at a 1:1?
I played with the idle some tonight to get the o2 feedback within +/- 2%, as well as up to 2.5k, before switching back to my maf V7 rom. I plan on doing some crusie logging tomorrow afternoon to begin testing that portion of the conversion.
***EDIT: After further reading and playing around with the tables I have answered my own question and have a better understanding of how it works.
Last edited by ReaperX; Dec 14, 2012 at 07:16 AM.
Newbie
Joined: Feb 2010
Posts: 15
Likes: 0
From: Russia
Please share the settings for Omni 4 bar, GM IAT:
1. SD MAP Sensor VE and Calibration
2. SD IAT ADC Scaling
The air temperature sensor installed in the inlet GM Connections connector MAF.
selected SD Option: IAT Input for MAT - 0x03
The temperature in Evosсan shows - MUT11 - 1.8x-40
As the temperature change in the inlet, AFR floats. Oxygen Feedback varies from -10 to +10 depending on the temperature ...
That i will not it? Why is this happening?
1. SD MAP Sensor VE and Calibration
2. SD IAT ADC Scaling
The air temperature sensor installed in the inlet GM Connections connector MAF.
selected SD Option: IAT Input for MAT - 0x03
The temperature in Evosсan shows - MUT11 - 1.8x-40
As the temperature change in the inlet, AFR floats. Oxygen Feedback varies from -10 to +10 depending on the temperature ...
That i will not it? Why is this happening?
Last edited by Mr.Nik; Feb 21, 2013 at 12:25 AM.
Evolved Member
Joined: May 2010
Posts: 500
Likes: 4
From: Australia
Does anyone know what the following fields should be set to (what voltages) when using the GM 3 bar map sensor?
I can only find values for omni 4 bar and zeitronix and I am trying to get SD running on my JDM 8. It's not running right since 96534706 is preconfigured for omni 4 bar but not sure what I have to change to make it work with my map sensor. Car runs ok in vacuum but wont boost over gate pressure.
For example:
I need these but for GM 3 bar. There may be other values I need to change too, I don't know which ones though and I can't find anywhere that explains it.
I can only find values for omni 4 bar and zeitronix and I am trying to get SD running on my JDM 8. It's not running right since 96534706 is preconfigured for omni 4 bar but not sure what I have to change to make it work with my map sensor. Car runs ok in vacuum but wont boost over gate pressure.
For example:
Zeitronix 5Bar settings:
Map test 1: Mid VE max voltage = 4.90
Map test 1: Mid VE min voltage = 0.10
Map test 2: Low VE Max Voltage = 4.90
Map test 3: High VE Min Voltage = 0.51
Map test 4: Max minus Min = 0.51
Map test 1: Mid VE max voltage = 4.90
Map test 1: Mid VE min voltage = 0.10
Map test 2: Low VE Max Voltage = 4.90
Map test 3: High VE Min Voltage = 0.51
Map test 4: Max minus Min = 0.51
Step 4c: drive the car, no boost!
If your car is going to stay in closed loop (like mine and most cars are) drive the car around with no boost. Take this time to admire how awesomely smooth speed density makes the car, and how thankful you are to everyone mentioned above and all of their hard work for making your evo drive so nicely. Watch your AFRs, o2 feedback, and LTFT Mid. I spent a few days driving back and forth to work tweaking MAP VE and RPM VE to get the car to cold start nicely, drive nicely, and keep LTFT's in check. This is not unlike dialing in a new set of injectors, if your LTFT is a bit negative, lower the appropriate RPM VE and/or raise your MAP VE values a few % at a time to bring them back in line. If the LTFT is positive, raise RPM VE and/or lower MAP VE.
(can someone double check this for me? pretty sure this is how I remember it!)
It goes that way:
LTFT negative = too much fuel, so you have to lower RPM VE and/or lower MAP VE.
LTFT positive = not enough fuel, so you have to raise RPM VE and/or raise MAP VE.
And to help understand how SD works, I would add a simple explanation. It may sound simple for some, but it would've helped me when I started the tuning process.
RPM VE is only a horizontal load multiplier
MAP VE is only a vertical load multiplier
(but it's scaled as kpa vs load instead of kpa vs multiplier %. )
That's the way I understand it.
I.E. if you multiply RPM VE by 2, and divide MAP VE by 2 for all axis, the car would follow exactly the same load curve:
In other words: Load = MAPVE(%) * RPMVE(%) * MAT compensation * Baro * Base load * Whatever other compensations
RPM VE is only a horizontal load multiplier
MAP VE is only a vertical load multiplier
(but it's scaled as kpa vs load instead of kpa vs multiplier %. )
That's the way I understand it.
I.E. if you multiply RPM VE by 2, and divide MAP VE by 2 for all axis, the car would follow exactly the same load curve:
In other words: Load = MAPVE(%) * RPMVE(%) * MAT compensation * Baro * Base load * Whatever other compensations
Last edited by domyz; Jun 11, 2013 at 06:45 AM.
Evolving Member
Joined: Jan 2010
Posts: 233
Likes: 0
From: Italy
i don't understand this dear domyz.
From what i understand sd rpm ve set the amount of fuel in a certain rpm and you have to make it closest to 0 looking stft,
And sd map sensor ve set the load correlated to how much pressure (kpa/psi) map sensor measure to re-create the old maf-load curve.
Isn't right?
From what i understand sd rpm ve set the amount of fuel in a certain rpm and you have to make it closest to 0 looking stft,
And sd map sensor ve set the load correlated to how much pressure (kpa/psi) map sensor measure to re-create the old maf-load curve.
Isn't right?
Again, like setting up tephramod v7, information is on the website but spread all around.
First of all, your understanding of SD is a little bit off because you read the phenem how-to which is I think, lacking some important details.. it's at least skipping some basics.
You also need to play with MAPVE to get the trims in check. If you read the how to and don't think further than it, you'll end up with a thinking a bit off target. (Not saying that the how-to is wrong)
Old maf-load curve is in fact a curve which has RPM and MAP on X-Y axis. You need to play with both to imitate the old curve perfectly. Look at this advice by Jamie@Dynotech. It's THE EASIEST way to start tuning speed density,
Jamie is a great ressource about this.(and more)
I will make myself more clear in a few days. I will post more basics about SD. I haven't a big experience with it, but I think I can gather information and popularise it a little bit more. After countless reading on it, I can tell you it's simplier than it looks.
You also need to play with MAPVE to get the trims in check. If you read the how to and don't think further than it, you'll end up with a thinking a bit off target. (Not saying that the how-to is wrong)
Jamie is a great ressource about this.(and more)
I will make myself more clear in a few days. I will post more basics about SD. I haven't a big experience with it, but I think I can gather information and popularise it a little bit more. After countless reading on it, I can tell you it's simplier than it looks.
Last edited by domyz; Jun 20, 2013 at 12:30 AM.
I'm having a issue with rom 94171715. Ive loaded the SD tune and have it idling well and drives ok. But if I disconnect the MAF it goes to hell. Like its still using the MAF, any suggestions?
