View Single Post
Old 05-26-2017, 08:38 AM   #730
TachyonBomb
Senior Member
 
Join Date: May 2017
Drives: 06 Evo GSR SE, 17 Series Yellow BRZ
Location: San Jose, CA
Posts: 227
Thanks: 279
Thanked 169 Times in 79 Posts
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
So I came from the 03-15 evo world. I've been tuning them with tactrix cable + ecuflash since 07. How did ecuflash go from such a nice user friendly program with lots of updates, lots of constantly updated ROMs with nifty features like multiple maps, map switching through our intercooler sprayer switches or with holding down gas pedals, no lift shift, warning functions, electronic boost controls, anti-lag, cam adjustments etc etc... for both US generations of the evolution to this hollow patch work thing you have going on here?

How did it go from one platforms primary tuning program for daily driven 700hp cars running e85, multiple map switching while in motion, ecu controlled boost, and speed density to this subcommunity of a subcommunity for the brz, with no support and no one using it on the brz/86 platform? :-(

Better yet how are ecutek and oft a thing when this community has access to ecuflash? Ecuflash is pretty much on par with ecutek in the evo world. I'm really shocked to see how polar opposite the situation is here with no real push to have it mirror a similar level of functionality and versatility.

I always knew the gods smiles down on mitsubishi with great, cheap and easy to use tuning options like DSM Link for the eclipse and ecuflash for the evo. It was one of biggest reason I stayed away from other platforms.

So here is how I remember ecuflash going

1) get cable, drivers, ecuflash
2) copy and paste current version of evo ROM
3) get .xml with all the neat tweaks you want, make sure ROM fits your ecu model year and region,
4) free data logger program
5) use the data logging program
6) download .bin from your car,
7) edit in ecuflash,
8) load back into car,
9) data log
10) rinse repeat

From everything I've read in the case of the brz/86 this seems to be the order of operations:

1) get cable, drivers, ecuflash
1.1) get romraiders, download 32bitbase file
2) copy and paste current version of brz ROM
3) get .xml with all the neat tweaks you want, make sure ROM fits your ecu model year and region
3.1) looking through the table definitions on romraiders and through the posted pics of the table options in the romraiders software there seems to be quite a large gap in the extras department between brz and evo. along with a large gap between table definition/options in romraiders and ecutek
4) free data logger program
4.1) No good logging option for the tactrix cable + ecuflash combo (so forget points 4 & 5)
5) use the data logging program
6) download .bin from your car
6.1) Stays the same
7) edit in ecuflash
7.1) convert to romraiser format
7.2) edit in romraiders (disregard step 7)
7.3) convert back to .bin ecuflash usable form.
8) load back into car with ecuflash
9) data log
9.1) (reference step 4.1)
10) rinse repeat

Was I close to the mark on my estimations of the current ecuflash situation here?

Here are my main questions about ecuflash in relation to a turbo application:
1) Are there any xml definitions with boost control features and/or e85 features such as map switching or flexfuel
2) For the timing and fuel maps can the load values be increased if so what is their maximum value?

Notable observations on the current state of brz/86 tuning:
-No one is currently working on new features/definitions. At least I believe that is what i read some pages back. This is kind of a sad thing to find out.

-Lastly one of the biggest shocks of all is that this community is so dependent and ok with the idea of "mail in" tunes. pre-made mail in tunes got so beaten out of the mitsubishi community because they were blowing up engines left and right in the early evo years. Ecuflash came around and the idea of personalized road/dyno tuning with many many many log pulls became the standard so the tune can best fit the car after that the rate of engine failures decreased dramatically thereafter. But everyone here is in a copy someone else's tune free for all, like I said earlier total polar opposite of what I'm familiar with.

^^^ That last point is the whole reason ecutek methods and business model rubs me the wrong way. It may not be as big a deal for NA applications but for the forced induction guys doing this email tag with one log sent to the tuner thing has me saying a little prayer for their motor.
TachyonBomb is offline   Reply With Quote
The Following User Says Thank You to TachyonBomb For This Useful Post:
504 (05-26-2017)