For dealership visits you. Would want to flash back to your original Rom. The ecutek map switching is achieved by altering the actual program code of the Rom and adding additional program code which can reference up to 4 maps and other additional tables e.g. custom maps to perform additional functions and interpret inputs from non standard sensor inputs it's an entirely different Rom.

Most other tuning platforms just alter the table data and leave the program code unaltered except for some minor patches for launch control an flat foot shift, these implementations are much less sophisticated than ecutek where lc and ffs parameters and maps can be changed on the fly without the need to reflash.

The logging and other features make ecutek a better platform and faster for tuners to achieve their goals but it does cost more you just have to work out if you want or need the extra features and capabilities against the price.

You might want a 91 93 e85 tune plus tune with or without of offs. Or you might want a low boost economy tune for daily drive and then full boost track tune switchable on the fly.

You wouldn't want to switch to a "stock" map for dealer visits since the ecu code is so hacked. Flash a stock map with ECUtek is much better, but even that isn't "Stock" because it has license data embedded in it.

are those the same patches that OFT uses? If so, have they cleared it with tinywrex?

Did not say it too well but that was my thoughts exactly, it one slight "problem" with ecutek the stock map isnt exactly the same :)

Do you know what OFT stands for? OpenFlash Tablet. The OFT uses the open flash protocols (which is open source), the only proprietary stuff about the tablet is the hardware and the software you use to load tunes to the tablet.

You could do the exact same stuff manually using a Tactrix cable and a laptop, but the OFT is a lot more portable and user friendly than the alternatives with open flash.

Funny, I didn't see this thread at all. So much incorrect information earlier on in the thread... I think Vgi's covered most of the inaccuracies. All these features are proprietary code that is compiled and added into the stock code, and is 'hooked' in at the relevant areas to redirect the stock code to run the modified code. (E.g. if switch speed density = 1, then JSR to SD code, as opposed to run stock MAF code).

Since I'm holding the torch for opensource, I'll just make the point that there has been hacks in the OS community going back many years, on multiple platforms, I suspect long before the commercial guys got involved. Tinywrx has been mentioned (who actually wrote all the code required for live tuning on the older 16bit roms, just never got implemented in the GUI, and a host of other hacks for LC, FFS, valet, etc.). Tephra on the Mitsu side did an enormous amount of work for the Evo's, NSFW created another LC / FFS implementation, and more recently Merp has created a whole range of impressive hacks, including multiple map switching, map blending (usable with various triggers, e.g. TGV sensor inputs - think flex fuel, live mode switching, SI drive switching), CEL and other conditions (EGTs, Coolant), a very sophisticated launch control and FFS system that puts both the Ecutek and OFT implementation to shame - matched to the OEM gear ratios, with the ability to retard timing, compensate fueling, remove FBKC; a whole range of boost and wastegate hacks for map switching; Blended speed density.

I could go on... bottom line is that this has not yet been ported across to the BRZ platform - primarily due to the different CPU that these ecu use. But that's just a matter of time - if you doubt me, I compiled this for a mate for a 2006 hawkeye Sti this weekend:

http://i990.photobucket.com/albums/a...ps11276ec2.jpg

Yup - all that's understood about the stock code has been reverse engineered from the assembly language.

Two things: oft/brzedit launch control isn't launch control, it's a two step rev limiter. It does nothing at all to actually control the launch after you drop the clutch, ecutek does.

Also the main difference between a patched rom and what ecutek does in my view is the method of implementation. Open source patches have to be ported feature by feature, one by one into each rom (hence why we don't have it yet) whereas ecutek doesn't implement features, it gives tuners a method by which to implement any feature (custom maps). Even when the patches are ported you still won't have custom mapping, which really is the secret sauce to begin with.

Think of it as adding a few bullet points to a list of features vs opening up the ability to create almost any feature you can imagine yourself. It's a big difference.

Yeah, sorry I don't quite buy that - yes, custom maps are flexible and provide the ability to generate a multitude of controls given that you control the parameters that make up the axis - but are you honestly saying that they are so powerful that code is not required to implement various features?

The code would be pretty straightforward actually - code an additional routine that attaches to the main routine, using the normal lookup table map pull functions, and variable inputs / outputs. Still doesn't replace proper control logic structure.

Just because you can view the source code does not mean it's open source. There is a HUGE difference between open source software and just having access to the source code.

What I meant by OFT being open source is that the technologies it uses are for the most part open and readily available. The OFT is just a nice package that bundles readily available things into an easy to use package.

I never argued on OFT being a great package and has always recommended it to people who want a flashing solution with ots tunes.

I believe I have made my point but if it doesn't get through I'll let shiv to make a comment on that if he feels like it.