Hey guys, Let me first start off by saying that I have searched and cannot find a single source of this information.

This is a request to all EcuFlash highly experienced users and pro tuners.

I think it would benefit the Evo X community to have a single source/thread for all Evo X EcuFlash table descriptions and how they impact your tune.

I know that a lot of the tables are intuitive, such as the high octane fuel table, but others are not quite so intuitive.

Screenshots would be great, but are not necessary, something along the lines of:

High octane fuel map:
Configures the fueling for open loop operation during the use (or detection) of higher octane fuel. - Normally used to set WOT A/F ratio.


Additionally, a single source of all XML code for each Rom ID can be stored on-line for all to lookup and use. If a better hosting solution cannot be found, I will offer my google site.

The goal here is to create a SINGLE source of information describing each known table in EcuFlash and possibly hosting the known XML code for each Rom ID.

I am not asking anyone to divulge any super secret tuning methods, "special sauce", or table values (other than min-max values)

Again, if there is a single source and I have missed it, please delete this thread. My experience is that I have to hunt around for each table and either guess or ask a few key people for its intended use. Tephra is remarkable in finding and publicizing this information, yet no one, that I know of, centralizes this data.

 

It's a sticky...about 4 posts up

https://www.evolutionm.net/forums/ev...10-thread.html

 

Yes, that does have some good data in it, but again, it's not a single source of information. It's bombarded with converstaions left and right and has generic table definitions such as this one:

Mivec Exhaust #2 (This is the adjustable Exhaust Cam map #1)

There's is no mention of when it's used...Normal operating temps? High altitude? Nothing to let a person know if they should modify #2 or #1, or both.

I'm not asking this because I'm clueless, I've have tuned successfully, but that doesn't mean I know what every table acomplishes.

EcuFlash is opensource/free so why can't us users provide the table definitions to help people understand what each table acomplishes.

For example, I have no idea what idle table #4 does... I end of modifying all the idle tables because I don't know specifically what each one does. This works for me to set my idle, but doesn't help me understand the ecu any better.

 

Most of the definitions that are important for tuning are covered in that thread though, discounting all the random crap in it and side conversations. It's the closest thing you will find to a single source thread. Otherwise you will have to go through all of Tephra's threads and compile them into a single thread along with the legitimate info from the definitive thread.

Since the majority of people only need a handful of the maps to be changed (High Octane Fuel, High Octane Timing, IPW, Injector Scaling, Injector Latency, Stationary Rev Limit, and WGDC maps, and the disable p codes) defining the exact function of some of the lesser maps may be very hard to accomplish.

If you're looking for the best defined XML for the 2008/2010 GSR which includes all the little tweaks available etc as well as some more concise naming conventions for some of the sections pm Golden or search his threads for the most up to date xml. I have his on my car for the 2010 and it is great. It also indicates which things are warmup and regular running temp on things like MIVEC maps as well as indicates the p codes that are disabled with that bit on or off.

Hope this helps
~Trent

 

Or you can start adding ROMs and threads to the stock ECU tuning wiki (see my sig)

 

I really need to update that thread. I created it right when the Evo 10 XML was first coming out for the 10. There are a ton more tables available now and we know much more about them.

It's crazy, I created that thread almost exactly two years ago..

- Bryan

 

That would be great Bryan! Could you start a new thread that's locked so that people can't clutter it up like the old one. For the descriptions of each table we don't need anything to long, just something quick to explain what the table does and when it's active. Example high altitude boost tables.

 

Great idea.

the central xml repository would also be very helpful.
I know this has been discussed before, and that they will eventually be included in future releases of ECUFlash, but a go-to site would be most useful indeed

There are probably dozens of versions of each xml floating around aswell - it would be sooo nice to know that you have the 100% up to date "authorative" xml for your particular ROM on your laptop!

 

this comes up every 6 months or so.

as I've said before, if anyone is up to maintaining something in CVS/SVN, I'd be happy to donate server+bandwidth.

 

This is a really good idea. It will help out alot of people, including myself, who are trying to learn how to tune. Another thing is that the 2008's and 2010's are just alittle bit different.