Skip to content

Changelog & known issues for firmware 1100 v2.03

Known issues in latest bugfix version

We test all releases thoroughly via automated robotic end tests. Any issues that still occur in the latest bugfix version are listed below. If you're experiencing an issue with an older version, please first try the latest bugfix version. To report a new issue, please get in touch.

No issues currently known


2.03.03 (2023-01-17)

Bug fixes

  • The PC/SC interface couldn't be activated on the products 12115-xxx-xx and 12117-xxx-xx.

  • VHL.Select returned the error VHL.ErrApdu instead of VHL.ErrNoTag if the reader didn't have a required Bluetooth license. Now, the reader returns VHL.ErrNoTag as expected.

    Note: This bug only applies to custom products that run firmware v2.03.02 and on which the Bluetooth functionality needs to be activated via BALTECH LicenseCard.

2.03.02 (2022-12-23)

This version also includes all features and bugfixes of the stable version v2.01 up to and including v2.01.01.


  • Added support for the products 12115-xxx-xx and 12117-xxx-xx

  • For custom products, it's now possible to make the Bluetooth functionality activatable with BALTECH LicenseCard.

Bug fixes

  • Aborting a VHL.ExchangeAPDU for ISO 14443-4 Type A inter-industry cards resulted in an undefined state when the command was executed in continuous mode.

  • Updated LEGIC SM-4200 firmware to OS v4.4.0.0. This has improved read reliability, especially when used in metal environments with cards that have their antennas placed close to the edge.

  • Bluetooth Peripheral Advertisement was enabled on readers configured to read the UIDs of all supported card types. Now it's disabled by default and needs to be explicitly enabled via the reader configuration.

Back to top