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

[Td-d]

Originally Posted by Kodename47

@Td-d feel free to update your github with my defs. They were all originally based on your latest definitions.

Thanks for that, will do when I get some time this weekend maybe. Outside of doing the Ecuflash defs as metric some time back, just have not had the bandwidth to allocate to it, rather time consuming...

[aagun]

THX ^^

I update my rom ja01j

</table>
    <table name="Base Timing Idle (In-Gear)(Above Speed Threshold)" storageaddress="1159F8">
      <table type="X Axis" storageaddress="1159C8" />
      <table type="Y Axis" storageaddress="1159F0" />
    </table>

Originally Posted by Kodename47

After the last complaint, I have done a complete set of cross checking and fully defining what may reasonably be required. As I possibly have the most defined G series definition, I have gone through C,D and I and defined all the same tables. The folder structure may be different to others but I have tried to stick to Romraider's native naming structure where possible. I have checked that all tables are directly comparable. The links below have been updated. The only things that I now can't define easily are the CEL codes, although if anyone needs any that aren't defined then I'll see what I can do

The main updates:
All cranking tables defined (A through to J)
All Idle Tables (A through to I)
CL/OL Delay tables specific to AT or MT
Rev Limit B
Idle Ignition Timing specific to AT and MT
Idle Throttle Targets & Failsafe

If you downloaded on my last update, I would suggest that you download again.

[aagun]

Originally Posted by Td-d

Are we talking tables, or logging parameters? Normally, AVCS is not at play during idle for a range of reasons (oil pressure not being the least of them).

If it's tables, PM me, and maybe I can help.

i ganna email you about what what i have information about AVCS

[Td-d]

ZA1JF10G is up: http://www.romraider.com/forum/viewt...p?f=34&t=12178

[Td-d]

I've also ported the LC/FFS code across for the OFT

[steve99]

Originally Posted by Td-d

I've also ported the LC/FFS code across for the OFT

Hi @Td-d noticed the new F01C def on github has LC/FFS tables if someone tries to edit those parameters (insert values) a stock non patched rom its probably bricked ecu .

Would it be better if standard defs had those tables removed from def ?

thanks

[Td-d]

Yeah, ideally they should not be in there for a stock rom - but no, it won't do anything even if you do edit it erroneously - the code is in empty space in the rom, so all you would be doing is changing a couple of long words, which are not referenced, from 0xFFFFFFFF to whatever the float value is.

[benk]

Is there a DI injector scalar somewhere in the ROM? The "GDI Flow Rate" table appears to be a correction factor? Surely the injector rate is no 1cc/sec @ 20MPa, 1.2V

[steve99]

Originally Posted by benk

Is there a DI injector scalar somewhere in the ROM? The "GDI Flow Rate" table appears to be a correction factor? Surely the injector rate is no 1cc/sec @ 20MPa, 1.2V

gdi pressure multiplier check our the differences between an oft petrol and e85 rom is the easiest way thier is also a injector scalar to the pi

[benk]

Originally Posted by steve99

gdi pressure multiplier check our the differences between an oft petrol and e85 rom is the easiest way thier is also a injector scalar to the pi

Sorry what I meant was has anyone discovered the DI injector Scalar, I can see the GDI Pressure Multiplier tables, but surely they multiply a scalar that's yet to be mapped?


Anyone got a disassembly handy?

[Kodename47]

Originally Posted by benk

Sorry what I meant was has anyone discovered the DI injector Scalar, I can see the GDI Pressure Multiplier tables, but surely they multiply a scalar that's yet to be mapped?

The DI maps relating to DI flow & injection are:
GDI Flow rate (Probably the one you want)
GDI Pressure Targets A & B
GDI Pressure Multipliers A & B

[ztan]

Originally Posted by benk

Sorry what I meant was has anyone discovered the DI injector Scalar, I can see the GDI Pressure Multiplier tables, but surely they multiply a scalar that's yet to be mapped?


Anyone got a disassembly handy?

A01G:
There is also another scalar which is used to multiply with the result of GDI Multipliers A and B before the value is passed to the GDI flow table:

<table name="GDI Pressure Multiplier C" storageaddress="10C614">
    </table>
    
<table type="2D" name="GDI Pressure Multiplier C" category="Fueling - GDI" storagetype="float" endian="little" sizey="1" userlevel="4">
      <scaling units="" expression="x" to_byte="x" format="0.0000" fineincrement=".0001" coarseincrement="0.01" />
     <table type="Static Y Axis" name="GDI Pressure Multiplier C" sizey="1">
    <data>Value</data>
    </table> 
    <description>Multiplies GDI Pressure Multipliers A and B before passing value to GDI Flow Table.</description>
    </table>

[benk]

has anyone had issues logging a ZA1JD00G with Tactrix and the G-series logcfg.txt from the first post? I have it logging data (LED's flash differently from the first post, just fast flashing all colours) but the data is wrong. Could the RAM address be different for late 2014/2015 ROM or perhaps I just have it setup wrong...


EDIT: found it here http://www.ft86club.com/forums/showp...&postcount=178

[steve99]

Originally Posted by benk

has anyone had issues logging a ZA1JD00G with Tactrix and the G-series logcfg.txt from the first post? I have it logging data (LED's flash differently from the first post, just fast flashing all colours) but the data is wrong. Could the RAM address be different for late 2014/2015 ROM or perhaps I just have it setup wrong...

The ram addresses are different for the D00G rom, the g series logcfg.txt files is for A01G rom.

their is a dump of doog ram addresses in the first post you will need to substitute in the appropiate addresses into the old logcfg.txt files.

thge tactrix should recognise that old file it will just log incorrect, if its just doing the rainbow colours and not producing a log file or the error file its not connecting to ecu of your logcfg.txt is wrong

the file must be called logcfg.txt not logcfg.txt.txt or something and it must be in root directory.
dont edit it with a fancy text editor like word, just use notepad so no extra characters are added like formatting stuff.