VLLO - APMonitor Option

Main.OptionVllo History

Hide minor edits - Show changes to output

June 08, 2017, at 11:01 PM by 10.5.113.159 -
Changed line 13 from:
See also [[Main/OptionVdvl|VDVL]], [[Main/OptionVlaction|VLACTION]], [[Main/OptionVlhi|VLHI]], [[Main/OptionVllo|VLLO]]
to:
See also [[Main/OptionVdvl|VDVL]], [[Main/OptionVlaction|VLACTION]], [[Main/OptionVlhi|VLHI]]
June 08, 2017, at 11:01 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/OptionVlaction|VLACTION]], [[Main/OptionVlhi|VLHI]], [[Main/OptionVllo|VLLO]]
June 01, 2017, at 06:40 AM by 45.56.3.173 -
Added lines 1-11:
(:title VLLO - APMonitor Option:)
(:keywords VLLO, Optimization, Estimation, Option, Configure, Default, Description:)
(:description Lower validity limit:)

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

 Type: Floating Point, Input
 Default Value: -1.0e20
 Description: Lower validity limit

VLLO is the lower validity limit for a measured value. Validity limits are one way to protect an application against bad measurements. This gross error detection relies on a combination of change values and absolute limits to determine when a measurement should be rejected. If the VLLO limit is crossed, the measured value is placed at VLLO or the maximum move allowed by VDVL when VLACTION=1. If VLACTION=0, there is no change in the measured value when a limit (VDVL, VLHI, VLLO) is exceeded.