Skip to content

Configure readers for your RFID interface

The RFID interface defines the interaction with the project card. Whether and how you need to configure it depends on the operation mode:

Operation mode RFID interface component
Autoread Autoread component
VHL & Autoread VHL file and Autoread component
APDU via VHL none
PC/SC none
Low level commands none

Add an Autoread component

Autoread components configure the RFID interface for autonomously scanning for cards of a specific card type and read the desired number.

To add an Autoread component:

  1. In BALTECH ConfigEditor.
  2. Open the configuration you've created.

  3. Click the Plus icon > RFID Interface > Your card type.

    Screenshot: Add an Autoread component manually to a configuration for an RFID reader in BALTECH ConfigEditor

  4. Select the appropriate Autoread component. Depending on your card type, 1 or both may be available:

    I don't know the card type yet

    In this case, configure the RFID interface to read UIDs of all supported card types for now. To do so, click the Plus icon > RFID interface > Show More > All Card Types. Make sure you later replace this component with a card-type-specific one.

    I only know the type number from Reader Maintainer

    If you're working with print-management readers and previously used Reader Maintainer, you may only know the type number from its stock configurations. To identify the card type, use these tables: Find your type number in the Decimal column, then refer to the Product name column for the corresponding card type.

    Autoread component Description
    Autoread UID Read and convert the UID (serial number) of the card. Also works for cards that return a random ID by default. See conversion options for output customization.
    Autoread UID – Print Management Available for some card types. Use this if you're configuring print-management readers and this component is offered for your card. Otherwise, use Autoread UID for print-management readers as well.
    Autoread UID – Print Management – MX Compatible Available for some card types. Use this when configuring print-management readers that must emulate MX reader behavior (output format, LED, and beeper). If not required, use Autoread UID – Print Management (if available), or otherwise Autoread UID.
    Autoread Number in File/Sector/Segment etc. Read and convert a programmed card number (PCN) stored in a file, sector, or segment of the card.

More complex scenarios

In most cases, you'll need to add 1 Autoread component to your configuration as described above. In more complex scenarios you may need multiple Autoread components, e.g. when dealing with multiple card types or exchanging an encryption key.

Add a VHL file

A VHL file is needed if you develop your own application using the VHL macro command set. The VHL file contains card-type-specific information, i.e. the memory location to access and, if applicable, encryption keys needed. With this information, the reader can "translate" VHL commands into low-level commands for your card type.

To add a VHL file:

  1. Open BALTECH ConfigEditor.
  2. Open the configuration you've created.

  3. Click the Plus icon > RFID Interface > Your card type > VHL File.

    Screenshot: Add a VHL file manually to a configuration for an RFID reader in BALTECH ConfigEditor

VHL files are currently available for the following card types:

  • EMarine
  • FeliCa
  • HITAG
  • ISO 15693
  • ISO 7816-4
  • LEGIC
  • MIFARE DESFire
  • MIFARE Classic
  • MIFARE Ultralight

If you need a VHL file for a different card type, please get in touch with us.

Title