openecu.org

Well, I'm here to join you guys. I just ordered my cable and I'm looking forward to working with you all here to get this open source software set as a standard! I've been following this project for a while and I know there is a lot to learn.

I'll be letting the guys over at AWDPirates.net know all about this. We are a small forum mostly from Colorado.

I have a 05 WRX, so my first goal is to get rid of the OL/CL delay. If anyone has any suggestions please PM me or let me know otherwise.

I'm RK Performance over on Nasioc.

Thanks so much to the developers!

-Ryan

Welcome.

If you want to get rid of your delay, please send me a dump of your ECU once you receive your cable. I've tried this on a bunch of cars now with very good results.

The 04/05 code is similar, so I can send you a modified image very easily. I'd also like to get a few logs after you flash the fix to make sure that everything is working okay.

Thanks,
Mike

Mike-

I've been enjoying your fix for a while too. It might be nice to post some "known working" OL/CL fix ROMs for the versions that have been tested.

Colby

Thanks, Colby.

I've got two people interested in trying this right now- as soon as I get some feedback from them, I think I'd feel comfortable that it has been thoroughly tested.

Thanks Mike For the sake of research let me know if you guys want me to get some initial data logs, then reflash, then some more logs. I will have the 1.2 tactrix cable so as far as I can tell I won't be able to use the current version of the ECU explorer software. It looks like I'll need the stand alone version of ecuFLASH to do flashing and ECU Explorer to do the logging. Give me some specific ideas and I should be able to get something done. Semester starts next week so the sooner I dig into this the better. Otherwise it will be set aside until the summer.

The car is a 2005 WRX MT with a CBE, and U/P <--I didn't know!

-Ryan

crazymikie wrote:Thanks, Colby.

I've got two people interested in trying this right now- as soon as I get some feedback from them, I think I'd feel comfortable that it has been thoroughly tested.

May I make a suggestion?

Subaru has created a reflash for the 2004/5 which corrects a problem described as "Pinging during full throttle acceleration around 5000RPM" (see http://forums.openecu.org/viewtopic.php?p=1998#1998). Chances are that your "delay" fix isn't based on the ROM CalIDs that incorporate the pinging fix. I don't recall that these SOA reflashes to fix pinging for the 2004/5 WRX have ever been discussed at NASIOC, so I conclude they're very rare in the wild.

I think it's very important, in the event you make your ROMs public, that you declare the CalIDs on which they're based, and that you recommend they not be installed when a user's CalID is higher. If a user has a higher CalID, he should, instead, be encouraged to publish his ROM image, so that your fix can be incorporated without loss of SOA's fixes. Ideally, your fix would be based on SOA's latest ROM.

For reference, here are the CalIDs which incorporate the 2004/5 WRX ping fix. Higher CalIDs for these models will include the ping fix because any newer SOA reflash is cummulative, incorporating fixes for all previous problems.

04 WRX MT - A4TF520F
04 WRX AT - A4TF520E
05 WRX MT - A4TF810F
05 WRX AT - A4TF810E

Cable came in today. I think I'm going to make a backup of my ROM, do a few logs and then see if I can get the reflash from Subaru. We'll see how it goes.