How To: Speed Density on the evo8 using tephra v7/Phenem pre-patched roms
Newbie
Joined: Mar 2010
Posts: 1
Likes: 0
From: USA
Hi guys i am new here especially on this field of ecuflash ,but if any can help me on this doubt this kind of patch used for Evo 8 We can used on a eclipse turbo ECU 2g ? Or any one know if exist a patch specific for the eclipse ecuflash.
thank you
thank you
This write up is the main reason I did ventured over to speed density. From installing the harness(SpoolinUp) to tuning/tweaking the rom the car is night and day. So smooth transitioning from cell to cell and from closed to open. It's no longer jagged and rough. Stop and go traffic is not a pain.
I would add the xml for evoscan/mitsulogger for logging MAT in this thread. It took me almost 1 day to find with this wonderful search engine lol (mrfred's inbox is a lost cause lol)
Another thing I did was the ALT-G for graphs on 2D maps. I made sure transitions were smooth for VE's to the Asynch TPS.
One of the best and thorough write ups on EvoM.
I would add the xml for evoscan/mitsulogger for logging MAT in this thread. It took me almost 1 day to find with this wonderful search engine lol (mrfred's inbox is a lost cause lol)
Another thing I did was the ALT-G for graphs on 2D maps. I made sure transitions were smooth for VE's to the Asynch TPS.
One of the best and thorough write ups on EvoM.
Newbie
Joined: Sep 2005
Posts: 43
Likes: 0
From: Haverhill, MA
Step 3b, MAP Sensor Selection:
This rom has no scaling tables for the MAP sensor and is setup for the JDM/EvoX 3bar MAP sensor by default. If you are using a different MAP sensor, you need to change the scaling on a few tables from 'PSIa8 JDM3barMAP' to 'PSIa8 OMNI4barMAP', or the preset for your specific MAP sensor. Right-click on the map/table in the left column of EcuFlash and select Edit, and pick the appropriate scaling from the drop-down menu.
- Alternate Boost Desired Engine 'PSI' : PSIa8 JDM3barMAP -> PSIa8 OMNI4barMAP
- Boost Error Correction (PSI) : BoostErrorPsi JDM3barMAP -> BoostErrorPsi OMNI4barMAP
- Boost Desired Engine 'PSI' : PSIa8 JDM3barMAP -> PSIa8 OMNI4barMAP
- Boost Adder (PSI) : PSIa16 JDM3barMAP -> PSIa16 OMNI4barMAP
NOTE: I tried keeping XML editing out of this post, but for now, it needs to be done if you are using anything other than the JDM/EvoX 3.3 bar map sensor. There are different scalings for MAP kPa based on which sensor you use. You can choose to use these or not. I HIGHLY recommend updating the MAP kPa scaling in c:\Program Files\EcuFlash\rommetadata\mitsubishi\evo\96531706 .xml based on mr. fred's values here: https://www.evolutionm.net/forums/6744341-post2.html
- Alternate Boost Desired Engine 'PSI' : PSIa8 JDM3barMAP -> PSIa8 OMNI4barMAP
- Boost Error Correction (PSI) : BoostErrorPsi JDM3barMAP -> BoostErrorPsi OMNI4barMAP
- Boost Desired Engine 'PSI' : PSIa8 JDM3barMAP -> PSIa8 OMNI4barMAP
- Boost Adder (PSI) : PSIa16 JDM3barMAP -> PSIa16 OMNI4barMAP
As well as "SD MAP Sensor VE and Calibration" to use "kPa Kavlico3.5barMAP". Are there further changes that need to be done?
by 'SD MAP Sensor VE and Calibration" what do you mean? The scaling? You need to make sure to update the scaling for 'MAP 16bit' for your 3.5bar, then you're good to go. This is the most common stumbling point, just make sure you get it changed, save, close, re-open and you're done....well, with that step anyways 
Newbie
Joined: Sep 2005
Posts: 43
Likes: 0
From: Haverhill, MA
by 'SD MAP Sensor VE and Calibration" what do you mean? The scaling? You need to make sure to update the scaling for 'MAP 16bit' for your 3.5bar, then you're good to go. This is the most common stumbling point, just make sure you get it changed, save, close, re-open and you're done....well, with that step anyways
Newbie
Joined: Sep 2005
Posts: 43
Likes: 0
From: Haverhill, MA
I'm not sure. My life is a bit of a mess right now (https://www.evolutionm.net/forums/ev...nd-my-vag.html) if anyone else has any ideas, please let me know. Otherwise I'll have to look into this when I can.
Newbie
Joined: Sep 2005
Posts: 43
Likes: 0
From: Haverhill, MA
I'm not sure. My life is a bit of a mess right now (https://www.evolutionm.net/forums/ev...nd-my-vag.html) if anyone else has any ideas, please let me know. Otherwise I'll have to look into this when I can.
Understand that the speed density patch works off of a 10bit target X where x is a voltage reading and not really a unit of kPa. Therefore when a different sensor is used a different scaling is used to re point the target X to a different location but essentially the kPa of the sensors remain around the same spot for the most part
.
few stupid questions. im converting and changing everything over.. what tables do i need to change for MAP scaling i dont see any there? same with boost control/limits
running omni 4 bar
running omni 4 bar
I want to clear something up and make sure I'm going about step 3b correctly since it's not exactly clear to me. The car has run decent w/o changing from Map VE Load to Map 16bit and I want to make sure I'm going about this correctly.
- I've updated my Map 16-bit values in the XML to reflect Mrfred's values for OMNI 4-bar (below):
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.4072" frexpr="x/0.4072" format="%.1f" min="0" max="450" inc="0.4072" storagetype="uint16" endian="big"/>
-Do I change the scaling for "SD Map Sensor VE & Calibration" from Map VE Load to Map 16-bit (images below)?
- If I do change the scaling to Map 16bit, the values should look skewed, correct ?(another image below)
-Should I set the kPa values that changed to be a closer match to the values in the MAP(kpa) column? I set them back to 1:1 for display purposes (image below)
- I've updated my Map 16-bit values in the XML to reflect Mrfred's values for OMNI 4-bar (below):
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.4072" frexpr="x/0.4072" format="%.1f" min="0" max="450" inc="0.4072" storagetype="uint16" endian="big"/>
-Do I change the scaling for "SD Map Sensor VE & Calibration" from Map VE Load to Map 16-bit (images below)?
- If I do change the scaling to Map 16bit, the values should look skewed, correct ?(another image below)
-Should I set the kPa values that changed to be a closer match to the values in the MAP(kpa) column? I set them back to 1:1 for display purposes (image below)