Skip to content

Changelog for firmware 1100 v2.10

2.10.03 (2024-11-07)

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

Features

  • Added commands VHL.GetCardType and AR.RestrictScanCardFamilies. With these commands, you can use our recommended operation mode "VHL & Autoread" even without configuring readers.

  • Via keyboard emulation, it's now possible to create characters based on keyboard shortcuts including the Alt and Windows keys. (So far, only shortcuts including Ctrl, Shift, and AltGr were supported.)

  • Readers can now be configured to accept Mobile ID apps from multiple projects, e.g. at the main entrance of a multi-tenant building.

  • Added support for Mobile ID's new interaction mode Remote: Trigger from Distance. With this mode enabled in the reader configuration, users trigger the reader from a distance via the press of a button, typically to open parking lot barriers or other remote-controlled gates.

  • Added support for Mobile ID's new interaction mode Convenient: Leave in Pocket. With this mode enabled in the reader configuration, users don't need to present their phones to the reader, but can leave them in their pockets.

  • Detection of Mobile ID devices improved to achieve better reactivity.

Bug fixes

  • Since v2.00.07, OSDP stopped working approx. 1 hour after the last reader reboot.

  • Fixed sporadic aborts during firmware uploads on ID-engine Z product variants 12115-xxx-xx.

  • On ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx, a failed firmware update due to an invalid digital signature, which may e.g. indicate a corrupt or manipulated firmware file, is now reported back to the host explicitely with a new error code.

  • Readers crashed if the command AR.SetMode, VHL.Select, or Sys.HFReset was executed shortly (approx. less than 2 seconds) after connecting the reader to the computer.

  • CCID communication may have got stuck for approx. 1 minute when the card was removed during APDU exchange and/or when response messages were larger than 127 bytes.

  • Error and status messages transmitted in the header of a CCID message may have been incorrect.

  • If the ID of a Mobile ID app was changed while the app had an active connection to the reader, the connection could be blocked for approx. 30 seconds.

  • If both BALTECH Mobile ID and Mobile Card Emulation (MCE) were activated, the reader failed to read Mobile ID apps, MCE devices or any cards. A factory-reset. wasn't possible either.

  • When running VHL.ExchangeLongAPDU, the first response always had the ContinueResp parameter set to true, even if there was no more data to be transmitted.

  • In the ISO 7816-4 VHL file, the Data Start Position value wasn't applied correctly.

  • When running the VHL.ExchangeLongAPDU command, the total amount of data to transfer was limited to 200 bytes. Now you can transfer any amount of data, the size of which is only dependent on the dispatcher.

  • On reader variants 10115-xxx-xx, 10117-xxx-xxx, 10097-xxx-xx, and 10119-xxx-xx, firmware uploads may have failed if support for 125 kHz cards was activated.

Title