RomRaider help? ECU definition cannot be found even when present?

[Xaftos]

Hi guys!

As the title says I'm currently having issues with RomRaider not detecting or having incompatibility issues with my definition. I have added the .xml for my tune provided by Shiv into the definition manager, applied and saved, so all should be good in that regard, correct?

Well, when trying to open my .bin image, it brings up the error "ECU definition not found". I'm not sure if I'm just missing something stupid, or if my .xml and .bin are incompatible for whatever reason, but I need some assistance regardless.

Any ideas as to what may be causing my problem?

Here are some screen grabs of my RomRaider to show that I'm doing everything hopefully correct.

Thanks!

[stefodrom]

i got this message when the Cal ID's are not matching.
Open the Xml with a notepad and look for the vehicle Data and check if it has the same Cal ID as your Rom

[Wayno]

Rom is K00D and definition is F00D, therefore you don't have a definition for K00D.

[Xaftos]

Originally Posted by stefodrom

i got this message when the Cal ID's are not matching.
Open the Xml with a notepad and look for the vehicle Data and check if it has the same Cal ID as your Rom

Originally Posted by Wayno

Rom is K00D and definition is F00D, therefore you don't have a definition for K00D.

Thank you both for your responses. I have changed the ID's to K00D and it seems to have detected and read the file. However, I get an "ERROR - Data Mistmatch" window that pops up now saying that the Definition file or ROM image may be corrupt. I'm assuming this is a result of me just changing the F to a K? Should I be worried about this? It comes up for every folder within the ROM. Here is an image for reference as to what I'm seeing.

[Xaftos]

Seems to be working okay I think? I'm still able to load a lot of tables, but maybe some (or a majority) are excluded due to this data mismatch error?

[Xaftos]

Alright final post regarding this issue which seems to have been resolved in a much easier fashion than I expected. So my main goal with all of this was to modify my ROM to allow my car to backfire, which it pops once when shifting at high RPM but that's about it. More pops when releasing the accelerator would be nice. Any idea how to accomplish this given this table? I don't think the numbers on the left side are supposed to be that high, but hell do I know? What numbers should I change to accomplish this?

[stefodrom]

Do not use this Def file, its a wrong one.

For sure you can open it editing the Cal ID.

But the storage adresses are not matching your rom, and thats why it doesn't display the correct values

Look for a "real" K00D Definition and do not edit something with this one

[Wayno]

Originally Posted by Wayno

Rom is K00D and definition is F00D, therefore you don't have a definition for K00D.

Rom is K00D and definition is F00D, therefore you DO NOT have a definition for K00D.

[steve99]

Originally Posted by Xaftos

Alright final post regarding this issue which seems to have been resolved in a much easier fashion than I expected. So my main goal with all of this was to modify my ROM to allow my car to backfire, which it pops once when shifting at high RPM but that's about it. More pops when releasing the accelerator would be nice. Any idea how to accomplish this given this table? I don't think the numbers on the left side are supposed to be that high, but hell do I know? What numbers should I change to accomplish this?

Every rom calid has tables in differnt locations, you cannot just change the calid in a def and expect it to work.

This is an easy way to brick your ecu.

Please read the Romraider tips link below.

Only use the KOOD def that came​ with your tune from shiv, if you did not get a def from shiv then you will need to ask him for the correct def

[Xaftos]

Originally Posted by stefodrom

Do not use this Def file, its a wrong one.

For sure you can open it editing the Cal ID.

But the storage adresses are not matching your rom, and thats why it doesn't display the correct values

Look for a "real" K00D Definition and do not edit something with this one

Originally Posted by Wayno

Rom is K00D and definition is F00D, therefore you DO NOT have a definition for K00D.

Originally Posted by steve99

Every rom calid has tables in differnt locations, you cannot just change the calid in a def and expect it to work.

This is an easy way to brick your ecu.

Please read the Romraider tips link below.

Only use the KOOD def that came​ with your tune from shiv, if you did not get a def from shiv then you will need to ask him for the correct def

Lmao that would've been bad then, aye? Well I've emailed Shiv asking for the K00D file as opposed to the F00D file and hopefully I get it relatively soon.

Thanks guys!