RomRaider

Only the four I have listed will make a difference.
You could try this to see if it helps.
viewtopic.php?p=129915#p129915

Hey all !

There's no such thing in the logger.xml :



For example, for P76, should I delete the entire parameter tag like :



Sorry for that noob question !

What problem are you trying to resolve?

Sorry, that was half of the message.


The Lorax kindly helped me to get learning tables working thanks to the missing parameters on my 07 EDM Legacy SpecB 3.0 MT.

Unfortunately, it still showed " xxx not defined " on the two tables ( FLKC etc )

So i hoped that removing some parameters would help. I just didn't find the same semantic in my updated legacy logger file, as what you said in a previous post.

I deduced that i had to remove or comment the whole XML "parameter" tags that i didn't want.

I don't have the eclipse project anymore, so i can't reverse engineer to know how it works. ( and github is awful for that )

This means parameter E173 is not defined so the tables can't be displayed. Commenting parameters from the definition will not make this parameter appear. Someone has to open the ROM and find it, then write it into the definition.

Thanks,

I had a updated logger file The Lorax gave me, but i thought that error message was because of the logging parameters.
Thanks to your reply, I've found that it wasn't defined.

Thanks a lot.


Edit, he added it

Hey guys,

I'm also having the recurring issue with LV tables showing crazy float numbers. I need some assistance with finding out the correct address for the FLKC Table start for my ECU/ROM as I still can't get around setting up IDA to open my rom.

rr_system.log and/or a screenshot would be helpful.

Silly me, I thought it's only about the E173 parameter address, otherwise I wouldn't have ommited the logs.

Attaching two TRACE logs and a screenshot - cantopen is prior to commenting out a bunch of parameters, as suggested previously in the thread and wrongvalues is after commenting them out and getting the weird floats, as seen on the screenshot.

Most likely E175 will need to be defined for your ROM, the FLKC tables may be offset from a typical ROM. Or you could switch to the newer ROM D2ZS002C which is well defined.

Try this, which would allow for the larger parameter set to succeed during reading.

Just tried with the new .jar file, but I got pretty much the same FLKC table displayed with two big numbers in there.

For D2ZS002C, try setting Logger parameter E173 to 0xFF8324.

Success!

Seems like D2ZS000C and D2ZS002C are almost identical and it worked for me, too. Altough I didn't expect the FLKC table to have positive corrections, it seems to be accurate now.

Thanks a lot man!

You have positive FLKC because your IAM is less than 1.0

Yeah, after re-reading the knock control strategy threads again the table makes more sense now. I had misinterpreted the conditions for going between fine and rough correction.