GET Cellular Communicator¶

1. Description¶

The communicator is designed to transmit event messages from the control panel to the CMS (Central Monitoring Station) and the Protegus2 application.

Cellular/Ethernet communicator GET can be directly connected to DSC, Paradox, UTC Interlogix (CADDX), Texecom, Innerrange, Honeywell control panels. The communicator can also be connected to the telephone communicators (which supports the Contact ID communication protocol transmitted by DTMF tones) of control panels.

Communicator transmits full event information to the Central Monitoring Station.

Communicator works with Protegus2 application. With Protegus2 users can control their alarm system remotely and get notifications about security system events. The Protegus2 app works with all security alarm panels from various manufacturers to which the GET communicator is connected. Communicator can transmit event notifications to the Central Monitoring Station and work with Protegus2 simultaneously.

1.1 Features¶

Connects to the control panel's serial or keyboard bus or telephone line (TIP/RING).

Sends events to monitoring station receiver:

• Sends events to TRIKDIS software or hardware receivers that work with any monitoring software.

• Can send event messages to SIA DC-09 receivers.

• Can send event messages to SUR-GARD receivers. The annex has a table for converting Contact ID codes to SIA codes.

• Monitoring the connection by sending a PING request to the IP receiver every 30 seconds (or by user defined period).

• Backup channel, that will be used if connection with the primary channel is lost.

• With parallel communication channel events can be sent to two receivers at same time.

• When Protegus2 service is enabled, events are first delivered to CMS, and only then are sent to app users.

Works with Protegus2 app:

• “Push” and special sound notifications informing about events.

• Remote system Arm/Disarm.

• Remote control of connected devices (lights, gates, ventilation systems, heating, sprinklers, etc.).

• Different user rights for administrator, installer and user.

Notifies users:

• Users can be notified about events with Protegus2 app.

Controllable outputs and inputs:

• 2 double I/O terminals that can be set either as input (IN) or controllable output (OUT) terminals.

• Outputs controlled by the Protegus2 app.

Quick setup:

• Settings can be saved to file and quickly written to other communicators.

• Two access levels for configuring the device for CMS administrator and for installer.

• Remote configuration and firmware updates.

1.2 List of compatible control panels¶

Underlined - Control panels directly controlled by communicator. Firmware PARADOX control panels, which are directly controlled, must be V.4 or higher.

* Connect control panels from other manufacturers to the GET communicator using the TIP RING terminals of the control panel.

1.3 Communicator model types¶

This manual is for LTE communicators.

1.4 Specifications¶

1.5 Communicator elements¶

1. Cellular antenna SMA connector

2. Light indicators

3. Frontal case opening slot

4. Terminal for external connections

5. “RESET” button.

6. SIM2 card slot

7. SIM1 card slot

8. USB-C port for communicator programming

9. Ethernet connection RJ45 socket

1.6 Purpose of terminals¶

1.7 LED indication of operation¶

1.8 Structural schematic of using the GET communicator¶

2. Quick configuration with TrikdisConfig software¶

1. Download TrikdisConfig configuration software from www.trikdis.com (type “TrikdisConfig” in the search field) and install it.

2. Open the casing of the communicator with a flat-head screwdriver as shown below:

   

3. Using a USB-C cable connect the communicator to the computer.

4. Run TrikdisConfig. The software will automatically recognize the connected communicator and will open a window for configuration.

5. Click Read [F4] to read the communicator’s settings. If requested, enter the Administrator or Installer 6-digit code in the pop-up window.

Below we describe what settings need to be set for the communicator to begin sending events to the Central Monitoring Station (CMS) and to allow the security system to be controlled with the Protegus2 app.

2.1 Settings for connection with Protegus2 app¶

In “Panel settings” window:

1. If the communicator is connected to the TIP/RING terminals of the control panel, then you need to make the “AUTO” setting.

The communicator is connected to the keypad bus or serial bus of the control panel.

2. Select “Security panel model” that will be connected to the communicator.

3. Select “Remote Arm/Disarm” if you want users to be able to control the panel in Protegus2 app with their keypad code. This setting is only shown for directly controlled panels.

4. For the direct control of Paradox and Texecom panels enter “Security panel PC download password”. It must match the password that is entered in the control panel.

In “User reporting” window, “PROTEGUS Cloud” tab:

4. Tick the checkbox “Enable connection” to the Protegus Cloud.

5. Change the “PROTEGUS Cloud access Code” for logging in to Protegus2 if you want users to be asked to enter it when adding the system to Protegus2 app (default password – 123456).

In “Network settings” window:

These settings must be made if the communicator is connected to a LAN network.

3. Check “Use DHCP” the box so that the communicator automatically reads the computer network settings (subnet mask, gateway) and is assigned an IP address.

These settings must be made if the SIM (or two SIM cards) card is inserted into the communicator.

4. Enter “SIM card PIN” code.

5. Change “APN” name. “APN” can be found on the website of the SIM card operator (“internet” is universal and works in many operator networks).

6. Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

7. Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

In “CMS reporting” window:

12. In the group of options "Reporting mode", the order of communication channels is set, how the communicator will send messages to CMS and to Protegus2. The connection types are specified in order. If the communicator fails to connect using the “Main type” connection , it switches to the “Backup type”, and so on. If the backup connection type was successful in transmitting the message to the CMS, then the Return to main connection type will be attempted after the specified time interval.

After finishing configuration, click the button Write [F5] and disconnect the USB cable.

2.2 Settings for connection with Central Monitoring Station¶

In “System settings” window:

1. Enter “Object ID” (account) number provided by the Central Monitoring Station (characters, 0-9, A-F. Do not use FFFE, FFFF Object ID).

In “Panel settings” window:

2. If the communicator is connected to the TIP/RING terminals of the control panel, then you need to make the “AUTO” setting.

3. Select “Security panel model” that will be connected to the communicator.

In “CMS reporting” window settings for “Primary channel”:

4. Communication type - select the IP connection method.

5. Protocol - select the protocol type for event messages: TRK8 (to TRIKDIS receivers), DC-09_2007 or DC-09_2012 (to universal receivers), TL150 (to SUR-GUARD receivers).

6. Encryption key - enter the encryption key that is set in the receiver.

7. Domain or IP - enter the receiver’s Domain or IP address.

8. Port - enter receiver’s network port number.

9. TCP or UDP - choose event transmission protocol (TCP or UDP) in which events should be sent.

10. (Recommended) Configure “Primary channel Backup” settings.

11. In the group of options "Reporting mode", the order of communication channels is set, how the communicator will send messages to CMS and to Protegus2. The connection types are specified in order. If the communicator fails to connect using the “Main type” connection , it switches to the “Backup type”, and so on. If the backup connection type was successful in transmitting the message to the CMS, then the return to main connection type will be attempted after the specified time interval.

In “Network settings” window:

These settings must be made if the communicator is connected to a LAN network.

12. Check “Use DHCP” the box so that the communicator automatically reads the computer network settings (subnet mask, gateway) and is assigned an IP address.

If a SIM card (or two SIM cards) is inserted in the communicator, the following settings must be made.

13. Enter “SIM card PIN” code.

14. Change the “APN” name. “APN” can be found on the website of the SIM card operator (“internet” is universal and works in many operator networks).

15. Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

16. Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

After finishing configuration, click Write [F5] and disconnect the USB cable.

3. Installation and wiring¶

3.1 Installation process¶

1. Remove the top cover and pull out the contact terminal.

2. Insert SIM card into the holder.

3. Remove the PCB board from the bottom part of the case.

4. Fix the bottom part to a suitable place with screws.

5. Place the PCB board back into case, insert contact terminal.

6. Screw cellular antenna on.

7. Close the top cover.

8. If the LAN network will be used to transmit events to the CMS, a LAN cable must be connected to the communicator.

3.2 Installation in intrusion control panel enclosure panel¶

The GET communicator must be installed inside the intrusion control panel enclosure, which is protected by a lid tamper. It is mounted on the internal rear surface of the enclosure using the supplied industrial-grade double-sided acrylic foam mounting tape. The tape must be applied to a clean, dry surface with firm pressure to ensure reliable adhesion.

If the host enclosure does not allow secure installation as described above, the communicator may be installed in a separate tampered enclosure.

3.3 Schematics for wiring the communicator to a security control panel¶

Following one of the schematics provided below, connect communicator to the control panel.

3.4 Schematic for wiring of the communicator to the keypad bus and telephone communicator (TIP/RING terminals) of the PARADOX SP/SP+/MG/MG+ control panel¶

When connecting the communicator to the keypad bus and the TIP/RING terminals of the control panel, you must make the following settings for the GET communicator:

1. Select “AUTO”.

2. Select the control panel model “7. Paradox SP+/MG+ series KeyBus“.

3. Select “Remote Arm/Disarm” if you want users to be able to control the panel using the Protegus2 app using their own keypad code.

4. To directly control the security panel, enter the “Security panel PC download password”. It must match the password entered in the security panel.

The Paradox control panel must be programmed to transmit events to the CMS and for remote control from the Protegus2 application.

3.5 Schematic for wiring the communicator to the control panel keyswitch zone¶

Follow this schematic if the control panel will be armed/disarmed with a communicator PGM output turning on/off the panel’s keyswitch zone.

The communicator is connected to the keypad bus or serial bus of the control panel. / Arming/disarming the panel via keyswitch zone.

The communicator is connected to the telephone communicator (TIP/RING terminals) of the control panel. / Arming/disarming the panel via the keyswitch zone.

3.6 Schematics for input connection¶

The communicator has 2 universal input / output terminals that can be set to input IN mode. NC, NO, NO / EOL, NC / EOL, NO / DEOL, NC / DEOL circuits can be connected to the input terminal. The input type can be changed in the TrikdisConfig window „IN/OUT” -> “Type”.

Connect the input according to the selected input type (NO, NC, NC/EOL, NO/EOL, NO/DEOL, NC/DEOL), as shown in the schemes below:

3.7 Schematics for wiring a relay¶

With relay contacts you can control (turn on/off) various electric appliances. The I/O terminal of the communicator must be set to an output (OUT) mode.

3.8 Turn on the communicator¶

To start the communicator, turn on the security control panel’s power supply. This LED indication on the GET communicator must show:

• “POWER” LED illuminates green when the power is on;

• “NETWORK LTE” LED illuminates green and blinks yellow when the communicator is registered to the cellular network.

4. Programming the control panel¶

4.1 Programming of control panels when the communicator is connected to the keypad bus or serial bus¶

Below it is described how to program the security control panel so that the GET communicator could read events from the panel and control it remotely.

To enable remote control of the security panel, make sure that the checkbox “Remote Arm/Disarm” is selected in the TrikdisConfig window “Panel settings”.

4.1.1 DSC¶

DSC panels do not need to be programmed.

4.1.2 PARADOX¶

Paradox control panels need to be programmed only for direct control with Protegus2. You do not need to program Paradox panels for reading events.

For remote control of Paradox panels, you need to set up a PC download password. This password must match the password which was set in the TrikdisConfig window “Panel settings”, when the checkbox next to “Remote Arm/Disarm” was selected.

To set this password, with the keyboard connected to the security control panel:

• For MAGELLAN, SPECTRA series: go to cell 911 and enter 4-digit PC download password.

• For DIGIPLEX EVO series: go to cell 3012 and enter 4-digit PC download password.

4.1.3 TEXECOM¶

Texecom control panels need to be programmed for both reading events and remote control.

You need to set the Texecom panel’s “UDL passcode”. This password must match the password which was set in the TrikdisConfig window “Panel settings”, when the box next to “Remote Arm/Disarm” was selected.

The security control panel can be programmed with Texecom software - Wintex. Enter “UDL passcode” (4-digit code) in the “Communication Options” window, “Options” tab.

Also, you can program with a keypad connected to the security control panel:

1. Enter the 4-digit installer’s code and press the [Menu] button to enter the programming menu.

2. Press the [9] key immediately afterwards.

3. Press [7][6], and then [2]. Enter the 4-digit “UDL passcode” (“UDL passcode” must match the GET communicator’s “PC login password”).

4. Press [Yes] and leave the programming mode by pressing [Menu].

4.1.4 UTC INTERLOGIX (CADDX)¶

With the keyboard connected to the security control panel:

1. Press [*][8] and enter the installer’s code (default - 9713).

2. Enter the device number assigned to the connected communicator (default - 0).

3. Set the settings below for each row. In sequence, enter the position, segment number and the required setting. Clicking [*] (asterisk) will return you to the local input field.

After having programmed all the fields listed, press [Exit] twice to exit the programming mode.

4.1.5 INNERRANGE¶

Innerrange Inception security control panel version must be 2.3.0.3507-r0 or higher.

The control panel must be connected to the internet. Connect to Innerrange Inception by entering: https://skytunnel.com.au/inception/SERIALNUMBER, where SERIALNUMBER is the number of the controller that you can find on the panel’s enclosure.

Open Configuration > General > Alarm Reporting. In the 3rd Party Device Configuration settings group you need to enter:

1. Enable 3rd Party Device Reporting - select this checkbox.

2. 3rd Party Device Type - set “Trikdis”.

3. Serial port - set “Serial Port 1 (Plugged In, In Use By 3rd Party Device)”.

4. Save settings and exit the application.

4.1.6 HONEYWELL ADEMCO VISTA¶

Follow these steps for Honeywell Ademco Vista-20 and Honeywell Ademco Vista-48 panels. The panel’s firmware version must be V5.3 or higher. With a keypad that is connected to the panel:

1. Enter the programming mode. Enter the installer code 4][1][1][2] and after that [8][0][0] . Alternatively, turn on the panel‘s power supply. In 50 seconds after the power supply is turned on, press the buttons [*] and [#] at the same time (this method can be used when programming mode was exited by pressing in keypad [*][9][8] ).

2. Turn on the sending of Contact ID events via LRR. Press [*][2][9][1][#] in keypad.

3. When using the „Remote Arm/Disarm“ function, allow to use the 2nd AUI address. In keypad press [*][1][8][9][1][1][#] .

Exit the programming mode. In keypad press [*][9][9].

4.2 Programming of control panels when the communicator is connected to the TIP/RING terminals of the control panel¶

For the control panel to send events via the landline dialer, it must be turned on and properly set up. Following the panel’s programming manual, configure the control panel’s landline dialer:

1. Turn on the panel’s PSTN landline dialer.

2. Enter the monitoring station receiver’s telephone number (you can use any number longer than 4 digits. The GET communicator will pick up and answer when the panel calls to any phone number).

3. Choose DTMF mode.

4. Select Contact ID communication protocol.

5. Enter the panel’s 4 digit account number.

The control panel zone to which the GET output OUT is connected should be set to keyswitch zone for arming/disarming the control panel remotely.

4.2.1 PROGRAMMING HONEYWELL VISTA LANDLINE DIALER¶

Using the control panel’s keypad enter these sections and set them as described:

• *41 – enter monitoring station receiver telephone number;

• *43 – enter control panel’s account number;

• *47 – set the Tone dial to [1] and enter the number of dial attempts;

• *48 – use default setting, *48 must be set to 7;

• *49 – Split/Dual message. *49 must be set to 5;

• *50 – delay for sending burglary alarm events (optional). Default value is [2,0]. With it the event message transmission will be delayed for 30 seconds. If you want the message to be sent immediately, set [0,0].

When all required settings are set, it is necessary to exit programming mode. Enter *99 in keypad.

4.2.2 SPECIAL SETTINGS FOR HONEYWELL VISTA 48 PANEL¶

If you want to use GET communicator with Honeywell Vista 48 panel, set the following sections as described:

When all required settings are set, it is necessary to exit programming mode. Enter *99 in keypad.

4.2.3 UTC INTERLOGIX(CADDX)¶

Programming of the Interlogix NX-4V2 (NX-6V2, NX-8V2) control panel when the communicator is connected to the TIP/RING terminals of the control panel.

5. Remote control¶

5.1 Adding the security system to Protegus2 app¶

With Protegus2 users will be able to control their alarm system remotely. They will see the status of the system and receive notifications about system events.

1. Download and launch the Protegus2 application or use the browser version: www.protegus.app.

   

2. Log in with your user name and password or register and create new account.

3. Click “Add new system” and enter the GET’s “IMEI/Unique ID” number. This number can be found on the device and the packaging sticker. Click “Next”.

4. Enter the system „Name”. Click "Next".

5.2 Additional settings to arm/disarm the system using the control panel’s keyswitch zone¶

Follow the instructions below if the security control panel will be controlled with a GET PGM output, turning on/off the control panel keyswitch zone.

1. Click „Continue“.

2. Enter “Area name”. Enable PGM output control using the Protegus2 application.

3. Select “Pulse” or “Level”, depending on how the keyswitch zone type is configured. If necessary, you can change the "Pulse" interval.

4. Click „Save“.

3. If there is another Area for the security system, then you need to click “Click to add an area”. Setting up the PGM output is similar to that described above.

4. After completing the settings, click the “Skip” button.

5.3 Arming/disarming the alarm system with Protegus2¶

1. In the “System Home Screen” window, click on the “Disarm” status icon.

2. Protegus2 will receive a message about a change in the status of the security system and the status icon will change its state.

6. TrikdisConfig window description¶

6.1 TrikdisConfig status bar description¶

After connecting the GET communicator and clicking Read [F4], TrikdisConfig will provide information about the connected device in the status bar:

After pressing Read [F4], the program will read and show the settings which are set in the GET. Set the necessary settings according to the TrikdisConfig window descriptions given below.

6.2 “System settings” window¶

“General” settings group

• Object ID – if the events will be sent to the CMS (Central Monitoring Station), enter the account number provided by the CMS (6 characters hexadecimal number, 0-9, A-F. Do not use FFFE, FFFF Object ID).

• Module ID – enter the identification number of the module.

• Time set - select which server to use for time synchronization.

“Access” settings group

When setting up the communicator GET there are two levels of access for, the administrator and the installer:

• Administrator code - allows you to access all configuration fields (default code - 123456).

• Installer code - limited access for configuring the communicator (default code - 654321).

• Only an administrator can restore - if the box is checked, factory settings can be restored only by entering the administrator code.

• Allow installer to change – the administrator can specify which settings can be changed by the installer.

6.3 “Panel settings” window¶

“TLC” settings group

The communicator is connected to the TIP RING terminals of the telephone communicator of the control panel.

• Communication protocol – enable/disable DTMF landline interface on the communicator.

• First HSK tone / Second HSK tone – handshake" tone of control panel.

• Use security panel account ID – if the box is marked with a check mark, the communicator will not send the value set in the "Object ID" field, but the object number entered in the control panel.

• Wait acknowledgment from CMS – if the box is marked with a check mark, after sending each event message, the communicator will wait for confirmation from the IP receiver that it has successfully received the message. If the communicator does not receive a confirmation signal, it will not generate a “kiss-off” signal. If the communication end signal is not received, the control panel's telephone communicator will repeat the event message.

• Dial tone frequency - the frequency at which the communicator communicates with the control panel through the telephone communicator.

“Serial bus” settings group

The communicator is connected to the control panel via a Serial Bus.

• Event coding protocol – select the event reporting protocol (CID or SIA).

• Security panel model – select the control panel model that will be connected to the communicator.

• Remote Arm/Disarm – when the checkbox is selected, the GET will directly control the control panel remotely. This setting will be visible only for directly controlled panels. For direct control of the control panels you need to change the panel settings, as described in section 4.1 “Programming of control panels when the communicator is connected to the keypad bus or serial bus”.

• Event – check the box so that the communicator sends events to the CMS and to Protegus2.

• Security panel PC download password - for the direct control of Paradox and Texecom control panels you need to enter the PC/UDL password. It must match the password that was entered in the control panel. How to change this password is described in section 4.1 “Programming of control panels when the communicator is connected to the keypad bus or serial bus”.

6.4 “CMS reporting” window¶

“CMS settings” tab

Events can be sent over several channels of communication. The primary and parallel communication channels can operate simultaneously, this way the communicator can send events to two receivers at the same time. Backup channels can be assigned for both primary and parallel channels, which will be used when the connection via the primary or parallel channel is interrupted.

Communication is encoded and password protected. A TRIKDIS receiver is required for receiving and sending event information to the monitoring programs:

• For connection over IP - software receiver IPcom Windows/Linux, hardware IP/SMS receiver RL14 or multichannel receiver RM14.

“Primary channel” settings group

• Communication type - select the method of communication with the monitoring station receiver (IP).

• Protocol - select in which coding the events should be sent: TRK8 (to TRIKDIS receivers), DC-09_2007 or DC-09_2012 (to universal receivers), TL150 (to SUR-GUARD receivers).

• Encryption key - 6-digit message encryption key. The key written to the communicator must match the receiver’s key.

• Domain or IP - enter the domain or IP address of the receiver.

• Port - enter the network port number of the receiver.

• TCP or UDP - select in which protocol (TCP or UDP) the events should be sent.

“Primary channel Backup” settings group

Enable the backup channel mode to send events via backup channel if connection via primary channel is lost. Backup channel settings are same as described above.

“Parallel channel” settings group

Events are transmitted in parallel with the primary channel through this channel. When the second channel is enabled, events can be sent simultaneously to two receivers (e.g., local and centralized monitoring stations). Parallel channel settings are the same as described above.

“Settings” tab “Settings” settings group

• Test period - TEST event period for testing the connection. Test events are sent as Contact ID messages and forwarded to the monitoring software.

• IP ping period – period for sending internal PING heartbeats. These messages are only sent via IP channel. The receiver will not forward PING messages to the monitoring software to avoid overloading it. Notifications will only be sent to the monitoring software if the receiver fails to receive PING messages from the device within the set time.

By default, the “Connection lost” notification will be transmitted to the monitoring software if the PING message is not received by the receiver over a time period three times longer than set in the device. E.g. if the PING period is set for 3 minutes, the receiver will transfer the “Connection lost” notification if a PING message is not received within 9 minutes.

PING messages keep the active communication session between the device and the receiver. An active session is required for remote connection, control and configuration of the device. We recommend setting the PING period for no more than 5 minutes.

• Backup reporting after - indicates the number of unsuccessful attempts to send the message via “Primary” channel. If device fails to transmit specified number of times, the device will connect to transmit the messages via “Backup” channel.

• Return from backup after - time after which the communicator GET will attempt to reconnect and transmit messages via the Primary channel.

• Line No. - enter line number of the receiver.

• Receiver No. - enter the receiver number.

“Reporting mode” settings group

For setting parameters on how the control panel will communicate with the CMS channels and with Protegus2. The connection types are specified in order. If the control panel fails to connect using the “Main type” connection , it switches to the “Backup type”, and so on. If the backup connection type was successful in transmitting the message to the CMS, then the “Return to main” connection type will be attempted after the specified time interval.

• Main type – select a connection type (LAN, SIM1, SIM2) with the CMS receiver and Protegus2.

• Backup type – select a connection type (LAN, SIM1, SIM2) with the CMS receiver and Protegus2.

• Backup type 2 – select a connection type (LAN, SIM1, SIM2) with the CMS receiver and Protegus2.

• Communication path test – specify the time period for which the selected connection types should be tested (LAN, SIM1, SIM2).

6.5 “User reporting” window¶

“PROTEGUS cloud” tab

Protegus2 service allows users to remotely monitor and control the communicator. For more information about Protegus2 service, visit www.protegus.eu.

“Protegus Cloud” settings group

• Enable connection – enable the Protegus2 service, the GET communicator will be able to exchange data with Protegus2 app and to be remotely configured via TrikdisConfig.

• Protegus Cloud access Code - 6-digit code for connecting to the Protegus2 app (default - 123456).

• Parallel reporting – allow parallel report sending using the primary channel and to Protegus2. Reports will only be sent to Protegus2 and to users after they’ve been sent to the security company.

6.6 “Network settings” window¶

“LAN” tab

These settings must be made if the communicator is connected to a LAN network.

“Ethernet settings” settings group

• Use DHCP - check the box to have the communicator automatically register to the network. If the auto-register fails, you will need to enter it manually:

• Static IP – static IP address for when manual registering mode is set.

• Subnet mask – subnet mask for when manual registering mode is set.

• Default gateway – gateway address for when manual registering mode is set.

• DNS1, DNS2 - (Domain Name System) identifies the server that specifies the IP address of the domain. Used when domain is set in the communication channel “Domain or IP” field (not IP address). Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

“SIM1” tab

These settings must be made if the SIM card is inserted into the SIM1 slot of the communicator.

“SIM card” settings group

• SIM card PIN - enter the SIM card PIN code. This code can be disabled by inserting the SIM card into a mobile phone and disabling the request. If you disabled the SIM card PIN request, leave the default value in this field.

• APN - enter APN (Access Point Name). It is required for connecting the communicator to the internet. APN can be found on the website of the SIM card operator (“internet” is universal and works in the networks of many operators).

• Login, Password - if required, enter the user name (login) and password for connection to the internet.

• SIM ICCID - enter the ICCID number of the SIM card if you want the communicator to work only with this SIM card.

• DNS1, DNS2 - (Domain Name System) identifies the server that specifies the IP address of the domain. Used when domain is set in the communication channel Domain or IP field (not IP address). Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

• Preferred operator – after entering the mobile network operator code, the communicator will connect only to the network of the selected operator. The mobile operator code consists of MCC and MNS codes.

“SIM2” tab

These settings must be made if the SIM card is inserted into the SIM2 slot of the communicator.

“SIM card” settings group

• SIM card PIN - enter the SIM card PIN code. This code can be disabled by inserting the SIM card into a mobile phone and disabling the request. If you disabled the SIM card PIN request, leave the default value in this field.

• APN - enter APN (Access Point Name). It is required for connecting the communicator to the internet. APN can be found on the website of the SIM card operator (“internet” is universal and works in the networks of many operators).

• Login, Password - if required, enter the user name (login) and password for connection to the internet.

• SIM ICCID - enter the ICCID number of the SIM card if you want the communicator to work only with this SIM card.

• DNS1, DNS2 - (Domain Name System) identifies the server that specifies the IP address of the domain. Used when domain is set in the communication channel Domain or IP field (not IP address). Google DNS server is set by default. Regardless of IP settings, make sure the DNS addresses match those supported by your ISP.

• Preferred operator – after entering the mobile network operator code, the communicator will connect only to the network of the selected operator. The mobile operator code consists of MCC and MNS codes.

6.7 “IN/OUT” windows¶

The communicator has 2 universal (input / output) terminals. The table can set the terminal operating mode (Disabled, IN, OUT). The input must specify the type of circuit to be connected NC, NO, NO / EOL, NC / EOL, NO / DEOL, NC / DEOL.

Additional sensors can be connected to the communicator inputs. When the sensor is triggered, the communicator will send an event message. The input is assigned a Contact ID (SIA) code, which will be sent to CMS and Protegus2.

• Enable – checked event fields where messages will be sent to CMS and Protegus2.

• E/R – choose what type of event will be sent when input is triggered – “Event” or “Restore”.

• CID – enter the event code or leave the default value. Upon entering the event, the event code will be sent to Protegus2 and CMS.

• SIA - – enter the event code or leave the default value. Upon entering the event, the event code will be sent to Protegus2 and CMS.

• Part. – enter the partition (area) number that will be sent when an internal event occurs and the system is restored.

• Zone - enter the zone number that will be sent when an internal event occurs and the system is restored.

6.8 “Event summary” window¶

In this window, you can enable, disable and modify internal messages sent by your device. Disabling an internal message in this window will prevent it from being sent regardless of other settings.

• COMMUNICATION – message about connection error between the control panel and communicator.

• LAN_FAILURE - LAN communication failure message.

• POWER – message about low power supply voltage.

• REMOTE_FINISHED – message about disconnection from remote configuration with TrikdisConfig.

• REMOTE_STARTED – message about remote connection to configure GET with TrikdisConfig.

• SIM1_FAILURE - mobile communication failure message.

• SIM2_FAILURE - mobile communication failure message.

• TEST – periodic test message.

• Enable – when selected, the sending of messages is enabled.

You can change the Contact ID (SIA) code for each event, and also the zone and partition number.

6.9 Restoring factory settings¶

To restore the communicator's factory settings, you need to click the “Restore” button in the TrikdisConfig window.

Another way to restore factory settings.

Power supply is connected to the communicator. Press and hold the “RESET” button on the communicator PCB board. Hold the “RESET” button pressed for 10 seconds until the LED indicators ("NETWORK", "POWER", "TROUBLE") turn off and the LED "POWER" indicator lights up. Release the "RESET" button. The communicator's factory settings have been restored.

7. Remote configuration¶

1. Start the configuration program TrikdisConfig.

2. In the “Remote access” section enter the communicator’s “IMEI/Unique ID” number. This number can be found on the device and the packaging sticker.

3. (Optional) in the “System name” field, enter the desired name for the communicator with this Unique ID.

4. Press “Configure”.

5. In the newly opened window click Read [F4]. If required, enter the administrator or installer code. To save the password, select “Remember password”.

6. Set the necessary settings and when finished, click Write [F5].

8. Test communicator performance¶

When the configuration and installation is complete, perform a system check:

1. Generate an event:

• by arming/disarming the system with the control panel’s keypad;

• by triggering a zone alarm when the security system is armed.

1. Make sure that the event arrives to the CMS (Central Monitoring Station) and/or is received in the Protegus2 application.

2. To test communicator input, trigger it and make sure to receive the correct event.

3. To test the communicator outputs, activate them remotely and check their operation.

4. If the security control panel will be controlled remotely, arm/disarm the security system remotely by using the Protegus2 app.

9. Firmware update¶

The communicator’s firmware can also be updated or changed manually. After an update, all previously set settings will remain unchanged. When writing firmware manually, it can be changed to a newer or older version. To update:

1. Run TrikdisConfig.

2. Connect the communicator via USB cable to the computer or connect to the communicator remotely.

   • If a newer firmware version exists, the software will offer to download the newer firmware version file.

3. Select the menu branch “Firmware”.

4. Press “Open firmware” and select the required firmware file.

5. Press Update [F12].

6. Wait for the update to complete.

10. Safety requirements¶

The communicator should be installed and maintained by qualified personnel.

Prior to installation, please read this manual carefully in order to avoid mistakes that can lead to malfunction or even damage to the equipment.

Disconnect the power supply before making any electrical connections.

Changes, modifications or repairs not authorized by the manufacturer shall void your rights under the warranty.

Please act according to your local rules and do not dispose of your unusable alarm system or its components with other household waste.

11. Annex¶

The communicator converts Contact ID codes received from the alarm control panel into SIA codes.

Contact ID to SIA code conversion table