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

[steve99]

Originally Posted by lizbrayan

So I made a zip folder that has my stock rom from the ecu and the oft stage 2 uel 93 tune that "has" my calid. @steve99 and if some of you other guys can also help me out thatd be great thanks!

yep your stock rom is ZA1JD00D it was saved in ecuflash .srf format so hex locations different, you can open the rom and save it as .bin if you load a ECUFLASH DOOD def into the correct directory in ecuflash then the hex locations they are 8000,10000,11EB9E hex in standard bin format

checked the stage2 rom in your zip its real D00D as well so you will be able to use standard ecuflash D00D definition to flash

be sure to allow ecuflash to correct checksum before flashing

[steve99]

Originally Posted by Tor

Yes, I meant brake pressure via own sensor. Hence, I would think it's probably easier to add a potentiometer to the pedal. Probably not as accurate as monitoring pressure, but probably enough to pick up brake technique mistakes or spot bad habits.

Seems like it would be possible, another project for the winter.


P.s.
I read the link you gave about KCA and now I think I understand what you meant with "be careful with adding timing". Because the ECU can't pull as much timing with Waynes map as the stock one can (lower values in KC Advance Max A), in case one would add much too much?


Again, thank you were much for your help.

main reason is some people just blindly copy base B say out of a standard OFT tune into wayno's without realising that he has changes the KCA table from what oft guys use

[lizbrayan]

Originally Posted by steve99

yep your stock rom is ZA1JD00D it was saved in ecuflash .srf format so hex locations different, you can open the rom and save it as .bin if you load a ECUFLASH DOOD def into the correct directory in ecuflash then the hex locations they are 8000,10000,11EB9E hex in standard bin format

checked the stage2 rom in your zip its real D00D as well so you will be able to use standard ecuflash D00D definition to flash

be sure to allow ecuflash to correct checksum before flashing

So im good to go? i have the za1jd00d def in the brz 2014 folder because theres no 2015 folder and the 32bitbase def in the base folder. What do i have to check in the za1jd00d def to make sure its okay?

Sent from my SGH-T999N using Tapatalk

[Tor]

Originally Posted by steve99

main reason is some people just blindly copy base B say out of a standard OFT tune into wayno's without realising that he has changes the KCA table from what oft guys use

I see. No, I would have select all fields in Base Timing B and added 2 degs with "Increment Value (Coarse)" arrow-up button.

I got helped to another solution. However, my questions are wandering off the Tactrix topic. So to avoid clutter I'll find appropriate threads when I have further questions.

Again many thanks for your help, and to everyone else who helped me out in this thread!

[Kodename47]

Originally Posted by Tor

I see. No, I would have select all fields in Base Timing B and added 2 degs with "Increment Value (Coarse)" arrow-up button.

Don't just go adding 2 degrees across the whole map....

[Tor]

Originally Posted by Kodename47

Don't just go adding 2 degrees across the whole map....

Thanks, yes I have the utmost respect for messing with thing. I wouldn't have done that without a lot of questions first with exactly how to go about it. I just meant I certainly wouldn't blindly copy/paste anything from another map. I'm surprised that there are people treating it all with such carelessness. They must have deep pockets.

I noticed yesterday that my brakes are so bad I am not driving the car before I get my brake job done (got my new XP10 pads in the mail today). So first priority is now brakes.

I also want to drive on track next Wednesday, so I'm considering just to leave it all as it is on Waynes 108.2 tune and log it there to see how it behaves. For me it's more important that it has a conservative track tune, than to squeeze out every hp for street usage. During the pulls I logged it had no knock at all.

I also did a log pulling the car fairly hard up a hill on a backroad in mid rpm range (I think I was feeling out the torque dip) - there after just normal cruising. To be honest, I didn't look at that log very thoroughly until today
http://datazap.me/u/tor/ww1082-drivi...26-27&mark=332

During the "hill climb" there were a 4 flkc events (0.65 range) and 2 fbkc (1 at -2,1 at 3200 rpm and 0.93 load, going off the throttle). I suppose that is "normal"? And even with these events more timing wouldn't hurt, possibly pulled back in those areas if it's consistently reproducible?

Now I am getting off-Tactrix topic again. I guess I should use the sticky datalog thread instead?

[lizbrayan]

Alright so i flashed the oft stage 2 uel to my car. Feels great. Just got a question is it possible to program a launch control on an a/t with ecuflash, if so how do i do it?

Sent from my SGH-T999N using Tapatalk

[phrosty]

Originally Posted by lizbrayan

Just got a question is it possible to program a launch control on an a/t with ecuflash, if so how do i do it?

In theory it may be possible, but your torque converter stall limit gets in the way of any meaningful launch control.

[Kodename47]

@Tor if you're using Wayno's base and advance tables, if you want to advance timing I would suggest no more than 1 degree at a time and even then it's only really beneficial to do it for WOT loads. You might find some response improvements by adding timing in medium transient loads (~0.8+) if you're not showing any signs of timing retard but there's no point in increasing timing on cruise over stock IMO. How you add this is up to you, in the base table or the advance, just remember to check the totals of the 2 combined to try and keep a smooth-ish table.

[Tor]

Thanks for the description. It helped to increase my understanding. For now I wont need to change anything. It was stupid to mention the +2 deg on the whole table, without the full picture. What I meant to say was "I won't copy tables from one map to another without someone telling me why to do it".

[EAGLE5]

Originally Posted by lizbrayan

Alright so i flashed the oft stage 2 uel to my car. Feels great. Just got a question is it possible to program a launch control on an a/t with ecuflash, if so how do i do it?

Sent from my SGH-T999N using Tapatalk

You place your left foot on the brake pedal and your right foot on the accelerator. When you hit the desired RPM, lift your left foot. Last I remember, all the launch control did was hold a chosen rpm before dropping the clutch.

[lizbrayan]

Originally Posted by jsimon7777

You place your left foot on the brake pedal and your right foot on the accelerator. When you hit the desired RPM, lift your left foot. Last I remember, all the launch control did was hold a chosen rpm before dropping the clutch.

Lol you made me laugh bud, it was worth a shot

Sent from my SGH-T999N using Tapatalk

[EAGLE5]

Originally Posted by lizbrayan

Lol you made me laugh bud, it was worth a shot

Are you sure you're from Jersey? Your skin is awfully thick and you're awfully smart. You must not be a governor.

[steve99]

Originally Posted by lizbrayan

Alright so i flashed the oft stage 2 uel to my car. Feels great. Just got a question is it possible to program a launch control on an a/t with ecuflash, if so how do i do it?

Sent from my SGH-T999N using Tapatalk

No not easily

you need mechanical changes to the torque converter in the auto. and number two the launch control rpm limiter is a software patch to the actual ecu coding like flat foot shifting. Changing ecu program code is a whole new level of dificulty and skill as oposed to changing table vaules like about 100 times