Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:release_note_270 [2020/07/28 14:37] yjjung |
en:release_note_270 [2023/08/17 13:25] (current) |
||
---|---|---|---|
Line 9: | Line 9: | ||
* Supports lift lock/unlock zone features based on schedule | * Supports lift lock/unlock zone features based on schedule | ||
* Supports User phrase (Private message) feature on the server | * Supports User phrase (Private message) feature on the server | ||
- | * Supports Global APB violation check by the door sensor | + | * Supports Global APB By Door Open |
<text size="x-large">1.</text> Device XPass D2 Revision, XPass D2 Keypad Revision are supported. | <text size="x-large">1.</text> Device XPass D2 Revision, XPass D2 Keypad Revision are supported. | ||
Line 15: | Line 15: | ||
<text size="x-large">2.</text> Lift lock/unlock zone which works based on schedules regardless of access group is supported. | <text size="x-large">2.</text> Lift lock/unlock zone which works based on schedules regardless of access group is supported. | ||
- | * Structure [[zone control api#BS2LiftFloors]] has been added | + | * Refer to structure [[zone control api#BS2LiftFloors]] |
- | * Structure [[zone control api#BS2LiftLockUnlockZone]] has been added | + | * Refer to structure [[zone control api#BS2LiftLockUnlockZone]] |
- | * API [[BS2_GetLiftLockUnlockZone]] has been added | + | * Refer to API [[BS2_GetLiftLockUnlockZone]] |
- | * API [[BS2_GetAllLiftLockUnlockZone]] has been added | + | * Refer to API [[BS2_GetAllLiftLockUnlockZone]] |
- | * API [[BS2_GetLiftLockUnlockZoneStatus]] has been added | + | * Refer to API [[BS2_GetLiftLockUnlockZoneStatus]] |
- | * API [[BS2_GetAllLiftLockUnlockZoneStatus]] has been added | + | * Refer to API [[BS2_GetAllLiftLockUnlockZoneStatus]] |
- | * API [[BS2_SetLiftLockUnlockZone]] has been added | + | * Refer to API [[BS2_SetLiftLockUnlockZone]] |
- | * API [[BS2_SetLiftLockUnlockZoneAlarm]] has been added | + | * Refer to API [[BS2_SetLiftLockUnlockZoneAlarm]] |
- | * API [[BS2_RemoveLiftLockUnlockZone]] has been added | + | * Refer to API [[BS2_RemoveLiftLockUnlockZone]] |
- | * API [[BS2_RemoveAllLiftLockUnlockZone]] has been added | + | * Refer to API [[BS2_RemoveAllLiftLockUnlockZone]] |
<text size="x-large">3.</text> User phrase feature that you can request the user phrase(private message) to the server is supported. | <text size="x-large">3.</text> User phrase feature that you can request the user phrase(private message) to the server is supported. | ||
- | * Structure [[configuration api#BS2DisplayConfig]] has been added | + | * Refer to structure [[configuration api#BS2DisplayConfig]] |
- | * API [[BS2_SetUserPhraseHandler]] has been added | + | * Refer to API [[BS2_SetUserPhraseHandler]] |
- | * API [[BS2_ResponseUserPhrase]] has been added | + | * Refer to API [[BS2_ResponseUserPhrase]] |
- | <text size="x-large">4.</text> Global APB violation check by the door sensor is supported. \\ | + | <text size="x-large">4.</text> Global APB By Door Open is supported. \\ |
- | The feature checks twice for Global APB violation; 1. after user authentication 2. door sensor base. \\ | + | Global APB By Door Open has two steps; i) User authentication ii) Actual access based on the door sensor \\ |
You can figure out the user who actually doesn't go in even after successful authentication and the door unlock using this feature. | You can figure out the user who actually doesn't go in even after successful authentication and the door unlock using this feature. | ||
- | * Structure [[door_control_api#BS2DoorSensor]] has been added | + | * Refer to structure [[door_control_api#BS2DoorSensor]] |
- | * API [[BS2_SetGlobalAPBViolationByDoorOpenHandler]] has been added | + | * Refer to API [[BS2_SetGlobalAPBViolationByDoorOpenHandler]] |
- | * API [[BS2_CheckGlobalAPBViolationByDoorOpen]] has been added | + | * Refer to API [[BS2_CheckGlobalAPBViolationByDoorOpen]] |
\\ | \\ | ||
Line 46: | Line 46: | ||
<text size="x-large">2.</text> Fixed the issue that SDK can't process received packets from the device with IPv6 connection mode.\\ | <text size="x-large">2.</text> Fixed the issue that SDK can't process received packets from the device with IPv6 connection mode.\\ | ||
- | * Structure [[user management api#BS2UserBlobEx]] has been added | + | * Refer to structure [[user management api#BS2UserBlobEx]] |
- | * API [[BS2_VerifyUserEx]] has been added | + | * Refer to API [[BS2_VerifyUserEx]] |
- | * API [[BS2_IdentifyUserEx]] has been added | + | * Refer to API [[BS2_IdentifyUserEx]] |
- | * API [[BS2_EnrolUserEx]] has been added | + | * Refer to API [[BS2_EnrolUserEx]] |
- | * API [[BS2_VerifyUserSmallEx]] has been added | + | * Refer to API [[BS2_VerifyUserSmallEx]] |
- | * API [[BS2_IdentifyUserSmallEx]] has been added | + | * Refer to API [[BS2_IdentifyUserSmallEx]] |
- | * API [[BS2_EnrollUserSmallEx]] has been added | + | * Refer to API [[BS2_EnrollUserSmallEx]] |
<text size="x-large">3.</text> Fixed the issue with the error BS2_SDK_ERROR_INVALID_PACKET when received log from the device due to the image log larger than 16KB.\\ | <text size="x-large">3.</text> Fixed the issue with the error BS2_SDK_ERROR_INVALID_PACKET when received log from the device due to the image log larger than 16KB.\\ | ||
- | * API [[BS2_GetLogBlob]] has been added | + | * Refer to API [[BS2_GetLogBlob]] |
- | * API [[BS2_GetLogSmallBlob]] has been added | + | * Refer to API [[BS2_GetLogSmallBlob]] |
- | * API [[BS2_GetLogBlobFromDir]] has been added | + | * Refer to API [[BS2_GetLogBlobFromDir]] |
- | * API [[BS2_GetLogSmallBlobFromDir]] has been added | + | * Refer to API [[BS2_GetLogSmallBlobFromDir]] |
- | * API [[BS2_GetImageLog]] has been added | + | * Refer to API [[BS2_GetImageLog]] |