someone posted an update on the other forum saying they're finishing testing and aiming for the beta to be released sunday. i'm on the beta list so i expect to get an email, i'll post when it happens. i can't wait... almost broke down and bought brzedit this weekend lol.

How did you get onto the beta list? jelly.

i don't think it means anything being that the beta is public, probably just an email notification list or something. i just emailed asking about brz support and the guy asked if i wanted to be added to the list.

i just posted to the romraider thread about the same.
I have an old BRZ (man date feb 2012) that needs(wants) the ROM update and have a tactrix cable.
I am ready to help too.

Ive been trying to post, but I cant get by the mod approval.

I also have a May 2012 build 86 and would love a ROM update the dealer wont do it for me :'(.

Is there a guide for this already?

You don't need a guide it's crazy simple. If you need help applying it just pm me when the time comes.

Don't stress - Dale will pick up the post. Unfortunately, a 1st post mod approval had to be implemented due to a massive pick up in spam some time back. Lesser of two evils.

A couple more days:

interesting tuning note from the thread over on romraider

i thought a/f learning max was set to 40 on a stock rom? were they talking about a brz in that post?

Seems like they were, it was in the BRZ definition thread, anyway: http://www.romraider.com/forum/viewt...=9999&start=15

A/F learning min / max is set to -40% / 40% - but the AF Learning ranges are what is being talked about:
The last range is carried across into open loop. Less of an issue with N/A, but with forced induction, going into open loop 4/5% lean equals 'boom'.

@Td-d Updates??

It's imminent - been chatting to Mike via email, I should be getting the raw disassembly that Colby's done to help along with filling out the definition files shortly (hopefully over and above what I've already dug out) and Colby has been plugging away at finalising the testing of the beta on all ecus (the BRZ functionality is already there, for a while, but due to extensive rewriting core aspects of Ecuflash, they are testing it on all ecus to ensure that nothing was broken with respect to backward compatibility). I think one of Diesel guys has already tested an early version of the beta on the diesel Subarus, and works perfectly.

I get where he's coming from - once the beta is out in the wild, it cannot be removed from the net - so they want to ensure it works on all models.

i agree 100% with the methodology. testing is important and stuff :). i can't wait to play with it but i know how it is. it's hard to un-fubar something once it's out in the wild.

Thanks for the quick reply! Thanks for the hard work! I know some tuners who are standing by waiting for this to happen to start taking cracks at tuning the 86's

Im going to be most interested to actually see what the hell is causing the torque dip first hand.

well we need logging to work before we even care about pulling/pushing a ROM.
I get the feeling that the data logging is what is holding things back.
OFT cant do it yet either.

There are lots of tools to log with. You don't necessarily have to use romraider. I use logworks and techstream over op2. Direct parameter logging will be a nice plus, though.

FYI - it will be coming in a future beta, he's just prioritising getting the first beta out now:

Looks like the folks working Evoscan havnt gotten around SSMIII, compatability stops at II.

They do have a CAN universal selection, I'll give it a try when I get home. though im sure a hundered other people have tried, Ive not seen any reference to it though.

Right!

Calling all South Africans on here - I have a copy of the first beta in my grubby paws, and would like to test drive. We have been specifically requested not to distribute this version yet, but rather do some testing to make sure it's all kosher (if you want a copy, contact Mike directly, and he may provide you with a copy).

Bring it on!

too

exciting


o-o

I'm sure Jamesm will chime in - he also has a copy.

If I could get a copy of the beta I could test on two brzs, my own and another local =P

I could even use it on older subarus for Unit testing / regression testing.

Cmon td-d convince the powers that be to get me a copy!

PM Mike on RR forums - I'm sure he will send you a copy. They just want to keep track on the distribution of the beta at this stage.


Sent from my iPhone using Tapatalk - now Free

Just sent a PM to Mike.

I haven't been able to open the beta. Tried two different computers, fresh install of windows, all I get is appcrash error :(.

I has that problem on my desktop, but loaded fine on my rom flashing netbook.


Sent from my iPhone using Tapatalk - now Free

luckily i'm a nerd with plenty of disposable old windows machines to test on. working on an old toshiba laptop now to see if i can get it running. surely one of these will work... :)

edit: i got it working... turns out it was the fresh install of windows that was breaking it. installed on an older vm with existing old ecuflash and it works. Still can't get the rom to pull, working on that one.

Im getting the appcrash error on win7 64 and win8 86.

Ive tried all manner of install and run compatibility, ive also tried installing to the same existing directory and to a separate. No dice yet.

Unfortunately, none of my machines seem to work at the moment. Getting memory access violation errors. I will have to attach to a debugger later to see if I can't hop over the exception.

Pm me I'll send you a file to fix it.

I could use that file as well - PM'd you, thx.


Sent from my iPad using Tapatalk HD

@jamesm, I saw your posts on the other forum? Were you able to pull a rom successfully yet?

https://www.dropbox.com/s/o3pq9qscfaa9kdd/BRZ.png

Pulled my rom.

That is a much busier brain than my talon has. But i can definitely see the table relation, the x16 tables appear related to VE and map scaling, warm up enrichment's, etc.

I had no difficulties, save the .DLL issue James promptly assisted with. Running on my desktop, Win7 x64 and I pulled the rom with my Win8 x86 tablet.

After I was done, My door lock module did not wake up until after I started the car. I suspect once ecuflash shuts down the non required communications, they are not initialized until flash up again.

Not yet. It appears as though brzedit has 'locked' (changed the seed-key algorithm I presume) my ecu. I thought brzedit doesn't do this, but if you look at their forum announcement the first listed feature is 'read protection option' or something like that.

Going to flash a stock rom on with brzedit Monday and try again.

That's annoying.

Start uploading those roms (other than ZA1JA00C) on the RR forums, and I will get going with defining them.

Roger that.


Edit: just realized that my rom. Bugger.