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_240 [2023/04/11 15:03] mashin |
en:release_note_240 [2023/08/17 13:32] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| \\ | \\ | ||
| \\ | \\ | ||
| - | <callout type="warning" icon="true"><WRAP em>CAUTION</WRAP> \\ | + | <callout type="warning" icon="true">**CAUTION** \\ |
| New APIs have been added that will work only with the v2.4 FW group. Please check the FW that will be compatible with the new APIs.\\ | New APIs have been added that will work only with the v2.4 FW group. Please check the FW that will be compatible with the new APIs.\\ | ||
| \\ | \\ | ||
| <text size="large">New API for v2.4</text>\\ | <text size="large">New API for v2.4</text>\\ | ||
| - | * API [[BS2_EnrolUserEx]] has been added | + | * Add API [[BS2_EnrolUserEx]] |
| - | * API [[BS2_GetUserInfosEx]] has been added | + | * Add API [[BS2_GetUserInfosEx]] |
| - | * Structure [[user management api#BS2UserBlobEx]] has been added | + | * Add structure [[user management api#BS2UserBlobEx]] |
| - | * [[ssl api]] has been added | + | * Add [[ssl api]] |
| \\ | \\ | ||
| Line 27: | Line 27: | ||
| <WRAP em><text size="x-large">New Features</text></WRAP> | <WRAP em><text size="x-large">New Features</text></WRAP> | ||
| <text size="x-large">1.</text> A brand new lift controller OM-120 has been released. New APIs and structures were added to allow SDK users to integrate this device and features to their own system.\\ | <text size="x-large">1.</text> A brand new lift controller OM-120 has been released. New APIs and structures were added to allow SDK users to integrate this device and features to their own system.\\ | ||
| - | * [[lift control api]] has been added | + | * Add [[lift control api]] |
| The OM-120 is a new device having capability of controlling 12 relays which can be used for lifts. There is now a new concept as floors, which will work exactly like the doors. Once a user authenticates, the floors connected to the relays of the OM-120 will be activated depending on the floor level the access group has. The floor level is the same concept of the access level and they both will be allocated to an access group.\\ | The OM-120 is a new device having capability of controlling 12 relays which can be used for lifts. There is now a new concept as floors, which will work exactly like the doors. Once a user authenticates, the floors connected to the relays of the OM-120 will be activated depending on the floor level the access group has. The floor level is the same concept of the access level and they both will be allocated to an access group.\\ | ||
| Line 34: | Line 34: | ||
| <text size="x-large">2.</text> The new FaceStation 2 will be released in the 2nd quarter of 2017. The v2.4 has implemented all features so the FaceStation 2 can be used right away with its release. | <text size="x-large">2.</text> The new FaceStation 2 will be released in the 2nd quarter of 2017. The v2.4 has implemented all features so the FaceStation 2 can be used right away with its release. | ||
| \\ | \\ | ||
| - | * [[face api]] has been added | + | * Add [[face api]] |
| The FaceStation 2 will be supporting a feature called group matching, which is a feature where you can have maximum 5000 users to be used for 1:N matching. The user can select the group that they belong to, and continue with the face matching.\\ | The FaceStation 2 will be supporting a feature called group matching, which is a feature where you can have maximum 5000 users to be used for 1:N matching. The user can select the group that they belong to, and continue with the face matching.\\ | ||
| \\ | \\ | ||
| Line 40: | Line 40: | ||
| <text size="x-large">3.</text> Certain devices will be compatible with the v1 Template on Cards. It was a downside of the v2 devices since there can be sites having v1 and v2 devices mixed. Now, it is possible to read the pre-issued cards from the v1 devices. | <text size="x-large">3.</text> Certain devices will be compatible with the v1 Template on Cards. It was a downside of the v2 devices since there can be sites having v1 and v2 devices mixed. Now, it is possible to read the pre-issued cards from the v1 devices. | ||
| \\ | \\ | ||
| - | * Structure [[configuration api#BS1CardConfig]] has been added | + | * Add structure [[configuration api#BS1CardConfig]] |
| The v2 devices can now be set to read Template on Cards issued from a v1 device. The v2 device will need the starting block index to be the same as the CIS index block of the v1 Template on Card. To use both v1 Template on Card, v2 Access on Card/Secure Credential Card together, they will need to share the same starting block index and CIS index block.\\ | The v2 devices can now be set to read Template on Cards issued from a v1 device. The v2 device will need the starting block index to be the same as the CIS index block of the v1 Template on Card. To use both v1 Template on Card, v2 Access on Card/Secure Credential Card together, they will need to share the same starting block index and CIS index block.\\ | ||
| \\ | \\ | ||
| Line 46: | Line 46: | ||
| <text size="x-large">4.</text> Job code has been added to support flexibility on integrations with a T&A software. It is possible to allocate job codes to users and get the job code information from the logs. This feature is included only with the v2.4 FW group. | <text size="x-large">4.</text> Job code has been added to support flexibility on integrations with a T&A software. It is possible to allocate job codes to users and get the job code information from the logs. This feature is included only with the v2.4 FW group. | ||
| \\ | \\ | ||
| - | * Structure [[user management api#BS2UserBlobEx]] has been added | + | * Add structure [[user management api#BS2UserBlobEx]] |
| Due to the limitation on size of the existing [[user management api#BS2UserBlob]] structure, there were needs to create a new structure to implement a new feature. The new [[user management api#BS2UserBlobEx]] structure will work only with the v2.4 FW group which includes a field for the job code. Each user will have their own code and name for each job code.\\ | Due to the limitation on size of the existing [[user management api#BS2UserBlob]] structure, there were needs to create a new structure to implement a new feature. The new [[user management api#BS2UserBlobEx]] structure will work only with the v2.4 FW group which includes a field for the job code. Each user will have their own code and name for each job code.\\ | ||
| \\ | \\ | ||
| Line 52: | Line 52: | ||
| <text size="x-large">5.</text> A new method to retrieve logs has been added. | <text size="x-large">5.</text> A new method to retrieve logs has been added. | ||
| \\ | \\ | ||
| - | * API [[BS2_GetLogBlob]] has been added | + | * Add API [[BS2_GetLogBlob]] |
| - | * Structure [[log management api#BS2EventBlob]] has been added | + | * Add structure [[log management api#BS2EventBlob]] |
| The existing API [[BS2_GetLog]] was not capable to get logs including the job code. Now there is a new API where it gets the event blob. The event blob can be categorized using a mask value, which leads to be possible to get logs based on the type of the log.\\ | The existing API [[BS2_GetLog]] was not capable to get logs including the job code. Now there is a new API where it gets the event blob. The event blob can be categorized using a mask value, which leads to be possible to get logs based on the type of the log.\\ | ||
| \\ | \\ | ||
| Line 59: | Line 59: | ||
| <text size="x-large">6.</text> Personal messages will be supported from the next version of the firmware for certain devices. This was implemented to be ready to use once the releases are made. | <text size="x-large">6.</text> Personal messages will be supported from the next version of the firmware for certain devices. This was implemented to be ready to use once the releases are made. | ||
| \\ | \\ | ||
| - | * Structure [[user management api#BS2UserBlobEx]] has been added | + | * Add structure [[user management api#BS2UserBlobEx]] |
| This feature will be supported starting from the FaceStation 2. The rest of the devices with a display screen will support this feature in the future release.\\ | This feature will be supported starting from the FaceStation 2. The rest of the devices with a display screen will support this feature in the future release.\\ | ||
| Due to the limitation on size of the existing [[user management api#BS2UserBlob]] structure, there were needs to create a new structure to implement a new feature. The new [[user management api#BS2UserBlobEx]] structure will work only with the v2.4 FW group which includes a field for personal messages. | Due to the limitation on size of the existing [[user management api#BS2UserBlob]] structure, there were needs to create a new structure to implement a new feature. The new [[user management api#BS2UserBlobEx]] structure will work only with the v2.4 FW group which includes a field for personal messages. | ||
| Line 66: | Line 66: | ||
| <text size="x-large">7.</text> SSL Communication will be available between the server and devices. This will allow the devices to be only connected to a server where the certificate is valid. | <text size="x-large">7.</text> SSL Communication will be available between the server and devices. This will allow the devices to be only connected to a server where the certificate is valid. | ||
| \\ | \\ | ||
| - | * [[ssl api]] has been added | + | * Add [[ssl api]] |
| \\ | \\ | ||
| \\ | \\ | ||