Echelon i.LON SmartServer 2.0 - Manual (Page 111)

i.LON SmartServer 2.0 Programmer’s Reference 7-19
created. An Alarm Notifier will not generate a log file until it has generated an alarm notification.
You should not attempt to read more than 100 log entries with a single Read request.
The following code demonstrates how to use a Read request to generate a list of up to the first 100
entries stored in a specific Alarm Log.
Request
//Item[@xsi:type="UFPTalarmNotifier_Data"][UCPTalarmLog="HISTORICAL"]
[position()<100]
Net/LON/iLON App/Alarm Notifier[0]
Response
0
Net/LON/iLON App/Alarm Notifier[0]
2008-02-29T15:01:40.650-08:00
LonFormat="UCPTalarmLog">HISTORICAL
2008-02-29T11:14:41.300-08:00
2008-02-29T11:14:41.300-08:00
0
0.496
1
xsi:type="UFPTalarmNotifier_Data">
Net/LON/iLON App/Data Logger[0]/nvoDlLevAlarm[0]
nvoDlLevAlarm[0]
2008-02-29T11:14:41.300-08:00
LonFormat="#0000000000000000[0].SNVT_alarm#LO">0
LonFormat="UCPTpointStatus">AL_NO_CONDITION
255
//*[@xsi:type=“UFPTalarmNotifier_Meta_Data”]
[UCPTname=“Net/LON/iLON App/Alarm Notifier[0]”]
Net/LON/iLON
App/Alarm Notifier[0]
2008-02-29T11:13:44.560-08:00
iLON
LonFormat="UCPTalarmStatus">AUTO_CLEAR
Online
0
0
LonFormat="UCPTalarmType">PASSIVE
In addition to the requested log entries, the Read function returns a single of type
“UFPTalarmNotifier_Meta_Data” for each log file from which entries were read. This
“UFPTalarmNotifier_Meta_Data” has the following properties:
The name of the data logger from which entries were read in
the following format: <network/channel/device/functional
block>.
A timestamp indicating the time that the last log entry was