Documentation Center 
Simulate continuous or discretetime twodegreeoffreedom PID controllers
Implement a continuous or discretetime twodegreeoffreedom controller (PID, PI, or PD) in your Simulink^{®} model. The PID Controller (2DOF) block allows you to implement setpoint weighting in your controller to achieve both smooth setpoint tracking and good disturbance rejection.
The PID Controller (2DOF) block generates an output signal based on the difference between a reference signal and a measured system output. The block computes a weighted difference signal for each of the proportional, integral, and derivative actions according to the setpoint weights you specify. The block output is the sum of the proportional, integral, and derivative actions on the respective difference signals, where each action is weighted according to the gain parameters. A firstorder pole filters the derivative action. Controller gains are tunable either manually or automatically. Automatic tuning requires Simulink Control Design™ software (PID Tuner or SISO Design Tool).
Configurable options in the PID Controller (2DOF) block include:
Controller type (PID, PI, or PD)
Controller form (Parallel or Ideal)
Time domain (continuous or discrete)
Initial conditions and reset trigger
Output saturation limits and builtin antiwindup mechanism
Signal tracking for bumpless control transfer and multiloop control
In one common implementation, the PID Controller (2DOF) block operates in the feedforward path of the feedback loop. The block receives a reference signal at the Ref input and a measured system output at the other input. For example:
For a singleinput block that accepts an error signal (a difference between a setpoint and a system output), see the PID Controller block reference page.
You can generate code to implement your controller using any Simulink data type, including fixedpoint data types. (Code generation requires Simulink Coder™ software; fixedpoint implementation requires the FixedPoint Designer™ product.)
For an example illustrating an application of the PID Controller (2 DOF) block, see the Simulink example Two DegreeofFreedom PID Control for Setpoint TrackingTwo DegreeofFreedom PID Control for Setpoint Tracking.
The PID Controller (2DOF) block accepts real signals of any numeric data type that Simulink software supports, including fixedpoint data types. See Data Types Supported by Simulink in the Simulink documentation for more information.
The following table summarizes the PID Controller (2DOF)block parameters, accessible via the block parameter dialog box.
Task  Parameters 

Choose controller form and type. 

Choose discrete or continuous time.  
Choose an integration method (discrete time).  
Set and tune controller gains. 

Set integrator and filter initial conditions. 

Limit block output. 

Configure antiwindup mechanism (when you limit block output). 

Enable signal tracking. 

Configure data types. 

Configure block for code generation. 

Select the controller form.
Selects a controller form in which the proportional, integral, and derivative gains P, I, and D operate independently. The filter coefficient N sets the location of the pole in the derivative filter.
Parallel twodegreeoffreedom PID controller, where input 1 receives a reference signal and input 2 receives feedback from the measured system output:
The parallel twodegreeoffreedom PID controller can be equivalently modeled by the following block diagram:
R(s) represents the reference signal and Y(s) represents the feedback from measured system output. In this model, C(s) is a single degreeoffreedom controller, and F(s) acts as a prefilter on the reference signal. For a parallel twodegreeoffreedom PID controller in the Continuoustime Timedomain, the transfer functions F(s) and C(s) are:
where b and c are the Setpoint weight parameters.
Alternatively, the parallel twodegreeoffreedom PID controller can be modeled by the following block diagram:
R(s), Y(s), and C(s) are as discussed previously. In this realization, Q(s) acts as feedforward conditioning on the reference signal R(s). For a parallel PID controller in the Continuoustime Timedomain, the transfer function Q(s) is:
Selects a controller form in which the proportional gain P acts on the sum of all actions.
Ideal twodegreeoffreedom PID controller, where input 1 receives a reference signal and input 2 receives feedback from the measured system output:
Similarly to the parallel controller form discussed previously, the ideal twodegreeoffreedom PID controller can be modeled as a single degreeoffreedom controller C(s) with a prefilter F(s). For an ideal twodegreeoffreedom PID controller in the Continuoustime Timedomain, the transfer functions F(s) and C(s) are:
where b and c are the Setpoint weight parameters.
Alternatively, modeling the ideal twodegreeoffreedom PID controller as a onedegreeoffreedom controller C(s) with feedforward conditioning Q(s) on the reference signal gives, in continuoustime:
The controller transfer function for the current settings is displayed in the block dialog box.
Specify the controller type.
Implements a controller with proportional, integral, and derivative action.
Implements a controller with proportional and integral action.
Implements a controller with proportional and derivative action.
The controller transfer function for the current settings is displayed in the block dialog box.
Select continuous or discrete time domain. The appearance of the block changes to reflect your selection.
Selects the continuoustime representation.
Selects the discretetime representation. Selecting Discretetime also allows you to specify the:
Sample time, which is the discrete interval between samples.
Discrete integration methods for the integrator and the derivative filter using the Integrator method and Filter method menus.
(Available only when you set Timedomain to Discretetime.) Specify the method used to compute the integrator output. For more information about discretetime integration methods, see the DiscreteTime Integrator block reference page.
Selects the Forward Rectangular (lefthand) approximation.
This method is best for small sampling times, where the Nyquist limit is large compared to the bandwidth of the controller. For larger sampling times, the Forward Euler method can result in instability, even when discretizing a system that is stable in continuous time.
Selects the Backward Rectangular (righthand) approximation.
If you are generating code using Simulink Coder software or the FixedPoint Designer product and you activate the Backcalculation Antiwindup method, this integration method can cause algebraic loops in your controller. Algebraic loops can lead to slower performance of generated code. For more information about algebraic loops in Simulink models, see Algebraic Loops in the Simulink documentation.
An advantage of the Backward Euler method is that discretizing a stable continuoustime system using this method always yields a stable discretetime result.
Selects the Bilinear approximation.
If you are generating code using Simulink Coder software or the FixedPoint Designer product and you activate the Backcalculation Antiwindup method, this integration method can cause algebraic loops in your controller. Algebraic loops can lead to slower performance of generated code. For more information about algebraic loops in Simulink models, see Algebraic Loops in the Simulink documentation.
An advantage of the Trapezoidal method is that discretizing a stable continuoustime system using this method always yields a stable discretetime result. Of all available integration methods, the Trapezoidal method yields the closest match between frequencydomain properties of the discretized system and the corresponding continuoustime system.
(Available only when you set Timedomain to Discretetime.) Specify the method used to compute the derivative filter output. For more information about discretetime integration methods, see the DiscreteTime Integrator block reference page.
Selects the Forward Rectangular (lefthand) approximation.
This method is best for small sampling times, where the Nyquist limit is large compared to the bandwidth of the controller. For larger sampling times, the Forward Euler method can result in instability, even when discretizing a system that is stable in continuous time.
Selects the Backward Rectangular (righthand) approximation.
If you are generating code using Simulink Coder software or the FixedPoint Designer product, this filter method can cause algebraic loops in your controller. Algebraic loops can lead to slower performance of generated code. For more information about algebraic loops in Simulink models, see Algebraic Loops in the Simulink documentation.
An advantage of the Backward Euler method is that discretizing a stable continuoustime system using this method always yields a stable discretetime result. Any filter parameter value N > 0 yields a stable result with this method.
Selects the Bilinear approximation.
If you are generating code using Simulink Coder software or the FixedPoint Designer product, this filter method can cause algebraic loops in your controller. Algebraic loops can lead to slower performance of generated code. For more information about algebraic loops in Simulink models, see Algebraic Loops in the Simulink documentation.
An advantage of the Trapezoidal method is that discretizing a stable continuoustime system using this method always yields a stable discretetime result. Any filter parameter value N > 0 yields a stable result with this method. Of all available filter methods, the Trapezoidal method yields the closest match between frequencydomain properties of the discretized system and the corresponding continuoustime system.
(Available only when you set Timedomain to Discretetime.) Specify the discrete interval between samples.
Default: 1
By default, the block uses a discrete sample time of 1. To specify a different sample time, enter another discrete value, such as 0.1.
If you specify a value of –1, the PID Controller (2DOF) block inherits the sample time from upstream blocks. Do not enter a value of 0; to implement a continuoustime controller, select the Timedomain Continuoustime.
See Specify Sample Time in the online documentation for more information.
Specify the proportional gain P.
Default: 1
Enter a finite, real gain value into the Proportional (P) field. Use either scalar or vector gain values. For a parallel PID Controller form, the proportional action is independent of the integral and derivative actions. For an ideal PID Controller form, the proportional action acts on the integral and derivative actions. See Controller form for more information about the role of P in the controller transfer function.
When you have Simulink Control Design software installed, you can automatically tune the controller gains using the PID Tuner or the SISO Design Tool. See Choosing a Compensator Design Approach.
(Available for PID and PI controllers.) Specify the integral gain I.
Default: 1
Enter a finite, real gain value into the Integral (I) field. Use either scalar or vector gain values.
When you have Simulink Control Design software installed, you can automatically tune the controller gains using the PID Tuner or the SISO Design Tool. See Choosing a Compensator Design Approach.
(Available for PID and PD controllers.) Specify the derivative gain D.
Default: 0
Enter a finite, real gain value into the Derivative (D) field. Use either scalar or vector gain values.
When you have Simulink Control Design software installed, you can automatically tune the controller gains using the PID Tuner or the SISO Design Tool. See Choosing a Compensator Design Approach.
Specifies the filter coefficient of the controller.
(Available for PID and PD controllers.) Specify the filter coefficient N, which determines the pole location of the filter in the derivative action:
The filter pole falls at s = N in the Continuoustime Timedomain. For Discretetime, the location of the pole depends on which Filter method you select (for sampling time T_{s}):
Forward Euler:
Backward Euler:
Trapezoidal:
Default: 100.
Enter a finite, real gain value into the Filter Coefficient (N) field. Use either scalar or vector gain values. Note that the PID controller (2DOF) block does not support N = inf (ideal unfiltered derivative).
When you have Simulink Control Design software installed, you can automatically tune the controller gains using the PID Tuner or the SISO Design Tool. See Choosing a Compensator Design Approach. Automatic tuning requires N > 0.
Specify the proportional setpoint weight b.
Default: 1
Enter the proportional setpoint weight value into the Setpoint weight (b) field. Setting b = 0 eliminates the proportional action on the reference signal, which can reduce overshoot in the system response to step changes in the setpoint.
The following diagrams show the role of Setpoint weight (b) in Parallel and Ideal PID controllers. See Controller form for a discussion of the corresponding transfer functions.
Parallel TwoDegreeofFreedom PID Controller
Ideal TwoDegreeofFreedom PID Controller
(Available for PID and PD controllers.) Specify the derivative setpoint weight c.
Enter the derivative setpoint weight value into the Setpoint weight (c) field. To implement a controller that achieves both effective disturbance rejection and smooth setpoint tracking without excessive transient response, set c = 0. Setting c = 0 yields a controller with derivative action on the measured system response but not on the reference input.
The following diagrams show the role of Setpoint weight (c) in Parallel and Ideal PID controllers. See Controller form for a discussion of the corresponding transfer functions.
Parallel TwoDegreeofFreedom PID Controller
Ideal TwoDegreeofFreedom PID Controller
Select the source of the integrator and filter initial conditions. Simulink uses initial conditions to initialize the integrator and filter output at the start of a simulation or at a specified trigger event (see External reset). The integrator and filter initial conditions in turn determine the initial block output.
Specifies the integrator and filter initial conditions explicitly using the Integrator Initial condition and Filter Initial condition parameters.
Specifies the integrator and filter initial conditions externally. An additional input port appears under the block inputs for each initial condition: I_{0} for the integrator and D_{0} for the filter:
(Available only when Initial conditions Source is internal and the controller includes integral action.) Specify the integrator initial value. Simulink uses the initial condition to initialize the integrator output at the start of a simulation or at a specified trigger event (see External reset). The integrator initial condition, together with the filter initial condition, determines the initial output of the PID Controller (2DOF) block.
Default: 0
Simulink does not permit the integrator initial condition to be inf or NaN.
(Available only when Initial conditions Source is internal and the controller includes integral action.) Specify the filter initial value. Simulink uses the initial condition to initialize the filter output at the start of a simulation or at a specified trigger event (see External reset). The filter initial condition, together with the integrator initial condition, determines the initial output of the PID Controller (2DOF) block.
Default: 0
Simulink does not permit the filter initial condition to be inf or NaN.
Select the trigger event that resets the integrator and filter outputs to the initial conditions you specify in the Integrator Initial condition and Filter Initial condition fields. Selecting any option other than none enables a reset input on the block for the external reset signal, as shown:
Or, if the Initial conditions Source is External:
The reset signal must be a scalar of type single, double, boolean, or integer. Fixed point data types, except for ufix1, are not supported.
Note: To be compliant with the Motor Industry Software Reliability Association (MISRA^{®}) software standard, your model must use Boolean signals to drive the external reset ports of the PID controller (2DOF) block. 
Does not reset the integrator and filter outputs to initial conditions.
Resets the outputs when the reset signal has a rising edge.
Resets the outputs when the reset signal has a falling edge.
Resets the outputs when the reset signal either rises or falls.
Resets and holds the outputs to the initial conditions while the reset signal is nonzero.
Force Simulink linearization commands to ignore any reset mechanism that you have chosen with the External reset menu. Ignoring reset states allows you to linearize a model around an operating point even if that operating point causes the PID Controller (2DOF) block to reset.
Simulink linearization commands do not ignore states corresponding to the reset mechanism.
Simulink linearization commands ignore states corresponding to the reset mechanism.
Enable zerocrossing detection in continuoustime models upon reset and upon entering or leaving a saturation state.
Zerocrossing detection can accurately locate signal discontinuities without resorting to excessively small time steps that can lead to lengthy simulation times. If you select Limit output or activate an External reset in your PID Controller (2DOF) block, activating zerocrossing detection can reduce computation time in your simulation. For more information, see ZeroCrossing Detection.
Uses zerocrossing detection at any of the following events: reset; entering or leaving an upper saturation state; and entering or leaving a lower saturation state.
Does not use zerocrossing detection.
Enabling zerocrossing detection for the PID Controller (2DOF) block also enables zerocrossing detection for all undermask blocks that include the zerocrossing detection feature.
Limit the block output to values you specify as the Lower saturation limit and Upper saturation limit parameters.
Activating this option limits the block output internally to the block, obviating the need for a separate Saturation block after the controller in your Simulink model. It also allows you to activate the builtin antiwindup mechanism (see Antiwindup method).
Does not limit the block output, which is the weighted sum of the proportional, integral, and derivative actions.
Limits the block output to the Lower saturation limit or the Upper saturation limit whenever the weighted sum exceeds those limits. Allows you to select an Antiwindup method.
(Available only when you select the Limit Output box.) Specify the lower limit for the block output. The block output is held at the Lower saturation limit whenever the weighted sum of the proportional, integral, and derivative actions goes below that value.
Default: inf
(Available only when you select the Limit Output box.) Specify the upper limit for the block output. The block output is held at the Upper saturation limit whenever the weighted sum of the proportional, integral, and derivative actions exceeds that value.
Default: inf
(Available only when you select the Limit Output option and the controller includes integral action.) Select an antiwindup mechanism to discharge the integrator when the block is saturated, which occurs when the sum of the block components exceeds the output limits.
When you select the Limit output check box and the weighted sum of the controller components exceeds the specified output limits, the block output holds at the specified limit. However, the integrator output can continue to grow (integrator windup), increasing the difference between the block output and the sum of the block components. Without a mechanism to prevent integrator windup, two results are possible:
If the sign of the input signal never changes, the integrator continues to integrate until it overflows. The overflow value is the maximum or minimum value for the data type of the integrator output.
If the sign of the input signal changes once the weighted sum has grown beyond the output limits, it can take a long time to discharge the integrator and return the weighted sum within the block saturation limit.
In both cases, controller performance can suffer. To combat the effects of windup without an antiwindup mechanism, it may be necessary to detune the controller (for example, by reducing the controller gains), resulting in a sluggish controller. Activating an antiwindup mechanism can improve controller performance.
Does not use an antiwindup mechanism. This setting can cause the block's internal signals to be unbounded even if the output appears to be bounded by the saturation limits. This can result in slow recovery from saturation or unexpected overflows.
Discharges the integrator when the block output saturates using the integralgain feedback loop:
You can also specify a value for the Backcalculation coefficient (Kb).
Stops integration when the sum of the block components exceeds the output limits and the integrator output and block input have the same sign. Resumes integration when the sum of the block components exceeds the output limits and the integrator output and block input have opposite sign. The integrator portion of the block is:
The clamping circuit implements the logic necessary to determine whether integration continues.
(Available only when the backcalculation Antiwindup method is active.) Specify the gain coefficient of the antiwindup feedback loop.
The backcalculation antiwindup method discharges the integrator on block saturation using a feedback loop having gain coefficient Kb.
Default: 1
Force Simulink linearization commands ignore PID Controller (2DOF) block output limits. Ignoring output limits allows you to linearize a model around an operating point even if that operating point causes the PID Controller (2DOF) block to exceed the output limits.
Simulink linearization commands ignore states corresponding to saturation.
Simulink linearization commands do not ignore states corresponding to saturation.
(Available for any controller with integral action.) Activate signal tracking, which lets the output of the PID Controller (2DOF) block follow a tracking signal. Provide the tracking signal to the block at the TR port, which becomes active when you select Enable tracking mode.
When signal tracking is active, the difference between the tracked signal and the block output is fed back to the integrator input with a gain Kt. You can also specify the value of the Tracking coefficient (Kt).
For information about using tracking mode to implement bumpless control transfer scenarios and multiloop controllers, see Enable tracking mode in the PID Controller reference page.
Disables signal tracking and removes TR block input.
Enables signal tracking and activates TR input.
(Available only when you select Enable tracking mode.) Specify Kt, which is the gain of the signal tracking feedback loop.
Default: 1
Select the data type of the gain parameters P, I, D, N, Kb, and Kt and the setpoint weighting parameters b and c.
See Data Types Supported by Simulink in the Simulink documentation for more information.
Simulink chooses a data type to balance numerical accuracy, performance, and generated code size, while taking into account the properties of the embedded target hardware. If you change the embedded target settings, the data type selected by the internal rule might change. It is not always possible for the software to optimize code efficiency and numerical accuracy at the same time. If the internal rule doesn't meet your specific needs for numerical accuracy or performance, use one of the following options:
Specify the output data type explicitly.
Use the simple choice of Inherit: Same as input.
Explicitly specify a default data type such as fixdt(1,32,16) and then use the FixedPoint Tool to propose data types for your model. For more information, see fxptdlg.
To specify your own inheritance rule, use Inherit: Inherit via back propagation and then use a Data Type Propagation block. Examples of how to use this block are available in the Signal Attributes library Data Type Propagation Examples block.
Use data type of the driving block.
Use data type of input signal.
Name of a data type object. For example, Simulink.NumericType.
Select the product output data type of the gain parameters P, I, D, N, Kb, and Kt and the setpoint weighting parameters b and c .
See Data Types Supported by Simulink in the Simulink documentation for more information.
Simulink chooses a data type to balance numerical accuracy, performance, and generated code size, while taking into account the properties of the embedded target hardware. If you change the embedded target settings, the data type selected by the internal rule might change. It is not always possible for the software to optimize code efficiency and numerical accuracy at the same time. If the internal rule doesn't meet your specific needs for numerical accuracy or performance, use one of the following options:
Specify the output data type explicitly.
Use the simple choice of Inherit: Same as input.
Explicitly specify a default data type such as fixdt(1,32,16) and then use the FixedPoint Tool to propose data types for your model. For more information, see fxptdlg.
To specify your own inheritance rule, use Inherit: Inherit via back propagation and then use a Data Type Propagation block. Examples of how to use this block are available in the Signal Attributes library Data Type Propagation Examples block.
Use data type of the driving block.
Use data type of input signal.
Name of a data type object. For example, Simulink.NumericType.
Select the summation output data type of the sums Sum, Sum1, Sum2, Sum3, Sum D, Sum I1 , SumI2 ,and SumI3, which are sums computed internally within the block. To see where Simulink computes each of these sums , rightclick the PID Controller (2DOF) block in your model and select Look Under Mask:
Sum is the weighted sum of the proportional, derivative, and integral signals.
Sum1 is the difference between the reference input weighted by b and the measured system response.
Sum2 is the difference between the reference input weighted by c and the measured system response.
Sum3 is the difference between the unweighted reference input and the measured system response.
SumD is the sum in the derivative filter feedback loop.
SumI1 is the sum of the block input signal (weighted by the integral gain I) and SumI2. SumI1 is computed only when Limit output and Antiwindup method backcalculation are active.
SumI2 is the difference between the weighted sum Sum and the limited block output. SumI2 is computed only when Limit output and Antiwindup method backcalculation are active.
SumI3 is the difference between the block output and the signal at the block's tracking input. SumI3 is computed only when you select the Enable tracking mode box.
See Data Types Supported by Simulink in the Simulink documentation for more information.
Simulink chooses a data type to balance numerical accuracy, performance, and generated code size, while taking into account the properties of the embedded target hardware. If you change the embedded target settings, the data type selected by the internal rule might change. It is not always possible for the software to optimize code efficiency and numerical accuracy at the same time. If the internal rule doesn't meet your specific needs for numerical accuracy or performance, use one of the following options:
Specify the output data type explicitly.
Use the simple choice of Inherit: Same as first input.
Explicitly specify a default data type such as fixdt(1,32,16) and then use the FixedPoint Tool to propose data types for your model. For more information, see fxptdlg.
Use data type of the driving block.
Use data type of first input signal.
Use the same data type as the corresponding accumulator.
Name of a data type object. For example, Simulink.NumericType.
Specify the accumulator data type.
Default: Inherit: Inherit via internal rule
Use internal rule to determine accumulator data type.
Use data type of first input signal.
Accumulator data type is double.
Accumulator data type is single.
Accumulator data type is int8.
Accumulator data type is uint8.
Accumulator data type is int16.
Accumulator data type is uint16.
Accumulator data type is int32.
Accumulator data type is uint32.
Accumulator data type is fixed point fixdt(1,16,0).
Accumulator data type is fixed point fixdt(1,16,2^0,0).
The name of a data type object, for example Simulink.NumericType
See BlockSpecific Parameters for the commandline information.
For more information, see Specify Data Types Using Data Type Assistant.
Select the data type of the integrator output.
See Data Types Supported by Simulink in the Simulink documentation for more information.
Simulink chooses a data type to balance numerical accuracy, performance, and generated code size, while taking into account the properties of the embedded target hardware. If you change the embedded target settings, the data type selected by the internal rule might change. It is not always possible for the software to optimize code efficiency and numerical accuracy at the same time. If the internal rule doesn't meet your specific needs for numerical accuracy or performance, use one of the following options:
Specify the output data type explicitly.
Use Inherit: Inherit via back propagation.
Explicitly specify a default data type such as fixdt(1,32,16) and then use the FixedPoint Tool to propose data types for your model. For more information, see fxptdlg.
Use data type of the driving block.
Name of a data type object. For example, Simulink.NumericType.
Select the data type of the filter output.
See Data Types Supported by Simulink in the Simulink documentation for more information.
Simulink chooses a data type to balance numerical accuracy, performance, and generated code size, while taking into account the properties of the embedded target hardware. If you change the embedded target settings, the data type selected by the internal rule might change. It is not always possible for the software to optimize code efficiency and numerical accuracy at the same time. If the internal rule doesn't meet your specific needs for numerical accuracy or performance, use one of the following options:
Specify the output data type explicitly.
Use Inherit: Inherit via back propagation.
Explicitly specify a default data type such as fixdt(1,32,16) and then use the FixedPoint Tool to propose data types for your model. For more information, see fxptdlg.
Use data type of the driving block.
Name of a data type object. For example, Simulink.NumericType.
Select the saturation output data type.
See Data Types Supported by Simulink in the Simulink documentation for more information.
Use data type of input signal.
Use data type of the driving block.
Name of a data type object. For example, Simulink.NumericType.
Select the category of data to specify.
Default: Inherit
Inheritance rules for data types. Selecting Inherit enables a second menu/text box to the right. Select one of the following choices:
Inherit via internal rule (default)
Inherit via back propagation
Same as first input
Same as accumulator
Builtin data types. Selecting Built in enables a second menu/text box to the right. Select one of the following choices:
double (default)
single
int8
uint8
int16
uint16
int32
uint32
Fixedpoint data types.
Expressions that evaluate to data types. Selecting Expression enables a second menu/text box to the right, where you can enter the expression.
Clicking the Show data type assistant button enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specify Data Types Using Data Type Assistant.
Select the category of data to specify.
Default: Inherit
Inheritance rules for data types. Selecting Inherit enables a second menu/text box to the right. Select one of the following choices:
Inherit via back propagation
Same as input (default)
Builtin data types. Selecting Built in enables a second menu/text box to the right. Select one of the following choices:
double (default)
single
int8
uint8
int16
uint16
int32
uint32
Fixedpoint data types.
Expressions that evaluate to data types. Selecting Expression enables a second menu/text box to the right, where you can enter the expression.
Clicking the Show data type assistant button enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specify Data Types Using Data Type Assistant.
Select the category of accumulator data to specify
Default: Inherit
Specifies inheritance rules for data types. Selecting Inherit enables a list of possible values:
Inherit via internal rule (default)
Same as first input
Specifies builtin data types. Selecting Built in enables a list of possible values:
double (default)
single
int8
uint8
int16
uint16
int32
uint32
Specifies fixedpoint data types.
Specifies expressions that evaluate to data types. Selecting Expression enables you to enter an expression.
Clicking the Show data type assistant button for the accumulator data type enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specify Data Types Using Data Type Assistant.
Specify data type override mode for this signal.
Default: Inherit
Inherits the data type override setting from its context, that is, from the block, Simulink.Signal object or Stateflow^{®} chart in Simulink that is using the signal.
Ignores the data type override setting of its context and uses the fixedpoint data type specified for the signal.
The ability to turn off data type override for an individual data type provides greater control over the data types in your model when you apply data type override. For example, you can use this option to ensure that data types meet the requirements of downstream blocks regardless of the data type override setting.
This parameter appears only when the Mode is Built in or Fixed point.
Specify whether you want the fixedpoint data as signed or unsigned.
Default: Signed
Selecting Mode > Fixed point enables this parameter.
For more information, see Specifying a FixedPoint Data Type.
Specify whether you want the fixedpoint data to be signed or unsigned.
Default: Signed
Specify the fixedpoint data to be signed.
Specify the fixedpoint data to be unsigned.
Selecting Mode > Fixed point for the accumulator data type enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specifying a FixedPoint Data Type for more information.
Specify the method for scaling your fixedpoint data to avoid overflow conditions and minimize quantization errors.
Default: Best precision, Binary point, Integer
Specify binary point location.
Enter slope and bias.
Specify bestprecision values. This option appears for some blocks.
Specify integer. This setting has the same result as specifying a binary point location and setting fraction length to 0. This option appears for some blocks.
Selecting Mode > Fixed point enables this parameter.
Selecting Binary point enables:
Fraction length
Calculate BestPrecision Scaling
Selecting Slope and bias enables:
Slope
Bias
Calculate BestPrecision Scaling
See BlockSpecific Parameters for the commandline information.
For more information, see Specifying a FixedPoint Data Type.
Specify the method for scaling your fixedpoint data to avoid overflow conditions and minimize quantization errors.
Default: Binary point
Selecting Mode > Fixed point for the accumulator data type enables this parameter.
Selecting Binary point enables:
Fraction length
Selecting Slope and bias enables:
Slope
Bias
See BlockSpecific Parameters for the commandline information.
See Specifying a FixedPoint Data Type for more information.
Specify the bit size of the word that holds the quantized integer.
Default: 16
Minimum: 0
Maximum: 32
Selecting Mode > Fixed point enables this parameter.
For more information, see Specifying a FixedPoint Data Type.
Specify the bit size of the word that will hold the quantized integer.
Default: 16
Minimum: 0
Maximum: 32
Large word sizes represent large values with greater precision than small word sizes.
Selecting Mode > Fixed point for the accumulator data type enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specifying a FixedPoint Data Type for more information.
Specify fraction length for fixedpoint data type.
Default: 0
Binary points can be positive or negative integers.
Selecting Scaling > Binary point enables this parameter.
For more information, see Specifying a FixedPoint Data Type.
Specify fraction length for fixedpoint data type.
Default: 0
Binary points can be positive or negative integers.
Selecting Scaling > Binary point for the accumulator data type enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specifying a FixedPoint Data Type for more information.
Specify slope for the fixedpoint data type.
Default: 2^0
Specify any positive real number.
Selecting Scaling > Slope and bias enables this parameter.
For more information, see Specifying a FixedPoint Data Type.
Specify slope for the fixedpoint data type.
Default: 2^0
Specify any positive real number.
Selecting Scaling > Slope and bias for the accumulator data type enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specifying a FixedPoint Data Type for more information.
Specify bias for the fixedpoint data type.
Default: 0
Specify any real number.
Selecting Scaling > Slope and bias enables this parameter.
For more information, see Specifying a FixedPoint Data Type.
Specify bias for the fixedpoint data type.
Default: 0
Specify any real number.
Selecting Scaling > Slope and bias for the accumulator data type enables this parameter.
See BlockSpecific Parameters for the commandline information.
See Specifying a FixedPoint Data Type for more information.
Select to lock the output data type setting of this block against changes by the FixedPoint Tool and the FixedPoint Advisor.
Default: Off
Locks the output data type setting for this block.
Allows the FixedPoint Tool and the FixedPoint Advisor to change the output data type setting for this block.
Parameter: LockScale 
Type: string 
Value: 'off'  'on' 
Default: 'off' 
For more information, see Use Lock Output Data Type Setting.
Specify whether overflows saturate.
Default: Off
Overflows saturate to either the minimum or maximum value that the data type can represent.
For example, an overflow associated with a signed 8bit integer can saturate to 128 or 127.
Overflows wrap to the appropriate value that is representable by the data type.
For example, the number 130 does not fit in a signed 8bit integer and wraps to 126.
Consider selecting this check box when your model has possible overflow and you want explicit saturation protection in the generated code.
Consider clearing this check box when you want to optimize efficiency of your generated code.
Clearing this check box also helps you avoid overspecifying how a block handles outofrange signals. For more information, see Checking for Signal Range Errors.
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.
Parameter: SaturateOnIntegerOverflow 
Type: string 
Value: 'off'  'on' 
Default: 'off' 
Specify the rounding mode for fixedpoint operations.
Default: Floor
Rounds both positive and negative numbers toward positive infinity. Equivalent to the MATLAB^{®} ceil function.
Rounds number to the nearest representable value. If a tie occurs, rounds to the nearest even integer. Equivalent to the FixedPoint Designer convergent function.
Rounds both positive and negative numbers toward negative infinity. Equivalent to the MATLAB floor function.
Rounds number to the nearest representable value. If a tie occurs, rounds toward positive infinity. Equivalent to the FixedPoint Designer nearest function.
Rounds number to the nearest representable value. If a tie occurs, rounds positive numbers toward positive infinity and rounds negative numbers toward negative infinity. Equivalent to the FixedPoint Designer round function.
Automatically chooses between round toward floor and round toward zero to generate rounding code that is as efficient as possible.
Rounds number toward zero. Equivalent to the MATLAB fix function.
Parameter: RndMeth 
Type: string 
Value: 'Ceiling'  'Convergent'  'Floor'  'Nearest'  'Round'  'Simplest'  'Zero' 
Default: 'Floor' 
For more information, see Rounding in the FixedPoint Designer documentation.
Assign unique name to each state. The state names apply only to the selected block.
To assign a name to a single state, enter the name between quotes; for example, 'velocity'.
To assign names to multiple states, enter a commadelimited list surrounded by braces; for example, {'a', 'b', 'c'}. Each name must be unique. To assign state names with a variable that has been defined in the MATLAB workspace, enter the variable without quotes. The variable can be a string, cell, or structure.
Default: ' ' (no name)
Require that state name resolve to Simulink signal object.
Default: Off
Require that state name resolve to Simulink signal object.
Do not require that state name resolve to Simulink signal object.
State name enables this parameter.
Selecting this check box disables Code generation storage class.
Parameter: StateMustResolveToSignalObject 
Type: string 
Value: 'off'  'on' 
Default: 'off' 
Select state storage class.
Default: Auto
Auto is the appropriate storage class for states that you do not need to interface to external code.
State is stored in a global variable
model_private.h declares the state as an extern variable.
model_private.h declares the state as an extern pointer.
State name enables this parameter.
Setting this parameter to ExportedGlobal, ImportedExtern, or ImportedExternPointer enables Code generation storage type qualifier.
CommandLine Information
Parameter: StateStorageClass 
Type: string 
Value: 'Auto'  'ExportedGlobal'  'ImportedExtern'  'ImportedExternPointer' 
Default: 'Auto' 
Specify the Simulink Coder storage type qualifier.
Default: ' '
If left blank, no qualifier is assigned.
Setting Code generation storage class to ExportedGlobal, ImportedExtern, or ImportedExternPointer enables this parameter.
Parameter: RTWStateStorageTypeQualifier 
Type: string 
Value: ' ' 
Default: ' ' 
Direct Feedthrough  The
following ports support direct feedthrough:

Sample Time  Specified in the Sample time parameter 
Scalar Expansion  Supported for gain parameters P, I, and D for filter coefficient N, and for setpoint weights b and c 
States  Inherited from driving block and parameters 
Dimensionalized  Yes 
ZeroCrossing Detection  Yes (in continuoustime domain) 