Simplex 4100-6047 Assembly instructions

Cautions, warnings, and regulatory information
READ AND SAVE THESE INSTRUCTIONS Follow the instructions in this installation manual. These instructions must be followed to avoid damage to
this product and associated equipment. Product operation and reliability depend upon proper installation.
DO NOT INSTALL ANY SIMPLEX™ PRODUCT THAT APPEARS DAMAGED Upon unpacking your Simplex product, inspect the contents
of the carton for shipping damage. If damage is apparent, immediately file a claim with the carrier and notify an authorized Simplex
product supplier.
ELECTRICAL HAZARD Disconnect electrical field power when making any internal adjustments or repairs. All repairs should be
performed by a representative or an authorized agent of your local Simplex product supplier.
STATIC HAZARD Static electricity can damage components. Handle as follows:
• Ground yourself before opening or installing components.
• Prior to installation, keep components wrapped in anti-static material at all times.
FCC RULES AND REGULATIONS – PART 15. This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment
is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming
Manual
*0579949D*

Introduction
The Building Network Interface Card (BNIC) allows the connection of a 4100ES or 4010ES Fire Alarm Control Panel (FACP) to a local area Ethernet
network (LAN) or to a dedicated Ethernet network used only for the fire alarm systems. Figure 1 shows the BNIC connection on a 4100ES panel. The
4010ES connection is similar but the board and connection locations are different.
Note: The BNIC is for ancillary use only and does not provide any fire alarm or burglary function other than a tool for service technicians to use in
configuring and maintaining the system.
Important: To use the BNIC, you must have a 4100ES Master Controller Card (566-719) installed in your system, OR have a 4010ES FACP. If you are
using an older 4100U CPU Card, upgrade using the 4100-7158 upgrade kit.
Figure 1: BNIC connection diagram (4100ES connection shown)
*4100-6047 BNIC shown.
BNIC Overiew
The BNIC isolates the FACP from the external or building network but allows an authorized user with the proper security clearance to access the FACP
through the Network. Authorization is provided transparently through service tools such as the ES Programmer.
A service tool connected to the FACP through the BNIC will behave as if it were directly connected to the Panel. In an ES Net configuration, the BNIC
can not remotely connect to other panels on the Fire network.
Package contents
This package includes:
• One 4100-6047 (4100ES FACP) or 4010-9914 (4010ES FACP) BNIC
• Hardware to secure the BNIC in the expansion bay
• Two 5ft (1.5 m) Ethernet cables (746-186)
FACP requirements
The FACP must meet the following requirements for the card to function properly:
• It must use the 4100ES Master Controller Card or be a 4010ES
• It must use FACP System Firmware version 1.01 or later
page 2 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Card specifications
Table 1: Card specifications
Card size: 4 x 11¼ inches (102 x 286 mm) /dual block module (occupies 2 vertical PDI
blocks)
Earth fault detection (Port A only): 10 K Ohm max direct current connection to earth
Operating conditions:
Operating temperature range 32°F - 120°F (0°C - 49°C)
Operating humidity range Up to 93% relative humidity at 90oF (32°C)
Power requirements:
Operating voltage Nominal 24 VDC from PDI
Maximum current over operating range 291 mA (maximum over range)
Figure 2: BNIC layout
page 3 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Setting DIP switch SW1
Dual Inline Package (DIP) Switch SW1 is used to set the BNIC eSlave address as identified in the ES Panel Programmer job. The address is set with the
card in its normal orientation (connectors up) as shown in the mounting instructions (see Figure 6).
Table 2: BNIC DIP switch functions
Switch Position Function Figure
ON Sets the card to “online” and allows the card to operate
normally.
SW1-1
OFF Sets the card “offline” which stops all communication to
the FACP.
ONSW1-2
through SW1-8 OFF
Set the BNIC eSlave address. Refer to Figure 4 for a
complete list of switch settings for all possible card
addresses.
Figure 3: BNIC DIP switch
page 4 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Figure 4: BNIC DIP switch addresses
page 5 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Jumpers
Jumper P1 sets the Autoforward mode to determine how data traffic is handled before the BNIC CPU is online.
Setting 1-2:
This is the recommended default setting. In this mode the BNIC does not allow traffic to be routed through the switch until the BNIC CPU is online and
running.
LED indicators
Table 3 lists the different LED indicators found on the BNIC that are troubleshooting aids.
Table 3: BNIC LED descriptions
LED Description Signification
Port A (LED 9)
Port B (LED 6)
Port C (LED 2)
Port D (LED 1)
Port Status LED OFF = No Connection
ON Steady = Non-active connection
ON Blinking = Active connection
X (LED 5)
Y (LED 4)
Z (LED 3)
Card Status LED Used for manufacturing and development only, not used for installed BNIC
Offline (LED 7) Offline Indication ON = Offline (not communicating with 4100ES Master Controller Card)
OFF = Normal Operation
Reset (LED 10) (see Figure 2 for
positioning)
Reset Indication ON = BNIC is in reset
Off = Normal Operation
Earth Fault (LED 8) Earth Fault Indication on Port A ON = Earth Fault detected on Port A
OFF = No Earth Fault detected
Figure 5: LED positioning
page 6 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Mounting the BNIC
The BNIC must be mounted in the master controller cabinet and can be placed in any open expansion bay slot.
Use the following steps as well as Figure 6 to properly install the BNIC:
Note: The card must be installed with the ports facing up.
1. Insert the Power Distribution Interface (PDI) connector on the back of the card into one of the bottom PDI connectors on the expansion bay.
2. Secure the card in place using the provided hardware.
Figure 6: Mounting the BNIC into the expansion bay (4100ES shown)
page 7 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Wiring
All Ethernet ports on the BNIC are auto-crossover (crossover cables are not required) and compatible with 802.3u, 100Base-TX type standard
RJ45 type connections.
WARNING: Miswiring the BNIC can result in limited network connectivity for users attempting to log into the network.
Note: Cable requirements:
• Category 5 (CAT5) cable or greater is required for 100Mbit operation. Using lower grade (i.e. Category 3) cables can result in slower link speeds
or shorter distances which may affect the performance of your connection.
• The maximum distance from the BNIC to the next Ethernet termination (router, switch etc.) is 328 ft (100 m) with CAT5 cable.
• Cables are to be in conformance with TIA/EIA-568-B standard.
Note: Not supported:
• Style 7 connection. Only one path through the building network should exist.
Note: Multiple connections to separate networks are permissible (i.e., dedicated network and building network).
• Power over Ethernet (PoE).
Note: External connections:
• BNIC Port A provides Earth Detection for optional external network connection needs, see Important notes in the Figure 7 BNIC Wiring
Diagram.
• BNIC Port B connects to the building network.
Note: Panel Connections:
• BNIC Port C connects to the CPU (Master Controller Card) Ethernet connection, except in ES Net configurations, where Port C connects to Port
D of the ES Net card.
Note: This connection is required to enable communication between the BNIC and the CPU.
• BNIC Port D connects to the display assembly at the Ethernet connection board (566-848).
Important: Port A is a special application connection that provides earth detection by placing a low DC voltage signal on the port. It is NOT
COMPATIBLE with PoE (Power over Ethernet) connections and should NEVER be connected to a PoE port!
Figure 7: BNIC wiring diagram
page 8 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Configuring a Node with ES Net and BNIC Card
Figure 8 shows a node with the connection to an external network through a BNIC card.
Figure 8: Node with BNIC
Configure the following options in the ES Net Card configuration dialog for each node in Table 5. The BNIC port options are non-configurable.
Table 4: ES Net Card configuration options
Configuration Connection
Port A Unused N/A
Port B Unused N/A
Port C CPU Connect to CPU Card Ethernet Port
Port D Panel Net Connect to BNIC port "C"
Media Module 1 Single Mode Fiber N/A
Port E Fire Network Connect to Neighbor Node
Port F Fire Network Connect to Neighbor Node
Media Module 2 Unused N/A
Port G Unused N/A
Port H Unused N/A
Table 5: Node with BNIC configuration and connections
Configuration Connection
Port A External Network To building network
Port B External Network N/A
Port C CPU Connect to ES Net Card Port "D"
Port D Service Port Connect to Front Panel's Service Port
As the ES Net card is used to bridge the BNIC and the CPU card, you must configure Port D of the ES Net as Panel Net so that the connection is
supervised.
Panel Net Ports
Use the Panel Net port type to connect Ethernet slave cards, such as a BNIC, to the CPU card. This port type provides supervision of the link and
declares a port trouble if the link goes down.
page 9 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Programming the BNIC
Software requirements
In order to properly program the BNIC the computer must use FACP System Firmware version 1.01 or later. Consult the ES Panel Programmer’s Manual
(574-849) for more information.
Adding the BNIC to the programmer
Note: These instructions detail adding the 4100-6047 BNIC to the Programmer for a 4100ES. Follow the same procedure for adding the 4010-9914
BNIC to a 4010ES.
Follow these steps to add the BNIC to the programmer:
1. Start the programmer software.
2. Open an existing job or create a new one. If you create a new job you must change the box size to a 2 or 3 bay box.
3. Select the Hardware tab.
4. Click the Box icon.
5. Right-click the appropriate bay and select Add a Card. See Figure 9.
Figure 9: Adding a card
6. Select INTERFACE from the Category drop-down menu.
7. Select 4100-6047 - Building Interface Network Card from the Type drop-down menu.
8. Click OK.
Figure 10: Select the BNIC
Figure 11: Adding the BNIC
page 10 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

Configuring the BNIC
Follow these steps to configure the BNIC:
1. Right-click on the BNIC icon in the Hardware tree view.
Figure 12: Accessing the card properties
2. Select and open the Properties option. This will open the BNIC window.
3. Configure the Card Properties tab by setting:
- The Card Address
- The Card Custom Label
- The Card Alternate Custom Label
- The Unit
- The Box
- The Bay
- The Location
Note: For additional information on card properties consult the ES Programmer Manual.
Figure 13: Card properties tab
4. Select the BNIC IP Settings tab.
5. Configure the BNIC IP Settings tab by setting:
- The IP Address.
• Use the Dynamic Host Configuration Protocol (DHCP) option to have the Building Network automatically assign an IP address
to the card.
• Select the Use the following address option if you want to set the IP address manually and enter a Static IP address.
- For Static IP Addresses:
• If you are using a Customer LAN, refer to the worksheet information on Before You Approach Your MIS/IT Department for
customer provided addresses.
page 11 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

• If you are using a Proprietary Fire Alarm LAN, the Recommended Convention for the Subnet is 255.255.0.0.
Important:
•- To avoid network conflicts, do not use 192.168.100.1 for an IP Address when assigning BNICs.
•- The mDNS works within the same broadcast domain. Typically all devices on a single subnet are on the same
broadcast domain and are reachable via IP broadcast. The facility MIS/IT department will provide guidance on use of
mDNS.
- The Domain Name Server (DNS).
• By default, the Obtain DNS server address automatically option is selected. It is recommended to leave this setting selected.
• A domain server IP address can be entered manually in the Use the following DNS server address box.
Figure 14: BNIC IP settings tab
- Multicast Domain Name Server (mDNS).
• The mDNS works within the same broadcast domain. Typically all devices on a single subnet are on the same broadcast domain
and are reachable via IP broadcast. The facility MIS/IT department will provide guidance on use of mDNS.
• A device that supports mDNS advertises its name and available services using IP broadcasts (multicast address 224.0.0.251). An
mDNS client (the Programmer) can make a request for a device with a particular service to advertise itself. This enables the user to
locate devices. If you do not enable this feature the BNIC will not Advertise itself.
- mDNS Modes:
• NORMAL (default): The BNIC will periodically advertise its name and service for 2 minutes after startup (unsolicited advertisement).
• QUIET: The BNIC will advertise its name and service once at startup. QUIET mode may be used at the request of an IT department
that does not want unsolicited traffic on the network.
6. Select the BNIC Network Ports tab. Ensure that the settings are the same as those featured in Figure 15.
Figure 15: BNIC network tab
7. Click on the OK button at the bottom of the BNIC window to save the BNIC settings.
page 12 579-949 Rev. D
4100-6047 and 4010-9914 Building Network Interface Card Installation and Programming Manual

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

Before You Approach Your MIS/IT Department
For DNS or Fixed IP configuration:
Find the MAC address that is printed on a label located near the center of the board. Carefully record this number below because your MIS/IT
department will need this information to configure the BNIC properly on your network. The format of the MAC address will look something similar to
00:08:BD:1C:48:1A.
Record the BNIC MAC address:
For DNS:
The BNIC will not operate properly if the DNS name does not match the Building Network Panel Name as found under the CPU Ethernet tab in the job
configuration.
Record the suggested name for the BNIC host. This must be retrieved from the BNIC card editor of the ES Programmer (BNIC IP Settings tab). If the
suggested name cannot be used, the Building Network Panel Name must be changed in the job configuration for proper operation.
Record the suggested DNS name:
Minimum Parameters Required to connect the BNIC
The IT/MIS Department must complete this section
Now you may take this worksheet to your MIS/IT department for assistance in obtaining the parameters required for the BNIC to operate properly on
your local network.
WARNING: Do not attempt to connect the BNIC using random entries; serious consequences may result. You can inadvertently affect other
computers and networked devices on your network.
Fixed IP:
DHCP/DNS:
If the assigned name does not match the suggested name:
The MIS/IT assigned parameters must be added to the job configuration for the FACP, using the BNIC card editor of the ES Programmer. Once the
configuration is updated and downloaded to the panel, the BNIC can be connected to the building network.
579-949 Rev. D
© 2020 Johnson Controls. All rights reserved. All specifications and other information shown were current as of document revision and are subject to change without notice. Additional listings may be applicable, contact your local Simplex®
product supplier for the latest status. Listings and approvals under Simplex Time Recorder Co. Simplex, and the product names listed in this material are marks and/or registered marks. Unauthorized use is strictly prohibited. NFPA 72 and
National Fire Alarm Code are registered trademarks of the National Fire Protection Association (NFPA).