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.


fxptdlgStart Fixed-Point Tool


DataTypeWorkflow.ConverterCreate fixed-point converter object


Working with the Fixed-Point Tool

Data Type Conversion Overview

Convert data types in your model to fixed point in one of three ways.

Autoscaling Using the Fixed-Point Tool

Use the Fixed-Pint Tool to convert a system from floating point to fixed point.

Use the Fixed-Point Tool to Explore Numerical Behavior

This example shows how to use the Fixed-Point Tool to compare floating-point and fixed-point data types.

Choosing a Range Collection Method

There are three methods for collecting ranges on which to base data type proposals.

Control Views in the Fixed-Point Tool

Filter, sort, and analyze information in the Fixed-Point Tool.

Run Management

Learn how to manage multiple runs in the Fixed-Point Tool.


Collect Ranges

Second step in autoscaling workflow.

Convert Floating-Point Model to Fixed Point

Use the Fixed-Point Tool to convert a floating-point model to fixed point.

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

Highlights 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.


How Range Analysis Works

Describes how the static 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 uses design range information when deriving ranges.

Derive Ranges Using Block Initial Conditions

How range analysis takes into account block initial conditions.

Derive Ranges for Simulink.Parameter Objects

How 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

Maintain integer data types in your model when using data type override.

Resolve Range Analysis Issues

Troubleshoot range analysis issues.

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

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.

Featured Examples