Accessing the FACP through the BNIC
Terminal emulation
To access the FACP from the Building Network once the BNIC has been installed:
1.
Connect the PC to a Building Network Ethernet port.
2.
Start the ES Panel Programmer.
3.
Click on
Terminal
on the Programmer’s task bar.
4.
Click on
Ethernet Connection
5.
Click on
Panel for loaded job
. This will automatically launch
Tera Term
and connect to the panel identified by the current job.
Figure 16: Opening Tera Term
6.
Proceed as you would if you were connected to the FACP through the service port.
Building Network Interface Card MIS/IT Configuration Worksheet
Terms
Table 6: Terms
Term
Definition
DHCP
Dynamic Host Control Protocol
DNS
Domain Name System
mDNS
DNS Multicast Domain Name System
MAC
MAC Media Access Control
FACP
Fire Alarm Control Panel
RFC
Request for Comments
About the BNIC
The Building Network Interface Card (BNIC) is a module that mounts internally to a fire alarm control panel (FACP) located on your premises to provide
the ability to access the FACP through a secure IP network channel. To interface the FACP to your Internet LAN, an EIA/TIA-568A CAT-5 (10/100-BaseT)-
compliant Ethernet drop to the panel is required. This connection requires a standard Ethernet RJ-45 terminating connector.
BNIC installation prerequisite
There are 2 options available for obtaining an IP address for the BNIC. Before installing the BNIC, coordinate with the MIS/IT department to determine
how they want the system to operate.
Customer Network:
Option 1:
DHCP served IP address. This is the preferred method for obtaining an IP address. In order for the BNIC to function properly, DHCP must be
used in conjunction with a name service (DNS or mDNS).
Option 2:
Fixed IP address. This method should only be used when a name service is not available.
There are 2 name service options available for resolving the FACP name to an IP address.
Option 1:
DNS. DNS is required when the network hosts (FACPs and the service PC) will not be in the same broadcast domain. This is normally the
case when the network hosts are on different subnets.
Option 2:
mDNS. mDNS is the preferred method when all network hosts (FACP and service PC) are in the same broadcast domain. The name to IP
address resolution requires no additional MIS/IT support. mDNS also provides FACP panel discovery.
Panel Discovery is supported through DNS. This requires additional MIS/IT support. The DNS server must be configured with service records (defined
in RFC 2782). This also must be coordinated with the MIS/IT department prior to installation.
page 13
579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual
