Installation and Programming Manual Part: Building Network Interface Card Product: 4100ES

Transcription

1 Installation and Programming Manual Part: Building Network Interface Card Product: 4100ES Cautions and Warnings 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 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. Introduction The Building Network Interface Card (BNIC) allows the connection of a 4100ES 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. 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 ( ) installed in your system. If you are using an older 4100U CPU Card, upgrade using the upgrade kit. Ethernet Ethernet Authorized Service PC Facility LAN BNIC Figure 1. BNIC Connection Diagram 4100ES Fire Alarm Control Panel In this Publication This publication discusses the following topics: Topic Page Overview 2 Card Specifications and Layout 3 Configuration 4 Mounting the Card 6 Wiring and Cable Requirements 7 Programming the BNIC 8 Accessing the FACP through the BNIC 12 Building Network Interface Card MIS/IT Configuration Worksheet SimplexGrinnell LP. All rights reserved. Specifications and other information shown were current as of publication and are subject to change without notice. Simplex and the Simplex logo are trademarks of Tyco International Ltd. and its affiliates and are used under license Rev. A

2 Overview BNIC Overview 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. Package Contents This package includes: One BNIC Hardware to secure the BNIC in the Expansion Bay Two 5ft (1.5 m) Ethernet cables ( ) FACP Requirements The FACP must meet the following requirements for the card to function properly: It must use the 4100ES Master Controller Card It must use ES FACP System Firmware version 1.01 or later 2

3 Card Specifications and Layout Card Specifications Table 1. Card Specifications Card Size: 4 x 11¼ inches (102 x 286 mm) /Dual Block Module Earth Fault Detection (Port A only): 10 K Ohm Max direct current connection to earth Operating Conditions: Operating Temperature Range 32 o F o F (0 o C-49 o C ) Operating Humidity Range Up to 93% relative humidity at 90 o F (32 o C ) Power Requirements: Operating Voltage Maximum Current over Operating Range Nominal 24 VDC from PDI 291 ma (maximum over range) BNIC Ethernet Port Label EXTERNAL NETWORK PANEL CONNECTION Connections to External Networks Connection to NXP CPU Card Connection to Panel Download Port EARTH DETECT BUILDING CPU DISPLAY Port A Port B Port C Port D (Placed over the RJ-45 jacks) Port status LEDs Status LEDs eslave Address Switch, SW1 Communication Loss LED Earth Fault LED Reset LED Auto Forward Jumper MAC Address Label Future Expansion Port PDI Connector (bottom side) Serial Number MAC address Chip Socket Figure 2. BNIC Layout 3

4 Configuration 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 5). Table 2. BNIC DIP Switch functions Switch Position Function Figure SW1-1 SW1-2 through SW1-8 ON OFF ON OFF Sets the card to online and allows the card to operate normally. Sets the card offline which stops all communication to the FACP. Set the BNIC eslave address. Refer to Table 3 for a complete list of switch settings for all possible card addresses. Table 3. BNIC DIP Switch Addresses DIP Switches SW1-2 through SW1-8 set the Card Address Position 1 of SW1 is the online / offline setting of the card and must be set to ON Figure 3. BNIC DIP Switch Address SW 1-2 SW 1-3 SW 1-4 SW 1-5 SW 1-6 SW 1-7 SW 1-8 Address SW 1-2 SW 1-3 SW 1-4 SW 1-5 SW 1-6 SW 1-7 SW ON ON ON ON ON ON OFF 61 ON OFF OFF OFF OFF ON OFF 2 ON ON ON ON ON OFF ON 62 ON OFF OFF OFF OFF OFF ON 3 ON ON ON ON ON OFF OFF 63 ON OFF OFF OFF OFF OFF OFF 4 ON ON ON ON OFF ON ON 64 OFF ON ON ON ON ON ON 5 ON ON ON ON OFF ON OFF 65 OFF ON ON ON ON ON OFF 6 ON ON ON ON OFF OFF ON 66 OFF ON ON ON ON OFF ON 7 ON ON ON ON OFF OFF OFF 67 OFF ON ON ON ON OFF OFF 8 ON ON ON OFF ON ON ON 68 OFF ON ON ON OFF ON ON 9 ON ON ON OFF ON ON OFF 69 OFF ON ON ON OFF ON OFF 10 ON ON ON OFF ON OFF ON 70 OFF ON ON ON OFF OFF ON 11 ON ON ON OFF ON OFF OFF 71 OFF ON ON ON OFF OFF OFF 12 ON ON ON OFF OFF ON ON 72 OFF ON ON OFF ON ON ON 13 ON ON ON OFF OFF ON OFF 73 OFF ON ON OFF ON ON OFF 14 ON ON ON OFF OFF OFF ON 74 OFF ON ON OFF ON OFF ON 15 ON ON ON OFF OFF OFF OFF 75 OFF ON ON OFF ON OFF OFF 16 ON ON OFF ON ON ON ON 76 OFF ON ON OFF OFF ON ON 17 ON ON OFF ON ON ON OFF 77 OFF ON ON OFF OFF ON OFF 18 ON ON OFF ON ON OFF ON 78 OFF ON ON OFF OFF OFF ON 19 ON ON OFF ON ON OFF OFF 79 OFF ON ON OFF OFF OFF OFF 20 ON ON OFF ON OFF ON ON 80 OFF ON OFF ON ON ON ON 21 ON ON OFF ON OFF ON OFF 81 OFF ON OFF ON ON ON OFF 22 ON ON OFF ON OFF OFF ON 82 OFF ON OFF ON ON OFF ON 23 ON ON OFF ON OFF OFF OFF 83 OFF ON OFF ON ON OFF OFF 24 ON ON OFF OFF ON ON ON 84 OFF ON OFF ON OFF ON ON 25 ON ON OFF OFF ON ON OFF 85 OFF ON OFF ON OFF ON OFF 26 ON ON OFF OFF ON OFF ON 86 OFF ON OFF ON OFF OFF ON 27 ON ON OFF OFF ON OFF OFF 87 OFF ON OFF ON OFF OFF OFF 28 ON ON OFF OFF OFF ON ON 88 OFF ON OFF OFF ON ON ON 29 ON ON OFF OFF OFF ON OFF 89 OFF ON OFF OFF ON ON OFF 30 ON ON OFF OFF OFF OFF ON 90 OFF ON OFF OFF ON OFF ON 31 ON ON OFF OFF OFF OFF OFF 91 OFF ON OFF OFF ON OFF OFF 32 ON OFF ON ON ON ON ON 92 OFF ON OFF OFF OFF ON ON 33 ON OFF ON ON ON ON OFF 93 OFF ON OFF OFF OFF ON OFF 34 ON OFF ON ON ON OFF ON 94 OFF ON OFF OFF OFF OFF ON 35 ON OFF ON ON ON OFF OFF 95 OFF ON OFF OFF OFF OFF OFF 36 ON OFF ON ON OFF ON ON 96 OFF OFF ON ON ON ON ON 37 ON OFF ON ON OFF ON OFF 97 OFF OFF ON ON ON ON OFF 38 ON OFF ON ON OFF OFF ON 98 OFF OFF ON ON ON OFF ON 39 ON OFF ON ON OFF OFF OFF 99 OFF OFF ON ON ON OFF OFF 40 ON OFF ON OFF ON ON ON 100 OFF OFF ON ON OFF ON ON 41 ON OFF ON OFF ON ON OFF 101 OFF OFF ON ON OFF ON OFF 42 ON OFF ON OFF ON OFF ON 102 OFF OFF ON ON OFF OFF ON 43 ON OFF ON OFF ON OFF OFF 103 OFF OFF ON ON OFF OFF OFF 44 ON OFF ON OFF OFF ON ON 104 OFF OFF ON OFF ON ON ON 45 ON OFF ON OFF OFF ON OFF 105 OFF OFF ON OFF ON ON OFF 46 ON OFF ON OFF OFF OFF ON 106 OFF OFF ON OFF ON OFF ON 47 ON OFF ON OFF OFF OFF OFF 107 OFF OFF ON OFF ON OFF OFF 48 ON OFF OFF ON ON ON ON 108 OFF OFF ON OFF OFF ON ON 49 ON OFF OFF ON ON ON OFF 109 OFF OFF ON OFF OFF ON OFF 50 ON OFF OFF ON ON OFF ON 110 OFF OFF ON OFF OFF OFF ON 51 ON OFF OFF ON ON OFF OFF 111 OFF OFF ON OFF OFF OFF OFF 52 ON OFF OFF ON OFF ON ON 112 OFF OFF OFF ON ON ON ON 53 ON OFF OFF ON OFF ON OFF 113 OFF OFF OFF ON ON ON OFF 54 ON OFF OFF ON OFF OFF ON 114 OFF OFF OFF ON ON OFF ON 55 ON OFF OFF ON OFF OFF OFF 115 OFF OFF OFF ON ON OFF OFF 56 ON OFF OFF OFF ON ON ON 116 OFF OFF OFF ON OFF ON ON 57 ON OFF OFF OFF ON ON OFF 117 OFF OFF OFF ON OFF ON OFF 58 ON OFF OFF OFF ON OFF ON 118 OFF OFF OFF ON OFF OFF ON 59 ON OFF OFF OFF ON OFF OFF 119 OFF OFF OFF ON OFF OFF OFF 60 ON OFF OFF OFF OFF ON ON 4

5 Configuration (continued) 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 4 lists the different LED indicators found on the BNIC that are troubleshooting aids. Table 4. BNIC LED Descriptions LED Description Signification Port A (LED 9) Port B (LED 6) OFF = No Connection Port Status LED ON Steady = Non-active connection Port C (LED 2) ON Blinking = Active connection Port D (LED 1) X (LED 5) Used for manufacturing and development only, not Y (LED 4) Card Status LED used for installed BNIC Z (LED 3) Offline (LED 7) ON = Offline (not communicating with 4100ES Offline Indication Master Controller Card) OFF = Normal Operation Reset (LED 10) (see Figure 2 for positioning) Earth Fault (LED 8) Reset Indication Earth Fault Indication on Port A ON = BNIC is in reset Off = Normal Operation ON = Earth Fault detected on Port A OFF = No Earth Fault detected Port A Port B Port C Port D Port A LED9 LED7 LED8 Earth Fault Port A Port B LED6 LED5 LED4 Port C LED2 LED3 Port D LED1 Figure 4. LED positioning 5

6 Mounting the Card 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 5 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. EXPANSION BAY BNIC (Install with the ports at the top) SCREW HOLES WASHERS STANDOFFS SCREW RETAINERS SCREWS Figure 5. Mounting the BNIC into the Expansion Bay 6

7 Wiring and Cable Requirements 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. 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. 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). External Connections: 1. Port A provides Earth Detection for optional External Network connection needs, see Important Notes in the Figure 6 BNIC Wiring Diagram. 2. Port B connects to the Building Network. Panel Connections: 3. Port C connects to the CPU (Master Controller Card) Ethernet connection. Note: This connection is required to enable communication between the BNIC and the CPU. 4. Port D connects to the Display assembly at the Ethernet connection board ( ). 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! NXP Master Card Controller ( ) CPU Ethernet Port BAT ON BAT OFF SERVICE PORT DISPLAY Top View of the Ethernet Connection ( ) This connects the BNIC to the Display Assembly Building Network Optional Port (Port A) Important: Before disconnecting Ethernet cables from BNIC, identify and label the function of each cable to ensure connection to the correct Port. Port A Port B Port C Port D BNIC Figure 6. BNIC Wiring Diagram Connection to Display Assembly (Port D) Connection to NXP CPU Card (Port C) Connection to the Building Network (Port B) 7

8 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 ( ) for more information. Adding the BNIC to the Programmer 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 7. Figure 7. Adding a card 6. Select INTERFACE from the Category drop-down menu. 7. Select Building Interface Network Card from the Type drop-down menu. 8. Click OK. Figure 8. Select the BNIC 8

9 Programming the BNIC (continued) Adding the BNIC The BNIC appears in the Tree View. Figure 9. Adding the BNIC Configuring the BNIC Follow these steps to configure the BNIC: 1. Right click on the BNIC icon in the Hardware Tree View. Figure 10. 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 11. Card Properties tab Continued on next page 9

10 Programming the BNIC (continued) Configuring the BNIC 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 Page 12 for customer provided addresses If you are using a Proprietary Fire Alarm LAN, the Recommended Convention for the Subnet is Important: To avoid network conflicts, do not use 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 name can be entered manually in the Use the following DNS server address box. Figure 12. BNIC IP Settings tab 10

11 Programming the BNIC (continued) Configuring the BNIC 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 ). 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 13. Figure 13. BNIC Network tab 7. Click on the OK button at the bottom of the BNIC window to save the BNIC settings. 11

12 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 Network. 5. Click on Remote Panel. This will automatically launch Tera Term. Tera Term will connect using the IP information from the current job. Figure 14. Opening Tera Term 6. Proceed as you would if you were connected to the FACP through the service port. 12

13 Building Network Interface Card MIS/IT Configuration Worksheet Terms DHCP Dynamic Host Control Protocol DNS Domain Name System mdns Multicast Domain Name System MAC Media Access Control FACP Fire Alarm Control Panel RFC Request for Comments About the BNIC BNIC Installation Prerequisite 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. 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. 13

14 Building Network Interface Card MIS/IT Configuration Worksheet (continued) 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: : : : : : Ex:00:08:BD:IC:48:1A 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: Ex: Main_Lobby 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: MIS/IT Assigned BNIC Static IP Address:... Ex: MIS/IT Assigned BNIC Gateway:... Ex: MIS/IT Assigned BNIC Subnet Mask:... Ex: DHCP/DNS: If the assigned name does not match the suggested name: MIS/IT Assigned BNIC DNS Name: Ex:Fire_Panel_1 Check here if DNS Service Records are Enabled (required for panel discovery) 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. 14

15

16 Rev. A