Firmware Version 1.2.0 (Build No. 1.2.0_181119)
Release|2018-11-29
Main Fixes
-
When attempting to connect to a wireless LAN, if a user deletes and saves the IP address and gateway, the device restarts repeatedly.
-
When Micom is reset, the output does not restore to its previous status.
-
Wiegand Out is not output when authenticating with blacklist card.
-
With Bypass enabled, authentication failure message is not displayed when unregistered ID is authenticated.
-
Authentication fails because the server matching enabled for RFID cards and IDs.
-
The user cannot issue a new File after the App and File are created when issuing the DESFire card.
-
The device reboots if a user authenticates the RFID card or face consecutively on the device.
-
If using Group Matching, the device displays the group name as None when authenticating a face.
-
A code is added to prevent the authentication fails because the cache memory is broken.
New Features and Improvements
-
Support to AES encryption type for DESFire card.
-
Support to DESFire/DESFire EV1 Advanced option.
-
Support to the creation of up to 2048 Access Levels and Access Groups.
-
If a user is registered, modified, or deleted, the event log shows whether the editing was done on the server or on the device.
-
If the data transmission fails when communicating with OSDP, it is transmitted again.
-
Improves the data protection.
-
Increase the items to encrypt the data.
-
Support to setting the period for storing the personal information.
-
Support for additional features in Secure Tamper: Delete Users, Logs, Data Encryption Key, SSL certificate, and Smart Card Layout when a secure tamper event occurs.
-
-
Change the maximum value of the width for the Wiegand Input.
-
Support to the number of users, fingerprints, faces, and cards in Manage Users in Device.
-
Support for Individual Authentication Successful Messages and Working alarm time reports.
-
When using The bypass, The card ID is output as Wiegand even though a user authenticates with the AoC.
Bug Fixes
-
The relay does not work even though a user successfully authenticated the face on the device.
-
The relays operate differently from the previous status if the slave device is reconnected.
-
Modified the firmware of that slave device so that it cannot be upgraded when a device not supported by the master device is connected as a slave.
-
With Bypass enabled, the device does not respond even if a user selects the Menu, T & A, or ID after authentication.
-
Change some special characters (\, /, :, *, ?, ", ', `, <, >, |, .) to be unavailable when setting a user name.
-
The setting value is not saved when Face Config is set to the slave device.
-
The device(FS2-D) intermittently reboots.
-
If a user authenticates the card to XPass D2 connected to as a slave device, the beep sounds twice.
-
1: N authentication can also be added on the slave device even though the master device is only capable of 1: 1 authentication.
-
If the user uses the BS_GetLogBlob command to get the door ID, the door ID is not output normally.