openecu.org

Ok here's my stock ROM/RAM dump from my 2004 WRX ECU. I have no engine mods. Im just interested in creating my own stage1 91oct maps. I also want to get rid of the ol/cl problem. I'd appreciate it if anyone has created a stage1 91oct map themselves and share so i can tweak it myself. When I'm done I can share whatever i did as well.

note: please rename the extension *.tar to *.hex

Im sharing this information so folks here can enhance them for "Off Road use only".

Here is a later ROM of the same vehicle above. SOA updated this in 2005. This is the latest Stock ROM as of 12/2005. AF4TF520F. This has a fix for "Pinging at 5000 RPM" as well as fixes for error codes. The maps for EcuEdit do not match the ones for this ROM.

Again please rename this from *.tar to *.hex

Im sharing this information so folks here can enhance them for "Off Road use only".

For a description of the fixes and revisions above please go to this link.

http://forums.openecu.org/viewtopic.php?t=207

If you are using ecuEdit, you might need this file handy. This XML file works with this ECU Calid AF4TF520F. This will not work with older Calid's.

Rename this file and put it in the same directory as ecuEdit.exe.

Thanks for uploading the AF4TF520F my car seems to like it much better

That XML is way off and has very limited maps. Anyone actually put one together that's complete since xmlwrite doesn't support anything past the 510 map?

Enginuity supports the 520f.

Damn, I hate Sun Java... guess I'll have no choice now since epifan decided to punk out and actually charge for his (re)work.

Thanks for the info. Does Enginuity actually have the same extensive map definitions that ecuEdit does?

JRSCCivic98 wrote:Damn, I hate Sun Java... guess I'll have no choice now since epifan decided to punk out and actually charge for his (re)work.

Thanks for the info. Does Enginuity actually have the same extensive map definitions that ecuEdit does?

Ecuedit has no definitions, but you are probably talking about using xmlwrite. No, the definitions aren't as extensive as xmlwrite, but include pretty much any table you would want to tune with. That is, more capability than Streettuner, but less tables than xmlwrite. But, you have your choice of standard units (psi, F) and metric and everything is nicely categorized so you don't have to scroll through 50 useless tables (there's a couple extra tables not in xmlwrite that are in Enginuity as well). Also, you have check box cel disabling which Ecuedit/xmlwrite doesn't do.

Xmlwrite seems to be a direct copy of Ecutek (even the tables names are letter for letter identical to the Ecutek software), so either the dude that created it used to work for Ecutek or is really good friends with a shop that lets him use the software. Maybe Ecutek went after him as he's taken down the download link (some other guy is hosting it though). I still use it when I'm looking for an obscure table. You can use xmlwrite to create definitions for Enginuity (slight bug in v6 - you have to replace the first romid).

Pertaining to the CEL disable. I like to make changes to the tables that control the CEL limits. By this I mean... I change the EGT tables to higher values in order to get around the CEL. I don't like to just disable the CEL because if you do it this way it's still set off and readable by OBDII software from what I've seen. You won't get an actual CEL on your dash, but smog inspections indicate that something isn't right. (This is what I've read anyway.) My ROM is setup to allow for CELs, but the limits on the EGT and O2 sensors have been moved so that they don't get set. This way if I really do have a sensor that goes bad I'll know it since I haven't killed the CEL codes directly.

Anyway, maybe I'll try and get Enginuity working on an old laptop to see if it's better then it used to be a while back. I dunno yet...

I've added the cat efficiency tables (2-3 depending on revisions) that Cobb and Ecutek modify to do the exactly what you are talking about - by setting these thresholds to a minimum (0x0) or a maximum (0xFFFF) depending on the table. This is a checkbox feature as well in Enginuity. I also have added a TGV fix that other tuners use to the latest def version, but it still throws some CELs.

I'm switching over to Enginuity as well, as a matter of fact that is what I have already done last night.

Something about charging for software that was developed using info borrowed from here and possibly Ecutek leaves me with a bad taste.

Maybe more people need to tell this Russian what's up. I mean, if it's Open developed software then it shouldn't be charged for. Hell, he might as well pay out some royalties to the people on here for beta testing it for him. In all reality, the only thing the sharware version will do is have those stupid ass 60 sec delays in it from what I heard. But I agree with you, for a program such as this he should not be charging.

Yeah, the posts about it are like an advertisement now. This is an OpenECU (Open Source Logging/Tuning/Flashing) which shareware, closed source software does not apply. He should at least be paying the openecu site operators some advertising fees.

We should start a new thread about it. State how many of us don't agree with his recent change in development ideas. I think it's just lame for him to try and sell this... especially since he blatantly states that he will not include the xml definitions for the program to work. He either needs to create the xml defs and include them in the program or not put a price on it. I don't think this kind of request is out of line.