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

[Illuminaughty]

Originally Posted by steve99

Tuning a boosted car from scratch is not easy

The tables you have access to in romraider ecuflash brzedit or ecutek are similar, ecuteck has quite a few extra features as their software also includes rom code patches to add extra functionallity and features. The other systems just give you access to read edit and flash the existing rom tables.

I would not recomend anyone trying to tune a turbo or sc car from scratch unless you are quite experienced with tuning.

if you bought say a sbd kit that comes with an open base tune, it possible with a bit of reading you could tweak the base tune to run a bit better. Although fiddling first time with a 10 psi tune can be dangereous.

maybe cut your teeth doing some NA tweaks then maybe work up to boosted, but id suggest you tread very carefully and start with a base tune and kit like the sbd, and maybe the lower boost 7 psi version

the logging is were your likely to run into issues as with tactrix its fairly raw and you need to know ecu ram addresses.
you might be better buying an open flash tablet or brzedit or even ecutek as you can make your own maps with ecutec

take a look here
http://www.ft86club.com/forums/showp...21&postcount=1

and talk to the speed by design guys i think it about the only opensource tune and matching kit arround. Dont try and use the tune on a different kit whole kit turbo piping intercooler wastegate the lot must match else you risk serious engine damage

I don't post very often but I came to say that I did almost EXACTLY this. Started off with an OFT using the canned tunes on NA and just looking at the logs. Got a SBD turbo kit that came with an OFT base tune for it. Ran just the base tune for a thousand or so miles until I got brave and started tweaking it ever so slightly (started with just some closed loop fueling tweaks). Tons of revisions on the OFT and I decided to scoop up an OpenPort 2.0. 20k miles later I'm running like my 30th revision of my E85 turbo tune and am now considering switching over to Ecutek to see what goodies are available there.

Also your guides helped immensely, seriously.

[steve99]

Originally Posted by Illuminaughty

I don't post very often but I came to say that I did almost EXACTLY this. Started off with an OFT using the canned tunes on NA and just looking at the logs. Got a SBD turbo kit that came with an OFT base tune for it. Ran just the base tune for a thousand or so miles until I got brave and started tweaking it ever so slightly (started with just some closed loop fueling tweaks). Tons of revisions on the OFT and I decided to scoop up an OpenPort 2.0. 20k miles later I'm running like my 30th revision of my E85 turbo tune and am now considering switching over to Ecutek to see what goodies are available there.

Also your guides helped immensely, seriously.

Thanks
just be aware with ecutek, you need the additional race rom ectension pack to access the majotity of the fancy features. A tuner can give you a tune (generally locked) with the additional features used that you can flash and use, but if you want to make your own tunes with the fancy features like custom maps SD fueling etc you need the extra pack over and above the standard pro ecu cable\dongle kit and ecu licience

[Jaden]

I just received an email from Tactrix support. The new version of ECUFlash is available that fixes the firmware so that SD card standalone logging works.

I have already DL'd installed and tested it and SD logging is fixed.

Jaden

[Wayno]

1.44.4790?

Originally Posted by Jaden

I just received an email from Tactrix support. The new version of ECUFlash is available that fixes the firmware so that SD card standalone logging works.

I have already DL'd installed and tested it and SD logging is fixed.

Jaden

[Jaden]

Originally Posted by Wayno

1.44.4790?

yessir...

Jaden

[Tor]

I ordered a Tactrix adapter and am preparing my software for it's arrival (ordered Monday and it should arrive today, from California to Germany!!).


All these different sources of definition files has me a bit scared of messing something up. So I would appreciate if someone has the time to answer some questions:

- 32BITBASE
I replace with the one from GitHub (linked in first post), in the bases folder. Is it safer to delete the rest of the files in that directory, or should I leave them as they are?

- How do I determine which rom is in my car?
Will I see that information somewhere when I do a read?

From what I understand, most likely I will have A01G (EU), if my dealer updated the rom at some point, Or maybe the the car was even delivered with A01G (03/2013).

- If my car has an older tune than A01G, what should I do?


For the sake of example, let's assume that I have A01G already for the rest of the questions:

Say I want to use a OTS v2.076 stage 1 tune (or an edit based on that tune):

- Which definition file do I use for Romraider?
It seems there are more options:
1) I could use the A01G from Github (RR_ZA1JA01G.xml in the example).
2) I could use the A01G included in the 2.076 package, filename starting with RR and picking my A01G (also named RR_ZA1JA01G.xml <- same file as in 1. above?).
3) If I want access to more tables, I need the definition files from Kodename47? Which one do I pick? Standard, Custom or "OFT Manual"? ("OFT Manual" refer to the tune being OFT or that the file is to be used with the tablet and not Tactrix?).

- Which definition file do I use for EcuFlash?
Does it matter which definition file (e.g. Kodename47) was used in RomRaider to edit the tune? Or do I ALWAYS use the one from Guthub? (Filename is the example "ZA1JA01G.xml" updated 6 months ago)?

Thanks a million to who ever can help me get my mind straight!

[steve99]

Originally Posted by Tor

I ordered a Tactrix adapter and am preparing my software for it's arrival (ordered Monday and it should arrive today, from California to Germany!!).


All these different sources of definition files has me a bit scared of messing something up. So I would appreciate if someone has the time to answer some questions:

- 32BITBASE
I replace with the one from GitHub (linked in first post), in the bases folder. Is it safer to delete the rest of the files in that directory, or should I leave them as they are?

- How do I determine which rom is in my car?
Will I see that information somewhere when I do a read?

From what I understand, most likely I will have A01G (EU), if my dealer updated the rom at some point, Or maybe the the car was even delivered with A01G (03/2013).

- If my car has an older tune than A01G, what should I do?


For the sake of example, let's assume that I have A01G already for the rest of the questions:

Say I want to use a OTS v2.076 stage 1 tune (or an edit based on that tune):

- Which definition file do I use for Romraider?
It seems there are more options:
1) I could use the A01G from Github (RR_ZA1JA01G.xml in the example).
2) I could use the A01G included in the 2.076 package, filename starting with RR and picking my A01G (also named RR_ZA1JA01G.xml <- same file as in 1. above?).
3) If I want access to more tables, I need the definition files from Kodename47? Which one do I pick? Standard, Custom or "OFT Manual"? ("OFT Manual" refer to the tune being OFT or that the file is to be used with the tablet and not Tactrix?).

- Which definition file do I use for EcuFlash?
Does it matter which definition file (e.g. Kodename47) was used in RomRaider to edit the tune? Or do I ALWAYS use the one from Guthub? (Filename is the example "ZA1JA01G.xml" updated 6 months ago)?

Thanks a million to who ever can help me get my mind straight!

I think you need to re-read my posts on Tactrix and romraider.



1. Yes load the 32bitbase from github as linked in post
2. Ecuflash will let you READ the rom from the car, if ecuflash has a matching ECUFLASH definition then it will automaticly recognise and open your rom.
3. If not you will need to save rom and then open it with hex editor and look for the string 'ZA1J" to determine the calibration ID

4. As per the rom compatability list at top of Tactrix post 400G,700G,A00G should al be replaced with A01G.

5. Ecuflash definitions and Romraider definitions are different and NOT compatable.

6. read this post and understand it how definitions work and how to recognise if you have mismatched definition
http://www.ft86club.com/forums/showthread.php?t=79152 this applies to bothe romraider and ecuflash. both can become confused by the oft calibration changes to roms and defs.

7. Rom/tune must match definition as per above link, failure to recognise this (do not rely on manes of files of roms) will almost certianly result in a bricked ECU. This applies to both romraider and ecuflash .

8. If your car is 03/2013 it will almost certianly be an A00G or A01G. but you need to confirm this

9. Many oft tunes and definitions are calid hacked for example the oft 700G tune and def are actually an A01G tune and def adjusted by hacking calid to make it look like and A01G tune. The oft A01G tunes and def were actually A01G tunes last time i looked but the A02G tune was actually an A01G tune in disguise. If your going to "borrow" their tune you need to be very carefull and learn about roms and definitions else its likely to end in tears and a bricked ecu.

10 Their are several versions of definitions floating arround, oft, github(romraider and ecuflash), kodename47 metric and imperial ones and waynos oft defs. you need to understand and know the differences

[freerunner]

Tor, you should pull the existing rom with Ecuflash first once you have your Tactrix set up, so you will always be able to reflash it in case anything goes wrong.

Next, you can flash the OFT tunes right away, if they're for A01G. A01G is always A01G (^= not calid hacked).

The last times I used Ecuflash, I went with the original 32bitbase and it worked without any flaws. Only use it for flashing and you will be fine. As already suggested, do the entire editing in RomRaider with Wayno's or Kodename47's RR defs.

[Tor]

Hi Steve, I am new to this part of the forum and I don't want to get off on the wrong foot with anyone. I read all the post in your signature a dozen times. I didn't come here and ask "hey, can someone give me a run down on how Tactrix work"...

I asked some specific, clear questions (that was at least the intention).

2. Ecuflash will let you READ the rom from the car, if ecuflash has a matching ECUFLASH definition then it will automaticly recognise and open your rom.
3. If not you will need to save rom and then open it with hex editor and look for the string 'ZA1J" to determine the calibration ID

Thank you for the information on the hex editor, I didn't see that anywhere else. I will use that method, since I don't know with certainty which definition file to load in the first place.

5. Ecuflash definitions and Romraider definitions are different and NOT compatable.

6. read this post and understand it how definitions work and how to recognise if you have mismatched definition
http://www.ft86club.com/forums/showthread.php?t=79152 this applies to bothe romraider and ecuflash. both can become confused by the oft calibration changes to roms and defs.

7. Rom/tune must match definition as per above link, failure to recognise this (do not rely on manes of files of roms) will almost certianly result in a bricked ECU. This applies to both romraider and ecuflash .

I understood these points already, and bricking the ECU is my fear, which is why I specifically asked for which files to use where. My questions were divided for EcuFlash and RomRaider.

I also tried opening the same A01G map in both RomRaider and EcuFlash with various A01G definitions. The map seemed to open fine (Base timing B looked the same e.g), but being new to this it still didn't give me reassurance that everything is ok. E.g. if using Kodename47 definitions (not sure I use the right one), I see tables in RomRaider, that I afterward don't see in EcuFlash. I don't know if this is acceptable.

10 Their are several versions of definitions floating arround, oft, github(romraider and ecuflash), kodename47 metric and imperial ones and waynos oft defs. you need to understand and know the differences

Thanks, that what I am trying to. Frankly, telling me that I need to understand the difference is not much help at all. Believe me, I do wan't to know the difference, that's why I practically didn't sleep for 2 days reading up on this stuff.

Can we start over? Or can someone else perhaps answer the questions I had regarding definitions. Shortened for brevity (which I sometime fall into):

1) Which Kodename47 definition file should I use for RomRaider for e.g. an OTS 2.076 A01G tune (imperial)?

2) If using the file in question 1), will it influence which file I should use for EcuFlash? Or should I always stick with the 6 months old GitHub file (ZA1JA01G.xml)?

I just need these 2 answers to make sure I feel safe. Then I won't bother anyone with more stupid questions.

[Tor]

Originally Posted by freerunner

Tor, you should pull the existing rom with Ecuflash first once you have your Tactrix set up, so you will always be able to reflash it in case anything goes wrong.

Next, you can flash the OFT tunes right away, if they're for A01G. A01G is always A01G (^= not calid hacked).

The last times I used Ecuflash, I went with the original 32bitbase and it worked without any flaws. Only use it for flashing and you will be fine. As already suggested, do the entire editing in RomRaider with Wayno's or Kodename47's RR defs.

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?

[nikitopo]

Originally Posted by Tor

I ordered a Tactrix adapter and am preparing my software for it's arrival (ordered Monday and it should arrive today, from California to Germany!!).

Too bad I didn't catch it before. I had a spare Tactrix adapter here in Germany. I don't need it.

[Tor]

Originally Posted by nikitopo

Too bad I didn't catch it before. I had a spare Tactrix adapter here in Germany. I don't need it.

Hi nikotopo, are you on gt86drivers.de? Are you in Chapter West (sounds like the German GT86 community is a part of hells-angels). I got it in the mail this morning! I managed to do a read (I'm A00G according to EcuFlash) and do a log already:

http://datazap.me/u/tor/stock-a00g-m...&zoom=834-1115

I'm sure you can sell it with ease on the forum. When I get a grip on it I might write a beginners guide in my lousy German or make a few videos. The setup is a pain in the ass, especially with these stereotype disorganised programmer geeks not making a simple structure for which files to use.

[steve99]

Originally Posted by Tor

Hi nikotopo, are you on gt86drivers.de? Are you in Chapter West (sounds like the German GT86 community is a part of hells-angels). I got it in the mail this morning! I managed to do a read (I'm A00G according to EcuFlash) and do a log already:

http://datazap.me/u/tor/stock-a00g-m...&zoom=834-1115

I'm sure you can sell it with ease on the forum. When I get a grip on it I might write a beginners guide in my lousy German or make a few videos. The setup is a pain in the ass, especially with these stereotype disorganised programmer geeks not making a simple structure for which files to use.

the reason its seems unorganised is


A small company of two guys makes Tactrix hardware and does ecuflash software for a very reasonable price $160. They don't produce definitions bitbases or tunes etc.


Another group of people at romraider (who basicly work for free in their spare time) write romraider.


Pretty well one guy on the planet tdd produces definitions for 86/brz for romraider and ecuflash, and he does not even own a 86/brz.


Kodename47 and wayno used the tdd base defs to produce their own defs more suited to some people and themselves




The tactrix guys or romraider don't produce how to guides for ecuflash its basicly work it out yourself




OFT guys are not affiliated with tactrix or ecuflash of romraider they are an independent company.


Their defs are produced again of tdd base defs and their defs suit their system and tunes and are not meant to be used with tactrix/ecuflash system


OFT tunes most people hijack are produced by the OFT guys for the OFT system your really supposed to buy an oft :-) , while they provide them openly they are not designed to be used with tactrix/ecuflash they are designed for OFT system, so they are not going to help you use them on a competing system that they derive no income from.


The initial ECU ram addresses (they are different for every rom calid) were extracted by tdd and then another guy ztan added some more and produced some logcfg.txt files.


Extracting ram address testing and producing defs takes hundreds of hours.


A couple of years ago I attempted to collate all this random info and posted up the Tactrix guide with links to bitbases,defs,romraider defs, stock roms etc and some logcfg.txt files to make it easier for people.


Just remember all these guys are working for free :-)




If you want a plug and play system then buy ecutek system and a tune for about $1000, their is a reason its more expensive because they get paid :-)

[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.