Echelon LonPoint Application and Plug-In - Manual (Page 155)

The LonPoint Application and Plug-in Guide 11-9
Schedule Constraint Equations
Schedule constraint equations are created to specify site-specific limitations in
the way that Schedule Keeper users may modify a Schedule. These equations
are then evaluated every time that the user exits the “Schedules” modification
screen or moves from one Schedule tab to another. If the equation evaluates to
FALSE when schedule constraints are evaluated, the constraint error string will
be displayed and the modification will not be accepted.
Legal equations include:
The comparison equation – if you want to compare one event time to another, all
of the standard comparison operations are available. Examples include:
EnableUnoccupiedOpsOFF < EnableMorningWarmupON
The EnableUnoccupiedOpsOFF event must occur before the
EnableMorningWarmupON
event.
EnableUnoccupiedOpsOFF + 00:10 > EnableMorningWarmupON
The EnableUnnocupiedOpsOFF event must occur either after or less than 10
minutes before the EnableMorningWarmupON event.
EnableUnoccupiedOpsOFF >= EnableMorningWarmupON
The EnableUnoccupiedOpsOFF event must occur at the same time or after
EnableMorningWarmupON
event.
EnableUnoccupiedOpsOFF <= EnableMorningWarmupON + 00:20
The EnableUnoccupiedOpsOFF event must occur before or no more than 20
minutes after the EnableMorningWarmupON event.
EnableUnoccupiedOpsOFF = EnableMorningWarmupON
The EnableUnoccupiedOpsOFF event must occur at the same time as the
EnableMorningWarmupON
event.
EnableUnoccupiedOpsOFF !=EnableMorningWarmupON
The EnableUnoccupiedOpsOFF event must not occur at the same time as
EnableMorningWarmupON
event.
The existence equation – If there is an event that must appear in every schedule,
you should specify it with the existence equation. This equation consists of the
event name and only the event name.
Logical equations - Simple equations may be logically strung together with the
“&” and “|” operators, signifying logical AND and OR, respectively. In general,
this should be avoided, as the same effect can usually be achieved by writing
more constraint equations, and each one can have a more specific error string.