Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging

[steve99]

Originally Posted by Tor

Thanks freerunner, we cross posted.

I will make a read/save first thing.

Everyone from my neck of the woods seems to have A01G, so I suppose I do as well. That's one less thing to worry about then.

I already updated the 32bitbase, with the one from Github. I just wanted confirmation that it was correct.

Which RR file from Kodename47 should I pick? Is his "standard" definitions also containing the extra tables?

don't get me wrong im not being an ass.


Over the past three years ive attemped to help several people who have bricked their ecu due not understanding the process and whats going on with flashing/defs/roms ect.


Bricking your ecu was quite expensive until we discovered the process to exchange ecu yourself , before that it was buy new ecu from dealer and get them to install and code in, about $1300 our money.


It took me quite some time to understand this process and their was basicly nothing written on how to do it back then.


This process is robust if you know what your doing and understand the process.


Its also very unforgiving if you get it wrong, once ecu is bricked its bricked, its not like a memory stick you can just erase and try again.


Things change constantly, and at freerunner said your usually ok with A01G roms/defs but oft guys change stuff all the time so you need to check. Also A01G is not suitable for all cars only up to about mid 2014 manuals.




Read out your stock rom first
Save a copy as .srf and .bin
Establish which calid it is


Play around with ecuflash and romraider and tunes before you try to flash


Conform the rom calid of the rom your going to flash
check tables in ecuflash and romraider if your editing and before flashing


always allow ecuflash to correct checksum if it askes (failure to do this will likely brick ecu)

[Tor]

Originally Posted by Kodename47

@Tor I'll link to my A01G Romraider defs when I'm on a laptop so you can choose which ones you prefer. What files are you trying to flash? OFT with launch control etc or just a normal standard ROM?

It doesn't matter if the tables don't appear in ECUflash, the definitions just point to the table locations so if the info isn't in the definition it is just invisible.

Questions still open:
1)My car is stock with A00G. I want to flash either OTS 2.076 or Wayne's 1.09 to the car.
Q:
From what I read so far I can flash the A01G version to my 2013/A00G car?

2) I want to use RomRaider to add timing to Waynes 1.09 if using that instead of OTS (tip from Wayne). EU/German fuel is supposedly better than AU (see my log, no knock on stock tune with 34 deg C ambient temperature).
Q:
I suppose your "OFT Manual G series" A01G file will work both for Waynes 1.09 and OFT 2.076?

I might want to experiment with "sound tuning" (exhaust bubble). Or other simple stuff where I can follow guides and slowly learn to use the software. I would need the Overrun tables from your definitions (thank you for your work).

Questions that have been answered:
1) Use Github 32bitbases - leave the other files as they are.

2) The OTS is a true A01G and won't cause me headaches if/when editing.

3) Use Github A01G EcuFlash definition (6 months old) for any A01G tune, no matter what definition was used to edit in RomRaider (thanks).


Future plans:
After I moved (in 2 months) and get a garage I want to remove the cat from the stock header. Then I want to repeat the above for a stg 2 tune, or depending on how brave I am/how much it catches my interest/how much time I have, might try out working on it myself.

Thanks for helping me out.


Steve99, I don't know what I did to piss you off, I am just looking for advice on the (I suppose) fairly simple questions above. In any case thank you for writing the many guides, which without I would be even more confused.

[Tor]

Looks like we were both writing and cross posting.

Originally Posted by steve99

don't get me wrong im not being an ass.


Over the past three years ive attemped to help several people who have bricked their ecu due not understanding the process and whats going on with flashing/defs/roms ect.

I can imagine there are a lot of questions from people not reading up on the stuff. I think I did and I am fairly sure that my own answers to my questions are correct. The reason for asking them and not simply diving into it, is exactly because I do not want to brick my ECU. So while my questions might seem noobish, I am basically just looking for a blessing before ruining anything.

And I do indeed want to learn! But I need to get started somewhere. I am practically orientated. I want to get my hands on it in a safe way, even if I don't know it all from the beginning.

Things change constantly, and at freerunner said your usually ok with A01G roms/defs but oft guys change stuff all the time so you need to check. Also A01G is not suitable for all cars only up to about mid 2014 manuals.

For that reason, my plan is to stick with whatever definitions and tunes I pick out now and with the advice I get are deemed safe combinations. If I in the future for some reason need to change, I wont due so without due diligence.

Read out your stock rom first
Save a copy as .srf and .bin
Establish which calid it is

Check and save! It's A00G according to "current ROM metadata" to the left. I wonder how it's recognised as I only have the Github A01G definition loaded in EcuFlash.

When saving I also got an error message about "invalid data":



I suppose that is exactly because I don't have a A00G definition loaded? I will of course do it properly before attempting any kind of flashing. Only have A00G on the read, delete it and put the A01G in the folder when flashing.



Check on the rest of the advice as well. Thank you. I already edited (and discarded) several files, just to find out how the RomRaider interface works.

Thanks for your help, it's much appreciated! I hope I will be just as enthusiastic as you and many others, and who knows maybe I can contribute down the line (I'm a flow chart kind of guy ).

[steve99]

Originally Posted by Tor

Questions still open:
1)My car is stock with A00G. I want to flash either OTS 2.076 or Wayne's 1.09 to the car.
Q:
From what I read so far I can flash the A01G version to my 2013/A00G car?

2) I want to use RomRaider to add timing to Waynes 1.09 if using that instead of OTS (tip from Wayne). EU/German fuel is supposedly better than AU (see my log, no knock on stock tune with 34 deg C ambient temperature).
Q:
I suppose your "OFT Manual G series" A01G file will work both for Waynes 1.09 and OFT 2.076?

I might want to experiment with "sound tuning" (exhaust bubble). Or other simple stuff where I can follow guides and slowly learn to use the software. I would need the Overrun tables from your definitions (thank you for your work).

Questions that have been answered:
1) Use Github 32bitbases - leave the other files as they are.

2) The OTS is a true A01G and won't cause me headaches if/when editing.

3) Use Github A01G EcuFlash definition (6 months old) for any A01G tune, no matter what definition was used to edit in RomRaider (thanks).


Future plans:
After I moved (in 2 months) and get a garage I want to remove the cat from the stock header. Then I want to repeat the above for a stg 2 tune, or depending on how brave I am/how much it catches my interest/how much time I have, might try out working on it myself.

Thanks for helping me out.


Steve99, I don't know what I did to piss you off, I am just looking for advice on the (I suppose) fairly simple questions above. In any case thank you for writing the many guides, which without I would be even more confused.

Im not upset mate


I just don't like hearing about people bricking their ecu :-)




If your stock rom is A00G then yes use A01G roms and defs and you should be fine.


You probably best using wayno's roms and his defs for romraider use the A01G roms and defs. His roms are already set up with a lot of good tweaks and set up for 98 ron fuel not usa 91/93.


Then just flash with ecuflash using a A01G def, make sure you let ecuflash correct checksum, romraider does not correct it properly.








All the roms are native metric, the defs just scale the parameters to display in metric (some eg kodename47 defs) or imperial (romraider , wayno,s). The danger is transferring data from one rom to another if you have a mix of metric and imperial defs.


keep everything A01G and you should be fine. always worth checking rom with hex editor to see all three calid are same and A01G and that some tables like Primary OL fueling and base timing B look fine and x/y axis look good, mismatch rom/def will show up with weird values or weird axis values.


If you ever see anything weird, don't flash, find out what problem is.

[Kodename47]

A00G/A01G/A02G all compatible.

Defs (Non-OFT, no LC access):
A01G - Metric/Ratios - ECUtek Style
A01G - Metric/%

These will work correctly with any A01G file whether OFT or not, so the ones you listed are compatible.

[steve99]

as above from @Kodename47


A00G/A01G/A02G defs compatible


just be aware that


OFT A00G A01G and A02G are all actually based on A01G rom


The stock A00G/A01G/A02G roms appear not to have been recompiled or what ever was done did not alter the locations of the known tables in definitions so they are compatible definition wise. It likely that changes were made to "undefined" or unknown tables in the rom for A02G


The A00G to A01G incorporated a critical fix to transient retard tables so its well worth going to A01G if your going to drive car hard, A02G seemed to just add more idle stability fix's according to the romraider gurus.


If you want a "real" A02G rom you will have to transfer all the changed tables from a OFT A01G rom to a stock A02G rom.

[freerunner]

Originally Posted by Tor

Everyone from my neck of the woods seems to have A01G, so I suppose I do as well. That's one less thing to worry about then.

As long as your car didn't come with a D00G or upwards you can flash A01G regardless which version was installed. Commonly European models before or early 2015 haven't had D00G, IIRC.

Originally Posted by Tor

I already updated the 32bitbase, with the one from Github. I just wanted confirmation that it was correct.

Can't hurt but should not be necessary any more based on my last experience.

Originally Posted by Tor

Which RR file from Kodename47 should I pick? Is his "standard" definitions also containing the extra tables?

They all come with extra tables, you just have to choose which units are more pleasant to your eye. I went with standard/metric since the units are mostly similar to my Tactrix logcfg.

[Tor]

Thanks a lot to all of you. With your help I feel confident to flash now.

I will start out by simply flashing Waynes 1.08.2 Stg 1 A01G, without any changes. Then do some logging and see if it knocks. If it doesn't I might add 2 deg timing to the base timing B, using Waynes defs.

[freerunner]

Don't want to cut your zeal, but I suggest you to get your AFR (-> maf scale) right in the first place

[steve99]

Originally Posted by Tor

Looks like we were both writing and cross posting.



I can imagine there are a lot of questions from people not reading up on the stuff. I think I did and I am fairly sure that my own answers to my questions are correct. The reason for asking them and not simply diving into it, is exactly because I do not want to brick my ECU. So while my questions might seem noobish, I am basically just looking for a blessing before ruining anything.

And I do indeed want to learn! But I need to get started somewhere. I am practically orientated. I want to get my hands on it in a safe way, even if I don't know it all from the beginning.


For that reason, my plan is to stick with whatever definitions and tunes I pick out now and with the advice I get are deemed safe combinations. If I in the future for some reason need to change, I wont due so without due diligence.


Check and save! It's A00G according to "current ROM metadata" to the left. I wonder how it's recognised as I only have the Github A01G definition loaded in EcuFlash.

When saving I also got an error message about "invalid data":



I suppose that is exactly because I don't have a A00G definition loaded? I will of course do it properly before attempting any kind of flashing. Only have A00G on the read, delete it and put the A01G in the folder when flashing.



Check on the rest of the advice as well. Thank you. I already edited (and discarded) several files, just to find out how the RomRaider interface works.

Thanks for your help, it's much appreciated! I hope I will be just as enthusiastic as you and many others, and who knows maybe I can contribute down the line (I'm a flow chart kind of guy ).

If you save image as .srf it saves extra data and info about tge rom for the tactrx guys.

if you save as .bin format it does not save the extra info , and it zero pads the 0000-7FFF area this does not get written when you write a rom to car, its just a warning message and is ok.

the 0000-7FFFF is the " boot" area of the ecu, this is the failsafe area and will often save you from bricking ecu as it allows the ecu to still communicate with obd port after a failed flash, but only if you dont turn off ignition Not even tactrix guys have worked out how to read thi locked area yet so the info in that area id not valid anyway.

once you turn off ignition the ecu may jump from program mode to run mode and pass through boot area and attempt to run a corrupted partial flash and go into an indetermiate or loop state, it does not appear to have a good watchdog timer .

if you ever get fail always reflash , dont turn ignition off.

[steve99]

Originally Posted by Tor

Thanks a lot to all of you. With your help I feel confident to flash now.

I will start out by simply flashing Waynes 1.08.2 Stg 1 A01G, without any changes. Then do some logging and see if it knocks. If it doesn't I might add 2 deg timing to the base timing B, using Waynes defs.

just be carefull adding timing, wayno has also changed the knock correction max A table and total timing is base b plus knock correction max A.

also if your looking at usa 93 tunes their 93 is usually more knock resistant than your 98 ron.

im sure your flash will be fine

[Tor]

I flashed Waynes stg 1 A01G tune without any problems. And the car runs fine. There is a noise I didn't hear before at 4000 rpm. Best described as like a hissing noise from the valves. I suppose that comes from some adjustments and it's normal?

Edit:
I suppose this is what I hear at 4000 rpm?


I drove the car for about 45 mins to 1 hour and in the end did some pulls in 3rd gear.

also if your looking at usa 93 tunes their 93 is usually more knock resistant than your 98 ron.

I think there is a misconception (or generalisation) about EU fuel. We have (Germany and Northern EU) fuel that is at least on par or surpasses US fuel. Actually there is equally a common misconception here, that all US fuel is crap.

Anyway I run 100 octane Shell V-power (we got 102 octane Aral as well). And I have 0 flkc / 0 fbkc and IAM 1 with Wayne's 1.08.2.

http://datazap.me/u/tor/ww1082-stg-1...ata=2-16-19-27

However I will leave it as it is until I see how it's working at the track.

As for how it feels, I can't feel a difference in power as expected. But the pedal tuning feels very nice, more aggressive generally and when accelerating from within the torque dip it feels more linear. Best way to describe it is there is a better correlation between what you demand and what you get (I make no illusions that I am actually getting significantly more power in the torque dip).

Originally Posted by freerunner

Don't want to cut your zeal, but I suggest you to get your AFR (-> maf scale) right in the first place

Thanks!

How does the MAF look in the log? 12-13 during the pull should be okay?

I will have a closer look at the guide:
http://www.ft86club.com/forums/showthread.php?t=64790

[Tor]

Originally Posted by steve99

just be carefull adding timing, wayno has also changed the knock correction max A table and total timing is base b plus knock correction max A.

Is the info about KC max additive advance found here applicable to our cars as well?

http://forums.nasioc.com/forums/show....php?t=2612534

[lizbrayan]

Alright Guys, so I got my tactrix openport 2.0. I got the D00D definitions from github. Read my stock ecu which is also D00D. Have my oft stage 2 uel 93 map open and I checked it in a hex editor. The only place za1jd00d shows up is at 8000. What else do I have to do to make sure I dont brick my ecu. Did I cover all my bases am I good to go ?