Hondata

Hello,

I've noticed that when using the boost tables, you can't view the additional columns, in the Knock/WOT maps.
Wasn't it supposed to show the columns in all maps?

Tested this in V4.2.5 and 4.0.8 of KManager and the behavior is the same.
How can i tune the missing columns?

Thanks in advance

Those tables only have 10 columns.

ok, but what is the behavior when the map sensor readings are bigger than the last value of the table?
it assumes the last value of the highest map value of the table for that rpm? or just ignores the table?

You can rescale the columns if you need to go higher in boost.

Spunkster wrote:You can rescale the columns if you need to go higher in boost.

I would, but it doesn't let me rescale the load columns in those specific tables. The option when you right click the load columns is greyed out.
Can you clarify about what happens when the map sensor readings are bigger than the last value of the table?
Is there any kind of limitation that forces these tables to only have 10 columns?
Sorry for all the questions, but i really want to try to understand this, to figure out the best way to get around this.

All the fuel and ignition tables have this option in K-Manager. What table are you referring to?

I'm refering to Knock/WOT tables.

Those tables just read from the last column when you go higher than that value.