- You want to read data other than a number.
(To read a number, we recommend Autoread).
- You want to write data to the card.
What is VHL?
VHL stands for Very High Level card access. It's a macro command set that allows you to handle nearly all aspects of a card technology. Compared to low-level commands, however, VHL offers significant advantages:
- Independence of card type
All card-type-specific information is stored on the reader. If needed, you can later modify the reader setup without having to adapt your application.
With a single command, you can read or write large data volumes - no complex command sequence needed. This also saves you the effort of familiarizing yourself with the details of the respective card type.
Communication errors are handled automatically as far as possible, e.g. using retry mechanisms.
- Optimized performance
VHL avoids unnecessary round trips to the application by handling communication between reader and card whenever possible. Depending on the amount of data to transfer and the interface you use, this may have a positive impact on performance.
How it works
- Configure the reader for your cards' data structure. You can use our GUI tools in BALTECH ToolSuite to conveniently create and deploy the configuration (including wireless deployment options).
- This configuration "translates" VHL commands into low-level commands, handles communication with the card, and returns the final results.
- Control reader feedback (e.g. LED and beeper) and other hardware functionality directly via the host.
- USB HID (recommended with the SDK)
- USB virtual COM port (recommended when not using the SDK, required for RDP)
- Ethernet (host as client only)
Use VHL & Autoread if:
- You implement your host application as an Ethernet server.
- You've used Autoread so far and want to "upgrade" to VHL to implement a more complex logic.
Use VHL without configuration if:
- You don't want to configure readers.
- You don't want to specify the card structure (i.e. the parameters to access the card) before putting readers in operation, but control the parameters flexibly during reader operation.
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. It will include a "VHL File", in which you describe the card's data structure.
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
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 VHL.Select to scan for cards.
With this parameter, you decide if the reader configuration can later be updated with BALTECH ConfigCards or not. So make sure you set the parameter in line with project requirements.
Run the VHL command(s) required for your operations. Here are the most important ones:
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: