Originally Posted by D-VO (Post 3266778)

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!

Originally Posted by steve99 (Post 3266817)

Your car would run rinson an A01G rom if needed ie to go flex or get the increased logging ability

Originally Posted by D-VO (Post 3267123)

OK thanks! But what's rins?

Originally Posted by tomm.brz (Post 3281421)

If you flashed stage 1 ots, it should be already a k00g inside
Maybe try put the cfg on the tactrix s microsd for k00g and should log

Originally Posted by Td-d (Post 3281423)

Padding the bin is normal. I could define this rom for you and pull the logging addresses out, slowing down for the year.


Sent from my iPhone using Tapatalk

Originally Posted by hifiguy99 (Post 3281432)

Eh I am using the OTS ROMs anyways, which are based on K00G. Are you talking about defining the ZA1JS00C rom?

Originally Posted by hifiguy99 (Post 3281415)

Hello all, not sure who can answer this so maybe @steve99 can help clarify this :D

So I recently picked up a Tactrix OP2 to flash OFT OTS tunes.
I downloaded the ROM for my car (Cal ID: ZA1JS00C) and the definitions off Open Flash's website, used the RR2EcuFlash utility to get the EcuFlash definitions. I flashed the OTS Stage 1 ROM using the definition, it flashed fine and the car runs great on 93. However, I have few questions.

The first of which is logging on the car. I am under impression that logging is only defined for ZA1JK00G (http://www.romraider.com/forum/viewt...p?f=34&t=13808)

My car is a 2019 USDM 6MT CAL ID: ZA1JS00C, so how do I go about logging? I assume the RAM addresses haven't been defined for ZA1JS00C, so is it possible to flash ZA1JK00G? Would anything break/not work correctly/get bricked if I did so? And is it as simple as taking the ZA1JK00G OTS ROM and definition and just flash it with EcuFlash?


The second question I have is that when I extracted the stock ROM, it worked fine and I got the SRF and I was able to save it just fine. However, when I tried saving it as a BIN, it complains and wants to apply zero-padding. Is my ROM fine? I have attached it. If it isn't, can I get a working ZA1JS00C stock ROM?

Thanks!

Originally Posted by steve99 (Post 3281902)

All the manual 2017+ car oft roms are all based on the K00G base rom jist calid hacked to look like different roms.


With ractrix its easier\safer to jist flash the Base K00G based tunes and use K00G defs so your not dealing with jacked roms amd defs.


And ues you should be avle to log with ghe K00G logcfg.txt file
Grab it from first post but unzip amd the rename to logcfg.txt

Originally Posted by hifiguy99 (Post 3281415)

Hello all, not sure who can answer this so maybe @steve99 can help clarify this :D

So I recently picked up a Tactrix OP2 to flash OFT OTS tunes.
I downloaded the ROM for my car (Cal ID: ZA1JS00C) and the definitions off Open Flash's website, used the RR2EcuFlash utility to get the EcuFlash definitions. I flashed the OTS Stage 1 ROM using the definition, it flashed fine and the car runs great on 93. However, I have few questions.

The first of which is logging on the car. I am under impression that logging is only defined for ZA1JK00G (http://www.romraider.com/forum/viewt...p?f=34&t=13808)

My car is a 2019 USDM 6MT CAL ID: ZA1JS00C, so how do I go about logging? I assume the RAM addresses haven't been defined for ZA1JS00C, so is it possible to flash ZA1JK00G? Would anything break/not work correctly/get bricked if I did so? And is it as simple as taking the ZA1JK00G OTS ROM and definition and just flash it with EcuFlash?


The second question I have is that when I extracted the stock ROM, it worked fine and I got the SRF and I was able to save it just fine. However, when I tried saving it as a BIN, it complains and wants to apply zero-padding. Is my ROM fine? I have attached it. If it isn't, can I get a working ZA1JS00C stock ROM?

Thanks!

Originally Posted by hifiguy99 (Post 3295267)

Okay, I have another question. How do I flash back to stock? I opened the ROM in ecuflash but it is complaining about not having the correct definitions.

Reason for me going back to stock is I want to head to the dealer to see if I can get some stuff repaired under warranty. If I can't flash it back should I just wing it and see if they won't notice?

Thanks