L-INX User Manual
92
LOYTEC
Version 4.0
LOYTEC electronics GmbH
A date range: This defines a range. Starting with a start date and ending with the end
date. No wildcards should be used.
A Week-and-Day definition: This defines dates based on a week, such as every 1st
Friday in a month, every Monday, every last Wednesday of a month.
While exception days of a calendar are accessible to all schedules on a device, specific
exceptions can be defined, which are embedded into a specific schedule. These are referred
to as an
embedded calendar
. In contrast to a regular calendar each calendar pattern of an
embedded calendar can hold exactly one date entry. This can be a single date or a date
range. The embedded exception days are only visible to the schedule they are defined in.
Apart from these restrictions, embedded calendars behave like the regular calendar. Figure
75 shows an example for an embedded exception day named ‗*-12-24‘.
A schedule defines at which time instants certain states of the scheduled data points are
maintained. The
next-state
feature allows looking ahead into the future and predicting when
the next scheduled state will occur. There are two data points involved: the time-to-next-
state is a counter in minutes to the next scheduled event, and the next-state data point is the
state of the next scheduled event. This information can be used by controllers to optimize
their algorithms (e.g., pre-heat a room for the scheduled occupancy state). Use the
SNVT_tod_event in CEA-709 to accomplish this task.
When a scheduler is executing the schedule on the local device, it is called a
local
scheduler
. Such a scheduler is configured to schedule data points and later its daily
schedules can be modified. When accessing the daily schedules of a scheduler, which
executes on a remote device, the object is called a
remote scheduler
. A remote scheduler
has the same interface to the user to modify daily schedules. A remote scheduler object can
be used as a user-interface for schedulers that execute on different devices.
5.3.4 Trending
Trending refers to the ability to log values of data points over time. A trend log object is
responsible for this task. It is configured, which data points shall be trended. Log records
are generated either in fixed time intervals, on change-of-value (COV) conditions, or when
a trigger is activated. Trend log objects can trend either local or remote data points.
The trend data is stored in a binary format on the device. The capacity of a given trend log
is configured. The trend log can be operated in one of two modes: In
linear mode
the trend
file fills up until it reaches its capacity. It then stops logging. In
ring buffer
mode the oldest
log records are overwritten when the capacity is reached.
A fill-level action can be activated, whenever the trend log has logged a percentage of its
log size with new log records. A fill-level condition of 70% on a trend log with 1000 items
capacity will activate the fill-level trigger every 700 logged records. This trigger can be
used to send E-Mails.
Trended data points can be logged as their actual values at given time instants or as an
aggregated value over the defined log interval. Aggregation can be calculated as minimum,
maximum, or average. Aggregation can be beneficial, if the trended value changes more
frequently than the selected log interval. Using aggregation, the log interval can be chosen
to limit the amount of logged data while preserving information of the trended value.
How many data points can be trended in one trend log is limited by the underlying
technology. So are some of the log modes. Refer to the technology sections for more
information.
5.3.5 E-mail
The e-mail function can be combined with the other AST features. The format of an e-mail
is defined through
e-mail templates
. An e-mail template defines the recipients, the e-mail
