Test RFID interface and LED configuration
You can test both the RFID interface component as well as LED and beeper right on your computer. All you need is BALTECH ToolSuite, a test reader, and a sample card.
Set up the test
Open BALTECH ConfigEditor.
If you haven't installed it yet, you can download it here as part of BALTECH ToolSuite.
Open the BALCFG file of the configuration.
Click Test Configuration in the bottom left.
BALTECH ID-engine Explorer opens.
- Connect a test reader to your computer.
Click the reader, then click Select.
- If several interfaces are shown for the reader, please select HID.
- Connecting an Ethernet reader works when the reader is unconfigured or required permissions are granted in PKI Encryption and Authorization settings.
In the popup, click Yes to enable Autoread.
The configuration is now transferred to the reader. You can test it in ID-engine Explorer as described below.
Test RFID interface component
- Place a sample project card on the reader.
In the Message Data (ASCII) field, you'll see the data that is being read from the card based on your RFID interface component.
This test output may differ from the output in your host system
In 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 convert the number accordingly and keep in mind that the output in ID-engine Explorer won't match the output in your host system (learn more).
To keep editing the RFID interface component in BALTECH ConfigEditor, click Continue Editing Configuration in the bottom left. Then test your changes again in BALTECH ID-engine Explorer until the reader returns the data you need.
As an option, you can further restrict the card numbers by creating a blacklist or whitelist.
What to do if things don't work
- You can always delete the RFID interface component and start from scratch. To do so, just right-click them on the left side of the screen.
- Let us look into it and order a configuration from us. This works for all 125 kHz cards and 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 configuration
Red (basic state)
The red LED turns automatically on as configured once you've set up the test.
Green (valid card detected)
The green LED turns on as configured when you test the RFID interface component with a valid card.
If you don't have an 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 Add > RFID Interface > Show More > All Card Types > Autoread All UIDs.
The logical yellow LED turns on as configured when the red and green LEDs are turned on at the same time.
This only applies in the following cases:
- The LED is controlled by the host application.
- You use the Wiegand host interface with LED Control set to INPUT_0 controls green LED, and INPUT_1 controls red LED. In addition, the reader's I/O ports must be connected accordingly.
To keep editing the Custom LED component in BALTECH ConfigEditor, click Continue Editing Configuration in the bottom left. Then test your changes again in BALTECH ID-engine Explorer.