I’ve always wanted to get into arduinos, but this does not seem like a first time project. I guess it’s back to pulling the fuse.

See here


http://www.ft86club.com/forums/showp...7&postcount=30

ZA1JF00D
 

Uploading the stock ROM pulled from my MY2016 AT USDM FR-S (ZA1JF00D) in case anyone needs it.



Just flashed OFT stage 1 v4.03, it had a checksum error with the flash only definition I created (not sure why EcuFlash never asked for a checksum module in the definition creation wizard? :bonk:), so I flashed back to stock (without turning off the car) and tried again with Steve's K00G flash only xml from earlier in the thread with a few changes to suit my car and it worked great.



Big thanks to Steve!

Thanks ill add that stock rom to lust in first post soon

Thanks ill add that stock rom to lust in first post soon


If youd caf was F00D auto , you should use K01I for auto not K00G as that is manual car rom

For flash only I used this

<?xml version="1.0" encoding="UTF-8"?>
<rom>
<romid>
<xmlid>ZA1JF00D</xmlid>
<internalidaddress>8000</internalidaddress>
<internalidstring>ZA1JF00D</internalidstring>
<caseid>8644387107</caseid>
<year>2013</year>
<market>AUDM</market>
<make>Subaru</make>
<model>BRZ</model>
<submodel>FA20</submodel>
<transmission>AT</transmission>
<flashmethod>subarubrz</flashmethod>
<memmodel>SH72531</memmodel>
<checksummodule>subarudbw</checksummodule>
</romid>
<include>32BITBASE</include>
</rom>

Added 2017 Thailand manual K00R rom and USA auto F00D roms to stock rom lisy in first post

Came to ask this....

Nuts! Though could it be done with BRZedit? Though the dev would need to know he sequence used by OFT/ECUtek to do it and they're not likely to share the info...

Quick question: is it possible to dump an Ecutek ROM? My 86 has an AVO Turbo-Kit with an Ecutek tune on it. Was just digging into my STIs ROM, as I had to make a few changes and was curious to look at the 86 tune. But for some reason ECUflash is throwing an error, everytime I try to read the ECU.

*it is showing the actual VIN, just changed it for confidentiality reasons

No you canmpt read ecutek or brzedit tuned cars with tactrix, both those systems alter the seed key access routine to access ecu.


If the tuner would give you a copy of the unlocked ecutek rom, then you could chamge it but this would be unlikey​ to happen

Attaching a copy of my stock ROM (Cal ID ZA1JS10C), pulled from my 2019 BRZ 6MT USDM (Canada) with Red Manifold, in case anyone wants it.


Also, before messing up my car, I'm looking for a spare ECU. Please see my thread here: http://www.ft86club.com/forums/showthread.php?t=136476


Thanks
Mr.Fluke

Hey guys. Does anyone know what it means when the status lights on the OP2 stay solid red and green when connected to the OBDII? I tried changing the SD card already but there is no difference; I cant log anymore. I also tried contact tactrix but I think their email is down.

Check the obd connection by trting an ecu READ.


Make sure SD card is formatted fat 32 file system


Make sure the logcfg.txt is in the root directory and its name must be exact


If you edited the logcfg.txt tactrix coesnt like any control or formatting characters that some editors add.
try the original logcfg.txt file.


Make sure you jave latest version of ecuflash, one of the older versions the logging didnt work. So you need to update ecu flash then connect tactrix so it can update its firmware


Oh it wont log if it connected to computer must be standalone to log.


Check SD card see if it produces a logcfg.out file tgis may have some error messages in it

Well now that's interesting. The last set of data the OUT file had looked like this:

param name: Ram_GDI_Flow_Rate
param id: 0x00000000 <---WTH?
read width: 4 bytes
data width: 32 bits
data offset: 0 bits
float: 1
raw int: 0
signed int: 0
sign/magnitude int: 0
mode: 0x23
scaling: x

This was included in some of the RAM logging stuff that I added. I guess I forgot I did that. :bs: Anyway I removed those parameters that I added and I'm good to go again. Now on the thread I posted: http://www.ft86club.com/forums/showthread.php?t=137258
you asked that I log pulse width to see if it changes before the O2 or vice versa, which one is correct for logging pulse width on Za1jb01c?

;paramname = Base_Pulse_Width(ms?)
;paramid = 0xFFF89744
;isfloat = 1

;paramname = Fuel_Injector_1_Pulse_Width_4byteExt_E60
;paramid = 0xFFF887C8
;isfloat = 1

;paramname = Port_Injector_PW
;paramid = 0xFFF887C8
;isfloat = 1
;scalingrpn = x,0.001,*

;paramname = Port_Injector_PW_Ram
;paramid = 0xFFF887D8
;isfloat = 1
;scalingrpn = x,0.001,*

;paramname = Direct_Injector_PW
;paramid = 0xFFF887E8
;isfloat = 1

;paramname = Direct_Injector_PW_Ram
;paramid = 0xFFF887F0
;isfloat = 1

They are commented out because I couldn't get them working right. Also, will the O2 sensor sway wildly and hold lean or rich for days like that with no codes?

Also, would the O2 sensor still be affecting fueling even though I have it set to forced open loop?

Thanks!