Add device settings to your configuration

In the device settings, you define the protocol for the reader-host communication. If you use Autoread mode, you can optionally also define reader feedback (e.g. LED and beeper).

Note for Ethernet developers

If you want to run your application as an Ethernet server, you'll need to use a special form in which you can also configure the host (learn more).

Keep factory device settings or create your own?

BALTECH readers are shipped with factory device settings defining default protocols and feedback depending on the reader type. Do the factory device settings fully meet your requirements? Then you don't need to create your own device settings. If, however, you want to make any changes, you need to create your own device settings that fully overwrite the factory device settings.

Do you have multiple reader types in your project?

You may have multiple reader types with different host protocols and/or different user feedback in the same project, e.g. ACCESS2xx readers for access control and ID-engine readers for time and attendance. If this is the case and the factory device settings do not meet your needs, you have to create individual device settings per reader type.

Create a device settings component

  1. Open BALTECH ConfigEditor.

    If you haven't installed it yet, you can download it herecall_made as part of BALTECH ToolSuite.

  2. In the popup window, click Open and select the BALCFG file of your existing configuration.
    Screenshot: Open an existing configuration (BALCFG format) in BALTECH ConfigEditor

    If you don't have a configuration file yet, create a new one.

  3. Click Extend Configuration > Settings > Device Settings.
    Screenshot: Menu path to add device settings in BALTECH ConfigEditor

    Only 1 device settings component per configuration file

    If you already have a device settings component, you need to remove it before you can create a new one.

Fill out device settings

Specify host protocol and parameters

  1. In the Protocol drop-down, select the protocol that the host system uses to communicate with the reader. Find more details in the sections below.
  2. In the Autoread drop-down, keep the option EnabledIfDefinedRules selected.
  3. If applicable for your protocol, specify the Parameters as described in the sections below.

    Please refer to your host system documentation or ask your host system provider for this information.

Ccid

  • Protocol description: PC/SC (based on USB/CCID)
  • Parameters: none

BrpTcp

  • Protocol description: Ethernet/TCP; host system is implemented as a client.
  • Parameters: none

BrpHid

  • Protocol description: USB/HID
  • Parameters: none

BrpSerial

  • Protocol description: RS-232/virtual COM port
  • Parameters:
    • Baud rate: Specify the number of bits transferred per second
    • Parity: Specify if an even, odd, or no parity bit used

RawSerial

  • Protocol description: RS-232/virtual COM port
    The communication is unidirectional, i.e. the reader transmits a number that can be processed by any software supporting serial communication, e.g. a terminal software.
  • Parameters:

    • Serial Baudrate: Specify the number of bits transferred per second

      Note for developers: Specify the same baud rate as in your application.

    • Parity: Specify if an even, odd, or no parity bit used

    • Prefix and postfix: Specify characters to be added to the output before transmission to the host system

KeyboardEmulation

  • Protocol description: Reader output emulates keystrokes
  • Parameters:
    • Prefix and postfix: Specify characters to be added to the output before transmission to the host system.

OSDP

To enable OSDP on ACCESS2xx readers, you don't need device settings. Instead, you can set a bus address on each reader using BALTECH AdrCard. You only need device settings if you want to change the default parameters or set a fixed bus address on all readers.

  • Parameters:
    • Baud rate: Specify the number of bits transferred per second
    • Spec compliance: Specify which version of OSDP you want to use.
      For unencrypted communication, select V1. To enable encrypted communication, select V2.
    • Install mode (OSDP v2 only): When enabled, the host uses the default encryption key to initially authenticate with the reader. This is needed so the host can write the project-specific encryption key to the reader. Once this is done, the host will disable Install mode, so the default encryption key can no longer be used.
    • Secure mode (OSDP v2 only): When enabled, the communication will be encrypted whenever this is possible. Only certain non-critical commands will still be transmitted in plain text.
    • Bus address: To set an individual bus address on each reader, select Set with BALTECH AdrCard. You can later use BALTECH AdrCard to set the address when the readers are installed. If your host only supports 1 reader per bus, select Set fixed address and specify it in the field below.
    • Prefix and postfix: Specify characters to be added to the output before transmission to the host system.

Wiegand

  • Parameters:
    • Length in Bit: Length including parity bit
    • Prefix and postfix: Specify characters to be added to the output before transmission to the host system.

Define feedback to card holder

Only possible in Autoread mode

Defining feedback in the device settings is optional, but only possible in Autoread mode. If you develop your own application based on BRP, you can alternatively define feedback with the UI command groupcall_made,
no matter if you use Autoread, VHL, or low-level commands.

  1. Enable the LED / Beeper settings checkbox.
  2. Click Green Plus icon at the bottom of the input box.
  3. In the Events drop-down, select an event in which you want the reader to emit a signal, e.g. when powering up or when accepting a card.
  4. In the Beeper and LED sections, define the signal to be emitted in the selected event.

Screenshot: Dialog to define custom LED and beeper signals for certain events in BALTECH ConfigEditor

Now you're done with the device settings and can continue in your process.

Unlike project settings, you cannot test device settings in ID-engine Explorer, but only in your test application or test environment.