Yes, I formatted it to FAT32. Let me try one of those files, I don't believe I was using any of those.

Tried both of the first C files with no luck. Just keeps doing the rainbow cycle, the OP2 that is. I know for a fact the logcfg file is in the root of the SD card. So can't think of what else can be off?

I just plug the cable in, car off. Put the log cfg file in, crank the car. Press the rear defogger and nothing. When I disconnect it and connect it again i get the logout.txt file. Any ideas?

The tactrix must not be connected to computer for this logging to work . connect it to obd port only, take log, remove then connect to pc to read.

comment out any triggers they are not reliable, with no triggers it will just run any time engine is on

Hmmm. Okay, didn't think being connected could have conflicted. ... and I'll go try it soon. THANK YOU!!!

remove or comment out any triggers they are unreliable, it will then just log any time engine is on,

once you get that working then try triggers, i dont use them more trouble than they are worth

I'm about to go out and try it. I'll remove the triggers and go from there. Give me a few and I'll report back.

Alright so, one thing I notice is that in the "logcfg" file there is MAF Voltage in there. However, in the log itself, I don't see any MAF Voltage being logged. Any ideas? Do I have to make any changes to the "logcfg" file, or perhaps need to use another "logcfg" file? Thanks.

have a look in the logcfg.out file it may give you some clues as to why.

otherwise try the other C series logcfg.txt or just copy the MAF_V parameters and scaling from that file to yours.

Can't find nothing that helps me there. I already tried two different logcfg files that log but none show MAF Voltage.

paramname = MAF_Voltage
paramid = 0xFFF842AC
databits = 16
scalingrpn = x,0.000076293945,*

That was it bud. Now works, and I was able to go do a bit of tuning. Can't thank you enough for all your help man, really appreciate it, and all others who pitched in here and there.:w00t:

No problem mate , happy to help, glad its sorted :clap:

Does anyone have the IDC logging on the B01C ROM? I tried using the params from post #1 but its not working for me. By the way, IPW does not log when using the defogger start stop param.

Try getting rid of any triggers, then it will just log as soon as engine starts.

Triggers have proved unreliable

Also try making your own B01C parameter file start with one of the A01C files and just substitute in the addresses for BO1C from the ram address list.

clean out any non used parameters as well, should work then

I don't have any issues logging. I want to log IDC. The A01C doesn't have IDC. I tried using what was written on page 1:

type = calc
paramname = IDC
scalingrpn = RPM,IPW,*,0.0008333333,*

This particular param doesn't log correctly.

those are just examples, and for wrx ecu from memory so not sure if scaling would be correct
as long as RPM and IPW are defined prior to that it should work

if the ram address is not in the list on that page then you only hope is to talk to @Td-d

I've successfully used this guide to update my 2013 FRS from 700c to b01c, and then flash the stage 1 OFT tune. I did a bit of logging with techstream and it seems like everything is in order. Thanks! If I could only get the romraider logger working I'd be set.

The romraider logging is not all sorted out yet, but you can use the standalone logging with an sd card in the tactrix using the logcfg file as in the first post

I made the same mistake trying to get Rom Raider to work. It works but pretty useless. I use the stand alone logging on the SD card with the Tactrix and it works great, as mentioned by Steve already.:party0030:

Td-d supplied me with some more RAM addresses for G series ROM just add them to your G series (A01G) logcfg file, look in the G series Romraider or ecuflash definition files for scalings.

I suspect not all have been tested

added them to original post as well

G Series ROM (A01G) RAM addresses supplied by @Td-d


E_AF_Correction_1_4byteExt_E81 FFF8A550
E_AF_Learning_1_4byteExt_E48 FFF8A6D4
E_AF_Sensor_1_4byteExt_E91 FFF8932C
E_Closed_Loop_Fueling_Target_4byteExt_E121 FFF8A634
E_Engine_Load_4ByteExt_E32 FFF89148
E_Engine_Speed_Delta_E157 FFF893FC
E_Feedback_Knock_Correction_4byteExt_E39 FFF8AFAC
E_Final_Fueling_Base_4byteExt_E123 FFF89F84
E_Fine_Learning_Knock_Correction_4byteExt_E41 FFF8B048
E_Fuel_Injector_1_Latency_4byteExt_E50 FFF89FC4
E_Fuel_Injector_1_Pulse_Width_4byteExt_E60 FFF887C8
E_IAM_4byteExt_E31 FFF8119C
E_Idle_Speed_Map_SelectionExt_E49 FFF8B630
E_Knock_Correction_Advance_4byteExt_E43 FFF8AFA8
E_Knock_Correction_Advance_Max_PrimaryExt_E118 FFF8B014
E_Manifold_Relative_Pressure_4byteExt_E113 FFF88F78
E_Manifold_Relative_Sea_Level_Pressure_4byteExt_E5 2 FFF88F74
E_Throttle_Plate_Opening_Angle_4byteExt_E38 FFF89030
E_Tipin_ThrottleExt_E54 FFF89038
RAM_EngineSpeed FFF893EC
Ram_AFR_Sensor_Heater_Protection_Result FFF88480
Ram_AFR_Sensor_Heating_Limit_Result FFF88478
Ram_AF_Correction_3_32bit_ECU FFF8A860
Ram_AF_Sensor_1_Current FFF89328
Ram_AF_Sensor_1_Resistance FFF89340
Ram_Accelerator_Pedal_Angle FFF8922C
Ram_Accelerator_Pedal_Angle_0 FFF8D2D0
Ram_Accelerator_Pedal_D FFF8D2C4
Ram_Accelerator_Pedal_E FFF8D2C8
Ram_Alternator_Duty FFF884A4
Ram_Ambient_Air_Temperature FFF8D2BC
Ram_Atmospheric_Pressure FFF8D290
Ram_Atmospheric_Pressure_1 FFF89B84
Ram_Base_Pulse_Width_times_100_0.84 FFF89CAC
Ram_Battery_Voltage FFF87C6C
Ram_Battery_Voltage_0 FFF8D29C
Ram_CFP_Delta FFF89048
Ram_CPC_Valve_Duty_Ratio FFF89CBC
Ram_Calculated_Base_Pulse_Width_ FFF89FC0
Ram_Catalyst_Temperature_Bank_1_Sensor_1 FFF8D298
Ram_Commanded_Secondary_Air_Status FFF8D2E5
Ram_CoolantTemperature FFF890A4
Ram_Coolant_Temperature FFF8D24C
Ram_Distance_Traveled_since_DTCs_cleared FFF813EE
Ram_Distance_Traveled_with_MIL_On FFF813EC
Ram_EVAP_Commanded_Purge FFF8D288
Ram_E_AF_Learning_1_4byteExt_Percentage FFF8D254
Ram_Engine_Load_Absolute FFF8D2A0
Ram_Engine_Load_Calculated FFF8D248
Ram_Engine_Oil_Temperature FFF8D2DC
Ram_Engine_Oil_Temperature_0 FFF87C74
Ram_Engine_Speed FFF89564
Ram_Engine_Speed_0 FFF8D25C
Ram_Exhaust_VVT_Retard_Angle_Left_ FFF8BFCC
Ram_Exhaust_VVT_Retard_Angle_Right_ FFF8BFC8
Ram_Fuel_Air_Commanded FFF8D2AC
Ram_Fuel_Injector_1_Pulse_Width FFF887D8
Ram_Fuel_Injector_1_Pulse_Width_4byteExt_E60??? FFF887F0
Ram_Fuel_Injector_2_Pulse_Width FFF887DC
Ram_Fuel_Level FFF8D28C
Ram_Fuel_Pressure_MPa FFF8936C
Ram_Fuel_Pump_Duty FFF8B09C
Ram_Fuel_Pump_Duty_0 FFF8BC20
Ram_Fuel_Rail_Pressure_direct_inject FFF8D27C
Ram_Fuel_System_1_Status FFF8D2E2
Ram_Fuel_System_2_Status FFF8D2E3
Ram_Fuel_Trim_1_Short_Term FFF8D250
Ram_Fuel_Type FFF8D2E6
Ram_Fueling_Mode? FFF88FA8
Ram_Fueling_Mode??? FFF8BC2F
Ram_High_Low_Load_0_L_1_H FFF8A060
Ram_Idle_Switch FFF8B4AE
Ram_Ignition_Total_Timing FFF8ACF4
Ram_Intake_Air_Temperature FFF8D268
Ram_Intake_Air_Temperature_0 FFF87C64
Ram_Intake_Manifold_Pressure FFF8D258
Ram_Intake_OCV_Current_Left FFF891B4
Ram_Intake_OCV_Current_Right FFF891A8
Ram_Intake_OCV_Duty_Left FFF8C090
Ram_Intake_OCV_Duty_Right FFF8C09C
Ram_Intake_Temp FFF890B4
Ram_Intake_VVT_Advance_Angle_Left FFF8BF84
Ram_Intake_VVT_Advance_Angle_Right FFF8BF80
Ram_Learning_1_Current_Range_A FFF8A6FC
Ram_Map_Delta? FFF8A19C
Ram_Mass_Airflow FFF89114
Ram_Mass_Airflow_0 FFF8D26C
Ram_Number_of_warm_ups_since_DTCs_cleared FFF826CE
Ram_Roughness_Monitor_Cylinder_1 FFF8CC11
Ram_Roughness_Monitor_Cylinder_2 FFF8CC12
Ram_Roughness_Monitor_Cylinder_3 FFF8CC13
Ram_Roughness_Monitor_Cylinder_4 FFF8CC14
Ram_Run_Time_Since_Engine_Start FFF84DB4
Ram_SI_Drive_Mode_I3_S1_SSharp2_ FFF88999
Ram_Throttle_Opening_Commanded FFF8D2CC
Ram_Throttle_Position FFF8D270
Ram_Throttle_Position_B FFF8D2C0
Ram_Throttle_Position_relative FFF8D2B4
Ram_Time_Run_with_MIL_On FFF813F0
Ram_Timing_Advance FFF8D264
Ram_Transient_Threshold_Testunk FFF8923C
Ram_Vehicle_Speed FFF8D260
Ram_Vehicle_Speed_0 FFF893C4

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?

Is there an oil temp logging entry pre-formatted for the A01C ROM logcfg.txt? I can find coolant and cat, but not oil. I know I can log with torque, but I'd rather do so with the OpenPort.

I'm sure there is, I'll pull the address for you.

RR-0.5.7
EcuFlash-1.44.4247

There's a newer RR version, try that one, might sort your issue out:

https://www.assembla.com/spaces/romr...C1-windows.zip

FFF8DC08 Ram_Engine_Oil_Temperature

@Td-d guy just sent me a new version Australian/European BRZ ROM

JA1JD00G from latest 2015 BRZ/86 manual in Oz but no douby will be out in Europe/South Africa as well soon unfortunately the structure appears different so will have to ask you for a definition :D

Its attached to first post in this thread (last ROM at end of attachments)

Thanks
Steve