VHL & Autoread
This mode covers the same use case as the standard VHL implementation. We recommend it if:
- You're implementing an Ethernet application as a server.
- You've used Autoread via BRP so far and want to implement
a more complex logic now, e.g. read large data volumes, write data, or set up complex
Note that in this case, your configuration will become more complex.
What is VHL?
VHL stands for Very High Level card access. It's a simplistic macro command set that is independent of a specific card type (learn more).
What is Autoread?
The reader scans for cards and reads them autonomously (learn more).
How it works
This implementation is based on BALTECH Reader Protocol (BRP). To keep your effort low, we provide an SDK for the most common platforms.
This approach combines Autoread via BRP with the standard VHL implementation.
- The reader runs in Autoread mode to perform basic tasks autonomously, e.g. poll for cards or give feedback to the card holder.
- Once the reader has detected a card, it reads the card's number and buffers it in an internal queue.
- The reader pauses Autoread and waits for the host to retrieve the number from the queue, run VHL and/or other I/O commands. (If the host is implemented as an Ethernet server, this step requires the reader to open a connection first.)
- When done, the host reenables Autoread.
- USB HID (recommended with the SDK)
- USB virtual COM port (recommended when not using the SDK, required for RDP)
- Ethernet (host as client/host as server)
Configure the reader
To prepare readers for access from your application, create a configuration for the readers. Alternatively, you can order a configuration from us.
- A Windows computer with BALTECH ToolSuite installed
- A test reader you can connect to your computer.
If the productive reader type doesn't provide a USB connection, we recommend you use an ID-engine ZB to create and test the configuration.
To configure the reader:
Create a configuration that contains an Autoread component (to enable Autoread on the reader) and a "VHL file" (in which you describe the card's data structure).
If you work with the SDK, you can use one of the demo configurations in the app notes as a basis. To do so create a copy of it.
Test the VHL file. This step also helps you verify the parameters you'll later need to run VHL commands.
To control access permissions and set up authenticated and encrypted communication, you can additionally configure Authentication and Encryption.
Configure the test reader to later test your application..
Set up SDK
The easiest way to use VHL is the BALTECH SDK, available for Windows, macOS, and Linux.
My platform's not supported
If you can't use the SDK, you can create the BRP command frames yourself. Please refer to the BRP specification and example frames.
To set up the SDK:
- Download the SDK from our website.
- Get familiar with its components. We recommend you get started by trying out the app notes.
- Integrate the SDK into your application.
- Set up a protocol stack to be able to run commands.
- Run AR.Setmode with Mode = EnableOnce (0x02). This ensures that the reader pauses Autoread mode as soon as it has detected a card, so you can perform operations.
- Run AR.GetMessage to poll the reader for a detected card and its number.
Run the VHL command(s) required for your operations. Here are the most important ones:
Start from 1. again to reenable Autoread mode.
Reader hardware control
There are various commands to control the reader hardware. You can control reader feedback (e.g. LED and beeper), reboot the reader, check its firmware version, etc.
That's it for the development part. The next steps are as follows:
- Release and export the configuration
- Check deployment options and create a ConfigCard if needed.
- Install the readers and deploy the configuration.
Does someone else take over configuration management?
If someone else needs to adapt your configuration for various projects (e.g. exchange encryption keys), then please give them the released configuration in BALCFG format. They can then create a copy of it. When documenting what they need to change, you may want to reuse some of the how-tos you find here.
Troubleshooting & support
Got stuck somewhere along the way? Don't worry, we'll help you troubleshoot: