No, it just means that the ECU is compatible with those ROM versions. Go get a B01D file, edit that and flash that onto the ECU. That way you have all the updated changes made by the OEM that we can't see etc.

I am having a problem reading my current ROM. I hope I can find some help.

I just received my tactrix and have the 32bitbase file in the correct directory. My car has the B01D calibration ID, so I have the raw definition in brz/2012/2013/2014 folders. ECUFLASH reads the current rom, but it says there are no definition files for the rom. I save it as .bin and try to open in Romraider with the specific romraider definition file and it still says no matching ecu definitions. And there's no Rom Metadata for the read in ECUFLASH.

Is there something I'm overlooking? Thanks!
http://i.imgur.com/tCe3ZTl.png
http://i.imgur.com/I3AtrOI.png
http://i.imgur.com/LbAxejB.png
http://i.imgur.com/XSi51BK.png
http://i.imgur.com/6aesgdv.png
http://i.imgur.com/ZeBSCKb.png

post up the rom image you saved and ill look at it. It probably been tuned previously with a calid hacked rom




Id also download the latest 32bitbase and B01D Ecuflash definitons from the github site




the error message your getting saving your rom as .bin is normal ,about the padding. Just click yes to save as bin


also try opening a stock B01D rom that attached to first post in this thread, see if that will open.


If not update your 32bitbase and defs from github

Added ZA1JK00P 2017 Australian manual new logic rom for udated car with red intake manifold

Added ZA1JK01I
2017 auto European

Ecuflash Definition file for 2017 BRZ MT Chinese Market ID ZA1JK00N
 

Hi everyone

can someone help me out with the definition file for 2017 BRZ MT foe the Chinese Market , calibration ID : ZA1JK00N

Attached is the Stock file

appreciate any help

Cheers

Hi
I believe this is the rom from my car :thumbsup:
Still having trouble with the definition file for this thing, its the old logic but doesnt match any of the old definition files. Attempted reverse engineering the rom using IDA but its a little beyond my current understanding. Anyone know an easier way to identify the tables if they should be similar to a previous rom?

Unfortunatly very few people possess both the skills and time to reverse engineer these roms and find the tavles and logging addresses.

Basicly one guy on ghe planet tdd over at romraider, and i think hes swamped and has a real job to do as well.

If your in a hurry your going to have to buy brzedit, ecutek or oft.

There will be large chunks of tables with similar data, but at locations offset from earlier roms.

ScoobyRom might help.

Thanks everyone for the responses in the posts above. It looks like the community could do with a few more hackers 😉
I have a feeling the oft guys dont have a working rom for this id either, I emailed shiv as that would be my preferred option over ecutek.
I'll have a go with ScoobyRom it looks promising and see how far I can get. Hopefully post findings and guidance back to the forum incase anyone else fancies giving it a go on any new roms. Cheers.

More people isn't what you need, it's time (and/or money).

As the auto and even the manuals in europe did not get the updates like the australian and usa red manifold . You may be in luck and you may be able to flash in the older A01I rom to your car which is definied and has log addresses.

Now this involves some risk.
I did this to a K00P manual here flashed an A01G, now the car did not start , but recovery was to reflash original K00P and resync security. Its jist looping a couple of pins on obd port for 30 min.
All good car recovered and all ok.

Now as your car is old rom logic its possible the older rom will work in your car.
And if not you should be able to recover like i did.

You can make up a flash only definition, see first post in this thread for you K01I rom.

Do that and confirm you can reflash your stock rom.

Then try flashing A01I older rom

If car starts runs, log and check all ok, happy days you can now tune

Car wont start reflash original K01I
And then most likely ecu security resync proceedure
Full info here
http://www.ft86club.com/forums/showthread.php?t=102810

You wont need to worry about vin or other stuff just reflash K01I

Then loop pins and wait 30 mins

7. Turn OFF ignition
8. Loop pins 4 and 13 on OBD port in car (this puts control units in comms mode)
9. Turn ignition to full ON position with working key or for keyless fob in car and two pushes of start button (in park or not pressing clutch) DO NOT TRY TO START car, DO NOT remove FOB from car during the 30 minute period.

To be really safe here make sure everything electrical is off in car radio, fans lights ect have the drivers window down and doors closed. Reach in through window to operate ignition at start and end of 30 minute period. Because when you open door window does the jump/up/down ie electrical load/spikes .

10. Wait at least 30 minutes (the CEL light should flash if pins looped successfully)
11. turn OFF ignition (again reaching through window not opening door)
12. Remove loop on OBD port pins 4 to 13
13. Start car let it run for more than 5 seconds.
14. Enjoy your car.


Now i cannot offer you a 100% guaranee, however i did this on a 2017 manaual car and recovered. So sgould be same for 2017 auto

It's not too bad.

MAF IAT Comp
B8DF4 107C28 107C40 107C68

MAF Load Comp
B8E2C 107CB8 107CF0 107D38

GDI Firing Angles
BB68C 112958 112984 1129C8
BB6A8
BB6C4
BB6E0
BB6FC 112E08 112E34 112E78

GDI Pressure Multiplier A
BB718 112F34 112F58 112F80

GDI Pressure Target B
BB76C 113004 113040 113084

Injector Ratios
BB814 1132B8 1132E8 113310
BB830 113388 1133B8 1133E0
BB84C 113458 113488 1134B0

Primary OL Fuel
BBA34 1139D0 113A04 113A60

OL Fuel Additive
BBA6C 113BA0 1138D4 113C30

GDI Pressure Multiplier B
BBC9C 1145DC 114600 114628

Cranking
BBD28
BBD44
BBD60
BBD7C
BBD98
BBDB4
BBDD0
BBDEC
BBE08
BBE24

Closed Loop Fuel
BC2EC 1160F8 116124 116150
BC308 116244 116270 11629C

Base Timing A?
BCE98 119E4C 119E84 119EE0
Base Timing B?
BCEB4 11A024 11A05C 11A0B8

Timing Compensation (IAT) Activation
BCFB0 11A29C 11A2BC 11A2D0

Catalyst Warm Up Idle
BD058
BD090

Transient Ignition Retard
BD0E4 11A63C 11A65C 11A6BC

Timing Compensation Per Cylinder
BD18C 11A8D0 11A910 11A928
BD1A8 11A988 11A9C8 11A9E0
BD1C4 11AA40 11AA80 11AA98
BD1E0 11AAF8 11AB38 11AB50

Knock Correction A
BD26C 11AC0C 11AC44 11ACA0

Desired Overrun Mass Airflow A
BDD08 11D95C 11D9B0 11D9F0
Desired Overrun Mass Airflow B
BDD40 11DCA8 11DCFC 11DD3C

Idle Speed Stability A
BDDB0 11E024 11E084 11E0B0
Idle Speed Stability B
BDDCC 11E2C0 11E320 11E34C

MAF Correction After Start
BDF3C 11ED04 11ED30 11ED50
BDF58 11EE00 11EE2C 11EE4C

Target Throttle Plate Position Maximum
BE1E8 13C76C 13C7C0 13C81C

Requested Torque B
BE290 13CC9C 13CCDC 13CD38

Requested Torque A
BE4B4

Intake Cam Advance Safe
BF18C 125BFC 125C3C 125C9C

Intake Cam Advance Normal
BF1A8

Intake Cam Advance Base
BF1C4

Exhaust Retard Base
BF1FC

Exhaust Cam Retard Normal
BF368

Exhaust Cam Retard Safe
BF384 126E84 126EC4 126F24


Fuel Multiplier Display Offset
B7DE8 101CF8 101D0C

Requested Torque Base
BE0F0 13C498 13C4F4

MAF Scale
BEA30 122444 12251C

Fantastic info steve, I have some friends who are big into mapping and ecu recovery so I will have this with me when we attempt to do mine.

Wow! I had the day off today to look into this but you beat me to it. On with creating a definition file for me :)


How do you 'thank' a post on here?

I think you need 10 posts or something before thank button shows up

The reason for A01I is it will work in all 2012-2016 auto cars that came with I roms

Same with manuals A01G will work in all 2012-2016 manual

This is confirmed

All ecu even 2017 is same processor and appears to be same hardwsre worldwide

Their are usa guys running G roms in cars that came with C roms originally

I'd prefer this approach to try A01 and make the K00D/G/I redundant, but perhaps there are quite a few more hardware changes in MY17 than happened in MY15 that the K00x roms might need to be mapped anyway to pull out things like the updated transient ignition retard injector compensations, not to mention all the unmapped stuff, etc. Having said that, most of those changes will appear and could be pulled out of K00G anyway.

The EU MY17 ROMs are more similar to the MY15 G series, although there are still differences. Perhaps that definition is a better starting point.

Better starting point is the K00G def, as some tables will have identical locations.

Cleaned up that K00G def that was uploaded, added the missing tables.

Looks like EU MY17 got the 4.3 FD.

Around 120 tables done so far, in around 6-8 hours.

No, still the 4.1 I'm afraid.

Wayno sent me the MY17 EU AT stage 1 rom and definition last night, excited to get it loaded and start logging.
Legend!

AU 6AT MY17

It has been changed to a 4.3. Guy in our group (Belgium) had a 2016 BRZ after 2 or 3 months the car was totaled by an old lady and he bought a 2017 BRZ, he confirmed the FD change, also the change in suspension setup.

Added ZA1JK00S 2017 Auto Australian rom to first post as supplied by wayno.


note the K00S and the K01I auto roms are interchangeable

Interesting, the MY17 BRZ spec change info state otherwise.

Can anyone help with a definition for JDM 2012 MT ZA1J700A?

I did some research and unfortunately there's very little information available on ZA1J700A. From what I found (http://minkara.carview.co.jp/userid/...262/parts.aspx), this ROM is compatible with ZA1JA01A (and possible ZA1JA02A).

I managed to read it using ZA1JA01A definition, however not sure how save this solution would be.

Any advice is highly appreciated.

Sounds like you have a japanese import ?? If it runs the same ax other countries then 700A A01A and A02A will ve compatable. Id flash the A02A rom if your staying stock.

Reading amd writing is pretty safe as all roms from all countries are same basic size amd flashmethod. However editing is different story defs must match exactly.

If you want to tune the car you might want ro try flashing a A01G from australia\europe their is rearly good definitions for that rom series and its highly likely it will run fine in your car.

If theirs any dramas jist make sure you keep a copy of your A series rom to flash back.

+1. make your life easy, switch to A01G

Thanks man, this is what I thought. Yes, this it is Japanese import, so I think I'll just flash to A02A rom for now (need that fix for DI issue, already replaced the seals once) and will be looking into OFT Stage 1.

Do you guys have any experience using OFT roms with OpenPort 2 cable?

So I've bent my pins in and haven't noticed any connection losses yet I'm still getting a ton of log files during one drive. I have no issues running a Bluetooth odb2 logger with torque but this always has issues. Here's a link to my files from a 30ish minute drive.

https://drive.google.com/folderview?...AsAd-jH69D2O3m

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

I had the same problem on mine. Bending pins didn’t help much either. A heavy rubber band seemed to help. I ended up getting a 6ft extension and ran it into the glovebox so it’s easier to access and it has a solid connection.

Here is the exact cable I ordered:
https://www.amazon.com/dp/B0716RW33M

have you also removed any triggers in the logcfg.txt file they are unreliable

i only have the trigger for if rpm over 0. I was under the impression that you had to have that otherwise it wouldnt log. the rear defroster trigger is 100% worthless i know that.

Thats strange , ive always run with no triggers, and nothing refering to triggers.

Just either plug in tactrix, or switch power on to it via switched cable when i want to log

If it creates a bunch of log files like that its likely the connection to obd port is intermittent. Try bending both roms of pins inwards, use say an old SD memory card so you keep the pins in straight line, onlt need to bend them vert slightly like 0.5mm or so

Triggers never worked for me either. When no triggers are set it logs at all times. I do however log the defogger switch and use it to tag the parts of the log I am interested. I then use a PowerShell script to extract the parts of the log that have the defogger enabled into individual log files.

Trigger based on oil temp works for me. Tactrix begins logging when my engine is warm. :-) Currently on the tab right now. I'll post my logcfg.txt when I'm back at the computer. Stay tuned.

Remember to use the pointers/ids from your corresponding calid.

Here you are:

You have your trigger set to OilTemp but the paramid for OilTemp is missing. Maybe it is working for you because it’s dropping the miss-configured trigger and you’re actually logging all the time.

Or maybe you just didn’t post your entire config... or maybe I am blind (reading on my phone) and OilTemp is in there somewhere. Hahaha

∆ this :-)