RomRaider

Hi, I have 02 bugeye wrx and have installed carrbery rom. After doing so I cannot read knock correction from the learning view, is it normal?
There no problem to open and edit the rom, start logger and read values live.
I also cannot read fault codes.

Pics: https://imgur.com/a/JJb04bl

im having the same problem as well. ive tried some things but i just ignore it and i do pulls logging the flkc and match it up to see exactly where its happening. if you do figure this out please repost ur solution.

I remember having the same question. Knock correction in Carberry works different than in the Factory tune. The factory tune has a separate map it uses the calculate the total ignition timing. That Knock Map is an Addition to the base timing map. When it senses knock, it will only pull the amount of timing listed in that knock map at that cell.
Say a certain cell in the knock map says 5*. If it senses knock in that area, it will only pull 5*.

Now carberry works different. Carberry works by running the base ign map all the time. The Knock Map is the map of how much timing it can subtract in any given cell. Carberry works by subtracting the cell in the knock map only when it senses knock. Otherwise, it will always run the Base Ign Map values.

So when running carberry, when you you see 0 in the knock feedback and correction, that is a good thing. when you see negative numbers there, that is when it senses knock.

In summary> OEM Knock map Adds to Basemap all the time
Carberry Knock map only used when knock is detected and subtracts from the base map.

Hope this helps

There's some weirdness in the definitions.

Learning view works fine with the standard definitions (non-SD, found here - viewtopic.php?f=8&t=1642 )

Just be aware the load values on the X-axis are halved.

I am new to carberry. I tried using learning view and in the FLKC table, a few cells have large numbers in blue. For example in the 5600+ rpm 1.33-1.65 load cell, the value is 31745.00 in blue. What do these values mean?
Thanks msspag

You may need to change the axis names that are used to read the tables.
In the text file "C:\Program Files (x86)\RomRaider\customize\ssmlearning.properties" change the second line to:

Save the file (you might have to use admin rights), restart the Logger and try LTV again.

viewtopic.php?p=151457#p151457

Very large blue entries are the result of reading past the end of the table and interpreting the value incorrectly. Check that the table axis sizes are correct in the editor def.

Dale,

How do I get LTV to target a different FLKC location.

Currently it targets E173, and shows up incorrect data, so how can this be changed to show E12 data, or another set of data tables.

Yours in advance,


Mark...

It should be automatic based on CAL ID.