Skip to content

Create a ConfigCard with ConfigEditor

With a BALTECH ConfigCard, you can easily deploy a configuration by presenting the card to the readers. With BALTECH ConfigEditor, you can create a ConfigCard using the BALCFG configuration file.

With this method, project managers can create ConfigCards and provide them to technicians. Alternatively, technicians can create ConfigCards on-site in Uploader.

Equipment & requirements

  • Any BALTECH ToolSuite version
  • A reader to create the ConfigCard: We recommend ID-engine ZB Brick or ACCESS200

  • A ConfigCard v2 (can be overwritten)
    or a blank MIFARE DESFire card (EV1 or above)

    Older ConfigCards (without the addition v2 on the label) only work with configurations that have legacy firmware support enabled.

  • The configuration in BALCFG format

    • If the configuration includes a packaged firmware the firmware won't be included on the ConfigCard due to space limitations.

  • Target readers with the following firmware:

    • If legacy firmware support is enabled:
      • Any firmware version
    • If legacy firmware support is disabled:
      • 1100 v2.00 or above
      • Custom firmware originally created as of November 2021

Create ConfigCard

  1. Connect a reader to your computer.

  2. Open BALTECH ConfigEditor.
    If you haven't installed it yet, you can download it here as part of BALTECH ToolSuite.

  3. Open your BALCFG configuration file.

  4. Click Deploy Config > Create ConfigCard.
  5. Place a BALTECH ConfigCard on the reader.

Screenshot: ConfigCard dialog in BALTECH ConfigEditor

The configuration is being transferred to the card.

When you see the success message, you can take the card off the reader and use it to deploy the configuration to other readers.

Screenshot: ConfigCard created in BALTECH ConfigEditor

Got a warning message instead?

You get a warning if the configuration is still a draft version. While it's possible to load a draft to a ConfigCard for testing, we highly recommend you release a version of the configuration when testing is completed, and only use ConfigCards with the released version for productive deployment. This helps you later to keep track of the configuration versions in the field.

Back to top