1. GENERAL INFORMATION AND SCP SPECIFICATIONS

This document describes the structure and operating principles of the SCP with 1.4.X version (hardware version (HW)/firmware version/firmware revision).

Due to the improvements in the system functionality, the version and (or) revision of the built-in firmware of the SCP can be changed. The SCP version is displayed in the oLoader II and Control NOVA II software. We strongly recommend updating the firmware to the latest version before installing the SCP.

1.1 Purpose of SCP

The SCP is intended for autonomous or central monitoring protection of premises.

The system can be controlled by local access devices (X-Pad and X-Key) and remotely via the Internet using the Control NOVA II software.

The SCP can transmit information about the state of the system to the CMS, the Control NOVA II software, by SMS messages, and a control call to the specified user phone numbers.

The SCP is intended for continuous operation in the premises with controlled climatic conditions with no direct influence of climatic factors of the environment.

1.2 System composition

1.2.1 SCP

Depending on the requirements of the protected object, wireless detectors, keypads and sirens are connected to the SCP.

Main power source – general network (230 V, ~50 Hz).

In case of no main power supply, the SCP case has a built-in battery with a capacity of 2600 mA·h. The SCP can work from a fully charged battery for ~24 hours. The battery is fully charged in 8 hours.

Alternative power supply – USB Type-C input (5V/1A). It can be used instead of the main power supply or simultaneously with it.

The main power fault occurs only when there is no main and alternate power supply. The SCP can be powered via the USB Type-C input both from a USB-adapter and from a Power Bank.

1.2.2 Compatible devices

Up to 64 wireless devices can be connected to the SCP.

Detectors (up to 64):

• X-Shift – wireless opening detector (for windows and doors);
• X-Shift+ – wireless opening, shock, and tilt detector (for windows and doors);
• X-Motion – wireless motion detector;
• X-Motion+ – wireless motion and glass break detector;
• X-Motion Alarm – wireless motion detector with sounder;
• X-Water – wireless water leak detector;

Key fobs (up to 32):

• X-Key – wireless key fob;

Keypads (up to 4):

• X-Pad – wireless keypad;

Sirens (up to 4):

• X-Siren – wireless outdoor siren;

Repeaters (up to 4):

• X-Cover S^[1] – wireless radio signal repeater.

[1] One repeater supports up to 4 wireless devices for amplification.

1.2.3 Communication modules

The SCP is equipped with following built-in modules for communication with the CMS and Tiras CLOUD II service:

Wi-Fi provides communication via a wireless 2.4 GHz Wi-Fi network (IEEE 802.11 b/g/n). The protection of information transmitted over the Wi-Fi channel is provided by WPA PSK and WPA2 PSK technologies. The SCP connects to the Internet via the Wi-Fi access point specified in the settings.

GSM ensures communication via the GSM (GPRS) network using 2G technology. The module provides the possibility to send SMS messages and make a control call to the user’s mobile phone.

When M-WiFi and GSM communication modules operate simultaneously, Wi-Fi communication is prioritized.

1.3 Specifications

The SCP specifications are given in Table 1.1.

2. SYSTEM INSTALLATION

All electrical connections should be made only when the power supply is switched off.

2.1 System installation plan

Before installation, we strongly recommend designing the system: the SCP, keypads, detectors, sirens, and other devices. Thick walls, metal partitions, mirrors, etc. reduce the range of GSM, Wi-Fi signal and wireless devices. It should be considered when choosing the place for the SCP mounting. The location of the SCP and other system devices should be within the detector-covered area.

2.2 Location of devices

The SCP and devices (except X-Key and X-Water) are intended for wall mounting. The SCP and devices are installed on the bracket fixed to the flat surface by screws. The location of the holes on the SCP allows it to be fixed to the socket box. The detachable element on the bracket of the SCP enclosure (see Figure B.1, Appendix B) and other devices is used to detect detachment from the wall. It should be fixed to the wall with a screw. When the SCP bracket is detached from the wall, the detachable element remains on the surface, which leads to tampering.

The installation dimensions of the SCP are shown in Figure B.1, Appendix B.

2.3 Main power connection (230V)

All installation and connection works should be completed before the power supply is switched on. A separate 230V power supply line protected by a circuit breaker with the parameters in accordance with the specifications of the SCP should be available at the SCP installation place. The SCP is supplied with the main power cable with an EU standard Type C plug that is already connected to it. To supply the main power of the SCP, it is necessary to insert the plug into power outlet (EU type C or F) of the 230 V network.

If necessary, another cable for the SCP main power supply may be used. We strongly recommend using the cable with a conductor cross-section of at least 0.5 mm².

Before connecting the main power cable to the SCP connector, make sure that there is no voltage on the cable conductors.

The main power is connected via the connector on the SCP board. The cable conductors are connected to the removable part of the connector (Figure 2.1). The insulated area of the cable conductors should not protrude beyond the joint (recommended insulation stripping length is 8 mm).

Figure 2.1 – Connecting the cable to the connector

The detachable part of the cable connector is connected to the AC 230V connector on the SCP board (Figure 2.2). After connecting, the plug and the power cable should be attached to the case using the screws and protective cap provided with the SCP.

Figure 2.2 – Connecting the 230 V connector

Do not disconnect the connector by pulling on the power cord.

2.4 Devices installation

Before installing wireless devices (detectors, keypads, and sirens), they should be added according to sections 4.1.

After adding devices, it is necessary to check the possibility of transmitting signals to the SCP from the place of the planned installation.

To check the signal strength, it is necessary to perform a signal test for each wireless device in the oLoader II or Control NOVA II software. If the signal strength is unsatisfactory or the SCP does not receive signals from the wireless device, it is necessary to change the location of the device. Once a good or satisfactory signal strength is achieved between the SCP and the wireless device, it can be installed in the location.

When tampering with the SCP, the keypad or detector, the siren is activated only if there are armed detectors with the set “Security”, “Entrance door” or “Corridor” mode in the system.

2.5 “Start” button functions and SCP indication

The SCP is turned on after pressing and holding the  “Start” button for 3 seconds.

Depending on the time the  “Start” button is pressed, one of the service functions described in Table 2.1 is performed. To select a specific function, release the button while the TIRAS logo flashes in the corresponding color. The execution of the command is confirmed by the double flashing of the logo in the same color.

In autonomous mode, the TIRAS logo displays the current state of the SCP (see Table 2.2).

Table 2.1 – “Start” button functions

Pressing type (in standby mode)	Indication	Reaction
Pressing and holding for up to 3 s	Indicator does not light	Button press is ignored (no reaction)
Holding from 3 s to 10 s	Blinking green	Switching off the SCP (the TIRAS logo gradually goes out – the SCP switches off)
Holding from 10 s to 15 s	Blinking yellow	Resetting user codes
Holding from 15 s to 20 s	Blinking blue	Resetting the SCP communication channel settings
Holding from 20 s to 25 s	Blinking violet	Resetting to factory settings
Holding longer than 25 s	Turning off the status indication	Exit function selection mode

2.6 Working with GSM module

The SCP is equipped with a built-in GSM-module. For the SCP to work via the GSM (GPRS) channel, install SIM cards in the holders (Figure A.1, Appendix A). After the SIM cards installation, it is necessary to check the GSM signal strength for each SIM card. After installing the SIM cards, it is necessary to check the signal strength of the GSM network for each SIM card. The gradation of the signal strength is given in Table 2.3. The GSM signal strength can be viewed on the keypad or in the Control NOVA II and oLoader II software.

If the test does not show a sufficient GSM signal strength (3 flashes of the SIM indicator) with the built-in antenna, or the unstable operation of the GSM channel is observed during the SCP operation, we strongly recommend using an additional Wi-Fi channel or connecting an external GSM antenna to the SMA connector (Figure A.1, Appendix A).

For the SCP to start working with the external antenna, it is necessary to enable this option in the SCP settings using oLoader II software: SCP Settings → Connection → GSM antenna → External. This option can be enabled only after the connection of the external antenna to the connector.

It is not recommended to install the antenna near sources of powerful electromagnetic radiation (electric motors, X-ray machines, etc.).

Installation/removal of the SIM card should be carried out only when the SCP is switched off.

2.7 Working with Wi-Fi module

The SCP is equipped with a built-in Wi-Fi module (2.4 GHz). For the SCP to work via the Wi-Fi channel, set the network settings using oLoader II software. The Wi-Fi signal strength can be viewed on the keypad or in the Control NOVA II and oLoader II software. The gradation of Wi‑Fi signal strength is given in Table 2.4.

2.8 Working with wireless devices

The SCP operates with the wireless devices. The gradation of the signal strength of the wireless devices is given in Table 2.5.

If the test does not show a sufficient signal strength of the wireless devices or the unstable operation is observed during the SCP operation, we strongly recommend bringing the wireless device into the range of ​​the SCP and choose a permanent place of operation with the best signal strength.

2.9 Complex inspection after installation

After setting the SCP at the premises and after each subsequent change in its configuration, we strongly recommend checking the SCP operation via all communication channels to eliminate the possibility of improper downloading of the settings and equipment malfunctions.

To verify the system’s proper operation after installation, it is necessary to perform the following tests:

1. Make sure that the SCP transmits the messages listed below to the CMS and/or Tiras CLOUD II, alternately in each configured communication channel (each SIM card, Wi-Fi):
   – change of the security mode (armed/disarmed) using each registered user access ID;
   – transition to armed mode of each detector of the system;
   – generation of alarm message in case of triggering each detector and interference with the tamper of each device in the system.
2. Make sure that the enclosures of all detectors, keypads, sirens, and the SCP during system operation are closed.

For tamper detection, the “Tamper control” option should be enabled.

2.10 System operability

As a result of the failure of any of the system devices, the level of protection decreases. Devices installed outdoors (for example, outdoor sirens) are exposed to adverse environmental effects. Atmospheric phenomena, such as thunderstorms or atmospheric lightnings, may damage devices connected to electrical systems.

The SCP is equipped with a range of protective solutions and automatic diagnostic functions that check the system’s operability. Fault detection is indicated by the  LED on the keypad and is transmitted to the CMS. It is necessary to respond to such a situation in time and, if necessary, consult the system installer.

For the device to meet the Grade 2 safety grade, you need to configure:

• indication of the system status and zones status is available only after entering the access code, therefore, the permanent indication of the keypads must be disabled;
• generation time of “CMS connection malfunction” message should be less or equal to 2 minutes;
• it is not allowed to disable tamper protection of the devices;
• user access IDs must consist of at least 4 digits;
• if there is any fault in the system, group arming is allowed only for the users having the “Ignore faults” authority;
• alarm sounding time must be at least 90 seconds;
• entry delay should not exceed 45 seconds;
• auto-arming delay of the hold-up button must be at least 180 seconds.

3. SYSTEM CONFIGURATION

The SCP can be configured with Windows PC/MacOS or Android device with installed oLoader II software.

3.1 Configuring SCP using oLoader II software

oLoader II is a special software that is intended to configure the SCP. The Windows PC/MacOS versions are available for download on the manufacturer’s website: tiras.technology in the Software section. The Android version is available in Google Play. A detailed description of the SCP settings in the oLoader II software is given in section 3.2.

The SCP may be configurated only in remote mode using the oLoader II software via the Tiras CLOUD II service. The local SCP setting is not available.

The remote SCP configuring is possible when it works with the Tiras CLOUD II service and requires the connection of the Windows PC/MacOS or Android device to the Internet.

For remote configuration of the SCP, you need to do the following:

1. launch the pre-installed oLoader II software – the registration window opens to create an account or log in;
2. configure one of the communication channels for the SCP:
   – set a Wi-Fi access point in the mobile phone or other device with available Internet traffic according to Table C.1 (Appendix C). Access point name – TIRAS, password – 12345678;
   – install a SIM card with available Internet traffic in the SIM1 slot (while doing this, the SCP should be disconnected from the power supply).
3. power on the SCP and wait for the SCP connection to the Wi-Fi or GSM network and establishment of a communication with the Tiras CLOUD II server (see Table 2.2);
4. add the SCP to the Tiras CLOUD II account within 10 minutes after its start. To add the SCP, do the following in the oLoader II software:
   – in the “Objects” window, click the “+” button (add);
   – in the “Device serial number” field, enter the 9-digit serial number of the SCP;
   – in the “Access code” field, enter the default installer access code (9-digit serial number of the SCP);
   – in the field “Object name”, enter the name of the object (from 1 to 50 characters);
   – click the “Add” button.
5. select the required SCP from the list of objects and enter the current installer code (after entering the installer code, the settings from the SCP will be downloaded to the oLoader II software);
6. change the SCP settings.

Changing the SCP settings is possible if the groups or detectors are disarmed; the state of the 24-hour detectors does not affect this.

3.2 Description of SCP settings

3.2.1 Communication settings

The communication settings include the settings of the Wi-Fi, SIM cards, CMS, and service Tiras CLOUD II.

3.2.2 System and security settings

The system and security settings are described in the tables below.

3.3 Description of devices settings

3.3.1 Detectors

Up to 64 detectors can be configured to work with the SCP.

^[1] For X-Water, the option “Communication test interval” can be set from 30 to 3590 seconds.

3.3.2 Key fobs

Up to 32 key fobs can be configured to work with the SCP.

3.3.3 Keypads

The SCP supports up to 4 X-Pad keypads.

3.3.4 Sirens

The SCP supports connection up to 4 X-Siren sirens.

3.3.5 Repeaters

The SCP supports operation with up to 4 X-Cover S repeaters.

3.4 Settings of groups

The groups are set with the help of “Use group mode” option (disabled by default) located in the “About object” tab.

3.4.1 “Use group mode” option is disabled

Disabling the option leads to the following changes:

• “Groups” settings tab – unavailable;
• all security detectors are armed and disarmed together;
• all users are authorized to access the whole system (to all detectors);
• user can arm/disarm/review the whole system at the same time;
• when added to the system, 24h detectors are automatically assigned to all previously created users;
• when a new user is created, he is automatically granted authority to manage existing system detectors.

For premises that require more complex configuration, you can enable “Use group mode” in the “About object” tab.

3.4.2 “Use group mode” option is enabled

When the option is enabled, the “Groups” settings tab appears, after that the Installer can distribute detectors and authorities. Group settings and new user settings become available in the oLoader II software.

Enabling the option leads to the following changes:

• all security detectors remain in Group 1;
• all users have access and authority to Group 1;
• all users have access to 24h detectors;
• sirens assigned to all groups and 24h detectors.

Up to 16 groups can be created in the system. Additional parameters can be specified for each of the groups.

If the Use group mode option is disabled, system will return to operation according to p. 3.4.1.

3.5 User settings

Up to 32 users can be created in the system. The “Installer”, “Installer with administrator rights” and “Administrator” users have special authorities.

4. INSTALLER OPERATIONS WITH DEVICES

4.1 Wireless device adding

Wireless device should be added and activated to work with the SCP. To add the wireless device, the following steps should be carried out:

• select the “Devices” tab in the oLoader II software;
• press the “+” button;
• enter the serial number of the device or scan the QR code;
• select the operation mode (only for the detectors and key fobs);
• enter the device name;
• press the “Start” button on the device (or any button on the X-Key) when the activation timer starts.

After pressing the “Start” button  (or any button on the X-Key), the device will enter the activation mode and start searching for the SCP that is in the adding mode. The indication on the device during the SCP search is shown in Table 4.1.

If after pressing the Start button the device does not display the indication according to Table 4.1, but only one short flashing of the LED, this indicates that this device has already been added to another SCP. In this case, you need to perform the procedure of deleting the device (see section 4.2.2), after which try to activate it again.

As a result of the search for the SCP, the indication will be generated on the device according to Table 4.2.

4.2 Wireless device deleting 

There are two ways to delete the wireless device: deleting using the “Start” button or the oLoader II or Control NOVA II software.

4.2.1 Deleting using oLoader II or Control NOVA II software

The system installer can delete the device by means of the oLoader II software. To delete it, it is necessary to go to the “Devices” tab, select the required device from the list and click  “Delete”.

The wireless device can be deleted by the administrator or installer by means of the Control NOVA II software. To delete the device using the Control NOVA II software, you should log in, go to the “Wireless devices” menu, select the required device from the list and select the  “Delete” item.

The device is deleted from the settings, and the SCP sends it a delete command. After receiving the command, the device resets to the factory settings and turns off (if it is in the SCP range). For X-Key to receive the delete command, press any button on it while it is in the range of the SCP signal.

In case of communication fault with the SCP during deletion, the device will not receive the delete command and will remain added. For further use of the device, it must be deleted using the Start button (see section 4.2.2).

After deletion, the device will confirm the received command (see Table 4.3).

4.2.2 Deleting using the “Start” button

To delete the device (except X-Key), press and hold the “Start” button until it flashes twice (6 seconds), then immediately release the “Start” button.

To delete the X-Key, press and hold the  and  buttons simultaneously (5 seconds) until the red indicator lights up for a long time, then release the  and  buttons. During next two seconds (while the red indicator lights up), briefly press the  button.

If there is communication with the SCP when using the “Start” button for deletion, the SCP will receive the corresponding command and deactivate it.

The indication on the device when deleting using the “Start” button is given in Table 4.3.

4.3 Switching on wireless device

To turn on the activated device, remove it from the bracket and press the  “Start” button. The indication of activation is given in Table 4.4.

If the device is not activated, when it is switched on, it will display the indication according to Table 4.1.

4.4 Switching off wireless device

To switch off the activated device, press and hold the “Start” button  until the second short flashing of the indicator (the first flashing occurs when the “Start” button  is pressed). The indication of the successful switching off is given in Table 4.5.

If the device is not activated, it switches off automatically immediately after failed activation.

4.5 Switching on wireless device

4.5.1 X-Key

When the “Hold-up button” is pressed, the alarm message about an attack is transmitted to the Control NOVA II software to all users except the initiator of the action.

The key fob has protection against false presses. To execute the command, it is necessary to press the button from 0.3 to 2 seconds and release it, then the LED indicator on the added key fob will flash one of the following colors:

• green – the command has been transmitted;
• red – the command has not been transmitted (try again);
• two short green flashes – incorrect pressing (the button was held for more than 2 seconds), the command will not be executed.

After the command has been successfully transmitted, the indicator flashes at intervals of 1 second, confirming the command execution:

• short triple flashing of the green indicator – the command has been executed;
• short triple flashing of the red indicator – the command is forbidden to execute.

There is no command execution indication for the “Hold-up button” and when the previous command is repeated.

The key fob set as the “Hold-up button” transmits an attack message when any of its buttons is pressed.

4.5.2 X-Motion

To ensure long battery life, X-Motion generates 5 alarms per security session by default. The detector will respond to motion after repeated or automatic arming. The number of the detector alarms is set using the oLoader II software. If the “Constantly active motion sensor” option (see Table 3.6) is disabled, after receiving the arming command, X-Motion requires ~30 seconds for the PIR sensor to start detecting motion.

4.5.3 X-Motion+^[1]

The oLoader II software allows to set glass break sensor with three levels of sensitivity, as well as to enable the “Activate siren” option with two values for selection: “When motion is detected” and “When glass brake is detected”.

Be careful with the microphone connection cable because it can be easily damaged when replacing the battery (CR123A).

^[1] Except advanced features, it has all the features of X-Motion.

4.5.4 X-Motion Alarm^[1]

X-Motion Alarm has a built-in siren, which can be switched off to preserve the detector battery life. The “Autonomous notification” option activates the siren if X-Motion Alarm is armed and the connection with the SCP is lost.

The following events can be selected to activate the built-in siren^[2]:

• The “Security alarms” option – the siren will be activated when the armed detector is violated.
• The “Device tamper alarms” option – the siren will be activated when the tampers of the devices included in the security system are violated.
• The ” Loss of communication with the detector during guarding” option – the siren will be activated when communication with the predefined detectors is lost. The “State information” option should be configured as “Groups (detectors)”.
• The “Successful arming” option – confirmation of arming from the CMS will be accompanied by the siren activation (one short sound signal).
• The “Disarming” option – the siren will be disabled following two short sound signals before it turns off.

In the detector settings, you can select one of two siren state information options:

• The “Whole system” option – the siren will be activated when any armed group in the system is violated.
• The “Groups (detectors)” option – the siren will be activated when a previously selected armed group or groups are violated.

^[1] Except advanced features, it has all the features of X-Motion.

^[2] In the oLoader II software, the given option is set in “Another indication” item located in the “Built-in siren” tab.

4.5.5 X-Shift

The magnet can be placed both on the right and on the left side of the detector, parallel to its axis. The detector with a magnet can be placed in a vertical and horizontal position. The maximum distance between the magnet and the detector on a non-metallic surface is 15 mm. The maximum distance between the magnet and the detector on the metal surface is 4 mm.

After installing the X-Shift in the place of permanent use, it is necessary to calibrate its magnetic field sensor. X-Shift calibration increases the accuracy of door/window opening detection and detection of tampering with a powerful magnet. The calibration process can be launched in the oLoader II or Control NOVA II software. Calibration is performed with closed windows/door on which the detector is installed.

It is possible to connect a remote LED or an external detector to the X-Shift. To do this, open the X-Shift case and connect the remote LED or the external detector to the terminal connector in the middle of the case. Then, in oLoader II software, when configuring the detector, enable the “Wired connection” option and select the connection type:

• The “External detector” option – when connecting the external detector.
• The “Confirmation LED” option – when connecting the LED. When connecting the LED, it is necessary to consider the wire polarity.

4.5.6 X-Shift+^[1]

It is also possible to select the break sensor sensitivity level if it is enabled. The available sensitivity levels are as follows: high, medium (by default), and low. When the “Ignore single shocks” option is enabled, the alarm is generated only if the sensor detects more than one shock.

^[1] Except advanced features, it has all the features of X-Shift.

4.5.7 X-Pad

For the correct operation of the touch keys of the keypad, there must be no foreign objects on the touch field.

Before entering the access code on the activated keypad, press any button to “wake up the keypad”, a multi-tone signal will sound. 

4.5.8 X-Siren

The siren can operate in two notification modes:

• The “Whole system” option – the siren will be activated when any armed group in the system is violated.
• The “Groups (detectors)” option – the siren will be activated when a previously selected armed group or groups are violated.

In the siren settings, there is a list of event indications that can be enabled:

• The “Device tamper alarms” option – the siren will be activated when the tampers of the devices included in the security system are violated. Additional settings are available: Logo LED lightning and LED indication by contour, Signal volume, and Signal duration.
• The ” Loss of communication with the detector during guarding” option – the siren will be activated when communication with the predefined detectors is lost. The “State information” option should be configured as “Groups (detectors)”.
• The “Armed” option – the siren will be activated according to the settings when the group is armed.
• The “Successful arming” option – the siren will be activated according to the settings when arming is successful with confirmation from the CMS.
• The “Unsuccessful arming” option – the siren will notify about the failed group arming, which may be caused by the failure to arm one or more zones.
• The “Disarming” option – the siren signals when the group is disarmed.
• The “Entry delay” option – the siren will be activated when the entry delay starts.
• The “Unviewed alarms” option – the siren will notify about the presence of unreviewed faults in the system.

In addition, it is possible to customize the logo LED lightning and LED indication by contour, signal volume, and signal duration.

The siren can be also activated when its own tamper is triggered, if there are armed groups in the system. It is impossible to turn off or delete the siren with the button if there are armed groups in the system.

When using an external 12V power supply, the “External supply” option should be enabled in the siren settings.

4.5.9 X-Water

We strongly recommend testing the X-Water at least once a quarter by wetting the sensors (terminal pairs) with water. After the “Water leak” alarm is generated, wipe the detector’s enclosure, sensors, and installation place with a dry cloth.

If the “Confirmation of water leak” option is enabled, the “Water leak” alarm will be generated, when any two sensors (terminal pairs) are triggered.

The “Flip control” option monitors the vertical position of the detector. If the detector is turned over, it will produce sound signals.

The “Displacement control” option monitors the horizontal position of the detector. If the detector is displaced, it will produce sound signals.

When changing the testing intervals of communication with the wireless device from longer to shorter, the communication loss message can be generated before the device accepts the new setting.

4.5.10 X-Cover S

The wireless devices that can be configured for amplification by means of the repeater are as follows: X-Shift, X-Shift+, X-Motion, X-Motion+, X-Motion Alarm, X-Water, X-Siren, and X-Key.

When configuring the wireless devices for amplification, you should first add the repeater and then add the wireless devices, or vice versa. The wireless devices with poor signal strength that have been previously added to the system can also be configured for amplification.

The general configuring algorithm is as follows.

Step 1: Add a repeater and new wireless devices.

Step 2: Select the wireless devices for amplification.

Step 3: For a wireless device to receive settings and start working with the repeater, this device should be brought into the range of the SCP or you should tamper with the device or wait for several communication test intervals.

Step 4: Place the repeater in a possible place of installation and conduct a signal test to determine the permanent place of operation of the repeater.

Step 5: After successful configuration and location of the repeater, move the wireless device to a possible installation location and conduct a signal test to determine the location with the best signal strength for permanent operation of the wireless device.

Specifics of configuring:

1. Adding new wireless devices for amplification and a new repeater.

To add new wireless devices for amplification and a new repeater, you should follow steps 1-5.

2. Adding new wireless devices for amplification to the previously activated repeater.

It is necessary to add new devices and follow steps 2-5 of the general configuring algorithm described above.  After successful activation in the range of the SCP, you should install the wireless device in a permanent place of operation by selecting it with the help of a signal test.

3. Adding existing wireless devices with poor signal strength to a new repeater for connection stability.

 After configuring the wireless device for amplification, it should be brought into the range of the SCP or you should tamper with the device or wait for several communication test intervals for the wireless device to receive the settings and start working with the repeater.

4. Removing the wireless devices from amplification.

After changing the settings, removing the necessary wireless device from the list of devices for amplification, you should tamper with the device, wait for several communication test intervals within the range of the repeater. After that, you should bring the wireless device into the range of ​​the SCP and choose a permanent place of operation using the signal test.

For the X-Key to start working with the repeater, after the configuration of the SCP and the repeater, as well as setting the X-Key for amplification, it is necessary to press any button of the key fob within the range of the SCP. The X-Key works only with the repeater it is assigned to.

5. FUNCTIONS AVAILABLE TO THE INSTALLER

For the installer to access the device functions via keypad, the “Access type” option should be set as “Full”.

Using the keypad, the installer can:

• view system status;
• control security (arming/disarming);
• change one’s own access IDs;
• restart the SCP;
• restore factory settings;
• view the signal strength of the GSM or Wi-Fi network.

5.1 Arming/Disarming

The installer, like other system users, can manage the groups added to him/her, as well as view their status, if this is allowed in his/her authorities. The system management is described in section 6.

5.2 Testing detectors

It is possible to perform a signal test of the detectors and check their status in the oLoader II and Control NOVA II software, in the “Wireless devices” menu.

Testing the activation of the detectors is performed in the Control NOVA II software, in the “Arm” menu. In this case, the detectors or groups of the detectors that need to be checked must be assigned to the installer.

5.3 Restart of the SCP

When the SCP is restarted, the current settings and event log will be saved.

If the SCP restart is performed during the firmware update download process, the firmware update download has to be initiated again.

To restart the SCP by means of X-Pad, enter the combination:

installer access code # 13 # installer access code #

To restart the SCP using the oLoader II software, click the “Reboot” button in the “SCP” settings tab.

5.4 SCP firmware update

The “Auto update software” option (see section 3.2.5) allows the SCP to independently check for firmware update (once a day in normal mode or 10 minutes after switching on), download and install it (if there are no armed groups in the system, as well as power faults).

5.5 Reset to factory settings

When restoring the factory settings, all SCP settings different from the factory ones will be lost. All data about the SCP in the Tiras CLOUD II service will be cleared, and the SCP will be deleted from all Control NOVA II software accounts.

The SCP can be reset to factory settings in one of the following ways:

• press and hold the “Start” button, releasing it when the logo flashes purple (see section 5);
• enter the combination on the keypad: installer access code # 5 # installer access code # .

After using one of the above methods, the device reboots and turns on.

5.6 Communication status

Using the keypad, the installer can check the signal strength of the Wi-Fi network and the GSM signal strength.

5.6.1 View the Wi-Fi network signal strength 

To check the Wi-Fi network signal strength, enter the following combination:

installer access code # 11 #

After entering the combination, indicators 1-4 of the keypad will display the signal strength of the Wi-Fi network as described in Table 5.1.

5.6.2 View the GSM signal strength

To view the current GSM signal strength of the network, enter the following combination on the keypad:

installer access code #  12 #

After entering the combination, the indicators 1-4 of the keypad will display the GSM signal strength of the active SIM-card as described in Table 5.2.

6. SCP CONTROL

The system can be controlled from local access identification devices (keypads, key fobs) and remotely, via the Internet, using the Control NOVA II software.

Access to the SCP functions is provided at four levels:

• 1^st access level (unauthorized user) – access for any person. It is not necessary to enter the access ID; to enter the first access level, it is necessary to wake up the keypad by pressing any key. At the first level, alarm notifications and a warning indication on the keypad ( indicator) are available, if the permanent indication mode is not configured.
• 2^nd access level (authorized user) – access for system users, which is limited by an access ID. The second level displays the system status indication on the keypad indicators (Table 6.1). Users from the second access level can manage the elements added to their settings.
• 3^rd access level (authorized user) – access for users of the “Installer” type. This level provides access to change all system settings.

Users of Administrator type can grant/block access to the 3^rd access level.

• 4^th access level – access level for the manufacturer; the manufacturer can make changes to the devices, equipment design, and built-in firmware of the SCP.

6.1 System control by means of keypads

The SCP supports wireless LED keypads – X-Pad (Figure 6.1).

Figure 6.1 – X-Pad

To work with the keypad, you need to press any button (for 1 s) to “wake up”, after that a multi-tone signal will sound. Controlling the system using keypads takes place after user authorization – entering a valid access code and pressing #. User authorization is confirmed by three short beeps of the keypad buzzer, after that the indicators on the keypad display the current system status according to Table 6.1.

If an invalid access ID is entered, one long sound signal is generated. If the invalid access ID is entered four times in a row, the keypad is blocked for 90 seconds, and the notification about selecting the code is sent to the CMS and the Control NOVA II software.

Table 6.1 – Operating modes of system status indicators on the keypads

Indicator	Access level	No lights	Blinks	Lights
“Attention”	I	No faults and alarms in the system	There are unviewed alarms and/or faults	All available faults and alarms are viewed
	II, III	No user-related faults and alarms in the system	There are user-related unviewed alarms and/or faults	All user-related available faults and alarms are viewed
“Ready”	I	–	–	–
	II, III	Group arming is forbidden	Indication of the steps of access IDs changing	All detectors in the controlled group are in normal mode (detectors with delay can be violated), no faults
“Security”	I	All groups are disarmed	One or more (but not all) groups are armed – partial protection	All groups are armed
	II, III	The controlled group is disarmed	Entry/exit delay	The control group is armed
“Alarm”[1]	I	No alarms	Unreviewed group alarm and/or penetration into the device housing	There are viewed alarms (group alarm, 24h detector, penetration into the device housing)
	II, III	No user-related alarms in the system	Blinking once – unviewed group alarm and (or) penetration into the device housing Blinking twice – unviewed alarm memory (group alarm and/or penetration in the device housing)	There are viewed alarms (group alarm and/or penetration into the device housing)
“Fault”	I	No faults	There are unviewed faults in the system	There are viewed faults
	II, III	No user-related faults in the system	There are user-related unviewed faults in the system	There are user-related viewed faults
“Power”	I	Power of all devices is normal	There is a power fault in the system	The power of all devices is normal
	II, III
Groups or detectors status indication on LED keypads
Indicator state		Detector state		Group state
No lights		Detector is disarmed		All detectors of the group are disarmed
Blinking red (once)		Entry delay in detector		Unviewed alarms in any detector of the group
		A detector is violated and is in alarm
Blinking red (double)		Unviewed memory of alarms in detectors		–
Lights red		Viewed alarm in the detector		Viewed group alarm
		The detector is violated and cannot be
Blinking green		Exit delay for “Entrance door” or “Corridor”		Group exit delay is counted
Lights green		The detector is armed		Group or its part is armed

^[1] The “Alarm” indicator does not display the operation of the detectors of the “Panic button” type at the 1^st access level.

6.1.1 Sound indication of keypads

Each keypad is equipped with a buzzer that emits a sound signal at certain events in the system or actions from the keypad. The operating modes of the keypad buzzer are described in Table 6.2.

6.2 Arming/Disarming

6.2.1 Arming

To arm, it is necessary to do the following:

1. close all doors, windows and rooms in the armed premises. Using available SCP control tools, make sure that the group or detectors are ready for arming;
2. if the detectors with a delay (“Entrance door”, “Corridor”) are not available, it is necessary to leave the premises that are being armed and close the entrance door. If the X-Pad is located inside the armed premises, the detectors with delay (“Entrance door”, “Corridor”) must be configured to ensure the correct setting. The detectors with delay may remain triggered during the exit delay countdown;
3. initiate arming:
   – if there are no detectors with delay, arming will occur immediately;
   – if the group contains the detectors with delay, then during the exit delay, you should leave the room and close the entrance door. When the exit delay expires or when all detectors return to the normal state, the system will be armed.

After arming the group, the notification is sent to the CMS about arming the corresponding detectors, if the SCP has been previously configured to work with the CMS.

Depending on the load of the CMS and the communication channel between the SCP and the CMS, the interval between the execution of arming and the receipt of the confirmation is from 1 to 20 seconds.

If, at the moment of the exit delay, at least one detector of the Entrance door type is triggered, this detector and all detectors of the Corridor type will not be armed. The corresponding detector/group indicators and the Security indicator (Table 6.1) will not light green. In this case, it is necessary to eliminate the cause of the failed arming and try again.

If one group has common detectors or is part of another group, then when arming the first group, the second one will be set as Partial armed. To switch a group from the Partial armed to the Armed mode, it is necessary to unarm this group and then arm it again. The confirmation LED will light if all detectors of the group or all entrance doors of the group are armed. Confirmation by siren will be provided when all detectors of the group are armed.

6.2.2 Disarming

If the X-Pad is inside the armed premises, to disarm the group, it is necessary:

• to open the entrance door – the entry delay will start;
• to disarm the system during the entry delay using the X-Pad.

If the X-Pad is outside the premises, the group should be disarmed using the SCP control tools.

6.2.3 Arming in “I’m at home” mode

The “I’m at home” mode allows to protect the perimeter of the premises (entrance doors, windows, etc.), while ignoring the violation of the marked detectors by the user inside the premises.

Setting in “I’m at home” mode can be done using the keypad or the Control NOVA II software, if there is at least one detector with the “I’m at home” option enabled.

Arming by means of the keypad

For arming in the “I’m at home” mode, it is necessary to initiate arming and do not trigger the detectors of the “Entrance door” type during the exit delay. After the exit delay expires, all detectors will be armed, except for the detectors of the “Corridor” and “Security” types configured in the “I’m at home” mode.

Arming by means of Control NOVA II software

To arm in the “I’m at home” mode, click on the “I’m at home” icon after authorization in the object. All detectors will be armed, except for the detectors of the “Corridor” and “Security” types configured in the “I’m at home” mode.

If the group (object) is armed in the “I’m at home” mode, when the “Entrance door” detectors are triggered, the siren (X-Siren) is activated without delay; the alarm is generated immediately.

The group (object) including the detectors with the I'm at home option should contain the detectors with delay (Entrance door). If they are absent, the I'm at home mode will be ignored.

6.2.4 Arming/Disarming by means of the keypad

At the 1^st access level, the indicators of the keypad detectors/groups display the current state of the detectors/groups specified in the keypad settings, only if “Permanent indication” option is enabled for the keypad. If the “Permanent indication” option is disabled for the keypad, then at the 1^st access level, the indicators of the system status and detectors/groups on the keypad are permanently turned off.

To control the group (object) from LED keypads, enter the combination:

access code ##

With the keypads, the user can manage the whole object or groups added to its settings. If the user has several groups, the group selected in the Main action option will be managed by the first group in the list of groups added to the user. If one user needs to manage several groups separately, it is necessary to create users in the system for each group.

After entering the valid access code and pressing once, three short beeps will sound (entering the 2^nd access level). If the X-Pad works in “Permanent indication” mode, after entering the access 2^nd level, the indication mode of the detectors/groups will not change, the indicators will display the status of the detectors/groups specified in the keypad settings (see Table 6.1). If the “Permanent indication” mode is disabled in the keypad settings, after entering the 2^nd access level, the indicators of the detectors/groups on the keypad will display the current state of the detectors of the group (the number of the indicator corresponds to the detector number in the group). If the detectors in the “24h” or “Panic button” mode are added to the user, their status will be also displayed on the keypad alarm indicators (after the group alarms).

The  indicator at the 2^nd access level displays the state of the group being managed:

• lights up green (ARMED) – all detectors of the group (object) are armed. When the # button is pressed again, the group (object) will be disarmed;
• does not light up (DISARMED) – if the indicator lights up green, then the group (object) is ready for arming. When the # button is pressed again, the group (object) will be armed.

Exiting the 2^nd access level occurs after arming or disarming or automatically after 10 seconds of user inactivity. Four short beeps sound. All indicators, except the  indicator, (if there is an unviewed fault or alarm in the system) on the keypad turn off, if the “Permanent indication” option is disabled for the keypad.

If the Quick action option is enabled for the user, then the stage of viewing the status of the group is skipped; group arming/disarming occurs after one press of the # button.

6.2.5 Arming/Disarming several groups with one code by X-Pad keypad

Control of several groups with one code may be caried out using the keypads with the “Quick action” option disabled. The users can control groups added to their settings. Groups are managed by their numbers in the system.

To arm/disarm a group, enter the combination on the X-Pad:

user access code # 0 group number ##

After the user is authorized, the status of the first user-configured group is displayed on the status indicators of the detectors/groups (the “Permanent indication” option is enabled). After entering 0 and group number, the status of the selected group is displayed on the status indicators of the detectors/groups (the “Permanent indication” option is disabled).

When pressed again, the state of the group changes.

After user authorization and input of the user access code # 0 group number ##, the indication of the keypad detector/group corresponds to the control of one group by the keypad.

With permanent indication, the display of detectors/groups does not change after entering the user access code # 0 group number ##.

6.2.6 Arming/Disarming by means of X-Key

The control of the groups using X-Key key fobs is carried out by pressing the following buttons:

• – arming;
• – disarming;
• – arming in “I’m at home” mode;
• – hold-up button.

The key fob has protection against false presses. To execute the command, it is necessary to press the button from 0.3 to 2 seconds and then release it, after that the LED indicator on the assigned key fob will flash one of the following colors:

• green – the command has been sent;
• red – the command has not been sent (try again).

After the command has been successfully sent, the LED indicator will briefly flash three times with a green indicator at an interval of 1 s, confirming the execution of the command, and briefly flash three times with a red indicator if the command is prohibited from being executed.

The command execution indication is not available for the “Hold-up button” and when the previous command is repeated.

6.3 Preventing from arming

The SCP can prevent the group from arming if the user has not the appropriate rights. Prevention from arming can be performed in the cases described in Table 6.3.

6.4 Alarms and faults handling with keypads

Alarms and faults can be viewed with the keypad. When an alarm or fault is detected in the system, the  indicator starts blinking.

After the user is authorized, one of the indicators starts blinking:

– when a fault is detected in the system;

– when there is a user-related alarm.

If the  indicator blinks at the 1^st access level, but after the user’s authorization, the and  indicators do not blink or light, this means that the user does not have the rights to view the fault or alarm (for example, there is alarm of the detector absent in the groups or there is alarm of 24h detectors of the user).

After reviewing all the alarms that are available to the user, the  indicator lights up if the alarms are not handled (for example, penetration in the case or alarm of the armed detectors). After eliminating all the alarms, the  indicator goes out.

After viewing all of the system faults, the  indicator lights up. When all faults are handled, the  indicator goes out.

When controlling a group status (arming, disarming, partial arming) with the Control NOVA II software, the alarms of the zones included in this group and the 24h zones added to the user are viewed. System faults also become viewed.

6.4.1 Alarm handling

To handle alarms with the keypad, the user must be authorized: enter the access code and press the # button. If the user active alarms are available in the system, the  indicator blinks red once. If an alarm memory is available in the system, the  indicator blinks red twice.

If there is the detector alarm, the  indicator will blink simultaneously with the appropriate keypad indicator of the triggered detector. In the case of a tamper alarm, only the  indicator blinks. To handle this alarm, press the  button at the 2^nd access level.

After viewing the list of all alarms, the  indicator goes out if there are no active alarms or lights up if active alarms still remain (after active alarms are handled, the  indicator automatically goes out).

All alarms are automatically cleared after disarming the group.

6.4.2 Fault handling

If there is a fault in the system, the  indicator blinks once after the user authorization. To enter the handling mode, enter the combination on the keypad (the  indicator starts blinking 4 times per second):

access code # 3 #

In the faults viewing mode, the system shows the next fault when pressing the # button. The detector indicators on the keypad display one of the current faults described in Table 6.4.

After viewing the last faults, the system returns to the first fault. When all faults are viewed, the  indicator starts lighting continuously if the faults are not handled, or goes out if the faults are handled. Exit troubleshooting mode by pressing the  button.

If you try to enter the faults handling mode when there are no faults in the system, there you will hear a long sound signal; the system does not enter handling mode.

6.5 Remote control and monitoring

The users can monitor the system status in the following ways:

• using the Control NOVA II software;
• SMS messages to users’ phone numbers;
• a check call in case of alarm (only in the autonomous mode of the SCP).

6.5.1 Control NOVA II software

Control NOVA II software is designed for remote control and monitoring of the system status. It is available for mobile devices running on Android or iOS. The software communicates with the SCP via the Tiras CLOUD II cloud service.

To operate the Control NOVA II software, your mobile device must be connected to the Internet.

The use of the Tiras CLOUD II services (remote control, firmware update, etc.), increases the amount of Internet (GPRS) traffic used by the SCP. We strongly recommend using a mobile phone service plan with an average of 50 MB per month (the amount of Internet traffic used by the SCP depends on the intensity of the use of the Tiras CLOUD II services).

The Control NOVA II software allows to do the following:

• arming/disarming;
• receive alarm, fault and other notifications;
• monitor the system status in real-time mode;
• view the event log;
• administrators and installers can invite other users to manage the system and perform some settings;
• view videos from the added CCTV cameras;
• change user access code.

Installation, first launch, and update of the Control NOVA II software

To install the Control NOVA II software, go to the store (Google Play for Android, App Store for iOS), find the Control NOVA II software, and install it. For the correct operation of this software, it is required to provide all permissions it asks when installing, or during the operation. To start the Control NOVA II software, select the appropriate icon in the main menu of the mobile device. To launch the Control NOVA II software, select the corresponding icon in the main menu of your mobile device. The language of the software (Ukrainian, Russian, or English) is set automatically according to the language settings of the mobile device. If the Google Play or App Store settings do not have permission to auto-update, then you will get the notification about the available updates after the release of a new software version.

Account registration

To register the account, follow these steps:

• open the software and click the “Register” button;
• add user photo from camera or gallery (optional);
• enter username in the “Name” field (at least 1 character);
• enter the correct user email in the “E-mail” field;
• enter a valid user phone number, in the following format “+380XXXXXXXXX” in the “Phone” field;
• enter the password in the “Password” field (minimum 6 characters);
• enter the same password as in the previous step in the “Repeat password” field;
• agree to the terms of use;
• click the “Registration” button.

After clicking the “Registration” button, a confirmation code entry box with an SMS message appears (sometimes the code window is not displayed, the activation is executed immediately). The Control NOVA II software automatically reads the code from an SMS message and goes to the next step. In some cases, when the SMS-message code does not automatically appear in the field, you should enter it manually.

The SMS message may not come if your phone number is registered with Google, in this case the authorization will be executed automatically.

After successful SMS verification of the phone number, you will get the message stating that the email has been sent to your mailbox confirming the account registration in the Control NOVA II software. To confirm the account registration, open the email with the help of the mobile device used for registration. In the email, click the hyperlink that will confirm the registration and open the Control NOVA II software.

If you have not got the registration confirmation letter, it is necessary to check the correctness of the entered email, the messages in the Spam category, and also whether the mailbox is full.

If the actions described above do not help, do not reinstall the Control NOVA II software; it is better to immediately contact the technical support.

Authorization

After completing the registration procedure, log in to your account:

• enter the email used at the registration stage;
• enter the password used during registration;
• click the “Login” button.

Adding the SCP to the administrator or installer account

The first person who adds the SCP to one’s own account must be the administrator or the installer. After adding the SCP, the administrator or the installer may invite other users.

Before adding the SCP to the account, it is necessary to enable the registration mode (see section 7.1), which is valid for 10 minutes. After enabling the registration mode, perform the following actions:

• in the “Objects” window, click the “+” button (add);
• in the “Serial number of device” field, enter the 9-digit serial number of the SCP;
• in the “Object name” field, enter the name of the object (from 3 to 50 characters);
• add a photo of the object from a camera or a gallery (optional);
• select the user role (administrator or installer) that adds the object to the account (user access code must match the chosen type);
• in the “Access code” field, enter the administrator or installer access code. If the mobile device is equipped with a fingerprint scanner, you may optionally enable the “Use of fingerprint scanner” option to enter the object. Note that when you first enter the “Object”, you should enter the access code for the Control NOVA II software to remember and associate it with your fingerprint;
• click the “Add” button.

An object with only one user of a specific device can be added to one account.

If the data is filled correctly, after clicking the “Add” button, the SCP will appear in the “Objects” window.

Adding the SCP to user accounts

After adding the SCP to the account, the administrator can view the list of system users and their data by going to the “Settings/Users” item. User data is obtained from the SCP settings and is displayed only for the installer to view, the administrator or the installer with administrator rights can change some user settings. In this section, the Control NOVA II user account with the SCP user can be associated. To do this, it is necessary to perform the following actions:

• select the required system user (user must have full or remote access);
• click the button in the form of the envelope;
• enter user email and click “OK”.

If you have entered an email that is not registered with the Control NOVA II software, an invitation letter will be sent to this email with the offer to register with Control NOVA II. After the account registration and user authorization, the SCP will automatically appear in the list of its objects.

If you have entered the email that is registered in the Control NOVA II software, the SCP will automatically appear in the list of objects of the given user.

The Control NOVA II software provides the user with the ability to control and monitor the protected premises remotely. The software does not replace local access devices – keypads or key fobs. When designing the security system, we strongly recommend using at least one keypad.

Push messages in the Control NOVA II software

Users can receive information about the security system status with push messages that are sent to the Control NOVA II software. If any event occurs in the security system, the software receives push messages with the specific content (depending on the settings in the “Notifications” section). There are 4 event types for which the notifications can be sent:

Alarms – sent when alarms (intrusion, tamper etc.) are detected in the system, which the user has the right to view;

Faults – sent when a fault is detected in the system (no 230 V power supply, battery discharged, etc.);

Arming/Disarming – sent when controlling the status of groups that are added to the user;

System – sent when system events occur, such as changing system settings, starting the SCP, changing the access code, etc.

Push messages with alarms have a specific sound signal. All push messages received by the software are stored in the notification center. Clicking the message opens the Control NOVA II software.

Push messages are no longer received if the number of unviewed messages exceeds 50.

Some problems with receiving push messages may appear if:

• energy-saving mode is switched on (for example, Stamina on Sony devices);
• user does not have any activated Google Account on the device;
• device does not have the latest version of Google Play, or Google Play is not defined as a system application;
• notifications for the Control NOVA II software are disabled (in the “Notifications” window in the device settings);
• there are restrictions on the operation of the Control NOVA II software in the background;
• device is not connected to the Internet;
• authorization is not performed in the object at the first start of the Control NOVA II software;
• when closing the Control NOVA II software, the account was logged out.

Notification sounds (including alarms) from the Control NOVA II software may be interrupted by notifications from other applications on the smartphone (calls, SMS, etc.).

Adding IP cameras to the Control NOVA II software

The Control NOVA II software enables the connection of IP cameras (regardless of the manufacturer) supporting the RTSP protocol.

RTSP (real-time streaming protocol) is the protocol used to view a stream from IP-cameras remotely.

Before adding a camera to the Control NOVA II software, do the following:

• make sure that the camera supports the RTSP protocol (this information should be specified in the technical specification of camera);
• find out from Internet provider if provided an external static IP address;
• configure the network equipment (port forwarding, IP address for the camera);
• configure the camera (using the manufacturer’s instructions);
• create an RTSP link to the video stream (usually the RTSP link format is specified in the manufacturer’s documents or in the camera’s web interface);
• add a camera to the Control NOVA II software.

Adding the camera to the Control NOVA II software is completed by entering an RTSP link to the video stream in the object settings. The administrator or installer with administrator rights can do that.

To add the camera, do the following:

• enter the object;
• click the icon in the upper left corner;
• go to the “Settings” section and select “CCTV”;
• press “+” in the lower right corner;
• specify the camera name (from 3 to 20 characters);
• insert RTSP-links to the stream;
• click “Add”;
• go to the “System” section and select “Users”;
• select the user to grant access to the camera and select “CCTV” in its settings;
• select cameras the user can view (after selecting the camera, the user will see the “CCTV” tab in the “Control” window).

6.5.2 SMS notification

The SCP can send SMS to the user phone numbers specified in their settings (see section 3.5). The following categories of SMS notifications can be configured for each user:

• Alarms – SMS about alarms available in user groups and detectors.
• Arm/Disarm – SMS about the status of groups that can be managed by this user.
• Service – SMS about system alarms (tamper of the SCP or devices) and faults.

The list of SMS messages that can be sent to the user phone numbers is given in Table C.2 (Appendix C).

6.5.3 Check call

When using the SCP in autonomous mode, it is possible to set a “Check call” option in case of an alarm.

If the “Check call” option is enabled in the user settings, then when an alarm message is received for the user, the SCP calls to the specified user phone number. Check call is made without voice message. For the check call and sending SMS messages, one phone number specified in the user settings is used.

Check calls are made one by one to users’ phone numbers in ascending order.

The SCP considers the check call successful when the user rejects the call; in other cases, it is considered that the user has not received the call and the SCP repeats the attempts. The maximum number of attempts to dial a single user per alarm is three attempts.

If the SCP fails to dial the user, it will try again after calling the remaining users, but not earlier than in 5 minutes (the interval between attempts to connect to one user).

If other events which are transmitted to Tiras CLOUD II or sent to SMS occur when ringing round the users, they are sent in regular mode. If at the moment of occurrence of such an event, someone calls the user, the call is not interrupted (the attempt is executed in full).

The call caused by tamper of the system devices is made only for the users of the Installer and Administrator types (if the “Check call” option is set).

6.6 Changing access and attack codes

The users can change their own access and attack codes using keypads or the Control NOVA II software.

The users with enabled “Quick action” option cannot change their own access IDs with keypads.

6.6.1 Changing access codes using X-Pad

To change the access code, enter the following on the keypad:

• current access code # 1 # (the  indicator starts blinking once per second);
• new access code # (the  indicator starts blinking twice per second);
• re-enter the new access code.

To change the attack code, enter the following on the keypad:

• current access code # 2 # (the  indicator starts blinking once per second);
• new attack code # (the  indicator starts blinking twice per second);
• re-enter a new attack code.

Successful change of access codes is confirmed by four short sound signals of the keypad buzzer. If the code change failed (the entered and re-entered combinations do not match, or the entered code is already used), you will hear one long sound signal.

6.6.2 Changing access codes with Control NOVA II

To change your own access code, do the following:

• enter the object;
• click the icon in the upper left corner;
• go to the “System/Object/Security” section;
• click the “Change access code” (the keypad will appear);
• enter a valid access code and press (confirm);
• enter a new access code and press (confirm);
• repeat the new access code and press (confirm).

After confirmation, you will get the message that the access code has been changed successfully. If an error occurs (if a new code cannot be set), repeat the operation using a different value.

7. ADMINISTRATOR OPERATIONS WITH KEYPADS

The administrator is the main system user having the rights available when working with keypads. There may be several administrators in the system.

Using the keypad, the administrator can perform the following actions:

• arm/disarm groups;
• view the system state;
• change one’s own access IDs;
• enable the SCP registration mode in Control NOVA II;
• delete the SCP data in the Tiras CLOUD II service.

7.1 SCP registration mode

Enabling registration mode is required to add the SCP to the Control NOVA II account.

After enabling the registration mode from the keypad (or after the SCP start), within 10 minutes users of the “Administrator” and “Installer” types will be able to add the SCP to their accounts (if the data is correctly specified in the Control NOVA II software).

To increase the system security, users will be prohibited from adding the SCP to Control NOVA II accounts if the SCP registration mode has not been enabled by the system administrator, or if more than 10 minutes have passed since enabling the registration mode (or the SCP start). Any error when adding an object (access code entered incorrectly, user type incorrectly specified, remote control rights missing, etc.) resets the 10-minute permission, after that it is necessary to re-enable the SCP registration mode. Note that if the registration mode is enabled by restarting the SCP, you should wait at least a minute after turning on the SCP before adding the object to the account. This is necessary for the SCP to establish a communication with the Tiras CLOUD II service.

The SCP registration mode can be enabled in one of the following ways:

• enter the combination on the keypad:

administrator access code # 7 #

• restart the SCP (turn it off and on using the “Start” button).

7.2 Deleting SCP data on the Tiras CLOUD II server

The administrator can delete the SCP data stored on the Tiras CLOUD II server (the SCP serial number, event log, etc.). If the SCP is available in Control NOVA II user accounts, it will also be removed.

To delete the data, enter the combination on the keypad:

administrator access code # 6 # administrator access code #

After entering the combination, the SCP data will be deleted.

APPENDIX A

Figure A.1 – Connectors, slots and buttons of the SCP

APPENDIX B

Figure B.1 –Installation dimensions of the SCP

APPENDIX C

[1] DD.MM – day, month, HH:MM – hours, minutes.

APPENDIX D

[1] Entering format – [access code # number of key #]. For subsection 6 – [access code # number of key # access code]