Configure print-management readers for keyboard emulation

Out of the box, print-management readers are supported by most MFPs running a Tungsten product such as ControlSuite, SafeCom, or Printix. On certain MFPs, however, or when running other products, readers need to be configured for keyboard emulation.

Configure for Tungsten products

1. Open the latest version of BALTECH ConfigEditor.
   Download it here as part of BALTECH ToolSuite.

2. Click Start Autoread Wizard > Print Management > Tungsten Products > Keyboard Emulation, and complete the wizard.

   My readers are currently configured with a custom configuration

   Then we recommend you create a new version of it. This lets you deploy the updated configuration via ConfigCard.

     

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. Complete the configuration as described here.

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

6. Transfer the configuration to the reader and run a test with your MFP.

7. Release & export the configuration for productive deployment.

8. Deploy the exported BEC file via Wired Upload or ConfigCard.

   When using ConfigCard, you may first have to remove the existing stock solution.

Configure for other products

Update firmware

• To support keyboard emulation with other products, readers must run firmware 1096 v2.40.03.
• For Micro Card Readers, we recommend 1096 v3.00.04 or above.

To check and update the firmware:

1. Find out the current firmware version.
2. If you need to update, download the required firmware file.
3. Deploy the firmware file via Wired Upload in BALTECH Uploader.

Create configuration

1. Open the latest version of BALTECH ConfigEditor.
   Download it here as part of BALTECH ToolSuite.

2. Click Start Autoread Wizard > Print Management > Keyboard Emulation for Other Products, and complete the wizard.

   My readers are currently configured with a custom configuration

   Then you need to create a new version of the existing configuration.

     

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. Enter project-specific details as listed in the left column of Your Workflow.

   

Test RFID interface configuration

Before testing the reader with your MFP, make sure the reader reads the card as expected. If you have a working third-party reader, check its output as a reference.

Identify third-party reader output

1. Connect the third-party reader to your computer.
2. Open a text editor, e.g Windows Notepad.
3. Present a sample card to the third-party reader.

4. In the text editor, you'll now see the card number as read and converted by the third-party reader.

   

Test BALTECH reader output

1. Connect the BALTECH test reader to your computer.
2. Open your configuration in ConfigEditor.

3. Test the RFID interface configuration and edit as needed to match the BALTECH reader's output ConfigEditor with the third-party reader's output.

   

Test full config

Transfer the configuration to the reader and run a test with your MFP.

It doesn't work?

If the reader still isn't supported by the MFP, try alternative USB keyboard settings.

To enable alternative USB keyboard settings:

1. In the configuration, select the component Keyboard Emulation for Print Management.

2. Enable Improve MFP Compatibility.

   

3. Transfer the configuration to the reader and try again with the MFP.

4. If there is still no response, also try alternatives 2 and 3 in the USB Keyboard Settings dropdown.

   

Readers are no longer directly recognized by BALTECH software tools

To connect a reader with alternative USB keyboard settings to a BALTECH tool such as ConfigEditor, enable the checkbox Show print-mgmt readers with alternative USB keyboard settings. Select the reader and confirm the dialog.

Export

Release & export the configuration for productive deployment.

Deploy

Deploy the exported BEC file via Wired Upload or ConfigCard.

When using ConfigCard, you may first have to remove the existing stock solution.