Ethernet communicator E16¶

1. Description¶

“Ethernet” communicator E16 directly connects to supported DSC, Paradox, UTC Interlogix (CADDX), Innerrange, Texecom, Honeywell, Crow and Pyronix alarm panels.

Communicator transmits full event information to the Central Monitoring Station.

Communicator also works with Protegus2 application. With Protegus2 users can control their alarm system remotely and get notifications about security system events. Protegus2 app is compatible with all security alarm panels from various manufacturers that are supported by the E16 communicator. Communicator can transmit event notifications to the Central Monitoring Station and work with Protegus2 simultaneously.

For panels from other manufacturers use the E16T communicator.

1.1 Features¶

Sends events to monitoring station receiver:

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

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

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

• Connection supervision by polling to IP receiver every 30 seconds (or by user defined period).

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

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

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

Works with Protegus2 app:

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

• Remote system Arm/Disarm.

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

• Remote temperature monitoring (with iO or iO-WL expanders).

• Different user rights for administrator and installer.

Notifies users:

• Users can be notified about events with Protegus2 app.

Controllable outputs and inputs:

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

• Outputs controlled by the Protegus2 app.

• Add additional inputs and controllable outputs with wired and wireless iO expanders.

Quick setup:

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

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

• Remote configuration and firmware updates.

1.2 List of compatible control panels¶

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

*Connect control panels from other manufacturers to the E16T communicator.

1.3 Specifications¶

1.4 Communicator elements¶

1. Light indicators.

2. Frontal case opening slot.

3. Terminal for external connections.

4. USB Mini-B port for communicator programming.

5. Ethernet connection RJ45 socket.

1.5 Purpose of terminals¶

1.6 LED indication of operation¶

1.7 Structural schematic with E16 usage¶

2. Quick configuration with TrikdisConfig software¶

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

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

   

3. Using a USB Mini-B cable connect the E16 to the computer.

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

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

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

2.1 Settings for connection with Protegus2 app¶

In “System settings” window:

1. Select Security panel model that will be connected to the communicator.

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

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

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

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

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

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

2.2 Settings for connection with Central Monitoring Station¶

In “System settings” window:

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

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

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

3. Communication type - select the IP connection method.

4. Protocol - select the protocol type for event messages: TRK (to TRIKDIS receivers); DC-09_2007 or DC-09_2012 (to universal receivers); TL150 (to SUR-GARD receivers).

5. TRK encryption key - enter the encryption key that is set in the receiver.

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

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

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

7. (Recommended) Configure Primary channel Backup settings.

8. (Recommended) Configure Parallel Channel and its Parallel Channel Backup settings.

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

3. Installation and wiring¶

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

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

3.2 Schematic for connecting to panel keyswitch zone¶

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

3.3 Schematics for input connection¶

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

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

3.4 Connect LAN cable¶

3.5 Schematics for wiring a relay¶

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

3.6 Schematics for connecting iO series expansion modules¶

If more inputs or outputs need to be connected to the communicator, or if you want to connect a temperature sensor, connect the TRIKDIS iO series wired or wireless output expander. Configuration of expander modules connected to the E16 is described in chapter 6.6 ““RS485 modules” window”.

3.7 Turn on the communicator¶

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

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

• “NETWORK” LED illuminates green, when the communicator is connected to the network.

4. Programming the control panel¶

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

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

4.1 DSC¶

DSC panels do not need to be programmed.

4.2 PARADOX¶

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

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

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

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

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

4.3 TEXECOM¶

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

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

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

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

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

2. Press the [9] key immediately afterwards.

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

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

4.4 UTC INTERLOGIX (CADDX)¶

Security control panel version must be V2 or higher With the keyboard connected to the security control panel:

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

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

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

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

4.5 INNERRANGE¶

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

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

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

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

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

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

4. Save settings and exit the application.

Innerrange Integriti security control panel version must be 19.1.0.36608 or higher, the professional software version 19.1.0.15396 or higher.

Specify the Trikdis communication protocol in the control panel configuration program. Contact ID data format. The port (TTL Port-0) of the security panel, to which the E16 communicator is connected, has the settings 19200, 8, N, 1. Save the settings and exit the program.

4.6 Honeywell Ademco Vista¶

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

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

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

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

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

Crow

There is no need to program Crow Runner 4/8 and Runner 8/16 panels.

5. Remote control¶

5.1 Adding the security system to Protegus2 app¶

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

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

   

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

3. Click “Add new system” and enter the E16’s “MAC” number. This number can be found on the device and the packaging sticker. Click “Next”.

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

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

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

1. Click „Continue“.

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

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

4. Click „Save“.

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

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

5.3 Arming/disarming the alarm system with Protegus2¶

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

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

6. TrikdisConfig window description¶

6.1 TrikdisConfig status bar description¶

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

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

6.2 “System settings” window¶

“General” settings group

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

• Select the Security Panel model that will be connected to the communicator.

• Remote Arm/Disarm - when the checkbox is selected, the E16 will directly control the control panel remotely. This setting will be visible only for directly controlled panels. For direct control of the control panels you need to change the panel settings, as described in section 4 “Programming the control panel”.

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

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

“Access” settings group

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

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

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

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

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

6.3 “CMS reporting” window¶

“CMS settings” tab

The communicator sends events to the monitoring station via a wired internet (IP) connection.

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

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

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

“Primary channel” settings group

• Communication type - select which method for connecting to the monitoring station receiver will be used (IP).

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

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

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

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

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

“Primary channel Backup” settings group

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

“Parallel channel” settings group

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

*“Settings” tab* “Settings” settings group

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

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

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

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

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

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

“DC-09 settings” settings group

The settings are displayed when the DC-09_2007 or DC-09_2012 protocol is set in the communication channel Protocol field for sending events to universal receivers.

• Object ID in DC-09 - enter the object number. The object number entered in this field will be used if DC-09 encoding is selected. A hexadecimal number from 3 to 16 characters can be entered. This Number is provided by the CMS (central monitoring station).

• DC-09-line No. - enter line number of the receiver.

• DC-09 receiver No. - enter the receiver number.

6.4 “User reporting” window¶

“PROTEGUS Cloud” tab

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

“Protegus Cloud” settings group

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

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

6.5 “Ethernet settings” window¶

“Ethernet settings” settings group

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

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

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

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

• DNS1, DNS2 - (Domain Name System) identifies the server that specifies the IP address of the domain. Used when domain is set in the communication channel Domain or IP field (not IP address). Google DNS server is set by default.

6.6 “IN/OUT” windows¶

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

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

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

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

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

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

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

6.7 “RS485 modules” window¶

“Modules list” tab

iO series expanders can be connected to the communicator to add additional inputs, outputs and serial buses for temperature sensors. Connected expanders must be added to the Modules list table.

• Module type – select the module that is connected to the communicator via RS485 from the list.

• Serial No – enter the module serial number (6 digits), which is indicated on stickers on the module’s case and packaging.

Go to RS485 modules → Module.

“Module” tabs

After adding the expander to the communicator as described above, in the RS485 modules window a new tab will appear with this module’s settings. The tab will be given a number. Bellow we describe the settings for iO-8 and iO series expanders.

iO-8 expander settings window

Expander iO-8 has 8 universal (input/output) terminal contacts. Up to four iO-8 expanders can be connected.

• Input Count – select what number of terminal contacts should be set to input (IN) mode. The rest of the terminal contacts will become outputs (OUT).

Settings for controllable outputs are set directly in Protegus2 app. There you can assign an output for arming/disarming the alarm system or for remote control of devices.

In the table inputs can be assigned Contact ID event and restore codes. After input is triggered, the communicator will send an event with set event code to monitoring station receiver, Protegus2 app.

Contact ID event code:

• Enable – allow message transmission, when the input is triggered.

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

• CID – assign a Contact ID event code to the input.

• Part. – assign the partition (area) to the input. It is set automatically: if the module no. is 1, then the area is 91; if the module no. is 4, then the area is 94.

• Zone – set the zone number for the input.

*Contact ID restore code*:

• Enable – allow message transmission when the input is restored.

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

• CID – assign the Contact ID restore code to the input.

• Part. – assign the partition (area) to the input. It is set automatically: if the module no. is 1, then the area is 91; if the module no. is 4, then the area is 94.

• Zone – set the zone number for the input.

• Input type – select the type of the input (NO or NC).

iO expander settings window

Expander iO has: terminals for 1 input, 1 output (relay contacts) and 1-Wire serial bus for connecting temperature sensors.

Relay output can be controlled according to logical (AND, OR, XOR) conditions.

• Input IN1 type – set the input type (NO or NC).

• Max ^◦C(T1) – when the temperature is higher than this setting, an event message will be generated. For an event message to be generated, it must be enabled in the table.

• Min ^◦C(T2) – when the temperature is lower than this setting, an event message will be generated. For an event message to be generated, it must be enabled in the table.

• Relay control – set logical (AND, OR, XOR) conditions, upon which the relay output will be controlled.

In the table inputs can be assigned Contact ID event and restore codes. After an input is triggered, the communicator will send an event with the set event code to the monitoring station receiver and to Protegus2 app. Set as described in the previous page about iO-8 expander settings window.

6.8 “Event summary” window¶

This window allows you to turn on, off, and modify internal messages sent by your device. Disabling an internal message in this window will prevent it from being sent regardless of other settings.

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

• POWER – message about low power supply voltage.

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

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

• START – message about E16 connecting to the network.

• TEST – periodic test message.

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

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

6.9 Restoring factory settings¶

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

7. Remote configuration¶

1. Start the configuration program TrikdisConfig.

2. In the Remote access section enter the communicator’s MAC number. This number can be found on the device and the packaging sticker.

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

4. Press Configure.

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

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

8. Test communicator performance¶

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

1. Generate an event:

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

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

1. Make sure that the event arrives to the CMS (central monitoring station) and/or is received in the Protegus2 application.

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

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

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

9. Firmware update¶

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

1. Run TrikdisConfig.

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

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

3. Select the menu branch Firmware.

4. Press Open firmware and select the required firmware file. If you do not have the file, the newest firmware file can be downloaded by registered users from www.trikdis.com , under the download section of the E16 communicator.

5. Press Update [F12].

6. Wait for the update to complete.

10. „Ethernet“ communicator E16¶

11. Safety requirements¶

The communicator should be installed and maintained by qualified personnel.

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

Disconnect the power supply before making any electrical connections.

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

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

12. Annex¶

The communicator can work with a SUR-GARD receiver. The communicator converts Contact ID codes received from the alarm control panel into SIA codes.

Contact ID to SIA code conversion table