FireCom fire communicator – installation and programming manual

1. Overview

The Trikdis FireCom is an EN 54 certified fire communicator with Ethernet and 4G mobile network (dual SIM) connections.

The FireCom forwards the fire alarm control panel's messages over the local network (LAN) and/or the mobile network to the monitoring station's receiver. How it works: when one of the communicator's inputs (zones) is violated, the FireCom sends an event message over mobile internet and/or the local network to the monitoring station's receiver or to the Protegus 2 app; it can also send SMS messages and make phone calls. The communicator is available with a 4G modem. You make the settings with the TrikdisConfig software, over a USB cable or remotely.

1.1 What it is for and how it works

Connection to the fire alarm control panel

• Connected to the panel's outputs: the panel's status outputs (alarm, fault, etc.) are connected to the FireCom's inputs (section 3.4).
• On the RS485 2 bus: to fire alarm control panels using the ESPA 4.4.4 protocol, and to NSC Solution, INIM Smartline, C-TEC Cast ZFP and Polon-Alfa 3000 fire alarm control panels (sections 3.5–3.9); the Polon-Alfa 3000 can also be connected over the local network (LAN).
• In line with EN 54, two relay outputs signal to the control panel a fault in the connection to the monitoring station and the successful delivery of a message (section 3.12).

Messages to the monitoring station

• It sends the events through the built-in LAN module or the 4G mobile modem.
• It sends the events over the available communication channels, in the order you set.
• Any monitoring station can receive its messages if it has a Trikdis software or IP receiver, or an IP receiver from another manufacturer that supports the SIA DC-09 IP protocol.
• Reporting to the monitoring station can be given priority: the messages go to the monitoring station first, and only after that to Protegus 2.
• It can also send events to the receivers of two different monitoring companies.
• It sends the event messages with Contact ID or SIA codes.

Messages to the users

• It calls the selected phone numbers (up to 8 users).
• It sends SMS messages about the events.
• It sends push notifications and event notifications with special sounds to the Protegus 2 app.
• Remote temperature monitoring.

Remote control of the outputs

• from the Protegus 2 app;
• by calling the device's phone number;
• by SMS message.

Setup and installation

• Setup over a USB cable or remotely, with the TrikdisConfig software.
• Remote firmware update.
• Two access levels (account types) for the settings: installer and administrator.

Inputs and outputs

• 3 relay outputs (1 A, 30 V DC).
• The FLOOP input is for connecting two-wire fire detectors.
• 10 I/O terminals, each of which can be set as an input (IN) or an output (OUT). Types selectable as an input: NC, NO, EOL, EOL_T, ATZ, ATZ_T. Resistors of different values can be used in the EOL and ATZ circuits.
• With iO expansion modules the number of inputs (IN) can be extended to 32 and the number of outputs (OUT) to 16.
• The iO series expansion modules connect to the RS485 bus (A1, B1).
• The fire alarm control panel connects to the RS485 2 bus (A2, B2).

1.2 Technical specifications

The “up to … m” distances are theoretical maximums achievable under ideal conditions. In practice, the quality and routing of the cable, sources of interference and, for radio links, walls and terrain give a considerably shorter range. Plan with a margin, and on long runs check the connection during commissioning.

Trikdis FireCom Ethernet + 4G fire communicator

1.3 Parts of the communicator

The numbers in the figure mark the parts of the FireCom's printed circuit board. The board is mounted together with the power supply in a metal enclosure (chapter 3).

• 1 connection and operation LEDs
• 2 push button – not used
• 3 backup power supply terminal block
• 4 main power supply terminal block
• 5 RESET button
• 6 external terminal block
• 7 1-Wire terminal block
• 8 LAN connector
• 9 relay output terminal block
• 10 SIM card holders
• 11 mobile network (GSM) antenna connector
• 12 USB Type-C connector

1.4 Terminals

The terminal names are printed on the circuit board, next to the terminal blocks.

1.5 LEDs

There are five LEDs on the circuit board (SIM, ETH, DAT, STA, FPS) and three on the front of the enclosure (POWER, DATA, TROUBLE). The table describes the DAT / DATA, STA / TROUBLE and FPS / POWER pairs together; where an indication applies to only one of them, its name is given in brackets.

Section 3.14 describes the correct indication after power-up and how to evaluate the signal strength.

1.6 Tools and accessories needed for installation

Before you start the installation, check that you have everything at hand:

1. a USB Type-C cable for the setup;
2. a cable with at least 4 cores for connecting the communicator to the fire alarm control panel;
3. a 2.5 mm flat-blade screwdriver;
4. an external mobile network antenna if the signal at the site is weak;
5. an activated nano SIM card (the PIN request can be switched off);
6. the manual of the fire alarm control panel you are connecting the communicator to.

The listed accessories must be purchased separately – order them from your dealer. If the signal at the site is weak, use an external antenna on a cable that can be placed away from the enclosure:

Trikdis ME301M magnetic antenna with 2,5m wire Trikdis ANT04 GSM stick-on antenna with 2,5m wire

2. Power supply

2.1 Main power supply

The communicator must be powered from a direct current (DC) power source. For an uninterruptible power supply, a backup power source – a 12 V battery – must be connected to the system. A 12 V, 4 Ah or 7 Ah lead-acid battery is suitable as the backup power source (section 1.2); the note in section 3.1 covers how to choose it.

12 V 7 Ah gel battery for alarm control panel

2.2 Backup power supply

If there is a problem with the main power supply, the communicator sends a DC Fault event message and automatically switches over to the 12 V backup battery. If the battery voltage drops to 11.5 V, a Low Battery event message is generated. If the voltage falls below 9.5 V, the battery is disconnected. When the DC supply voltage returns, a DC Restore message is generated and battery charging starts automatically. When the battery voltage reaches 12.6 V, a Battery Restore event message is generated.

2.3 Package contents

3. Installation and wiring

The communicator's printed circuit board is mounted in an enclosure in which the DC power supply with the 3.15 A fuse is already installed, and which also has room for the backup battery. This chapter describes the wiring order; the wiring of detectors, smoke detectors and fire alarm control panels (the panel's outputs, and on the RS485 2 bus the ESPA 4.4.4 protocol, NSC Solution, INIM Smartline, C-TEC Cast ZFP and Polon-Alfa 3000 panels); temperature sensors; the relay and the LED indicator; the panel's inputs; the iO expansion modules; and finally powering up the communicator.

Dimensions of the FireCom board

The figure shows the dimensions of the board and the mounting holes (in millimetres), as well as the position of the holes.

3.1 Wiring order

The numbers in the figure are the numbers of the steps below.

1. If you use a SIM card, insert the activated SIM card into the SIM holder.
2. If you use a local network (LAN), connect the LAN cable.
3. Connect the fire detectors, the indicators and the controlled devices according to the wiring diagrams given here and the own wiring diagram of each device to be connected.
4. Connect the mains (AC) power wires to the terminals.
5. Place the backup battery in the enclosure. Connect the battery terminals to the communicator's BAT+ / BAT− terminals.

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.2 Connecting detectors

On the communicator board, 10 terminals (IO1–IO10, inputs) are used for connecting detector circuits. The number of inputs can be increased to 32 with input expanders (iO-8, iO-MO, iO-LORA, iO8-LORA). Any terminal can be set as an input and given zone properties: the circuit type (NO, NC, EOL, EOL_T, ATZ, ATZ_T) and the sensitivity to transient circuit events (section 6.6, Zones page).

The wiring diagrams of the detectors follow. The selectable values of the resistors (RT – tamper, R1 – detector 1, R2 – detector 2):

You enter the values used in the EOL Type field of the System Options page (section 6.2).

• T tamper contact ("Tamper"), signals that the detector cover has been opened

• 1 circuit of detector 1 ("Detector terminal 1")
• 2 circuit of detector 2 ("Detector terminal 2")

• T tamper contact ("Tamper"), signals that the detector cover has been opened
• 1 circuit of detector 1 ("Detector terminal 1")
• 2 circuit of detector 2 ("Detector terminal 2")

3.3 Connecting smoke detectors

Two-wire smoke detectors on the FLOOP terminal

If you use this wiring, on the Zones page you must select the FC Fire sensor (FLOOP input) input as the zone's input (Input) (section 6.6). The alarm current of the fire detector must be greater than 10 mA. Up to 8 fire detectors can be connected to the FLOOP terminal.

• EOL 2.2 kΩ end-of-line resistor ("End of line resistor")

Two-wire smoke detectors with an SM1 relay module

If you connect the smoke detector circuit to a selected input, the input (IOx) must be enabled and the circuit type must be set (NO, NC, EOL, EOL_T, ATZ, ATZ_T; section 6.6, Zones page). If you connect the power circuit of the smoke detectors to the PGM output (IO10), the Fire Sensor Reset function must be assigned to the output (section 6.7, PGM page).

• R K1 relay ("Relay") – its role is in the note above
• EOL the R1 end-of-line resistor ("End of line resistor")

Or:

• R K1 relay ("Relay") – its role is in the note above
• EOL the R1 end-of-line resistor ("End of line resistor")

Four-wire smoke detectors

If you connect the smoke detector circuit to a selected input, the input (IOx) must be enabled and the circuit type must be set (NO, NC, EOL, EOL_T, ATZ, ATZ_T; section 6.6, Zones page). If you connect the power circuit of the four-wire smoke detectors to the PGM output (IO10), the Fire Sensor Reset function must be assigned to the output (section 6.7, PGM page).

• R K1 relay ("Relay") – its role is in the note above
• EOL the R1 end-of-line resistor ("End of line resistor")

3.4 Connecting to the outputs of the fire alarm control panel

If you want to monitor the state of the fire alarm control panel, connect the appropriate outputs of the panel to the FireCom's inputs. The panel's outputs (PGM1, PGM2, PGM3) must be set as status outputs (alarm, fault, etc.) in the panel. The drawing comes in two versions: when the FireCom is powered from the panel's 24 V (without the built-in power supply), and when it runs from its own built-in power supply.

3.5 Fire alarm control panel with the ESPA 4.4.4 protocol

Connect the fire alarm control panel using the ESPA 4.4.4 protocol to the FireCom on the RS485 2 bus (A2, B2), according to the drawings below.

Setting up the FireCom in TrikdisConfig when it is connected to a fire alarm control panel with the ESPA 4.4.4 protocol:

1. In the RS485 2 interface group of the Modules page, select the ESPA 4.4.4 protocol.
2. Select the connection type (Connection).
3. The data transmission settings of the FireCom and the fire alarm control panel must be identical.

• 1 Interface type – selecting ESPA 4.4.4
• 2 Connection – the connection type (RS485 in the picture)
• 3 data transmission settings (in the picture Baudrate 9600, 8 data bits, None parity, 1 stop bit, Delay 0 ms)

4. On the Users & Reporting page, enter the phone numbers and e-mail addresses of the users who receive messages from the FireCom (section 6.4).
5. If you want the user to receive a message (or a call) about the events, tick the SMS (or Call) checkbox on the SMS & Call reporting tab of the System events page.

• 5 the SMS and Call checkboxes

6. If the messages must also reach the monitoring station's receiver, set up the communication channel on the Reporting to CMS page (sections 4.2 and 6.3). The event messages are sent with the SIA DC-09 protocol.

Test the system: trigger a fire alarm and check that the FireCom's messages arrive at the monitoring station and in Protegus 2.

3.6 NSC Solution fire alarm control panel

Connect the NSC Solution fire alarm control panel to the FireCom on the RS485 2 bus, according to the drawings below.

Setting up the FireCom in TrikdisConfig when it is connected to an NSC Solution fire alarm control panel:

1. In the RS485 2 interface group of the Modules page, select the NSC solution panel.
2. The NSC slave address (the communicator's slave address) must not be the same as the address of the modules connected to the fire alarm control panel.

• 1 Interface type – selecting NSC solution
• 2 NSC slave address – 10 in the picture

3. On the Users & Reporting page, enter the phone numbers and e-mail addresses of the users who receive messages from the FireCom (section 6.4).
4. The users receive SMS messages and calls about the ticked events (Users & Reporting page, SMS for Panel events tab). In the CID column you can add further Contact ID event codes; next to the new codes you must also enter the SMS text. If you want the user to receive a message (or a call) about the events, tick the SMS (or Call) checkbox.

• 4 the SMS and Call columns of user 1

5. If the messages must also reach the monitoring station's receiver, set up the communication channel on the Reporting to CMS page (sections 4.2 and 6.3).

After setting up the FireCom, switch on the power of the fire alarm control panel and wait until the panel's software has loaded. Then the modules connected to the RS485 bus must be searched for (scanned) on the panel. On the panel press: PROG. > INSTALLER > (enter the installer code) 00000 OK > (select) SETTINGS > ENTER > (select) SCAN RS485 > ENTER. Wait until the search has finished, then press the CANCEL button twice to return to the main screen.

Test the system: trigger a fire alarm and check that the FireCom's messages arrive at the monitoring station and in Protegus 2.

3.7 INIM Smartline fire alarm control panel

Connect the INIM Smartline fire alarm control panel to the FireCom on the RS485 2 bus, according to the drawings below.

If you connect the INIM Smartline panel to the FireCom on the RS485 bus, the panel must be set to slave mode – you can do this in the panel's SmartLeague software.

Setting up the FireCom in TrikdisConfig when it is connected to an INIM Smartline fire alarm control panel:

1. In the RS485 2 interface group of the Modules page, select the INIM smartline panel.

• 1 Interface type – selecting INIM smartline

2. On the Users & Reporting page, enter the phone numbers and e-mail addresses of the users who receive messages from the FireCom (section 6.4).
3. The users receive SMS messages and calls about the ticked events (Users & Reporting page, SMS for Panel events tab; the picture of the tab is in section 3.6). In the CID column you can add further Contact ID event codes; next to the new codes you must also enter the SMS text. If you want the user to receive a message (or a call) about the events, tick the SMS (or Call) checkbox.
4. If the messages must also reach the monitoring station's receiver, set up the communication channel on the Reporting to CMS page (sections 4.2 and 6.3).

Test the system: trigger a fire alarm and check that the FireCom's messages arrive at the monitoring station and in Protegus 2.

3.8 C-TEC Cast ZFP fire alarm control panel

Connect the C-TEC Cast ZFP fire alarm control panel to the FireCom on the RS485 2 bus, according to the drawings below.

Setting up the FireCom in TrikdisConfig when it is connected to a C-TEC Cast ZFP fire alarm control panel:

1. In the RS485 2 interface group of the Modules page, select the C-TEC Cast ZFP panel.

• 1 Interface type – selecting C-TEC Cast ZFP

2. On the Users & Reporting page, enter the phone numbers and e-mail addresses of the users who receive messages from the FireCom (section 6.4).
3. The users receive SMS messages and calls about the ticked events (Users & Reporting page, SMS for Panel events tab; the picture of the tab is in section 3.6). In the CID column you can add further Contact ID event codes; next to the new codes you must also enter the SMS text. If you want the user to receive a message (or a call) about the events, tick the SMS (or Call) checkbox.
4. If the messages must also reach the monitoring station's receiver, set up the communication channel on the Reporting to CMS page (sections 4.2 and 6.3).

Setting up the panel with the ZFPtools software

Install the ZFPtools software on the computer and start it. Switch on the power of the fire alarm control panel and wait until the panel's software has loaded. Connect the panel to the computer with a USB 2.0 A-B cable. The marker numbers in the pictures are the numbers of the steps.

1. Open the Node View tab.

• 1 Node View

2. Download the panel's settings to the computer.

• 2 Retrieve All Data – downloading the panel's settings

3. Enter the code (4444 by default).
4. Click the OK button.

• 3 the code fields
• 4 OK (green tick)

5. Select the BMS Interface item.
6. Click a free icon.

• 5 BMS Interface in the Device Palette list
• 6 a free slot in the Devices area (number 16 in the picture)

7. Click the Edit Devices button.

• 7 Edit Devices

8. On the Device tab, enter the name of the system.

• 8 Name – the name of the system (FIRECOM in the picture)

9. On the Properties tab, enter the name of the system.
10. Specify the ABUS RS485 bus to which the FireCom is connected.
11. Set up the messages.
12. Write the settings to the panel.

• 9 Name – the name of the system (FIRECOM)
• 10 Connection – ABUS RS485
• 11 the messages: Zone Disablements – Reports Zone; Input Group Disablements, Output Group Disablements, Group Actions – Reports Group
• 12 Send All Data – writing the settings to the panel

13. Enter the code (4444 by default).
14. Click the OK button (the Panel Log In window is the same as in steps 3–4).

The panel is programmed. Unplug the USB 2.0 A-B cable from the panel.

Test the system: trigger a fire alarm and check that the FireCom's messages arrive at the monitoring station and in Protegus 2.

3.9 Polon-Alfa 3000 fire alarm control panel

Connection on the RS485 bus

The FireCom connects to the Polon-Alfa 3000 panel on the RS485 bus.

Setting up the FireCom in TrikdisConfig:

1. In the RS485 2 interface group of the Modules page, select the Polon-Alfa 3000 panel.
2. As the connection type (Connection), select RS485.

• 1 Interface type – selecting Polon-Alfa 3000
• 2 Connection – RS485

3. On the Users & Reporting page, enter the phone numbers and e-mail addresses of the users who receive messages from the FireCom (section 6.4).
4. If you want the user to receive a message (or a call) about the events, tick the SMS (or Call) checkbox (System events page, SMS & Call reporting tab, section 6.9).
5. If the messages must also reach the monitoring station's receiver, set up the communication channel on the Reporting to CMS page (sections 4.2 and 6.3).

The Polon-Alfa 3000 panel with the MK-30 module must be set up in the POLON Studio software to work with the Modbus RTU (RS485) protocol.

Test the system: trigger a fire alarm and check that the FireCom's messages arrive at the monitoring station and in Protegus 2.

Connection over the local network (LAN)

The FireCom and the Polon-Alfa 3000 panel connect to the same local network (LAN).

• 1 LAN cable ("LAN cable")

Setting up the FireCom in TrikdisConfig:

1. In the RS485 2 interface group of the Modules page, select the Polon-Alfa 3000 panel.
2. As the connection type (Connection), select TCP.
3. Enter the IP address of the Polon-Alfa 3000 panel (IP address).

• 1 Interface type – selecting Polon-Alfa 3000
• 2 Connection – TCP
• 3 IP address – the IP address of the panel (192.168.1.2 in the picture)

4. On the Settings tab of the Reporting to CMS page, in the LAN network parameters group, tick the DHCP checkbox (automatic registration mode): this way the FireCom reads the network settings (subnet mask, gateway) automatically and gets an IP address (section 6.3).
5. On the Users & Reporting page, enter the phone numbers and e-mail addresses of the users who receive messages from the FireCom (section 6.4).
6. If you want the user to receive a message (or a call) about the events, tick the SMS (or Call) checkbox (System events page, SMS & Call reporting tab, section 6.9).
7. If the messages must also reach the monitoring station's receiver, set up the communication channel on the Reporting to CMS page (sections 4.2 and 6.3).

The Polon-Alfa 3000 panel with the MK-30 module must be set up in the POLON Studio software to work on the local network (LAN). Enter the LAN IP addresses according to the settings of your own network.

Test the system: trigger a fire alarm and check that the FireCom's messages arrive at the monitoring station and in Protegus 2.

3.10 Connecting a temperature sensor

Connect the temperature sensors according to the drawings.

• red wire ("Red wire")
• yellow wire ("Yellow wire")
• black wire ("Black wire")

• red wire ("Red wire")
• yellow wire ("Yellow wire")
• black wire ("Black wire")

Up to 8 Maxim® / Dallas® DS18S20 or DS18B20 temperature sensors, or up to 1 AM2301 humidity and temperature sensor, can be connected to the FireCom. If you connect the sensor with a wire longer than 0.5 m, we recommend a twisted-pair cable (UTP 4×2×0.5 or STP 4×2×0.5). The board's +5V terminal supplies 5 V DC to the devices connected to the 1-Wire data bus; the maximum output current is 0.2 A. The output is protected against overload: if the current exceeds the maximum permitted value, the power is switched off automatically. The communicator detects and assigns the connected devices automatically (the AM2301 must be assigned manually on the Sensors page, section 6.8).

DS18B20 temperature sensor with 1m wire

3.11 Connecting a relay and an LED indicator

With the relay contacts you can switch various electrical devices remotely (on/off). The communicator's universal I/O terminal must be set as an output (OUT), and the Remote control definition must be assigned to it (PGM page, Output definition, section 6.7).

• R relay ("Relay")

3.12 Connecting the inputs of the fire alarm control panel

According to the EN 54 standard, the fire alarm control panel must be informed by the communicator about a fault in the connection to the monitoring station, and about the monitoring station having successfully received the messages. For this, the communicator's PGM outputs (for example the Relay1 and Relay2 outputs) must be connected to the dedicated inputs of the fire alarm control panel. The Relay1 PGM output must be set to CMS fail (fault in the connection to the monitoring station), and Relay2 to ACK received (acknowledgement received) (PGM page, section 6.7). The Relay1 output switches on when the communication channel to the monitoring station is interrupted; the Relay2 output switches on for 5 seconds when the message has successfully reached the monitoring station.

• R the communicator's relay output ("Relay"): Relay1 at the top, Relay2 at the bottom

3.13 Connecting iO series expansion modules

If the FireCom needs more inputs (IN) or outputs (OUT), connect a wired or wireless Trikdis iO series input and output expander to it. Section 6.5 (Modules page) describes how to set up the expansion modules in the FireCom.

Trikdis iO8 wired expander module

Connecting the LORA modules: the RF-LORA transceiver is placed on the RS485 bus and keeps a radio connection, up to 5000 m, with the iO-LORA, iO8-LORA and REL-LORA expanders and the PB-LORA panic button.

• W wireless connection ("Wireless connection"), up to 5000 m ("up to 5000 m")

The “up to … m” distances are theoretical maximums achievable under ideal conditions. In practice, the quality and routing of the cable, sources of interference and, for radio links, walls and terrain give a considerably shorter range. Plan with a margin, and on long runs check the connection during commissioning.

Trikdis RF-LORA wireless expander module Trikdis IO-LORA wireless expander module Trikdis IO8-LORA wireless expander module Trikdis PB-LORA wireless panic button

3.14 Powering up the communicator

To power up the communicator, switch on its power supply. The LEDs must behave as follows:

• the STA LED is steady green during power-up and flashes green after start-up – the supply voltage is correct;
• the SIM LED is steady green and from time to time flashes yellow at least 3 times – the green colour shows that the SIM card has successfully registered on the mobile network, and the number of yellow flashes shows the signal strength of the mobile network. The ETH LED is green if the communicator is connected to the local network (LAN).

4. Quick setup with the TrikdisConfig software

This chapter describes the settings with which the FireCom sends the events to the Protegus 2 app (section 4.1) or to the monitoring station (section 4.2). The other settings of the FireCom are in chapter 6.

1. Download the TrikdisConfig software (with the button above, or on www.trikdis.com type "TrikdisConfig" in the search field), and install it.
2. Connect the FireCom to the computer with a USB Type-C cable.
3. Start TrikdisConfig. The software detects the connected device automatically and opens the FireCom's programming window.
4. Click the Read [F4] button: the software reads and shows the FireCom's current settings. If the software asks for the administrator or installer code, enter the 6-digit code.

4.1 Setup for the Protegus 2 app

In the SIM group of the System Options page:

• 1 SIM card PIN – the SIM card's PIN code
• 2 APN – the mobile internet access point

1. Enter the SIM card's PIN code (SIM card PIN).
2. If needed, change the APN field. You can find the APN on the mobile operator's website; "internet" is universal and works in most operators' networks. Operator data for Europe: APN settings – list of European mobile operators.

In the Cloud application group of the Users & Reporting page:

• 3 Enable cloud service – switching on the Protegus cloud
• 4 Cloud Access Code – the cloud access code (123456 by default)

3. Tick the Enable cloud service checkbox.
4. If you want users to have to enter the code when they add the system to Protegus 2, change the value of the Cloud Access Code (123456 by default).

On the Settings tab of the Reporting to CMS page:

• 5 DHCP – automatic network setup
• 6 Protegus reporting mode – the order of the connection types used towards Protegus 2 (in the picture Main type: Ethernet (LAN), Backup type: SIM, Backup type 2: Disabled)

5. If a LAN cable is connected to the communicator, tick the DHCP checkbox (automatic registration mode): this way the FireCom reads the network settings (subnet mask, gateway) automatically and gets an IP address.
6. Here you set how the communicator sends the messages to Protegus 2. The connection types follow each other in order: if the connection fails with the primary connection type, the communicator switches to the next one, and so on. If the message was delivered to Protegus 2 over a backup connection type, after the set time the communicator tries the primary connection type again (Return to Primary).
7. On the Zones settings tab of the Zones page, tick the Prot. checkbox for the zones whose state changes the users should be notified about in Protegus 2 (section 6.6).
8. On the Outputs tab of the PGM page, tick the Prot. checkbox for the PGM outputs whose state changes the users should be notified about in Protegus 2 (section 6.7).
9. On the Events tab of the System events page, tick the Prot. checkbox for the communicator's internal events whose state changes the users should be notified about in Protegus 2 (section 6.9).

At the end of the setup, click the Write [F5] button and unplug the USB cable. Adding the system to the Protegus 2 app: section 5.1.

4.2 Setup for the monitoring station

On the System general tab of the System Options page:

• 1 Object ID – object identifier (0001 in the picture)
• 2 SIM card PIN – the SIM card's PIN code
• 3 APN – the mobile internet access point

1. Enter the object identifier received from the monitoring station (Object ID, account number): 4 characters, 0–9 and A–F. Do not use the identifiers FFFE and FFFF.
2. Enter the SIM card's PIN code (SIM card PIN).
3. If needed, change the APN field. You can find the APN on the mobile operator's website; "internet" is universal and works in most operators' networks.

On the Settings tab of the Reporting to CMS page:

• 4 DHCP – automatic network setup
• 5 CMS reporting mode – the order of the connection types used towards the monitoring station (in the picture Main type: Ethernet (LAN), Backup type: SIM, Backup type 2: Disabled)

4. If a LAN cable is connected to the communicator, tick the DHCP checkbox (automatic registration mode): this way the FireCom reads the network settings (subnet mask, gateway) automatically and gets an IP address.
5. Here you set how the communicator sends the messages to the monitoring station. The connection types follow each other in order: if the connection fails with the primary connection type, the communicator switches to the next one, and so on. If the message was delivered to the monitoring station over a backup connection type, after the set time the communicator tries the primary connection type again (Return to Primary).

On the Reporting tab of the Reporting to CMS page:

• 6 Communication type – the connection type
• 7 Domain or IP – the receiver's address
• 8 Port – the receiver's port
• 9 Protocol – transmission protocol
• 10 Encryption Key – encryption key (123456 in the picture)
• 11 Backup channel – the backup channel
• 12 Parallel channel – the parallel channel (TCP/IP in the picture)

6. Communication type – select the connection type (TCP or UDP).
7. Domain or IP – enter the receiver's domain name or IP address.
8. Port – enter the receiver's network port.
9. Protocol – select the protocol the device uses to send the messages: TRK (for Trikdis receivers), DC-09_2007 or DC-09_2012 (for universal receivers), TL150 (for Sur-Gard receivers).
10. Encryption Key – enter the receiver's encryption key.

11. (Recommended) Set up the backup channel (Backup channel).
12. If the messages must also be sent to the monitoring station's second receiver, set up the parallel channel (Parallel channel).

At the end of the setup, click the Write [F5] button and unplug the USB cable.

5. Remote control

The FireCom can be controlled from the Protegus 2 app, by SMS command and by phone call (with the phone's keypad during the call). In the app the users also see the state of the system and receive notifications about system events; by SMS the administrator can also change some of the settings.

5.1 Adding the FireCom to Protegus 2

In Protegus 2 the users see the state of the system and receive notifications about system events. The app is available for phones and in the browser (the download links are below, at creating the system).

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.

With the FireCom, pay attention to the following when adding it:

1. After Add new system, enter the FireCom's unique identifier (Unique ID), then click the Next button. You can find the identifier on the sticker on the device and on the box; with a USB connection you also see it in the TrikdisConfig status bar (section 6.1).
2. If the installer has changed the factory value 123456 of the Cloud Access Code, the app asks for the code when you add the system (section 4.1).

5.2 Setup and control by SMS message

1. Change the administrator password. For security, replace the factory administrator SMS password. Send an SMS in this format:

PSW 123456 xxxxxx

2. Allow control for other users. The system can only be controlled by SMS and phone call from the phone numbers on the user list. From the administrator's phone, send an SMS with the phone numbers and names of the other people so that they can also control the system:

SETN xxxxxx PHONEx=+PHONENR#NAME#EMAIL

List of SMS commands

5.3 Controlling the PGM outputs by phone call

If you want to control a PGM output remotely:

• The user must have the right to control the outputs (OUT) (section 6.4), and the Remote control type must be assigned to the output (OUT) in TrikdisConfig (PGM page, Output definition, section 6.7).
• Call the number of the FireCom's SIM card. The FireCom answers the call, and you can enter commands with the phone's keypad according to the table.

6. TrikdisConfig pages

This chapter describes the pages of the TrikdisConfig programming window, in the order in which they follow each other in the menu on the left. Connecting the FireCom with a USB cable: chapter 4; remotely: chapter 7.

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.

When you click the Read [F4] button, the software reads and shows the current settings stored on the FireCom. Set the required parameters based on the following page descriptions.

6.2 "System Options" page

The general settings of the device, on three tabs: System general, Groups and Access.

System general tab

General group

• Object ID – if the events go to the monitoring station, enter the object identifier received from the monitoring station (4-character hexadecimal number, 0–9, A–F). Do not use the identifiers FFFE and FFFF.
• Object name – the name of the object; this name appears in the SMS messages sent to the users.
• Test period – when ticked, the FireCom sends a "Test" message at the set interval.
• Start test at – when ticked, here you set at what time the test messages are sent.
• Clear Events after reset – when ticked, all unsent event messages are deleted on restart (reset).
• Text language – the language of the SMS messages: the device uses the specific characters of the selected language in the SMS messages.
• Suspend event reporting when … same events per … s – suspends event reporting if the given number of identical events repeats within the given number of seconds.
• Restore event reporting after … min – after this time the suspension of event reporting ends (0–999 minutes).
• Call – in the event of an event, the FireCom calls the user(s) this many times. If the call is rejected or answered, the FireCom stops calling. One call lasts 20 seconds.
• EOL Type – the nominal value of the resistors connected to the detectors (EOL – End Of Line; RT + R1 + R2: RT – tamper, R1 – detector 1, R2 – detector 2). The selectable values: section 3.2.
• Communication path test – the interval after which the communicator checks the backup communication channels: it sends a message over them to the monitoring station. After the messages have been sent, the communicator returns to the primary channel.

SIM group

• SIM card PIN – the SIM card's PIN code.
• APN – the name of the mobile operator's mobile internet access point. You must enter it if the event messages go over a mobile data connection (GPRS) to the Protegus 2 app or to the monitoring station. Operator data for Europe: APN settings – list of European mobile operators.
• Login, Password – the APN user name and password, if the mobile operator requires them.
• Locked ICCID – if you want the communicator to work only with a specific SIM card, enter the card's ICCID number.
• Preferred operator – after you enter the mobile operator's code, the communicator connects only to the network of the selected operator. The operator code consists of the MCC (country code) and the MNC (network code).

Time settings group

You can set the time with the Set PC time button. If Disabled is shown in the Time set field, the communicator takes over the computer's time. If a modem or a server is selected in the Time set field, the communicator synchronises its time to it.

• Time zone (hours) – the time zone of the country (for example +1 for Central European Time).
• Time set – the server to which the FireCom's internal clock is synchronised. Synchronisation takes place after the communicator is powered up.
• Daylight saving time – when ticked, the communicator's internal clock switches automatically between summer and winter time.
• Power failure delay – if the main power supply fails, the notification about the power failure is sent after the given delay. When the supply voltage returns, the notification about the restore is also sent after the given delay.

Groups tab

The zones can be assigned to partitions (Zones page, Group column, section 6.6). The name of each partition can be changed; the partition names are shown in Protegus 2.

Access tab

On the Access tab you set the access codes and the installer's permissions.

Access codes group

• Administrator Code – full access to the settings (123456 by default).
• SMS password – password for remote control and programming by SMS (123456 by default).
• Installer Code – limited access for changing the settings (654321 by default).

Installer permissions group – here the administrator sets which parameters the installer can change.

6.3 "Reporting to CMS" page

The FireCom sends the messages to the monitoring station over the internet (IP). A backup channel can be assigned to the primary channel: the device uses it if the connection on the primary channel is lost. The page has two tabs: Reporting and Settings.

Reporting tab

The messages sent to the monitoring station are encoded and password-protected. To receive the messages and pass them on to the monitoring software, a Trikdis receiver is needed:

• For IP messages: the IPcom receiver software (Windows or Linux), the RL14 IP/SMS hardware receiver or the RM14 multichannel receiver.

Trikdis IPcom v5 Windows software receiver Trikdis IPcom v5 Linux software receiver

Primary channel group – and in the same way the Parallel channel

• Communication type – the connection method with the monitoring station's receiver.
• Domain or IP – the receiver's domain name or IP address.
• Port – the receiver's network port.
• Protocol – the encoding used for the events: TRK (for Trikdis receivers), DC-09_2007 or DC-09_2012 (for universal receivers; when you select the SIA DC protocol, the SIA-DCS message format can also be selected), TL150 (for Sur-Gard receivers).
• Encryption Key – 6-digit encryption key; the communicator's encryption key must match the receiver's.

If you also enter the parameters of the parallel channel (Parallel channel), the messages go over both channels at the same time. The two channels cannot be set to the same receiver.

Backup channel group – and in the same way the Parallel backup channel. Switch on the backup channel so that the messages go over the backup channel if the connection is lost. Its settings are the same as above.

Settings tab

Settings group

• Return to Primary after – after this time the FireCom tries to return to the primary channel (Primary channel).
• IP PING period – the interval at which internal PING signals checking the connection are sent. The PING signals are sent only on an IP channel; the receiver does not pass them on to the monitoring software, so they do not load it. The software is notified only if the receiver gets no PING from the device for the set time.
• Backup reporting after – after how many unsuccessful sending attempts the FireCom sends on the backup channel (Backup channel): if the message is still not sent on the primary channel (Primary channel) after this many attempts, the device sends it on the backup channel.
• DNS1, DNS2 – the DNS servers (Domain Name System) that translate the domain name into an IP address. They are needed if you entered a domain name (and not an IP address) in the channel's Domain or IP field. By default, Google's DNS servers.

The fields below are visible only if you selected the DC-09_2007 or DC-09_2012 protocol in the channel's Protocol field:

• Object ID in SIA DC-09 – the object number; with the DC-09 protocol this number is put into the messages. Enter the 3–16-character hexadecimal number received from the monitoring station.
• SIA DC-09 receiver No. – the receiver number.
• SIA DC-09 line No. – the line number in the receiver.
• Local time in SIA – when ticked, the messages sent to the monitoring station contain the time set in the module.

Reporting mode group

Here you set how the communicator communicates on the monitoring station channels and with Protegus 2. The connection types follow each other in order: if the communicator cannot connect with the Main type connection type, it switches to the Backup type, and so on. If the message was delivered to the monitoring station over a backup connection type, after the given time the communicator tries the primary connection type again (Return to main).

• Main type – the primary connection type (SIM or Ethernet (LAN)) towards the monitoring station receiver and Protegus 2.
• Backup type – the backup connection type (SIM or Ethernet (LAN)) towards the monitoring station receiver and Protegus 2.
• Backup type 2 – the second backup connection type (SIM or Ethernet (LAN)) towards the monitoring station receiver and Protegus 2.
• Dual path for CMS – dual path mode: CMS1 works over LAN, CMS2 over SIM. The two channels and communication paths work in parallel.
• Return to main (both channel) – after this many minutes the FireCom tries to return to the primary channel if it has been working on a backup channel.

LAN network parameters group

• DHCP mode – the method of registering on the local network (LAN) (manual or automatic). When ticked (automatic registration mode), the FireCom reads the network settings (subnet mask, gateway) automatically and gets an IP address automatically.
• Static IP – static IP address in manual mode.
• Subnet mask – subnet mask in manual mode.
• Default gateway – default gateway in manual mode.
• LAN Trouble indication – when ticked, the communicator's LED lights up if the LAN connection is lost.

SIM parameters group

• Disable indication of the absence of a SIM card – when ticked, the FireCom does not indicate if there is no SIM card in it.
• Use dial and SMS when working over internet module – when ticked, the communicator can also be controlled by call and SMS. If it is not ticked and there is a LAN network, SMS and calls are not used. If it is not ticked and there is no LAN network, the FireCom can still be controlled by call and SMS, and it sends SMS messages to the user.
• Disable the use of SIM card mobile data – when ticked, the FireCom does not use the SIM card's mobile data connection: data is sent only over LAN. If the LAN network is temporarily unavailable, the FireCom stores the data in its memory and sends it over LAN once the LAN is back.

6.4 "Users & Reporting" page

The settings of the users, the Protegus cloud and the SMS replies, on three tabs: Users, Protegus and SMS answer texts. Setting up SMS messages and calls about the events of the fire alarm control panel (SMS for Panel events tab): section 3.6.

Users tab

Users & Reporting to User group

• ID – the user's number on the list.
• Name – the user's name; this name appears in the event SMS messages and in the app.
• Tel number – the user's phone number to which the SMS messages are sent; enter it starting with the international country code (+…). The first 8 phone numbers receive messages and calls about the events.
• E-mail – the user's e-mail address: the user receives the invitation to Protegus 2 at this address, so that they can control the system.
• PGM – when ticked, the user can control the outputs remotely (by call, by SMS).
• ACK – when ticked, the FireCom sends a reply SMS to the user after every SMS command received (the text of the replies: SMS answer texts tab).
• FWD – when ticked, the FireCom forwards to the user the SMS messages arriving from numbers outside the system (for example the SIM card's balance notifications or advertising messages).

Protegus tab

Cloud application group

• Enable cloud service – switches on the Protegus 2 service: this way the FireCom exchanges data with the Protegus 2 app and can also be set up remotely with TrikdisConfig (chapter 7).
• Parallel reporting – parallel reporting: the messages go at the same time over the primary channel (Primary channel) and to Protegus 2.
• Cloud Access Code – 6-digit code for logging in to Protegus 2 (123456 by default).

SMS answer texts tab

In the SMS text column you can edit the text of the replies sent to SMS commands. The texts of the SMS messages sent when the inputs and outputs are activated are also here.

6.5 "Modules" page

The settings of the expansion modules connected to the RS485 bus and of the fire alarm control panel connected to the RS485 2 bus.

RS485 modules tab

RS485 modules group

• ID – the module's number on the list.
• Module – the module used, from the module list: iO-8, iO-MO, iO-LORA, iO8-LORA, PB-LORA, REL-LORA (wiring: section 3.13).
• Serial No. – mandatory, 6-digit number; you can find it on the module's enclosure and packaging.
• Name – the name of the module (any).
• Firmware version – the module's firmware version; it appears when the FireCom finds the connected module.

RS485 2 interface group

A fire alarm control panel can be connected to the FireCom's RS485 2 bus: one with the ESPA 4.4.4 protocol, NSC Solution, INIM Smartline, C-TEC Cast ZFP or Polon-Alfa 3000. Sections 3.5–3.9 describe the wiring and setup of the panels.

6.6 "Zones" page

The settings of the zones (inputs), on three tabs: Zones settings, SMS & Call reporting and Zone's codes.

Zones settings tab

• Zone No – the zone's number on the list.
• Name – the zone's name; this name appears in the SMS messages and in the app.
• Input – which input (IN) of the FireCom or of the expansion module belongs to the zone.
• Group – assigning the zone to a partition (the partition names: section 6.2, Groups tab).
• Type – the type of the circuit connected to the zone's input: NC – normally closed; NO – normally open; EOL – with an end-of-line resistor; EOL_T – with an end-of-line resistor and tamper monitoring; ATZ – two-zone, normally closed circuit with end-of-line resistors, without tamper monitoring (to use it, select the second ATZ zone in the input list); ATZ_T – two-zone, normally closed circuit with end-of-line resistors, with tamper monitoring (to use it, select the second ATZ zone in the input list). The wiring diagrams: section 3.2.
• CMS – when ticked, messages about the zone's events go to the monitoring station.
• Prot. – when ticked, notifications about the zone's events go to the Protegus 2 app.
• Delay – the reaction time of the input (IN) in milliseconds.

SMS & Call reporting tab

This tab appears only if you have entered at least one user phone number on the Users & Reporting page.

• Zn – the zone number with the event's keyword: Event or Restore.
• User SMS/Call – for each zone event you can select whether the user receives an SMS and/or a call.

Zone's codes tab

When the zone is violated, the communicator sends an event message. A Contact ID (SIA) code belongs to the input; this is sent to the monitoring station and to Protegus 2.

• Enable – messages go to the monitoring station and to Protegus 2 from the ticked event fields.
• E/R – which event type is sent when the input is activated: Event (E) or Restore (R).
• CID – the event code; enter it, or leave the factory value.
• SIA – the SIA event codes.
• Group – the partition number sent when the event occurs.
• Zone – the zone number sent when the event occurs.

6.7 "PGM" page

The settings of the PGM outputs, on four tabs: Outputs, Set Action, Scheduler and SMS & Call reporting.

Outputs tab

• PGM No – the PGM output's number on the list.
• Name – the name of the PGM output.
• PGM output – the output (OUT) assigned to the PGM: that of the FireCom or of an external device.
• Output definition – the operating mode of the output (OUT) (Remote Control in the picture).
• Pulse time, s – how long the output (OUT) stays on, 0–9999 seconds.
• CMS – when ticked, messages about the selected events go to the monitoring station.
• Prot. – when ticked, notifications about the output's events go to the Protegus 2 app.

Set Action tab

• ID – the output's number on the list.
• Enable – switches on the PGM operating algorithm.
• PGM No. – the output (OUT) that the communicator controls when the event described in the Factor, Factor No., Start when and Set value columns occurs.
• Action – the action:
  • PGM OFF – the state of the output (OUT): off ("Off").
  • PGM ON – the state of the output (OUT): on ("On").
  • Pulse OFF – the initial state of the output (OUT) is on ("On"); after the command it switches off ("Off") for the pulse time (Pulse time), then automatically returns to the initial, on state.
  • Pulse ON – the initial state of the output (OUT) is off ("Off"); after the command it switches on ("On") for the pulse time (Pulse time), then automatically returns to the initial, off state.
• Pulse time, s – the pulse time, 0–9999 seconds.
• Factor / Factor No. – which event switches the output (OUT) on: a zone (Zone), the arrival of an SMS (SMS received) or a zone tamper (Zone tamper).
• Start when – an additional condition for switching the output (OUT) on, depending on the Factor event.
• Set value – depending on the condition selected in the Factor column, here you can enter a value (the text of the received SMS). If the communicator recognises this value, it performs the action selected in the Action column. You can structure the SMS text with % signs: the % signs separate the keyword that changes the output state from the whole received SMS.

The SMS text is case-sensitive.

Scheduler tab

• ID – the schedule's number on the list.
• Enable – switches on the schedule.
• Start time – when the output (OUT) switches on – the start of the schedule.
• Stop time – when the output (OUT) switches off – the end of the schedule.
• Mon – Sun – the days of the week on which the output (OUT) must switch on or off.

SMS & Call reporting tab

This tab appears only if you have entered at least one user phone number on the Users & Reporting page. These settings can apply only to the first 8 users.

• PGM – the number of the output (OUT) and the event type: Event – the output switches on; Restore – the output switches off.
• User SMS/Call – you can select which users receive an SMS and/or a call when the output (OUT) switches on and off.

6.8 "Sensors" page

The settings of the temperature sensors (wiring: section 3.10).

• ID – the temperature sensor's number on the list.
• Module type – the temperature sensor assigned to the row (ID).
• Serial No. – the sensor's serial number; the communicator reads it out.
• Sensor name – the name of the sensor.
• Max – if the temperature is higher than this, an event message is generated; for this the High checkbox must be ticked.
• Min – if the temperature is lower than this, an event message is generated; for this the Low checkbox must be ticked.
• Delay – the event is sent if the value measured by the sensor crosses the Max or Min value within the set time. Enter the time in minutes.
• Sensor type – the type of the connected temperature sensor: Dallas 1Wire – up to 8 such sensors can be connected, and the communicator assigns them automatically; Humidity & Temperature – one AM2301 temperature and humidity sensor can be connected; if you use it, it must be assigned manually in the Module type column.

6.9 "System events" page

The settings of the communicator's own (system) events, on two tabs: Events and SMS & Call reporting.

Events tab

• ID – the event's number on the list.
• Event name – the name of the event.
• Enable – switches on monitoring of the event.
• CMS – messages about the selected events go to the monitoring station.
• Prot. – notifications about the selected events go to the Protegus 2 app.
• CID Code – the Contact ID code of the event.
• SMS event text – the SMS text of the event.
• SMS restore text – the SMS text of the restore.

SMS & Call reporting tab

This tab appears only if you have entered at least one user phone number on the Users & Reporting page.

• ID – the event's number and keyword (Event, Restore).
• Event SMS text – the text of the event that goes into the SMS message.
• User SMS/Call – for each event you can select whether the user receives an SMS and/or a call.

6.10 "Events Log" page

Here you can read out and clear the device's event log.

• Read Log – the button reads the event log from the device's memory.
• Clear Log – the button deletes the log entries from the device's memory.
• The table shows the event's number (Event No.), time (Time), CID code and description (Event definition). The log shows up to 1000 events stored in the FireCom's memory.

6.11 Restoring the factory settings

To restore the FireCom's factory settings, click the Restore button in TrikdisConfig.

7. Remote programming

You can also read and change the FireCom's settings remotely with TrikdisConfig, through the Protegus cloud – you do not need to go to the site.

1. Start TrikdisConfig on the computer.
2. In the Remote access area, enter the FireCom's unique identifier (Unique ID) in the Unique ID field. You can find this number on the back of the device and on its packaging.

3. (Optional) In the System Name field, enter a name for the device (for example the name of the object).
4. Click the Configure button.
5. In the window that opens, click the Read [F4] button. If the software asks for it, enter the administrator or installer code.
6. At the end of the setup, click the Write [F5] button. When you have finished with TrikdisConfig, click the Disconnect button.

8. Testing the operation

At the end of the setup and installation, test the whole system:

1. To check an input, activate (violate) the input. Check whether the event has arrived at the monitoring station and/or in the Protegus 2 app.
2. To check the outputs, switch them on remotely and check that they work. Make sure that the events have arrived at the monitoring station and/or in the Protegus 2 app.
3. Carry out a fire alarm test, and check that the monitoring station receives the events correctly.

You can also query the communicator's data, the state of the inputs and outputs and the values of the temperature sensors by SMS: INFO 123456, ASKI 123456, ASKO 123456, ASKT 123456 (replace 123456 with your own SMS password; section 5.2).

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.

Connect the FireCom to the computer with a USB Type-C cable, or log in remotely (chapter 7).

10. Troubleshooting and frequently asked questions

If the communicator does not do what you expect, first look at the LEDs (section 1.5), then at the points below.

The STA LED (TROUBLE on the front) flashes red – what does the number of flashes mean?

The number of flashes is the cause of the fault: 1 – no SIM card inserted; 2 – the SIM card's PIN code is wrong (System Options → SIM card PIN, section 6.2); 3 – cannot connect to the mobile network; 4 – cannot connect to the IP receiver on the primary channel (Reporting to CMS, section 6.3); 5 – cannot connect to the IP receiver on the backup channel; 6 – no DC supply voltage (section 2.1); 7 – AUX output fault (overcurrent or overvoltage); 8 – battery fault (section 2.2); 9 – the LAN cable is not connected; 10 – DHCP error on the local network (LAN network parameters, section 6.3).

The FPS LED (POWER on the front) flashes green – what is wrong?

1 green flash: no mains (AC) supply voltage. 2 green flashes: the voltage of the backup power supply (battery) is not sufficient (section 2.2). If the LED is steady green, there is no problem with the power supply (section 1.5).

How many yellow flashes are needed on the SIM LED?

The number of yellow flashes shows the signal strength of the mobile network: on a 4G network, 3 flashes are already sufficient. If you count fewer yellow flashes than this, the signal strength is not sufficient: choose another place for the communicator, move the antenna, or use a more sensitive mobile antenna (sections 1.6 and 3.14). If none of the FireCom's LEDs light up, check the power supply and the wiring.

The ETH LED flashes green

The LAN cable is not connected, or there is a DHCP error (section 1.5). Check the cable and the router. For automatic address assignment, DHCP mode must be ticked; for manual setup, fill in the Static IP, Subnet mask and Default gateway fields (Reporting to CMS → Settings, LAN network parameters, section 6.3). What the network must provide: section 3.1.

Protegus 2 cannot find the communicator

• Check the conditions for adding it: activated SIM card, PIN code entered or switched off, Protegus service switched on (Users & Reporting → Enable cloud service, section 6.4), STA flashing green, and the SIM LED steady green and flashing yellow and/or the ETH LED green (section 5.1).
• If the SIM or the DAT LED is steady yellow, the device cannot connect to the mobile network and/or to Protegus 2 (chapter 7). Check the APN setting (section 6.2).
• If the Cloud Access Code is not the factory 123456, enter the correct code when adding the system (section 4.1).

I cannot control the outputs by call or SMS

• Control by SMS and call is only possible from the phone numbers on the user list (section 5.2).
• The user must have the right to control the outputs (PGM checkbox, section 6.4), and the Remote control definition must be assigned to the output (Output definition, section 6.7).
• Check the Use dial and SMS when working over internet module checkbox (section 6.3): if it is not ticked and there is a LAN network, calls and SMS are not used.

I get no reply to my SMS commands

For the reply SMS, the ACK checkbox must be ticked for the user (Users & Reporting, section 6.4). You can edit the text of the replies on the SMS answer texts tab.

Can the data go over the local network (LAN) only?

Yes. If you tick the Disable the use of SIM card mobile data checkbox, the FireCom does not use the SIM card's mobile data connection: the data goes over LAN only. If the LAN is temporarily unavailable, the communicator stores the data in its memory and sends it once the LAN is back. If there is no SIM card in the communicator, you can switch off the indication of its absence with the Disable indication of the absence of a SIM card checkbox (section 6.3).

How many smoke detectors can be connected to the FLOOP terminal?

Up to 8 two-wire fire detectors whose alarm current is greater than 10 mA. A 2.2 kΩ end-of-line resistor is needed after the last detector, and on the Zones page the FC Fire sensor (FLOOP input) input must be selected as the zone's input (sections 3.3 and 6.6). If you connect the detectors to an IO input, the wiring diagrams are in the same place.

What kind of temperature sensors, and how many, can be connected?

Up to 8 Maxim® / Dallas® DS18S20 or DS18B20 temperature sensors, or 1 AM2301 humidity and temperature sensor. The communicator assigns the Dallas sensors automatically; the AM2301 must be assigned manually on the Sensors page (sections 3.10 and 6.8). You can also query the values by SMS: ASKT (section 5.2).

What battery is needed?

A 12 V, 4 Ah or 7 Ah lead-acid battery (sections 1.2 and 2.1). According to the EN 54 standard, the battery must charge to 80 % of its capacity within 24 hours and reach the rest within the following 48 hours (section 3.1). At 11.5 V a Low Battery message is sent, below 9.5 V the battery is disconnected (section 2.2).

How does the fire alarm control panel know that the message has reached the monitoring station?

According to the EN 54 standard, the panel must know about a fault in the connection to the monitoring station and about the successful reception of the messages. For this, two PGM outputs of the communicator must be connected to the dedicated inputs of the panel: the Relay1 output set to CMS fail switches on when the communication channel is interrupted, and the Relay2 output set to ACK received switches on for 5 seconds when the message has reached the monitoring station (section 3.12).

INIM Smartline: what should I watch out for?

The panel must be set to slave mode in the SmartLeague software. If repeaters are connected to the panel, the FireCom cannot be connected on the RS485 bus; and if the FireCom is connected to the panel's RS485 bus, the iO expansion modules are not supported (section 3.7).

NSC Solution: the panel does not see the communicator

After setting up the FireCom, the modules connected to the RS485 bus must be searched for (scanned) on the panel (SCAN RS485, section 3.6). The NSC slave address must not be the same as the address of the modules connected to the panel.

11. Safety instructions

• The communicator may only be installed and maintained by a qualified person.
• Read this manual carefully before installation to avoid mistakes that can lead to malfunction or even damage to the equipment.
• Disconnect the power supply before every electrical connection.
• Changes, upgrades or repairs not authorized by the manufacturer void the warranty.
• Follow local waste disposal regulations: do not throw the device and its parts in household waste – hand in the discarded device as electronic waste.

See also

• iO8 input and output expander – installation manual – the iO-8 expansion module for the FireCom.
• APN settings – list of European mobile operators – if the mobile data connection is not established.
• Protegus Android / iPhone and web app – about the app.
• Protegus 2 Business Account – managing several systems as an installer.
• Documentation in English: docs.trikdis.com – Communicator FIRECOM for fire alarm control panels. The manuals on docs.trikdis.com are in English.