Model-level debugging: a bridge between control engineering and software engineering: Page 3 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. 

Examples of use of a model-level debugger

The simulation model can be displayed and browsed within an IDE, as a read-only view showing all simulation blocks, subsystems, and sub-model references.


Displaying the model in an Integrated Development
Environment (IDE)

You can define the model's inputs via using the standard simulator capabilities, or even using completely separate models. A model-level debugger can record all inputs provided


Creating input for the target using the simulator.

to the model and create a debugging session where the same inputs are sent, under control of the debugger, to the generated code. The behavior of the model and the generated code with these inputs can then be observed and debugged in sync.

Just as you can insert a breakpoint in the source code, a model-level debugger lets you insert a breakpoint directly from the model view. Execution will subsequently pause when reaching the code corresponding to the block containing the breakpoint.


Inserting a breakpoint on a given block or model
reference.

 

 


Vous êtes certain ?

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

Vous allez être rediriger vers Google.