being able to put variables (from the project tree) into any/all/some fields would be epic.
It is possible, but in specific places.
Whenever you see an option to assign a “channel,” it means you can assign any real-time value from the log. For example, fuel short term trim has a custom activation condition:
“Hard fuel cut target” is supposed to be a last-resort option to stop the engine from spinning too fast. Why do you feel the need for this parameter to change during operation?
You have tables for “Target Base” and “Target Correction”. Any dynamic limiter should be done using those tables.
I like that most of the time the question is why. This keep the software from getting bloated
But in this case I ask why not? It adds no more boxes or menus but opens up a ton of possibilities.
Why?
Because it makes your product more competitive in a crowded field.
Also, for years I’ve been waiting for rev limiter based on vtec/high cam pressure switch, like stock ecus do it. When the vtec pressure isn’t detected the hard rev limit keeps the motor from reving to redline on low cam. Making that a variable as the hard rev limit pretty much solves that and every other scenario.
I see
Engine → RPM → limiter → target → base
and
Engine → RPM → limiter → target → correction
these can be changed to have anything as the x axis and that could be a variable/function/table/multiple tables
but it’s not necessarily the same as the hard limit, so still some flexibly there (and other places) won’t be a bad thing.
Maybe being able to plug variables into spots that are currently constants is a fundamental change to how the software works so it makes sense to push back on it.