|
|
|
| R2012a Documentation → Simulink | |
Learn more about Simulink |
|
| Contents | Index |
Signal Attributes
The Data Type Conversion Inherited block forces dissimilar data types to be the same. The first input is used as the reference signal and the second input is converted to the reference type by inheriting the data type and scaling information. (See How to Rotate a Block in the Simulink documentation for a description of the port order for various block orientations.) Either input undergoes scalar expansion such that the output has the same width as the widest input.
Inheriting the data type and scaling provides these advantages:
It makes reusing existing models easier.
It allows you to create new fixed-point models with less effort since you can avoid the detail of specifying the associated parameters.
The Data Type Conversion Inherited block accepts signals of the following data types:
Floating point
Built-in integer
Fixed point
Boolean
Enumerated
For more information, see Data Types Supported by Simulink in the Simulink documentation.
Specify whether the Real World Value (RWV) or the Stored Integer (SI) of the input and output should be the same. Refer to Description in the Data Type Conversion block reference page for more information about these choices.
Specify the rounding mode for fixed-point operations. For more information, see Rounding in the Simulink Fixed Point User's Guide.
Select to have overflows saturate to the maximum or minimum value that the data type can represent. Otherwise, overflows wrap.
When you select this check box, saturation applies to every internal operation on the block, not just the output or result. In general, the code generation process can detect when overflow is not possible. In this case, the code generator does not produce saturation code.
Direct Feedthrough | Yes |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
