Author: Alexander Marin [email protected]
[TOC]
| SDK function name | Described(X=Yes, O=No) | Notes |
|---|---|---|
| OnConnected | X | This can be easily checked with a device info request. |
| OnDisConnected | X | This can be easily checked with a device info request. |
| OnAlarm | X | |
| OnDoor | X | Some tests need to be performed. |
| OnAttTransaction | O | Applicable only to BW. |
| OnAttTransactionEx | X | |
| OnDeleteTemplate | O | Todo. |
| OnEnrollFinger | X | |
| OnFinger | X | |
| OnFingerFeature | X | |
| OnHIDNum | O | Todo. |
| OnKeyPress | O | Todo. |
| OnNewUser | O | Todo. |
| OnVerify | X | |
| OnWriteCard | O | Todo. |
| OnEmptyCard | O | Todo. |
| OnEMData | O | Just triggers the event for unknown inputs. |
| RegEvent | O | Just checks for several events. |
| ReadRTLog | O | Involves reading PC buffer. |
| GetRTLog | O | Involves reading PC buffer. |
The realtime events are useful to monitor the state of doors and to receive alarms of abnormal situations, this type of packets are also used to follow the steps of an enrolling procedure.
To receive this type of packets a connection needs to be setup, so the idea is to connect to all the devices to be monitored and interpret the incoming packets from the machines.
This packets are sent without prior request since they depend on external situations, so the general conversation flow is as follows:
> rtpacket(event=EF_X, data=<...>, reply number=0000)
> packet(id=CMD_ACK_OK, session id=<s>, reply number=0000)
Where the session id of the client reply is the same as the id set from the connection, and the reply number is the same of the incoming packet which for realtime packets, happens to be 0000.
To be able to receive realtime packets, you must send a packet with the command CMD_REG_EVENT and a fixed data field of 4 bytes:
> packet(id=CMD_REG_EVENT, data=ffff0000)
> packet(id=CMD_ACK_OK)
There may be several causes to trigger the alarm, this info is included in the realtime packet sent to the device, the general form of the packet is given by:
rtpacket(event=EF_ALARM, data=<alarm info>)
Where the alarm info structure varies according to the event trigger, if the alarm is triggered.
1.If the alarm is triggered because of an exit button, tamper or misoperation.
The alarm info is 4 bytes long and the first byte indicates the alarm type, with the following codification:
| Alarm type | Value[hex] |
|---|---|
| Misoperation | 3A |
| Tamper | 37 |
| Exit button | 35 |
2.If the alarm is triggered because the door closes the alarm info is 8 bytes long and the first byte indicates the door is closing, with the value 0x54.
3.For duress alarms the alarm info is 12 bytes long
| Name | Description | Value[hex] | Size[bytes] | Offset |
|---|---|---|---|---|
| Fixed. | ffffffff | 4 | 2 | |
| alarm type | Alarm type, indicates cause. | varies (<) | 2 | 4 |
| user sn | User's serial number. | varies (<) | 2 | 6 |
| match type | Matching way. | varies (<) | 4 | 8 |
(<): Little endian format.
The alarm type indicates what triggered the alarm:
| Alarm type | Value[hex] |
|---|---|
| Duress | 20 |
| Passback | 22 |
See Alarm section.
| Name | Description | Value[hex] | Size[bytes] | Offset |
|---|---|---|---|---|
| user id | User's pin number, stores as a string. | varies | 9 | 0 |
| Fixed. | zeros | 15 | 9 | |
| verify type | Verify type. | varies (<) | 2 | 24 |
| att time | Time given in a special format. | H0H1H2H3H4H5 | 6 | 26 |
(<): Little endian format.
The verify type follows the same codification given on the attendance logs.
The time of attendance is given with a special format, if the time is given by the sequence:
H0 H1 H2 H3 H4 H5
The date
YEAR/MONTH/DAY HOURS:MINUTES:SECONDS
can be obtained by extracting each byte as a number, and entering them in the following formula:
date = 20<H0>/<H1>/<H2> <H3>:<H4>:<H5>
This is a realtime packet of an attendance event:
00000000: 50 50 82 7D 28 00 00 00 F4 01 AC 12 01 00 00 00 PP.}(...........
00000010: 39 39 39 31 31 31 33 33 33 00 00 00 00 00 00 00 999111333.......
00000020: 00 00 00 00 00 00 00 00 01 00 12 06 19 11 29 05 ..............).
The user id is "999111333", verified using the fingerprint and the date corresponds to:
2018/06/25 17:41:05
After a fingerprint enrolling process the machine returns a structure indicating how the procedure went:
rtpacket(event=EF_ENROLLFINGER, data=<enroll result>)
The enroll result structure has the following fields:
| Name | Description | Value[hex] | Size[bytes] | Offset |
|---|---|---|---|---|
| result | Error code. | varies (<) | 2 | 0 |
| fp size | Size of fingerprint template. | varies (<) | 2 | 2 |
| user id | User's pin number, stores as a string. | varies | 9 | 4 |
| finger index | Finger index of the template. | varies | 1 | 13 |
If the error code is equal to zero, that means the there was no error in the enrolling process, if the value is not zero that means that there was an error, in that case the fields fp size, user id and finger index, aren't even included.
After someone puts finger on the machine reader, the machine sends a packet to indicate this, this happens in the enroll procedure and also in normal operation, whether the user is registered or not.
The packet doesn't carry any additional data.
rtpacket(event=EF_FINGER)
When performing the enrolling procedure, the machine sends a packet after a fingerprint sample to indicate the score of the given sample:
rtpacket(event=EF_FPFTR, data=<score>)
The score is a measure of the "quality" of the fingerprint sample, the value is given as number, that may be 0 or 100(0x64).
When someone tries to perform verification, the machine sends a packet to the client with the serial number of the user.
rtpacket(event=EF_VERIFY, data=<verify info>)
The returned structure has the following fields:
| Name | Description | Value[hex] | Size[bytes] | Offset |
|---|---|---|---|---|
| user sn | User's serial number. | varies (<) | 4 | 0 |
| Fixed. | 01 | 1 | 4 |
If the user can't be identified, then the user sn equals to ffffffff