Download Print this page

Event Logging - 2N Helios IP Configuration Manual

Door access intercom http api
Hide thumbs Also See for Helios IP:

Advertisement

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:
1
2
3
4
500
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
KeyPressed
CallStateChanged
CodeEntered
CardEntered
DeviceState
The 2N
There are two 2N
®
2N
TELEKOMUNIKACE a.s., www.2n.cz
TimeStamp
13/06/01 12:05:01
13/06/01 17:30:23
14/06/01 08:10:23
14/06/01 08:10:23
...
27/06/01 17:05:01
®
Helios IP event log readout is based on the WS-BaseNotification standard.
®
Helios IP log event retrieval modes –
RecordID
Event Type
65533
CardEntered
65534
CardEntered
65535
KeyPressed
0
KeyPressed
...
...
496
CardEntered
Popis
Keystroke
Call state change
Numerical code entering
RFID card detection
Device state change
Subscription
Event Data
Card=...
Card=...
Key=...
Key=..
...
Card=...
and
PullPoint
.
8

Advertisement

loading