IMPORTANT NOTE:
If intending to use dial capture or serial for sending alarms,
please confirm beforehand with your ARC that their automation software is capable
of differentiating correctly between pin alarms (Essential IP or Redcare Platform
generated alarms), and alarm panel generated zone alarms.
Alarm list
Description
Pin
CID (zone)
Inputs 1–16
1–8
323 (901–8)
Low Battery
985
302 (999)
Unit reboot
984
305 (995)
Panel dial fail
983
314 (999)
Software changed
979
304 (999)
Panel message error
958
311 (997)
Panel Connection (RS485)
n/a
356 (997)
BSIA 175 Test
n/a
354 (998/999)
Inputs 1–8 Cut alarm
n/a
325 (901–16)
Inputs 1–8 Short Alarm
n/a
324 (901–16)
Total Comms Fault
n/a
350 ( 999)
Figure 9 – alarms signals as delivered to your ARC
IP specification notes
IP Protocol:
TCP
Port:
443 or 10443
Data Usage/requirements
IP polling occurs every 300 seconds. A poll and
response results in 288 total bytes transferred
(including IP headers). Typically, a small number of
alarms will also be generated per day, resulting in
296 bytes being transferred. Overall, this generates
approximately 500K bytes per day, per site.
Traffic direction
The Essential IP establishes an outgoing TCP
connection from your network to the BT Redcare
platform. Once this outgoing TCP connection has
been established, traffic over that connection is
two-way.
Additional protocols
Only TCP is required from your network.
Port forwarding
No ports need to be forwarded in the incoming
direction. The outgoing TCP connection connects
to port 443 or 10443 on the BT Redcare network,
so you need to allow outgoing access to port 443,
or 10443 if you block that by default.
NAT:
Not required
DHCP and static addressing
The communicators can be configured either as
DHCP clients, or with specific static IP addresses on
your internal network as you prefer.
DNS server
The device uses host names for establishing
connection to the servers, so DNS addresses
will be needed.
59