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

[EAGLE5]

Tactrix's software is locked into their hardware. Some of the clones work with the hardware, but bricking your ECU is no fun. I strongly suggest real Tactrix or OFT. EcuTek is good for people getting a custom tune from a pro. The big boys often use an ECU replacement.

[steve99]

Originally Posted by Rossi

Would it be possible to flash using a ELM 327 cable or a obd2 cable that can read data? Or do you have to have the tactrix cable?

ELM327 adapters can only do basic interaction with ECU using standard OBD calls, ie read cel codes clear cel codes and access basic engine data that the manufacturer has made available via standard obd call they are required to by law.

To flash the ECU with new ROM data you need a specialized device any one of the 3 below will work they are in order of cheapest to most expensive. Tactrix is the least user friendly

Tactrix adapter
OpenFlash Tablet -comes with free tunes
Ecutek Cable and Licience

[dave-]

Probably been asked before but info seems to be all over the place...

What/where are the most complete RR definitions for the A01G ROM? There are Td-d github repos, I've seen OFT ones from @Wayno dated late last year, revisions by @Kodename47 and various useful additions by @ztan.

I'm not using an OFT to flash but from memory that doesn't matter in the case of A01G def's?

Second question, can someone provide a working G series logcfg.txt file to do tactrix logs with boost? Think I have the wrong addresses or settings. Did try to generate a new logcfg file with that app but it gives me an error because the RR logger isn't configured correctly. I gather most boosted people are running ecutek here from my searches? Sprintex supercharger kit in my case.

[steve99]

Originally Posted by dave-

Probably been asked before but info seems to be all over the place...

What/where are the most complete RR definitions for the A01G ROM? There are Td-d github repos, I've seen OFT ones from @Wayno dated late last year, revisions by @Kodename47 and various useful additions by @ztan.

I'm not using an OFT to flash but from memory that doesn't matter in the case of A01G def's?

Second question, can someone provide a working G series logcfg.txt file to do tactrix logs with boost? Think I have the wrong addresses or settings. Did try to generate a new logcfg file with that app but it gives me an error because the RR logger isn't configured correctly. I gather most boosted people are running ecutek here from my searches? Sprintex supercharger kit in my case.

kodename47 are probably the most upto date he has usually intergrated most of the other guys stuff.

you can only extract parameters the ecu uses with the logging, if you after some extra parameters you could try asking ztan

romraider logger not set up for our ecu

you might want to talk to @D-VO he has done supercharger open source

[ztan]

Originally Posted by dave-

Second question, can someone provide a working G series logcfg.txt file to do tactrix logs with boost? Think I have the wrong addresses or settings. Did try to generate a new logcfg file with that app but it gives me an error because the RR logger isn't configured correctly. I gather most boosted people are running ecutek here from my searches? Sprintex supercharger kit in my case.

paramname = MAP
paramid = 0xFFF87C60
isfloat = 1
scalingrpn = x,0.133322368,*

Logs MAP in kPa

[dave-]

Originally Posted by ztan

paramname = MAP
paramid = 0xFFF87C60
isfloat = 1
scalingrpn = x,0.133322368,*

Logs MAP in kPa

That's what I had, didn't know it was kPa though which helps. But my logs still don't look right as WOT runs peak at 137.297 kPa so ~20psi?

It's a Sprintex SPS/210+ kit with 69mm pulley. Positive the peak was 12-13psi on the dyno.

Did some logs yesterday/today with some spirited driving.
http://datazap.me/u/dave/sprintex-tune
http://datazap.me/u/dave/sprintex-tune-log-2
http://datazap.me/u/dave/sprintex-tune-log-3

[ztan]

Originally Posted by dave-

That's what I had, didn't know it was kPa though which helps. But my logs still don't look right as WOT runs peak at 137.297 kPa so ~20psi?

It's a Sprintex SPS/210+ kit with 69mm pulley. Positive the peak was 12-13psi on the dyno.

Did some logs yesterday/today with some spirited driving.
http://datazap.me/u/dave/sprintex-tune
http://datazap.me/u/dave/sprintex-tune-log-2
http://datazap.me/u/dave/sprintex-tune-log-3

MAP is in kPa absolute.

137kPa absolute = 100kPa atmospheric + 37kPa (5.3 psi) boost.

Is your MAP sensor scaling right? Which sensor are you using and which ROM address did you adjust (the original def sensor scaling addresses were wrong). Just had a look at your logs - your MAP is pegged high at 137kPa which looks like a maxed out stock sensor. The psi boost value is in your logs as manifold_relative_pressure.

Stock sensor scaling = 250mmHg/V -150mmHg
Stock sensor at 5V = 1100mmHg ~= 145kPa

ps: you can delete the AF_Corr_3 and AF_Learn_3 values from your logcfg.txt - I'm sure the latter is an OL_enrichment value and I haven't traced the AF_Corr_3. You can also boost the sampling rate by dropping some of the parameters that you aren't really looking at and decreasing the calcsampinterval value - I am using 500 at the moment and log 32 parameters at 40ms interval.

[dave-]

Originally Posted by ztan

MAP is in kPa absolute.

137kPa absolute = 100kPa atmospheric + 37kPa (5.3 psi) boost.

Is your MAP sensor scaling right? Which sensor are you using and which ROM address did you adjust (the original def sensor scaling addresses were wrong).

Yeah saw the ~5psi bit when I added this from some thread here:
paramname = Manifold_Relative_Pressure
paramid = 0xFFF88F78
isfloat = 1
scalingrpn = x,0.0193367747,*

Believe it is the OEM MAP sensor as the kit doesn't change it. Not 100% sure.

Manifold Pressure Sensor Scaling A/B/C are the same:


ROM def's are Kodename's metric & % one:
<table name="Manifold Pressure Sensor Scaling A" storageaddress="1000CC" />
<table name="Manifold Pressure Sensor Scaling B" storageaddress="1000E4" />
<table name="Manifold Pressure Sensor Scaling C" storageaddress="11CC20" />

Logged using:
paramname = MAP
paramid = 0xFFF87C60
isfloat = 1
scalingrpn = x,0.133322368,*

Should add it isn't my tune and from my inexperienced eye, looking at the logs it isn't very good anyway.

[ztan]

Originally Posted by dave-

Yeah saw the ~5psi bit when I added this from some thread here:
paramname = Manifold_Relative_Pressure
paramid = 0xFFF88F78
isfloat = 1
scalingrpn = x,0.0193367747,*

Believe it is the OEM MAP sensor as the kit doesn't change it. Not 100% sure.

<table name="Manifold Pressure Sensor Scaling C" storageaddress="11CC20" />

The scaling at 11CC20 is the only one that affects MAP.

When you get a uprated MAP sensor, have a look at my boost fuel cut fix to protect you from major overboost. Boost protection at the moment with that stock sensor won't work, but not critical with supercharger compared to turbo.

[dave-]

Originally Posted by ztan

The scaling at 11CC20 is the only one that affects MAP.

When you get a uprated MAP sensor, have a look at my boost fuel cut fix to protect you from major overboost. Boost protection at the moment with that stock sensor won't work, but not critical with supercharger compared to turbo.

Scaling for C is the same so all good there.

Have all your opensource threads saved, as you said not critical with the blower but would def do it for a turbo.

Will have to confirm still stock sensor but not overly impressed with the setup so far so who knows how long the kit will stay installed anyway!

[Kodename47]

You can't change the MAP sensor on the Sprintex, but there's no need. MAP just caps at the sensor limit.

What's wrong with the setup @dave-?

[dave-]

Originally Posted by Kodename47

What's wrong with the setup @dave-?

We're not seeing much of a difference to a couple cars with the standard kit and 75mm pulley after custom tuning. The canned tune that was supplied with the stage 2/plus kit is part of the problem (it's shit) but ultimately the claimed improvements of the stage 2/plus blower and extra boost from the 69mm pulley, I'd expect a lot more than we're seeing.

Need to get the car on a dyno again and put some decent effort into the tune. I'll report back once that is done. Haven't ruled out hardware or install issues either as yet. I do know the intercooler took a few go's to bleed completely. I wasn't present for the install so not sure what happened there or if its a common thing. Haven't read much of the sprintex thread TBH.

[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??

[Kodename47]

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??

I don't know the answer to your question, but like the PI Ratio tables they are all set to the same so I've only ever seen them set all to the same. There must be some form of hysteresis however I very much doubt anyone would go to the bother of changing SOI dependent on temps.