The control performance of the MPCPlus function block is modified in much the same way as the MPC and MPCPro blocks. The main difference between the three function blocks is that the MPCPlus block requires no controller generation.
The following table provides guidelines for tailoring the control performance of the MPCPlus block.
| Steps to achieve the desired level of control performance | Where | Comments |
|---|---|---|
|
Review and modify the process model. |
DeltaV PredictPro application. |
Refer to Tailoring MPC Control Performance. |
|
Adjust the Penalty on Moves settings. |
Tuning dialog in the MPC Operate Pro application. |
Refer to Tailoring MPC Control Performance for guidelines on setting the value. |
|
Adjust the Penalty on Error (POE) settings. |
Tuning dialog in the MPC Operate Pro application. |
The value of the dynamic POE that the block calculates for CVs with a Target optimization type is based mostly on the configured/tuned value of POE_MID. Therefore, when the optimization type is Target, a good starting point for all three POE values (POE_ABOVE, POE_MID, and POE_BELOW) is 1.0. Use the response trajectory filter for the CV or the POM values of manipulated variables to tune the control response for target CVs. In general, if it is necessary to tune the POE values, adjust all three POE values equally. It may be appropriate for the POE_MID value to be lower than POE_ABOVE and POE_BELOW, but keep in mind that the value of POE_MID dominates. For a constraint variable with an optimization type of None, a good starting point for POE_MID is 0.1 or lower, and 1.0 for POE_ABOVE and POE_BELOW. Refer to Tailoring MPC Control Performance for basic guidelines on setting the error penalty. |
|
Adjust the response trajectories: setpoint trajectory or setpoint filter. |
Detail display for controlled variables in the MPC Operate Pro application. |
Refer to Tailoring MPC Control Performance. |
|
Adjust the maximum MV move. |
Detail display for manipulated variables in the MPC Operate Pro application. |
Refer to Tailoring MPC Control Performance. |
|
Adjust the model error filter values ( model correction factor). |
The MOD_CORR_FACTOR[#] parameter, where # is the process output number. |
Refer to Tailoring MPC Control Performance. |
|
Adjust the target setpoint filter. |
The horizontal slider on the Tuning dialog in the MPC Operator Pro application. |
The single slider simultaneously adjusts the target setpoint filter for all process outputs in the range of 0.1 (Robustness) to 0.8 (Performance). The larger the value, the faster the optimizer's optimal setpoint value is applied to the working setpoint of controlled variables. |
|
Adjust the MV target weight. |
The OPT_MV_WT parameter. |
The parameter holds a value common to all manipulated variables. The default value of 1.0 results in the MV move plan being strongly influenced by the steady-state MV values determined by the optimizer. A value of 0.0 provides a light influence; a value of 0.1 provides a moderate influence. Control performance is subtly impacted by the value. A value of 0.0 provides slightly less integrated error when working setpoints of controlled variables remain at their setpoint (no constraints are being hit). A value of 1.0 provides slightly less integrated error when working setpoints tend to deviate from setpoint during a dynamic response (constraints are being hit). |
|
Adjust moves blocking and CV blocking |
The MV_BLOCKING and CV_BLOCKING parameters visible offline and online in Control Studio |
Normally, the default moves blocking and CV blocking
settings suffice. There are two reasons to change these settings:
|
|
Set the optimization type for process outputs. |
Tuning dialog in the MPC Operate Pro application. |
In the MPCPlus block, a CV with an economic objective (Max or Min) is given a lower preference by the optimizer than a CV with a target objective. If you want a Max or Min CV to have a higher preference than a Target CV, change the Target CV to a PSV CV by setting the optimization type to PSV. A PSV CV behaves the same as a Target CV with the exception that a PSV CV will relax its working setpoint if needed for an economic objective to be met when there are insufficient degrees of freedom. |
|
Set the Priority for process outputs. |
Tuning dialog in the MPC Operate Pro application. |
The optimizer uses the Priority value to differentiate preference when the solution is infeasible. If it becomes necessary for steady-state working setpoints to deviate from CV setpoints, the optimizer will relax variables in priority order, that is, start with the variables with the lowest priority (highest Priority value). Each process output has a priority setting because all have the potential to become constrained. The priority setting will not override the block's standard preference based on the optimization type, but will differentiate among outputs with the same optimization type. Gain ratios can have an influence on preference, so you may need to increase the spread between Priority values to achieve the desired result. |
|
Adjust Value per % for economic variables. |
Tuning dialog in the MPC Operate Pro application. |
The Value per % setting applies to economic variables and is used by the optimizer to essentially differentiate preference among economic variables. A higher value gives more weight to achieving the economic objective. The priority setting for an economic variable can have a supplemental influence when multiple economic objectives have already been achieved and there are insufficient degrees of freedom. |
|
Change the MPCPlus block's model gain |
An expression in a CALC or Action block or an Action in a phase Sequential Function Chart (SFC). |
For MODEL_GAIN[x][y] where:
The instruction in the following expression sets the gain multiplier of the transfer function for control/constraint variable 2, manipulated/disturbance variable 4 in the MPC-PLUS1 block of module MPCP-8CON to the value of the parameter named GAIN_C2_M4: '//MPCP-8CON/MPC-PLUS1/MODEL_GAIN[2][4].CV' := '^/GAIN_C2_M4.CV';If the transfer function gain is set to 0.6 in PredictPro and the MODEL_GAIN[2][4] is 0.25, the actual gain becomes 0.15. |