2020-10-16

1. Added feature to change device ID.
2. Enhancement in the security of the device

• Restrict unencrypted connections.
• Enhancement in security of encryption keys
• Encrypt and migrate user information.

3. Improved Anti-passback zone to operate based on the door status.

4. Improved the scheduled unlock zone function for each floor when controlling elevator.

5. Supports new device.

• XPass D2 (Rev 2)

6. Support to the Mobile Access V1.1.
7. Changed the color of LED indicator.

1. Logs generated while the device is disconnected are not sent to BioStar 2, even after the device is reconnected.
2. When a user attempted authentication continuously in a short cycle, Wiegand output did not work properly.

1. An OSDP security session error occurred when connecting the OM-120 and XPass D2 as slave devices.

2. If a user set as device administrator was retransmitted, the user could not enter the admin menu.

3. When a 'Tamper On' event occurred after rebooting the master device, only output, of all trigger and actions set in the slave device, was operational.

4. When the connection with the master device had been lost due to a secure tamper with the slave device, the device did not connect again.

5. When all or user data were exported to a USB and then the user data were imported again after upgrading the device firmware, the event log was deleted.

6. An error in the master-slave connection occurred due to the RS-485 communication key.

7. When the device was powered off and then on again to update the fingerprint template, the user was deleted.

8. When the authentication was being processed on the device after a secure credential card had been issued, an authentication failure occurred with “Auth Unexpected Credential.”

9. After a global anti-passback violation, an authentication success log occurred twice.

10. An error occurred when authenticating with an iCLASS SEOS card when a smart card layout was set but SEOS was not selected in the card type option.

11. PIN authentication failed.

12. After upgrading the device firmware, all, user, or log data were not able to be exported to a USB.

13. After the message 'Invalid payload' occurred on the slave device, it was disconnected abnormally and reconnection was impossible.

14. When a locked device was rebooted for an RS-485 connection, the slave device became unlocked.

15. When Factory Default was performed using SDK, the device resource (logo image) did not initialize.
16. Authentication of fingerprints registered as duress fingerprints failed.
17. Device reboots or a timeout occurred when upgrading firmware or transferring user data during SSL secure communication.
18. It was unable to edit, delete or add an authentication mode.
19. When the delay for the output signal occurred repeatedly, the device did not work properly.
20. When the device was connected as a slave, the output port could not be set in the Trigger and Action.
21. Runtime crashed intermittently after initializing the fingerprint sensor.
22. When a user authenticated on the slave device using a smart card or the face, the master device would reboot.
23. When a user authenticated the fingerprint after setting the byte order as LSB and the Wiegand output information as the user ID, the device would reboot.
24. Once a card had been registered on the Wiegand output device, the device would not work properly when trying to output data using a fingerprint registered to another user.
25. When the code for generating protocol packets in RFCore-HID SAM exceeded 127, the device did not work properly.
26. When the master device wss rebooted with both the scheduled unlock and manual lock set, it operated using the scheduled unlock.
27. Slave device with stored certificates failed to connect to the server while using Secure communication with a device.