Versatility and saving SRAM space
- versatility means that things are possible that otherwise would not be possible - users often request different deviant (sometimes unreasonable) function
- only those features consume space that are actually used
- Remember that this is certainly not our major tool to save space. Using tables directly from EEPROM/flash saves appr 1000 bytes, so that is the main space-saver
Important warning: tuningsoftware issues
Unfortunately the worst part of this is the tuningsw side, to make it configurable that is. We will NOT DEPEND ON THIS UNTIL that is solved
Might not be hard, as MegaTune vemsv3.ini can be generated from a particular dynamic configuration. But anyway, must be solved.
Textually configurable
yacc / lex / whatever can be used to generate the binary translation of the human-editable language
Graphically
The dynamic config will originally not be graphically editable.
TuningSoftware support for revpol is not more complex than other competing schemes (at least when considering only the cases that less effective scheme ssupport).
Full graphical editor for the reverse-polish language will not be available this week, unless it is already implemented somewhere on sourceforge, look for graph editors on LogAnalysis.
After all, all it takes is connecting the (input/output) ports of building blocks (like "blend" is a building block in our exampe below).
Dynamic configuration - THE best approach
Far the best way for dynamic configurability is
- simple language can be used
- stored in a compact way
- efficient for the firmware to execute
Eg. a stack-based reverse-polish language (in short, let's call "revpol"), like postscript. (and maybe Forth ?). But stored in binary form.
This means a user-specified function like\n
blend( tablelookup( vetable, RPM, MAP ), tablelookup( vetable, RPM, TPS ), curvelookup( MAP_TPS_blend, RPM ) )
can be stored in appr 15 bytes. with 4 function codes.
The blend function code is the very last byte, it eats 3 variables from the stack, calculates the blend result that it pushes back to the stack.
Another example:
- A + B * C is represented as B, C, *, A, +
But remember we mostly use it for complex functions like
- tablelookup (2D table)
- curvelookup (1D curve)
- blend
- interpolate
- read input
- store / actuate output (or variable that can be logged)
- read flash (care is needed to avoid access to unauthorized area)
- ...
The implementation is very fast, takes little SRAM and flash, and very efficient. Some functions must allow to load/store data from SRAM (/ flash / EEPROM), not just stack (the tablelookup above is a clear example).
When someone wants to blend between 2 tables according to a manually actuated switch, the other according to actual position of the variable valves, we really want to avoid the configuration (+documentation) blowup that happens with the traditional config method.
Scheme language might be good to look at, maybe there is an "embedded scheme" implementation that could be used with little effort
- http://www.miata.net/sport/Physics/08-Program.html
- http://sourceforge.net/projects/escm/
- http://citeseer.ist.psu.edu/dube00bit.html
- GenBoard/UnderDevelopment/FirmWare/MiscOutputs - some ideas will be merged to this page
- GenBoard/UnderDevelopment/FirmWare/ConfigRelated - config changes that remain within "old style" boundaries