apalrd wrote:
I think the model-based programming methodology is often confused with programming in modeling languages. In a lot of ways, using engineering units and basing equations on physical relationships is the core concept of model based programming. I think EL is right to call it a 'model'.
Someday, you will run out of memory, and it will be an issue. Your model will probably grow a lot before that.
I'm working in the secondary heap they call it, Jim said its faster....its about 2/3 full. The primary is the same size and unused....I have a long long way to go
Quote:
I use the display scaling for all kinds of things, like inverting factors (as I mentioned earlier), multiplying loop counts by the loop time into seconds, doing fixed-precision integers, etc...
I can create virtual channels that show only on the display to put data in a form I want to view it vs the form the ecu actually needs. I've not messed with that much yet, a couple times....really handy for data analysis. The o5e project used TunerStudio which where everything had to be defined by what it was and how I wanted to view it....what a pain in the butt that was compared to everything is just right (because everything is floating point) or right click "add row" to change table sizes on the fly or click "add item" or "open item" to to add to or alter the model on the fly. ELC is pretty friendly compared anything I've used before.