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

[D-VO]

Theorizing for an answer to why at .70 load is so lean when the ECT is 65 - 144 degrees F. I was trying to run open loop to correct fueling issues under certain conditions, but its not working out.

[ztan]

Originally Posted by D-VO

Hey guys. QQ for you: Where exactly does the 'GDI Firing Angle Low Load Cold' become effective? Its a little confusing. Why would there be a designation of "High Load" and "Low Load" if both tables have an X-Axis of 0.20 -> 1.20 load? Also, where does "cold" start and end? @Td-d @Kodename47 @ztan Maybe??

A01G:

High and Low Load switch is based on a value at FFF8A060 (1=high load table). Have not been able to trace where this gets set, I was wondering if it related to A/C on or off.

Cold/Hot switch for these tables is based at FFF89F42 (1=cold table). Again, I have not traced where this gets set - a lot of the RAM switches are set based on indirect referencing and can't be looked up easily.

[ztan]

Originally Posted by ztan

A01G:

High and Low Load switch is based on a value at FFF8A060 (1=high load table). Have not been able to trace where this gets set, I was wondering if it related to A/C on or off.

Cold/Hot switch for these tables is based at FFF89F42 (1=cold table). Again, I have not traced where this gets set - a lot of the RAM switches are set based on indirect referencing and can't be looked up easily.

Looked at disassembly for A01G:

I think the Hot/Cold Tables are defined the wrong way around.
From sub 56ECC:

FFF89F42 is set to 1 when ECT>60 (at 10C5C8) and 0 when ECT<55 (at 10C5CC).

Cold tables (as defined) used when FFF89F42 = 1


Updated A01G def:

<table name="GDI Firing Angle Idle" storageaddress="110440">
      <table type="X Axis" storageaddress="1103D0" />
      <table type="Y Axis" storageaddress="1103FC" />
    </table>
    <table name="GDI Firing Angle High Load Hot" storageaddress="11056C">
      <table type="X Axis" storageaddress="1104FC" />
      <table type="Y Axis" storageaddress="110528" />
    </table>
    <table name="GDI Firing Angle High Load Cold" storageaddress="110698">
      <table type="X Axis" storageaddress="110628" />
      <table type="Y Axis" storageaddress="110654" />
    </table>
    <table name="GDI Firing Angle Low Load Hot" storageaddress="1107C4">
      <table type="X Axis" storageaddress="110754" />
      <table type="Y Axis" storageaddress="110780" />
    </table>
    <table name="GDI Firing Angle Low Load Cold" storageaddress="1108F0">
      <table type="X Axis" storageaddress="110880" />
      <table type="Y Axis" storageaddress="1108AC" />
    </table>

[Td-d]

Yup, you're right... that's what comes from pushing this stuff out in bulk

I'd better check all the defs and see if I've swapped them around in all the roms.

[D-VO]

Thats amazing guys! Thank you!

[dave-]

@D-VO what are you using for boost control? I know ztan is using an EBC but really don't like the idea of spending $500+ on what is effectively a box with pretty lights for the interior and I'd never bother with per gear boost etc.

That said, all my searches on the forum end up with people achieving this solution using ecutek. How is it done in opensource world?

Can anyone point me to a thread on here showing install using something like the Grimspeed 3 port solenoid?
Which tables on A01G are relevant?

Should add that I've already removed the Sprintex kit and is being replaced with a turbo kit. Installer and tuner are more than competent, but first turbo so I'm doing some leg work to save time. Was going to just go manual control but if I can get a boost control solenoid to play nice with romraider/ecuflash then great...

[Kodename47]

@dave- ECUtek is all done by repurposing the CPC solenoid control but uses custom maps to achieve boost control. I've not seen anything on OS that's comparable. I have CPC duty defined in Romeaider however there is no way to control this to be useful for ECU controlled EBCS using OEM ROMs.

[D-VO]

Originally Posted by dave-

@D-VO what are you using for boost control? I know ztan is using an EBC but really don't like the idea of spending $500+ on what is effectively a box with pretty lights for the interior and I'd never bother with per gear boost etc.

That said, all my searches on the forum end up with people achieving this solution using ecutek. How is it done in opensource world?

My FRS is supercharged so no boost control other than the BOV that came with the KW kit. I have an Apexi AVC-R digital controlling the boost in my Evo though which is also tuned with ECUFlash. IMO its one of the best on the market. I tried tuning one of those GS ones on a friends Evo with no success unfortunately. Ever since then I've felt that going with a piggyback boost controller is best especially if you have an external wastegate.

[ztan]

Originally Posted by dave-

@D-VO what are you using for boost control? I know ztan is using an EBC but really don't like the idea of spending $500+ on what is effectively a box with pretty lights for the interior and I'd never bother with per gear boost etc.

I thought about working with the stock ECU, but was happier getting the pretty lights and control on the fly without pulling over for a 2 min reflash then waiting another 3 for AVCS to start working again. I also really like the boost graph that my GReddy OLED EBC gives me.

Tuning boost from scratch with duty cycle maps, integral and proportional maps is quite doable, but I suspect the time taken getting it to run just right would be too big once you factor in the time you need to reflash each tune. Now if we had live tuning...

[dave-]

Yeah EBC is a last resort. We'll start with a manual bleed and see how it goes. Leaving it up to the tuner.

Yes live tuning would be great but I suspect its not going to happen unless you quit your day job.

[D-VO]

Is there anyone else logging incorrect data output from the Exhaust VVT in the ZA1JB01C ROM?

The scaling that was attached (scalingrpn = x,50,-) really didn't make any sense given the output on the Intake vvt. Without it, I'm seeing data that follows very closely to the AVCS table I have set, however the data logged for the exhaust VVT does not follow.

[steve99]

Note for Australian and possibly Eurropean BRZ 86 owners.

toyota and subaru appear to now be using separate ROM designations for MY 2016 cars

see here
http://www.ft86club.com/forums/showp...25&postcount=1

The roms that come from 2016 BRZ manual and toyota 86 Manual are no longer the same designation , its possible that they are compatable but best to use the identical romid that cam with car.

It possible the Auto brz/86 will be similar.

also note that G and I series seems to be for toyota and P & Q series now for BRZ.

P series in old designation was for japan rom.

Please be very carefull with your rom designations

[Td-d]

I'm done with the Q definition, will post both P and Q defs shortly.

[eddieflyinv]

anyone interested in defining the rest of the Base Timing Idle (In Gear)(Above Speed Threshold) for ZA1JB01C, only defined/comprehensible up to 2000rpm then the headers are random. also I cant seem to save changes made to this table..
want to use this to play with some overrun things....

edit: Found using Kodename47's Defs.

Now another question. Can I safely use Kodename47's Defs to modify a stock ZA1JB01C, and include in it all the timing changes etc from an OFT_2.072_ZA1J700C rom that added power, and flash the stock rom (basically a mirrored image of the OFT rom but with added definitions) to my cars ECU using my openflashtablet

reason being I would rather benefit from additional definitions, than the LC/FFS settings etc.