Set up readers for Mobile ID

To set up readers for Mobile ID, you need to:

• Enable Mobile ID in the reader configuration
• Update the reader firmware to 1100 v2.06 or above (for standard readers) or 1096 v3.01 (for print-management readers)

This feature requires BALTECH ConfigEditor v5.00.07 or above.

Prepare configuration

1. Open BALTECH ConfigEditor.
   If you haven't installed it yet, you can download it here as part of BALTECH ToolSuite.

2. If you don't have a configuration yet, create a new one for your project.
   In the Autoread Wizard, enable the checkbox for BALTECH Mobile ID.

   

   If you already have a configuration, create a new version. Then, click the Plus icon > RFID Interface > BALTECH Mobile ID > Autoread BALTECH Mobile ID.

   

Do not include the Autoread All UIDs component

If you want to read physical cards as well, use the specific Autoread UID component for your card type(s) instead of Autoread All UIDs. Otherwise, the reader may respond repeatedly to the same phone (learn more).

Enter encryption key

In the configuration, you specify the encryption key from your Mobile ID project, so readers can communicate with your users' apps.

To enter the encryption key:

In the Encryption Key field, paste the key for that project from Mobile ID Manager.

Where do I find that key exactly?

1. Log in to your admin account in Mobile ID Manager.

2. If you have multiple projects, make sure the desired one is open.

   How do I switch projects?

   Click the arrow next to the project name at the top.

   

3. Go to Settings.

4. Copy the Encryption key to the clipboard.

   

I want to add keys from multiple projects

So the reader accepts apps from multiple projects, e.g. at the main entrance of a multi-tenant building, you can add multiple keys:

1. Enable Support Multiple Keys.

   

2. Click .

3. In the Add Key field, enter the encryption key of the first project.

4. Click again to add another key.

   

Define user interaction

This feature requires Mobile ID app v1.1.0 or above.

In the User Interaction dropdown, select how you want users to interact with the reader:

Interaction	Description
Card-like	Users need to present their phones to the reader as they would present a physical ID card.
Convenient	Users just need to carry their phones with them, but can leave them in their pockets.
Car park	Users trigger the reader from a distance via the press of a button, typically to open the barrier of a car park.

Package configuration with firmware

We recommend you package the configuration with the firmware. Thus, you can deploy them both in one go.

To package configuration with firmware:

1. Download the appropriate firmware for your reader type:

   • Firmware 1100 v2.06 or above for standard readers
   • Firmware 1096 v3.01 or above for print-management readers

2. In Administrative Information, enable the option Package with Specific Firmware Version.

3. Select the downloaded firmware file.

   

4. Release and export the configuration.
   You'll receive a BEC2 file with both the configuration and the firmware that you can deploy to readers.

Deploy configuration and firmware

Depending on your readers' current firmware, you have the following options to deploy the BEC2 file:

• On standard readers with firmware versions below 1100 v2.00, use Wired Upload.
• On standard readers with firmware version 1100 v2.00 or above, use Wired Upload or Wireless Upload.
• On print-management readers, use Kofax Reader Maintainer.

Future firmware updates must be packaged with the configuration as well

As soon as the reader contains a configuration packaged with a firmware, you cannot upload a firmware file alone. To upload it, you need to create a new version of the configuration and package it with the BF2 file as described above. Otherwise, you'll need to factory-reset the reader when uploading the BF2 file and re-deploy the configuration afterward.

Troubleshooting

It doesn't work as expected? Please find typical issues and solutions in our troubleshooting guide