Will the OFT tune Stage2 EL E85 map which is part of this zip folder http://www.procedetuning.com/BRZ_FR-S/downloads-4/files/OFT%20FA20%20ROMS%20v1_34beta.zip


Can this tune be successfully applied to a 2013 FR-S series 10 w Auto Trans using the tactrix cable & software ?


I trust my tuner but want to be more than 99% sure he's got this right

Tactrix Ecuflash will write any un-encrypted rom in correct format to any BRZ/86/FRS regardless of whether its correct ROM type for your car so you need to know your original rom series. Have a read of original post

re E85 read here

http://www.ft86club.com/forums/showthread.php?t=67310

Ty Steve99
 

I read all those posts and that is what led me to want to get that ROM for my stock FR-S.. sounds almost too good to be true..


I know about staying closed loop for the first 10 miles or so & about oil specs & change interval's.


My main concern is getting a "bad" flash.


I'm an IT pro since 1978 and I know motherboards can be bricked if a ROM erase/write goes bad. I also know that different file formats can play havoc with some programs too.


That's why I was wondering if anyone has taken an OFT tune and used it with another flash program (other than the little OFT box) to successfully write an ECU on the twins.


LMK TY

Yes, it has been done.

as an it pro since 1978 you should know that erase/write has nothing to do with the tune/rom. it depends on how good your cable is, how well connection is made (eg, plugged it all the way in, or bent pins, etc), how well your laptop is running and provides proper voltage without interruption.

as for file formats - all tuning programs can open and then write raw binary format (also called opened). this is basically just a one-to-one byte-by-byte snapshot of ecu rom which then may have been modified (tuning process).

I was in the middle of a flash when the battery in my laptop died. I was pretty lucky that I was still able to get it home on half a flash. It was pretty scary though! I re-wrote the ROM after getting the battery charged up and I was good to go!

Apologies if my newbie status is showing here but just looking at the files relating to G series ROM and just trying to understand how parameters are added etc.

The list below are 10 of the 34 parameters from the G SERIES ROM logcfg.txt example that I cannot see listed in G series ROM RAM addresses.txt file. So my question is, where do these addresses come from? Is there a generic list which covers all ROM's not just the G Series?

FFF8A8A0 AF_Learn_3
FFF8AD70 BaseTiming
FFF89393 Defogger
FFF887E8 Direct_IPW_0
FFF87C68 ECT
FFF8B066 FLKC_Offset
FFF87C70 MAF
FFF842AC MAF_V
FFF87C60 MAP
FFF8AB08 Tip_In_Enrich

I've had no issues getting the example cfg file dumping data to the SD card on my tactrix so thanks for the guide Steve.

As this is opensource stuff its just what the guru,s dig up after countless hours of reverse engineering the ecu code, Td-d appears to do the lions share of this work aver at romraider . The G series logcfg i posted was given to me by onother chap who hunted arround in the ecu code ztan who appears to have retired now so its likely he dug up some different parameters. The lasest ones i posted from Td-d will need testing as he does not own a BRZ think he has wrx sti.

sometimesits just a different name eg ECT as oposed to engine coolant temp or similar

Ah all good then. Smart blokes!

Anybody else noticing that setting the port ratio table doesn't seem to affect the port ratio? I've got all three tables set to 25% port from 2400 rpm to redline, but on the logger I'm still seeing 100% direct from 3200 - 4800 rpm.

@D-VO and @solidONE should compare notes you may have similar issues ?

I just upped the user level and it worked fine.

I have mine set to developer. Same crap. I just changed the load to 2.50 to see if that makes a difference, but haven't had a chance to test yet.

What version RR are you using, D-VO?