Changelog & known issues for BALTECH ToolSuite
BALTECH ToolSuite consists of the tools ID-engine Explorer, ConfigEditor, and Uploader. Here, you can find the changelog as well as the known issues with the latest version.
If you're experiencing an issue in an older version, please update first to get the latest bug fixes. To report a new issue in the latest version, please get in touch.
Known issues in latest version
Draft configurations are displayed as version 01
When you deploy a draft configuration to a reader, ID-engine Explorer displays it as version 01.
There's currently no workaround. It may be a bit confusing during testing; however, you're on the safe side if you stick to the workflow we generally recommend: Use draft configurations for testing only, and only use released versions for productive deployment.
"Autoread All UIDs" produces unexpected iClass/HID Prox UIDs on ACCESS200 iClass readers
Issue ACCESS200 iClass readers (article numbers 10097-621-xx) configured with the Autoread All UIDs component produce different UIDs for iClass and HID Prox cards than with factory settings.
To get the same UIDs as with factory settings, please remove the Autoread All UIDs component from your configuration and add the Autoread UID component for iClass or HID Prox respectively.
Importing a host interface component may overwrite the configuration name
When you import a host interface component into a configuration that doesn't have an RFID interface component, the Name in Administrative Information will be overwritten with the name of the host interface component.
Manually change the name back to the desired one.
Ethernet firmware update in maintenance mode leaves reader in corrupted state if link-local address is used
When you connect an Ethernet reader in maintenance mode to a computer, the reader will obtain its IP address via link-local in most cases. If you then start a firmware update, the update process will abort after a few seconds. You'll get the following error message: Driver internal problem. Reader disconnected. The aborted update leaves the firmware in a corrupted state, i.e. the reader functionality is no longer available.
Connect the reader to a DHCP network and restart the firmware update.
- Analyzing the card structure of a MIFARE DESFire card works more stable now.
- Several stability improvements
When invoking Uploader from a custom application, you no longer need to specify the reader's serial number if only 1 reader is connected.
You get better guidance if a firmware upload has failed.
Several help texts and labels have been improved.
Redesigned start screen
- The start screen now provides an overview of all features, alongside the main reader info.
- The features for testing the reader and configuration are no longer shown in individual tabs, but in dialog windows.
- You can now conveniently open ConfigEditor and Uploader from ID-engine Explorer.
- You can now see if your reader supports Bluetooth.
Testing an Autoread configuration enables Autoread on the reader
You no longer need to manually enable Autoread when testing an Autoread configuration.
Autoread Wizard puts together all the components you need
The new Autoread Wizard helps you set up your configuration for autonomously reading a number: Select your host interface, card type, and the type of number to read. All required components will then be added to your configuration.
A workflow overview guides you to your ready-to-deploy config
- The new workflow overview guides you through the steps of config completion, testing, and release.
- For released configurations, the workflow overview shows you all the options you have (e.g. create a new version or a ConfigCard).
- To make room for the workflow overview, the ConfigEditor layout has been adapted: e.g., the list of components is now at the top right, and the Add button is now a Plus icon.
BEC2 is now the default format for deployable configuration files
With v4.26, we introduced the new file format BEC2 for deployable configuration files, in addition to the existing file format BEC. BEC2 supports additional features such as Wireless Upload, but requires readers with firmware 1100 v2.00 or above. As of v5.00, BEC2 is the default format for new configurations. For compatibility with older firmware, you can change back to BEC at any time.
Hints are now easier to find
Question mark icons now indicate when hints with additional info are available.
Autoread configurations can now be tested right in ConfigEditor
You no longer need to switch to ID-engine Explorer to test your Autoread configuration. The same test functionality is now available in ConfigEditor.
New configuration components
The following RFID interface components have been added:
- ISO 14443 Type B - Autoread UID
- FeliCa - Autoread Number in Block
Improved configuration components
- If your MIFARE DESFire, Classic, and Plus card returns random IDs, you no longer need to use the special component Autoread UID with Authentication. Instead, the standard Autoread UID components for these card types include the option Card Returns Random ID. Here, you can specify an encryption key that lets you access the card's real UID.
- MIFARE DESFire VHL File now supports backup files.
- In the host interface component for Wiegand, the beeper is now by default enabled, i.e. the reader will beep as soon as a corresponding signal is sent by the host. This matches the new factory settings for ACCESS200 readers.
Host interface components now ask for your operation mode to help you make the right settings
The operation mode you choose for your readers determines whether or not to configure the RFID interface and how to control feedback to the card holder (i.e. beeper and LED). As some host interfaces (e.g. USB-HID) support various operation modes, the respective components now ask for your operation mode, so ConfigEditor can better guide you to a valid configuration.
Saving an existing configuration no longer asks for a filename and path
- Only Save As will now ask you for a filename and path.
- When you change the configuration name, ConfigEditor adapts the filename accordingly when you next save the configuration.
Improved help texts, error messages, and labels
Various help texts, error messages, and labels have been rewritten or added to provide better user guidance. Where further info may be useful, you can now find links to the respective topic in the online docs.
Connecting a reader to a ToolSuite application is now easier
- You can now see which of the readers connected to your computer are currently used by other applications and thus can't be selected.
- A USB reader configured for virtual COM port is no longer listed as 2 different devices, but only once as a USB device.
New app icons
Since this is a new major release, it was about time to give the app icons a new design as well. We hope, you like them. :-)
When testing sample cards, the display refreshes more quickly
When you test sample cards in the Basics tab of ID-engine Explorer, the display now refreshes more quickly when a card is removed.
New deployable file format
When you export a configuration for deployment, you can now optionally save it in BEC2 format. With this format, you can make use of the following new features:
- Wireless Upload via NFC in BALTECH Uploader
- Create ConfigCard in BALTECH Uploader
- Package configuration with firmware
To get a BEC2 file, enable the option Support Legacy Firmware Versions.
As BEC2 files are only supported by readers with the latest firmware version 1100 v2.00, the default format is currently still BEC, which is supported by any firmware version.
Package configuration with firmware
Package your configuration with a firmware version to ensure consistent behavior across all readers. To do so, enable the option Package with Specific Firmware Version.
This only works if Support Legacy Firmware Versions is disabled.
New conditions for ConfigCard creation
To create a ConfigCard, you now need a ConfigCard v2. (This is what you'll automatically receive when ordering a ConfigCard as of now.) ConfigCard v2 is compatible with any configuration. The following alternatives apply:
- If Support Legacy Firmware Versions is enabled, you can also use an old ConfigCard.
- If Support Legacy Firmware Versions is disabled, you can also use a blank MIFARE DESFire card (EV1 or above).
For configurations packaged with a firmware, the firmware is not included on ConfigCards due to space limitations. To allow ConfigCard creation in Uploader, you can optionally also export a BEC2 file without the firmware.
With the new Customize LED component, you can now configure the LED behavior in detail: Pick from a wide color palette, adjust intensity, make LEDs pulse, or enable smooth transitions. To support color-blind users, you can optionally illuminate only the right or left side of the housing.
Enhanced support for MIFARE Ultralight
ConfigEditor now contains 2 new RFID interface components for MIFARE Ultralight cards:
- Autoread Number in Block to read a number programmed into the card's memory.
- VHL File to read or write to cards using our macro command set VHL.
AES Authentication and Encryption no longer included by default
The component AES Authentication and Encryption (in previous versions referred to as Security Settings) is only relevant in few projects and for SDK developers only. That's why it is no longer included in ConfigEditor by default, but available as a separate component that can be imported when needed.
- The Add menu (formerly Extend Configuration) has been restructured for better usability. E.g., components for card types are now listed in the submenu RFID interface and sorted by how commonly they're used.
Configuration components have been revised:
- There's now an individual component for each host interface.
- The operations Convert to Decimal, Remove Leading Zeros, and Define Length of Output have been moved from the Autoread components to the host interface components.
- The iClass Advanced component has been removed to simplify usage.
Many terms in the interface have been changed to more understandable ones, e.g.:
- Project settings becomes RFID interface
- Device settings becomes Host interface
- Finalize configuration becomes Release
- Important error messages have been reworded to be more helpful.
- The popup with the options New, Auto-Create, and Open, which was shown when starting ConfigEditor, has been removed.
Wireless Upload via NFC
Upload a configuration (or a configuration packaged with a firmware) using Wireless Upload via NFC.
- Transfer reader:
ID-engine ZB Brick, ISO/MIFARE product line (10115)
The LEGIC product line (10117) will not work.
- Target reader firmware:
- 1100 v2.00 or above
- Custom firmware originally created as of November 2021
Create a ConfigCard in Uploader using a deployable configuration file.
Deployable configuration file in BEC2 format.
The BEC2 file must contain a configuration only. A config firmware package can't be stored on ConfigCards due to space limitations.
New BALTECH ConfigCard v2 (This is what you'll automatically receive when ordering a ConfigCard as of now.) Alternatively, you can use a blank MIFARE DESFire card (EV1 or above).
- Reader to load configuration to the ConfigCard: ID-engine Z or ACCESS200
- Target reader firmware:
- 1100 v.2.00 or above
- Custom firmware originally created as of November 2021
Firmware-Upload via RS-232
Firmware files (BF2 file format) can now also be uploaded via RS-232. Previously, this was only possible via USB.
Remote Support as a separate tool
Remote support, which lets you grant BALTECH employees access to your computer for support purposes, is no longer integrated in BALTECH ToolSuite, but a separate application. It's available for download on our website.