MAP / TPS WOT Determination

[GernBlanston]

I spent a couple hours yesterday trying to figure out how the WOT Determination behavior is different when the "Use MAP to determine WOT" box is un-checked, and wound up pretty frustrated. First, there is definitely a bug in the Live Tuning for those tables (1.1.9.6 - S2000). I have always left the "Use MAP ..." box checked, and it's always worked fine. However, after uploading a calibration with that box un-checked and live tuning enabled on the WOT determination tables, then later uploading another calibration with it checked again (while the live tuning option was still enabled for these tables), it continued triggering on TPS. The only way I could get it to switch back to MAP was to disable the live tuning on those tables and upload it again.

That said, I'm still really curious how the tables are supposed to work. If the "Use MAP ..." box is checked, do the TPS WOT tables do anything at all? If the "Use MAP ..." box is un-checked, does the MAP WOT table do anything at all? I thought maybe there would be some interdependency between the TPS and MAP tables if the box was unchecked.

Also, what does the TPS MAP determination LOW table do? It doesn't seem to have any effect at all for my S2000. The effect of TPS MAP det High is very obivous when I change the values, but the changes I make in the LOW table don't do anything obvious. Even when I set the max target throttle map to 50% in order to force repeatable conditions, changing the TPS MAP det Low values seems pointless.

EDIT: I should mention that my S2000 is NA with basic bolt-ons.

[Hondata]

I've tested with 1.3.2 and it works as I would expect.

The 'Use MAP to determine WOT' selects whether to use MAP or TPS to determine WOT. Both tables are used elsewhere, but the main function is to switch out of closed loop. Be aware that there can be other factors in effect too - for instance, a delay timer will stop rapid switching back and forward between open & closed loop based on throttle.

The difference between 'low' and 'high' is for hysteresis. The 'high' table is where the closed -> open loop transformation occurs. The 'low' table is where the open -> closed transformation occurs. The help file does not mention this and I'll update it.

[GernBlanston]

I've tested with 1.3.2 and it works as I would expect.

The 'Use MAP to determine WOT' selects whether to use MAP or TPS to determine WOT. Both tables are used elsewhere, but the main function is to switch out of closed loop. Be aware that there can be other factors in effect too - for instance, a delay timer will stop rapid switching back and forward between open & closed loop based on throttle.

The difference between 'low' and 'high' is for hysteresis. The 'high' table is where the closed -> open loop transformation occurs. The 'low' table is where the open -> closed transformation occurs. The help file does not mention this and I'll update it.

That makes much more sense! Maybe it would be more clear to change the labels on the TPS tables to something like "TPS PT Determination" and "TPS WOT Determination".

BTW, in case it hasn't already been fixed in a newer version, there is also a problem with the Short Term Fuel Trim Min / Max. In 1.1.9.6 you can enter a negative value for the min AND max value, which causes some very undesirable behaviors. I believe ther should be a validation that the Min value is always less than or equal to 0, and the Max value is always greater than or equal to 0.