Set up readers for existing project cards and host system
Integrating a BALTECH reader into a specific project isn't rocket science at all. It's a straightforward workflow that we'll walk you through step by step.
Your operation mode: Autoread
In Autoread mode, the reader autonomously scan for cards, transfers data to the host, and interacts with the user (e.g. give feedback via LED and beeper or switch a door relay). This means for you: None or minor adjustments to the host system required - you can make all necessary changes directly on the reader via its configuration.
Prepare project cards
If the application data for your project still need to be programmed onto the cards, we can help you do the formatting for certain card types.
Create reader configuration
The configuration defines the reader's behavior within your project. With our software tools, you can create the configuration yourself. Alternatively you can order a configuration from us.
Already have a configuration?
You may already have received a configuration with a configured host interface (e.g. from your host system provider). In this case, you can create a copy of it to add or modify components as needed.
- A Windows computer with BALTECH ToolSuite installed
A test reader you can connect to your computer.
My productive readers don't have a USB connection.
Then we recommend you use an ID-engine ZB Brick for project management. In this case, you may also want to order a BALTECH ConfigCard for convenient configuration deployment (learn more about deployment methods).
My company uses their own BALTECH customer key.
If your productive readers are equipped with your own customer key, the test reader needs to hold that customer key as well.
I have a legacy reader.
Legacy readers with a firmware ID other than 1100 don't support the following project management features:
- Analyze card structure
- Create a ConfigCard in ConfigEditor or Uploader
- Release and export a configuration
- Wireless Upload of configuration and firmware
To use them, please get one of our current reader types. We recommend ID-engine ZB Brick.
A sample project card
- The expected number to read from the sample card
This is usually an entry in the host system's database. Often, it's also printed on the card.
To create the configuration:
- Collect project information
- Create the configuration
- Test Autoread configuration and LED/beeper with BALTECH ToolSuite
- Test the entire configuration in a test environment
Prepare configuration for deployment
When your configuration is ready to go:
Learn more about deployment methods
We can also deploy the configuration for you during production if you order large reader quantities. Please get in touch for more information.
Install readers & deploy configuration
Hand over your configuration and a test project card to the technician to install the readers. For detailed installation steps, please see our installation guides.
Updates & maintenance
In the lifecycle of a project, you may want to update the reader configuration (e.g. to change the project key or support an additional card type) and/or the reader firmware (e.g. to use a new feature). This is possible at any time, also during productive use.
- See our recommended workflows for configuration or firmware upates.
- If the application data on the project cards needs to be changed as well, we can help you reformat the cards.
- When reusing a reader in a different project, make sure you do a factory reset first.
Troubleshooting & support
Got stuck somewhere along the way? Don't worry, we'll help you troubleshoot: