Skip to content

Deploy configuration via Wireless Upload with BALTECH Uploader

For this deployment method, connect a transfer reader to a laptop and upload the configuration via the transfer reader to the target reader over NFC.

Diagram: Wireless Upload of a configuration via a transfer reader connected to BALTECH Uploader

Equipment & requirements

  • Laptop with BALTECH Uploader v4.26 or above
    If you haven't installed it yet, you can download it here as part of BALTECH ToolSuite.
  • Deployable configuration file, exported in BEC2 format
  • Transfer reader: ID-engine ZB Brick, ISO/MIFARE product line (10115)

    The LEGIC product line (10117) as well as legacy readers with a firmware ID other than 1100 will not work.

  • Target readers with the following firmware:

    • 1100 v2.00 or above
    • Custom firmware originally created as of November 2021

Perform Wireless Upload

  1. Connect the transfer reader to the laptop.
  2. Open BALTECH Uploader.
    If you haven't installed it yet, you can download it here as part of BALTECH ToolSuite.

  3. Click Browse... in the top right and select the BEC2 file to deploy.

    My configuration consists of several files.

    In this case, first deploy the file with the host interface configuration, and afterwards the file with RFID interface configuration (i.e. the configuration for the card type). If you do it the other way round, the reader won't accept the host interface configuration.

  4. Click Start Wireless Upload.

    Starting Wireless Upload will trigger a tamper alarm. During the upload, the communication with the host will be interrupted.

    Screenshot: Start Wireless Upload in BALTECH Uploader

  5. The transfer reader now starts searching for a target reader.

    Screenshot: Transfer reader searching for a target reader in BALTECH Uploader

  6. Position the transfer reader on top of the target reader and align antenna centers (i.e. card symbols on front stickers). Tolerance is 10 mm max. in each direction.

  7. Once the target reader has been detected, the upload starts automatically.

    Screenshot: Progress of Wireless Upload in BALTECH Uploader

  8. When the upload is completed, remove the transfer reader from the target reader and confirm the info message on the screen. The transfer reader then starts searching for the next target reader.

Automate this process

To automate deployment, you can invoke Uploader from your own application or script.

LED and beeper signaling during upload

Diagram: Feedback pattern of BALTECH readers during Wireless Upload

Error prevention & troubleshooting

Avoid interruptions

If the file to upload includes a packaged firmware, the process may take up to a minute. To avoid interruptions, keep the readers as close as possible to each other and their antenna centers aligned until the target reader's LED turns green.

Resume an interrupted upload

An interrupted upload is indicated by LED and beeper as shown in the diagram above. Besides, you'll see the following message in Uploader. To resume the upload, reposition the transfer reader on the target reader within 15 seconds.

Wireless Upload interruped in BALTECH Uploader

Repeat an aborted upload

If an upload is permenantly aborted, e.g. due to a power outage, we highly recommend you repeat the upload, even if the reader reboots normally. This is to ensure the new firmware has been loaded completely and is fully functional.

Repeating the upload is mandatory if the target reader displays one of the following LED patterns after reboot:

  • Yellow LED, followed by red flashes
    Diagram: Feedback pattern 2 of BALTECH readers after Wireless Upload has failed and reupload is mandatory

  • Red flashes
    Diagram: Feedback pattern 2 of BALTECH readers after Wireless Upload has failed and reupload is mandatory

For more details, please see this troubleshooting entry.

Other errors

  • If the target or transfer reader's LED turns red, please see the corresponding error message on the screen. For many errors, you can find more information in our troubleshooting guide.

  • If the reader doesn't respond at all, please see this troubleshooting entry.

Integration in ACCESS200 installation workflow

To see how config deployment fits into the full installation workflow for ACCESS200, please refer to the full installation guide.