beautypg.com

Event calendar, Eventcalendar.xml, Event calendar -1 – Echelon i.LON 100 e2 Internet Server User Manual

Page 168: Eventcalendar.xml -1, 11 event calendar, 1 eventcalendar.xml

background image

i.

LON 100 Internet Server Programmer’s Reference

11-1

11 Event Calendar

Use the Event Calendar application to define the exception points that you will reference

when creating the date-based schedules for your Event Schedulers. Each exception point you

create represents a date, or a group of dates. When you reference an exception in an Event
Scheduler, you will be able to assign the dates for that exception a unique schedule. This

may be useful when creating an Event Scheduler that requires different schedules for

holidays than regular weekdays, or during different seasons of the year.

This chapter describes how to create exceptions with the Event Calendar application.

Chapter 10, Event Scheduler, describes how to create an Event Scheduler and reference the
exceptions you create.
You can create daily exceptions as one-time exceptions, or exceptions that will be repeated

annually. The

i.

LON 100 supports one active Event Calendar, with up to 256 schedule

exception points.
When an Event Scheduler references an exception point, the Event Calendar application

supplies the dates an exception point references to the Node Object using the data point
NVL_nvoEcDateEvent. The Event Scheduler then reads this exception list from the local

Node Object. The information contained in the exception list includes when the exception is
valid, and when the exception will recur.
Whenever an exception is modified with the functions described in this chapter, all

exceptions in the Event Calendar are recalculated and copied to the NVL_nvoEcDateEvent
data point as a series of updates. By default, the NVL_nvoEcDateEvent data point of the

Event Calendar and the NVL_nviDateEvent data point of the Node Object are internally

bound, so that no network traffic is generated. Thus, the update from the Event Calendar is
passed to the local Node Object, and all the Event Schedulers will read the updated exception

list from the local Node Object.
In this fashion, each Event Scheduler will always have up-to-date definitions of the
exceptions it references. To force all exceptions to be recalculated and copied to the

NVL_nvoEcDateEvent data point, you may update the NVL_nviEcDateResync data point

(which will be internally bound to the NVL_nvoDateResync data point of the Node Object if
no external binding is created) with a value of "100.0 1".

11.1 EventCalendar.XML

The EventCalendar.XML file stores the configuration of the Event Calendars that you have
added to the

i.

LON 100. You can create multiple Event Calendars with up to 256 exceptions

per

i.

LON 100. However, the

i.

LON 100 supports only one active Event Calendar at a time.

The active Event Calendar must use index number 0.
Each defined Event Calendar is signified by a element in the XML file. You can

create event Calendars with the EventCalendarSet function, or by manually editing the
EventCalendar.XML file and downloading it to the

i.

LON 100 via FTP. The sections

following this example provide instructions and guidelines to assist you when doing so.

The following represents a sample EventCalendar.XML file for an

i.

LON 100 with an Event

Calendar that has three defined exceptions named Holiday, Easter, and Christmas.

1

1