Skip to content

RL25 hardware receiver

RL25 is IPCom v5 delivered on dedicated, prevalidated hardware. It runs the Linux edition, and the web interface is largely the same as any other IPCom v5 Linux deployment — so the rest of this IPCom section describes how to operate it. This page covers what is specific to the hardware unit, including the one section RL25 has that other deployments do not.

Some material elsewhere in this section does not apply to RL25:

  • The Windows .exe access flow in Access and login.
  • The Windows column of the capability comparison in the overview.
  • The server sizing and operating-system requirements in the overview. Those are for building your own Linux server; RL25 arrives with that work done.
  • The General page describes a non-RL25 deployment, so it does not show the Network settings section covered below.

1. Form factors

Variant Description
RL25 Compact Standalone unit
RL25 Rack 19-inch rack-mounted unit

Both variants run the same IPCom v5 software. This page describes both known form factors — confirm which is currently orderable with TRIKDIS sales.

2. What ships preconfigured

RL25 arrives with the platform installed, so you go straight to configuring the receiver rather than building a server. Compared with a Windows or Linux installation, the following are already done for you:

  • Linux operating system installed and configured
  • IPCom v5 installed
  • SSD and RAM preinstalled

You do not install an operating system, prepare a server, or run an installer.

RL25 is sold licensed.

3. Front panel indicator

The unit has a single blue indicator, which shows only whether it is powered on. There are no separate indicators for network, reception or fault conditions. The unit reports its condition through the software instead — see Status and Logs.

4. Specifications

Item RL25
Power supply External supply, nominal 220 V AC mains in, DC 12 V 5 A out
Network interfaces 2 × Ethernet RJ-45
IP receiver Yes
Event reception TCP, UDP, COM, RS232
Supervised objects Up to 50,000 per 1 GB RAM
Management Web browser over HTTP/HTTPS
Remote configuration and control TrikdisConfig, API, Protegus 2 Cloud
Compatible devices All TRIKDIS devices
Rack height 2U (Rack variant)

4.1 Event output

RL25 supports the full IPCom v5 output set. In the Outputs tab you choose an output Type and, for the types that carry CMS traffic, a Protocol.

Types: TCP, TCP Server, COM Port, JSON Server, Webhook.

Protocols: Surgard MLR2, Surgard MLR2 8, Surgard MLR2 No End, Surgard MLR2 Line with Account, SurgardMRL2000 CID, Monas 3, Ademco 685, Ademco 685 CID, SIA DC-09.

Writing events to a MySQL database is configured separately, under Database settings in the General tab — not in Outputs.

4.2 Environmental reference data

These are the computer manufacturer's figures for the machine inside the unit, not a tested rating for the assembled receiver with its external supply.

Item Manufacturer's figure
Operating temperature −20 °C to +65 °C
Storage temperature −20 °C to +75 °C
Operating humidity 5–95 % RH, non-condensing

The assembled RL25 has no validated environmental rating. Do not approve an installation on the strength of these numbers — for a cold, hot, humid or otherwise unconditioned location, confirm with TRIKDIS first.

5. Capabilities compared with other deployments

RL25 runs the Linux edition, so it carries the Linux feature set — including the Protegus 2 relay, which the Windows installation does not provide. See the capability comparison in the IPCom overview for the full table.

6. Connecting for the first time

Both Ethernet interfaces are identical and both use DHCP. No interface is dedicated to management — IPCom is reached at whatever address your DHCP server assigns, on the same TCP port whichever interface you use.

Before you begin:

  • The unit needs DHCP to be reachable the first time. There is no alternative — no fixed fallback address, and no way in over a serial or direct connection. On a network without a DHCP server you cannot reach it at all.
  • The unit is powered through an external supply, included with it. It takes nominal 220 V AC mains and delivers the DC 12 V, 5 A the receiver needs, so you do not provide a DC source yourself. Check the input voltage and frequency printed on the supply against your local mains, and check the cord and plug, before energising it. A power cable, a LAN cable and a rack bracket are normally supplied too; check against the packing list for your order.
  1. Connect the unit to your network with an Ethernet cable, using either interface.
  2. Apply power.
  3. Find the address assigned to the unit, from your router's or DHCP server's client list.
  4. Open https://<address>:30003 in a browser. TCP port 30003 is IPCom's default for HTTPS; 8080 is the default for HTTP.
  5. Sign in — see Access and login.

Tip

Leaving the unit on a plain DHCP lease means its address can change when the lease is renewed, and the receiver moves without warning. Either reserve its address on your DHCP server, or give it a fixed address in Network settings.

The power supply is external — it sits outside the chassis, so allow for it when planning the installation.

7. Network settings

The General tab on an RL25 has a Network settings section that does not appear on Windows or self-installed Linux deployments. On those, the operating system is yours and TRIKDIS does not manage it; on RL25 the appliance owns the network configuration, so it is configured here.

Warning

Plan the change before you make it. Decide the address, prefix, gateway and DNS values in advance, confirm the new address is reachable from where you are working, and make sure you have another way onto the unit's network if it is not. Changing the settings of the interface you are connected through will drop your session.

You need an account with the network_settings permission. Each interface is listed by name with a DHCP toggle; turning DHCP off reveals the fixed-address fields:

Field Purpose
IP address The fixed address for this interface
Prefix Network prefix length, for example 24 for a 255.255.255.0 mask
Gateway Default gateway
DNS 1, DNS 2 Name servers

After you apply a change, IPCom runs a verification step and reports whether it could confirm the unit on the new settings. Treat that as a signal, not a guarantee — confirm access yourself through the new address before you rely on it.

8. Restoring factory defaults

Restoring defaults is a software function, performed from within IPCom Control. There is no hardware reset button on the unit.

Warning

A restore returns IPCom to factory settings, so the configuration on the unit is lost. Do not run it on a receiver that is in service.

A restore does not touch the network interfaces. Whatever you set under Network settings — DHCP or a fixed address — survives it, so the unit keeps its address. IPCom itself returns to its default ports, which it reports as 8080 for HTTP and 30003 for HTTPS, so reconnect there if you had changed them.

9. After the first login

Work through these in order to get a new receiver into service:

  1. Status — confirm the unit is healthy and reachable.
  2. General — review API and database options, and configure them if your deployment needs them.
  3. Receivers — define the receiver lines that accept device events.
  4. Outputs — route events to your monitoring software.
  5. Users — create named operator accounts for daily work, and reserve administrator for break-glass use.

Review Networking and firewall before exposing the unit beyond a trusted network.