WOLFRAM SYSTEMMODELER
LimPIDP, PI, PD, and PID controller with limited output, antiwindup compensation, setpoint weighting and optional feedforward 
SystemModel["Modelica.Blocks.Continuous.LimPID"]
This information is part of the Modelica Standard Library maintained by the Modelica Association.
Via parameter controllerType either P, PI, PD, or PID can be selected. If, e.g., PI is selected, all components belonging to the Dpart are removed from the block (via conditional declarations). The example model Modelica.Blocks.Examples.PID_Controller demonstrates the usage of this controller. Several practical aspects of PID controller design are incorporated according to chapter 3 of the book:
Besides the additive proportional, integral and derivative part of this controller, the following features are present:
The parameters of the controller can be manually adjusted by performing simulations of the closed loop system (= controller + plant connected together) and using the following strategy:
Initialization
This block can be initialized in different ways controlled by parameter initType. The possible values of initType are defined in Modelica.Blocks.Types.InitPID. This type is identical to Types.Init, with the only exception that the additional option DoNotUse_InitialIntegratorState is added for backward compatibility reasons (= integrator is initialized with InitialState whereas differential part is initialized with NoInit which was the initialization in version 2.2 of the Modelica standard library).
Based on the setting of initType, the integrator (I) and derivative (D) blocks inside the PID controller are initialized according to the following table:
initType  I.initType  D.initType 
NoInit  NoInit  NoInit 
SteadyState  SteadyState  SteadyState 
InitialState  InitialState  InitialState 
InitialOutput and initial equation: y = y_start 
NoInit  SteadyState 
DoNotUse_InitialIntegratorState  InitialState  NoInit 
In many cases, the most useful initial condition is SteadyState because initial transients are then no longer present. If initType = InitPID.SteadyState, then in some cases difficulties might occur. The reason is the equation of the integrator:
der(y) = k*u;
The steady state equation "der(x)=0" leads to the condition that the input u to the integrator is zero. If the input u is already (directly or indirectly) defined by another initial condition, then the initialization problem is singular (has none or infinitely many solutions). This situation occurs often for mechanical systems, where, e.g., u = desiredSpeed  measuredSpeed and since speed is both a state and a derivative, it is natural to initialize it with zero. As sketched this is, however, not possible. The solution is to not initialize u_m or the variable that is used to compute u_m by an algebraic equation.
When initializing in steadystate, homotopybased initialization can help the convergence of the solver, by using a simplified model a the beginning of the solution process. Different options are available.
The parameter limitAtInit is obsolete since MSL 3.2.2 and only kept for backwards compatibility.
controllerType 
Value: .Modelica.Blocks.Types.SimpleController.PID Type: SimpleController Description: Type of controller 

k 
Value: 1 Type: Real Description: Gain of controller 
Ti 
Value: 0.5 Type: Time (s) Description: Time constant of Integrator block 
Td 
Value: 0.1 Type: Time (s) Description: Time constant of Derivative block 
yMax 
Value: Type: Real Description: Upper limit of output 
yMin 
Value: yMax Type: Real Description: Lower limit of output 
wp 
Value: 1 Type: Real Description: Setpoint weight for Proportional block (0..1) 
wd 
Value: 0 Type: Real Description: Setpoint weight for Derivative block (0..1) 
Ni 
Value: 0.9 Type: Real Description: Ni*Ti is time constant of antiwindup compensation 
Nd 
Value: 10 Type: Real Description: The higher Nd, the more ideal the derivative block 
withFeedForward 
Value: false Type: Boolean Description: Use feedforward input? 
kFF 
Value: 1 Type: Real Description: Gain of feedforward input 
initType 
Value: .Modelica.Blocks.Types.InitPID.DoNotUse_InitialIntegratorState Type: InitPID Description: Type of initialization (1: no init, 2: steady state, 3: initial state, 4: initial output) 
xi_start 
Value: 0 Type: Real Description: Initial or guess value for integrator output (= integrator state) 
xd_start 
Value: 0 Type: Real Description: Initial or guess value for state of derivative block 
y_start 
Value: 0 Type: Real Description: Initial value of output 
homotopyType 
Value: Modelica.Blocks.Types.LimiterHomotopy.Linear Type: LimiterHomotopy Description: Simplified model for homotopybased initialization 
strict 
Value: false Type: Boolean Description: = true, if strict limits with noEvent(..) 
limitsAtInit 
Value: true Type: Boolean Description: Has no longer an effect and is only kept for backwards compatibility (the implementation uses now the homotopy operator) 
controlError 
Default Value: u_s  u_m Type: Real Description: Control error (set point  measurement) 

u_s 
Type: RealInput Description: Connector of setpoint input signal 


u_m 
Type: RealInput Description: Connector of measurement input signal 

y 
Type: RealOutput Description: Connector of actuator output signal 

u_ff 
Type: RealInput Description: Optional connector of feedforward input signal 
Modelica.Blocks.Examples Demonstrates the usage of a Continuous.LimPID controller 

Modelica.Electrical.Machines.Examples.SynchronousInductionMachines Test example: ElectricalExcitedSynchronousInductionMachine with voltage controller 

Modelica.Electrical.Machines.Examples.SynchronousInductionMachines Test example: ElectricalExcitedSynchronousInductionMachine with rectifier 

Modelica.Electrical.Machines.Examples.DCMachines Test example: DC with permanent magnet starting with current controller 

Modelica.Magnetic.FundamentalWave.Examples.BasicMachines Test example: ElectricalExcitedSynchronousInductionMachine with voltage controller 

Modelica.Magnetic.FundamentalWave.Examples.BasicMachines Test example: ElectricalExcitedSynchronousInductionMachine with rectifier 