TRIKDIS SIA-IP-DC-09 GET 4G And LAN Alarm Transmitter Instruction Manual

May 15, 2024
TRIKDIS

TRIKDIS SIA-IP-DC-09 GET 4G And LAN Alarm Transmitter

TRIKDIS-SIA-IP-DC-09-GET-4G-And-LAN-Alarm-Transmitter-
IMAGE

Product Information

Specifications

  • Model: Cellular/Ethernet communicator GET
  • Manufacturer: UAB Trikdis
  • Connectivity: Cellular, Ethernet
  • Compatibility: See list of compatible control panels below
  • Inputs/Outputs: 2 double I/O terminals, expandable with iO-8 expanders
  • Notifications: Push notifications, special sound alerts
  • Remote Control: Arm/Disarm system, control connected devices
  • Quick Setup: Remote configuration and firmware updates

Product Usage Instructions

Safety Requirements

The communicator should be installed and maintained by qualified
personnel. Disconnect power supply before making any electrical
connections. Follow local rules for disposal of equipment.

Installation

  1. Read the manual carefully before installation.
  2. Connect the communicator to the control panel’s serial or keyboard bus or telephone line.
  3. Set up the connection with the Protegus app and Central Monitoring Station using the provided settings.
  4. Ensure proper backup channel setup to prevent data loss.
  5. Configure user rights and notifications as needed.

Usage

  1. Use the Protegus app for remote system control and notifications.
  2. Control outputs and inputs as required, utilizing the double I/O terminals and expanders.
  3. Save settings to files for quick setup on other communicators.
  4. Regularly monitor connection status and perform firmware updates remotely.

List of Compatible Control Panels

  • Model PC585, PC1404, PC1565, PC1616, PC1832, PC1864, PC5020
  • SPECTRA SP4000, SP5500, SP6000, SP7000, SP65, SP5500+, SP6000+, SP7000+
  • MAGELLAN MG5000, MG5050, MG5050E, MG5050+, MG5075

FAQs

  • Q: Can the communicator be used with wireless control panels?
    • A: The communicator is designed for use with the listed compatible control panels that support wired connections.
  • Q: How do I update the firmware of the communicator?
    • A: Firmware updates can be performed remotely through the provided software. Follow the instructions in the manual for updating firmware.

“`

Cellular/Ethernet communicator GET
Installation manual
October, 2023 www.trikdis.lt UAB Trikdis Draugysts g. 17, LT-51229 Kaunas, Lithuania +370 37 408 040 info@trikdis.lt

www.trikdis.com

2

October, 2023

Cellular/Ethernet communicator GET
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.

www.trikdis.com

3

October, 2023

Cellular/Ethernet communicator GET

Description

The communicator is designed to transmit complete event information of the control panel to the receiver of the Central Monitoring Station. Cellular/Ethernet communicator GET can be directly connected to DSC, Paradox, UTC Interlogix (CADDX), Texecom, Honeywell control panels. The communicator can also be connected to the telephone communicators of control panels. Communicator works with Protegus application. With Protegus users can control their alarm system remotely and get notifications about security system events. The Protegus 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 Protegus simultaneously.
Features
Connects to the control panel’s serial or keyboard bus or telephone line.
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. 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. When Protegus service is enabled, events are first delivered to CMS,
and only then are sent to app users.
Works with Protegus 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 Protegus 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 Protegus app. Add additional inputs and controllable outputs with iO-8 expanders. Four iO-8 expanders can be connected to the
communicator and recieve additional 32 universal input/output terminals.
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.

www.trikdis.com

4

October, 2023

Cellular/Ethernet communicator GET

1.1 List of compatible control panels

Manufacturer DSC® PARADOX®
UTC Interlogix® Texecom®
Honeywell®

Model PC585, PC1404, PC1565, PC1616, PC1832, PC1864, PC5020 SPECTRA SP4000, SP5500, SP6000, SP7000, SP65, SP5500+, SP6000+, SP7000+ MAGELLAN MG5000, MG5050, MG5050E, MG5050+, MG5075 DIGIPLEX EVO48, EVO192, EVOHD, NE96, EVO96 SPECTRA 1727, 1728, 1738 ESPRIT E55 NetworX (Caddx) NX-4v2, NX-6v2, NX-8v2, NX-8e Premier 412, 816, 832, 832+ Premier 24, 48, 88, 168 Premier Elite 12, 24, 48, 64, 88, 168 Ademco Vista-15, Ademco Vista-20, Ademco Vista-48

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.2 Communicator model types
This manual is for LTE communicators.

1.3 Specifications

Parameter Dual purpose terminals [IN/OUT] Modem EG915U-EU (Europe) Modem EG915U-LA (Latin America) Modem BG95-M5 (Cat M1)
Power supply voltage Current consumption Transmission protocols Message encryption Buffer memory capacity Changing settings Operating environment Communicator dimensions

Description 2, can be set as either NC; NO; NC/EOL; NO/EOL; NC/DEOL; NO/DEOL (2,2 k) type inputs or open collector (OC) type outputs with current up to 0,15 A, 30 VDC max. An additional 32 inputs/outputs can be added with iO-8 expanders. LTE FDD: B1/B3/B5/B7/B8/B20/B28 GSM: B2/B3/B5/B8 LTE FDD: B2/B3/B4/B5/B7/B8/B28/B66 GSM: B2/B3/B5/B8 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 EGPRS: 850/900/1800/1900 MHz 10-18 V DC 175 mA TRK, DC-09_2007, DC-09_2012 AES 128 60 events With TrikdisConfig computer program remotely or locally via USB-C port Temperature from -10 °C to 50 °C, relative humidity – up to 80% at +20 °C 113 x 70 x 25 mm

www.trikdis.com

5

October, 2023

Parameter Weight

110 g

1.4 Communicator elements

Cellular/Ethernet communicator GET
Description
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.5 Purpose of terminals

Terminal +12 VDC -12 VDC CLK DATA I/O 1 I/O 2 COM A 485 B 485 LAN TIP RING

+10 V/+18 V DC power supply 0 V DC power supply

Description

Serial bus terminals for direct connection to control panel

1st input/output terminal (default setting ­ OUT) 2nd input/output terminal (default setting ­ OUT) Common (negative) terminal

RS485 terminals are for connecting iO-8 input/output expanders

Ethernet connection RJ45 socket Terminal to connect with control panel TIP terminal Terminal to connect with control panel RING terminal

1.6 LED indication of operation

Indicator NETWORK LTE

Light status Off Yellow blinking

Description No connection to cellular network Connecting to cellular network

www.trikdis.com

6

October, 2023

Cellular/Ethernet communicator GET

Indicator NETWORK LAN DATA POWER
TROUBLE
INTERFACE

Light status Green solid with yellow blinking Off Green solid Off Green solid Green blinking Off Green solid Yellow solid Green solid and yellow blinking Yellow solid OFF 1 red blink 2 red blinks 3 red blinks 7 red blinks –

Description Communicator is connected to cellular network. Sufficient cellular signal strength for 4G level 3 (three yellow flashes)
No connection to a computer network Communicator is connected to a computer network No unsent events Unsent events are stored in buffer (Configuration mode) Data is being transferred to/from communicator Power supply is off or disconnected Power supply is on with sufficient voltage Power supply voltage is insufficient (11.5V) (Configuration mode) Communicator is ready for configuration
(Configuration mode) No connection with computer No operation problems Connection error at the “physical” level (PHY Link status error), check LAN cable SIM1 card error SIM2 card error Lost connection with control panel (serial bus) Not used

1.7 Structural schematic of using the GET communicator

Note:

Before you begin, make sure that you have the necessary: 1. USB-C cable for configuration. 2. At least 4-wire cable for connecting communicator to control panel. 3. CRP2 cable for connecting to Paradox panel`s serial port.

www.trikdis.com

7

October, 2023

Cellular/Ethernet communicator GET
4. Flat-head 2,5 mm screwdriver. 5. Sufficient gain cellular antenna if network coverage in the area is poor. 6. Activated SIM card (PIN code request can be turned off). 7. Particular security control panel`s installation manual. Order the necessary components separately from your local distributor.

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 Protegus app.
2.1 Settings for connection with Protegus app
In “Panel settings” window:

1. Select “Security panel model” that will be connected to the communicator.
2. Select “Remote Arm/Disarm” if you want users to be able to control the panel in Protegus app with their keypad code. This setting is only shown for directly controlled panels.
3. Select “Event” so that the communicator sends event messages.
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.

www.trikdis.com

8

October, 2023

Cellular/Ethernet communicator GET

Note:

For the direct panel control to work, you will need to change the panel settings. How to do this is described in chapter 4.1 “Programming of control panels when the communicator is connected to the keypad bus or serial bus”. In this section you will find information on how to change the “PC download/UDL password”.

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

5. Tick the checkbox “Enable connection” to the Protegus Cloud. 6. Change the “PROTEGUS Cloud access Code” for logging in to Protegus if you want users to be asked to enter it when
adding the system to Protegus app (default password ­ 123456).
In “Network settings” window:

These settings must be made if the SIM (or two SIM cards) card is inserted into the communicator.
7. Enter “SIM card PIN” code. 8. Change “APN” name. “APN” can be found on the website of the SIM card operator (“internet” is universal and works in
many operator networks).

These settings must be made if the communicator is connected to a LAN network.
9. Check “Use DHCP” the box so that the communicator automatically reads the computer network settings (subnet mask, gateway) and is assigned an IP address.

www.trikdis.com

9

October, 2023

In “CMS reporting” window:

Cellular/Ethernet communicator GET

10. In the group of options “Reporting mode”, the order of communication channels is set, how the communicator will send messages to CSP and to Protegus. 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.

Note:

For more information about other GET settings in TrikdisConfig, see chapter 6 ,,TrikdisConfig window description”.

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. Select “Security panel model” that will be connected to the communicator. 3. Select “Event” so that the communicator sends event messages.

www.trikdis.com

10

October, 2023

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

Cellular/Ethernet communicator GET

4. Communication type – select the IP connection method. 5. Protocol – select the protocol type for event messages: TRK (to TRIKDIS receivers), DC-09_2007 or DC-09_2012 (to
universal 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 CSP and to Protegus. 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:

If a SIM card (or two SIM cards) is inserted in the communicator, the following settings must be made.
12. Enter “SIM card PIN” code.
13. 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).

www.trikdis.com

11

October, 2023

Cellular/Ethernet communicator GET

These settings must be made if the communicator is connected to a LAN network.
14. Check “Use DHCP” the box so that the communicator automatically reads the computer network settings (subnet mask, gateway) and is assigned an IP address.
After finishing configuration, click Write [F5] and disconnect the USB cable.

Note:

For more information about other GET settings in TrikdisConfig, see chapter 6 ,,TrikdisConfig window description”.

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.

Note:

One or two SIM cards can be inserted into the communicator. Ensure that the SIM card is activated. Ensure that mobile internet service (mobile data) is enabled if connected via IP channel. To avoid entering the PIN code in TrikdisConfig, insert the SIM card into your mobile phone and turn off the PIN request function.

www.trikdis.com

12

October, 2023

Cellular/Ethernet communicator GET
3.2 Schematics for wiring the communicator to the serial or keypad bus of the control panel
Following one of the schematics provided below, connect communicator to the control panel.

www.trikdis.com

13

October, 2023

Cellular/Ethernet communicator GET

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

Note:

GET communicator has 2 universal input / output terminals that can be set to the OUT (PGM) operating mode. The outputs (OUT) can control two areas of the security system. If you want to control the system in this way, in TrikdisConfig, in the “Panel settings” window, uncheck “Remote Arm/Disarm”. The Protegus apps must be configured with the settings described in chapter 5.2 “Additional settings to arm/disarm the system using the control panel’s keyswitch zone”.

3.4 Schematics for wiring the communicator to the telephone line of the control panel
Following one of the schematics provided below, wire the communicator to the control panel.

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

Note:

The GET communicator has 2 universal input/output terminals that can be set to an OUT (PGM) operating mode. The outputs can control two areas of the security system. Area control settings are made in the Protegus app.

www.trikdis.com

14

October, 2023

Cellular/Ethernet communicator GET
3.5 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:

Note:

If more inputs or outputs need to be connected to the communicator, connect the TRIKDIS iO-8 expander.

3.6 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.7 Schematics for connecting iO-8 expansion modules
If more inputs or outputs need to be connected to the communicator connect the TRIKDIS iO-8 expander. Configuration of expander modules connected to the communicator is described in chapter 7.8. “”RS485 modules” window”. Four iO-8 expansion modules can be connected to the communicator to provide an additional 32 universal I/O terminals.

www.trikdis.com

15

October, 2023

Cellular/Ethernet communicator GET

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.

Note:

Sufficient strength of LTE signal is level three (three “NETWORK LTE” indicator flashes in yellow color).
If you count less yellow “NETWORK LTE” LED flashes, the network signal strength is insufficient. We recommend to select a different place to install the communicator, or to use a more sensitive cellular antenna.
If you see a different LED indication, it indicates a certain malfunction. Diagnose it by following the LED indication table in chapter 1.6 “LED indication of operation”.
If the GET indication does not illuminate at all, check the power supply and connections.

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”.
DSC
DSC panels do not need to be programmed.
PARADOX
Paradox control panels need to be programmed only for direct control with Protegus. 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.
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].
UTC INTERLOGIX (CADDX)
With the keyboard connected to the security control panel: 1. Press [*][8] and enter the installer’s code (default – 9713).

www.trikdis.com

16

October, 2023

Cellular/Ethernet communicator GET

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.

Position

Segment

Setting

23

3

12345678

37 (not necessary)

3

12345678

4

1234567*

90

3

12345678

93

3

12345678

96

3

12345678

99

3

12345678

102

3

12345678

105

3

12345678

108

3

12345678

After having programmed all the fields listed, press [Exit] twice to exit the programming mode.
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 2 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.

Note:

Keyswitch zone can be momentary (pulse) or level. By default, the GET controllable output OUT is set to 3 second pulse mode. You can change the impulse duration or change to level mode in Protegus settings. See chapter 6.2 “Additional settings to arm/disarm the system using the control panel’s keyswitch zone”.

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;

www.trikdis.com

17

October, 2023

Cellular/Ethernet communicator GET

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.

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:

Section

Data

Section

Data

S Section

Data

*41 1111 (receiver telephone number)

*60

1

*69

1

*42 1111

*61

1

*70

1

*43 1234 (panel account number)

*62

1

*71

1

*44 1234

*63

1

*72

1

*45 1111

*64

1

*73

1

*47 1

*65

1

*74

1

*48 7

*66

1

*75

1

*50 1

*67

1

*76

1

*59 0

*68

1

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

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.

Location 0 Location 1 Location 2 Location 4
Location 23
Location 37

Keypad Entry 89713 0# 0# 1234# 1# 1234# 2# 1# 4# 12345678 12345678# 23# * 12345678# 37#

Enter programming mode

Description

All zones LEDs are ON (segment 1) All zones LEDs are ON (segment 2)
All zones LEDs are ON (segment 3)

www.trikdis.com

18

October, 2023

Cellular/Ethernet communicator GET

Keypad Entry * 12345678 12345678*# EXIT EXIT

Description
All zones LEDs are ON (segment 3) All zones LEDs are ON (segment 4) Exit programming mode

Remote control

5.1 Adding the security system to Protegus app
With Protegus 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 Protegus application or use the browser version: web.protegus.app.

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

Important:

When adding the GET communicator to Protegus check if: 1. The inserted SIM card is activated and the PIN code is either entered or disabled; 2. Or a LAN cable is connected. 3. “Protegus cloud” is enabled. See chapter 6.5 “User reporting” window; 4. Power supply is connected (“POWER” LED illuminates green); 5. Registered to the network (“NETWORK LTE” LED illuminates green and blinks yellow).

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

www.trikdis.com

19

October, 2023

Cellular/Ethernet communicator GET
5.2 Additional settings to arm/disarm the system using the control panel’s keyswitch zone
Important: The control panel zone to which the GET output OUT is connected to has to be set to keyswitch mode. Follow the instructions below if the security control panel will be controlled with communicator’s PGM output, turning on/off the control panel keyswitch zone.
1. Click ,,Continue”.

2. Enter “Area name”. Enable PGM output control using the Protegus 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”.

www.trikdis.com

20

October, 2023

Cellular/Ethernet communicator GET
5. 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.
6. After completing the settings, click the “Skip” button.

www.trikdis.com

21

October, 2023

Cellular/Ethernet communicator GET 5.3 Arming/disarming the alarm system with Protegus
1. In the “System Home Screen” window, click on the “Disarm” status icon.
2. Protegus will receive a message about a change in the status of the security system and the status icon will change its state.

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:

www.trikdis.com

22

October, 2023

Cellular/Ethernet communicator GET

Object IMEI/Unique ID Status Device SN BL FW HW State Administrator

Description Device IMEI number Operating condition Device type (GET should be shown) Device serial number Browser version Device firmware version Device hardware version Connection to program type (via USB or remote) Access level (shown after access code is approved)

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.

www.trikdis.com

23

October, 2023

6.3 “Panel settings” window

Cellular/Ethernet communicator GET

“TLF” settings group
The communicator is connected to the TIP RING terminals of the telephone communicator of the control panel.
Security panel model ­ select the control panel model that will be connected to 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.

www.trikdis.com

24

October, 2023

Cellular/Ethernet communicator GET
“Serial bus” settings group
The communicator is connected to the control panel via a Serial Bus. Panel 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 CSP and to Protegus. 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”.

www.trikdis.com

25

October, 2023

6.4 “CMS reporting” window “CMS settings” tab

Cellular/Ethernet communicator GET

Make settings for the “Primary” and “Backup” communication channels if the communicator will send events to the security firm’s CMS receiver. Messages can be sent over a single communication channel to a single receiver. ,,Backup” channel can be assigned for primary channel, which will be used when the connection via the primary 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: TRK (to TRIKDIS receivers), DC-09_2007 or DC-09_2012 (to
universal 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.
“Reporting mode” settings group
For setting parameters on how the control panel will communicate with the CMS channels and with Protegus. 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 Protegus.
Backup type ­ select a connection type (LAN, SIM1, SIM2) with the CMS receiver and Protegus. Backup type 2 ­ select a connection type (LAN, SIM1, SIM2) with the CMS receiver and Protegus.

www.trikdis.com

26

October, 2023

Cellular/Ethernet communicator GET
Communication path test ­ specify the time period for which the selected connection types should be tested (LAN, SIM1, SIM2).
“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.
6.5 “User reporting” window
“PROTEGUS cloud” tab

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

www.trikdis.com

27

October, 2023

Cellular/Ethernet communicator GET
“Protegus Cloud” settings group
Enable connection ­ enable the Protegus service, the GET communicator will be able to exchange data with Protegus app and to be remotely configured via TrikdisConfig.
Protegus Cloud access Code – 6-digit code for connecting to the Protegus app (default – 123456).
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:
o Static IP ­ static IP address for when manual registering mode is set. o Subnet mask ­ subnet mask for when manual registering mode is set. o 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
Important: 1. Ensure that the SIM card is activated and working before using it. 2. Ensure that mobile data service is enabled.

www.trikdis.com

28

October, 2023

Cellular/Ethernet communicator GET
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. Forbid connection when roaming detected – you can use this function when the security system is installed near the country border. This function prevents the communicator from operating in the other country’s mobile network.
“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.
Forbid connection when roaming detected – you can use this function when the security system is installed near the country border. This function prevents the communicator from operating in the other country’s mobile network.

www.trikdis.com

29

October, 2023

6.7 “IN/OUT” windows

Cellular/Ethernet communicator GET

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 CSP and Protegus.
Enable ­ checked event fields where messages will be sent to CMS and Protegus. 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 Protegus
and CMS. SIA – ­ enter the event code or leave the default value. Upon entering the event, the event code will be sent to Protegus
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 “RS485 modules” window
“Modules list” tab
iO-8 expanders can be connected to the communicator to add additional inputs, outputs. Connected expanders must be added to the “Modules list” table.

“Modules list” settings group
Module type ­ select the module that is connected to the communicator via RS485 from the list. Serial No ­ enter the module serial number (6 digits), which is indicated on stickers on the module’s case and packaging. After selecting the connected module and entering its serial number, go to “RS485 modules” “Module”.

www.trikdis.com

30

October, 2023

Cellular/Ethernet communicator GET
“Module” tabs
After adding the expander to the communicator as described above, in the “RS485 modules” window a new tab will appear with this module’s settings. The tab will be given a number. Bellow we describe the settings for iO-8 expanders.
iO-8 expander settings window

Expander iO-8 has 8 universal (input/output) terminal contacts. Up to four iO-8 expanders can be connected. Input count ­ select what number of terminal contacts should be set to input (IN) mode. The rest of the terminal contacts will become outputs (OUT).
Settings for controllable outputs are set directly in Protegus app. There you can assign an output for arming/disarming the alarm system or for remote control of devices. In the table inputs can be assigned Contact ID (SIA, 4+2) event and restore codes. After input is triggered, the communicator will send an event with set event code to monitoring station receiver and Protegus app.
Contact ID event code: Enable ­ allow message transmission, when the input is triggered. E/R ­ choose what type of event will be sent when input is triggered ­ “Event” or “Restore”. CID ­ assign a Contact ID event code to the input. SIA ­ assign a SIA event code to the input. 4+2 – assign a 4+2 event code to the input Part. ­ assign the partition (area) to the input. It is set automatically: if the module No. is 1, then the area is 91; if the module No. is 4, then the area is 94. Zone ­ set the zone number for the input.
Contact ID restore code: Enable ­ allow message transmission when the input is restored. E/R ­ choose what type of event will be sent when input is restored ­ “Restore” or “Event”. CID ­ assign the Contact ID restore code to the input. SIA ­ assign a SIA event code to the input. 4+2 – assign a 4+2 event code to the input. Part. ­ assign the partition (area) to the input. It is set automatically: if the module No. is 1, then the area is 91; if the module No. is 4, then the area is 94. Zone ­ set the zone number for the input. Object ID – the input (IN) can be assigned an “Object ID”, which will differ from the “Object ID” of the communicator. Input type ­ select the type of the input (NO, NC, EOL).

www.trikdis.com

31

October, 2023

Cellular/Ethernet communicator GET
6.9 “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. 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. TEST ­ periodic test message.

Note:

To enable periodic TEST messages and set their period, go to “CMS reporting” -> “Settings” -> “Test period”.

Enable ­ when selected, the sending of messages is enabled. You can change the Contact ID (SIA, 4+2) code for each event, and also the zone and partition number.

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

Remote configuration

Important:

Remote configuration will work only if: 1. The inserted SIM card is activated and the PIN code is either entered or disabled; 2. Or a LAN cable is connected. 3. “Protegus cloud” is enabled. How to enable cloud is described in section 6.5 “User reporting” window; 4. Power supply is connected (“POWER” LED illuminates green); 5. Registered to the cellular network (“NETWORK LTE” LED illuminates green and blinks yellow).

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.

www.trikdis.com

32

October, 2023

Cellular/Ethernet communicator GET

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. 2. Make sure that the event arrives to the CMS (Central Monitoring Station) and/or is received in the Protegus application. 3. To test communicator input, trigger it and make sure to receive the correct event. 4. To test the communicator outputs, activate them remotely and check their operation. 5. If the security control panel will be controlled remotely, arm/disarm the security system remotely by using the Protegus app.

Firmware update

Note:

When the communicator is connected to TrikdisConfig, the program will automatically offer to update the device’s firmware if updates are present. Updates require an internet connection. Antivirus software, firewall or strict access to internet settings can block the automatic firmware updates. In this case, you will need to reconfigure your antivirus program.

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

www.trikdis.com

33

October, 2023

Cellular/Ethernet communicator GET
4. Press “Open firmware” and select the required firmware file. If you do not have the file, the newest firmware file can be downloaded by registered users from www.trikdis.com , under the download section of the GET communicator.
5. Press Update [F12]. 6. Wait for the update to complete.

www.trikdis.com

34

October, 2023

Cellular/Ethernet communicator GET

10 Annex
The communicator converts Contact ID codes received from the alarm control panel into SIA codes. Contact ID to SIA code conversion table

System Event
Medical alarm Personal emergency Fire in zone: Water flow detected in zone: Pull station alarm in zone: Panic in zone: Panic alarm by user: Panic alarm in zone: Panic alarm in zone: Panic alarm in zone: Panic alarm in zone: Alarm active in zone: Alarm active in zone: Alarm active in zone: Alarm active in zone: Alarm active in zone: Alarm active in zone: Tamper active in zone: Intrusion verified in zone: Alarm active in zone: System failure (143) Tamper active in zone: Tamper active in zone: Alarm active in zone: Alarm active in zone: Gas detected in zone: Water leakage detected in zone:

Foil break detected in zone: High temperature at sensor: Low temperature at sensor: CO detected in zone: Fire failure in zone: Monitored alarm System failure (300) AC power supply loss Low battery System failure (304)

CID Report Code
E100 E101 E110 E113 E115 E120 E121 E122 E123 E124 E125 E130 E131 E132 E133 E134 E135 E137 E139 E140 E143 E144 E145 E146 E150 E151 E154 E155 E158 E159 E162 E200 E220 E300 E301 E302 E304

SIA Report Code
“MA” “QA” “FA” “SA” “FA” “PA” “HA” “PA” “PA” “HA” “HA” “BA” “BA” “BA” “BA” “BA” “BA” “TA” “BV” “UA” “ET” “TA” “TA” “BA” “UA” “GA” “WA” “BA” “KA” “ZA” “GA” “FS” “BA” “YP” “AT” “YT” “YF”

www.trikdis.com

35

October, 2023

System Event
System reset in zone: Panel programming changed System shutdown Battery failure (309) Ground fault Battery failure (311) Power supply overcurrent (312) Engineer reset by user: (313) Sounder/Relay failure System failure (321) System failure (330) System failure (332) System failure (333) System failure (336) System failure (338) System failure (341) System failure (342) System failure (343) System failure (344) System communication failure (350) System communication failure (351) System communication failure (352) System failure (353) System communication failure (354) System failure (355) Fire trouble in zone: Trouble in zone: Trouble in zone: Trouble in zone: Wireless zone fault: Wireless module failure (382) Tamper active in zone: Low battery in wireless zone: Trouble in zone: (389) Trouble in zone: (391) Trouble in zone: (393) User disarmed the system User disarmed the system Automatic disarm Deferred disarm user Alarm cancelled by user:
www.trikdis.com

Cellular/Ethernet communicator GET

CID Report Code
E305 E306 E308 E309 E310 E311 E312 E313 E320 E321 E330 E332 E333 E336 E338 E341 E342 E343 E344 E350 E351 E352 E353 E354 E355 E373 E374 E378 E380 E381 E382 E383 E384 E389 E391 E393 E400 E401 E403 E405 E406
36

SIA Report Code
“RR” “YG” “RR” “YT” “US” “YM” “YP” “RR” “RC” “YA” “ET” “ET” “ET” “VT” “ET” “ET” “ET” “ET” “XQ” “YC” “LT” “LT” “YC” “YC” “UT” “FT” “EE” “BG” “UT” “US” “UY” “TA” “XT” “ET” “NA” “NC” “OP” “OP” “OA” “OR” “BC”
October, 2023

System Event
User disarmed remotely Quick disarm Remote disarm Call back request made by CMS Successful data download Entry access denied for user Entry by user

Forced Access zone Exit access denied for user Exit by user User disarmed too early User armed too late User Failed to Disarm User Failed to Arm Auto arm failed Partial arm by user: Exit violation by user: System disarmed after alarm by user: Recent arm user Wrong code entered Auto-arm time extended by user: Device disabled (501) Device disabled (520) Wireless sensor disabled in zone: (552) Zone bypassed Zone bypassed Zone bypassed Zone bypassed Group bypass by user: Zone bypassed Zone bypass cancelled Vent zone bypass Walk test activated by user: Manual test report Periodic test report System event (605) System event (606) Periodic test report with trouble System event (622) System event (623) Time/Date was reset by user www.trikdis.com

Cellular/Ethernet communicator GET

CID Report Code
E407 E408 E409 E411 E412 E421 E422 E423 E424 E425 E451 E452 E453 E454 E455 E456 E457 E458 E459 E461 E464 E501 E520 E552 E570 E571 E572 E573 E574 E576 E577 E579 E607 E601 E602 E605 E606 E608 E622 E623 E625
37

SIA Report Code
“OP” “OP” “OS” “RB” “RS” “JA” “DG” “DF” “DD” “DR” “OK” “OJ” “CT” “CI” “CI” “CG” “EE” “OR” “CR” “JA” “CE” “RL” “RO” “YS” “UB” “FB” “MB” “BB” “CG” “UB” “UB” “UB” “TS” “RX” “RP” “JL” “LF” “RY” “JL” “JL” “JT”
October, 2023

System Event
Inaccurate Time/Date System programming started System programming finished System event (631) System event (632) System not active (654) Medical alarm restored Personal emergency restored No more fire alarm in zone : No more water flow alarm in zone: Panic alarm restored in zone: Panic alarm cancelled by user: Panic alarm restored in zone: Panic alarm restored in zone: Panic alarm restored in zone: Panic alarm restored in zone:

No more alarm in zone: No more alarm in zone: No more alarm in zone: No more alarm in zone: No more alarm in zone: No more alarm in zone: No more tamper in zone: No more alarm in zone: No more system failure (143) No more tamper in zone: No more tamper in zone: No more alarm in zone: No more alarm in zone: No more gas alarm in zone: No more water leakage alarm in zone: Foil break restored in zone: Temperature has normalized at sensor: Temperature has normalized at sensor: No more CO alarm in zone: No more fire failure in zone: Monitored restore alarm No more system failure (300) AC power supply OK Battery OK No more system failure (304) www.trikdis.com

Cellular/Ethernet communicator GET

CID Report Code
E626 E627 E628 E631 E632 E654 R100 R101 R110 R113 R120 R121 R122 R123 R124 R125 R130 R131 R132 R133 R134 R135 R137 R140 R143 R144 R145 R146 R150 R151 R154 R155 R158 R159 R162 R200 R220 R300 R301 R302 R304
38

SIA Report Code
“JT” “LB” “LS” “JS” “JS” “CD” “MH” “QH” “FH” “SH” “PH” “HH” “PH” “PH” “HH” “HH” “BH” “BH” “BH” “BH” “BH” “BH” “TA” “UH” “UR” “TR” “TR” “BH” “UH” “GH” “WH” “BH” “KH” “ZH” “GH” “FV” “BH” “YA” “AR” “YR” “YG”
October, 2023

System Event
System reset restored in zone: No more battery failure (309) Restore ground fault No more battery failure (311) Restore power supply overcurrent (312) No more sounder/Relay failure No more system failure (321) No more system failure (330) No more system failure (332) No more system failure (333) No more system failure (336) No more system failure (338) No more system failure (341) No more system failure (342) No more system failure (344) No more system communication failure (350) No more system communication failure (351) No more system communication failure (352) No more system failure (353) No more system communication failure (354) No more system failure (355) Fire trouble restored in zone: No more trouble in zone: No more trouble in zone: No more wireless zone fault: No more wireless module failure (382) No more tamper in zone: Battery OK in wireless zone: No more trouble in zone: (391) No more trouble in zone: (393) User armed the system User armed the system Automatic arm User armed remotely Quick arm Remote arm User armed to Stay mode User armed too early User

disarmed too late User Failed to Disarm Partial Arm by user: www.trikdis.com

Cellular/Ethernet communicator GET

CID Report Code
R305 R309 R310 R311 R312 R320 R321 R330 R332 R333 R336 R338 R341 R342 R344 R350 R351 R352 R353 R354 R355 R373 R374 R380 R381 R382 R383 R384 R391 R393 R400 R401 R403 R407 R408 R409 R441 R451 R452 R454 R456
39

SIA Report Code
“RR” “YR” “UR” “YR” “YQ” “RO” “YH” “ER” “ER” “ER” “VR” “ER” “ER” “ER” “XH” “YK” “LR” “LR” “YK” “YK” “UJ” “FJ” “EA” “UJ” “UR” “BR” “TR” “XR” “NS” “NS” “CL” “CL” “CA” “CL” “CL” “CS” “CG” “CK” “CJ” “CI” “CG”
October, 2023

System Event
Recent disarm user Device enabled (501) Device enabled (520) Wireless sensor enabled in zone: (552) Zone bypass cancelled Zone bypass cancelled Zone bypass cancelled Zone bypass cancelled Group bypass by user: cancelled Zone bypass cancelled Zone bypass cancelled Vent zone bypass cancelled Walk test deactivated by user Time/Date was reset by user System active (654)

Cellular/Ethernet communicator GET

CID Report Code
R459 R501 R520 R552 R570 R571 R572 R573 R574 R576 R577 R579 R607 R625 R654

SIA Report Code
“CR” “RG” “RC” “YK” “UU” “FU” “MU” “BU” “CF” “UU” “UU” “UU” “TE” “JT” “CD”

www.trikdis.com

40

October, 2023

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>

Related Manuals