The Fixed-Point Tool is a graphical user interface that automates specifying fixed-point data types in a model. The tool collects range data for model objects. The range data comes from either design minimum and maximum values that objects specify explicitly, from logged minimum and maximum values that occur during simulation, or from minimum and maximum values derived using range analysis. Based on these values, the tool proposes fixed-point data types that maximize precision and cover the range. With this too, you can review the data type proposals and then apply them selectively to objects in your model.
|Fixed-Point Tool Capability||More Information|
Deriving range information based on specified design range
Proposing data types based on simulation data
Proposing data types based on derived ranges
Proposing data types based on simulation data from multiple runs
Debugging fixed-point models
To open the Fixed-Point Tool, use any of the following methods:
From the Simulink® Analysis menu, select Fixed-Point Tool.
From the model context menu, select Fixed-Point Tool.
From a subsystem context menu, select Fixed-Point Tool.
If you want to open the tool programmatically, use the
For more information, see
The Fixed-Point Tool contains the following components:
Model Hierarchy pane — Displays a tree-structured view of the Simulink model hierarchy (see Model Hierarchy Pane).
Contents pane — Displays a tabular view of objects that log fixed-point data in a system or subsystem (see Contents Pane).
Workflow pane — Displays parameters for specifying particular attributes of a system or subsystem, such as its data type override and fixed-point instrumentation mode (see Dialog Pane).
Toolbar — Provides buttons for commonly used Fixed-Point Tool commands (see Main Toolbar).
Shortcut Editor — To open the Shortcut Editor, on the far right-hand pane, click the Add/Edit shortcuts link. This editor provides the ability to configure shortcuts that set up the run name as well as model-wide data type override and instrumentation settings prior to simulation or range derivation. For more information, see Run Management with the Shortcut Editor.