1 overview of the scheduler xml file, Overview of the scheduler xml file -2, Overview of the scheduler xml file – Echelon i.LON SmartServer 2.0 User Manual
Page 133
i.LON SmartServer 2.0 Programmer’s Reference
9-2
comes from the local Calendar object via an internal binding between the nvoEcDateEvent output of
the Calendar, and the nviDateEvent input of the NodeObject.
After a restart, the Scheduler recalculates the last Scheduler operation. It also sets the data point
nvoDateResync to “100.0 1”, which updates the SmartServer’s exception list. You can set the value
of nvoDateResync to “100.0 1” and then return it back to “0.0 0” with the Write function at any time to
refresh the exception list manually. The data point nviEcResync of the Calendar will be internally
bound to nvoDateResync if no external binding is created. However, the Scheduler pulses the
NodeObject NV to ensure that the NodeObject always has an up-to-date Exception list, so this should
not be necessary.
9.1
Overview of the Scheduler XML File
The #8000010128000000[4].UFPTscheduler.xml file stores the configuration of the Schedulers that
you have added to the SmartServer. You can create new Schedulers using the Set function, or by
manually editing the #8000010128000000[4].UFPTscheduler.xml file, and rebooting the SmartServer.
You can create up to 40 Schedulers per SmartServer. You can add more than 40 Schedulers if you
load the dynamic v40 XIF on your SmartServer and you operate your SmartServer in Standalone
mode. Note that using the v40 XIF with the SmartServer operating in LNS mode (LNS Auto or LNS
Manual) is not supported.
The following represents a sample #8000010128000000[4].UFPTscheduler.xml file for a SmartServer
with one Scheduler.
App/Scheduler[0]
App/Scheduler[0]/nviEsEnable[0]
App/Digital
Output
1/nviClaValue_1
App/Digital
Output
2/nviClaValue_2
LonFormat="UCPTeventType">ET_LOCK
LonFormat="">ON
LonFormat="UCPTvalueDef">ON
LonFormat="UCPTtimeDirection">TD_POSITIVE
LonFormat="UCPTeventType">ET_NUL