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

Displaying values for signals dynamically.

By maintaining exact traceability between code variables and their corresponding signals in the simulation model, a model-level debugger can display signal values as they are updated. It can grey out blocks that have been executed, to show which signals have been updated and which still have values from the previous computation cycle.


Changing signal values during the execution.

A model-level debugger provides a powerful way to analyze the specific behavior of a given simulation model. By changing signal values for one or more iterations you can direct the model into a desired state of interest to the debugging session.

A model-level debugger can store in a file all or some signal values obtained during a debug session. When opening this file in the simulator, you then have links to the corresponding simulation block of each signal. This helps trace problems identified at the code level to corresponding model-level blocks, where you can investigate them further in the simulator.

Vous êtes certain ?

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

Vous allez être rediriger vers Google.