SSM and FLKC (degree of correction)

Mart · **Posted:** Thu Aug 12, 2010 1:02 pm

Hi,

Looking at the definition for an 06 STI, I am able to locate for an SSM query:

FLKC Columns load: 0x0C864C
FLKC Rows RPM: 0x0C865C

now I am trying to fetch the data in that table but I am unable to figure out what address to query. is there something I am missing in the def file?

thanx

Mart

nsfw · **Joined:** Thu Nov 23, 2006 2:23 am **Posts:** 2565

The table itself lives in RAM, so it cannot be altered with a ROM editor, so it's not in the ECU definition.

Merchgod mentioned a while back that the table's RAM address is near something else that the logger supports, but I can't remember what. Might have been a Learning View thread, I don't remember. I realize that doesn't give you much to go on, but that's all I got.

Mart · **Posted:** Tue Aug 17, 2010 12:20 pm

I can confirm that on mine, it is IAM address + 0x14 is where the data is sitting..

NSFW wrote:

The table itself lives in RAM, so it cannot be altered with a ROM editor, so it's not in the ECU definition.

Merchgod mentioned a while back that the table's RAM address is near something else that the logger supports, but I can't remember what. Might have been a Learning View thread, I don't remember. I realize that doesn't give you much to go on, but that's all I got.

nsfw · **Joined:** Thu Nov 23, 2006 2:23 am **Posts:** 2565

That sounds sorta familiar.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

FLKC RAM start = IAM + 0x14 (32-bit ECU) is the case most of the time but not always.

Mart · **Posted:** Wed Aug 18, 2010 11:49 pm

thanx for the confirmation.

Mart

merchgod wrote:

FLKC RAM start = IAM + 0x14 (32-bit ECU) is the case most of the time but not always.

dschultz · **Posted:** Thu Aug 19, 2010 12:50 am

IAM+0x14 in my ROM too.
I found the FLKC RAM table address defined in a few different places in my ROM. You then just need to know the axis sizes to be able to retrieve the correct amount of data and display it in a nice table format.

Mart · **Posted:** Thu Aug 19, 2010 12:58 am

Yeah that is the next thing (axis sizes) to find via SSM (if doable)...

dschultz wrote:

IAM+0x14 in my ROM too.
I found the FLKC RAM table address defined in a few different places in my ROM. You then just need to know the axis sizes to be able to retrieve the correct amount of data and display it in a nice table format.

dschultz · **Posted:** Thu Aug 19, 2010 1:20 am

You know that from the ROM def. You posted that in your first post... ;-)

For my ROM the table is 5 x 7. So I would need 35 x 4 byte values. The RAM area seems to have the values in two sets of 4 bytes. So I'd have to pull back 70 x 4 byte values to get the entire table.

hmanxx · **Joined:** Wed Jul 12, 2006 3:01 pm **Posts:** 154

Assuming we know the exact RAM address of FLKC ..can we use the Testwrite application on Romraider to overwrite certain cells on FLKC.

Application
1) To be able to temporarily insert timing retard into the table,the objective is to enable car to run on lower grade petrol without reflashing new map

As occasionally i need to travel to neighboring country which only lower grade petrol available..

It is even better ,we add simple code .will do the retard or reference to new FLKC with some gesturing e.g defrogger switch toggling..

Are data on FLKC RAM area stored in 4bytes floating point format?

Sasha_A80 · **Posted:** Mon Sep 20, 2010 4:06 pm

Writing into calibration region may be not allowed in some ROMs. I have this one.

1 - yes, if possible. Alternatively you may use SSM write 0x6F - IgnitionRetard. 0-5 deg is allowed (clipped if written out of bounds). More over you may do this dynamically IgnRetard vs (PRM/Load).
2 - 32 bit ecu stores corrections 4 byte float.
But. You are to put those 4 bytes bit inversed just after the value stored.

RomRaider

SSM and FLKC (degree of correction)

Who is online