TephraMod V7
TephraMod V7-PheNem/l2r99gst/recompile modified
USDM Evo IX
Option 1 88590715 (v7) - Download
Option 2 - Thanks to recompile 88590715 (v7 + Mods) - Download | Mirror
EvoScan XML Data to add:
USDM Evo IX
Option 1 88590715 (v7) - Download
Option 2 - Thanks to recompile 88590715 (v7 + Mods) - Download | Mirror
- Setup for JDM MAP and PSI based boost control (mrfred)
- WGDC Correction Interval set to 1 (Stock = 10)
- Max Total Upward WGDC Correction @ 100% TPS set to 0 (Stock = 10)
- EGR System Disabled (mrfred)
- Max Timing Retard set to -20 degrees (tephra)
- FAA bit.10 disabled ("weird unknown" timing pull at cruise)
- FAA bit.09 disabled (cat-warmup ignition retard)
- FBA bit.00 disabled (lean spool)
- FCA bit.09 disabled (EGR Test)
- OBD Inspection set to Pass all tests (acamus)
- Rear O2 Heater patch applied (mrfred)
- Fuel Cut Load Limit x2 and set to 300 (mrfred)
EvoScan XML Data to add:
Code:
<DataListItem DataLog="Y" Color="" Display="Gear" LogReference="Gear" RequestID="40" Eval="x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="5" Visible="False" /> <DataListItem DataLog="Y" Color="" Display="RPM_SPEED_RATIO_AVERAGE" LogReference="RPM_SPEED_RATIO_AVERAGE" RequestID="42" RequestID2="43" Eval="x/36.37" Unit="rpm/kph" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> <DataListItem DataLog="Y" Color="" Display="Airflow Rate gm/s" LogReference="gmas" RequestID="00" RequestID2="01" Eval="x*0.0236" Unit="gm/s" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="10000" ChartMin="0" ChartMax="10000" ScalingFactor="1" Notes="" Priority="4" Visible="False" /> <DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.3*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="Displays state of the throttle. High voltage or % value means a more open throttle. When logging engine activity (especially on the dyno), it is useful to log throttle position. This makes it easy to see when a power run begins and ends i.e. when the driver's foot is depressing the accelerator fully. Some mitsubishis show up to 20% when your foot is off the accelerator, and will show a max of 90-99% when your foot is fully applied, this is normal.
" Priority="1" Visible="False" /> <DataListItem DataLog="Y" Color="" Display="Airflow 2Byte" LogReference="AirFlow2Byte" RequestID="02" RequestID2="03" Eval="6.29*x/64" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="3000" ChartMin="0" ChartMax="2500" ScalingFactor="0.1" Notes="" Priority="4" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Airflow Rate lb/min" LogReference="lbamin" RequestID="00" RequestID2="01" Eval="0.00312*x" Unit="lb/min" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="10000" ChartMin="0" ChartMax="10000" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Mileage Gasoline" LogReference="mpg" RequestID="CALC" Eval="5.9*[Speed]*[AFRMAP]/[lbamin]" Unit="mpg" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="10000" ChartMin="0" ChartMax="10000" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Mileage E85" LogReference="mpge" RequestID="CALC" Eval="4.18*[Speed]*[AFRMAP]/[lbamin]" Unit="mpg" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="10000" ChartMin="0" ChartMax="10000" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> Omni 4-Bar MAP <DataListItem DataLog="Y" Color="" Display="OMNI MAP" LogReference="OMNIMAP" RequestID="38" Eval="0.2369*x-14.7" Unit="psig" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-15" GaugeMax="35" ChartMin="-15" ChartMax="35" ScalingFactor="1" Notes=""/>
Thanks for cleaning up the XML! Also, for any of you who ran into the same issue with being unable to see and change some of the tables when I downloaded from this link. The recompile XML (TephraMOD-88590715-v7) on this download was not including the 88590015_r3compile_20091010 XML. You just need to include it by pasting this onto the TephraMOD-88590715-V7 XML "<include>88590015_r3compile_20091010</include>" without the ", I attached the fixed XML file. Thanks again to the people who were involved! 
Doesn't the recompile rom also have the rear O2 heater disabled? You may want to note that.
Also, it looked like he applied the mrfred airflow calc patch, but I believe it was already applied to the v7 rom already. I can't confirm that one since I don't use it, but I thought I saw it added.
Lastly, make sure the 2 JDM Map values are corrected that I posted about earlier.
Also, it looked like he applied the mrfred airflow calc patch, but I believe it was already applied to the v7 rom already. I can't confirm that one since I don't use it, but I thought I saw it added.
Lastly, make sure the 2 JDM Map values are corrected that I posted about earlier.
There is NO POINT in leaving ANY tables in there that are not used in certain patched roms,completely pointless. Why have us waste the time adding tables that you couldn't even use with that patched ROM anyways? If someone confirms that we NEED the MAF tables for tuning with SD (I can't see why since they'd create SD tables to do all of it) than I'll leave them in.
There are 4 ROM versions,
MAF ---------------------->(96530706)
MAF +Live Mapping -->(96531706)
SD ------------------------>(96532706)
SD+ Live Mapping ---->(96533706)
Each version will only show the tables that pertain to the mods it has in it. There would be no point to have SD stuff in a ROM setup for MAF, ya know? Not like that ROM ID will EVER use SD since they created a ROM ID specifically for it.
There are 4 ROM versions,
MAF ---------------------->(96530706)
MAF +Live Mapping -->(96531706)
SD ------------------------>(96532706)
SD+ Live Mapping ---->(96533706)
Each version will only show the tables that pertain to the mods it has in it. There would be no point to have SD stuff in a ROM setup for MAF, ya know? Not like that ROM ID will EVER use SD since they created a ROM ID specifically for it.
Preconfigured MUT Requests
MUT00+MUT01 = 2byte airflow (ie MrFreds mod in g/s or lb/min)
MUT02+MUT03 = 2byte airflow (ie MAFHz)
MUT40 = 1byte gear
MUT41 = 1byte load
MUT42+MUT43 = 2byte SPEED/RPM ratio (to get your gear ratios correct - if you need to)
2byte load AND 2byte RPM are no longer included and IMHO not needed!
MUT00+MUT01 = 2byte airflow (ie MrFreds mod in g/s or lb/min)
MUT02+MUT03 = 2byte airflow (ie MAFHz)
MUT40 = 1byte gear
MUT41 = 1byte load
MUT42+MUT43 = 2byte SPEED/RPM ratio (to get your gear ratios correct - if you need to)
2byte load AND 2byte RPM are no longer included and IMHO not needed!
I'm not up to speed on all the new MUT requests.
Doesn't the recompile rom also have the rear O2 heater disabled? You may want to note that.
Also, it looked like he applied the mrfred airflow calc patch, but I believe it was already applied to the v7 rom already. I can't confirm that one since I don't use it, but I thought I saw it added.
Lastly, make sure the 2 JDM Map values are corrected that I posted about earlier.
Also, it looked like he applied the mrfred airflow calc patch, but I believe it was already applied to the v7 rom already. I can't confirm that one since I don't use it, but I thought I saw it added.
Lastly, make sure the 2 JDM Map values are corrected that I posted about earlier.
There is NO POINT in leaving ANY tables in there that are not used in certain patched roms,completely pointless. Why have us waste the time adding tables that you couldn't even use with that patched ROM anyways? If someone confirms that we NEED the MAF tables for tuning with SD (I can't see why since they'd create SD tables to do all of it) than I'll leave them in.
There are 4 ROM versions,
MAF ---------------------->(96530706)
MAF +Live Mapping -->(96531706)
SD ------------------------>(96532706)
SD+ Live Mapping ---->(96533706)
Each version will only show the tables that pertain to the mods it has in it. There would be no point to have SD stuff in a ROM setup for MAF, ya know? Not like that ROM ID will EVER use SD since they created a ROM ID specifically for it.
There are 4 ROM versions,
MAF ---------------------->(96530706)
MAF +Live Mapping -->(96531706)
SD ------------------------>(96532706)
SD+ Live Mapping ---->(96533706)
Each version will only show the tables that pertain to the mods it has in it. There would be no point to have SD stuff in a ROM setup for MAF, ya know? Not like that ROM ID will EVER use SD since they created a ROM ID specifically for it.
Here's the Recompile 88590715 XML minus all the Acamus OBDII stuff (rear o2, egr disable) and I removed the Airflow calc patch as well. This is how I wanted it just figured I'd post it up in case anyone else does...
So, I just finished up doing an "install" lap around the block. Everything is perfect, except for WOT shifts. I have NLTS and Launch Maps disabled to ensure that nothing silly happens while driving. During a WOT shift the car will stumble/misfire/jerk, whatever you want to call it, and then pick up. This only happens for a split second when getting back on the gas(WOT) during/after a shift.
I haven't changed any of my maps or anything else major. I'm wondering if it could be the "WGDC 100% under this load" table or something else new that I haven't really messed with. I have that set to 200 load...anybody else? Other than that issue, which I'm sure is something that I overlooked, the v7 is perfect and flawless. I have to play with the gear boost control a little also. V7 definitely rocks though!
I haven't changed any of my maps or anything else major. I'm wondering if it could be the "WGDC 100% under this load" table or something else new that I haven't really messed with. I have that set to 200 load...anybody else? Other than that issue, which I'm sure is something that I overlooked, the v7 is perfect and flawless. I have to play with the gear boost control a little also. V7 definitely rocks though!
So, I just finished up doing an "install" lap around the block. Everything is perfect, except for WOT shifts. I have NLTS and Launch Maps disabled to ensure that nothing silly happens while driving. During a WOT shift the car will stumble/misfire/jerk, whatever you want to call it, and then pick up. This only happens for a split second when getting back on the gas(WOT) during/after a shift.
I haven't changed any of my maps or anything else major. I'm wondering if it could be the "WGDC 100% under this load" table or something else new that I haven't really messed with. I have that set to 200 load...anybody else? Other than that issue, which I'm sure is something that I overlooked, the v7 is perfect and flawless. I have to play with the gear boost control a little also. V7 definitely rocks though!
I haven't changed any of my maps or anything else major. I'm wondering if it could be the "WGDC 100% under this load" table or something else new that I haven't really messed with. I have that set to 200 load...anybody else? Other than that issue, which I'm sure is something that I overlooked, the v7 is perfect and flawless. I have to play with the gear boost control a little also. V7 definitely rocks though!
Speed density wasn't created with only ONE method of tuning it. If you need examples here you go. https://www.evolutionm.net/forums/ec...irst-test.html Basically it allows the tuning process to be done by setting MAP and RPM VE tables to be 1:1 which in some circumstances makes it easier especially when you don't have any maf logs. I was just providing you with some feedback because you asked about it. And as far as the livemap tables for MAF comp + scaling I was asking if it was possible because it would be an asset.
So....from that thread, it looks like I can just add the MAF Scaling and MAF smoothing tables in the SD.xml shown in the 'Speed Density Tuning' section with the MAFHz and Percent(128) scaling pre-loaded. Or did someone create a table that incorporates MAF Scaling/MAF smoothing into one table already?
So from that thread, it looks like the MAT temps really throw the load values off a lot. I thought the point of using the MAT signal was to compensate for MAT temperature changes so the load will stay the same regardless of MAT temps (like factory)???
So I was comparing my two XMLs (95630006 v5.10 and 96530706 - phenem v7) and I noticed that my "MAF Sensor Filtering" addresses are different.
v5.10 has:
1500 being "Injector Latency Base"
1508 being "MAF Sensor Filtering"
v7 has:
1500 being "Injector Latency Base" AND "MAF Sensor Filtering"
I'm guessing this is an error. 1508 should still be "MAF Sensor Filtering", correct?
I only notice because I'm running a 2g MAF and I'm seeing if porting all the MAF setting over from the DSM roms will make my readings more consistent. My tune is very sensitive to the weather and I think that changing some of the evo MAF correction maps over to 2g MAF correction maps may help. -- But that's for another thread -- on DSMTuners.
v5.10 has:
1500 being "Injector Latency Base"
1508 being "MAF Sensor Filtering"
v7 has:
1500 being "Injector Latency Base" AND "MAF Sensor Filtering"
I'm guessing this is an error. 1508 should still be "MAF Sensor Filtering", correct?
I only notice because I'm running a 2g MAF and I'm seeing if porting all the MAF setting over from the DSM roms will make my readings more consistent. My tune is very sensitive to the weather and I think that changing some of the evo MAF correction maps over to 2g MAF correction maps may help. -- But that's for another thread -- on DSMTuners.
Last edited by knochgoon24; Oct 22, 2009 at 05:39 PM.





