Ir al contenido principal

Firmware Version 1.6.0 (Build No. 1.6.0_260212)

Release|2026-03-17

Precaución

  • After upgrading the firmware to v1.5.1 or later, it is not able to downgrade to an earlier version of the firmware.

  • BEP2-OA type of BioEntry P2 model support HID iCLASS card type through SE processor.
    For devices with the new SE processor, after upgrading the firmware to v1.4.4 or later, 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.

New Features and Improvements​

  1. Reflects global cybersecurity standards and the latest security requirements.

  2. Added identification code to support recognition of the latest cards.

    • DESFire EV3

  3. Improved time synchronization behavior between server and devices.

  4. Supports feature to set the baud rate of slave devices.

  5. Improved to distinguish devices that support the Secure Tamper feature.

  6. Supports the Ignore Repeated Signals Duration feature, which ignores repetitive authentication signals from the controller when the device is connected to a 3rd party controller via Wiegand.

  7. Supports not logging events when the Ignore Repeated Signals Duration feature is activated.

  8. Supports SL1, SL3, and SL1/SL3 Mix Mode for security level compatibility with MIFARE Plus EV1 cards.

    • SL1: Compatible mode with MIFARE Classic
    • SL3: Advanced security mode based on AES

  9. Improved to not recognize SEOS configuration cards as CSN for 1 minute after device booting.

  10. Improved so that when authentication is attempted on a door set to Manual Lock, an authentication failure event occurs and a locked message appears.

  11. Supports real-time monitoring of the device's multiple statuses in BioStar X.

  12. Improved compatibility to support accessing the detail page and changing settings for Master Admin supported devices connected as slaves.

Bug Fixes​

  1. Some smart cards fail to be recognized in environments using the new SE chip firmware. Versión afectada: 1.4.4

  2. Authentication fails with a ‘period expired’ message when using a smart card issued with a visual face included. Versión afectada: 1.0.0

  3. The database does not migrate when using the getOperator function in the SDK. Versión afectada: 1.0.0

  4. Access group authentication behaves abnormally according to the schedule (Daily) when DST is applied. Versión afectada: 1.0.0

  5. DESFire smart cards with the Custom Smart Card Layout set to Secondary Key are recognized as CSN cards. Versión afectada: 1.5.1

  6. When the RS-485 mode is set to Slave, the Custom Smart Card Layout and Byte Order of the device are not saved as set. Versión afectada: 1.5.1

  7. Custom Smart Card option does not appear on the device detail page when RS-485 mode is set to Slave. Versión afectada: 1.5.1

  8. When a user with more than two cards enrolled attempts card authentication to the Wiegand output device, the ID of a card other than the authenticated card is output. Versión afectada: 1.5.1

  9. When the device is restarted with the Primary Key set only in the Suprema Smart Card Layout and the Secondary Key set only in the Custom Smart Card Layout, the device recognizes the Custom Smart Card as a CSN card. Versión afectada: 1.5.1

  10. When the elevator is set to Schedule Unlock, if the RS-485 connection of the slave device is disconnected and then reconnected after the Schedule Unlock ends, the relay does not operate as locked. Versión afectada: 1.0.0

  11. Custom smart cards with the DESFire Advanced option enabled fail to be recognized. Versión afectada: 1.5.1

  12. Custom Smart Card Layout set through Batch Edit is not applied on the device detail page. Versión afectada: 1.5.1

  13. When the device log is full and a new event occurs, unintended logs are retrieved with the newly generated event. Versión afectada: 1.4.4

  14. When using the BS2_GetDeviceCapabilities function in the SDK to get information supported by the device, the CustomClassicPlus and CustomDesFireEV1 are displayed as False though the device supports custom smart cards. Versión afectada: 1.5.1

  15. Device abnormally restarts when changing the device’s Network settings in BioStar 2. Versión afectada: 1.0.0

  16. Incorrect maxFacePerUser value being returned for devices lacking face authentication support when retrieving device capabilities via the BS2_GetDeviceCapabilities API. Versión afectada: 1.0.0

  17. Some cards are recognized differently from the settings in the Suprema Smart Card option. Versión afectada: 1.4.1

¿Fue útil esta página?