How To: Speed Density on the evo8 using tephra v7/Phenem pre-patched roms - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community



How To: Speed Density on the evo8 using tephra v7/Phenem pre-patched roms

Reply
 
 
 
Thread Tools Search this Thread
Old Dec 16, 2009, 12:46 PM   #1
EvoM Moderator
Thread Starter
iTrader: (10)
 
scheides's Avatar
 
Join Date: Oct 2006
Location: Minneapolis
Posts: 4,826
Thanks: 0
Thanked 5 Times in 3 Posts

Drives: BeaterX

How To: Speed Density on the evo8 using tephra v7/Phenem pre-patched roms

scheides tested, ecu-guru approved! Still, be careful.
Also, it may (and likely will) change, I'll try and bump the thread with 'updated' as I do so...this is a work in progress!

Converting your evo8 to speed density is a lot easier than you might think! With the right tools, some time, and careful steps you'll be running MAF-Free in no time! I'll be using a lot of hyperlinks for reference points on material previously covered elsewhere. Make no mistake, speed density running on the stock ecu is a culmination of years worth of work by a lot of people around the world. Don't forget to thank them once you get it running properly: jcbanks, mrfred, JohnBradley, tephra, phenem, recompile, l2r99gst...to name a few.

First off, there's some hardware required. I HIGHLY recommend getting these going on your existing rom so you have a known good rom to easily flash back to while you are getting speed density going (in case you run into trouble and simply need to drive the car). Otherwise, swap the hardware below and read on!

Hardware Required:
  • Uprated MAP sensor: evoX 3.3bar or Omnipower 4.0 bar
  • Intake Air Temp sensor: GM IAT
  • Wideband O2 sensor: several are available, I use the Innovate LC-1 wired into the ecu


Step #1: A good running car with a safe tune on it.
Do a boost leak test, have a spare set of spark plugs handy (your existing ones may get fowled during this conversion process), fresh fluids, known-good boost levels, etc. If you car is in disrepair, take care of maintenance items before attempting this conversion; you will only be making it harder on yourself!

Step #2: Get a pre-patched rom from tephra/phenem:
https://www.evolutionm.net/forums/ec...hramod-v7.html
I used post #2, option 5, here's the direct link: Download

I used tephra v7 because it has all of the latest and greatest hacks in it, and this pre-patched rom has a LOT of work behind it to make what you're about to do much easier! Unpack the .zip file, put the 96531706-TephraMod-phenem-sd.bin file in a new folder somewhere called SpeedDensity. Put TephraMOD-96531706-v7.xml in C:\Program Files\EcuFlash\rommetadata\mitsubishi\evo\ and rename it 96531706.xml

Now launch ecuflash. Open the 96531706-TephraMod-phenem-sd.bin, make sure you can see some of the tables and that all is well. Hit save and call it 96531706-myspecialname-test1.bin (keep the original untouched so you have a local backup copy). Then load your existing rom off of your car or open a previously saved copy. You're ready for the dirty work.

Step 2a: light throttle cruise jitter (this may go away some day)
There is a very small issue with the existing speed density implementation that causes an ever-so-slight jitter while cruising around 2000-2500rpm. The final fix is still up in the air, but for now, I'm recommending mrfred's fix#2 since I've had the best luck with it. The XML is included in the pre-packaged rom, so simply find Fix2 or Fix3 under 'Speed Density Programming' and adjust the values per the mini directions.
  • Fix2: change 112 to 0
  • Fix3: change 8909 to 0009



Step 3: Copy *most* of the tables over from your old rom to the new rom.
I say *most* because there are some things set in this new rom that you're not going to want to mess with. The XML file that comes with these pre-patched roms does a good job detailing the periphery bits, so be careful which ones you copy over, and be careful which values you copy over in the MUT table. The ones that are key to getting this rom up and running on your car:
  • High/Low Octane Fuel and Timing tables (including rpm and load scaling values)
  • Injector scaling/latancy tables
  • Boost contrl/boost limit tables
  • MAF scaling (yes this does still have an effect)
  • MAP sensor scaling (scaling and xml here and here if you don't have this running already)
  • Immobilizer (or immob disable...if you car won't fire at all, this would be why)
  • ...
  • ...(any other suggestions?)


NOTE: This rom comes with BIG maps enabled. This is a mixed blessing; you now have a lot more resolution when tuning, but you'll have to get your existing table translated into big maps. A GREAT tool for this is this translator but don't just plug values in blindly, carefully double-check several rpm vs load cells and make sure they line up.


Step 3a, idle tables:
I left all of the stock values, save for desired idle RPM alone. To keep things simple, consider doing the same on your car, as SD idles amazingly well, even on a highly modified engine. You did a boost leak test, right?

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

Step Four, let's talk speed density!
There are two tables that will get a lot of your attention: SD MAP Sensor VE and SD RPM VE. These tables correlate pressure and speed with engine load (and thus fuel), and should be started at a 1:1 ratio like so:




Step 4a: SD RPM VE Table
The first table to play with will be SD RPM VE. (side note, starting here on a warm car may be advantagous). Start your car, leave it in neutral. Log wideband AFR and narrowband o2 feedback. If it is running extremely rich (like mine was), adjust values in the SD RPM VE table down in 5-10% increments until feedback is near zero and AFR is in the 14.7 range. Smooth the table from idle rpm areas up to boost areas (which are likely going to be just over 100%).

Once you have your idle or sub-2000rpm area dialed in and happy, push the throttle a bit and rev the engine up to 2500, 3000, and maybe 3500rpm and continue to monitor o2 feedback and wideband AFR.

As you do this process, got any check engine/service engine lights? Address them now. Once you drive the car on speed density you'll never wanna go back to a MAF

Step 4b: SD MAP VE Table
Again, log wideband AFR and narrowband o2 feedback. Put the car in gear, take off, in first, then grab second or maybe third gear. The car should drive pretty well with *feather* light throttle. NO BOOST! Now, tip in throttle a bit, maybe 25-35%, just enough to bring the car out of vacuum, mabye like 0-5psi. If your car is like mine, it will lean out a bit in this load range, and you'll need to lower the load% values that correlate to ~31-61kpa a bit to bring AFRs in line. I dropped mine about 8-10% for these light load cruising areas.

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!)

***EDIT***
Reduce MAP VE = LESS FUEL
Reduce RPM VE = LESS FUEL


Step 5: BOOST!
If you're smart, you will now turn down your boost. I started at wastegate pressure. Roll on the throttle, get the car into the main powerband area (typically 4000-6000rpm) and if you can, watch wideband AFR as you do this. You may now have to de-linearize the MAP VE and RPM VE tables. I started by bumping the top two values in MAP VE table up by about 15% per some existing tables that were posted and it landed me very near the desired AFR at WOT. Lowering and smoothing the RPM VE table in the 4000-8000rpm range dialed it in perfect. NOTE: Don't expect the values in your map to represent the actual desired AFR values, they are correlated but not equal.

Once you've verified that AFR is safe, time to turn the boost back up to where it was previously tuned at. Doing WOT pulls from low rpm, you want your timing numbers to line up with your previous tune. You can be as precise or rough as you like here, depending on what you have in mind. If you'd like to get your car running perfectly on your previous tune, you need to tweak the MAP VE and RPM VE tables until your car runs like it did when running the MAF. If you are about to do a full tune on the car, you can tweak the values a bit to make them smooth, and then simply begin tuning the timing table.

If you began with a tuned rom, chances are your VE tables may end up looking somewhat similar to mine:


Tuning notes from [email protected]:
Quote:
Originally Posted by JohnBradley View Post
It should be pointed out that as we play with the MAPVE and RPMVE the load will change for a given boost level. This can be used to play with the resolution if not on a V7 map.

i.e.- 29psi can be 300 load (depending on how long you take to play with it) to correlate to Kpa

29psi can also be 235 load and have a somewhat funky looking fuel map



Step6: drive the car, log, continue to monitor fuel trims, AFR and knock at WOT
This patch has not 100% proven to me that it is stable in all climate changes once it has been tuned. I'm sure its going to be close, but for now, plan on keeping an eye on things here and there, and if your car hasn't been professionally tuned, consider doing so!


Step 6a: tip-in/low rpm lean-out
A common problem that you may come across is the car wanting to run lean during initial TPS tip-in. For me, this occurred mostly at low rpm (1000-2000) and is induced while either lugging the car in traffic, or leaving from a stop. I found the solution by tweaking two tables: Asynch_vs_TPS (under global fueling) and your Fuel maps (don't forget the alt maps if you're using them). Bumping Asynch_vs_TPS by 10 units across the board is where I ended up, and richening up the AFR in areas around 80 load kpa from 1000-2250 a bit (with smoothing) made a world of difference for me.




Note: at this point, you can UNPLUG YOUR MAF sensor! You don' have to, but if you want to find a different intake setup to eliminate it from your intake tract, go for it!

Last edited by scheides; Oct 8, 2014 at 03:14 PM.
Offline
 
Reply With Quote
The Following 3 Users Say Thank You to scheides For This Useful Post:
Jayge91 (Sep 4, 2017), matthunter1448 (Mar 4, 2017), sandman121383 (Jun 8, 2017)
Old Dec 16, 2009, 12:50 PM   #2
Evolved Member
iTrader: (11)
 
mchuang's Avatar
 
Join Date: Sep 2005
Location: h town
Posts: 2,180
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2000 honda si turbo..sold 03' Rally Red BPU+

This is what I was waiting for before trying this. Thanks for this, now I must try.
Offline
 
Reply With Quote
Old Dec 16, 2009, 12:54 PM   #3
EvoM Moderator
Thread Starter
iTrader: (10)
 
scheides's Avatar
 
Join Date: Oct 2006
Location: Minneapolis
Posts: 4,826
Thanks: 0
Thanked 5 Times in 3 Posts

Drives: BeaterX

Sorry, I misspelled 'Phenem' in the subject. My bad. If a mod wouldn't mind fixing it, I'd appreciate it
Offline
 
Reply With Quote
Old Dec 16, 2009, 01:12 PM   #4
Account Disabled
 
Join Date: May 2008
Location: new york
Posts: 434
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: evo 9 mr

Quote:
Originally Posted by scheides View Post
Sorry, I misspelled 'Phenem' in the subject. My bad. If a mod wouldn't mind fixing it, I'd appreciate it
See your not perfect too...lol..can't wait to see u do this.
Offline
 
Reply With Quote
Old Dec 16, 2009, 01:22 PM   #5
Evolved Member
iTrader: (18)
 
Ev0ikon's Avatar
 
Join Date: Jan 2004
Location: 3rd Rock {from = sun}
Posts: 3,665
Thanked 7 Times in 7 Posts

Drives: Evo803Yello

Awesome!
Offline
 
Reply With Quote
Old Dec 16, 2009, 01:27 PM   #6
Former Sponsor
iTrader: (2)
 
Join Date: Sep 2009
Location: california
Posts: 189
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: evo

good write up lol
Offline
 
Reply With Quote
Old Dec 16, 2009, 02:09 PM   #7
Newbie
iTrader: (1)
 
pfunk47's Avatar
 
Join Date: Aug 2008
Location: Lansing, mi
Posts: 69
Thanked 0 Times in 0 Posts

Drives: 97 Ram, 03 Evo, 06 Montero, 14 X

Thanks for the write up, this will help a lot.

Last edited by pfunk47; Dec 16, 2009 at 04:19 PM.
Offline
 
Reply With Quote
Old Dec 16, 2009, 03:51 PM   #8
Evolved Member
iTrader: (3)
 
nonschlont's Avatar
 
Join Date: Mar 2007
Location: Ca
Posts: 1,759
Thanks: 0
Thanked 1 Time in 1 Post

Drives: 2011 WW gsr

Nice write up! Thanks for taking the time, to share the knowledge.
and to all of those who put in work on this... Pure Awesomeness!
Offline
 
Reply With Quote
Old Dec 16, 2009, 03:58 PM   #9
Account Disabled
iTrader: (9)
 
Join Date: Jan 2005
Location: :noitacoL
Posts: 1,762
Thanked 1 Time in 1 Post
stock ecu ftw
Offline
 
Reply With Quote
Old Dec 16, 2009, 04:09 PM   #10
Evolved Member
iTrader: (39)
 
phenem's Avatar
 
Join Date: Jul 2005
Location: Central PA
Posts: 811
Thanks: 0
Thanked 3 Times in 2 Posts

Drives: '03 Silver 2.3 EVO8, '07 Black Outlander XLS!

WOW! Did this need done! Great job man! Thanks for helping out, everything looks good as far as I can tell!

Scheides, if you want I can add the mrfred patch to the XML code and add fix2 and fix3 that way if fix3 is better we can take out Fix2 or vice versa? That way you can remove that from your directions and make it even easier!

P.S. - in your post you still spelled my alias wrong, hehe no worries
Offline
 
Reply With Quote
Old Dec 16, 2009, 04:30 PM   #11
Evolved Member
iTrader: (39)
 
phenem's Avatar
 
Join Date: Jul 2005
Location: Central PA
Posts: 811
Thanks: 0
Thanked 3 Times in 2 Posts

Drives: '03 Silver 2.3 EVO8, '07 Black Outlander XLS!

I would update your Async_vs_TPS from this post here: https://www.evolutionm.net/forums/7639720-post23.html

I don't know what table that is according to mrfred now, what address is that table you have?

mrfred completely re-did the names on most of the Async maps, so please update them according to the table here, pasted from post above for easy access:

Code:
<scaling name="TimeInjCranking" units="ms" toexpr="x*0.008" frexpr="x/0.008" format="%.1f" min="0" max="500" inc="1" storagetype="uint16" endian="big"/>
<table name="Cranking Primer Initial Pulse" category="Fuel" type="2D" level="2" scaling="TimeInjCranking" address="58d0">
  <table name="Coolant Temperature" type="Y Axis" elements="9" scaling="Temp" address="69d8"/>
</table>

<scaling name="TimeTCOMPCrankingHack" units="Approximate ms" toexpr="x*0.9" frexpr="x/0.9" format="%.1f" min="0" max="500" inc="1" storagetype="uint8" endian="big"/>
<table name="Initial Cranking IPW vs Coolant Temp" category="Fuel" address="5b3a" type="2D" level="2" scaling="TimeTCOMPCrankingHack">
  <table name="Engine Temp" address="69f4" type="Y Axis" elements="11" scaling="Temp"/>
</table>

<scaling name="Percent (128)" units="Percent (%)" toexpr="x/1.28" frexpr="x*1.28" format="%.0f" min="0" max="100" inc="1" storagetype="uint8" endian="big"/>
<table name="Cranking IPW Compensation vs Time" category="Fuel" type="2D" level="2" scaling="Percent (128)" address="382a">
  <table name="Time Since Engaging Starter (sec)" type="Static Y Axis" elements="20">
    <data>0.000</data>
    <data>0.022</data>
    <data>0.044</data>
    <data>0.066</data>
    <data>0.088</data>
    <data>0.110</data>
    <data>0.132</data>
    <data>0.154</data>
    <data>0.176</data>
    <data>0.198</data>
    <data>0.220</data>
    <data>0.242</data>
    <data>0.264</data>
    <data>0.286</data>
    <data>0.308</data>
    <data>0.330</data>
    <data>0.352</data>
    <data>0.374</data>
    <data>0.396</data>
    <data>0.418</data>
  </table>
</table>

<table name="Airflow/Hz Raw Scaling" category="Fuel" type="2D" level="2" scaling="uint8" address="3306">
  <table name="MAF Hz" type="Y Axis" elements="21" scaling="MAFHz" address="67a0"/>
</table>

<table name="Airflow/Hz Offset Raw" category="Fuel" type="1D" level="2" scaling="uint16" address="1512"/>

<table name="MAF Compensation" category="Fuel" type="2D" level="2" scaling="uint8" address="3322">
  <table name="MAF Hz" type="Y Axis" elements="21" scaling="MAFHz" address="67a0"/>
</table>

<scaling name="AirTempBaroFactor" units="Fraction" toexpr="x/48" frexpr="x*48" format="%.2f" min="0" max="2" inc="0.02" storagetype="uint16" endian="big"/>
<scaling name="AirTempBaroCorrection" units="Fraction" toexpr="x/128" frexpr="x*128" format="%.2f" min="0" max="2" inc="0.02" storagetype="uint8" endian="big"/>

<table name="Airflow/Hz Baro and Air Temp Compensation" category="Fuel" type="3D" level="2" swapxy="true" scaling="AirTempBaroCorrection" address="3351">
<table name="Rel Air Volume (20C, 1 bar)" type="X Axis" elements="4" scaling="AirTempBaroFactor" address="6870"/>
  <table name="MAF Hz" type="Y Axis" elements="9" scaling="MAFHz" address="6808"/>
</table>

<table name="Injector Size Scaling" category="Fuel" type="1D" scaling="InjectorScaling" address="1506"/>

<scaling name="Percent64(8-bit)" units="%" toexpr="100*x/64" frexpr="64*x/100" format="%.0f" min="0" max="400" inc="1" storagetype="uint8" endian="big"/>
<table name="BFPW Startup Comp vs Coolant Temp #1" category="Fuel" address="3732" type="2D" level="2" scaling="Percent64(8-bit)">
  <table name="Coolant Temp" address="69d8" type="Y Axis" elements="9" scaling="Temp"/>
</table>

<table name="BFPW Startup Comp vs Coolant Temp #2" category="Fuel" address="3742" type="2D" level="2" scaling="Percent64(8-bit)">
  <table name="Coolant Temp" address="69d8" type="Y Axis" elements="9" scaling="Temp"/>
</table>

<scaling name="AirDensComp" units="Air Density Correction" toexpr="x/129" frexpr="x/129" format="%.3f" min="0" max="2" inc="0.01" storagetype="uint8" endian="big"/>

<table name="Air Density Compensation for Load And IPW" category="Misc" type="2D" level="2" scaling="AirDensComp" address="36dc">
  <table name="MAF Air Temp" type="Y Axis" elements="8" scaling="Temp" address="6af0"/>
</table>

<scaling name="Mult128" units="Factor" toexpr="x/128" frexpr="x/128" format="%.2f" min="0" max="5" inc="0.02" storagetype="uint8" endian="big"/>

<table name="Sync Load Accel Compensation vs RPM" category="Fuel" type="2D" scaling="Mult128" level="2" address="3864">
  <table name="RPM" type="Y Axis" elements="15" scaling="RPM" address="6622"/>
</table>

<table name="Sync Load Accel Compensation vs Coolant Temp Table #1" category="Fuel" type="2D" level="2" scaling="Mult128" address="3856">
  <table name="Coolant Temp" type="Y Axis" elements="8" scaling="Temp" address="69be"/>
</table>

<table name="Decel IPW Subtraction Comp vs RPM" category="Fuel" address="393c" type="2D" level="2" scaling="Mult128">
  <table name="RPM" address="6576" type="Y Axis" elements="10" scaling="RPM"/>
</table>

<table name="Decel IPW Subtraction Comp vs Load" category="Fuel" address="394c" type="2D" level="2" scaling="Mult128">
  <table name="Load" address="66b6" type="Y Axis" elements="14" scaling="Load"/>
</table>

<table name="Decel IPW Subtraction Comp vs Coolant Temp" category="Fuel" address="392e" type="2D" level="2" scaling="Mult128">
  <table name="Coolant Temp" address="69be" type="Y Axis" elements="8" scaling="Temp"/>
</table>

<table name="Async Accel Pause Period" category="Fuel" address="1654" type="1D" level="2" scaling="uint16"/>

<table name="Async Accel Min TPS Delta" category="Fuel" address="1656" type="1D" level="2" scaling="ThrottlePercentage"/>

<scaling name="AsyncAccelMaxFPW" units="ms" toexpr="x*32*0.008" frexpr="x/(32*0.008)" format="%.2f" min="0" max="20" inc="0.02" storagetype="uint16" endian="big"/>
<table name="Async Accel Max Pulsewidth" category="Fuel" address="1658" type="1D" level="2" scaling="AsyncAccelMaxFPW"/>

<scaling name="Mult128-16" units="Multiplication Factor" toexpr="x/128" frexpr="x/128" format="%.2f" min="0" max="5" inc="0.02" storagetype="uint16" endian="big"/>
<table name="Async Accel Max Total Contribution During Accel Period" category="Fuel" address="165A" type="1D" level="2" scaling="Mult128-16"/>

<table name="Async Accel Mult to Coolant Temp Adder During 5 Sec After Startup" category="Fuel" address="165c" type="1D" level="2" scaling="Mult128-16"/>

<table name="Async Accel Above TPS Enrichment Cutoff vs RPM" category="Fuel" address="38b2" type="2D" level="2" scaling="ThrottlePercentage8">
  <table name="RPM" address="6622" type="Y Axis" elements="10" scaling="RPM"/>
</table>

<table name="Async Accel Multiplier vs TPS Delta" category="Fuel" address="38a2" type="2D" level="2" scaling="Mult128">
  <table name="TPS Delta" type="Static Y Axis" elements="9">
    <data>0.0%</data>
    <data>1.6%</data>
    <data>3.1%</data>
    <data>4.7%</data>
    <data>6.3%</data>
    <data>7.8%</data>
    <data>9.4%</data>
    <data>11.0%</data>
    <data>12.5%</data>
  </table>
</table>

<table name="Async Accel vs RPM Adder" category="Fuel" address="38d0" type="2D" level="2" scaling="uint8">
  <table name="RPM" address="6622" type="Y Axis" elements="15" scaling="RPM"/>
</table>

<table name="Async Accel vs Coolant Temp Adder (Main)" category="Fuel" address="38c2" type="2D" level="2" scaling="uint8">
  <table name="Coolant Temp" address="69be" type="Y Axis" elements="8" scaling="Temp"/>
</table>
Offline
 
Reply With Quote
Old Dec 17, 2009, 10:35 AM   #12
EvoM Moderator
Thread Starter
iTrader: (10)
 
scheides's Avatar
 
Join Date: Oct 2006
Location: Minneapolis
Posts: 4,826
Thanks: 0
Thanked 5 Times in 3 Posts

Drives: BeaterX

Quote:
Originally Posted by phenem View Post
WOW! Did this need done! Great job man! Thanks for helping out, everything looks good as far as I can tell!

Scheides, if you want I can add the mrfred patch to the XML code and add fix2 and fix3 that way if fix3 is better we can take out Fix2 or vice versa? That way you can remove that from your directions and make it even easier!

P.S. - in your post you still spelled my alias wrong, hehe no worries
Ya, if you want to add the xml for fix1,2, & 3 using the xml mrfred posted (and associated names) that would own. That way, I can change it to simply say something like, 'if you're having a slight stutter while cruising, try this...' and if we eventually settle on an agreed-upon fix we'll either change it in the base rom or I'll update the post with a definitive change to make.

Name updated, NO idea why I want to say phenOm, like you're a phenomenon or something!
Offline
 
Reply With Quote
Old Dec 17, 2009, 10:38 AM   #13
EvoM Moderator
Thread Starter
iTrader: (10)
 
scheides's Avatar
 
Join Date: Oct 2006
Location: Minneapolis
Posts: 4,826
Thanks: 0
Thanked 5 Times in 3 Posts

Drives: BeaterX

Quote:
Originally Posted by phenem View Post
I would update your Async_vs_TPS from this post here: https://www.evolutionm.net/forums/7639720-post23.html

I don't know what table that is according to mrfred now, what address is that table you have?
Are you talking about the xml for the various stutter fixes? If so I'll post specifically what I have.
Offline
 
Reply With Quote
Old Dec 17, 2009, 10:50 AM   #14
Evolved Member
iTrader: (39)
 
phenem's Avatar
 
Join Date: Jul 2005
Location: Central PA
Posts: 811
Thanks: 0
Thanked 3 Times in 2 Posts

Drives: '03 Silver 2.3 EVO8, '07 Black Outlander XLS!

Quote:
Originally Posted by scheides View Post
Are you talking about the xml for the various stutter fixes? If so I'll post specifically what I have.
Yes, specifically decel and async vs. tps tables
Offline
 
Reply With Quote
Old Dec 17, 2009, 12:05 PM   #15
EvoM Moderator
Thread Starter
iTrader: (10)
 
scheides's Avatar
 
Join Date: Oct 2006
Location: Minneapolis
Posts: 4,826
Thanks: 0
Thanked 5 Times in 3 Posts

Drives: BeaterX

The ones I'm using are:
  • Fix1: 162c (change from 205 to 255) "Maf Pulsewidth reset"
  • Fix2: 1630 (change from 112 to 0) "Scaling Factor for Load Transition"
  • Fix3: 27a0a (change from 0x8909 to 0x0009 IIRC) "BT->NOP for Static DeltaMasterLoadPos/Neg Threshold"

I'm currently using Fix2. The async vs TPS table I have left untouched. Perhaps I need to add a step 5a with common tables that may need to be tweaked once converted to SD? Might be getting out of scope though.
Offline
 
Reply With Quote
 
 
Reply

Related Topics
Thread Thread Starter Forum Replies Last Post
Speed Density 2.0 (3D VE Tables, Baro) RoadSpike EcuFlash 920 Dec 11, 2017 02:48 AM
Speed Density MAT 03whitegsr EcuFlash 50 Oct 8, 2017 09:16 AM
Speed Density Questions Rom 96531706 4b11slayer EcuFlash 16 Jul 28, 2017 11:33 AM
Omni 4bar writeup tephra Evo X Engine Management / Tuning Forums 66 Jun 1, 2017 04:42 AM
how-to: ECU-based direct boost control mrfred EcuFlash 1081 Aug 26, 2016 07:13 PM


Tags
conversion, density, evo, evo8, feedback, map, o2, problem, rom, sd, sensor, speed, studder, tephra, v7

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -7. The time now is 11:46 AM.


We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.
 
  • Ask a Question
    Get answers from community experts
Question Title:
Description:
Your question will be posted in: