RomRaider

In reference to LTV supporting SD ROMs.
viewtopic.php?f=14&t=9745&start=90

As of RomRaider release 0.6.0, a customization feature has been added to allow a user to change the tables the LTV feature looks for in the ECU definition.

In the RomRaider program directory you will find a folder named 'customize'.By text editing the file 'ssmlearning.properties', you can add the appropriate SD map names to the list 'af_table_names=', 'flkc_table_column_names=' and 'flkc_table_row_names=' properties.
It is important to note that each map name is : delimited and trailing spaces are important and will be interpreted in the name selection, as you can see in the default list of names.
To add a SD map name, append it to the list ensuring a ':' terminates the line.
If you will never use LTV with a MAF ECU then you can replace the existing names, again, terminated with a ':'.

Ensure that the SD definition file is listed first in the Editor Definition Manager to select the SD definition before any other definition files.

The default list for MAF is:


In the case of CarBerry, adding 'A/F Learning #1 MAP Ranges' to af_table_names will cause LTV to select that table to interpret A/F learning.

my car is 13 BRZ ZA1JA02N
when i try to start LTV, the table doesn‘t display.
and i try to use learning view, also failed.
the log is


is there an another method to log knock for my BRZ

BRZ is not supported by LTV or LearningView.

OK ,sincerely thanks, can i use an another app to log knock with open port2.0? except the oft

The Openport 2.0 built-in logger maybe an option.

built-in logger need resolving ram address of ecu. All can i find is c or g series logcfg.txt
i'm trying to find N series logcfg.txt （Chinese domestic market）

Hi,
I like to ckeck ltv. I have to do a test drive, whitout notebook. Only need to read ltv after testdrive, right?

I think ltv is stored in the ecu. No need to do livelog with my notebook. Or i am wrong?

Have a nice sunday...

Would someone be able to help me figure out why I'm getting random numbers in the FLKC table of the LTV? I think the logger definition may need editing but I'm not certain. Attached is the rr_system log if that will help. I think the LTV starts somewhere around line 1346.

Your log does not have any info in it pertaining to the read of the LTV values.
Possibly the RAM location of the FLKC table is wrong.
Make sure the address for extended parameter E31 for ECU ID CD2A904007 is set to 0xFF3384

Thanks for the response. Parameter E31 does have the address set to 0xFF3384:

<ecuparam id="E31" name="IAM (4-byte)*" desc="E31-KCA = (KA (max) map value * IAM) + FBKC + FLKC. Total Timing = KCA + base timing + timing compensations" target="1">

and

<ecu id="CD2A904007">
<address length="4">0xFF3384</address>
</ecu>

I noticed parameter E41 has the address set to 0xFF84E0:

<ecuparam id="E41" name="Fine Learning Knock Correction (4-byte)*" desc="E41-Current learned correction that is being applied which is stored and applied across specific load and rpm ranges." target="1">

and

<ecu id="CD2A904007">
<address length="4">0xFF84E0</address>
</ecu>

Do you think this address needs to change or a new parameter created? I noticed in this thread that some people had to create a new parameter E173 or E175?

It shouldn't need an new E17x parameter as calculating the table offset address from the E31 address should be enough.
A more detailed rr_system.log may help isolate the problem while you use the LTV feature.

I deleted the existing rr_system.log file, set the debugging level to TRACE, and generated a new rr_system.log file while sing the LTV. Attached is the resulting rr_system.log.

It's using E31 to calculate the offset to the FLKC table location but that's not where it is in RAM.

Try adding these lines to the E173 section of the logger.xml (just use Notepad to edit the XML file):

I added the lines but I'm still getting random info in the LTV. Here's the image and another log.

The ECU def specifies the wrong number of rows for your FLKC table.
It should be 4 rows and 5 columns for a total of 20 cells in the table.
You can change your ECU def, find "Fine Correction Rows (RPM)" including the quotes. The first defines only the address for your ECU, the second occurrence is the table definition.
There are two entries in that section for sizey="6", change both to 3
Then delete the three lines:
It should look like this after.

Save the file.

This is the raw data from the ROM I have for the rows and columns, did you change yours?
If so you need to reset them and reflash the ECU with the updated values.