Wait for the template files, most of the information is found by disassembling the code and finding the "Data sections" of it and what each section of data is used for..

I'm sure most tuners would not willingly give out that information since they paid alot of money to be the first to get the info..

However, give it time, this info will become widely available in the not too distant future.

Tuning in general is something you learn over time, any good book on tuning will give you a head start, also any book that teaches engine theory and how it works will help alot too, since things like timing and fuel ratios for power, and how turbocharging/supercharging affects compression, etc.. are all topics that one should understand anyway.

 

The Subaru has a lightening fast interpahse in the OBDII - ECU - for example Delta Dash which offers a world class data logging application for the Subaru

The Evo transfer rate is much slower which is why I generally like to log directly off the sensors themselves on evos

it will be interesting to see if anyone can work a way around the slow transfer rate on the evo and develop a better data logging application

Something like a Delta Dash is a really amazing product which makjes it easy to to a really great job

 

I think all the address locations have already been identifed by those who have developed the softwear in their forums

What I have figured out on my own was done through lots of trial and error

I am sure that when real computer engineers start to work on the code they will discover and identify a lot more functions than I have been able to find with my limited computer ability

As a tuner the unloking of locations is very exciting to me as it gives me the ability to give an even better tune

One of the areas I have been hard at work on with no success is the 0300 code settings

That a a few other CEL 's would be nice to tunr off as I can with my Suabru flashing equipment

 

You are correct. Short of a new processor in the ECU, I cannot see an OBDII bump in sample rate.

One thing to consider here is the read time and write time of this program, if it works as advertised it will be very slow process of flashing the entire image. I would estimate 30 minutes on the write for each flash. I don't want anyone to forget that the Evo ECU has a 100 flash HARDWARE LIMIT. For those eager to jump into this and "play around" with it, you can easily reach the flash hardware limit of your ecu in no time and have your ECU stuck on the 100th flash. After that you need to buy a new ECU.

 

I agree with you 100% and I encourage those who are interetsed in this sort of stuff to give it a shot. Of course, I am fascinated by the subject of tuning and stock ecus.

My suggestion is to ignore most of what you read and instead start with a stock map and make little changes at a time and see what effect they have on how the car feels, reacts and what the data logs say.

Very good and accurate data logging is key and a wide band and scan tool are required.

Taking your time, going step by SMALL step and recording the results of the small changes you make will give you a good learning process and give you a feel for what works and what does not work.

Once you have taken the time to master the simple process involved it becomes very simple to actually conduct "tuning " itself.

Just my two cents

 

I was under the impression that there is no 100 flash limit. That kind of function would need to be software based, correct? and as such could be overridden. If it were a hardware limit it how would it be accomplished? All i can think of would be some sort of fuse which burns out over time, but that doesnt seem very realistic. Flash memory doesn't have a limit set to it, e.g. memory cards.

 

I have gone well over 100 flashes on my own evo - I reached 923 flashes before I went with the AEM

The 100 limit is a threashold under which the memory is gauranteed to be accurate - it is possible to exceed that limit

I am more concerend with the realiability and function of the softwear itself - especially in a windows operating environment

If the softwear works without freezing up I think most users will be fine

Also - there was some discussion somewhere that the softwear only flashes the blocks you are changing which may make it faster than you have suggested

I guess we'll all have to wait to see how well it works in practice and I hope thyat it works really well

I am epsecially excited about the potential to flash the Lancers and 4th gen - I would love to work and figuring out some new ecus

Anyway - we'll all see soon enough how it works

 

you obviously have much more knowledge about this stuff but this just seems very difficult to stomach. 100flash hardware limit? wth?

 

Read my post above

Also - anyone who reached 100 flasheds could just get a used ecu to replace his ecu

I dont think its a serious obsticle

I am more concerend about the stability of the softwear application

 

Its a specification of the chip maker

The chip must be good for 100 flash events with a certain range of failure rate

After that the memory starts to degrade

 

so say you are flashing and fine tuning and say you make 10 pulls to make adjustments to the map each adjustment counts as 1 flash so after one tuning session you could be down to as little as 90 more?

and yes i read the posts below by al

 

gotcha...good to know that you didn't notice significant degradation, if any, in your 923 flashes

I'll be getting a wideband soon, I guess I should add a logger too based on your recommendations.

 

So then why are you asking the question? Al already explained it.

 

Another point to remember is that techtom and ecutek do not reflash the whole image so say for example only 10% of the blocks are rewritten, the flash memory hardware limit is likely based off of 100 flashes of the entire image, not just parts of it so you may be able to multiply this by 10 x 10%. If in fact this new flash hardware flashes the entire image, then I would say the 100 flash range would be more accurate.

Something to think about is also the ability to read and reprogram the immobilizer unique ID code, because without it the replacement ECU would not be able to be used.

 

for clarification on how the flashing works like can you flash sections or does each adjustment count as a flash. al didnt explain anything other than it is possible to go over 100 flashes but not guaranteed. ok smart guy