RomRaider

i opened my stock hex file that i pulled from my computer earlier in RomRaider and it doesn't seem to have the tables for the P0037 code. It also says that there is a later version but since everything had been deleted i can't download it. so does anyone know how to mod a stock map to get rid of the P0037 code? BTW my car is an 02' 5mt wrx.

heres a link to my factory hex.....

http://web.njit.edu/~ejm3/files/FactoryImage02WRX

in no way shape or form do i post this except for educational purposes.

Eric

In your 160k ROM, the p0037 code is at 0x25BB0. Use a hex editor. You'll see 03 0037 there. Replace that with 05 0000.

this method takes the code away, but the cel seems to appear without a code now. for me atleast.

I'm not into creating my own definitions (don't know xml yet) so what I did was download the A4SGE01C rom that was posted not long ago. Apparently it's the latest re-flash from Subaru. Someone had already taken the time to create many definitions including the P0037 (and most others too). You still need to set the threshold value though.

That value is not a threshold value. It is only doing the same thing as using the hex editor method and adding 05 0000. The reason why there are weird numbers is because you basically "back translating" the numbers so they will correspond with a 1 byte cell (05) and a two 1-byte cells(00 and 00), since RomRaider will not support combining a 1 byte and 2 byte data into the same definition.

Some CELs apparently aren't eliminated by the hex editor method. You have to find the real threshold numbers. All the tuner maps I've seen change these two values, which may have something to do with that CEL: Cat Threshold 2 fail above A and B (two different definitions).

my head just exploded on that last one....

merchgod what hex editor should i use?

I like this one:
http://www.mirkes.de/en/freeware/tinyhex.php

so i tried to flash my ecu with the updated code the other day ( using ecu flash) and it didn't work, heres my log http://web.njit.edu/~ejm3/files/ecuwriteDNW , any ideas?

Make sure you have the latest ECUflash 1.27 - it includes drivers for the cable. You are using the Openport 1.2 cable, right? Also, you have to have a flash block for flashing (or a jumper wire). If you have all that setup correctly, then another issue is turning on the ignition too early. Run ECUflash and go to flash and wait until the box comes up that tells you to turn on the ignition, then turn on ignition and hit the button immediately.

thread jack:

I've been using tiny hex to map out the TGV CELs, tiny hex shows that the hex location is at 0x024B20 but when I change the ecu_def to display that location I get some funky numbers(yeh, more funky than they are supposed to be). I have to change the hex location in the ecu_def file to read 0x2CB20(similar to other CELs) to read properly.

I'm familar with hex, is this a display settings issue in the tiny hex OR something I'm overlooking. Thanks.

Jeremy

Not sure what you're expecting and actually seeing, but check the <scaling> tag in RomRaider -- it could be altering the values you're looking at. Make sure expression and to_byte are set to "x"

thanks for the quick reply. Everything is working/mapping properly its just my locations are not corresponding from the ecu_defs to the hex file.

When I enter in location 0x24B20 (the hex location found in Tiny Hex) for CEL P1089 into the ecu_def file along with associated code. Then I alter(05 00 00) the code in hex form, then compare it to an unaltered map. They are the same. I had to type in location 0x2CB20 in order for it to display my changes to the hex.

I double checked my P0420 code @ 0x2C90C(mapped out in ecu_defs), that location is actual 0x02490C in tiny hex, there is no 0x2C90C. Is one of my settings in tiny hex wrong causing my locations to be labeled differently?

The reason why RomRaider will show some funky numbers, is because of the way the cel fixes are setup. It reads 2-byte chunks in a series of 2. So, it actually starts 1-byte before the CEL code and then reads the two chunks of 2-bytes. So, for example, in hex it might read 40 03 0037. In a hex editor, you would change the 03 0037 to 05 0000. In the current method of CEL fix in RomRaider it, would read 4003 0037 and this would be converted to a decimal representation and hence the wacky numbers. So, then the user would enter in the reverse decimal representation of hex 00050000.

Regardless, I'm adding the new cel fixing to this latest definition. It will be a lot easier to implement if you want to add your own definitions.

thanks guys, but I don't guess I've made myself clear.

I have no issues with the values displayed in RomRaider, I understand hex, dec, octal & binary numbers & the conversion of each & I'm not new to XML, Java or other programming languages for that matter.(Its been awhile but I'm familar w/ it)

my only issue is that the hex locations aren't the same between the ecu_def & the hex file...

CEL P0420 = 0x2C90C(RomRaider) = 0x02490C(tiny hex)

CEL P1089 = 0x2CB20(RomRaider) = 0x024B20(tiny hex)

^ get it?

If I type in the (tiny hex) location into the ecu_def it actual pulls from some other location, not the one I modified in hex.