Skip to content

Changelog for the firmware of
ID-engine Z & ACCESS200 (firmware ID 1100)

Versions available for download

You can download the current stable versions, each in the latest bugfix version, as well as selected legacy versions. Other versions are available on request.

Changelog

2.10.06 (2025-02-07)

Bug fixes

  • USB readers stopped responding when they were registered several times, i.e. in the BIOS and in the actual operating sytem. This is e.g. the case if the boot sequence has been changed in the BIOS so that USB sticks are booted first.

    Attention: This fix is not included in versions 2.11.xx to 2.12.xx.

  • FeliCa cards sending 16-byte instead of 8-byte responses couldn't be read using VHL or Autoread.

    Attention: This fix is not included in versions 2.11.xx.

  • In rare cases, a reboot occurred when VHL.ExchangeAPDU was executed on a card whose recognized type doesn't support this command.

    Attention: This fix is not included in versions 2.11.xx.

2.10.05 (2024-12-10)

Bug fixes

  • If a reader was configured to read the UID or a programmed card number from a file of a MIFARE DESFire card that returns random IDs, it would read the same card repeatedly.

  • On ID-engine Z product variants 10117-xxx-xx and 12117-xxx-xx, it wasn't possible to access a MIFARE DESFire card that returns random IDs. As a result, the reader could neither read a programmmed card number from a file nor the real UID via Autoread.

  • The UID of a MIFARE DESFire EV1 card that returns random IDs couldn't be read.

  • ConfigCards were read repeatedly when they remained in the reader's antenna field.

Attention: These fixes are not included in versions 2.11.xx.

2.10.03 (2024-11-07)

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.

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

  • 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 was'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.

2.07.02 (2024-07-01)

Features

  • Added support for ID-engine Z variants 10126-xxx-xx.

  • Added support for an expert Autoread configuration component that is available upon request.

  • Activated power-saving measures for the following readers operating in Autoread mode:

    • ISO/MIFARE readers
    • LEGIC reader variants 10117-xxx-xx, 12117-xxx-xx, and 10119-xxx-xx
  • On ISO 15693-based cards, you can now read block numbers above 256 using VHL and low-level commands.

Bug fixes

  • On ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx, firmware uploads in BEC2 or BF3 format via virtual COM port failed.

  • Presenting a Cotag card for 10 seconds or more could cause the card to be read several times.

  • The Iso15.GetUIDList low-level command no longer worked.

  • Several boot statuses were incorrectly categorized as hardware errors, although they actually only require a firmware upload or reader reboot.

2.06.06 (2024-06-05)

Features

  • When a support request is sent from the Mobile ID app, additional information about the reader hardware and firmware is now included in the app log attached to the request.

Bug fixes

  • Mobile ID stability and reactivity improvements

2.06.03 (2024-02-08)

Bug fixes

  • On ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx, firmware uploads failed occasionally.

    Attention: This fix is not included in versions 2.07.xx.

  • The reader's response to a Mobile ID app was delayed in the following cases:

    • Non-Mobile ID Bluetooth devices were present in the reader's close range.
    • The Mobile ID app was installed on an iPhone, and this device had been present in the reader's range for approx. 20 minutes.
    • NFC was enabled on the phone (in this case, delays occurred only occasionally).

  • In rare cases, the reader terminated and re-established the Bluetooth connection to a phone with an active Mobile ID app immediately after it was presented.

2.06.02 (2023-07-26)

Features

  • Added support for BALTECH Mobile ID (Beta). With Mobile ID, you can use smartphones to interact with BALTECH readers as an alternative to physical ID cards. During beta, the app is available for Apple iPhones; the Android app will be available for the official release.

    Beta testers welcome! If you're interested, get in touch.

  • Activated power-saving measures to significantly reduce the reader's power consumption. These measures have no impact on the reader's behavior. The specific savings depend on the card type used.

  • The HID Prox number format CardNumberLeftAdjusted has been added.
    For more details, refer to the HidProxSerialNrFormat configuration value.

2.05.00 (2023-03-03)

Features

  • On readers operating in Autoread mode, you can now disable individual maintenance functions cards, e.g. LicenseCards or ConfigCards, or maintenance functions via the NFC interface. To do so, you can use the new configuration value MaintenanceFunctionFilter.

  • Using the new Lic.ReadLicCard command, you can now read and evaluate LicenseCards, even if the reader doesn't operate in Autoread mode.

  • When a LicenseCard is presented, but that license type is not supported by the reader hardware or firmware, the reader now emits a specific signal pattern.

  • On ACCESS200 readers equipped with a Prox license for HID Prox, Indala, or Keri cards, the Wiegand interface is no longer disabled.

  • Added support for configuration files in BEC2 format that are exported from ConfigEditor without a reader connected to the PC.

    Note: This export functionality is only available in certain custom ToolSuite versions.

  • Activated power-saving measures for the RF antenna to significantly reduce the reader's power consumption. These measures have no impact on the reader's behavior. The specific savings depend on the card type used.

Bug fixes

  • When the block size of an ISO 15693 card is changed using a static VHL file, this changed block size is no longer implicitly applied when subsequently accessing the card using a different static or dynamic VHL file. In addition, you can now change the block size when creating a dynamic VHL file with VHL.Setup.

2.03.08 (2024-07-26)

Bug fixes

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

Attention: These fixes are not included in versions 2.05.xx to 2.07.xx.

2.03.07 (2024-05-23)

Bug fixes

  • Since v1.25.00, programmed card numbers couldn't be read from processor cards (e.g. NXP SmartMX) with DESFire emulation using Autoread.

  • ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx no longer booted when configured for OSDP.

    Attention: This fix is not included in versions 2.05.xx to 2.06.xx.

2.03.06 (2023-09-22)

Bug fixes

  • ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx operating in Autoread unidirectional communication mode via serial interface (RS-232/UART) couldn't be switched to BRP protocol e.g. in order to perform a firmware or configuration update.

    Attention: This fix is not included in versions 2.05.00 to 2.06.02.

2.03.05 (2023-03-15)

Bug fixes

  • ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx failed to read HITAG 1/2/S, EM4205, and Cotag cards after approximately 7,000 readings since v2.03.03.

  • On ID-engine Z product variants 10115-901-01 and 10117-901-01 running v2.03.03, firmware updates failed, rendering the device permanently defective.

    Attention: This fix is not included in version 2.05.00.

  • On ID-engine Z product variants 12115-xxx-xx and 12117-xxx-xx, multiple and incorrect readings of HITAG cards could occur since v2.03.03.

    Attention: This fix is not included in version 2.05.00.

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)

Features

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

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

2.01.01 (2022-08-12)

Features

  • Added support for the ID-engine Z product variants 10115-901-01 and 10117-901-01.

Bug fixes

  • Improved VHL status codes for the commands VHL.ExchangeAPDU and VHL.ExchangeLongAPDU.

  • When reading a MIFARE Classic emulation on a DESFire EV3-C card using VHL.Read, a subsequent VHL.IsSelected failed. As Autoread configurations run VHL.IsSelected internally, this bug could cause an Autoread operation to be aborted.

  • The VHL feature for prioritizing card families didn't work with cards returning random IDs.

  • Permissions for external SAM access and authentication commands used to be managed via the same bit in the access condition bit mask. To allow for more granular permission management, 2 separate bits are now used.

  • When a LicenseCard SE was presented to a LEGIC reader, the reader would book a license although LEGIC readers generally don't support the required HID iClass SE Processor. Now, LEGIC readers no longer accept the LicenseCard SE, only the LicenseCard Standard, which is compatible with any BALTECH reader.

2.00.10 (2023-03-22)

Bug fixes

  • Under certain circumstances firmware uploads could fail, requiring the reader to be disconnected and reconnected to repeat the upload. Currently, only the internal production process is affected.

  • Downgrading a LEGIC reader firmware to version 2.00.09 or below using a BEC2 or BF3 file fails if the version you downgrade from loads SM-4200 OS v4.7.0.0 or above.

    Note: All reader firmware versions released so far load SM-4200 OS v4.4.0.0 or below. Thus, this bug will only take effect when a reader firmware version to be released in the future loads SM-4200 OS v4.7.0.0 or above. Then, downgrading from that reader firmware version to version 2.00.09 or below using a BEC2 or BF3 file will fail.

Attention: These fixes are not included in versions 2.01.xx.

2.00.09 (2022-08-08)

  • Updated LEGIC SM-4200 OS to 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.

2.00.08 (2022-04-13)

Bug fixes

  • In rare cases, a firmware update could cause Bluetooth to stop working, indicated by the Bluetooth boot status being set. Subsequent updates to firmware versions below 2.00.08 terminated with an error, although the firmware was deployed correctly. This error state could only be left by upgrading to firmware version 2.00.08 or above; downgrades to older firmware versions were then possible again.

  • Running VHL.Read after VHL.IsSelected resulted in an authentication error VHL_AUTH_ERR when the following setup was used:

    • Reader from the LEGIC product line
    • MIFARE DESFire EV1 cards

2.00.07 (2022-03-02)

Features

  • Added support for the new BEC2 file format for configurations. This allows you to use wireless upload, create ConfigCards in BALTECH Uploader, and package configurations with a firmware.

  • Added support for emulating an ISO 14443-4 card with a reader. For this purpose, the Iso14CE command group is used. This allows you to use a reader as a transfer reader for wireless upload in BALTECH Uploader.

  • Added support for uploading BEC2 configuration files via NFC. This allows you to use wireless upload in BALTECH Uploader.
    The firmware also supports NFC upload apps for mobile phones to be developed in the future.

  • To protect a reader with a configured RFID interface against unauthorized firmware updates, the new configuration value Device / Run / DenyUnauthFwUploadViaBrp has been introduced: If this value is set, the reader blocks the upload of a firmware in BF2/BF3 format, i.e. a firmware can only be uploaded if it's packaged with a newer version of the configuration deployed to the reader (alternatively, a factory reset can be performed).

  • If the reader firmware is incomplete after a failed firmware update, you can now still perform a factory reset. This ensures the reader won't be left in a corrupted state if a firmware update has been aborted due to an RFID interface configuration that has the Device / Run / DenyUnauthFwUploadViaBrp bit set (see previous bullet point).

  • Incomplete firmware no longer returns a special ID (1053 for USB readers, 1075 for Ethernet readers), but the ID and version of the firmware you tried to upload. Thus, you can infer to the intended firmware state after an aborted update. So that you can still recognize when a firmware is incomplete, Sys.GetBootStatus now returns the new boot status IncompleteFirmware.

  • Added support for setting a bus address via NFC (implementation in our software tools is planned). Setting a bus address will be permitted either in the course of uploading a BEC2 file or when the reader housing is open (i.e. a tamper alarm is triggered).
    For very high security requirements, the new parameter GreaterVersion (see Device / Run / AuthReqUploadViaBrp and Device / Run / AuthReqUploadViaIso14443) can be set: Then, the bus address can only be set if a newer version of the existing configuration is deployed. This ensures that the bus address can't be changed arbitrarily by deploying the same configuration version again.

  • Added support for retrieving reader information via NFC (implementation in our software tools is planned).

  • Added support for MIFARE DESFire EV3.

  • Added VHL.Read and VHL.Write support for MIFARE Ultralight, Ultralight-C, and Ultralight-EV1 cards.

  • Added low-level commands for encrypted communication with Ultralight-C and Ultralight-EV1 cards:

  • Added an alive check for keypad components to further increase reliability of ACCESS200 keypad readers.

  • Increased the timeout for VHL.ExchangeAPDU to 60 seconds to cater for complex crypto operations.

  • LEGIC readers with security module SM-4500 are supported now.

  • You can now check if your reader's LED can be customized: If yes, Sys.GetFeatures will return the feature ID RgbLed or RgbLedLimited respectively.

  • Changed the default setting for OSDP: By default, the reader now uses SCBK-D without diversification.

  • OSDP now supports a tri-color LED (red/green/blue).

  • Added the OnPinEntry event, which is fired when a PIN code has been entered via the keypad. Now you can configure a custom action, e.g. to give visual or acoustic feedback when PIN entry is completed.

  • The SNET protocol now supports DKR readers.

  • You can now configure an individual transition time for each VLED definition .

  • Added support for MIFARE Plus values in security level 3. For this purpose, the Mif.ValueSL3 command has been added.

  • Added support for NXP AV3 SAM ( low level and VHL commands)

  • Added support for the following card types:

  • For readers that support OSDP, Sys.GetFeatures will now return the feature ID OsdpV217.

  • When you use LED customization to illuminate only 1 side of an ACCESS200 housing, the LEDs on the other side will be disabled.

Bug fixes

  • When a programmed card number (PCN) was truncated via the host interface component for virtual COM port undirectional, RS-232/UART undirectional, or keyboard emulation, it was truncated at the end. Now it's truncated at the front.

  • The I/O port protocol, which e.g. allows you to use a UART pin as a GPIO, wasn't supported by ID-engine Z.

  • Reading an ISO 14443 type A card without an iClass container was very slow if the reader configuration contained Autoread components for both iClass and ISO 14443 type A.

  • When setting beeper off time to 0 via the OSDP command osdp_BUZ, the beeper was still on after command execution. Now, the beeper is switched off afterwards.

  • LEGIC readers could hang if an ISO 15693 or ISO 14443 card was presented at the edge of the antenna field.

  • VHL.Select handled random IDs returned by Felica and ISO 14443 type B cards incorrectly: The command returned the card multiple times, each time as a new card with a new ID, even if the Reselect parameter was set to false. Now, the card is returned only once as long as it remains in the antenna field.

  • On MIFARE Plus S and MIFARE PLus L3 cards, authentication with SAM key only worked with SAM key 0.

  • Combo cards MIFARE DESFire/Classic were occasionally not detected.

  • Desfire.GetDfNames only worked when there was 1 application programmed onto the card.

  • Desfire.Authenticate terminated in an error.

  • VHL.IsSelected didn't work with FeliCa cards.

  • Since version 1.21.00, OSDP authentication was still possible with SCBK-D after installing SCBK.

  • LED signalization during AdrCard, ConfigCard, or LicenseCard presentation wasn't correct if a VLED transition time was configured.

  • Updating the reader via OSDP protocol did not work since version 1.05.00.

  • Reintroduced Iso14a.TransparentCmdBitlen. In rare cases this is still needed.

  • WTX was not supported by ISO 7816 T=1 protocol.

  • Encoding conversion, e.g. used by certain Autoread components in BALTECH ConfigEditor, didn't work properly when the data to convert had been cut out of the original data stream.

  • To enhance security, manipulation on the software level via the RFID interface now triggers a tamper alarm. This includes, e.g. the use of a ConfigCard, an AdrCard, or a wireless upload via NFC.

  • If deploying a configuration via Sys.GfgLoadBlock was blocked by the reader due to missing permissions, the reader returned the error Sys.ErrCfgAccess, which suggested an issue with the memory. Now, the error ErrAccessDenied is returned.

  • The timeout for SAM detection has been reduced to speed up initialization.

  • When a Prox license is missing, the low-level commands HID.ProxRead, HID.Prox32Read, and HID.IndalaRead now return the new error code HID.ErrLicense.

  • Unencrypted configurations can now only be deployed to legacy devices for which this is a requirement.

  • For MIFARE DESFire EV1 cards, read reliability has been improved for slow card presentation.

  • On ID-engine Z readers, handling multiple cards presented at the same time (anti-collision) resulted in an error for certain combinations of ISO 14443 Type A cards.

  • Minor bugs in LED customization feature fixed.

1.25.00 (2020-08-18)

Features

  • Added a Sum command to conversion rule templates. You can use it to calculate the sum of several bytes, e.g. to generate a checksum of the number read from a card.

1.23.01 (2020-08-07)

Bug fixes

  • Since version 1.23.00, HID Prox and Indala cards no longer worked with the Wiegand protocol on ACCESS200 readers manufactured before 2020-06-01.

1.23.00 (2020-07-19)

Features

  • Added a feature to identify a reader connected via RS-232/UART or virtual COM port and running in unidirectional communication mode. When you send a ? to such a reader, it now returns a string containing the constant prefix BALTECH Reader, followed by its firmware version and serial number.
  • The command Sys.GetFeatures now indicates HID iClass support if an HID iClass SE Processor is available.
  • Implemented the new Prox license model for HID Prox, Indala, and Keri cards. To equip affected 125 kHz readers with licenses yourself, you can order a BALTECH LicenseCard. To check a reader for an existing license, use the new Sys.GetLicenses command.

Bug fixes

  • When running VHL.Format on a MIFARE card, and a block writing error occurred due to incorrect access conditions, the command was canceled.
  • Since version 1.13.00, errors could occur when accessing ISO 15693 cards.
  • If the MIFARE emulation on a SmartMX platform was accessed first, subsequent ISO 14443-4 access attempts led to an error.
  • VHL HITAG 2 block access didn't work.

1.21.03 (2020-06-19)

Bug fixes

  • VHL.Read could only read TTF cards if the configurable TTF decoder was configured. If the default ScanCardTypesPart1 and ScanCardTypesPart2 settings were used instead, the 125 kHz plugin returned VHL.ErrConfig and card reading stopped.
  • Running VHL.IsSelected with EM 4100 cards resulted in sporadic misreads.
  • VHL.IsSelected sporadically failed to read 125 kHz cards. To improve reliability, an automatic retry for 125 kHz card types has been added.

1.21.00 (2020-05-11)

Features

  • Added optional card removal detection mode to Autoread. You can now configure the reader to send a message to the host and/or perform other actions (e.g. switch an LED), whenever it detects that a valid card has been removed.
  • Added VHL support for Cardax cards.

Bug fixes

  • The ISO14443A transparent command didn't work if EnMifBwProt (MIFARE backwards compatibility protocol) was enabled.
  • For MIFARE Classic cards, the VHL key list wasn't completely processed if a block read/write error occurred.
  • Read/write problems with ISO 15693 cards have been fixed.
  • The default configuration values for OSDP secure mode and OSDP data mode have been changed.

1.20.00 (2020-03-23)

Features

  • Added RGB-LED support for ID-engine Z
  • Added further RGB functions:
    • Smooth activation/deactivation of RGB colors
    • Signals pulsing continuously between 2 RGB colors
    • Virtual LED definitions that allow RGB colors to be activated via BRP commands or BALTECH script
    • User Interface (UI) commands for controlling LEDs and beeper

Bug fixes

  • Red and green LEDs resulted in light green when activated simultaneously. Now, the result in yellow as the intensity of the green LED has been reduced.
  • An empty blacklist rejected all cards.
  • HITAG 2 labels couldn't be selected in password mode

1.18.00 (2020-03-19)

Features

  • Added alternative data area for number comparison in black-/whitelist

Bug fixes

  • VHL.Read EM4205/4450 used wrong configuration values

1.17.00 (2020-03-06)

Bug fixes

  • Minor corrections for OSDP with encryption

1.16.00 (2020-02-26)

Features

  • Final release for OSDP with encryption
  • Bus address setup with BALTECH AdrCard is now also possible for an already installed reader (tamper switch closed) as long as no project settings are deployed.

Bug fixes

  • SAM access to invalid slot causes a reader to reboot.

1.15.00 (2020-02-05)

Features

  • Color and intensity of ACCESS200 LEDs are individually configurable now.
  • Raw serial-over-CDC protocol can't be disabled accidentally any more.

1.14.00 (2019-12-18)

Bug fixes

  • In presence of a strong external interference signal, the keypad could become unresponsive.

1.13.00 (2019-11-21)

Features

  • It's possible to lock the factory reset feature for a certain Security Level via the configuration file (BEC) or BALTECH ConfigCard.
  • Added the Sec.GetCurAcMask command.

Bug fixes

  • A keypress on an ACCESS200 reader could cause a USB communication failure.

1.12.00 (2019-11-06)

Bug fixes

  • After a software reset, the keypad and LED control of an ACCESS200 reader could be out of order.

1.11.00 (2019-10-31)

Bug fixes

  • The reader firmware could hang when sending a message to a host via read-only (e.g. Wiegand, keyboard emulation) or bus protocol (e.g. OSDP). This could result in an unresponsive keypad.
  • Under specific conditions, sending constant Wiegand data could cause the firmware to enter an endless loop.
  • The command VHL.CheckReconfigErr always returned false even if reconfiguration via BALTECH ConfigCard failed.

1.10.00 (2019-10-09)

Features

Bug fixes

  • OSDP: Wiegand raw data was sent without parity bits.

1.09.00 (2019-09-30)

Bug fixes

  • OSDP: Wiegand raw data was sent without parity bits.

1.08.00 (2019-08-29)

Bug fixes

  • ISO 15693 block length was restricted to 16 bytes. Now it supports up to 64 bytes.
  • HTG 1/S write command contained an error.

1.07.00 (2019-07-30)

Features

  • Card emulation NFC-A is supported now.
  • VHL.Setup and VHL.Write support for inter-industry cards added.

Bug fixes

  • On presentation of multiple ISO 14443A cards, sporadic reading problems could occur. This affected LEGIC readers only.
  • Sys.GetFeatures didn't return the feature IDs of EM4205 and EM4450.
  • The BLE alert service could overwrite the signalization of the blue LED even if this service wasn't used by the BLE host.
  • VHL.IsSelected didn't work with ioProx, Pyramid, and ISO15693 cards that had a block length of 32 bytes.

1.06.00 (2019-05-09)

Features

  • Card data format in OSDP replay messages is now adjustable.
  • BALTECH AdrCard supports address 0 now.

Bug fixes

  • 13.56 MHz card types couldn't be read anymore after executing security-based host commands.
  • LED signalization during BALTECH ConfigCard presentation wasn't correct.
  • HID iClass card presentation could cause the reader to reboot.

1.05.00 (2019-03-22)

Features

  • Wiegand allows sending frames of any bit number now.
  • Sys.GetFeatures returns supported host protocol encryption (AES, PKI) now.
  • Updated LEGIG SM-4200 firmware to OS V4.3.1.0.
  • Added new configuration value VhlCfg / File / LegicApplicationSegmentList, which is the basis for a Legic VHL file definition. It replaces the former value VhlCfg / File / LegicSegmentListLegacy, which is marked as deprecated now as it isn't supported by our SDK.
  • Added support for reading iClass card numbers with ID-engine Z Legic readers equipped with an SM-4200M (ISO 15693-based iClass cards only - no iClass SE/Seos).
  • Bluetooth transmission power can be adjusted via configuration now.
  • Added new Legic low-level command dispatcher, which currently only contains the transparent Command for direct communication with the SM-4x00. This dispatcher replaces the Lga dispatcher, which is marked as deprecated now as it isn't supported by our SDK.
  • Added 3 new ISO 15693 low-level commands: TransparentCmd, WriteMultipleBlocks, and ReadMultipleBlocks. These commands replace the commands 0x2105, 0x2106, and 0x2120, which were marked as deprecated as they aren't supported by our SDK.
  • Added VHL.ResolveFilename,
    which allows you to address VHL files via name instead of index. We recommend to follow this approach for new projects.
  • Readers now scan for BALTECH ConfigCards even when not adding ISO14443/A to Project / VhlSettings / ScanCardFamilies explicitly. In the latter case; ISO14443/A cards aren't processed by the Autoread Rules at all (it is only checked if they are BALTECH ConfigCards and transferred to the readers configuration if so). For the rare case that non-ISO14443/A ConfigCards are needed, a new configuration setting was introduced: "Project.VhlSettings.ConfCardFamily"
  • The serial communication interface (RS-232/UART) supports 7-bit data frames now (7N1, 7E1, 7P1).
  • Ultralight low-level commands added

Breaking Changes

  • Deprecated ISO15693 commands (command code 0x20XX) were removed. To execute low-level ISO15693 commands, use the Iso15 command group instead (as recommended for all current products).

Bugfixes

  • Sys.GetFeatures could indicate MIFARE Classic/Plus support for LEGIC readers erroneously.
  • Under specific conditions, sending constant Wiegand data could cause the firmware to enter an endless loop.
  • BCC-16 checksum in BRP response frames was incorrect in case of BRP over HID communication.
  • Problems occurred when reading ISO14443-4-compatible cards with an ID-engine Z LEGIC reader.
  • VHL Select didn't scan for 125 kHz cards after card analysis was done in ID-engine Explorer.
  • GProx is supported for any bit length now.
  • AWID supports any bit length now.

1.04.00 (2018-10-11)

Features

  • ACCESS200 reader platform is supported now.

Bug fixes

  • Reader configurations which operate on the Rawserial protocol using the second serial interface (Channel1) not only activate the RS-232/UART interface on ID-engine Z, but also the Rawserial over CDC communication channel now.

1.03.00 (2018-09-21)

Bug fixes

  • With the ISO14443 A stock configuration it could sporadically happen that cards weren't recognized any more after some time.

1.02.00 (2018-09-18)

Features

  • Reader configurations originally created for ID-engine SD readers which operate on the Rawserial protocol using the second serial interface (Channel1) are compatible with ID-engine Z readers now. The card number is sent unidirectionally to the host via the RS-232/UART interface of the ID-engine Z reader.

Bug fixes

  • During communication over the serial interface (RS-232/UART), single BRP commands could occasionally fail. The reader received or sent an incorrect BRP frame in this case.
  • Improved reading of EM4450 tags
  • Added ISO 15693 labels with option flag 1
  • ISO 15693 low-level write command: error codes: detail degree of status codes improved

1.01.00 (2018-09-14)

Features

1.00.00 (2018-09-10)

  • Initial release
Title