Versions Compared

Old Version 14

changes.mady.by.user Arnout van Wanrooij

Saved on

compared with

New Version Current

changes.mady.by.user MB

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleHow to convert A1/B1 config to API-implementation

If you want to convert A1/B1 configuration to API-implementation, the system must meet the minimum requirements, see Chapter 2.1.

  1. Browse to the menu: Installation | Hardware | Oss manufacturer.

  2. Select the used OSS element in the tree-view.

  3. Change the OSS Version from “A1” or “B1” to “DOM API-implementation“ .

  4. Browse to menu: Installation | Hardware | Node.

  5. Select the DOM OSS Node in the tree-view.

  6. Set the correct settings for the DOM controller see Chapter 4.5.2 .

Note

It is essential to configure the correct provisioner group at the DOM OSS node, as this will transmit the configuration and keys to the BridgeDOM controller.

If an incorrect provisioner is selected, the locks may be programmed with the wrong keys, rendering them incompatible with the existing cards.

  1. Discover the devices by using the wizard or manually see chapter 4.6.1.2.

  2. Set the correct unbound “device address/PHI” to the reader .

  3. image-20241026-124444.png

  4. Synchronize the locks by using the DOM service app see Chapter 3 .

Note

The configuration file and the keys for the bridge are sent via the provisioner in version =>10.04. This is different from older iProtect versions. To set this up correctly, it is necessary to request a key set from TKH.

Info

When migrating a system from A1/B1 to API, all locks must be re-synchronized.

...