RomRaider

Hi everyone,

That's my first post and it is in troublesshooting...

So i have a new UK Sti 02.
I read the rom with Ecuflash :

Internal ID : A4RN1000
Inherits: A4RN200H

(First news :The ROM is tune compared with the same stock Map downloaded here...)

And when i read my rom with Romraider, 2 ERROR windows open :



And F threshold

When i open my rom with ecuflash i dont have error window but when I open the threshold it's written "no match"

Do someone knows this error ?

thanks
Leo. (sorry for my english )

The errors indicate that the content of the tables in the ROM do not match any of the available options according to the definition file for that ROM. So, either the definition is wrong, the ROM file has been altered by some other means than EcuFlash or RomRaider.

Ok really thanks dschultz.

I have the lastest definition so It may be altered by another software...

The car is stock. What do you think about :
-flash my ecu the stock ROM find here ?
-or modify my current ROM with copy/past from the stock ROM ? (all maps present in romraider)

Because I don't know what was modify that romraider can't see...

RomRaider is telling you it sees two tables wrong.
Those two tables do not match the conditions described in the ROM definition.
You can look in the definition file to see what code is expected.

I'd start with a good stock ROM file and then copy over your map changes from your not so good ROM.
You can also compare the two ROMs byte-for-byte to see what has been changed.
On Windows the command: fc /b rom1 rom2
Will do the job.

news !

My ROM read from ecu :
=> Size : 160 Ko
=> Last adress : 27FF0

Stock ROM (same iternal ID) :
=> Size : 192 Ko
=> Last adress : 2FFF0

The error comes because of the Catalyst threshold F and G adress can't be find, it is at 2BA0D and 2B9F7 but my ROM stop at 27FF0 !?

Just to have a look when I open my ROM and the stock ROM



Can't understand because that same IDs that the stock ROM find in the forum !?

Edit : reading FAQ... difference between 160/192 Ko ROM

After reading ! I'm going to change ROM size to 192Ko, to test if romraider can read all the maps.

My problem :
What ROM size should I flash in my ECU ?
=>Because I read a 160Ko from it.
=>If 160Ko, to have a stock ROM, I have just to copy all maps from the stock 192 to my 160 ?


But why in the FAQ is it written "So which should you use? RomRaider and EcuFlash will work with either size ROM, so you don’t have to worry about it." ?

If size change, part of adresses change and romraider can't read maps

It doesn't matter, both RR and EcuFlash can read either size and adjust them accordingly.

Size is not the problem here. The problem is the data in the ROM (regardless of the size of the file) for those two maps does not match what the ROM definition XML indicates should be in the ROM. Each map has two states on / off and the data at those addresses must match one of the two states. Here are the sequence of bytes that need to match.

"Catalyst Readiness Threshold Fix F" storageaddress="0x2BA0D" sizey="10"
"on" data="FF FF FF FF FF FF FF FF FF FF"
"off" data="03 33 03 33 05 33 07 33 09 9A"

"Catalyst Readiness Threshold Fix G" storageaddress="0x2B9F7" sizey="10"
"on" data="FF FF FF FF FF FF FF FF FF FF"
"off" data="06 AC 06 AC 0A 02 0D 58 14 04"

Both RR and EcuFlash are telling you that neither state matches your ROM file data.
Note: the addresses in the definition are based on a ROM size of 192kB and RR and EcuFlash will internally convert the ROM to that size for editing.

Ok thanks Dale !

I converted my 160Ko ROM in 192Ko, results :
0x2BA0D : FF FE FF FE FF FE FF FE FF FE
0x2B9F7 : FF FE FF FE FF FE FF FE FF FE

therefore different...

Firstly : Why "FF FE..." and not "FF FF..." :
=> Is it the right datas for my ecu/engine ?
=> Or last tuner changed in wrong values ?


Secondly : With this data what does the ECU ?
"When enabled, this maximum threshold is set to its highest value, expanding the valid range for one of the catalyst monitor tests"
=> What the "catalyst monitor test" ? and why set the threshold at a highest value ?


After use an Hex editor, I have just to open the ROM with RR/Ecuflash to have good checksum ?
(or just flash the stock ROM but it's not educating )

I'm not familiar with how the values are used in the ECU code.

The best option is to set them to the 'on' sequence, set all 10 bytes to FF with a hex editor, save the file and proceed with your tuning.

Ok thanks, I'll try to

I'm getting the same errors when opening my original rom. My car is an ADM 02 STi stock apart from 3 inch TBE with high flow cats. I also downloaded a copy of the stock rom (60P) from here and that one is also getting the exact same errors.
https://web.archive.org/web/20211026224 ... bilityList

My RR definitions are the latest too. I'm not sure what the problem is but I'm not too worried since this is for the Cat so it shouldn't really effect anything (I hope). And since its the same in another stock image i figure the values are correct so it should be fine as is. Don't take my advice as I'm new to this but just my 2c.

If I find any issues with this approach along my way I'll post here. If you don't hear from me means no issues

The issue is with the definition for this ROM A4RG060P. Here's the correct info if you care to replace the lines in your ecu_defs.xml file:

Awesome dschultz! That code worked a treat

Thank you!

I have similar problem, I have read map from my ecu for the first time, in ecuflash everything works as expected, no errors. But when I open the map in RomRaider, I am getting 2 similar errors (ERROR - data mismatch):
Table: Catalyst Readiness Threshold Fix F,
Table: Catalyst Readiness Threshold Fix F2
Definition file or ROM image may be corrupt.

My car has been mapped in the past, could that be the reason why I get this error?
And the most important question is: is it dangerous? Can it e.g. brick my ecu if I edit map with such error and upload it to the ECU? Or does it only mean that I won't be able to edit afformentioned tables?

You get the error/warning because the value in your ROM for those parameters does not match what the ECU def specifies them to be. Someone edited them to something non-stock.