Skip to content

Switching from Reader Maintainer to BALTECH ToolSuite

When configuring readers for new projects or need to make config changes, we recommend you use BALTECH ToolSuite instead of Kofax Reader Maintainer (KRM).

Download ToolSuite

Why switch?

With ToolSuite as of v5.03, you can implement all common requirements for which you previously had to order a custom configuration, e.g.:

  • Improve MFP compatibility using alternative USB keyboard settings
  • Restrict operation to one or multiple card types
  • Read programmed card numbers, e.g. in a file, sector, or segment of the card
  • Enable BALTECH Mobile ID
  • Create ConfigCards for contactless updates

As KRM will no longer be updated, please only use it to configure replacement readers for legacy projects.

Feature overview

Get reader info & read sample card

Similar to KRM, the ToolSuite application ID-engine Explorer shows details about the connected reader.

Screenshot: See reader information in BALTECH ID-engine Explorer

You can also test a sample card to identify its type and UID.

Screenshot: Analyze sample card in BALTECH ID-engine Explorer

Detailed how-tos:

Customize reader

While KRM offers predefined stock solutions, the ToolSuite application ConfigEditor guides you step by step to create custom configurations — enabling also advanced use cases.

Screenshot: Option "Print Management" selected in Autoread Wizard in BALTECH ConfigEditor

Detailed how-tos:

General workflow

  1. Create a configuration: Open ConfigEditor, click Start Autoread Wizard, select Print Management, and complete the wizard.

    If readers are currently configured with a custom configuration, we recommend you create a new version of it. This lets you deploy the updated configuration via ConfigCard. Learn more

  2. Enter project-specific details as listed in the left column of Your Workflow.

    Screenshot: Example list of empty, mandatory configuration fields in a configuration in BALTECH ConfigEditor

  3. In Administrative Information, enable the checkbox Support Legacy Firmware Versions. This ensures that the configuration works also on older readers you may have in your project.

  4. Test RFID interface configuration and LED/beeper with ConfigEditor

  5. Transfer the configuration to the reader and run a test with your MFP.
  6. Release & export the configuration for productive deployment.
Workflow for keyboard emulation

Deploy configuration or firmware via USB

To deploy a configuration or firmware update as in KRM, use Wired Upload in the ToolSuite application Uploader.

Screenshot: Start Wired Upload to a connected reader in BALTECH Uploader

Detailed how-to:

Deploy configuration with ConfigCard

For contactless deployment to readers already installed, you can store the configuration on a ConfigCard.

Present a BALTECH ConfigCard to a reader to deploy a configuration

The individual steps depend on how readers are currently configured.

Unconfigured readers or readers with a KRM stock solution

For newly bought, unconfigured readers or readers currently running a KRM stock solution, you can usually deploy the configuration directly.

Detailed how-to:

  1. Create a ConfigCard containing the configuration you've created.
  2. Present the ConfigCard to each reader to deploy the configuration.
Exception: Some stock solutions must first be removed

The following stock solutions must first be removed:

  • HID Prox (type 138) / 37-bit card, 19-bit card number
  • ioProx (type 139) / site code and card number
  • EM4100-4102 (type 129) / reverse site code
  • Cotag (type 163)
  • Idteck (type 164)

To do so, create a ConfigCard with a reset configuration for your stock solution.

Detailed how-to

  1. Request a reset configuration for your stock solution.

  2. Create a ConfigCard containing the reset configuration.

  3. Create a second ConfigCard containing the new configuration.

  4. Present the ConfigCard with the reset configuration to each reader to remove the stock configuration.

  5. Present the ConfigCard with new configuration to each reader to deploy this configuration.

Readers with a custom configuration

To update readers using a custom configuration, the new configuration must be a new version of the existing one.

Why?

Readers configured with a custom configuration only accept new versions of the same configuration. This is to prevent unauthorized or malicious changes or rollbacks to potentially insecure versions.

Learn more about configuration protection

Detailed how-to:

  1. Ensure you have the current custom configuration as a BALCFG file.

    I don't have a BALCFG file

    To create a new version of a configuration, you need the editable BALCFG file. It's not possible to edit the deployable file (BEC2 or BEC format) or read out and edit a configuration that is already deployed.

    If the configuration name follows this naming scheme, it was created by BALTECH and we can provide the BALCFG file on request. You can identify the configuration name by:

    • Checking the file name of the BEC2 or BEC file.
    • Connecting the reader to ID-engine Explorer.

  2. Create a new version of this configuration.

  3. Modify the configuration as needed.

  4. Release and export the new version.

  5. Create a ConfigCard containing the new configuration version.

  6. Present the ConfigCard to each reader to deploy the update.

Support

Got stuck somewhere? Want to order a custom configuration from us?
Contact us

Title