Main

VLACTION - APMonitor Option

Main.OptionVlaction History

Show minor edits - Show changes to output

June 08, 2017, at 10:50 PM by 10.5.113.159 -
Changed lines 5-6 from:
%width=50px%Attach:fv.png  %width=50px%Attach:mv.png  %width=50px%Attach:cv.png
to:
%width=50px%Attach:fv.png  %width=50px%Attach:mv.png  %width=50px%Attach:cv.png [[Main/DbsVariable|Local Options]] | %width=30px%Attach:apm.png [[Main/DbsGlobal|Global Options]]
Added lines 12-13:

See also [[Main/OptionVdvl|VDVL]], [[Main/OptionVlhi|VLHI]], [[Main/OptionVllo|VLLO]]
June 01, 2017, at 06:39 AM by 45.56.3.173 -
Added lines 1-11:
(:title VLACTION - APMonitor Option:)
(:keywords VLACTION, Optimization, Estimation, Option, Configure, Default, Description:)
(:description Validity Limit Action:)

%width=50px%Attach:fv.png  %width=50px%Attach:mv.png  %width=50px%Attach:cv.png

 Type: Integer, Input
 Default Value: 0
 Description: Validity Limit Action

VLACTION is the validity limit action when VDVL is exceeded. The change in measured values is recorded at every cycle of the application and compared to the VDVL limit. Validity limits are placed to catch instrument errors that may otherwise create bad inputs to the application. If a delta validity limit is exceeded, the action is to either freeze the measured value at the last good value (VLACTION=0) or change the measured value by a maximum of VDVL in the direction of the bad measurement (VLACTION=1).