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

[elBarto]

@steve99 : You seem like the flashing Guru here .

I was wondering can I flash a ZA1JD00G file (the one that @Shiv@Openflash recently released for the 2015 EU-MT) on my 2013 GT86 with CalID ZA1JA00G. I've hex-edited the Bin file to read A00G and edited the XML-definition to read A00G so I don't have errors in RomRaider, but I'm a little scared that I will break something if I flash it through OpenFlash Tablet.

I've also been reading your topic about the Australian Ron98 knock fix and used your findings to run my EUDM GT86 on ron95 with great success, so many thanks for that also

[ML]

the car doesn't car what version it came with, you can flash it with any version. I started with a01c and now am on b01c and its been fine.

[elBarto]

Originally Posted by ML

the car doesn't car what version it came with, you can flash it with any version. I started with a01c and now am on b01c and its been fine.

Thank you for the Answer

How did you flashed it?
I've been trying to upload it trough OpenFlash tablet but it doesn't want to upload it. Keep getting "not compliant" error even though it's been edited with a hex-editor to match A00G

Or am I missing something?

[ML]

Originally Posted by elBarto

Thank you for the Answer

How did you flashed it?
I've been trying to upload it trough OpenFlash tablet but it doesn't want to upload it. Keep getting "not compliant" error even though it's been edited with a hex-editor to match A00G

Or am I missing something?

ahhhhhhhh, well there is your problem. This only works with a Taxtrix device. OFT will only let you flash what ever your current version is. I figured you had a tactrix cable since you posted in the tactrix thread.

[elBarto]

Originally Posted by ML

ahhhhhhhh, well there is your problem. This only works with a Taxtrix device. OFT will only let you flash what ever your current version is. I figured you had a tactrix cable since you posted in the tactrix thread.

Bummer. I posted it here because the Tactrix guys are the Bin Wizards

[Td-d]

All you guys hex editing the CAL id's are cruising for a bruising . There are changes between the various releases of the roms, meaning the addresses of the tables and parameters have shifted around. If you change the cal id so that it reads using a definition that was not made for that rom, you risk editing parts of the rom that may land up bricking the ecu. Don't do it.

In any case, there is a def for D00G - why not just use it?

[steve99]

Originally Posted by elBarto

@steve99 : You seem like the flashing Guru here .

I was wondering can I flash a ZA1JD00G file (the one that @Shiv@Openflash recently released for the 2015 EU-MT) on my 2013 GT86 with CalID ZA1JA00G. I've hex-edited the Bin file to read A00G and edited the XML-definition to read A00G so I don't have errors in RomRaider, but I'm a little scared that I will break something if I flash it through OpenFlash Tablet.

I've also been reading your topic about the Australian Ron98 knock fix and used your findings to run my EUDM GT86 on ron95 with great success, so many thanks for that also

As per @Td-d post changing calid can be done but its full of hidden traps and pitfalls best to leave it alone and wait for the experts at OpenFlash OFT to release the correctly modified ROM's and matching definitions.

As @Td-d says if you have tactrix you don't need to worry just use the matching D00G definition, but if you have OFT its best to wait for the official release unless your are very sure of what you are doing. or your stock ROM was a D00G then it will load fine with OFT without doing anything.

The OFT has a protection feature to stop you loading ROM's with a different calid, it was put their for good reason.

[elBarto]

Originally Posted by steve99

As per @Td-d post changing calid can be done but its full of hidden traps and pitfalls best to leave it alone and wait for the experts at OpenFlash OFT to release the correctly modified ROM's and matching definitions.

I agree, the 2015 D00G rom has to many changes compared to the A00G roms, unless you really really know what you are doing, stay away from editing the CalID. The risk of bricking your ECU is too big.

[fanaticalz]

went ahead and flashed the oft 2.05 stage 2 uel 91 octane tune. i think everything is alright, but i'm kind of curious what i'd be looking for in the data logs to see if anything was out of order.

i was able to do a WOT 2k to 7k 3rd gear pull:

http://datazap.me/u/fanaticalz/oft-2...?log=0&data=10

perrin drop in filter
tsudo uel header
stock op/fp
perrin 3" catback

[steve99]

Originally Posted by fanaticalz

went ahead and flashed the oft 2.05 stage 2 uel 91 octane tune. i think everything is alright, but i'm kind of curious what i'd be looking for in the data logs to see if anything was out of order.

i was able to do a WOT 2k to 7k 3rd gear pull:

http://datazap.me/u/fanaticalz/oft-2...?log=0&data=10

perrin drop in filter
tsudo uel header
stock op/fp
perrin 3" catback

read links below should provide all the info you need

[Toyota John]

I am confused on logging with the Tactrix op2. I formatted the SD card I have but what do i put into it?

[steve99]

Originally Posted by Toyota John

I am confused on logging with the Tactrix op2. I formatted the SD card I have but what do i put into it?

See first post. you need to have a files logcfg.txt in the root directory.

It contains the RAM addresses you want the op2 to interrogate to create the log . The ram addresses are different for each ROM and revision.


looks something like this for a A01C

_________________________________________

type = obd
protocolid = 6 ; ISO15765
mode23txaddrwidth = 4 ; mode23 req format info
mode23txlenwidth = 1 ; mode23 req format info
mode23rxaddrwidth = 0 ; mode23 req format info
mode23uds = 1 ; lets OBD channels know you are using mode23 UDS
sortpids = 1 ; sort these PIDs by value to potentially make for fewer requests (=faster)
calcsampinterval = 1000 ; timing parameter - leave as is - will make default for release version

; here are some known RAM addresses for ROM ZA1JA00C
; addresses are likely different for other ROMs
; you can comment out ones you don't need, but keep in mind that with
; the block read nature of UDS, reading extra parameters that have
; adjacent addresses comes at very little bandwidth (=sample rate) cost


paramname = RPM
paramid = 0xFFF8DB80
isfloat = 1


paramname = accel_pedal_angle
paramid = 0xFFF8922C
isfloat = 1

paramname = throttleplate_angle
paramid = 0xFFF89030
isfloat = 1




;Colby
paramname = MAF_default
paramid = 0xFFF8DB90
isfloat = 1


;TD-d
paramname = MAF_Tdd
paramid = 0xFFF89114
isfloat = 1

paramname = load
paramid = 0xFFF8DB6C
isfloat = 1


paramname = IAT
paramid = 0xFFF8DB8C
isfloat = 1



paramname = advance
paramid = 0xFFF8DB88
isfloat = 1



paramname = KC_learned_value
paramid = 0xFFF8B0AC
isfloat = 1

paramname = fine_knock_correct
paramid = 0xFFF8B14C
isfloat = 1

paramname = feedback_knock_correction
paramid = 0xFFF8B0B0
isfloat = 1



paramname = AFR
paramid = 0xFFF8932C

isfloat = 1

scalingrpn = x,14.7,*

paramname = STFT
paramid = 0xFFF8DB74
isfloat = 1

paramname = LTFT
paramid = 0xFFF8DB78
isfloat = 1

paramname = MAP
paramid = 0xFFF8DB7C
isfloat = 1

paramname = IAM
paramid = 0xFFF816F4
isfloat = 1

paramname = speed_KMH
paramid = 0xFFF8DB84
isfloat = 1

paramname = cool_temp
paramid = 0xFFF8DB70
isfloat = 1

paramname = fuel_press
paramid = 0xFFF8DBA0
isfloat = 1

paramname = lambda
paramid = 0xFFF8DBA4
isfloat = 1

paramname = O2_volt
paramid = 0xFFF8DBA8
isfloat = 1

paramname = O2_curr
paramid = 0xFFF8DBB8
isfloat = 1

paramname = cat_temp
paramid = 0xFFF8DBBC
isfloat = 1

;paramname = ECU_volt
;paramid = 0xFFF8DBC0
;isfloat = 1

paramname = abs_load
paramid = 0xFFF8DBC4
isfloat = 1


paramname = requested_torque
paramid = 0xFFF8B490
isfloat = 1

paramname = engine_load
paramid = 0xFFF89148
isfloat = 1

paramname = ignition_total_timing
paramid = 0xFFF8ADF8
isfloat = 1


paramname = requested_torque
paramid = 0xFFF8B490
isfloat = 1

paramname = gear
paramid = 0xFFF895D9
databits = 8


; Defogger switch for logging start/stop
paramname = defog
paramid = 0xFFF89393
databits = 8

conditionrpn = defog,1,==
action = start

conditionrpn = defog,0,==
action = stop

[steve99]

Has anyone managed to flash a D00G rom to a car that came with A01G or earlier rom ??

[d1ck]

Originally Posted by steve99

Has anyone managed to flash a D00G rom to a car that came with A01G or earlier rom ??

I was thinking about trying it, but I saw your other post and I think I'll wait until it gets cleared up.

Also, has anyone got the romraider logger working yet?