I mostly work with the evo7's 98640014 id but more recently I've been getting into the RA 90550001. The more I play around with this rom the more I notice it's similarities with 98640014. For instance 2Byte load and rpm are the same for both.

I changed the Int ID of one of my 98640014 roms to 90550001 and it opens fine in ECU flash....all the tables and values are good...my definition file for both roms are mirrors. My question is this:

Does changing the Int ID actually change the rom to that specific ID? I'm guessing not, just changes the way ecuflash sees the rom ID. If this is so it leads me to a second question:

Would it be potentially dangerous to change the init ID of my 90550001 to 98640014 and vice a versa? By changing this number, what else am I changing?

I've only divulged into the hex code lightly, so I don't know if their are significant differences I'm unaware of that could cause a problem. But so far, I can't see any differences in the location of tables between both roms.

Someone chime in.

 

No it doesn't change it to that ROMID. The ID is just a unique identifier which allows EcuFlash to apply a set of XML to it.

The danger in changing it is the XML might be different.

ie in the future we might discover "super dooper table xyz" which might have a different location in 90550011 that in 98640014.

if you have changed the 90550011 to 98640014 then the XML wont work, and you will explode your car.

No need to change the ID...

 

Thanks for putting it so eloquently.

 

no problems :P

 

I'd seen tuner change the rom-id for their tuned map (protection of their property). For noob, they won't know the correct romid and the correct xml if they download from their own car (unless he keep trying with different xml). Some may even use a simple xml to match the "fake" romid and then inherit from another xml (cause confusion).

That give disassembler extra work for future development and confusion when the noob seek for help (from evom/openecu).