Known issues in BALTECH ToolSuite

BALTECH ToolSuite consists of the tools ID-engine Explorer, ConfigEditor, and Uploader. Here, you can find the known issues in the latest versioncall_made.

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.

ID-engine Explorer

Analyzing a MIFARE card with a LEGIC reader causes ID-engine Explorer to freeze

Details

Issue
When you try to analyze a MIFARE Classic or DESFire card using a LEGIC reader, ID-engine Explorer freezes and shows the error message Problem encountered including a bug report.

Workaround
Use an ISO reader instead of a LEGIC reader to analyze the card. ISO readers are identifiable by a serial number starting with 10115.

Using the Test Configuration feature in ConfigEditor might cause ID-engine Explorer to crash

Details

Issue
When you click Test Configuration in ConfigEditor to open a configuration in ID-engine Explorer, ID-engine Explorer might crash after loading the configuration.

Workaround:
Re-open ID-engine Explorer manually. You can then test the configuration as normal.

Factory reset of a USB-HID reader might cause ID-engine Explorer to crash

Details

Issue
When you try to factory reset a reader connected via USB-HID, ID-engine Explorer might crash.

Workaround:
This issue occurs on specific computers only. Please try on a different computer.

Factory reset of an Ethernet reader might cause ID-engine Explorer to freeze

Details

Issue
When you factory reset an ID-engine XE reader, ID-engine Explorer might display the following error message after a few seconds: Error occurred: Command execution exceeded timeout. When you confirm the error message, ID-engine Explorer freezes.

Workaround
Despite freezing, ID-engine Explorer does complete the factory reset. You can close ID-engine Explorer via Windows Task Manager and then reopen it if necessary.

After factory-resetting an Ethernet Reader, ID-engine Explorer might fail to reconnect

Details

Issue
After factory-resetting an ID-engine XE reader, ID-engine Explorer might fail to reconnect to the reader. You'll see the following error message: Error on device access. Cannot connect to device: Device (TCP/IP-Device with S#=serial number) cannot be found.

Workaround
Despite this error message, the factory reset has successfully been performed. If necessary, you can manually reconnect by clicking Disconnect Reader in the bottom right and reselecting the reader.

Factory-resetting an Ethernet reader without authentication might fail

Details

Issue
Factory-resetting an ID-engine XE reader fails if all of the following applies:

  • The Ethernet standard configuration 00000-0000-1036-03 is currently deployed to the reader.
  • The reader is connected via its network port.
  • The reader is connected without authentication, i.e. you didn't load the the respective certificates into ID-engine Explorer.

In this case, you'll see the error message ERR_ACCESS_DENIED, and the factory reset is not performed.

Workaround
To perform the factory reset, please connect the reader in maintenance mode and try again.

Note: Once the factory reset is completed, you'll see the error message Error on device access. Cannot connect to device: Device (TCP/IP-Device with S#=serial number) cannot be found. Despite this message, the factory reset has successfully been performed. If necessary, you can manually reconnect by clicking Disconnect Reader in the bottom right and reselecting the reader.

Connecting to a reader via RS-232/virtual COM port might cause ID-engine Explorer to crash

Details

Issue
When you try to connect a reader to ID-engine Explorer via RS-232/virtual COM port, ID-engine Explorer crashes in the following cases:

  • The reader is configured for BRP and a boot status is set.
  • The reader is configured for unidirectional communication ("RawSerial"), and returns upper-case letters.

Workaround:
If you experience this issue, please get in touch with us.

ConfigEditor

Custom Length option might not work in Autoread UID forms

Details

Issue
In Autoread UID forms, the option Custom Length of Output Data doesn't work if you specify a length that is smaller than the original UID. The number you actually receive will not match the specified length.

Workaround:
If you experience this issue, please get in touch with us.

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.