Configurations for complex use cases

In most cases, you'll have a configuration with 1 device settings component (if factory device settings don't meet your needs) and 1 project settings component. However, there are use cases that can't be covered with this standard setup. Here's a list of special scenarios you may be confronted with, requiring multiple device settings or multiple project settings components.

Multiple reader types in the same project

You may have multiple reader types with different host protocols and/or different user feedback in the same project, e.g. BALTECH ACCESS2xx readers for access control and BALTECH ID-engine readers for time and attendance.

In this case you need to create individual device settings per reader type. This works as follows:

  1. Keep the individual device settings in separate configurations.
    There can only be 1 device settings component per configuration file.

  2. For the project settings, you have 2 options:

    1. Standard approach: Add project settings to each configuration file.
      This approach is required for initial installation and when deploying a new version that includes a device settings update.

      Add project settings to 1 configuration file. Then use the import feature to copy the project settings to the other configuration file(s).

      Add the same project settings to multiple BALTECH configurations with different device settings each

    2. Keep project settings in a separate configuration file.
      We recommend this approach when you later update the project settings only, e.g. to exchange an encryption key.

      When using this approach, make sure device settings are already deployed when you deploy the project settings.

      1 BALTECH configuration with project settings plus 2 additional configurations with different device settings each

Multiple card types

There may be more than 1 card type in your project, e.g. if you're managing the access control system of a company that has merged with another one, and all employees keep their original project cards.

In this case, create 1 project settings component per card type and add them all to the same configuration file.

  • The order of project settings matters: The reader tries them from top to bottom, so the order may impact performance and functionality. You may e.g. want to have the project settings for the more frequently used card system at the top. To change the order, right-click a component in the left part of BALTECH ConfigEditor and use the Up and Down options.
  • Deploy all project settings as a whole: All project settings components must be included in 1 configuration and deployed together.

1 BALTECH configuration with different project settings for different card types

Exchanging a project key

When exchanging the encryption key on your project cards, it usually takes a while to reformat or exchange all project cards. To cater for this interim period, you'll need to reconfigure the reader twice:

  1. Add a second project settings component with the new key and deploy the configuration.
    The reader will then accept cards with the old key as well as cards with the new key. Leave this configuration in place until all cards have been reformatted or exchanged.
  2. Remove the old project settings and deploy the configuration. Only cards with the new key will now be accepted.
  • The order of project settings matters: The reader tries them from top to bottom, so the order may impact performance and functionality. If you e.g. replace the bulk of the project cards right at the beginning, you'll want to have the project settings with the new key at the top. To change the order, right-click a component in the left part of BALTECH ConfigEditor and use the Up and Down options.
  • Deploy all project settings as a whole: All project settings components must be included in 1 configuration and deployed together.

Phases of exchanging an encryption key in a BALTECH configuration

Multiple companies in the same building

In an office building where each floor is used by a different company, you may have the following setup:

  • Each company has its own card system (i.e. card type, encryption keys, etc.) and its own host system.
  • The main entrance is used by all companies. Here, you have a simple (usually offline) reader that's only supposed to check if the card matches one of the company cards.

This is different from the site-code scenario

The multi-company scenario may also be solved with a site code: In that case, there's 1 host system for the entire building that grants access rights based on a site code that is part of the card number. For the site-code scenario, you only need a standard configuration with 1 project settings component (and 1 device settings component if factory device settings don't meet your needs).

If you have multiple companies and multiple host systems, proceed as follows:

  1. Create 1 configuration file per floor containing the floor-specific project settings (and individual device settings for the companies' individual host systems).
  2. Create an additional configuration file for the main entrance with project settings for all companies (and device settings for the main entrance; these are usually offline device settings).

    • The order of project settings matters: The reader tries them from top to bottom, so the order may impact performance and functionality. You may e.g. want to have the project settings for the company with the most employees at the top. To change the order, right-click a component in the left part of BALTECH ConfigEditor and use the Up and Down options.
    • Deploy all project settings as a whole: All project settings components must be included in 1 configuration and deployed together.

    To copy all company-specific project settings to the main entrance configuration, you can use the import feature.

BALTECH configurations for an office building with various companies and a shared main entrance