openecu.org

Finalized the little application to turn on/off DTC codes in most known Legacy GT images. It will also do the 05 STi image.

Anyway, simple app. open a image file into the program, un/check the codes you want on/off and click save.

Use ecuflash to upload.

The application will also write over the checksum with the 'checksum fix'

NOTE I have yet to test this application out, but will later tonight and let you know my results.

http://marylandturbo.com/misc/DTCEditInstall.msi

If you dl'ed before this post, dl again, just discovered a bug in parameter loading that is now fixed. I'm also going to add a config file today that will allow easy definition/read of other maps.

wow, way to contribute on your second day as a member!

I've been roaming for a while, but it's that time when I need this capability and I don't feel like blowing $ on a cobb ap when I already have a UTEC.

If you all want source code, there's really not that much to it, written in vb.net.

MDTURBO wrote:I've been roaming for a while, but it's that time when I need this capability and I don't feel like blowing $ on a cobb ap when I already have a UTEC.

If you all want source code, there's really not that much to it, written in vb.net.

I'd like to check it out. Perhaps we can use the data from the Legacy GT to help with the rest of the codes on all DBW roms?

I'm wondering if someone can test the current theory on DBW CELs and confirm that it is, in fact, correct. All of our current calculations are based on the info from tgp? in the "cel disabling" thread, but I have yet to see someone claim that it worked. A couple of people in that thread tried it, but it appears they didn't do the checksum fix. It looks like it is the proper methodology, but someone needs to verify that it does, in fact, work.

I would love to help you, but I'm not throwing any CELs as is.
I SHOULD start throwing p0420 soon, but my car is down right now as I am finishing up my exhaust install.

I'm actually planning on testing tonight, so I will let you know if this works. From what I can see in the binary, it certainly looks like the DBW methods are correct. there's the set of 153-159 bytes of 0 - off or 1 -ons and the preceding group of 'records' that indicate the DTC (there are the same number of 'records' as their are 0/1's)

There are differences in offsets between versions and model vehicles, but it's just a matter of finding them in the image.

I posted the source code here

http://marylandturbo.com/misc/DTCedit_src.zip

as a follow up, I looked in the Legacy GT tech manual. All DTCs noted in there matched up perfectly with the enabled switches in the image file. right down the list. DTCs in the image that were checked off (0) were not noted in the tech manual. The ones that were noted, all had (1) values, right down the list.

That's cool. It sounds like it's right. Let us know how it goes tonight.

If you get a P0607 DTC, then you should read the article at http://www.openecu.org/index.php?title=Subaru:DBW_Checksum_Algorithm.

yeah, I got the p0607 until I fixed the checksum issue.
thats NOT a CEL you want to disable lol

Good Results

First, did a DTC check and damn, I have a lot more than I thought.

I've got a neutral switch code and two front o2 sensor performance codes. Also a pcv sensor code for the sensor I took off for the catch can and the rear o2 performance codes (I have a perrin sim but without the rear o2 sensor in place it threw codes)

downloaded to see what I had, 510, which is junk.

took the 521N I got from this site, turned off the rear o2 codes and pcv code... others I left alone since I have to figure out if they're for real.

Lastly, did a test write, then did a full write. Started up fine. No more o2 and pcv codes Let the car run, idle. Rev'ed it some... ecu needs to relearn idle again with the lightened flywheel. It'll get there...

anyway, looks good. Still have nuetral and bank 1 sensor 1 codes.

I'd say that the DTCedit worked flawlessly. Now to get it to work with other images.

Great job.

Some codes won't throw, though, until a certain number of driving cycles have elapsed.

yep, I will do 3 driving cycles and do a follow up. I'm thinking my front o2 is coming loose, my starter connector is loose or shorted (gotta see what that's about) and the 852 neutral code is supposedly an AT code according to tech docs.. not sure what that's about ...