Skip to content

Test Autoread configuration & LED/beeper

If your configuration contains an Autoread component, i.e. an RFID interface configuration for autonomously reading a number, you can test right in BALTECH ConfigEditor, if the number is read as expected.

In the same step, you can also test the LED and beeper settings.

While you'll typically want to use this functionality in ConfigEditor, it's also available in ID-engine Explorer and works the same way.

Test Autoread configuration

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

  2. Open the BALCFG file of the configuration.

  3. Connect a test reader to your computer.

  4. Click Test Autoread Configuration.

    Screenshot: Button "Test Autoread Configuration" in BALTECH ConfigEditor

  5. Place a sample project card on the reader.

  6. In the Message Data (ASCII) column, you'll see the data that is being read from the card based on the Autoread component in your configuration.

    Screenshot: Example Autoread test result in BALTECH ConfigEditor or ID-engine Explorer

    This test output may differ from the output in your host system

    In ConfigEditor (and ID-engine Explorer), the number read from the card is always displayed in ASCII decimal encoding. Your host system may use a different encoding. In this case, please order a custom host interface component that converts the number accordingly and keep in mind that the output in ConfigEditor (and ID-engine Explorer) won't match the output in your host system (learn more).

  7. To keep editing the configuration, close the dialog, make your changes, and click Test Autoread Configuration again.

What to do if things don't work
  • You can always delete the Autoread component and start from scratch. To do so, just right-click it in the Configuration Components list at the top right.
  • Let us look into it and order a configuration from us. This works for all 125 kHz cards and for 13.56 MHz cards for which you know the encryption keys.
  • You can also work with the plain UID instead of the expected number. To do so, you need to create a new database for the host system that contains all the UIDs of the cards in your project and their corresponding programmed card numbers (PCNs) and/or card holder names. Please note that this is not possible for cards that return random IDs. Not sure if this approach works for you? We're happy to help.

Test LED and beeper

If feedback to card holder is controlled via the configuration (i.e the host interface component), LED and beeper will be switched accordingly during the above test of the Autoread configuration. If you're unsure how feedback to card holder is controlled, check the host interface component.

Section "Feedback to card holder" (LED and beeper) in BALTECH ConfigEditor

If you don't have the RFID interface configured yet, you can temporarily add the Autoread All UIDs component for testing. To do so, go to your configuration in ConfigEditor and click the Plus icon > RFID Interface > Show More > All Card Types > Autoread All UIDs.

If you've also added a Custom LED component, these settings will take effect as well.