Collect Ranges

Benchmark idealized model behavior

The Fixed-Point Tool uses ranges collected during this phase of the conversion process to propose data types for your model. Do this step after you have prepared your system for conversion Prepare System for Conversion. You can collect ranges through simulation with instrumentation, range analysis, or a combination of the two. To determine which approach you should use, see Choosing a Range Collection Method.


DataTypeWorkflow.ConverterCreate fixed-point converter object



Collect Ranges

Second step in autoscaling workflow.

Autoscaling Using the Fixed-Point Tool

Workflow steps for autoscaling using simulation data.

Fixed-Point Tool

Introduces the Fixed-Point Tool

Convert Floating-Point Model to Fixed Point

Details the steps taken to convert a floating-point model to fixed point.

Control Views in the Fixed-Point Tool

How to filter information in the Fixed-Point Tool.

Run Management

Learn how to manage multiple runs and set up shortcuts with the shortcut editor.

Fixed-Point Instrumentation and Data Type Override

Control fixed-point instrumentation and data type override settings to gather range information on your model.

The Command-Line Interface for the Fixed-Point Tool

Highlight the differences between the command-line interface workflow and the Fixed-Point Tool workflow

Convert a Model to Fixed Point Using the Command Line

Use the command line interface of the Fixed-Point Tool to autoscale a model.

Collect and View Simulation Ranges for Referenced Models

The Fixed-Point Tool logs simulation minimum and maximum values (ranges) for referenced models.


How Range Analysis Works

Describes how the analysis derives range information

Derive Ranges at the Subsystem Level

Differences between deriving ranges at the model level and at the subsystem level

Derive Ranges Using Design Ranges

How range analysis using design range information when deriving ranges.

Derive Ranges Using Block Initial Conditions

This example shows how range analysis takes into account block initial conditions.

Derive Ranges for Simulink.Parameter Objects

This example shows how the range analysis takes into account design range information for Simulink.Parameter objects.

Intermediate Range Results

Interpret the Intermediate Maximum and Intermediate Minimum results in the Result Details tab.

Simulink Blocks Supported for Range Analysis

Summary of range analysis support for Simulink® blocks.

Unsupported Simulink Software Features

Overview of software features that are not supported for range analysis.


Prevent The Fixed-Point Tool From Overriding Integer Data Types

This section explains how to maintain integer data types in your model when using data type override

Resolve Range Analysis Issues

The following table shows the different types of range analysis issues and the steps to resolve them.

Fixing Design Range Conflicts

If you specify conflicting design minimum and maximum values in your model, the range analysis software reports an error.

Insufficient Design Range Information

If the analysis cannot derive range information because there is insufficient design range information, you can fix the issue by providing additional input design minimum and maximum values.

Providing More Design Range Information

This example demonstrates how to proceed if the analysis cannot derive range information because there is insufficient design range information.

Troubleshoot Range Analysis of System Objects

How to reconfigure a System Object, if necessary, so that ranges can be derived for the model.

Was this topic helpful?