Order of events

[swifty]

Hi

I have read quite a lot of stuff here but haven't managed to quite figure out how everything fits together from start to finish. I expect my cable to arrive soon and would like to be clear and what steps I need to take to remap my car before I start. I have a friend who is an experienced mapper to give me a hand with the actual mapping but need to get the rest of it sorted out and working before I go and ask for his help. Here is my understanding right now:

Order cable, then when it arrives:
Install and configure comports for software, ECU Explorer for data logging, flashing and trouble codes, and Ecu Edit for mapping.
Connect green diagnostic connectors on car
Bridge other wires under dash (is this only needed for flashing ?)
Plug in cable and PC
Switch on ignition
Use ECU Explorer to interogate ecu and to take a dump of the rom.
Make several backup security copies in various places for safety.
Upload the rom to this site.
Do I need to perform any kind of conversion of the rom from binary to hex, or 160 to 192 or anything ? I see various roms are in bin or hex format.

The next bit is where it goes a bit fuzzy:
Figure out offsets
Define xml file(s)

My car is a MY01 JDM STI and has the following numbers on the ecu:
V8
22611AF481
112000-7546.

I see the 2001 JDM STI folder has a map from an S202 which is from a different ecu so hopefully my rom will be of use.

How do I figure out what the offsets are and what do I do with the details once known ? I don't understand where they fit in, somewhere within the xml ? Does this tell ecu edit what map is where ? How will I know if I have got them right or wrong ?

As for the xml file, do all ecus use a file of the same structure but with different values in ? If so, is there a defined template ?

So working on the basis I get all this together I should be able to look at and edit the maps in the rom file, save them then flash it back to the ecu.

I thought it would be a good idea to take a copy of an already defined rom and xml file and use it to get a feel for ecu edit but I have been unable to get that to work. I used the ah992-5513 files but think I am dong something wrong with regard to file placement or something, or should I only be able to see hex values in ecu edit ?

Sorry to ask so many basic questions but I would really like to get everything clear, then once I am up and running perhaps I can make a contribution to the forum.

Thanks

PS - wasn't sure where to post this so thought General was best.

[Freon]

You've got most of it.

I think the general trend is 192k. It definitely does matter when you go to start creating the XML definitions of the ROMs. If you create your XML looking at a 160k image, the XML wont work on 192k. It's easy enough to fix the XML later, though.

The offsets things is kinda technical. Calvin posted a huge list of offsets in a zip file, you may look in that and see if your ECU is in there.

If you want to start hacking up an XML file, I highly suggest using ecuedit. It has a nice hex viewer and good tools for doing the work. It's highly technical work. It isn't too hard if someone gives you a list of offsets to start with, but you still need to pay attention to details. As you said, I'd recommend downloading a ROM and finished XML file and poking around it to see how it works. You can open up two ROMs in ecuedit and compare.

I think Enguinity has some sort of tool in it to set the maps as well just by typing in the initial offset, but I haven't used it yet. Worth a download. Unfortunately it doesn't have much else to use to setup the XML. I'm not sure ecuedit and enguinity are compatible either.

[swifty]

Thanks

I have Calvin's file of offsets but how do I match my ecu up with what is in the list ? My ecu is 22611AF481 but there is nothing remotely resembling this there. Can I only do this once I have the rom image ?

My cable has finally been released by customs in the UK so with a bit of luck it will be delivered this week and I'll be able to take a copy of the rom.

[qoncept]

Open your image in a hex editor. The ECU revision is at 0x200.

[swifty]

Thanks
My cable is being delivered tomorrow so I should be able to get started over the weekend.