Roger OSR88M-IO User manual

Roger Access Control System
OSR88M-IO Operating Manual
Product version: 1.0
Firmware version: 1.0.8.205 or newer
Document version: Rev.B

OSR88M-IO Operating Manual.doc 20/10/2023
2/18
1. DESIGN AND APPLICATION
The OSR88M-IO is an identification terminal dedicated to work with an access controller that supports the
OSDP v2.2 protocol. The terminal is equipped with colour graphic display, sensor type keypad, 4 function
keys and MIFARE Ultralight/Classic/DESFire/Plus/ reader. Users can identify at the terminal with PINs,
MIFARE cards or mobile devices equipped with NFC (Near Field Communication) and BLE (Bluetooth Low
Energy) interfaces. MCT88M-IO can be connected to RS485 bus of MC16 access controller using the
additional MCI-3-LCD interface. When connected to MC16 controller it can be operated as access control
terminal, Time&Attendance terminal and additionally it can be used to control the system especially in
regard of building automation offered by RACS 5.
Characteristics
•Access terminal supporting OSDP v2.2
•Colour graphic display
•MIFARE Ultralight/Classic/DESFire/Plus cards reader
•NFC and BLE mobile identification
•Touch type keypad
•4 function keys
•3 inputs
•2 transistor outputs
•1 relay output
•RS485 interface
•Dimensions: 155,5 x 85,0 21,5
•CE
Power supply
The terminal requires power supply voltage in range of 11-15VDC. It can be supplied from MCX2D/MCX4D
expander of MC16-PAC-KIT, from MC16 access controller (e.g. TML output) or from dedicated power
supply unit. The supply wire diameter must be selected in such way that the voltage drop between supply
output and the device would be lower than 1V. The proper wire diameter is especially critical when device is
located in long distance from the supply source. In such a case the use of dedicated power supply unit
located close to the device should be considered. When separate power supply unit is used then its minus
should be connected to controller’s GND by means of signal wire with any diameter. It is recommended to
use UTP cable for connection of device to controller. The table below shows maximal UTP cable lengths in
relation to the number of wires used for power supply.
Table 1. Power supply cabling
Number of UTP wire pairs for power supply
Maximal length of power supply cable
1
150m
2
300m
3
450m
4
600m

OSR88M-IO Operating Manual.doc 20/10/2023
3/18
Fig. 1 OSR supply from MC16 access controller
Fig. 2 OSR supply from dedicated power supply unit
OSDP bus
The communication method with access controller is provided via the OSDP protocol on the RS485 bus.
The device can be connected directly to access controllers supporting this bus. However, for the MC16
controller, it is additionally necessary to use the MCI-3-LCD interface. The bus topology can be freely
arranged as star, tree or any combination of them except for loop. The matching resistors (terminators)
connected at the ends of transmitting lines are not required. In most cases communication works with any
cable type (standard telephone cable, shielded or unshielded twisted pair etc.) but the recommended cable
is unshielded twisted pair (U/UTP cat.5). Shielded cables should be limited to installations subject to strong
electromagnetic interferences. The RS485 communication standard used in the RACS 5 system guarantees
proper communication in a distance of up to 1200 meters as well as high resistance to interferences.
Note: Do not use more than single pair in UTP cable for RS485 communication bus.

OSR88M-IO Operating Manual.doc 20/10/2023
4/18
Display
The terminal is equipped with colour display (4 lines, 16 characters each). The display can be configured in
regard of background and font colours within low level configuration (RogerVDM) and in regard of displayed
information within high level configuration by means of Display command in VISO software navigation tree
which is explained in AN011 application note.
Moreover, default functions key icons, splash screen and screensaver can be replaced using device
memory card. Four new icons must be copied to ICONS folder on memory card (fig. 6) and they must be
named as icon_001.bmp, icon_002.bmp, icon_003.bmp and icon_004.bmp. Splash screen file in the same
folder must be named as icon_000.bmp. Screensaver graphics must be named as scrnsvr.bmp and it must
be copied to the main folder of memory card. Icons, splash screen and screen saver must in bmp format
(without alpha channel) and with 24bit colour depth (can be saved with MS Paint). Icon size must be
60x60pixels while splash screen size and screen saver size must be 320x240pixels.
Keypad
The terminal is equipped with numeric touch keypad and backlight. The keypad can be used for user
identification with PIN and for various keypad commands. By default, the key [#] is used for PIN confirming.
Function keys
The terminal is equipped with four touch function keys (fig. 3). Various functions can be assigned to these
keys within high level configuration (VISO) e.g. door bell, Set T&A Mode, Register Guard Tour Event, Set
Automation Node On, etc. Within low level configuration (RogerVDM) function buttons can be enabled.
Fig. 3 LED indicators and function keys
LED indicators
The terminal is equipped with three LED indicators (fig. 3) which are used to signal integral functions and
they can be additionally programmed with other available functions within high level configuration (VISO).
Table 2. LED indicators
Indicator
Colour
Integral functions
LED STATUS
Red/green
Default colour of the indicator is red. If the terminal is assigned to
Alarm Zone then the LED indicates zone arming (red) or disarming
(green).
LED OPEN
Green
LED indicates access granting.

OSR88M-IO Operating Manual.doc 20/10/2023
5/18
LED SYSTEM
Orange
LED indicates card reading and can signal other system functions
including device malfunction.
Note: Synchronic pulsing of LED indicators signifies lost communication with MC16 controller.
Buzzer
The terminal is equipped with buzzer which is used to signal integral functions and it can be additionally
programmed with other available functions within high level configuration (VISO).
Note: LED indicators, speaker and output lines in high-level configuration (VISO) can only be controlled as
on/off. Unlike MCT readers, flashing or cyclic activation is not supported.
Inputs
The terminal offers 3 general purpose inputs of NO, NC and 1 input internally connected to tamper contact.
Input types and electric parameters such as response time and parametric resistors are defined within low
level configuration (RogerVDM). Input functions are assigned within high level configuration (VISO). Multiple
functions can be assigned to the same input at the same time.
Table 3. Input types
NO input
NC input
NO input can be in normal or in triggered state. In
normal state CAcontacts are opened. Input
triggering is caused by CAcontacts closing.
NC input can be in normal or in triggered state. In
normal state CAcontacts are closed. Input triggering
is caused by CAcontacts opening.
Response time
Response time parameter defines minimal impulse time on the input which triggers the input. Each input can
be configured individually in range of 50 to 5000 ms within low level configuration (RogerVDM).
Tamper detector
Built-in tamper (sabotage) detector enables detection of unauthorized opening of device’s enclosure as well
as detachment of the enclosure from wall. The detector is internally connected to the terminal’s input. It
does not require low level configuration (RogerVDM) or any additional installation arrangements but it is
essential to mount front panel in such way as the tamper detector (fig. 6) would firmly press the back panel.
The detector requires high level configuration which consists in assignment of the function [133] Tamper
Toggle on the level of a Main Board of a controller in VISO software navigation tree.
Outputs
The terminal offers 2 transistor open collector type outputs (15V/150mA rated) and 1 relay output with
NO/NC contacts (30V/1.5A DC/AC rated). Electric parameters such as polarity are configured within low

OSR88M-IO Operating Manual.doc 20/10/2023
6/18
level configuration (RogerVDM). Function are assigned to outputs within high level configuration (VISO).
Multiple functions with different priorities can be assigned to the same output at the same time.
Identification
Following user identification methods are offered by the terminal:
•MIFARE Ultralight/Classic/Plus/DESFire proximity cards
•PINs
•Mobile devices (NFC and BLE)
MIFARE cards
By default the terminal 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 card
programming is given in AN024 application note which is available at www.roger.pl.
The technical characteristics of the device are guaranteed for RFID cards supplied by Roger. Cards from
other sources may be used, but they are not covered by the manufactures warranty. Before deciding to use
specific Roger products with third-party contactless cards, it is recommended to conduct tests that will
confirm satisfactory operation with the specific Roger device and software in which it operates.
PINs
The terminal accepts variable length PINs (by default 4-8 digits concluded with [#] key).
Mobile devices (NFC and BLE)
The terminal OSR88M-IO enables user identification with mobile device (Android, iOS) using NFC or
Bluetooth (BLE) communication. Prior to use of BLE/NFC identification on the terminal, within its low level
configuration (see section 4) configure own NFC/BLE authentication factor encryption key and NFC/BLE
communication encryption key while in case of Bluetooth additionally verify if the parameter BLE activated is
enabled. Install Roger Mobile Key (RMK) app on mobile device and configure the same parameters as in
the terminal. Create key (authentication factor) in RMK defining its type and number, then create the same
authentication factor in VISO software (fig. 4) and assign it to the user with adequate Authorisation(s) at the
terminal. When user wants to identify at the terminal using mobile device then key (authentication factor)
can be selected from the screen or with gesture.
Fig. 4 Authentication factor type in VISO software
2. INSTALLATION
Table 4. Screw terminals

OSR88M-IO Operating Manual.doc 20/10/2023
7/18
Name
Description
OUT2
OUT2 output line
OUT1
OUT1 output line
IN3
IN3 input line
IN2
IN2 input line
IN1
IN1 input line
NO
REL1 relay normally opened contact
NC
REL1 relay normally closed contact
COM
REL1 relay common contact
B
OSDP bus, line B
A
OSDP bus, line A
GND
Ground
+12V
12VDC power supply
1,2,3,4,5,6,7,8
Ethernet port

OSR88M-IO Operating Manual.doc 20/10/2023
8/18
Fig. 5 OSR88M-IO installation

OSR88M-IO Operating Manual.doc 20/10/2023
9/18
Fig. 6 Internal side of the front panel
Installation guidelines
•The terminal should be mounted on a vertical structure (wall) away from sources of heat and
moisture.
•Front panel should be attached in such way as the tamper detector (fig. 6) would firmly press the
back panel.
•All electrical connections should be done with disconnected power supply.
•If the terminal and controller are not supplied from the same PSU then GND terminals of both
devices must be connected with any wire.
•Device can be cleaned by means of wet cloth and mild detergent without abrasive components. In
particular do not clean with alcohols, solvents, petrol, disinfectants, acids, rust removers, etc.
Damages resulting from improper maintenance and usage are not covered by manufacturer
warranty.
3. OPERATION SCENARIOS
Connection vis MCI-3-LCD interface
The terminal when connected to MC16 access controller via the MCI-3-LCD interface, can be at the same
time used for access control, Time&Attendance and to control external devices with function keys. The
example of connection diagram for such scenario is shown in fig. 7 where the terminal is connected via the
MCI-3-LCD interface to the MC16 controller. The terminal with MCI-3-LCD interface can also operate with
MC16 controller using MCX2D/MCX4D expanders as in case of M16-PAC-x-KIT series.
In order to support OSDP terminals, it is necessary to run the automatic terminal detection procedure via the
MCI interface. The OSDP terminal detection procedure is described in a separate manual for the MCI-3-
LCD interface.

OSR88M-IO Operating Manual.doc 20/10/2023
10/18
Fig. 7 Typical connection diagram for the terminal and MC16 access controller via the MCI-3-LCD interface.
Direct connection to the OSDP controller
It is possible to make a direct connection of the OSR reader directly to the OSDP controller. An exemplary
connection diagram is shown below.
Fig. 8 Connecting the OSR reader directly to the OSDP controller
4. CONFIGURATION
The purpose of low level configuration is to prepare device for operation in RACS 5 system. In case of
RACS 5 v1 or RACS5 v2 system the address of device must be configured by means of RogerVDM
software or by manual addressing before connection to MC16 controller.