Skip to content

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.

Download 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

ID-engine Explorer

Draft configurations are displayed as version 01

Details

Issue
When you deploy a draft configuration to a reader, ID-engine Explorer displays it as version 01.

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

ConfigEditor

"Autoread All UIDs" produces unexpected iClass/HID Prox UIDs on ACCESS200 iClass readers

Details

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.

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

Uploader

Details

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

Workaround:
Connect the reader to a DHCP network and restart the firmware update.

Changelog

4.26.08

ID-engine Explorer

When testing sample cards, the display refreshes more quickly
Details

When you test sample cards in the Basics tab of ID-engine Explorer, the display now refreshes more quickly when a card is removed.

ConfigEditor

New deployable file format
Details

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:

To get a BEC2 file, enable the option [Support Legacy Firmware Versions] (../project-setup/create-new-config.md#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
Details

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
Details

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.

Customize LED
Details

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
Details

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 Encryption & Authentication no longer included by default
Details

The component AES Encryption & Authentication (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.

Usability improvements
Details
  • 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.

Uploader

Wireless Upload via NFC
Details

Upload a configuration (or a configuration packaged with a firmware) using Wireless Upload via NFC.

Requirements:

Create ConfigCard
Details

Create a ConfigCard in Uploader using a deployable configuration file.

Requirements:

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

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

Details

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.

Back to top