NET_DVR_FINGERPRINT_STATUS

Status structure of applying or deleting fingerprint information.

Structure Definition

struct{
  DWORD dwSize;
  BYTE  byCardNo[ACS_CARD_NO_LEN/*32*/];
  BYTE  byCardReaderRecvStatus;
  BYTE  byFingerPrintID;
  BYTE  byFingerType;
  BYTE  byRecvStatus;
  BYTE  byErrorMsg[ERROR_MSG_LEN/*32*/];
  DWORD dwCardReaderNo;
  BYTE  byRes[20];
}NET_DVR_FINGERPRINT_STATUS, *LPNET_DVR_FINGERPRINT_STATUS;

Members

dwSize

Structure size.

byCardNo

No. of card linked with the fingerprint information.

byCardReaderRecvStatus

Fingerprint and card reader status, which is represented by byte: 0-failed, 1-succeeded, 2-the fingerprint module is offline, 3-try again or poor fingerprint picture quality, 4-full memory, 5-the fingerprint information already exists, 6-the fingerprint ID already exists, 7-invalid fingerprint ID, 8-it is not required to configure this fingerprint module.

byFingerPrintID

Finger No., which is between 1 and 10.

byFingerType

Fingerprint type: 0-normal fingerprint, 1-duress fingerprint.

byRecvStatus

Status code of access controller: 0-succeeded, 1-invalid finger No., 2-invalid fingerprint type, 3-invalid card No., 4-the fingerprint is not linked with employee ID or card No., 5-the employee ID does not exist, 6-no fingerprint data, 7-invalid fingerprint and card reader No., 8-invalid employee ID.

byErrorMsg

Error information of applying, the value of this member represents the No. of card linked with the existing fingerprint information when value of byCardReaderRecvStatus is "5".

dwCardReaderNo

Face recognition module No., which is returned when error occurs during applying. The value of this member refers to the No. of fingerprint and card reader linked with existing fingerprint information when the value of byCardReaderRecvStatus is "5". If the value of this member is 0, it indicates that no error occurred.

byRes

Reserved.

Remarks

Only when the values of byRecvStatus and byCardReaderRecvStatus equal to "0" and "1", respectively, is the fingerprint information applied. Otherwise, you should check the error reason according to the returned values of byRecvStatus and byCardReaderRecvStatus, and then apply this fingerprint information again.