Event logging – 2N Helios IP HTTP API v2.6 User Manual
Page 8
8
3. Event Logging
2N® Helios IP implements an internal event log, which records events arising in the
device – such as KeyPressed, CodeEntered, CardEntered, CallStateChanged and so on.
The log capacity is 500 events. When the log fills up, any new event deletes the oldest
record. Events are arranged according to date and time (TimeStamp) in the log. The
maximum time resolution is 1s. Also, each event is assigned a unique 16-bit RecordId,
which is automatically incremented by 1s with every new event. The RecordId code
helps distinguish between records of the same date and time.
The 2N® Helios IP event logs can be arranged in a table:
TimeStamp
RecordID
Event Type
Event Data
1
13/06/01 12:05:01
65533
CardEntered
Card=…
2
13/06/01 17:30:23
65534
CardEntered
Card=…
3
14/06/01 08:10:23
65535
KeyPressed
Key=…
4
14/06/01 08:10:23
0
KeyPressed
Key=..
…
…
…
…
500
27/06/01 17:05:01
496
CardEntered
Card=…
The first table row represents the oldest record (log beginning). The last row
represents the most recent record (log end). Being a 16-bit number, the RecordID
automatically overflows from 65535 to 0.
2N® Helios IP defines several types of events to be logged.
Event
Popis
KeyPressed
Keystroke
CallStateChanged
Call state change
CodeEntered
Numerical code entering
CardEntered
RFID card detection
DeviceState
Device state change
The 2N
Helios IP event log readout is based on the WS-BaseNotification standard.
®
There are two 2N
Helios IP log event retrieval modes –
and
.
®
Subscription
PullPoint