2.5.1 MIFARE DESFire RFID

2.5.1.1 Standard OSS Application

2.5.2 Mobile device

This chapter describes both DOM OSS data on card and mobile access. A physical controller line is created for using DOM OSS data on card that can also be used for normal access or mobile access The hardware which is used are:

• Pluto network device.

• Orion door controller.

• Sirius iX card reader which supports BLE.

The on-line hardware is needed to profide the RFID card of a OSS application or to update these cards.

4.4.1 Add Network device for update- and enrollment function

Create a Pluto Network device. The readers connected to this line are used to write (add) an OSS application to the card and to update the cards when a card is presented on the reader before access is granted.

In iProtect, browse to menu: Installation | Hardware | Line.

• Right click in the tree view and click on the icon “Add Line”:

• Save this record.

4.4.2 Add Orion door controller (Node)

In iProtect, browse to menu: Installation | Hardware | Line.

• Select the Pluto line to which the Orion door controller is to be connected. Press right mouse-button: “Add Node”:

• Save this record.

4.4.3 Add online (Sirius) reader

4.4.3.1 Update reader

An update reader is required (per location) to read/write:

• the events (e.g. access granted, no access).

• the battery statuses of offline locks.

• update access rights .

• update the block list.

Browse to the menu: Installation | Hardware | Node.

• Select the Orion door controller Node and open this in the treeview (+).

• Select in the treeview Orion #1-4, prt 1 or prt2. Press right mouse-click, “Add Reader”

• Fill in a logical name for the reader.

• Select the OSS update card data interpretation at the tab “general”.

• Select the correct provisioner group with the OSS update files.

• See for more settings and setting details chapter “Reader dialog details”.

• Save this record.

4.4.3.2 Enrollment reader

An enrollment reader is necessary to provide existing cards with an OSS application.

Browse to the menu: Installation | Hardware | Node.

• Select the Orion door controller Node and open this in the treeview (+).

• Select in the treeview Orion #1-4, prt 1 or prt2. Press right mouse-click, “add Reader”

• Select the correct OSS update card data interpretation at the tab “general”.

• Select the correct provisioner group with the OSS Enrollment files.

• See for more settings and setting details chapter “Reader dialog details”.

• Save this record.

4.6.1 Add device

Although there are several methods to create the hardware, two methods will be described in this chapter.

• The readers with access rights are prepared in iProtect and linked to the device in the Service app.

  • Method 1: Link to existing reader <Prefered>.

• The reader and device are created in the DOM service app.

  • Method 2: Link to a new reader.

4.6.1.2 Link to existing reader

Start by adding manually readers within iProtect.

Browse to the menu: Installation | Hardware | Node.

• Add a reader by clicking with the right-mouse button on the DOM node.

• Click on the icon “add reader”.

• Fill in the logical name of the reader and select the correct card data interpretation.

• If desired, you can adjust the door open time in the "door behavior" tab.

• Once everything has been filled in, you can press the save button.

• You can grant access rights to the reader by adding the reader to the desired reader groups, you can do this in the reader group list under the created reader.

Browse back to the menu: Installation | Hardware | Node.

• Select the DOM Controller Node.

• Open the tab: Other and enable by Installation option the checkbox “Add automatically”.

• Select “Link to existing reader' at the New device (app) option.

• All newly added devices with the dom service app are automatically added to iProtect and linked to the correct reader.

  • After about a minute the device should been enrolled and linked to the reader, and you can also see this on the detail page of the readers.

• The offline sync status will be visible and if everything is correct the status should be changed in a minute to the status “The configuration is synchronized”.

4.6.1.2.1 DOM Service app

Use the DOM service app to add the devices. During this process you can directly link the newly created readers to the correct devices in the DOM service app.

• Synchronize the DOM service app with the DOM controller.

• Add a device by clicking the Devices button and then clicking the + sign in the DOM service app.

• Apply the mobile phone (Android) to the device or present de RF Wake-up card to the device (IOS).

• Click on the OSS-SO-configuration button to link the device to the door (iProtect reader).

• Press on the couple button.

• Follow the instructions in the DOM service app.

Once the new devices have been assigned from the DOM Service app and the app has been synchronized with the DOM controller, the devices will be enrolled and automatically linked to the correct reader in iProtect. After it has been linked automatically, when using mobile access, enable the checkbox “IPROTECT Access”.

4.6.1.3 Link to a new reader

This setup can be done automatically by the system by enabling the auto discovery function.
When a new device is assigned from the DOM Service app, and the app is synchronized with the DOM controller, iProtect will automatically recognize it and assign the preset settings to the device.

Browse to the menu: Installation | Hardware | Node.

• Select the DOM Controller Node.

• Open the tab: Other and enable by Installation option the checkbox “Add automatically”.

• Select “Link to new reader' at the New device (app) option.

• Select the correct Card data interpretation.

• When using mobile access, enable the checkbox “IPROTECT Access”.

• Select a Reader group which can be used during testing the system.

• Start the auto discovery process by pressing on the start button.

4.6.1.3.1 DOM Service app

Use the DOM service app to add a new device.

• Synchornize the DOM service app with the DOM controller.

• Add a device by clicking the Devices button and then clicking the + sign in the DOM service app.

• Apply the mobile phone (Android) to the device or present de RF Wake-up card to the device (IOS).

• Change the name of the device (this will be the reader name in iProtect).

• Press on the couple button.

• Follow the instructions in the DOM service app (sometimes multiple synchronizations are necessary).

When the reader is synchronized, the following is displayed:

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

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.

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.

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 .

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

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

9. 

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