Echelon i.LON SmartServer Technical Information Page 137

  • Download
  • Add to my manuals
  • Print
  • Page
    / 443
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 136
i.LON SmartServer 2.0 Programmer’s Reference
9-6
</GetResponse>
The function returns an <Item> element for each Scheduler referenced in the input parameters supplied
to the function. The properties included in each element are initially defined when the Scheduler is
created. You can write to these properties with the Set function. The following table describes these
properties.
Property Description
<UCPTname>
The name of the Scheduler in the following format:
<network/channel/device/functional block>.
<UCPTannotation>
The program ID and functional profile template used by the
Scheduler. This property is always
8000010128000000[4].UFPTscheduler
<UCPThidden>
A flag indicating whether the Scheduler functional block is
hidden or shown in the navigation pane on the left side of
the SmartServer Web interface. This property may have the
following values:
0 – shown
1 – hidden
<UCPTitemStatus>
This property only appears if the data logger is not
synchronized with an LNS network database or it has been
deleted. In this case, it has the following values:
IS_NOTSYNCED
IS_DELETED
<UCPTlastUpdate>
A timestamp indicating the last time the configuration of the
Scheduler was updated. This timestamp uses the following
format:
YYYY-MM-DDTHH:MM:SSZ
<UCPTuri>
The name of the file containing the configuration web page
for the Scheduler on the SmartServer flash disk, absolute or
relative to /web/user/echelon. This property is
#8000010128000000[4].UFPTscheduler _Cfg.htm by
default.
<DataPoint>
Input
For each <Data Point> element, you must enter the name
(UCPTpointName) of the data point to be updated. In
addition, you should fill in the delay time
(SCPTdelayTime) property for each data point. This
integer value represents the period of time, in seconds, that
must elapse before this data point is updated based on a
DayBased or DateBased schedule point. This allows you to
stagger the updating of your data points, which may be
advisable if a Scheduler scheduler is to update multiple data
points at the same time.
NOTE: If a SNVT_tod_event data point is used, it will
only be updated if its value (current_state of next_state) has
changed. If a heartbeat (UNVTminSendTime) is defined for
the SNVT_tod_event data point, the time_to_next_state
Page view 136
1 2 ... 132 133 134 135 136 137 138 139 140 141 142 ... 442 443

Comments to this Manuals

No comments