What it is
Most lambda corrections are fixed to one input, like coolant temperature or air temperature. The generic correction isn't. You decide what it depends on.
Default: one value
As shipped, the table has a single cell. Whatever you put there offsets the entire target lambda table. That's handy for a quick global test, for example seeing how the engine responds to running every target a little richer, without editing the main table.
Custom: your own axes
Give the table axes and it becomes a proper correction map. Haltech's help file shows it set up with TPS and RPM as an example only. Pick axes that describe the condition you want to correct for. A switch input for a street and race mode, or a boost-based adjustment, are the kinds of jobs it suits.
Tips from the shop
- Keep it empty (or at zero) unless you have a clear reason. Hidden corrections are the first thing that confuses the next tuner.
- Log the final target lambda channel after you enable it, to confirm the offset is doing what you think.
- If the correction is really about fuel type, use the fuel composition correction instead.
