Ethernet Communicator
Ethernet-based IP communicators for alarm systems – with stable, fast and reliable connection to the monitoring service. Trikdis Ethernet communicators connect via the control panel's data bus or serial port, enabling not just event transmission but also remote arming and disarming.
With the Protegus 2 app, real-time notifications and remote control are available. Compatible with Paradox, DSC and other manufacturers' alarm control panels.
There are no products to list in this category.
Frequently asked questions
Put the communicator on a separate, isolated network or VLAN with no access to the internal LAN. Local firewall and filtering rules then cannot block its outgoing connection, and the alarm device cannot see the internal machines either. No inbound port forwarding is needed — outgoing internet access is enough.
The symptom: the Ethernet-connected device — E16, E16T, GET or FLEXi SP3 — is on the network and gets an IP address, yet no connection is established towards Protegus 2 or the monitoring station.
Why: in most such cases the device is not at fault; the local network simply will not let it out. On company and institutional networks this is caused by a firewall rule, a content filter, a proxy, MAC filtering or a strict VLAN policy. In our experience this happens almost exclusively on closed corporate networks — but there we have run into it several times already.
The recommended solution: put the communicator on a separate, isolated network or VLAN with no access to the internal LAN. This solves two things at once:
- the internal network's rules do not interfere with the communicator's outgoing traffic;
- it is also the right arrangement from a security point of view: the alarm device cannot see the internal machines, and a possible infection of the internal network cannot reach the communicator.
What the device needs:
- outgoing internet access, without filtering;
- DHCP, or with a fixed IP address the correct gateway and DNS;
- no inbound port forwarding is required — the communicator establishes the connection outwards itself.
If a separate VLAN is not possible: on the firewall, exclude the device's IP address from content filtering and from the proxy, and allow its outgoing traffic without restrictions.
And keep in mind: a communicator has two separate connections — one towards the alarm panel (bus or TIP/RING) and one outwards (Ethernet or SIM). This fault affects the outward side; communication with the panel may well be working.
On many switches, loop protection (loop detection) for some reason detects the E16 as a loop and blocks its port. It is a common, known issue, not a cable or configuration fault. On a managed switch, turn off loop protection on that port. On an unmanaged switch it cannot be turned off, so the communicator has to be connected to a managed switch or a router.
The symptom: the E16 is connected to a switch, the cable is fine, yet it gets no IP address and reaches neither Protegus 2 nor the monitoring station. On a managed switch the interface shows the port as "loop detected" or "blocked". The same can happen with the other Ethernet communicators (GET, FLEXi SP3).
Why: many switches have loop protection (called loop detection, loop prevention, loop guard or loopback detection) — not only managed ones but simple unmanaged ones too. For some reason the switch detects the E16 as a loop and blocks its port. It is a common, known issue, not a fault of the device, the cable or the settings.
The solution:
- Managed switch: log in to its management interface and turn off loop protection on the port the communicator is connected to; if the port stays blocked, re-enable it.
- Unmanaged switch: loop protection cannot be turned off on it. Connect the communicator to a router or a managed switch and turn off loop protection there on the communicator's port.
Nothing needs to be changed on the communicator itself. If the port is not blocked and the communicator gets an IP address but still cannot reach the internet, see the question about closed corporate networks.
The Starlink router may block the E16's communication, and since it is not manageable, this cannot be resolved on it. Turn on Bypass Mode in the Starlink app and connect the E16 to your own router (for example TP-Link) that is connected to Starlink.
The symptom: the E16 is connected to Starlink internet through the Starlink router, yet it cannot reach the monitoring station. The TROUBLE LED blinks 6 times, which according to the manufacturer's manual means there is no connection with the monitoring station's receiver.
Why: the Starlink router may block the communicator's traffic. The Starlink router is not manageable, so this cannot be resolved on it. The solution is to take the Starlink router out of the path and let your own router manage the network.
The solution:
- In the Starlink app settings, turn on Bypass Mode (Settings → Bypass Mode). It roughly corresponds to the bridge mode familiar from modems: the Starlink router switches off, its WiFi is disabled too, and from then on your own router manages the network.
- Connect the WAN port of your own router (for example TP-Link) to Starlink, with the WAN set to DHCP. How to connect differs by Starlink kit (some need the Starlink Ethernet Adapter); Starlink support describes it kit by kit.
- Connect the E16 to one of the LAN ports of your own router. If the E16 has a fixed IP address, adjust it to your router's address range (gateway, DNS); with DHCP it gets an address automatically.
Note: according to Starlink, Bypass Mode can only be turned off by a factory reset of the Starlink router.
If the connection still fails behind your own router, also see the questions about switch loop protection and closed corporate networks.