Table of Contents

Version 2.1.0 (V2.1.0_221005)

Release

2022-10-05

For devices with the new SE processor, after upgrading the firmware to v2.1.0 or higher, you cannot downgrade to a lower version and downgrade the firmware customized in the lower version.
Devices with existing SE processor can be downgraded to a lower version.
For more information, check the serial number of the device and contact the Suprema (supremainc.com).


New features and improvement

1. Supports the dual SE processor.

2. Separated the log related to the cause of the door unlock.

3. Added relay deactivation option for exit button input.

4. Supports setting the byte order for smart cards.

5. Improved the OSDP ID to also be deleted when a security tamper occurs on the FaceStation F2 connected as a slave device.


Bug Fixes

1. Migration malfunction occurs when the firmware is upgraded from v1.1.0 or earlier to v1.1.1 or later (Affects version: v2.1.0).

2. Mobile card authentication suddenly does not work (Affects version: v1.0.0).

3. When the LAN cable connected to the device is disconnected and reconnected, it takes a long time for IP to be assigned by DHCP (Affects version: v1.0.0).

4. The device restarts when a user's face is enrolled consecutively or the main menu is repeatedly touched (Affects version: v1.0.0).

5. When using the card to authenticate to the device, the card that was normally authenticated fails intermittently (Affects version: v1.0.0).

6. The preview screen shown on the device during face authentication is different from the actual situation in front of the device (Affects version: v1.0.0).

7. If a user enrolled a face while face auth mode is off, and face authentication fails when face auth mode is turned on (Affects version: v1.0.0).

8. When the device sets the face auth mode to 1:N and sends many user faces on BioStar 2, it is stored even if the maximum number of faces that can be stored on the device is exceeded (Affects version: v1.0.0).

9. Improved the structure to prevent authentication fail caused by broken database or cache memory (Affects version: v1.0.0).