E16T communicator – installer and user manual

1. Overview

The E16T is Trikdis's universal Ethernet communicator: it connects to the telephone line output (TIP/RING) of the alarm control panel and behaves like a telephone exchange. The panel "dials", sends the Contact ID message with DTMF tones, and the E16T picks up the line, decodes the message and forwards it over the local network and the wired internet connection to the monitoring receiver, as well as to the Protegus cloud and the user's app. This way a panel of any make that has a Contact ID dialer can be used with it – the panel does not need to be replaced, only its dialer has to be set up. The E16T works over wired internet, without a SIM card or subscription.

1.1 What it is for and how it works

• It reports to the monitoring station. It sends the events over an IP connection to a Trikdis software or hardware receiver (TRK protocol; these receivers work with any monitoring software) or to any universal receiver (SIA DC-09 2007/2012, SUR-GARD TL150). By default it checks the connection every 30 seconds (it sends a heartbeat, a PING, to the receiver; the interval can be changed), and if there is a fault it switches to the backup channel.
• It notifies the user. The Protegus 2 app shows what happened with push notifications (with a separate sound alert) and an event list; from the app the user can arm and disarm, and switch the connected devices (lighting, gate, ventilation, heating, irrigation, etc.). The app works with the alarm control panel of any make that the E16T is connected to.
• It works with the monitoring station and the user together or separately: it can be used with Protegus 2 only (without a monitoring station), with a monitoring station only, or with both. If both are set up, the event is sent to the monitoring station first, then to the user.
• It has its own inputs and outputs. Three dual-function I/O terminals can be used as inputs (detector, tamper) or as controllable outputs (keyswitch zone, relay). With an iO-8 expander connected to the RS485 bus, 8 more I/Os can be added to the system.
• No subscription. The E16T uses the site's existing internet connection: no SIM card, mobile subscription or antenna is needed, and the mobile signal strength does not matter either.

The figure below shows how the system is built up: the telephone line output of the alarm control panel connects to the E16T, the E16T reaches the internet through the local router, and from there the monitoring receiver and the Protegus cloud, while the user sees the system in the Protegus 2 app.

1.2 Versions

This manual was written for the current, v2 hardware version of the E16T (TrikdisConfig shows it as E16T_2000), but it can also be used for the earlier E16T: wiring, setup and operation are largely the same. The differences are summarised in the table below; where the text gives the v2 value, take these into account for the earlier version.

You will find the hardware version in the TrikdisConfig status bar (HW) and on the label on the back of the device.

1.3 Main features

Connection to the alarm control panel

• It connects to the panel's telephone line output with 2 wires (TIP, RING) or 4 wires. With 4-wire connection, the connection between the panel and the communicator is supervised: the communicator signals a broken wire.
• The panel sends the events in Contact ID format with DTMF dialing; the E16T forwards the full event information (code, partition, zone or user).

Communication with the monitoring station

• IP connection to Trikdis receivers (IPcom software receiver, RL14, RM14) and universal receivers (SIA DC-09, TL150).
• Primary, backup and parallel channel: it can send to two receivers at the same time, with a separate backup channel for each.
• Encrypted, password-protected communication; event buffer of 60 messages.

User functions

• Protegus 2 mobile and web app: notifications, event list, arming and disarming, switching outputs.
• Multi-level user rights in the app (administrator, installer, user).

Installation and setup

• The settings can be saved to a file and loaded into another communicator.
• Two access levels: administrator and installer – for setting up the device, for the administrator of the monitoring station and for the installer.
• Can be set up and updated remotely with the TrikdisConfig software.

1.4 Parts of the communicator

The E16T has its printed circuit board in a white plastic case; the front cover is removable and the terminal block can be pulled off. The network (RJ45) connector is on the upper edge of the printed circuit board and can be reached through the opening in the case.

• 1 LED indicators (NETWORK, DATA, POWER, TROUBLE)
• 2 Slot to help remove the front cover (on the upper edge of the cover)
• 3 Detachable terminal block
• 4 USB Mini-B socket for programming
• 5 Ethernet connector (RJ45)

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

The terminal labels are also printed on the front cover, so you do not need to remove the cover for wiring.

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 the network connection, DATA the messages waiting to be sent and TROUBLE the fault.

NETWORK – network connection

DATA – data traffic

POWER – supply voltage

TROUBLE – fault

1.7 Technical data

2. Quick setup with TrikdisConfig

All settings of the E16T are made with the TrikdisConfig program, which runs on Windows – over a USB cable or remotely. In this chapter we describe the shortest route: you set up the device on the desk, before wiring, and on site you then only need to wire it. The settings are explained in detail in chapter 6.

2.1 Preparation

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

2. Open the front cover of the E16T and connect it to the computer. Insert a flat-blade screwdriver into the slot on the top edge of the cover and, levering downwards, gently snap off the front cover, then plug in the USB Mini-B cable. The USB provides enough power for programming; no separate power supply is needed.

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

The next two sections describe what needs to be set so that the alarm control panel can be controlled from the Protegus 2 app (2.2), and so that the communicator sends events to the monitoring station (2.3).

2.2 Connection to the Protegus 2 app

If the user wants to see and control the system from the Protegus 2 app, set the following on the User reporting page, on the PROTEGUS Cloud tab.

• 1 Enable connection – tick it: enables the connection to the Protegus cloud.
• 2 Protegus Cloud access code – change the default password 123456. This is what has to be entered in the app when the system is created; it cannot be changed after the system has been created.

Then check the type of the alarm control panel interface on the System settings page.

• 3 Security panel model – leave it at 2. INTERFACE DTMF (the telephone line connection with DTMF dialing).

For the network settings, Use DHCP is ticked by default on the Ethernet settings page: the device gets its IP address from the router automatically, and in most places nothing more needs to be done. If there is no DHCP on the network, or a fixed address has to be used, enter the manual settings here (section 6.5).

If you use the device with Protegus 2 only, without 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

If the device also reports to a monitoring receiver, first enter the object ID on the System settings page.

• 1 Object ID – the object ID received from the monitoring station (4 hexadecimal characters, 0–9, A–F). FFFE and FFFF cannot be used.
• 2 Security panel model – leave it at 2. INTERFACE DTMF.

Then, on the CMS reporting page, set the receiver details in the Primary channel section.

• 3 Communication type – IP (this is the only option on the E16T).
• 4 Protocol – TRK for a Trikdis receiver, DC-09_2007 or DC-09_2012 for a universal receiver, TL150 for a SUR-GARD receiver.
• 5 TRK encryption key – the 6-digit encryption key set in the receiver.
• 6 Domain or IP – the domain name or IP address of the receiver.
• 7 Port – the port number of the receiver.
• 8 TCP or UDP – the transmission protocol; it follows the receiver's setting.
• 9 Primary channel Backup – backup channel in case the primary one fails; fill it in the same way, it is recommended.

If the user also uses the Protegus 2 app, make the settings of section 2.2 as well (User reporting → PROTEGUS Cloud). At the end of the setup, press the Write [F5] button, wait for the confirmation and unplug the USB cable. The device is now ready for wiring.

3. Installation and wiring

3.1 Installation steps

1. Remove the front cover (see section 2.1) and pull off the terminal block.
2. Take the printed circuit board out of the back cover: open the latch in the corner.
3. Fix the back cover with screws in the chosen place.
4. Put the printed circuit board back into the back cover and plug the terminal block back in.
5. Plug the Ethernet cable into the RJ45 socket (section 3.6).
6. Put the front cover back on.

3.2 Location and network

• Put the communicator in a dry, indoor place, preferably near the alarm control panel's enclosure, so that the wiring is short. A metal enclosure does not interfere with it: the E16T has no antenna.
• The Ethernet cable (CAT-5 or better) to the router or switch can be up to 100 m long.
• Keep the communicator and the cables away from the panel's transformer and from mains wiring.

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.

3.3 Connection to the alarm control panel

The E16T has to be connected to the panel's telephone line output (TIP/RING), and it gets its power from the panel's 12 V auxiliary power output (AUX). It can be connected in two ways:

• With 2 wires (TIP, RING): simple, but the communicator does not detect if the wire is broken.
• With 4 wires (TIP, RING, plus T-1 and R-1 on the I/O 1 and I/O 2 terminals): the connection is supervised, the communicator signals a broken wire. For this, switch on the Line supervision option on the System settings page of TrikdisConfig. In this case I/O 1 and I/O 2 cannot be used for anything else.

3.4 Wiring a keyswitch zone

If you want to arm and disarm the panel remotely, from the Protegus 2 app, set one of the communicator's I/O terminals as an output and connect it to a keyswitch zone of the panel. When activated, the output pulls the zone to COM (negative); connect the zone's end-of-line resistor according to the panel's zone type. As the E16T has three I/O terminals, even three partitions can be handled with separate outputs.

The keyswitch zone can be pulse or latching (two-state) – the same mode has to be set in the Protegus 2 app (section 5.2). A separate article covers the details and pitfalls of keyswitch arming: Remote arming with a keyswitch from the Protegus 2 app.

3.5 Wiring the inputs

As inputs, the communicator's I/O terminals can also take additional detectors (e.g. tamper switch, panic button, temperature switch), independently of the alarm control panel. The input has to be connected between the selected I/O and the COM terminal.

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: NC, NO, EOL and DEOL types with a 2.2 kΩ end-of-line resistor, with a tamper loop for the DEOL types.

• T tamper contact (“Tamper”), signals that the detector's housing has been opened

• T tamper contact (“Tamper”), signals that the detector's housing has been opened

3.6 Connecting the Ethernet cable

Plug one end of the Ethernet cable into the RJ45 socket on the E16T's printed circuit board, and the other into a free port of the router or switch. A standard straight-through (patch) cable is needed; the cable enters through the upper opening of the case. After switching on, the green light of the NETWORK LED shows that the network connection has been established.

3.7 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 up to 0.15 A, up to 30 V DC. Switch a larger load or a mains-voltage device through a relay: one end of the relay coil goes to +DC, the other to the I/O terminal. An indicator LED can also be connected directly to the output: from +DC through a 2.2 kΩ series resistor to the LED, and the other leg of the LED to the I/O terminal (on the earlier E16T, to the OUT terminal).

• R relay (“Relay”)

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

3.8 Connecting an iO-8 expander

If more inputs or outputs are needed, up to four iO-8 expanders can be connected to the E16T's RS485 bus; each adds 8 more dual-function I/Os. Connect the A 485 and B 485 terminals to the A and B terminals of the module, and take the module's power from the panel's 12 V. The RS485 bus can be up to 100 m long – this is a theoretical maximum, see the note in section 3.2. The module has to be added on the RS485 modules page of TrikdisConfig (section 6.7). The other members of the iO series (iO, iO-WL, iO-LO, LO-MOD) can also be connected here; W485 and E485 modules do not go with the E16T, since the E16T itself is a wired internet device.

3.9 Switching on 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 starts when the alarm control panel is switched on. On the front cover you should see:

• POWER steady green – the power supply is correct;
• NETWORK steady green – connected to the local network;
• TROUBLE off.

If TROUBLE is flashing, the number of flashes tells you the cause (section 1.6): 1 = no physical connection (cable, port), 2 = no IP address received (DHCP), 3 = DNS error, 6 = it cannot reach the receiver. If none of the LEDs is lit, check the power supply and the wiring.

4. Programming the alarm control panel

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.

4.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 Panels of other makes

In the installer manual of every panel, look for the same five settings: enabling the telephone line communicator, the receiver's telephone number, the dialing mode (DTMF), the communication format (Contact ID) and the object ID. If the panel expects a dial tone before dialing, the E16T provides it; if the call still does not start, switch off dial tone detection in the panel ("dial without dial tone" or a similar option).

5. Remote control with the Protegus 2 app

With the Protegus 2 mobile and web app, the user can see the state of the system remotely, receives notifications about the events, can arm and disarm, and can switch the communicator's outputs.

5.1 Adding the device

Before adding the device, check that:

1. The E16T is connected to the network and can reach the internet: the NETWORK LED is steady green, and the DATA LED goes off after an event or a test report.
2. On the User reporting → PROTEGUS Cloud tab of TrikdisConfig (section 6.4), Enable connection is ticked – i.e. the Protegus cloud is enabled – and the Protegus Cloud access code is set (it cannot be changed after the system has been created).
3. The POWER 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 unique identifier of the device on the E16T is the MAC address: it can be read on the box and on the back of the device, and TrikdisConfig also shows it (MAC / Unique ID).

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. TrikdisConfig – the settings in detail

On the left side of the TrikdisConfig window you see the list of pages (System settings, CMS reporting, User reporting, Ethernet settings, IN/OUT, RS485 modules, Event summary, Firmware), at the top the button bar (Read [F4], Write [F5], Open [F8], Save [F9]), and at the bottom the status bar. This chapter goes through the settings of the E16T page by page.

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

After Read [F4], the program reads and shows the settings stored in the device; the Device field should show the device type (E16T; for v2, E16T_2000). Make the settings according to the page descriptions below.

6.2 System settings

The page consists of two groups: in the General group you set the basic operation of the device, in the Access group the access levels.

• Object ID – the object ID received from the monitoring station (4 hexadecimal characters: 0–9, A–F; FFFE and FFFF cannot be used). Mandatory if the device also reports to a monitoring station.
• Use security panel account ID – when ticked, the communicator does not use its own Object ID but the ID sent by the panel in the Contact ID message. Useful if several partitions report with separate IDs.
• Wait acknowledgment from CMS – when ticked, after each event the communicator waits for the receiver's acknowledgement and only then sends the closing (kiss-off) signal to the panel. If there is no acknowledgement, the panel sends the event again. In a system without a monitoring station, with Protegus 2 only, leave it off (default).
• Security panel model – the type of the telephone line interface; default 2. INTERFACE DTMF. With this you switch the communicator's DTMF telephone line interface on or off.
• Dial tone frequency – the frequency of the dial tone that the E16T gives to the panel (default 425 Hz, the standard dial tone in most European countries).
• Line supervision – supervision of the wire between the panel and the communicator; requires 4-wire connection (section 3.3).
• Time set – the source of the device's clock (default Cloud application, the Protegus cloud).

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.

6.3 CMS reporting

The communicator sends the events to the monitoring station over an IP connection. 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 over if that channel is interrupted. The communication is encrypted and password-protected; for receiving and forwarding to the monitoring software, a Trikdis receiver (IPcom software receiver for Windows or Linux, RL14 hardware IP/SMS receiver, RM14 multi-channel receiver) or a universal receiver that knows the DC-09 / TL150 protocol is needed.

Primary channel

• Communication type – on the E16T only IP can be selected.
• Protocol – TRK (Trikdis receivers), DC-09_2007 or DC-09_2012 (universal receivers), TL150 (SUR-GARD).
• TRK encryption key – 6-digit encryption key; it must be the same in the communicator and in the receiver.
• Domain or IP, Port – the address of the receiver (domain name or IP address) and its network port number.
• TCP or UDP – the transmission protocol: the events are sent with this (according to the receiver's setting).

Primary channel Backup – backup channel. It takes over communication if the primary channel is not working; its settings are the same as above. It is worth setting it up on a wired device too – for example with the receiver's second address or port – because the backup channel also bridges a fault on the receiver side.

Parallel channel. Alongside the primary channel, it sends to a second receiver at the same time (for example to the local and the central monitoring station). It has its own backup channel.

On the Settings tab you set the timings and the receiver and line number; the DC-09 group is only needed if you send with the DC-09 protocol (it is not yet visible in the 2022 screenshot).

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

6.4 User reporting

On the PROTEGUS Cloud tab you enable the Protegus service. The E16T has no SMS notification or SMS control, so this page has only this one tab.

• Enable connection – enables the connection to the Protegus cloud and remote access with TrikdisConfig.
• Protegus Cloud access code – 6-digit code for the Protegus connection (default 123456). If you have changed it, this is what has to be entered when the system is added in Protegus 2. It can only be set before the system is created in Protegus 2; it cannot be changed afterwards.

6.5 Ethernet settings

Here you set how the E16T connects to the local network.

• Use DHCP – when ticked, the device automatically gets its IP address, subnet mask and gateway from the router's DHCP server. This is the factory setting, and in most places nothing more needs to be done. If there is no DHCP on the network, if automatic login to the network fails, or if the network administrator asks for a static address, untick it and fill in the fields below and the name servers manually:
• Static IP – the device's static IP address on the local network (an address not used by any other device and outside the DHCP range).
• Subnet mask – the subnet mask of the network.
• Default gateway – the default gateway, usually the router's address. With a wrong gateway the device reaches the local network but not the internet.
• DNS 1, DNS 2 – name servers; through these the device finds the Protegus cloud and a receiver specified by domain name. Google's public DNS is set by default; if the network only allows its own name server towards the outside, enter the address of the local DNS here. 3 flashes of the TROUBLE LED indicate a DNS error.

The device's unique identifier, the MAC address (Internal MAC in the software), is shown in the newer TrikdisConfig window not on this page but at the bottom of the window, in the MAC / Unique ID field of the status bar.

On the earlier E16T, the MAC address is shown in the Internal MAC field of the Ethernet settings group on the System settings page (note in section 6.2).

6.6 IN/OUT

Here you set the role of the communicator's three dual-function I/O terminals: Disabled (not used), IN (input) or OUT (output). For an input, the type also has to be set (NC, NO, NO/EOL, NC/EOL, NO/DEOL, NC/DEOL).

When a detector connected to an input is violated, the communicator sends its own event (INx_ALARM, Contact ID 130), and when the tamper loop is violated, a tamper event (INx_TAMPER, 144), to the monitoring station and to Protegus 2; the events of every terminal set as an input appear in the table. The columns of the table:

• Enable – enables sending the message.
• E/R – the type of the event: Event (alarm) or Restore.
• CID – the Contact ID code.
• Part. – the partition number in the message.
• Zone – the zone number in the message.

6.7 RS485 modules

The iO-8 and other iO-series expanders connected to the RS485 bus have to be added on the Modules list tab.

• Module Type – the type of the connected module, from the list (Expander iO-8, IO, IO-WL, IO-LO, LO-MOD).
• Serial No – the 6-digit serial number of the module (on the module and its box, SN).

After selecting the module and entering the serial number, press the Write [F5] button, unplug the USB cable and wait a minute while the communicator registers the module. Then plug the cable back in, read the device (Read [F4]), and the module's own numbered tab appears on the RS485 modules page.

iO-8 expander – 8 dual-function I/Os; up to 4 modules can be connected to the communicator.

• Input Count – how many terminals should be inputs; the rest will be outputs. The input type (Input type: NO or NC) can be set in the table. The role of the outputs (arming / disarming or switching a device) is set in the Protegus 2 app.
• In the table you can assign Contact ID codes to the bus fault (BUS_FAULT, Contact ID 333) and to the violation and restore events of the inputs (INPUTx, 130) (Enable, E/R, CID, Part., Zone). By default, module 1 reports with partition 91 and module 4 with partition 94. By ticking Show Object ID, an object ID different from the communicator's can also be set for the inputs.

6.8 Event summary

On this page you can enable or disable the device's own internal messages and change their Contact ID code, partition and zone number. A message disabled here is not sent by the device on any channel. By default the messages are sent with partition 99 and zone 999.

• Enable – enables sending the message to the monitoring station and to Protegus 2.
• E/R – the message type: Event or Restore – the row stands for the occurrence of the event or its restore.
• Part. – the partition (area) number the device sends with the internal event and its restore.
• Zone – the zone number the device sends with the internal event and its restore.
• The CID code, the partition and the zone can be changed for any event; where there is a restore (Restore), its code can be set separately.

On the earlier E16T, the inputs are also set on this page (note in section 6.6).

6.9 Restoring the factory settings

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]).

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.

Enabling the Protegus service is described in section 6.4, downloading TrikdisConfig in section 2.1.

8. Testing the communicator

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.

10. Troubleshooting and frequently asked questions

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

The NETWORK LED is off – no network

1. Look at the flashes of the TROUBLE LED: 1 = no physical connection, 2 = no IP address received (DHCP), 3 = DNS error.
2. With 1 flash, check the cable and the connectors (whether the RJ45 is plugged in until it clicks), the port of the router or switch (whether it is live, whether it is disabled), and try another cable or port.
3. With 2 flashes, there is no DHCP server on the network or it does not respond: switch it on in the router, or give the device a fixed IP address, mask and gateway on the Ethernet settings page (section 6.5).
4. With 3 flashes, name resolution is not working: check the DNS 1 / DNS 2 fields (by default Google's public DNS), and whether the network allows outgoing DNS traffic.

There is a network, but the monitoring station does not receive 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. 6 flashes of the TROUBLE LED indicate that there is no connection to the receiver: check the receiver's address, port, the TCP/UDP setting and the encryption key (CMS reporting).
2. If the receiver is entered with a domain name, check the DNS setting (Ethernet settings).
3. With a fixed IP address, check the gateway (Default gateway): with a wrong gateway the device reaches the local network, but not the internet.
4. On a company or filtered network, the firewall may block the outgoing connection to the receiver's port – check with the network administrator (section 3.2).

The panel does not send the events to the communicator

1. The panel's dialer must be switched on, in DTMF mode, with Contact ID format and a telephone number entered (chapter 4).
2. Check the TIP/RING wiring; 7 flashes of the TROUBLE LED indicate a missing connection to the panel (with 4-wire, supervised connection).
3. If the panel expects a dial tone and does not start the call, switch off dial tone detection in it.
4. If the panel signals a "communication fault" although the event has arrived, check the Wait acknowledgment from CMS setting (section 6.2).

Protegus 2 does not see the device

1. Enable connection must be ticked on the User reporting → PROTEGUS Cloud tab.
2. When creating the system, the Protegus Cloud access code set in the device has to be entered; it cannot be changed in the device after the system has been created.
3. Enter the MAC address exactly, from the box or the back of the device – or scan the QR code on the label with the app, so it cannot be mistyped.
4. The internet connection must be working: the NETWORK LED is green, and the DATA LED goes off after an event. Reaching the Protegus cloud also requires a working DNS (Ethernet settings).

I cannot log in remotely with TrikdisConfig

1. The device must be online (NETWORK LED green, the DATA LED goes off after an event), and the Protegus connection must be enabled.
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.

I have forgotten the password

Only restoring the factory settings helps (section 6.9); this requires a USB connection, and all settings are deleted. If the administrator has disabled reset by the installer, the reset cannot be started without the administrator password either.

Do I need a fixed IP address or port forwarding on the router?

No. The E16T itself initiates the outgoing connection to the receiver and to the Protegus cloud, so neither a fixed public IP address, nor dynamic DNS, nor port forwarding is needed. On the local network, the address received via DHCP is also fine; only give it a fixed local address if there is no DHCP on the network or the network administrator asks for it (section 6.5).

Does it work over Wi-Fi?

No: the E16T only supports a wired (RJ45) network connection. If there is no network cable near the panel, a Wi-Fi bridge to the router can be set up, or choose the G16T cellular communicator.

What happens during a power failure?

The communicator is powered by the panel's battery, but if the router and the modem are left without power, there is no internet, and the events wait in the buffer (the DATA LED is lit). The device sends them once the internet is back. If the outage is not acceptable, an uninterruptible power supply for the network devices or a cellular communicator is the solution (section 3.2).

11. Safety instructions

• Security equipment may only be installed and maintained by a qualified installer.
• Read the manual carefully before installation; ignoring the instructions can lead to malfunction or failure.
• Disconnect the equipment from the power supply before wiring, before every electrical connection and before servicing.
• Faults resulting from improper installation or use, as well as modifications and repairs not authorized by the manufacturer, void the warranty.
• Follow local waste disposal regulations: do not throw the faulty device or its parts in household waste.

See also

• Remote arming with a keyswitch from the Protegus 2 app – the details and pitfalls of keyswitch arming.
• Documentation in English: docs.trikdis.com.