I just want to log for now.

this doesn't work on the latest ecuflash builds (anything past 1.28 i believe, as that is the newest version that i could get to recognize a standard j2534 cable). the newer versions require the tactrix branded cable, though that appears to be easily defeated with dongle cracking tricks if you were so inclined (unless you already own a bus pirate, you probably don't wanna go that route ;)).

best to save the trouble and buy the tactrix cable as it's cheap, has cool features (onboard logging, and the innovate plug you mentioned) and is a very good cable for the price.

Unless the exhaust temps are the reason innovates sensors burned up I'd stay away from them.

Had 5 in 50k miles on my wrx. Then the unit itself started having problems.

From what I understand the aem worked better but needed a custom cable to log with

Weird I've used innovate sensors (actually they're Bosch sensors, same supplied to many oems) for years without issues. Where were you installing them? Heat can be an issue if installed in the wrong location.

As far back in the dp as the cable would reach....

It was wrapped and I was running high boost. As much for the fact that I have 12psi for atmosphere

maybe the wrap, load on the turbo, and placement options conspired to kill your sensors lol.

About 300whp at 4500 ft.

Takes lots of boost in a stock turbo wrx.

I tried to get romraider to work with one of the posted RR_BRZ ECU definition files.
I get the "Cannot find ECU definition file" error.

Anyone on this forum actually get it to work yet?
I dont want to flash anything.
I just wanted to play with romraider before deciding if I want to go the ecuflash route or the openflash tablet route?
BTW - what ROM editor is used with Openflash? Can you still use romraider to edit the ROMs?

you can open the rom colby posted in tunerpro with the openflash defs (just don't open the flat foot shift or launch control tables lol). still waiting on the guy from the romraider forum to post his xml def. you could convert the .xdf from the openflash files to a romraider xml if you really didn't want to wait for it, or just use tunerpro for the time being.

that's important to note: you can use any tuning software for which defs are available for either flashing solution. all the openflash/ecuflash do is flash the rom. editing it is an entirely separate process.

you can use RomRaider and the RR_ZA1JA00c XML to open any of the OpenFlash Roms that have the SAME revision (ZA1JA00C)

Rom Raider actually has many more defined tables...and since td-d actually knows what he is looking at/for, ALL of the CEL tables have been Identified and defined. Looks highly promising...just waiting on the beta of ECUFlash now....

Does anybody know if Ecuflash has a donation link? I'd love to donate to them (they are open source aren't they? Couldn't find much information about the actual software...).

As far as I can tell, the RR defs work for any of the OpenFlash roms. They all appear to be based around the same ZA1JA00C rom. They just appear to have the CAL ID headers changed.

if you wanna support ecuflash, buy a tactrix cable. if you wanna support romraider, you can donate on the romraider.com main page with paypal.

ecuflash isn't open source, romraider is.

Morning guys

Just to answer some of the questions in the thread:

Ecuflash will allow both the editing and flashing of the Roms onto the ECU, whilst RR is an editor, logger and more recently has learning view capability incorporated (though not yet for the BRZ, the logic will need to be reviewed to see if there are changes, and the Ram addresses identified). I already have a good deal of the extended (4 byte) parameters defined, still digging through the logic to fully define, since the structure of the SSM array table is different in these new roms.

On reading Ecutek roms - the ones I've seen seem to be locked / encrypted. And
echoes my sentiments exactly.

On the issue of the various CAL IDs, I've seen the SADM and USDM roms, and as soon as Colby releases the beta, I'll be able to pull a local (South African) rom, which is the EUDM version. From what I've heard, there are little differences between the territories (generally the US roms are more anal about emissions). In any case, once one rom is defined, it is pretty straightforward to define the others using a set of of templates that speed up the disassembly process. Colby has also mentioned that he will assist with software that he developed that will auto define most of the roms once the initial table template is set up, which will speed things along.

Since I was already stuck in, I thought I'd finally define all the Alpha parameters that I've pulled out over the past 1-2 years. I've been avoiding it since it's tedious work and time is constrained - especially when it's for over a hundred tables and parameters :D

I've defined about 70 odd 'new' tables for the BRZ, of which ~30 are specific to DI, the other 40 are previously defined 'Alpha' parameters, a lot of which were identified through COBB's implementation on the forced induction platforms (I've never denied that ;) ).

There are still quite a few new tables to be incorporated into the definition, just need to find the time - hot restart, knock sensitivity, idle throttle, the remainder of the tau tables (transient fueling) to name a few (and I need to also trawl the logic to see whether others exist, like cruise/non-cruise map blending).

Once we have a fairly comprehensive solution going, I intend to work with Merp (if he has the time) to see if we can port his work to the BRZ platform (FFS, LC, map switching, Knock CEL flash, High EGT CEL flash, amongst a host of others). Otherwise, I need to start boning up on C## and the Renesas HEW environment...

One other thing - the picture of the timing table posted using the first definition needs to be replaced with one from the latest definitions (since the first iteration inherited the scaling from the existing roms, which is different (to be precise, the old scaling is (x*.3515625)-20, whereas the BRZs use (x*.3515625)-30 - hence the timing tables are 10* overstated).

Just before we start a whole thread about how open source is prone to errors, and the superiority of closed platforms ;) (trolololol...)

Is this open-source software? Like BRZEdit? I'm a bit new to the tuning industry.. never heard of the mentioned companies :(

OpenFlash, TunerPro, and ECUFlash are not open-source. They do not grant access to the source code of the applications themselves. They, however, do not encrypt or restrict what you are able to do with edited ROM files. RomRaider is completely open source. It's source code is available to all those that may want a copy.

I am really watching how all of this develops... ECUtek is awesome, but being locked and at the mercy of a tuner can really turn into a horrible situation so FAST....

Ask any of the Visconti and other tuners customers waiting a month or more for any type of response, let alone a real look at their logs and a real file update.

Correction, ecutek WAS awesome, now it's the most expensive and least flexible option on the market :)


Sent from my iPad using Tapatalk - now Free

Thank you! I just donated. Love to see more work on open source tuning tools.

Me Love you long time

and this is why i have been holding off on a tune

Short update on the timeframes:

when i talked to tactrix the other day they said friday or early next week.. so it should be soon. anticipation is killing me lol.

Once you tell me it is a go, I will be placing my order for my first Tactrix cable. :D

wanna be my tuner? lol

You have yourself a good tuner. :lol: I am happy with my tuner, but I am a tuner myself at heart, and I want a crack at tuning my own car.

I ordered mine before the rush. (The one I have is a v1.1 that was really only good for my 04 WRX)

The good part is that all our local Subarus are open source tuned by Anthony @ Drunkmann Tuning so I can easily unload the cable when I am done with it.

:paddle:

the anticipation is killing me. any news? i haven't seen anything on the other forum since last friday.

I'm waiting patiently for more news as well. I've had the Tactrix 2.0 cable for a while after having used it on a few other cars and was hoping I would be able to use it on this one. It's the mod that keeps on giving! :D

Ditto!

We need to meet up if/when I get back. I may have you take a look at my tune.

we're all relatively close... we should see about splitting some dyno time somewhere central and make a day of it :thumbsup: @Sportsguy83

Now that sounds like a plan. I would love a Florida Forced Induction Dyno Day. :thumbsup:

No problem. I am VERY good at reading datalogs.

Anticipation is killing me.. i suppose if i could at least log it with romraider that would keep me happy. but can't do that either!

I am very excited for this as well.

Me as well also too.