openecu.org

Hi guys,

I tried pulling the rom from my 05 LGT and it would start then say connect green jumper. Then it would throw an error regarding the kernal?

I am using the 1.3m cable (I also own an Evo IX) and was under the impression the 1.3m cable would work on DBW as well.

Also, I was able to pull my IX rom no problems.

Thanks,

Jason

Did you connect he green connectors under the dash? Did the ECU enter diag mode when you keyed on?

I just hooked up the openport cable. I was under the assumption that on DBW models the jumper were not needed?

Where are these green connectors and how do I connect them (paperclip like old hondas?)

Thanks,

Jason

If you want to read the map off you need to connect the green connectors under the driver side dash. It's above the pedals. If you can't find them, then you'll probably want to read throught he Cobb AP manual for the LGT if you don't feel like searching. I think they have some pictures in there. Only suggestion I have if you don't know where they are visually.

Got it. Thanks guys!

Anyone wanna make xml definitions for it? I opened it with ecuedit and was totally lost

Jason

Use XMLWrite to that. It may or may not have definitions for autocreate in it... you can try it though.

JRSCCivic98 wrote:Use XMLWrite to that. It may or may not have definitions for autocreate in it... you can try it though.

I tried it last night via xmlwrite. Everytime I would enter the cailid it would just close? I tried following the read me instructions, but could not get it too work.

SQ

What format xml were you trying to create? it will exit if trying to make a map for engenuity for a 32bit car, but ecuflash and ecuedit should work.

gregsachs wrote:What format xml were you trying to create? it will exit if trying to make a map for engenuity for a 32bit car, but ecuflash and ecuedit should work.

I tried the Ecuflash option and EcuEdit. Both did the same thing.

Jason

You have to make a copy of the ROM file and put it into the XMLWrite directory. Then rename that file to match the rom name.hex (just change the name before the extention). Then you run XMLWrite and type in the ROM id that matches that ROM filename... obviously the name has to be correct to the rom. XMLWrite will create the xml file in the same directory. This is all in the directions if the readme file with XMLWrite.

I tried again tonight and still got the same problem. I copied the file into the directory, when it came to pick an output it would close out as soon as I hit the key.

Maybe I am just not cut out for this

oh well. I will have a 06 WRX rom for everyone this weekend also.

Thanks,

Jason

most probably it is not supported. You can find out by opening your rom file with a hex editor and go to file offset 0x2000 (8192 decimal). You will see some text, the first 8 characters is the CALID. Note it down, run xmlwrite and just press ENTER to get a list of the supported models. If it is not there, tough luck

Nuked wrote:I tried again tonight and still got the same problem. I copied the file into the directory, when it came to pick an output it would close out as soon as I hit the key.

Maybe I am just not cut out for this

oh well. I will have a 06 WRX rom for everyone this weekend also.

Thanks,

Jason

If you want to post the ROM I can download it and try to create the xml file for you... if you want.

http://forums.openecu.org/viewtopic.php ... highlight=

The last post has the rom attatched to it.

Thanks, it is much appreciated.

Jason

No can do on the xml file. That ROM is not supported by XMLWrite. Now I did try to use it to generate an xml that was close to the same as your ROM, but XMLWrite would just lock up after a few K of generation. Another thing I tried is to get a ROM that was again close, generate an xml for that and use that xml (editing the file heading to match your ROM) to open your ROM. While the ROM opened, the data was inconsistant so... you'll have to wait a while for the defs to surface.