GET communicator – installer and user manual

1. Overview

The GET is Trikdis's Ethernet + 4G communicator: it forwards the events of the alarm control panel to the monitoring station and to the Protegus 2 app over the wired local network (LAN) or over the mobile network. It can be connected to the control panel in two ways: directly, to the panel's data bus or serial port (with DSC, Paradox, UTC Interlogix (Caddx), Texecom, InnerRange and Honeywell control panels), or to the telephone line dialer (TIP/RING) of any control panel that sends its events in Contact ID format with DTMF tones. The communicator forwards the complete event information (code, partition, zone or user) to the monitoring station. With the Protegus 2 app the user controls the system remotely and receives notifications about the events; the app works with every control panel the communicator supports, regardless of the panel's manufacturer. Reporting to the monitoring station and Protegus 2 can be used at the same time. This manual was written for the GET communicator with an LTE (4G) modem; the differences between the GET, the GT and the GT+ are summarized in section 1.2.

1.1 What it is for and how it works

• It reports to the monitoring station. It sends the events over an IP connection, via the wired network or the mobile network, to a Trikdis software or hardware receiver (TRK8 protocol) – these work with any monitoring software –, to a SIA DC-09 receiver or to a SUR-GARD receiver (TL150). Towards a SUR-GARD receiver it converts the Contact ID codes received from the control panel into SIA codes; the conversion table is in the appendix of the English documentation on docs.trikdis.com. It checks the connection with the receiver every 30 seconds (or at the interval you set) with a PING message; if the primary channel fails, it switches to the backup channel. With a parallel channel the events go to two receivers at the same time. You can put the connection paths – LAN, SIM1, SIM2 – in order: if the main path does not work, the communicator switches to the backup path (section 6.4.2). If the Protegus service is also switched on, the monitoring station receives the event first, and only then the users' app.
• It notifies the user. The Protegus 2 app shows the events in a push notification with a separate sound; from the app the user can arm and disarm, and switch the devices connected to it (lighting, gate, ventilation, heating, irrigation, etc.). In the app the administrator, the installer and the user have different rights. The GET does not send SMS or call notifications: notifications arrive through the Protegus 2 app.
• It controls the control panel directly. When connected to the data bus or serial port, the communicator also sees the panel's partition and zone states, and the user arms and disarms from Protegus 2 with their own keypad code – no keyswitch zone is needed for this.
• It has its own inputs and outputs. Two dual-function I/O terminals can be used as an input (IN) or as a controllable output (OUT); by default both are outputs. The outputs can be switched from the Protegus 2 app. The A 485 and B 485 terminals are not used on the GET; no RS485 expansion module can be connected to the GET.
• It can be set up with two tools. The settings can be made with the TrikdisConfig software running on Windows (over a USB-C cable or remotely) and – with firmware 1.08 or newer – also from the Protegus 2 app (Settings → Advanced settings). The settings can be saved to a file and written into other communicators. There are two access levels: the monitoring station's administrator and the installer. The communicator can also be set up remotely, and its firmware can also be updated remotely.

The diagram below shows the structure of the system: the alarm control panel connects to the communicator, the communicator reaches the internet in two ways – over the mobile network (LTE) or through the router (LAN) –, and from there the monitoring station's receiver (and its software) and the Protegus server; the user sees the system in the Protegus 2 app.

• 1 alarm control panel ("Alarm panel")
• 2 GET LTE communicator ("LTE communicator")
• 3 router ("Router")
• 4 internet ("Internet")
• 5 Protegus server ("Protegus server")
• 6 phone with the Protegus app ("Phone with Protegus software")
• 7 monitoring station receiver ("Receiver")
• 8 monitoring software ("Monitoring software")
• 9 the security company's monitoring station ("Monitoring station in security company") – in the dashed frame

1.2 Versions: GET, GT and GT+

The GET is the Ethernet-port sibling of the GT and GT+ communicators: wiring and programming of the alarm control panel, the range of compatible control panels, the modem, the transmission protocols and the use of Protegus 2 are the same, so the chapter structure of the three communicators' manuals is also the same. The differences are summarized in the table below.

All three communicators are made with the same three kinds of modem; for the European market the European (EU) version is the right one. You can find the modem type and the hardware version in the TrikdisConfig status bar (Device, HW) and on the device's label.

1.3 Compatible alarm control panels

The control panels below can be connected to the communicator directly, over the data bus or the serial port. The "Direct control" column shows whether the user can arm and disarm from Protegus 2 with their own keypad code without any further wiring; where this is not possible, the communicator reads the events from the bus, and a keyswitch zone is needed for control (section 3.4).

• The firmware of directly controlled Paradox control panels must be at least V.4. On the newer Paradox control panels (SP+, MG+, EVOHD+) the serial port may be locked at the factory; unlocking is covered in section 4.1.2. The Spectra SP / SP+ and Magellan MG / MG+ control panels can also be connected to the data bus (Keybus) and the TIP/RING terminals together instead of the serial port – this does not require the paid unlocking, but the communicator's firmware must be at least 1.21 (section 3.3.3).
• The control panels of all other manufacturers connect through their telephone line dialer (TIP/RING), if it sends the events in Contact ID format with DTMF dialing; in that case a keyswitch zone is needed for control.
• You can check which Trikdis communicator and which connection suits your control panel in the Compatibility finder.

1.4 Parts of the communicator

The communicator's printed circuit board sits in a black plastic case; the front cover snaps off, and the terminal block can be pulled off. The LAN socket and the TIP/RING terminals are accessible on the side of the case, through a separate opening.

• 1 SMA connector of the mobile antenna
• 2 LED indicators (NETWORK LTE, NETWORK LAN, DATA, POWER, TROUBLE, INTERFACE)
• 3 Slot for snapping off the front cover
• 4 Removable terminal block for the external connections
• 5 RESET button
• 6 SIM2 card holder
• 7 SIM1 card holder
• 8 USB-C socket for programming
• 9 Ethernet (LAN) RJ45 socket

The terminal block can be pulled off: this way the device can be disconnected from power or restarted in one move, it is easier to handle during wiring, and for USB programming the device can be taken to the computer.

1.5 Terminals

On the wiring diagrams the power terminals are marked +DC and −DC (on the device +12 VDC / −12 VDC), and the RS485 terminals A RS485 / B RS485 (on the device A 485 / B 485). The terminal labels are also printed on the front cover.

1.6 LED indications

The LEDs on the front cover are the most important tools for commissioning and troubleshooting. Read them together: POWER shows the power supply, NETWORK LTE the mobile network, NETWORK LAN the wired network, TROUBLE a fault; the INTERFACE LED has no function on the GET.

NETWORK LTE – mobile network connection

NETWORK LAN – wired network connection

DATA – data traffic

POWER – power supply

TROUBLE – fault

INTERFACE – not used on the GET.

1.7 Technical specifications

2. Quick start

The communicator can be set up with two tools: the Windows software called TrikdisConfig – over a USB-C cable or remotely – and the Protegus 2 app (Settings → Advanced settings). This chapter describes the shortest route: which settings are needed for the communicator to send events to the monitoring station, and for the system to be controllable from the Protegus 2 app. For every step we give both the app path and the TrikdisConfig path; the settings are explained in detail in chapter 6.

2.1 Preparation

Setup with TrikdisConfig. You set the device up on the desk, before wiring; afterwards, at the site, you only need to wire it in.

1. Download and install the TrikdisConfig software. On the Trikdis website (www.trikdis.com), type "TrikdisConfig" in the search field.

2. Open the communicator's case with a flat screwdriver: insert the screwdriver into the slot at the top, next to the antenna, and lever outwards, then at the bottom, at the opening, downwards. The figure also shows the location of the USB-C socket on the edge of the printed circuit board.

3. Insert the nano SIM card (or cards) into the holder, in the orientation shown in the figure: the SIM1 holder is in the middle of the printed circuit board, SIM2 is at the edge. The card must be active and have mobile data service, and if possible, switch off its PIN request in a phone (so you do not have to enter a PIN in the device). If you use the communicator on the wired network only, no SIM card is needed.

4. Connect the communicator to the computer with a USB-C cable.

5. Start TrikdisConfig. The program recognizes the device and opens the programming window. Click the Read [F4] button: the program reads the device's current settings. If it asks for a password, enter the 6-digit administrator code (default 123456) or installer code (default 654321).

Setup from the Protegus 2 app. You can make settings from the app if the communicator is already online and you have added it to your Protegus account (section 5.1). If the communicator cannot connect yet – for example because the SIM card asks for a PIN code, or the operator requires a different APN –, do the first setup with TrikdisConfig.

1. In the app, open the system and go to the Settings → Advanced settings menu.
2. The first time, the app warns you (Proceed with Caution): these settings are meant for professionals. Tap the Accept the risk and continue button; with the Do not show this again tick the warning will not appear next time.
3. The app reads the communicator's settings. If it asks for a Service Access code, enter the communicator's Protegus Cloud access code (default 123456).
4. Make the settings described below, then tap the Write button: the app writes them into the communicator.

2.2 Connection to the Protegus 2 app

In the app (Settings → Advanced settings):

1. Panel settings → TLF – if the communicator is connected to the control panel's TIP/RING terminals: set Security panel model to AUTO.
2. Panel settings → Serial Bus – if the communicator is connected to the control panel's data bus or serial port: in the Security panel model field, select the type of the connected control panel.
3. In the same place, switch on the Remote Arm/Disarm option if the users want to control the control panel from Protegus 2 with their own keypad code. It only appears for directly controllable control panels.
4. For direct control of a Paradox control panel, enter the PC download password, for a Texecom control panel the UDL passcode; it must match the password set in the control panel.
5. User reporting → Cloud: switch on the Enabled option, and change the Cloud access code if you want the user to have to enter it when the system is added to the app (default 123456).
6. Network settings → LAN – if the communicator is connected to the wired network: switch on the Use DHCP option.
7. Network settings → SIM and SIM2 – for every inserted SIM card: enter the SIM card PIN and the APN, and check that DNS1 and DNS2 work with your operator.
8. Reporting to CMS → CMS settings → Reporting mode: in the Main type, Backup type and Backup type 2 fields, set the order in which the communicator uses the LAN, SIM (SIM1) and SIM2 connections.
9. Tap the Write button.

In TrikdisConfig. First, on the Panel settings page, set how the communicator connects to the control panel.

If you connect it to the control panel's telephone line output (TIP/RING): in the Communication protocol field, select AUTO.

• 1 Communication protocol – 2. AUTO for TIP/RING connection.

If you connect it to the control panel's data bus or serial port: set up the control panel in the Serial bus group.

• 2 Security panel model – the type of the connected control panel.
• 3 Remote Arm/Disarm – tick it if the users want to control the control panel from Protegus 2 with their own keypad code. It only appears for directly controllable control panels.
• 4 Security panel PC download password – for direct control of a Paradox or Texecom control panel, the PC or UDL password set in the control panel; the two must match.

Then, on the User reporting page, on the PROTEGUS Cloud tab, enable the cloud connection.

• 5 Enable connection – tick it: it enables the connection to the Protegus cloud.
• 6 PROTEGUS Cloud access Code – the access code for Protegus 2 (default 123456). Change it if you want the user to have to enter it when the system is added to the app. If you change the code later, it must also be changed in the Protegus 2 app.

If the communicator is connected to the wired network, on the Network settings page, on the LAN tab, tick the Use DHCP option: the communicator automatically receives the network settings (subnet mask, gateway) and gets an IP address.

• 7 Use DHCP – when ticked, the communicator automatically gets an IP address and network settings from the router.

If there is a SIM card (one or two cards) in the communicator, enter the card's data on the SIM1 (and SIM2) tab.

• 8 SIM card PIN – the card's PIN code (if the PIN request is switched off, the default value can stay).
• 9 APN – the operator's data access point (see below).
• 10 DNS 1 – primary name server; by default Google's DNS. Regardless of the IP settings, check that the DNS addresses work with your operator.
• 11 DNS 2 – secondary name server (by default also Google's).

The APN (Access Point Name) is the mobile operator's data access point; without it the device cannot connect to the internet over the mobile network. You can find the exact value on the website of the SIM card's operator. We keep the known APNs of European operators in a separate article: APN settings – list of European mobile operators. If you have no other data from the operator, try the APN internet: it is generic and works in many operators' networks.

Finally, on the CMS reporting page, on the Settings tab, in the Reporting mode group, set the order of the connections: this is the path on which the communicator sends the messages to the monitoring station and to Protegus 2.

• 12 Reporting mode – Main type: the main connection (LAN, SIM1 or SIM2); Backup type: the backup; Backup type 2: the second backup.

You enter the connection types in order. If the communicator cannot connect with the Main type connection, it switches to the Backup type, and so on. If the backup connection has successfully delivered the message to the monitoring station, the communicator tries to return to the main connection after the set time (section 6.4.2).

If the device does not report to a monitoring station, the setup is now complete: press the Write [F5] button, wait for the confirmation, and unplug the USB cable.

2.3 Connection to the monitoring station

In the app (Settings → Advanced settings):

1. System options → System general: enter the account number received from the monitoring station (Account No.; 0–9, A–F; FFFE and FFFF cannot be used). On hardware version x1x1, with firmware 1.31 or newer, you enter the account number per channel: Reporting to CMS → CMS settings → Primary channel → Primary Account no. You can recognize this on the screen: if System general only shows the Time set field, use the channel setting.
2. Panel settings → TLF (TIP/RING connection): set Security panel model to AUTO; or Panel settings → Serial Bus (data bus or serial connection): select the Security panel model.
3. Reporting to CMS → CMS settings → Primary channel: switch on the Enabled option, then enter: Communication type: IP; the receiver's Domain or IP address and Port; TCP or UDP; Protocol: TRK8 for a Trikdis receiver, DC-09_2007 or DC-09_2012 for a universal receiver, TL150 for a SUR-GARD receiver; and the encryption key set in the receiver: with the TRK protocol in the TRK encryption key field, with DC-09 switch on the Enable encryption key option and enter the DC-09 encryption key.
4. (Recommended) Set up the Backup channel in the same way.
5. Reporting to CMS → CMS settings → Reporting mode: Main type, Backup type, Backup type 2.
6. Network settings → LAN (wired network): switch on the Use DHCP option. Network settings → SIM and SIM2 (for every SIM card): SIM card PIN, APN, and check the DNS1, DNS2 fields.
7. Tap the Write button.

In TrikdisConfig. First, on the System settings page, enter the account number.

• 1 Object ID – the account number received from the monitoring station (6 hexadecimal characters, 0–9, A–F). FFFE and FFFF cannot be used.

On the Panel settings page, set the control panel connection if you have not done so in section 2.2: for a TIP/RING connection set Communication protocol to AUTO; for a data bus or serial connection select the type of the connected control panel in the Security panel model field (the figures in section 2.2).

Then, on the CMS reporting page, on the CMS settings tab, in the Primary channel section, set the receiver's data. The picture shows the window before setup: the Communication type field of the primary channel is still Disable.

• 4 Communication type – select the IP connection.
• 5 Protocol – TRK8 for a Trikdis receiver, DC-09_2007 or DC-09_2012 for a universal receiver, TL150 for a SUR-GARD receiver.
• 6 Encryption key – the encryption key set in the receiver.
• 7 Domain or IP – the receiver's domain name or IP address.
• 8 Port – the receiver's port number.
• 9 TCP or UDP – the transmission protocol; it follows the receiver's setting.
• 10 Primary channel Backup – backup channel for a failure of the primary; fill it in the same way, it is recommended.

On the Settings tab, in the Reporting mode group, set the order of the connections (Main type, Backup type, Backup type 2) if you have not done so in section 2.2 – you will find the figure and the description of how it works there as well.

Finally, on the Network settings page, enter the network data if you have not done so in section 2.2: on the LAN tab the Use DHCP tick, on the SIM1 (and SIM2) tab the card's data (SIM card PIN, APN, DNS 1, DNS 2).

At the end of the settings, press the Write [F5] button, wait for the confirmation, and unplug the USB cable. The device is now ready to be wired in. With a telephone line connection, the alarm control panel's dialer must also be switched on and set up here, otherwise the control panel sends no events (chapter 4).

3. Installation and wiring

3.1 Installation steps

1. Remove the front cover (see section 2.1), and pull off the terminal block.
2. Insert the nano SIM card – or both – into its holder, if you have not done so during commissioning.
3. Take the printed circuit board out of the back cover: open the latch next to the antenna connector, and lift the board out (see the figure).
4. Fix the back cover with screws in the chosen place (the screw holes are circled in the figure), or, as described in section 3.2, with the supplied double-sided adhesive tape.
5. Put the printed circuit board back into the back cover, and plug the terminal block back in.
6. Screw on the mobile antenna.
7. Put the front cover back.
8. If you also send the events to the monitoring station over the wired network (LAN), plug the network cable into the communicator's LAN socket.

3.2 Placement in the control panel's enclosure, antenna

The communicator must be placed in the alarm control panel's enclosure protected by a cover tamper switch. Fix it to the inner back wall of the enclosure with the supplied industrial-grade double-sided acrylic foam tape: stick the tape on a clean, dry surface with firm pressure so that it holds securely. If the control panel's enclosure does not allow this secure fixing, the communicator can also be mounted in a separate, tamper-protected enclosure.

• In a metal enclosure the mobile signal is strongly attenuated. If the communicator goes into the control panel's metal housing, lead the antenna outside the enclosure, or use an antenna with a longer cable.
• Before final fixing, check the signal level: the number of yellow flashes of the NETWORK LTE LED must be at least 3 on 4G (section 1.6). If it is less, find a better place for the antenna, or switch to a more sensitive antenna that can be placed further away.
• Keep the antenna and the communicator away from the control panel's transformer and from mains wiring.
• Lead the LAN cable through the enclosure's cable entry into the RJ45 socket on the side of the communicator; the cable must not pull on the terminals.

3.3 Connection to the alarm control panel

Follow the diagram below that matches your control panel. On the diagrams +DC and −DC are the communicator's +12 VDC / −12 VDC power terminals, and A RS485 / B RS485 are the A 485 / B 485 terminals (these do not need to be connected on the GET). The communicator gets its power from the control panel's auxiliary power output (AUX), so during a power cut the control panel's battery also powers the communicator.

3.3.1 DSC – data bus (Keybus)

Connect the DSC control panel's Keybus to the communicator with four wires: RED → +DC, BLK → −DC, YEL → CLK, GRN → DATA.

3.3.2 Paradox – serial port

The communicator connects to the Paradox control panel's serial port with the EX-CRP2.4 cable, ordered separately: red → +DC, black → −DC, yellow → CLK, green → DATA.

• red wire ("R - red")
• black wire ("B - black")
• yellow wire ("Y - yellow")
• green wire ("G - green")

On the newer Paradox control panels (SP+, MG+, EVOHD+) the serial port may be locked at the factory; unlocking is covered in section 4.1.2. With the Spectra SP / SP+ and Magellan MG / MG+ control panels, the connection described in the next section can also be used instead of the serial port.

3.3.3 Paradox SP/MG – Keybus and TIP/RING

The Paradox Spectra SP, SP+ and Magellan MG, MG+ control panels can also be connected to their data bus (Keybus) and TIP/RING terminals together instead of the serial port: +AUX → +DC, −AUX → −DC, GRN → DATA, YEL → CLK, and TIP → TIP, RING → RING. This connection uses the control panel's Keybus instead of the serial port, so the paid Paradox serial port unlocking is not needed for it.

For this connection, set the following on the TrikdisConfig Panel settings page:

1. Communication protocol: 2. AUTO.
2. Security panel model: select Paradox SP+/MG+ series KeyBus from the list (in the picture 7. PARADOX SP+/MG+).
3. Remote Arm/Disarm: tick it if the users want to control the control panel from the Protegus 2 app with their own keypad code.
4. Security panel PC download password: for direct control, enter the PC password set in the control panel; the two must match.

In the Protegus 2 app the same settings are on the Panel settings → TLF (Security panel model = Communication protocol) and Panel settings → Serial Bus pages (section 6.3).

The Paradox control panel must also be programmed so that it sends the events to the monitoring station and can be controlled from Protegus 2 – on the keypad connected to the control panel, set the following sections:

The PC password entered in section 911 must match the communicator's Security panel PC download password field (section 4.1.2).

3.3.4 UTC Interlogix (Caddx) – data bus

Connect the Caddx NetworX control panel's data bus to the communicator with three wires: POS → +DC, COM → −DC, DATA → DATA. The CLK, TIP and RING terminals are not needed.

3.3.5 Texecom – serial port

The communicator connects to the Texecom Premier / Premier Elite control panel's serial port with the EX-CRP4 cable, ordered separately: red → +DC, black → −DC, blue → CLK, white → DATA.

• red wire ("R - red")
• black wire ("B - black")
• blue wire ("BL - blue")
• white wire ("W - white")

3.3.6 InnerRange Inception

The communicator gets its power from the Inception control panel's power output (VOUT + → +DC, VOUT 0V → −DC), and the data connection comes from the control panel's USB port, with Inner Range's 993030USB cable: black → 0V / −DC, green → CLK, white → DATA.

• black wire ("Black wire")
• green wire ("Green wire")
• white wire ("White wire")

3.3.7 InnerRange Integriti

The communicator connects to the Port 0 serial port of the Integriti control panel with Inner Range's INTG-996795 cable: +DET (+13 V) → +DC, GND (5) → −DC, Rx (3) → CLK, Tx (2) → DATA.

3.3.8 Honeywell Vista – data bus

Connect the keypad bus of the Honeywell Ademco Vista-15, Vista-20 and Vista-48 control panels from the control panel's terminals to the communicator: 5 → +DC (+12 V), 4 → −DC, 7 → CLK, 6 → DATA.

3.3.9 Any control panel – TIP/RING

Any other control panel can be connected through its telephone line communicator: power from the control panel's auxiliary power output (+AUX → +DC, −AUX → −DC), the telephone line output to the communicator's TIP and RING terminals (TIP → TIP, RING → RING). The control panel's dialer must be set up (section 4.2).

• 1 terminals of the control panel's telephone line communicator ("Telephone line communicator terminals")

3.4 Wiring a keyswitch zone

Follow this wiring if you want to arm and disarm the control panel from the Protegus 2 app with the communicator's output (PGM) switching the control panel's keyswitch zone. The communicator's two dual-function I/O terminals work as outputs (OUT, PGM) – on the GET both are outputs by default –, so the two outputs can control two partitions of the system: connect the keyswitch zone of partition 1 to the 1 I/O terminal, and that of partition 2 to the 2 I/O terminal. With this wiring, untick Remote Arm/Disarm on the TrikdisConfig Panel settings page, set the terminals to the OUT function on the IN/OUT page (section 6.7), and in the Protegus 2 app assign the outputs to the partitions as described in section 5.2.

With a data bus or serial connection, the data connection between the control panel and the communicator remains (the communicator reads the events from the bus), and arming and disarming are done through the keyswitch zone:

• 1 keyswitch zone of partition 1 ("1-st Area")
• 2 keyswitch zone of partition 2 ("2-nd Area")

With a telephone line (TIP/RING) connection, the control panel sends the events with its dialer, and arming and disarming are done through the keyswitch zone in the same way:

• 1 keyswitch zone of partition 1 ("1-st Area")
• 2 keyswitch zone of partition 2 ("2-nd Area")
• 3 terminals of the control panel's telephone line communicator ("Telephone line communicator terminals")

The keyswitch zone can be pulsed or two-state (latched) – the same mode must be set in the Protegus 2 app (section 5.2). The details and pitfalls of keyswitch arming are covered in a separate article: Remote arming with a keyswitch from the Protegus 2 app.

3.5 Wiring inputs

The communicator's two dual-function I/O terminals can also be used as inputs (IN) for additional detectors (e.g. tamper switch, panic button), independently of the alarm control panel. An NO, NC, NO/EOL, NC/EOL, NO/DEOL or NC/DEOL circuit can be connected to the input. On the GET the terminals are outputs by default: set the terminal you use to the IN function on the TrikdisConfig IN/OUT page, and enter the type of the connected circuit in the Type field; in the Protegus 2 app the same is on the Advanced settings → IN/OUT page, in the Type field of terminal 1 or 2 (section 6.7). The input must be connected between the selected I/O and the COM terminal, according to the selected type.

The inputs accept the following circuit types: NC, NO, NC/EOL, NO/EOL, NC/DEOL, NO/DEOL. The end-of-line resistor is 2.2 kΩ. With a single end-of-line resistor (EOL), both a short circuit and an open circuit count as an alarm; with double end-of-line resistors (DEOL), the two resistors allow the alarm and the tamper (short or open circuit) to be recognised separately. The factory setting is NO (normally open); you set the input type on the IN/OUT page of TrikdisConfig, according to the wiring.

When the input is triggered, the communicator sends its own event to the monitoring station and to Protegus 2; you can set the event's Contact ID code, partition and zone number on the IN/OUT page.

Wiring the input circuits between the COM and INx points: NO, NC, NC/EOL, NO/EOL, and with tamper detection NO/DEOL and NC/DEOL, with 2.2 kΩ end-of-line resistors; the individual states (short circuit, open circuit, 2.2 kΩ, 3.3–5.5 kΩ) are explained in the table of section 3.5.

• T tamper contact ("Tamper"), it signals opening of the detector's cover

• T tamper contact ("Tamper"), it signals opening of the detector's cover

3.6 Wiring an output with a relay

As outputs, the I/O terminals are open collector (OC) outputs: in the active state they pull the connected load to negative, with at most 0.15 A, up to 30 V DC. With the contacts of a relay you can switch various electrical devices on and off: one end of the relay coil goes to +DC, the other to the x I/O terminal, and the load is switched by the relay contacts (NC, C, NO). The I/O terminal you use must be an output (OUT) on the TrikdisConfig IN/OUT page (or on the app's IN/OUT page) – on the GET this is the default setting.

• R relay ("Relay")

You can switch the outputs from the Protegus 2 app (chapter 5).

3.7 Power-up and first check

Starting the TRIKDIS communicator

1. For SIM card communicators, insert the SIM card into the device before starting.
2. For devices with Ethernet, you can connect the Ethernet cable before or after starting up.
3. For startup, unplug the USB cable and connect the pulled jumper.

You can proceed to the next chapter when the device starts correctly and does not indicate any errors.

• The Power LED is green
• The Trouble LED does not flash red
• The Network LED is green (if it flashes yellow, it is okay)
• If the Data LED does not turn off, it means that the device cannot send some event. This indicates an internet / data connection error.

After wiring, the communicator also starts when the alarm control panel's power is switched on. On the front cover you should see:

• POWER steady green – the power supply is adequate;
• NETWORK LTE steady green and flashing yellow – connected to the mobile network; the number of yellow flashes is the signal level: on 4G, 3 flashes are adequate; if you count fewer, the signal is weak: find another place for the communicator or the antenna, or use a more sensitive antenna (section 3.2);
• NETWORK LAN steady green if you have also plugged in a network cable – connected to the wired network;
• TROUBLE off.

If TROUBLE flashes, the number of flashes tells you the cause (section 1.6); any other LED indication also signals some fault, look up its cause in the tables of section 1.6. If none of the LEDs light up, check the power supply and the wiring.

4. Programming the alarm control panel

How the control panel is set up depends on how you connected it: over the data bus or serial port (section 4.1), or through its telephone line communicator, on the TIP/RING terminals (section 4.2). For the Paradox SP / SP+ / MG / MG+ Keybus + TIP/RING connection, the settings of the control panel's sections are given in the table of section 3.3.3.

4.1 Data bus or serial connection

This section describes how to set up the control panel so that the communicator reads its events and can control it remotely. For remote control, the Remote Arm/Disarm option must be ticked on the TrikdisConfig Panel settings page (in the app: Panel settings → Serial Bus) (sections 2.2 and 6.3).

4.1.1 DSC

DSC PowerSeries panels (the list of supported models is in section 1.2) do not require any special settings: the communicator connected to the Keybus reads the events immediately, and once Remote Arm/Disarm is ticked, the user arms and disarms from the app with their own keypad code. The details of direct control – zone states, zone bypassing, automatic detection of partitions – are covered in a separate article: Direct control for DSC PowerSeries alarm panels.

4.1.2 Paradox

Paradox panels only need to be programmed for direct control; nothing needs to be set for reading the events. The panel's firmware must be at least V.4.

For control, the panel's PC password must be set, and the same must be entered in the System settings → Security panel PC download password field of TrikdisConfig – the two must match.

1. Enter the panel's installer programming on the keypad.
2. Open the PC password section: section 911 for the MAGELLAN and SPECTRA series, section 3012 for the DIGIPLEX EVO series.
3. Enter a 4-character password. The password cannot be 0000 and must not start with zero.
4. Exit programming and restart the panel – a change of the PC password takes effect after a restart. Then enter the same password in TrikdisConfig.

Keybus and TIP/RING connection (SP / SP+ / MG / MG+, section 3.3.3): in addition, the control panel must be programmed to send the events to the monitoring station and to be controllable from Protegus 2 – the values of the sections (801, 811, 812, 815, 911) are given in the table of section 3.3.3.

4.1.3 Texecom

Texecom Premier / Premier Elite panels must be programmed both for reading events and for control: you need to set the panel's 4-character password called UDL passcode, and enter the same in the System settings → Security panel PC download password field of TrikdisConfig – the two must match.

With Texecom's Wintex software: the UDL passcode is on the Options tab of the Communication Options window.

From the keypad:

1. Enter the 4-digit installer code and press [Menu] to enter the programming menu.
2. Immediately afterwards, press [9].
3. Press [7][6], then [2], and enter the 4-digit UDL passcode.
4. Press [Yes], then exit programming with the [Menu] button.

4.1.4 UTC Interlogix (Caddx)

The firmware of the UTC Interlogix (Caddx) NetworX panel must be at least V2. The following must be set on the panel's keypad:

1. Press [*][8] and enter the installer code (default 9713).
2. Enter the device number (device address) assigned to the communicator (default 0).
3. Program the rows of the table below one after the other: enter the location, the segment number and then the setting. You can go back to the previous field with the [*] button. 12345678 means that all eight switches of the segment are on (all digits are visible on the display).

4. When you have programmed all rows, press [Exit] twice to leave programming.

4.1.5 InnerRange

The firmware of the InnerRange Inception panel must be at least 2.3.0.3507-r0, and the panel needs an internet connection. The settings are made in the panel's web interface:

1. Open https://skytunnel.com.au/inception/SERIALNUMBER in a browser, where SERIALNUMBER is the serial number on the panel's box. Log in with the installer account.
2. Open the Configuration → General → Alarm Reporting page.
3. In the 3rd Party Device Configuration group: - tick Enable 3rd Party Device Reporting; - in the 3rd Party Device Type field, select Trikdis; - in the Serial Port field, select Serial Port 1 (Plugged In, In Use By 3rd Party Device).
4. Save the settings and log out of the interface.

The firmware of the InnerRange Integriti panel must be at least 19.1.0.36608, and its programming software (Integriti Professional) at least 19.1.0.15396. The settings are made in the panel's programming software:

1. For the serial port (TTL Port-0) to which the communicator is connected, select the Trikdis communication protocol.
2. The data format must be Contact ID.
3. Port settings: 19200, 8, N, 1.
4. Save the settings and exit the program.

4.1.6 Honeywell Ademco Vista

The firmware of the Honeywell Ademco Vista-20 and Vista-48 panels must be at least V5.3. The settings are made on the panel's keypad.

Entering programming – in two ways:

• enter the installer code (default 4112), then press [8][0][0]; or
• power up the panel and within 50 seconds press the [*] and [#] buttons at the same time (this only works if programming was previously exited with [*][9][8]).

Settings:

1. Enable sending Contact ID events on the long range radio (LRR) output: press [*][2][9][1][#].
2. For remote control, enable the use of the 2nd AUI address: press [*][1][8][9][1][1][#].

Exiting programming: press [*][9][9].

4.2 Telephone line (TIP/RING) connection

For the alarm panel to send events on its telephone-line output, the panel's dialler must be enabled and configured. You will find the exact program addresses in the panel's installation manual; the essence of the setting is the same for every manufacturer:

1. Enable the telephone-line (PSTN) communicator in the panel.
2. Enter 1234 as the telephone number of the monitoring receiver – whether the communicator is connected to the panel's RING/TIP terminals or to the telephone line. With another number it can happen that the panel dials but the communicator still does not receive the events: with a DSC PowerSeries NEO panel, too, reporting only started after the number was changed to 1234.
3. Dialling mode: DTMF (tone), not pulse.
4. Protocol: Contact ID.
5. Account number: the 4-digit account number received from the monitoring station (for Protegus 2 it does not have to be unique, but for the monitoring station it does).

If you want to arm and disarm the panel remotely with the communicator's output, the zone wired to the output must be set as a keyswitch zone in the panel.

The DSC, Paradox, Caddx, Texecom, InnerRange and Honeywell control panels can also be connected to the communicator through their telephone line output (section 3.3.9) – in that case the dialer must be set up for these as well, and direct control is not available.

4.2.1 Programming the Honeywell Vista dialer

Enter programming mode on the keypad and set the following program addresses:

For a Honeywell Vista 48 panel, also set the following program addresses:

At the end of programming, exit programming mode with the *99 command.

4.2.2 The dialer of the UTC Interlogix (Caddx) NX

Programming the Interlogix NX-4V2 (NX-6V2, NX-8V2) control panel when the communicator is connected to the control panel's TIP/RING terminals. On the keypad, enter the following one after the other:

5. Remote control with the Protegus 2 app

With the Protegus 2 mobile and web app the user sees the state of the system remotely, receives notifications about the events, can arm and disarm, and can switch the communicator's outputs. The app can be downloaded for Android and iOS (Google Play, App Store), or used in a browser: web.protegus.app. Log in with your user name and password, or register a new account. The GET does not notify by SMS or phone call, and does not accept SMS commands either: remote control and notification are done through the app; the communicator's settings are also available from the app (Settings → Advanced settings, chapter 6).

5.1 Adding the device

Before adding the device, check:

1. The SIM card is active, and its PIN code is entered in the device, or the PIN request is switched off – or the communicator is connected to the local network with a network (LAN) cable.
2. On the TrikdisConfig User reporting → PROTEGUS Cloud page, Enable connection is ticked (section 6.5).
3. The POWER LED is steady green.
4. The NETWORK LTE LED is steady green and flashing yellow (the device is on the mobile network); with a wired connection only, the NETWORK LAN LED is steady green.

Creating the system in the Protegus 2 application

1. Download the Protegus 2 application to your phone or open it in a browser




2. Register an account if you haven't already.
3. Log into your account.
4. On the main page, click the "+" button to create a system

5. Enter the unique identifier of the TRIKDIS device (you can also scan the barcode or QR code with your phone's camera), which you can find
   • On the sticker of the device
   • On the device's cardboard box
   • In the bottom left corner of TrikdisConfig (selectable and copyable format)

6. Enter the system name and select a time zone

7. Your system is created, you can still name the partitions and zones at the next step, but you can do this later anytime.

8. In the last step, your system's home screen will appear. Wait until the yellow stripe disappears and your system is ready.

The device's unique identifier (IMEI / Unique ID) can be read on the device's label and on the sticker on the box, and the TrikdisConfig status bar also shows it. If the PROTEGUS Cloud access Code in the device is not the default one, the app asks for it when adding.

5.2 Arming and disarming with an output

If you want to arm and disarm the alarm panel with the communicator's output, through the panel's keyswitch zone, specify in the Protegus 2 app for the partition which output controls it.

You can make the setting when creating the system, while adding the partitions, or later in the system settings, when editing the partition. When creating the system, the Protegus 2 wizard guides you through: click Continue, enter the partition name (Area name) and enable control of the PGM output from the Protegus 2 app – this is done with the following steps:

1. Select (or add) the partition you want to control. The partition number must match the one the panel sends in its events (partition 1 as 1, partition 2 as 2).
2. Switch on Control with Protegus2 (control with PGM), and in the Assigned Output field select the communicator output (PGM1, PGM2 …). One output can control only one partition.
3. Select the operating mode: Pulse or Level (latched) – the same one you set for the keyswitch zone in the panel. Typically we use pulse; the pulse length can also be set (default 3 s).
4. Save the setting (Save). With several partitions, repeat this for each one with its own output: in the wizard you add a further partition with the Click to add an area button and set its PGM output in the same way. When you have set up all partitions, move on in the wizard with the Skip button.

5.3 Arming and disarming from the app

1. Open the system in the Protegus 2 app. On the home screen every partition has its own card and padlock: a closed, red padlock means an armed partition, an open, green padlock a disarmed one.
2. Tap the partition's padlock and select the required action: arm or disarm.
3. If the app asks for it, enter the PIN code.

The padlock takes on the actual state in response to the event received from the alarm panel; the app also confirms in the event list and in a notification whether the panel has carried out the action.

6. The settings in detail

Most settings of the GET are available both in the TrikdisConfig software running on Windows and in the Protegus 2 app (Settings → Advanced settings, section 2.2); where something is only in one of them, we say so. Every setting is described once, and for each section we give where you find it in the two tools; the app's label is in brackets if it differs from TrikdisConfig's. On the left side of the TrikdisConfig window you see the list of pages (System settings, Panel settings, CMS reporting, User reporting, Network settings, IN/OUT, Event summary, Firmware), at the top the button bar (Read [F4], Write [F5], Open [F8], Save [F9]), and at the bottom the status bar.

6.1 Connecting to the communicator

Protegus 2 app. Open the system and go to the Settings → Advanced settings menu. At the top of every screen you see the data of the connected device: Unique ID (IMEI), Serial (serial number), Firmware and Boot version. The groups of settings in the menu: System options, Panel settings, Reporting to CMS, User reporting, Network settings, IN/OUT and System events. After making changes, you write the settings into the device with the Write button; Read reads the current values from the device again.

TrikdisConfig. After connecting the communicator and pressing Read [F4], the program shows the device's data in the status bar.

After connecting the device and reading it (Read [F4]), the most important device data are shown at the bottom of the window:

After making the settings, you write them to the device with the Write [F5] button; with the Open [F8] and Save [F9] buttons you can save the complete set of settings to a file and load it into another device. Save [F9] saves the settings to a settings file, and Open [F8] opens the saved file; you can later load the saved settings into other devices as well, so you can quickly set up several devices with identical settings.

The Device field must show a GET type code (in the picture GET_S170; the letter-number suffix indicates the hardware version), BL is the bootloader version. After Read [F4] the program reads out and shows the values set in the device; make the necessary settings according to the page descriptions below.

6.2 System settings (System options)

In the app: Advanced settings → System options → System general (identifiers, time synchronization) and System options → Access (codes and installer rights). Where the Account No. and the Device account No. are depends on the hardware version and the firmware: on x1x1 hardware, with firmware 1.31 or newer, you find them on the Reporting to CMS → CMS settings → Primary channel page (Primary Account no.; on the parallel channel Parallel Account no.) and on the Reporting to CMS → Settings page (Device account No.), and only Time set remains on the System general page; otherwise both are on the System general page.

In TrikdisConfig: the System settings page consists of two groups: in the General group you set the device's identifiers, in the Access group the access levels.

• Object ID (Account No.) – the account number received from the monitoring station (6 hexadecimal characters: 0–9, A–F; FFFE and FFFF cannot be used). Mandatory if the device also reports to a monitoring station.
• Module ID (Device account No.) – the module's identification number.
• Time set – the server from which the device synchronizes its clock.

In the Access group you manage the access levels and passwords.

There are two access levels for the device settings: administrator and installer.

• Administrator code – access to all settings (default password: 123456; the password is 6 characters: digits or Latin letters).
• Installer code – access that can be restricted (default password: 654321).
• Only an administrator can restore – when ticked, only the administrator can start restoring the factory settings.
• Allow installer to change – here you can select which groups of settings the installer may change: Account number, CMS reporting, User reporting, SIM card (on a mobile network device) or Ethernet settings (on an Ethernet device), Event summary.

Installer login in the app. If you open the communicator with the installer code, Protegus 2 hides the Administrator code and Only an administrator can restore fields, and shows the settings not allowed by the administrator as read-only. In the app the SIM card right also covers the LAN settings; where the identifiers are among the CMS settings (see above), the CMS reporting right applies to them.

6.3 Panel settings

On this page you set how the communicator connects to the alarm control panel: the TLC group (in the app TLF) contains the settings of the telephone line (TIP/RING) connection, the Serial bus group (Serial Bus) those of the data bus or serial connection. In the app: Advanced settings → Panel settings → TLF or Panel settings → Serial Bus.

TLC group – if the communicator is connected to the TIP/RING terminals of the control panel's telephone line communicator:

• Communication protocol (Security panel model) – switches the communicator's DTMF telephone line interface on (2. AUTO) or disables it (1. DISABLED). For a TIP/RING connection, select AUTO.
• First HSK tone, Second HSK tone – the handshake tone with which the communicator answers the control panel's dialer (in the picture Dual Tone and SIA FSK).
• Use security panel account ID – when ticked, the communicator does not send the value of its own Object ID field, but the account number set in the control panel and sent by the control panel.
• Wait acknowledgment from CMS – when ticked, after sending each event the communicator waits for the IP receiver's acknowledgment that the message has arrived; if the acknowledgment does not come, it does not give the "kiss-off" signal to the control panel, and the control panel's telephone line communicator repeats the message.
• Dial tone frequency – the frequency of the dial tone with which the communicator communicates with the control panel's dialer (default 425 Hz, the dial tone used in most European countries). On the app's TLF page there is also the Dial tone enabled switch: it switches the dial tone on or off; the frequency can only be changed when the dial tone is switched on.

Serial bus group – if the communicator is connected to the control panel's data bus or serial port:

• Event coding protocol (Protocol) – the event reporting protocol: CID or SIA.
• Security panel model – the type of the connected alarm control panel from the list (for the Paradox SP / SP+ / MG / MG+ Keybus + TIP/RING connection, select Paradox SP+/MG+ series KeyBus, section 3.3.3).
• Remote Arm/Disarm – when ticked, the communicator controls the control panel directly (arming and disarming from Protegus 2). Only visible for directly controllable control panels. For direct control the control panel must also be set up as described in section 4.1.
• Event – when ticked, the communicator sends the control panel's events to the monitoring station and to Protegus 2. The app shows this switch, but it cannot be changed there.
• Security panel PC download password (PC download password; for Texecom the UDL passcode) – for direct control of a Paradox or Texecom control panel, the PC or UDL password; it must match the password set in the control panel, which is described in section 4.1.

6.4 CMS reporting (Reporting to CMS)

The communicator sends the events to the monitoring station over an IP connection – over the wired network (LAN) or the mobile network (SIM1, SIM2), in the order set in section 6.4.2. The events can go over several channels: the primary and the parallel channel work at the same time (to two receivers at once), and each has a backup channel that takes effect if the given channel fails. Communication is encrypted and password-protected. The TRK protocols require a Trikdis receiver that receives the events and forwards them to the monitoring software: for an IP connection the IPcom software receiver (Windows or Linux), the RL14 IP/SMS receiver or the RM14 multi-channel receiver; the DC-09 and TL150 protocols are for universal and SUR-GARD receivers respectively (see below, Protocol).

6.4.1 Receiver channels (CMS settings)

In the app: Advanced settings → Reporting to CMS → CMS settings, then Primary channel, Backup channel or Parallel channel (within it Parallel primary channel and Parallel backup channel). The channel's settings appear when you switch on the Enabled switch.

In TrikdisConfig: the CMS settings tab of the CMS reporting page.

Primary channel

• Communication type – the mode of connection with the receiver: IP.
• Protocol – TRK8 (Trikdis receivers), DC-09_2007 or DC-09_2012 (universal receivers), TL150 (SUR-GARD receivers).
• Encryption key (TRK encryption key; with the DC-09 protocols Enable encryption key and DC-09 encryption key, with the HEX switch for a hexadecimal key) – the encryption key of the messages; it must be the same in the communicator and in the receiver. In the app the TRK encryption key is at most 6, the DC-09 encryption key at most 16 characters (32 in HEX).
• Domain or IP, Port – the receiver's domain name or IP address and network port.
• TCP or UDP – the transmission protocol.

Primary channel Backup – backup channel. When switched on, it takes over communication if the primary channel does not work; its settings are the same as above.

Parallel channel. Alongside the primary, it sends to a second receiver at the same time (for example to the local and the central monitoring station). Its settings are the same as those of the primary channel.

6.4.2 Test, PING and the order of connections

In the app: Advanced settings → Reporting to CMS → Settings (test, PING, backup channel timings, receiver and line number) and Reporting to CMS → CMS settings → Reporting mode (the order of the connection paths). In the app there is a switch next to every interval: Enable test for the Test period, Enable ping for the IP ping period and Test enabled for the Communication path test; on the Reporting mode page the connection types are called LAN, SIM (SIM1) and SIM2.

In TrikdisConfig: the Settings tab of the CMS reporting page.

• Test period – the interval of the periodic test report (default 24 hours). The test report is sent as a Contact ID message to the monitoring station and to Protegus 2.
• IP ping period – the interval of the keep-alive signal (PING) on the IP channel (default 30 s). You enable it with the tick box and enter the time in the minutes (min) and seconds (s) fields; it is required for connection supervision. The receiver does not forward PINGs to the monitoring software so as not to overload it; the software only receives a message if the receiver gets no PING for three times the set period. For example, if the PING period is 3 minutes, the loss of connection is reported after the 9th minute.
• Backup reporting after – after this many failed sending attempts the device switches to the backup channel (default 2).
• Return from Backup after – after this time it returns to the primary channel (default 1 min 30 s).

DC-09 Settings (on the right side of the tab) – only needs to be filled in if you send with the DC-09_2007 or DC-09_2012 protocol on any channel; the group appears when DC-09_2007 or DC-09_2012 is selected in the Protocol field of any channel:

• Object ID in DC-09 – a 3–16 character hexadecimal identifier, provided by the monitoring station.
• DC-09 line No – the line number.
• DC-09 receiver No. – the receiver number.

On the GET's Settings tab, the Line No. (the receiver's line number) and Receiver No. (receiver number) fields are also here; there is no separate "Object ID in DC-09" field on the GET.

Reporting mode group – here you set the path on which the communicator communicates with the monitoring station channels and with Protegus 2. You enter the connection types in order: if the connection set in Main type cannot be established, the communicator switches to the one set in Backup type, and so on; if the message was sent successfully on the backup path, after the set time (Return from backup after) it tries the main path again.

• Main type – the type of the main connection with the receiver and with Protegus 2: LAN, SIM1 or SIM2.
• Backup type – the type of the backup connection (LAN, SIM1, SIM2).
• Backup type 2 – the type of the second backup connection (LAN, SIM1, SIM2).
• Communication path test – the interval at which the communicator tests the selected connection types (LAN, SIM1, SIM2).

6.5 User reporting (Protegus Cloud)

With the Protegus 2 service the user monitors and controls the communicator and the system connected to it remotely; details: web.protegus.app. In the app: Advanced settings → User reporting → Cloud; in TrikdisConfig the PROTEGUS Cloud tab of the User reporting page.

• Enable connection (Enabled) – enables the Protegus 2 service: the device exchanges data with the Protegus 2 app, and TrikdisConfig can also reach it remotely.
• PROTEGUS Cloud access Code (Cloud access code) – 6-digit code for connecting to Protegus 2 (default 123456). If you change it in TrikdisConfig, it must also be changed in the Protegus 2 app.
• Parallel reporting (in the app only visible if the firmware supports it) – when ticked, the messages go on the primary channel (to the monitoring station) and to Protegus 2 at the same time; Protegus 2 and the users only receive the message after it has been sent to the monitoring station.

6.6 Network settings

6.6.1 LAN (Ethernet)

These settings must be entered if the communicator is connected to the wired local network (LAN). In the app: Advanced settings → Network settings → LAN; Static IP, Subnet mask, Default gateway, DNS1 and DNS2 can only be changed with Use DHCP switched off. In TrikdisConfig the LAN tab of the Network settings page, Ethernet settings group.

What does the network need? The communicator itself initiates the outgoing connection to the monitoring receiver and the Protegus cloud, so no port needs to be opened or forwarded on the router, and neither a public static IP address nor dynamic DNS is needed. What you do need:

• a free Ethernet port on the router or switch;
• DHCP (factory setting), or a static IP address, subnet mask, gateway and DNS provided by the network administrator;
• outgoing traffic allowed to the receiver's address and port (TCP or UDP, depending on the receiver setting), as well as to the Protegus cloud.

On a filtered – corporate or institutional – network, agree on this with the network administrator in advance: home routers allow all outgoing connections by default, but a firewall-protected network may need a separate rule.

• Use DHCP – when ticked, the communicator logs on to the network automatically (it gets an address from the router's DHCP server). If automatic logon fails, the addresses must be entered manually:
• Static IP – the communicator's fixed IP address with manual setup.
• Subnet mask – subnet mask with manual setup.
• Default gateway – the address of the gateway (router) with manual setup.
• DNS1, DNS2 – name servers (DNS, Domain Name System: it gives the IP address belonging to a domain name); they are needed if you entered the receiver in the channel's Domain or IP field with a domain name and not an IP address. The default is Google's public DNS. Regardless of the IP settings, check that the DNS addresses work with your internet service provider.

6.6.2 SIM1 and SIM2

These settings must be entered separately for every inserted SIM card; the settings of the SIM1 and SIM2 holders are the same.

In the app: Advanced settings → Network settings → SIM (SIM1) or SIM2. In TrikdisConfig the SIM1 or SIM2 tab of the Network settings page, SIM card group.

• SIM card PIN – the card's PIN code. You can switch off the PIN request by putting the card into a mobile phone and disabling it there; in that case the field's default value can stay.
• APN – the operator's access point (Access Point Name); without it the device does not connect to the internet. You can find the value on the website of the SIM card's operator; internet is generic and works in many operators' networks. The known APNs of operators are listed in the APN article (for an IoT / M2M card the operator gives a separate APN, see section 2.3).
• Login, Password – user name and password for the internet connection, if the operator requires them.
• SIM ICCID – the SIM card's ICCID number, if you want the device to work only with this card.
• DNS1, DNS2 – name servers; they are needed if you entered the receiver in the channel's Domain or IP field with a domain name. The default is Google's public DNS; check that the DNS addresses work with your operator.
• Preferred operator – the mobile operator's code (MCC + MNC); if you enter it, the device only connects to the selected operator's network. Only in TrikdisConfig.

On the app's SIM page, instead of Preferred operator there is the Forbid connection when roaming detected switch: when switched on, the communicator does not connect if it detects roaming. On hardware version M15, with firmware 1.17 or newer, the Generation and Bands settings also appear on the SIM page: with these you can restrict which mobile network technology and frequency bands the communicator uses.

6.7 IN/OUT

Here you set the role of the communicator's two dual-function I/O terminals: Disabled (not used), IN (input) or OUT (output; on the GET this is the default setting). For an input, the type of the connected circuit must also be set in the Type field (NC, NO, NO/EOL, NC/EOL, NO/DEOL, NC/DEOL). Additional detectors can be connected to the inputs: when the detector is triggered, the communicator sends its own event with the Contact ID (SIA) code assigned to the input to the monitoring station and to Protegus 2.

In the app: Advanced settings → IN/OUT, then terminal 1 or 2: the Function (Disabled, IN, OUT) and for an input the Type; in the Alarm and Tamper sections the event and restore messages sent when the input is triggered. In TrikdisConfig the IN/OUT page.

When the detector connected to the input is triggered, the communicator sends an alarm (INx_ALARM, Contact ID 130, SIA BA; restore BH), and when the tamper circuit is violated, a tamper event (INx_TAMPER, 144, SIA TA; restore TR); the events of every terminal set as an input appear in the table. The columns of the table:

• Enable (Enabled) – enables sending the message to the monitoring station and to Protegus 2.
• E/R (Classificator) – the type of the message: Event or Restore.
• CID (CID code) – the Contact ID code (it can be changed, or the default can stay); when the input is triggered, the message goes to Protegus 2 and to the monitoring station with this code.
• SIA (Sia code) – the SIA code (it can be changed, or the default can stay).
• Part. (Partition number) – the partition number in the message (for the event and the restore as well).
• Zone (Zone number) – the zone number in the message.

6.8 Event summary (System events)

Here you can enable, disable and change the device's own internal messages. A message disabled here is not sent, regardless of any other setting. In the app: Advanced settings → System events, the messages are in the Event and Restore lists; to change one, select the message. In TrikdisConfig the Event summary page.

The GET's internal messages (in brackets the default Contact ID code and zone):

• COMMUNICATION (350, zone 999) – fault of the connection between the control panel and the communicator; its restore is a separate message.
• LAN_FAILURE (358, zone 903) – fault of the wired network (LAN) connection; its restore is a separate message.
• POWER (302, zone 999) – low supply voltage; its restore is a separate message.
• REMOTE_FINISHED (412) – end of remote programming with TrikdisConfig (disconnection).
• REMOTE_STARTED (411) – remote connection for programming the GET with TrikdisConfig.
• SIM1_FAILURE (358, zone 901) – fault of the mobile network connection on SIM1; its restore is a separate message.
• SIM2_FAILURE (358, zone 905) – fault of the mobile network connection on SIM2; its restore is a separate message.
• TEST (602) – periodic test report.

• Enable (Enabled) – when ticked, sending the message is enabled.
• For every message, the Contact ID (SIA) code, and the zone and partition number can be changed.

6.9 Restoring the factory settings

The factory settings can not be restored from the Protegus 2 app: this requires the TrikdisConfig Restore button or the device's RESET button.

To restore the factory settings, click the Restore button in the Default settings group at the bottom left of the TrikdisConfig window. Restoring deletes all settings – including the passwords – so it is worth saving the settings to a file first (Save [F9]).

The factory settings can also be restored on the device, without a computer: with the power on, press and hold the RESET button on the printed circuit board (section 1.4) for 10 seconds, until the NETWORK, POWER and TROUBLE LEDs go out and then the POWER LED lights up. Then release the button: the factory settings have been restored.

7. Remote programming

TrikdisConfig reaches Trikdis devices not only over a USB cable but also remotely, via the Protegus cloud. This way you can change the settings of an already installed device without going to the site.

Remote access requires:

1. The device must be switched on and have a network connection (the POWER and NETWORK LEDs are lit green; on a mobile network device the NETWORK LED also flashes yellow). On a mobile network device, the inserted SIM card must be active and its PIN code must be entered in the device, or the PIN request must be disabled; on an Ethernet device, the network (LAN) cable must be plugged in and the device must be able to reach the internet.
2. On the User reporting → PROTEGUS Cloud page of TrikdisConfig, Enable connection must be ticked (set this over USB during the first commissioning).
3. You need to know the device's unique identifier (IMEI or MAC – printed on the box and on the back of the device) and the administrator or installer password.

Steps:

1. Start the TrikdisConfig software.
2. In the Remote access section, enter the device's unique identifier (IMEI or MAC) in the Unique ID field.
3. Optionally, give the system a name in the System name field – the software remembers it, and next time you can choose it from the drop-down list.
4. Press the Configure button.
5. In the window that opens, click the Read [F4] button and enter the password. With the Remember password tick box, the software remembers it for this session.
6. Make the changes, then send them to the device with the Write [F5] button.

The GET's unique identifier is the IMEI / Unique ID; it can be read on the device's label and on the sticker on the box. Remote access only works if the SIM card is active, and its PIN code is entered or the PIN request is switched off – or the communicator is connected with a network (LAN) cable –; Enable connection is ticked on the User reporting → PROTEGUS Cloud page (section 6.5); the POWER LED is steady green; the NETWORK LTE LED is steady green and flashing yellow (with a wired connection only, the NETWORK LAN LED is steady green). The communicator reports the start and the end of remote programming with the REMOTE_STARTED and REMOTE_FINISHED messages (section 6.8).

8. Checking that the communicator works

After programming and wiring, always check the whole chain: alarm panel → communicator → monitoring station and/or Protegus 2.

Before that, check that there is power (the POWER LED is lit green) and a network connection (the NETWORK LED is lit green).

1. Trigger an event. Arm and then disarm the system on the keypad, or violate a zone while the system is armed so that an alarm is generated.
2. Check that it arrives. See whether the event has appeared in the monitoring software and/or in the event list of the Protegus 2 app – with the correct partition and zone number.
3. Inputs. Trigger the detector wired to the communicator's own input and check the corresponding event.
4. Outputs. Switch the output from the Protegus 2 app and check that the connected device (relay, keyswitch zone) actually operates.
5. Remote arming. If the panel can be controlled remotely, also arm and disarm it from the Protegus 2 app.

9. Firmware update

You can update the firmware yourself – to a newer version and, if necessary, to an older one as well. All device settings remain unchanged after the update.

1. Start the TrikdisConfig software and connect the device with a USB cable, or open its programming remotely.
2. If newer firmware is available, the software offers to download it – accept it.
3. Select the Firmware page and click the Open firmware button. Select the firmware file.
4. Press the Update [F12] button, wait for the update to finish, then click OK in the pop-up window. Do not unplug the cable or interrupt the connection in the meantime.

Some functions of the GET require a specific firmware version:

• 1.08 or newer: setup from the Protegus 2 app (Advanced settings, section 2.2 and chapter 6);
• 1.17 or newer, on hardware version M15: the Generation and Bands settings on the app's SIM page (section 6.6.2);
• 1.21 or newer: the Paradox SP / SP+ / MG / MG+ Keybus + TIP/RING connection (section 3.3.3);
• 1.31 or newer, on hardware version x1x1: in the app the identifiers (Account No., Device account No.) are among the CMS settings (section 6.2).

10. Troubleshooting and frequently asked questions

The most common questions and faults, starting from the LED indications. Where the answer refers to a detailed chapter, you will find the exact location of the setting there.

The NETWORK LTE LED is off – no mobile network

1. Look at the flashes of the TROUBLE LED: 2 = SIM1 card fault, 3 = SIM2 card fault (section 1.6).
2. Check that the SIM card is active, has data service, and sits properly in its holder (SIM1 in the middle of the board, SIM2 at its left edge; section 3.1).
3. If the PIN request is switched on for the card, enter the PIN on the Network settings → SIM1 (or SIM2) tab, or switch off the PIN request in a phone.
4. Check the APN (section 2.3): for an IoT / M2M card the operator gives a separate APN.
5. Check the antenna: it is screwed on, it is not in a metal enclosure, and the signal level is adequate (the NETWORK LTE LED flashes yellow at least 3 times; sections 1.6 and 3.2).
6. If the communicator reports over the wired network, the lack of the mobile network does not stop it by itself: it sends on the next available path according to the Reporting mode order (section 6.4.2) – but the backup path is then missing, so it is worth fixing.

The NETWORK LAN LED is off – no wired network

1. 1 flash of the TROUBLE LED indicates a fault in the physical connection of the wired network: check the LAN cable at both ends, and whether the router or switch port is live (section 1.6).
2. If the cable is fine, look at the Network settings → LAN tab: with DHCP the router must give an address; with a fixed address the Static IP, the Subnet mask and the Default gateway must match the local network (section 6.6.1).
3. If you entered the receiver with a domain name, the DNS addresses must also work in the network (DNS1, DNS2).

There is a network, but the monitoring station gets no events

The DATA LED is the simplest internet check. The DATA LED is lit when there is a message waiting to be sent in the device's memory. A green NETWORK LED only tells you that the network connection has been established – for a mobile network device, that it has registered on the operator's network; for an Ethernet device, that the connection up to the router is alive – but not that the device can also reach the internet. If the NETWORK LED is green but the DATA LED stays lit continuously even after an event or test report, the internet connection is not working: the message cannot be sent. On a mobile network the most common culprit is the APN or the data service of the SIM card; on Ethernet, the router, the firewall or the DNS. When the DATA LED goes out, the message has been sent and the data connection is fine.

1. Check the receiver's address, port, the TCP/UDP setting, the protocol and the encryption key (CMS reporting → CMS settings, section 6.4.1); the key must be the same in the communicator and in the receiver.
2. Look at the Reporting mode setting (section 6.4.2): the Main type must be a path that is actually available at the site (there is a LAN cable, or there is a SIM card in the given holder), and there must be a backup path too.
3. If the receiver is entered with a domain name, check the DNS setting on the path on which the communicator reports (Network settings → LAN, or SIM1 / SIM2 → DNS1, DNS2).
4. On the mobile network, check that the SIM card's data plan does not block the required port (some M2M cards only allow certain addresses); on the wired network, the local firewall must allow the receiver's port outbound.
5. If the control panel sends no events (the DATA LED does not light up), the cause is on the control panel side: see the next item.

The TROUBLE LED flashes seven times – no connection to the control panel

1. With a data bus or serial connection, check the CLK and DATA wires, and that the type of the connected control panel is selected in the Panel settings → Security panel model field (section 6.3).
2. With a Paradox control panel, check that the serial port is not locked (section 4.1.2); with Texecom and Paradox control panels the Security panel PC download password must match the one set in the control panel.
3. With a telephone line connection, the control panel's dialer must be switched on, in DTMF mode, with Contact ID format and a phone number entered (section 4.2), and Communication protocol must be 2. AUTO (section 6.3).

Which path does the event take: LAN or SIM?

The one given by the Reporting mode order (section 6.4.2): the path set in Main type; if that does not work, the one in Backup type, then in Backup type 2. If the message was sent on the backup path, the communicator tries the main path again after the Return from backup after time, and tests every path at the Communication path test interval. The Protegus 2 connection uses the same path. On the wired network no mobile data is used.

What are the two SIM holders for?

With cards from two different operators, the mobile network also becomes dual-path: in Reporting mode SIM1 and SIM2 are separate connection types, and either can be the main or the backup path (section 6.4.2). The two cards must be set up separately (Network settings → SIM1, SIM2: PIN, APN; section 6.6.2); a SIM2 fault is indicated by 3 flashes of the TROUBLE LED and the SIM2_FAILURE message (sections 1.6 and 6.8). The communicator also works with one card.

DSC: every alarm arrives as an E130 general alarm

When connected to the Keybus only, the communicator receives the state of the zones from the control panel, but not the zone type, so it reports every alarm with the E130 code (section 3.3.1). Connecting the Keybus and TIP/RING together is not available on the GET (it is a function of the GT+). If the monitoring station expects the code matching the zone type (for example fire: E110), connect the GET only to the control panel's TIP/RING terminals and program the dialer (sections 3.3.9 and 4.2): this way the control panel's own Contact ID codes are sent, but there is no direct control – arming requires a keyswitch zone (section 3.4).

Paradox: the serial port is locked, or there is no connection

On the newer Paradox control panels (SP+, MG+, EVOHD+) the serial port may be locked at the factory; unlocking is covered in section 4.1.2 and in the article Unlocking a locked serial port on Paradox alarm control panels. With the Spectra SP / SP+ and Magellan MG / MG+ control panels, the Keybus + TIP/RING connection can also be used instead of the serial port (section 3.3.3); it does not require unlocking, but the communicator's firmware must be at least 1.21 (chapter 9).

I cannot arm from Protegus 2

1. With direct control, Panel settings → Remote Arm/Disarm must be ticked, and the control panel must be set up as described in section 4.1 (Paradox: PC password, firmware V.4+; Texecom: UDL passcode; Caddx, InnerRange, Honeywell: the settings described). Check in the table of section 1.3 whether the control panel can be controlled directly at all.
2. With keyswitch arming (section 3.4), the terminal must be OUT on the IN/OUT page (the GET's default setting), the control panel's zone must be a keyswitch zone, and in Protegus 2 the output must be assigned to the partition, in the same mode as the control panel's (pulsed or two-state; section 5.2).
3. Protegus 2 shows the partition's state from the control panel's arming and disarming events: the control panel must report these (Opening/Closing).

Protegus 2 does not see the device

1. Enable connection must be ticked on the User reporting → PROTEGUS Cloud page (section 6.5).
2. When adding, you must enter the PROTEGUS Cloud access Code set in the device; if you changed the code in TrikdisConfig, change it in the app as well.
3. Enter the IMEI exactly, from the device's label or the sticker on the box (or scan the QR code).
4. There must be a working internet connection on at least one path: the NETWORK LTE LED is green and flashing yellow (SIM card with data service and a correct APN), or the NETWORK LAN LED is green (LAN cable). The DATA LED must go out after an event.

I cannot log in remotely with TrikdisConfig

1. The device must be online (NETWORK LTE green, flashing yellow, or NETWORK LAN green), and the Protegus connection must be enabled (Enable connection).
2. CMS reporting → Settings → IP ping period must not be longer than 5 minutes: the PING keeps up the connection needed for remote access.
3. Check the administrator or installer password.

Can I set up the communicator from the app?

Yes: with firmware 1.08 or newer, most settings are available in the Protegus 2 Settings → Advanced settings menu (section 2.2 and chapter 6). What is only in TrikdisConfig: restoring the factory settings (section 6.9), Preferred operator (section 6.6.2) and manual firmware update (chapter 9); the app shows the Serial bus Event switch, but does not change it. When logged in with the installer code, you can only change the groups the administrator has allowed (section 6.2).

I have forgotten the password

Only restoring the factory settings helps (section 6.9): with the TrikdisConfig Restore button over a USB connection, or with the device's RESET button (held down for 10 seconds). All settings are erased. If the administrator has disabled restoring by the installer, the Restore button cannot be started with the installer password. Restoring cannot be started from the app.

How much data traffic does the device use?

The event messages and the PINGs are very small; the traffic mainly depends on the PING period and on the frequency of the test reports. For an average household system the monthly traffic typically stays below 10 MB. The exact value depends on the settings and on the operator's billing unit, so with a data-limited card it is worth checking the traffic of the first month. As long as the communicator reports over the wired network, the SIM card's data is not used.

11. Safety instructions

• Security equipment may only be installed and maintained by a qualified installer.
• Read the manual before installation; ignoring the instructions can lead to malfunction or failure of the equipment.
• Disconnect the equipment from the power supply before wiring, before every electrical connection and before servicing.
• Modifications, alterations and repairs not authorized by the manufacturer void the warranty.
• Follow local waste disposal regulations: do not throw the unusable device or its parts in household waste. The crossed-out wheeled bin symbol (WEEE) on the device indicates that it must be handed in separately as electronic waste.

See also

• Compatibility finder – which Trikdis communicator and which connection suits your alarm control panel.
• Trikdis communicator + DSC alarm control panel: short installer guide – the steps of the DSC connection in brief.
• Trikdis communicator + Paradox alarm control panel: short installer guide – the steps of the Paradox connection in brief.
• DSC Power Series NEO and Trikdis communicators: compatibility and solutions – why the NEO cannot be connected to the data bus, and what the solution is.
• Unlocking a locked serial port on Paradox alarm control panels – unlocking the serial port of the SP+, MG+ and EVOHD+ control panels.
• Remote arming with a keyswitch from the Protegus 2 app – the details and pitfalls of keyswitch arming.
• APN settings – list of European mobile operators – the operators' APNs, also for IoT / M2M cards.
• Documentation in English: docs.trikdis.com – GET – the Contact ID → SIA code conversion table is also here (appendix). The manuals on docs.trikdis.com are in English.