I just downloaded my ROM for the first time using ECUFlash, but my ECU Internal ID is listed as undefined. I searched around the forum, but I didn't find anything about this. This is a 2004 GSR with custom Dynoflash.

Has anyone seen this before?

I used 96420008 as the inherited definition and my tables seem to be scaled normally. Do you think I have a problem?

Thanks

Here is a screenshot.

 

I'm guessing that you have a 96420007 Evo VIII ROM. If you go to:

C:\Program Files\OpenECU\EcuFlash\rommetadata

and open the "Undefined.xml" text file, what info is listed under "internalidhex"?

 

- <rom>
- <romid>
<xmlid>undefined</xmlid>

<internalidaddress>f52</internalidaddress>

<internalidhex>96420007</internalidhex>

<caseid>MN191022</caseid>

<make>Mitsubishi</make>

<market>USDM</market>

<model>Lancer</model>

<submodel>EVO8</submodel>

<transmission>Manual</transmission>

<year>2004</year>

<flashmethod>mitsukernel</flashmethod>

<memmodel>SH7052</memmodel>

</romid>


<include>96420008</include>

</rom>

Looks like you are right on. So, now my question becomes.... how do i fix this? Do I just edit the XML where it says 0008 to 0007?

 

I have seen a few roms with that ID, and they've all been from DynoFlashed ECUs. Maybe its just coincidence. At any rate, there is no framework for your rom. The 96420008 framework is not quite correct, and there's nothing you can do to directly fix it. I suggest sending an email to Colby (ECUFlash author) to let him know that you have a ROM with this ID. Hopefully, the next version of ECUFlash will have a framework for 96420007. BTW, you can search on that ID in the ECUFlash subforum, and you'll find a few other threads on it. I don't recommend trying to modify your rom and then upload it to your ECU until there is a correct framework.

 

Dero, I have the same o4 96420008 ECU, I also have the ID listed in inherits and the ECU ID blank. It works for me fine and I don't want to go changing something that works so I keep it like this.

However, once you get the EcuFlash up and running can you do a flavor and look at your "Idle step lookup table" RPM column (advanced - won't find in beginner level). mine is messed up and I wonder if yours as well. I tried direct correction but car did not idle correctly so I immediately changed it back to the original

 

when you put the data in the fields , it will save the file with an appropriate name, otherwise it'll use undefined.xml if you leave those fields blank.. Regardless of if its defined from scratch, inherited, or copied.. inheriting adds a data segment that shows its inheriting another files XML data, anything you add or change supercedes it.. Copying is tricky, because if you foul up and don't update the ECUID and other identification info, it will overwrite your old definition.. always make a backup set of your defs on a regular basis for that reason.. It doesnt warn you that your updating or overwriting an existing file.

Also, the order of the wizard is kinda freaky, It doesnt tell you the ECU's ID until AFTER your given a choice of ECU Definitions to choose from, it should tell you first, if you hit the forward and back arrows a few times, it'll crash the software. Plus it doesn't auto-fill the unique ECU data in those fields so you don't accidentally overwrite or redefine an existing definition..

 

i have the same rom ID (9640007). you can just choose the 9640008. the only difference is the rpm scaling for the idle step-up look up table. everything else is the same and you can flash it normally. just dont attempt to fix up the rpm scaling

 

I tried and it idled like an old carberated V8 on a cold morning. That was the quickest flash I ever had on there - 3 minutes.

I immediately reinstalled the former messed up looking rpm table .

 

Thanks for all the feedback guys. I have the same problem with the idle step up scaling.

I'll send my info over to colby.