Quote:
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