Versions Compared

Old Version 3

changes.mady.by.user Arnout van Wanrooij

Saved on

compared with

New Version 4

changes.mady.by.user Arnout van Wanrooij

Saved on

Key

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

...

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 automaticaly.

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 automaticaly.

6. Migrate the DOM OSS configuration from A1/B1 to API

This section describe how to convert an existing dom DOM OSS configuration (A1/B1) to the API config

Expand
titleHow to convert A1/B1 config to API

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

6.1 Steps to convert A1/B1 to API configuration

  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 bridge 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 Bridge.

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
    image-20241026-124444.png

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

Info

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

...