Roger RKD32 User manual

Roger Access Control System
RKD32 Installation Manual
Product version: 1.0
App version: 1.3.2
Document version: Rev. C

RKD32 Installation and Configuration Manual.doc 16.10.2020
2/20
1. DESIGN AND APPLICATION
RKD32 electronic key cabinet enables management of keys or other items e.g. cards, remote control
devices, fobs, etc. The configuration in standalone mode is performed manually with MD70 panel which is
equipped with graphic touchscreen and Mifare card reader or remotely via web browser. The initial
configuration in network mode is performed with MD70 panel while further configuration in regard of users
and authorisation is performed in computer network on the level of VISO management software (RACS 5
system).
Up to four cabinets can be operated with single panel. In such scenario RKD32EXT cabinets are connected
to RKD32 cabinet. Prior to placing keys inside cabinet, they must be firmly attached to included RFID fobs.
RKD32 can recognize fobs so keys can be returned to any unoccupied slot in the cabinet. It is possible to
assign users with authorizations for particular keys. Typically users are identified at the panel with Mifare
proximity cards or PINs. When key is collected then both door lock and fob lock are released and frame
around the key is highlighted in green.
RKD32 cabinet is internally connected in factory and its installation requires only connection of power supply
and wall mounting inside premises.
Fig. 1 RKD32 overview
Characteristics
·Operates standalone or as a part of RACS 5 access control system
·WWW interface for managing the cabinet in standalone mode
·32 key sockets in a single cabinet
·Up to 4 cabinets controlled from the single control panel
·Key blocked mechanically when in a socket
·No extra seal between key and fob required
·Option to use an additional seal between fob an key
·Key identification by Mifare secure sector number
·Continuous socket monitoring
·Event log
·Time dependant authorisations for keys
·Signalization of prolonged key absence
·Free access to keys in office mode
·Key reservation
·Detailed reports on user activities and key circulation
·Emergency key releasing after commission opening the device housing
·Door opening detection
·Enclosure opening detection (tamper)

RKD32 Installation and Configuration Manual.doc 16.10.2020
3/20
·Touch control panel 7”
·Metal cabinet (RAL7016):
·RKD32: 535 x 935 x 183 mm
·RKD32EXT: 535 x 675 x 183 mm
·12V power supply
·Anti-burglary P2 class glass (SG variant)
·Possibility to mount the control panel on the wall (RP variant)
·Integration with fire protection system
·Post-warranty service and spare parts availability: 10 years
·SDK software for integration with third-party systems
Power supply
RKD32 requires 12VDC/2A buffer power supply. The power supply must be connected to connection block
which is wired to +12V and GND screw terminals at RKD board (fig. 4). Battery cannot be directly connected
to RKD32 so the emergency supply (battery, UPS) must be ensured on the level of buffer power supply unit
(e.g. HPSB2512B PSU from Pulsar company). The required emergency operational time of key cabinet(s)
must be considered when battery or UPS is selected.
In case of complete power supply loss, the RKD32 can be supplied from powerbank (min. 2A rated output)
connected to USB cable which is connected to RKD board (fig. 4).
Cabinet
RKD32 cabinet is made of stainless metal sheet which is powder painted in RAL7016 (anthracite grey).
Depending on the version, cabinet’s door can be equipped with tempered glass or P2 class safety glass.
The cabinet dimensions are given in fig. 4.
RFID fobs
The RKD32 includes 32 RFID fobs which are attached to keys or other supervised items. A key can be
attached to the fob manually without any specialized tools. When a key is placed on a ring and the ring is
inserted into a fob then it is not possible to detach the key from the fob without damaging it. This prevents
possible tampering with keys and fobs.
In order to join a key (or other object) with an identification fob, place the key on the metal ring, and then
press the ring so that only the oval part is visible. After joining, verify the correctness of the latch mechanism
by attempting to pull the key from the key fob. Optionally when secured element cannot be applied on the
ring then it can be attached to hole in the fob using wire and seal.
Fig. 2 RFID fob

RKD32 Installation and Configuration Manual.doc 16.10.2020
4/20
MD70 panel
Management of RKD32 is performed by means of MD70 panel. Single panel can be used to control up to 4
cabinets, each with 32 slots for RFID fobs and keys. The next cabinets (RKD32EXT) are connected to the
main cabinet (RKD32) using RJ45 sockets on RKD boards (fig. 7). Connections can be ensured with U/UTP
cat. 5 cable but the maximal cable length cannot exceed 5m. MD70 panel is equipped with graphic touch
screen, sounder and Mifare card reader. More information on the panel is given in its Operating Manual
which is available at www.roger.pl.
Identification
Following user identification methods are offered by the panel:
·MIFARE Ultralight/Classic/Plus/DESFire proximity cards
·PINs
·RFID fobs
MIFARE cards
By default the panel reads serial numbers (CSN) of MIFARE cards but it is possible to program cards with
own numbers (PCN) in selected and encrypted sectors of card memory. The use of PCN prevents card
cloning and consequently it significantly increases security in the system. More information on MIFARE
cards with PCN is given in section 7 and in AN024 application note which is available at www.roger.pl.
PINs
The panel accepts variable length PINs (by default 4-16 digits). PIN entered with keypad must be concluded
with # or OK key.
RFID fobs
If the option Quick key return mode is enabled (table 2) then key fob can be used for identification at MD70
panel to open the door and return the key to unoccupied slot. The recommended method of fob reading at
the panel is shown below.
Fig. 3 RFID fob reading at MD70 panel
Other proximity cards and biometrics
User can be identified at MD70 panel with other methods if additional external reader is connected. Any
MCT series reader or RFT1000 fingerprint reader can be used for that. Such reader must be configured with
ID=915 address and connected to RS485 A and RS485 B screw terminals of MCX4D module.
If it is necessary to apply identification method which is not offered by Roger then external reader with
Wiegand interface can be connected. In such scenario an additional MCX102 expander with ID=915
address must be installed inside the cabinet. Wiegand reader can be connected to IN1 (D0 line) and IN2

RKD32 Installation and Configuration Manual.doc 16.10.2020
5/20
(D1 line) screw terminals of the expander while the expander is connected to RS485 A and RS485 B screw
terminals of the MCX4D module.
Connection with intruder alarm system
RKD32 is equipped with tamper detectors which enable detection of cabinet enclosure opening. Additionally
tamper detector is located inside MD70 panel. Opening of RKD32 or MD70 enclosure is signalled on LCK4
transistor output of MCX4D board (fig. 8). Door ajar warning is signalled when user becomes logged out
(manually or automatically) to the panel’s starting screen. The warning is generated acoustically by MD70
panel for the time specified by the parameter Door open too long prealert time (table 2). If the door remains
opened when time elapses then BELL4 output of MCX4D board is activated for 3 minutes or till door closing.
BELL4 output is activated immediately also when door is opened by force. Both LCK4 and BELL4 outputs
can be connected to intruder alarm system, siren or other alarm device.
Connection with fire alarm system
In case of fire alarm detection or any other emergency situation, the RKD32 can release all locks to enable
key collecting by any person without authorisation. Such release requires connection of fire alarm system
output to DR3 screw terminal of MCX4D board. As long as output line is activated, door lock and key fob
locks are released. In such scenario the option Fire alarm support (fobs released) (table 2) must also be
enabled.
2. INSTALLATION
Two people are required for the installation of RKD32. Before installation, turn both locks shown in fig. 4
simultaneously to detach back cover. Connect and lead all cables through cable hole in back cover and then
mount the cover on wall according to fig. 6 using holes shown in fig. 5. When RKD32 is mounted on back
cover as in fig. 6 then both locks will latch automatically. The communication with RKD32 in network mode
and via web browser can be provided through Ethernet or Wi-Fi connection (more information on
configuration of MD70 network parameters is given in its manual). appropriate authorization.
Caution: After changing the number of cabinets (e.g. adding RKD32-EXT), start device scanning (Settings /
Configuration / Detect devices, in order to properly handle all slots.
Fig. 4 Inside RKD32 with back cover removed

RKD32 Installation and Configuration Manual.doc 16.10.2020
6/20
Fig. 5 Back cover
Fig. 6 Wall mounting

RKD32 Installation and Configuration Manual.doc 16.10.2020
7/20
Fig. 7 Connection of additional cabinets (RKD32EXT) to main cabinet (RKD32)
Fig. 8 RKD and MCX4D boards
Table 1. Screw terminals and sockets
Terminal/
socket Description
+12V 12VDC power supply
GND Ground

RKD32 Installation and Configuration Manual.doc 16.10.2020
8/20
BELL4 15VDC/1A output line for door alarms
LCK4 15VDC/1A output line for tamper alarms
DR3 Input line for connection of fire alarm system (emergency release of door and key locks)
MASTER RKD32: USB type A socket for connection of pendrive*
RKD32EXT: RJ45 socket for communication with RKD32
BOX-2 RJ45 socket for connection of second module (RKD32EXT), only at RKD32
BOX-3 RJ45 socket for connection of third module (RKD32EXT), only at RKD32
BOX-4 RJ45 socket for connection of fourth module (RKD32EXT), only at RKD32
* In newer RKD32 models, MASTER socket is available inside key chamber after door opening in the right
bottom corner (fig. 9).
Fig. 9 USB MASTER socket
3. RAACA APP
After connection of power supply, the MD70 panel will start RAACA app. When started for the first time the
panel will offer to create default Master user with 9999 password. You must also select the operating mode
of the device:
·Any fob position: keys can be returned to any socket
·Fixed fob position: each key is assigned a socket to return it to
Additionally, for the SH option, select the "Depository equipped with a shutter" option, and for the ND option,
"Depository without door". Then app can be accessed with 9999# password (if created) or with 12345*
administrator password. The administrator account is intended for the installer or the person who manages
the system i.e. for maintenance and service purposes. Daily service and configuration of RKD32 should be
done by means of user account with the appropriate authorization.
Caution: Both default passwords should be changed to your own passwords as described in section 7.

RKD32 Installation and Configuration Manual.doc 16.10.2020
9/20
Fig. 10 Default starting screen
Fig. 11 Main menu
When in the top right corner is selected then Alarm Center is started. It shows all alarm events (forced
opening, tamper, etc.) registered by RKD32 in selected time range. The colour of icon corresponds to
following statuses:
·White: No unconfirmed alarms.
·Orange: Alarm(s) from the past is/are in the memory of device.
·Red: At least one unconfirmed alarm is still on.
When is selected then office mode will be started after returning to the starting screen. In office mode
door lock and key locks are released indefinitely but keys which are reserved with blocking will not be
released. Office mode can also be automatically started and finished by schedule which can be defined in
Settings window (fig. 13) and assigned with the command Office Mode schedule (table 3).

RKD32 Installation and Configuration Manual.doc 16.10.2020
10/20
When is selected then Report Center is started as in fig. 12. After selection of Events tile it is possible to
browse, events (e.g. user login, key collecting, etc.) and after selection of in the same window it is
possible to delete and export events registered by RDK32. Key Report and User Report enable to display
respectively events related to particular key and events related to particular user. In both cases events can
be exported. Database Report displays list of users with their cards and PINs and their Authorisations.
Events in Report Centre can be exported to pendrive connected to MASTER USB socket (fig. 9), exported
to internal memory or sent by email according to settings in Configuration window (table 2). Available
formats are Excel (XLS) and PDF.
Fig. 12 Report Centre
When is selected in top right corner of the main menu then statuses of keys in the system are
displayed. It informs what keys are collected, by whom and which keys are reserved.
When is selected then settings window is displayed as in fig. 13.
Fig. 13 Settings window
Keys
When selected then the list of keys enrolled in the system is displayed. New key can be enrolled by
selection of Add command and then by reading fob at MD70 reader or inserting the fob into one of
unoccupied slots. Editing and deleting can be done by long clicking of an object on the list.