Main.OptionApmReqctrlmode History

Hide minor edits - Show changes to output

June 09, 2017, at 12:45 AM by -
Changed lines 5-6 from:
%width=50px%Attach:apm.png [[Main/DbsGlobal|Global Options]] | %width=30px%Attach:fv.png %width=30px%Attach:mv.png %width=30px%Attach:sv.png %width=30px%Attach:cv.png[[Main/DbsVariable|Local Options]]
Added lines 16-17:

See also [[Main/OptionCritical|CRITICAL]], [[Main/OptionApmCtrlmode|CTRLMODE]], [[Main/OptionReqonctrl|REQONCTRL]]
June 01, 2017, at 07:47 PM by -
Added lines 1-15:
(:title APM.REQCTRLMODE - APMonitor Option:)
(:keywords APM.REQCTRLMODE, Optimization, Estimation, Option, Configure, Default, Description:)
(:description Requested control mode: 1=simulate, 2=predict, 3=control:)


 Type: Integer, Input
 Default Value: 3
 Description: Requested control mode

REQCTRLMODE is the requested controller mode as an input for the application. The requested control mode (REQCTRLMODE) is set as an input to the desired level of control but sometimes the CTRLMODE is not able to match the request because of a failed solution, a critical MV is OFF, or other checks with the application. REQCTRLMODE level of 0 indicates that the program should not run and the program terminates without attempting a solution. REQCTRLMODE level of 1 (cold mode) indicates that the program should be run as a simulator with all STATUS values turned off on FVs, MVs, and CVs. REQCTRLMODE level of 2 (warm mode) indicates that the application should calculate control actions but only after the second cycle. This mode is commonly used to observe anticipated control actions before the controller is activated to level 3. REQCTRLMODE level of 3 means that the controller should be turned ON and implement changes to the process.