Skip to content

Troubleshooting ConfigCard

No signal

Details

Issue 1
The reader's operation mode doesn't support ConfigCards.
By default, ConfigCards can only be used with readers operated in Autoread mode (i.e. autonomous operation). This includes:

If you use "pure" VHL, you can enable ConfigCard support by running the VHL.Select command with the parameter AcceptConfCard = true.

In all other operation modes, readers do not recognize ConfigCards.

Solution 1
You can temporarily enable Autoread on the reader with BALTECH ID-engine Explorer:

  1. Connect the reader to your computer.
  2. Open BALTECH ID-engine Explorer.
  3. On the left, click Test Autoread Configuration.

Now you can use the ConfigCard as described here.

Note: Once the reader has read the ConfigCard, ID-engine Explorer will display the error message The connection to the reader has been lost. The happens because the reader needs to reboot after having received the configuration. To re-establish the connection, click Show Connected Readers in the error message and select the reader.

Issue 2
The reader is configured for Autoread mode, but Autoread has been disabled temporarily. This happens e.g. when the host sends a VHL or low-level command to the reader.

Solution 2
Reboot the reader. This automatically reenables Autoread mode.

Red LED | 7 beeps

Diagram: Feedback pattern of a BALTECH reader when a ConfigCard couldn't be read.
Details

The reader couldn't read the ConfigCard.

Issue 1
You've removed the ConfigCard from the reader too early.

Solution 1
Please try again. Do not remove the ConfigCard before the yellow LED is off.

Issue 2
The ConfigCard is defective.

Solution 2
Please get in touch with us.

Red LED | 7 + 1 beeps

Diagram: Feedback pattern of a BALTECH reader that has rejected a ConfigCard for security reasons.
Details

Issue 1
The configuration you're trying to deploy is for a different project than the one currently deployed. The reader rejects it to prevent unauthorized reconfiguration. It only accepts new versions of the same configuration (learn more).

Solution 1

  • If you actually want to deploy a configuration update for the existing project, please use a different workflow for creating that update: Create a new configuration version instead of a new configuration or a copy of an existing configuration.
  • If you want to use the reader in a different project, do a factory reset with BALTECH Uploader first to remove the existing configuration. Then, you can deploy the new configuration.
  • A factory reset may not always be feasible, e.g. when you have a standard configuration deployed and want to replace it with an end-customer-specific configuration with ConfigCard only (i.e. without BALTECH Uploader). In this case, you can order a special configuration that can be overwritten without a factory reset.

Issue 2
The configuration version you're trying to deploy is older than the one currently deployed. The reader rejects it to prevent rollbacks to potentially insecure versions. It only accepts newer versions of the same configuration (learn more).

This applies to all configurations created with BALTECH ConfigEditor v4.15.00 (released 11 September 2018) or above.

Solution 2
If you want to deploy the version on this ConfigCard, you need to do a factory reset first. However, what we recommend is a different workflow:

  • If you want to make a version rollback on productive readers:
    Open the version you want to deploy in ConfigEditor. Create a new version from it and deploy this version to the readers.
  • If you want to try out different settings with a test reader:
    Don't release the configurations, but keep them in draft mode. Then you can overwrite one configuration with another without a factory reset.

Red LED | 7 beeps + 2 beeps

Diagram: Feedback pattern of a BALTECH ACCESS reader that has rejected a ConfigCard due to a wrong customer key.
Details

Issue
The configuration you're trying to deploy was created with a customer key that doesn't match the customer key on the reader (learn more). This happens typically when productive readers are equipped with your company's own customer key, while the ConfigCard was created with a standard BALTECH reader holding a default customer key.

Solution
To fix this, create a new configuration and make sure to release it on a reader holding your company's own customer key. You can use your existing configuration as a template:

  1. In ConfigEditor, open the existing configuration in BALCFG format.
  2. Click Create a copy for a new project and enter a configuration name and description. This creates a copy of your configuration that is not linked to the previous customer key.
  3. Release the configuration with a reader that holds your company's own customer key.
  4. Load the configuration on the ConfigCard. You can keep your existing ConfigCard. The old configuration will be overwritten.
Title