Versions Compared

Old Version 13

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 update or remove offline devices...

5.1.1 Access rights management

If you want to add or remove access rights to an offline lock, you can do this using the steps below.

Browse to the menu: Installation | Hardware | Reader.

  1. Find the desired reader and unfold the reader with the + sign.

  2. Click on the reader group list, here you can add or remove the desired reader groups.

  3. after After +- one minute the offline synchronization status of the lock will change to "the configuration is not in sync"

  4. Get the configuration with the dom service app by syncing the app with the DOM controller.

  5. Sync the offline device with the DOM service app.

  6. Sync the DOM controller with the DOM service app.

  7. after After +- one minute the offline synchronization status of the lock will change to "the configuration is synchronized".

Info

For more information about Access Rights see this *Access rights in iProtect™ - Knowledge Base - Confluence (atlassian.net) article on our knowledge base.

5.1.2 Remove a device

Browse to the menu: Installation | Hardware | Node

  • Double click on the DOM controller node.

  • Right-click on the reader to be deleted.

  • Press on the button Delete.

  • Open the Device unbound section below the DOM controller node.

  • Select the device and change the state from “coupled” to “not coupled”.

  • Sync the DOM service app with the DOM controller.

  • Sync the offline device with the DOM service app.

  • Sync the DOM controller with the DOM service app.

  • Remove the device from iProtect by using the delete button.

Info

When a device has been successfully removed and properly uncoupled, the device is in freewheel mode.

Warning

Be aware! When removing a device without proper disconnection, the device may enter a state that it can only be disconnected using the master card. In the worst case, the lock must be returned to the supplier.

...

Expand
titleHow to update or remove online devices...

5.2.1 Access rights management

If you want to add or remove access rights to an offline lock, you can do this using the steps below.

Browse to the menu: Installation | Hardware | Reader.

  1. Find the desired reader and unfold the reader with the + sign.

  2. Click on the reader group list, here you can add or remove the desired reader groups.

  3. The device and the RF-NetManager start communication and synchronize the changes automaticalyautomatically.

5.2.2 Remove a device

Browse to the menu: Installation | Hardware | Node

  • Double click on the DOM controller node.

  • Right-click on the reader to be deleted.

  • Press on the button Delete.

  • Open the Device unbound section below the DOM controller node.

  • Select the device and change the state from “coupled” to “not coupled”.

  • The device and the RF-NetManager will start communication and the device will be uncoupled automaticalyautomatically.

6. Migrating from A1/B1 to DOM API-implementation

To take advantage of the new API-implementation and hereby the benefits (see Chapter 1.2), the setting OSS configuration in IPROTECT must be 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.

...