RomRaider

It simply determines which cell you in (which is being applied and also has the potential to be changed). So, if you look in learning view, cell 0,0 (x,y) is offset 1, cell 1,0 is offset 2, etc.

Yes, it will be handy.

I didn't realize this parameter was there so I calculated the position based upon logged rpm and logged load. However, there is a time delay between logged parameters so for fast changing rpm, I can end up in the wrong cell. With the logged offset, I can position the logged parameters right next to each other so that the time delay is minimized.

There is also a hysteresis range for both rpm and load for determining a change in the offset (I think it is only in one direction however).

Oh... that's really interesting.

I actually noticed that in the rpm... it seemed like when it was off it was only off in one direction. I thought it had to do with the ordering of how the parameters were logged.

Anyway, this offset parameter will be much more accurate than what I was doing before.

Added version 13.

I deleted the WGDC parameter since it isn't useful.

The initial input for the FLKC table is now taken from merchgod's leaning view tool.

The position in the FLKC table is now determiend from the FLKC offset parameter. Recommend logging these two parameters side-by-side so that there is little time delay between logging them.

1) What do you mean "side by side"?
2) So the procedure would now be something like "Get in car. Use Learning View and dump to file. Log correct parameters for spreadsheet. Get home and import log to spreadsheet. Open Learning View dump and copy to spreadsheet. Have spreadsheet process data"?

When I mean "side by side", I mean the columns of data for FLKC and FLKC offset should be next to each other. The order can vary depending upon how the parameters are selected. This is to minimize the time difference when the data is polled from the ecu.

Since loading a saved profile automatically calls the parameters in alpha order, won't this happen on its own?

You didn't read the instructions...

You are correct, Sir!

I hadn't bothered to boot into windows just to read the instructions since the spreadsheet won't open properly in Excel 11.

OK, I'm getting some strange results from version 13. I've attached the spreadsheet with my ROM tables in it, data from an actual log, and the results from running the spreadsheet. As you can see, the output on the FLKC tab isn't fitting to the FLKC table or if the strangeness here makes the results on the Knock tab suspect.

Thanks!

Well... it turns out there was a serious bug in the spreadsheet. It calculated the number of rpm values in the FLKC table but then I had a debug line in it that overwrote that value and substituted it with 5. That works with the LGT but it doesn't work with any other rom.

Oh well..

I changed the code and I reran your data. It appears to work correctly now.

Just downloaded version 14 from the first post in this thread.

Thanks for the quick turn around! Now that I'm back to tuning my car, I'm going to be using this frequently.

I'm trying to use this spreadsheet but I got an error "Run time error 13". Type mismatch. What could be wrong?

I've attached the spreadsheet with an actual log and my rom information keyed in.

Looks like you messed up your rom tables. Re-input them properly.

Also, lines 2719 to 2725 have the same time stamp but that shouldn't affect any of the calculations.