RomRaider

bravo... i'll be checking this out soon when i get the car running again. thanks a lot for another great addition.

you rock !!

Thanks again.

Don't know if I should start another thread, but look what my tables look like after a few days. Any idea what the lifespan is?

The FLKC table is cleared every time the IAM changes and of course, whenever the ECU is reset (which happens when you flash with Ecuflash for most ECUs).

The only thing I did was get gas. Hmm.

maybe you just have a good tune !

Intersting. My ECU doesn't reset when I flash so I assumed they were all like this. How many of them do? Is it predictable (i.e. the 16bits reset but the 32bits don't, or NA doesn't but turbo does)?

how do you figure it DOESN'T reset??

Most do. Some of the 32-bit ECUs don't. Not sure which ones.

Simplest way is to check if IAM is reset to the default initial value.

eg. after reflash my 32bit ECU the IAM will be reset to 0.5 (default)

How often are the FLKC values re-evaluated? I ask because I connected Learning View again this a.m. and the table looks exactly as it has the previous 3 times (all zero's except for one cell has -0.5). Granted, I am checking every 2-3 days and only driving ~30 miles in between checks, but I am surprised the table always looks exactly the same.

AF Learning values definitely change every time, so I know the check is happening and the program is working.

I don't know if anyone else would get any utility, but a comments field would be nice to have in Learning View. Just a simple 20-30 character text box would allow me to note the tune/fuel when the log was generated. Such as "91 oct winter, map 0191, 50,325 miles".

If you log "fine learning knock correction" and "fine learning table offset", you'll be able to double check if Learning View is reading your FLKC correctly. If the offset reads 1, that would be the cell (0,0) (x,y), 2 = cell (1,0) and so on. If something doesn't match, then I can check the Learning View defs for your ROM.

Of course, it is possible that the table remains the same over 2-3 days -> too many factors to determine exactly how frequently it would change (knock, tune, driving conditions, etc). Also, if your IAM is maxed, FLKC cannot be positive, so that would limit changes in a negative direction only from zero.

I can add the ability for the user to change the file name before it is saved (rather than just the standard date/time).

If you look at the LGT FLKC table, it is very coarse compared to other roms. When I had knock in some of the higher load cells, the FLKC would come and go seemingly random. I used my tracking spreadsheet to watch it.

However, it really turned out that it just depended upon whether or not I hit the localized area within the FLKC coarse cell. So, if I didn't hit the local knock prone area, eventually, the FLKC would clear in that cell but then later it would come back if I hit that cell. Also, most knock prone areas only knocked occassionally (1/3 to 1/2 the time).

Right now, the only FLKC that I have is at 4000 rpm below 1 g/rev. This is in an area that I always drive in. My FLKC is rock solid and never changes. I've driven like this for several weeks and it hasn't changed.

Also, as merchgod pointed out if the IAM changes, the FLKC table would be cleared. This would be something I would watch for especially if I had FLKC in the high load region.

How did you change the ranges?

You change the ranges in RomRaider ("Fine Correction Columns (Load)" and "Fine Correction Rows (RPM)").