Skip to content

Configure readers for your host interface

The host interface defines the reader's communication with the host system as well as basic feedback to the card holder (LED and beeper).

I have multiple reader types in my project

You may have multiple reader types with different host protocols and/or different user feedback in the same project, e.g. ACCESS200 readers for access control and ID-engine readers for time and attendance. If this is the case, you have to work with multiple configuration files to configure individual host interfaces per reader type.

Overview of host interface components

If you're unsure which component to use, please refer to your host system documentation or ask your host system provider.

Interface/Protocol Description
USB  
Keyboard Emulation Reader output emulates keystrokes and is sent autonomously to the host.
Virtual COM Port Undirectional Reader sends ASCII-formatted decimal number autonomously to the host.
Virtual COM Port Bidirectional Read results are buffered for the host to retrieve it. Based on BRP. This protocol also allows you to control the reader via the host application, e.g. to override the Feedback to card holder settings.
HID Read results are buffered for the host to retrieve it. Based on BRP. This protocol also allows you to control the reader via the host application, e.g. to override the Feedback to card holder settings.
PC/SC Interact with ISO 14443-4 cards via the PC/SC interface. Only use this component if the standard PC/SC configuration does not meet your needs.
RS-232/UART  
Unidirectional Reader sends data to host autonomously. No options to control the reader.
Bidirectional Read results are buffered for the host to retrieve it. Based on BRP. This protocol also allows you to control the reader via the host application, e.g. to override the Feedback to card holder settings.
Ethernet
Host as Client The host opens a connection to the readers (learn more). This component also contains settings for PKI authentication and encryption.
Host as Server Readers open a connection to the host in certain events. This is recommended for large numbers of readers or readers behind a firewall (learn more). This component also contains settings for PKI authentication and encryption.
Wiegand Change the default Wiegand settings on ACCESS200 or enable Wiegand on ID-engine Z.
OSDP Lets you switch ACCESS200 readers from Wiegand to OSDP and change default parameters if needed. Each reader is assigned bus address 1.
Alternatively, use BALTECH AdrCard to enable OSDP with default parameters and individual bus addresses.
You can also combine AdrCard and OSDP component: Then, the address set with AdrCard will be used, while the parameters from the component will apply.
Offline Access Control For access control setups without a host system. Learn more

Feedback to card holder (LED & beeper)

Depending on your host interace and operation mode, the feedback to card holder may be controllable via the configuration:

  • If you have a checkbox, you can either enable it to control feedback via the configuration, or disable it to control feedback via the host application using the UI command group. In both cases, you can additionally customize the LED using the custom LED component.

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

  • If there's no checkbox, you can only control feedback via the configuration. You can additionally customize the LED using the custom LED component.

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

  • If feedback settings are not shown at all, you have to control feedback via the host application using the UI command group.

    Section "Feedback to card holder" (LED and beeper) in BALTECH ConfigEditor not available for selected operation mode

Testing

To test the host interface component, run a test with your host sytem.

Title