Model-level debugging: a bridge between control engineering and software engineering: Page 5 of 6

February 01, 2018 //By S. Tucker Taft
Model-level debugging: a bridge between control engineering and software engineering
A "model-level" debugger is a debugger that can provide a side-by-side view of a simulation model of a control system (for example defined using Simulink) with the source code produced by an automatic code generator, and allow the developer to use the model instead of the generated source code for setting breakpoints, viewing and updating signal values, and stepping through execution. 

Logging signals and highlighting corresponding
blocks in the simulator.

A model-level debugger shows you how a model-based system performs on the final target, even when combined with hand-written code. You can observe and understand the behavior of the system at multiple levels - the model, the source code, or the assembly code - by stopping at critical points, examining signal values and seeing how they change over time, and stopping within hand-written code as desired. You can thus monitor, test, and debug an entire program, and bridge the gap from the control engineering view of the world of blocks and signals, to the software engineering view of the world of functions and variables. A model-level debugger can help you isolate and identify problems where they are most easily captured, by combining the full power of a low-level debugger with the model-level view of the whole system.


Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.