Book Creator
 Add this page to your book
Book Creator
 Remove this page from your book  

 Manage book (0 page(s))
 Help

This is an old revision of the document!

Version 1.4.3 (V1.4.3_250602)

Release

2025-06-04

  • The XP2-MAPB-H model cannot downgrade to firmware version v1.4.3 or lower.
  • The XP2-GKDPB model with hardware v1.2.0 or higher cannot downgrade firmware to lower than v1.4.3. The hardware version can be checked in the DEVICE menu of BioStar 2.
  • Devices with the new BLE chip cannot downgrade to a lower version after upgrading the firmware to v1.3.1 or higher. Devices with existing BLE chips can be downgraded to a lower version.

For more information, check the serial number of the device and contact the Suprema (https://supremainc.com).

New Features and Improvements

1. Added new model.

  • XP2-MAPB-H

2. Supports Keypad Backlight configuration.

  • XPass 2 (XP2-GKDPB) hardware v1.2.0 or higher, firmware v1.4.3 or higher.

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

  • DESFire EV3

4. 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

5. 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.
6. Supports not logging events when the Ignore Repeated Signals Duration feature is activated.


Bug Fixes

1. 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. (Affects version: v1.4.1)
2. 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. (Affects version: v1.4.1)
3. When authentication is successful using the Secondary Key, and the Secondary Key is then set to Not Use, authentication fails even if the Primary Key is valid. (Affects version: v1.0.0)
4. Authentication fails with a 'period expired' message when using a smart card issued with a visual face included. (Affects version: v1.0.0)