1. Team Members: ECE- Wes Williams, Will Steiden, Josh Howard, Alan Jimenez Sponsor: Brad Luyster Honeywell Network Traffic Generator

2. Honeywell Life Safety is a division of Honeywell International which designs and manufactures fire systems, sensors, and other safety devices.  The Louisville Design Center (LDC) works with different fire system brands to manufacture network devices for large scale fire systems.  These networks consist of Fire Alarm Control Panels (FACPs), each of which is capable of managing thousands of heat/smoke sensors and I/O modules. BACKGROUND INFORMATION

3. FIRE SYSTEMS OVERVIEW

4.  The LDC needs to test the fire systems extensively because of safety requirements.  Fire Panels are very expensive and buying them for testing purposes is inefficient. PROBLEM

5.  Build an FACP emulator so testing can be done without high costs  Emulator will inject large amounts of traffic into the Noti-Fire network (i.e. alarm events) PROPOSED SOLUTION

6.  The user will configure the emulator and schedule events from a PC application using a graphical user interface.  Must be able to communicate with the Centralized Monitoring Station  Must be able to generate the same type of traffic that a Fire Alarm Control Panel would generate EMULATOR REQUIREMENTS

7. Noti-Fire Network Noti-Fire Gateway Centralized Monitoring Station NFN Kernel Alarm Packet Generator MAJOR COMPONENTS Fire Alarm Control Panel Processing Unit Addressable Monitor Module Signaling Line Circuit Network Communications Module

8. SYSTEM DIAGRAM

9. FIRE ALARM CONTROL PANEL

10.  Manages inputs and Controls Outputs  Capable of managing thousands of heat/smoke sensors and I/O modules.  Communicates device events and internal status over the NFN.

11. PROCESSING UNIT

12.  The processing unit is able to monitor and control up to 3,180 detectors and beacons. The processing unit is also used to silence alarms. The processing unit communicates with other FACPs and the Centralized Monitoring Station via NCMs.  It is capable of polling 318 addressable devices on each SLC in less than two seconds and can activate up to 159 output devices in less than five seconds.  Although, an operational FACP is not required for the design of the FACP emulator, the FACP is useful in testing and diagnostics of the network before testing the FACP emulator. PROCESSING UNIT

13. ADDRESABLE MONITOR MODULE

14.  The Addressable Monitor Module is an addressable device that allows non-addressable devices such as switches and dry- contacts to be attached to the Processing Unit via the SLC.  Up to 159 Addressable Monitoring Modules may be connected to a single FACP. ADDRESABLE MONITOR MODULE

15. SIGNALING LINE CIRCUIT

16.  Daisy-Chain connection of different intelligent devices on a Fire Safety Network  Is constantly polled by the FACP processing unit to update status and check for alarms  Up to 159 detectors and 159 modules can be put on one SLC  Up to 10 SLCs on one FACP SIGNALING LINE CIRCUIT

17. NETWORK COMMUNICATION MODULE

18.  The Network Communication Module (NCM) is simply an LDC designed Printed Circuit Board (PCB) that is used between fire panels and the Noti-Fire Network.  Communicates with the FACP (or emulator) through serial (RS- 232) and communicates with the NFN through Unshielded Twisted Pair (UTP)  The Network Traffic Generator will be used to configure and send events across the network using the NFN Kernel. This will be the main tool in emulating the FACP. NETWORK COMMUNICATION MODULE

19. NOTI-FIRE NETWORK

20.  Unshielded Twisted Pair as communication medium  ARCNET based network that uses LDC Network Communication Modules (NCM) as nodes  Events from a FACP are sent to its NCM, which then sends it over the Noti-Fire Network  Events end up at the Centralized Monitoring Station which records logs of alarms and trouble events. NOTI-FIRE NETWORK

21. NOTI-FIRE NETWORK GATEWAY

22.  The Noti-Fire Gateway is a network card that allows users to view the status of FACPs via a web interface  The NFN Gateway can be configured to automatically send event information via email to a select group of users  The network card was designed at the LDC and it is proprietary hardware. NOTI-FIRE NETWORK GATEWAY

23. CENTRALIZED MONITORING STATION

24.  The Centralized Monitoring Station monitors alarm events that are passed over the NFN Network into the NFN Gateway via Ethernet 10bT  Located in security personnel office CENTRALIZED MONITORING STATION

25.  The NFN Kernel is written in C++ and handles the transmitting and receiving of events on the Alarm Packet Generator, NCM and NFN Gateway. This is done by setting up the presentation and transportation layers.  The NFN Kernel will be used to create and dispatch events according to the NFN Packet Structure  The NFN Kernel is used by the Network Traffic Generator that allows it to create a presentation object, transport object and other object classes needed to generate and send an event NFN KERNEL

26. Alarm Packet Generator

27.  The Alarm Packet Generator is the PC on which the NFN Kernel and Network Traffic Generator run  The Alarm Packet Generator interfaces with the Noti-Fire Network via an RS-232 connected to an NCM ALARM PACKET GENERATOR

28.  Modified ARCNET (Unshielded Twisted Pair)  RS-232  Ethernet  Power Converter  Graphical User Interface SYSTEM INTERFACES

29.  Made up of different nodes (i.e. NCMs) all connected by unshielded twisted pair (UTP)  Deterministic token ring passing protocol  Transmission Rate: 2.5 Mbs  Packet Size: 1 to 507 bytes  Network Size: Up to 255 nodes ARCNET

30. PACKET ARCHITECTURE

31. NETWORK DIAGRAM

32.  RS-232 will be the means of communication between the alarm packet generator and the NCM. RS-232

33.  The centralized monitoring station will interface with the NFN Gateway via the native 10/100 base T Ethernet interface. ETHERNET

34.  There will be an adapter converting power from 120V 60 Hz to 24V DC. There will also be a battery back-up for this system POWER

35.  The proposed user interface will run on the alarm packet generator and allow the user to schedule events. The user will be able to select the number of Signaling Line Circuits (SLCs), the serial port, and the scale of events the user wants to generate. GRAPHICAL USER INTERFACE

36. SOFTWARE DIAGRAM

37.  The Network Traffic Generator is the application running on the NFN Kernel to send alarm packets across the network  Written in C++ in the Visual Studio environment.  Heavily dependent on NFN Kernel NETWORK TRAFFIC GENERATOR

38. GUI CONFIGURATION TOOL

39.  Selectable Com port  Scale of events may be changed to allow anywhere from a single alarm point to every alarm point possible to be activated.  Logs alarm points to an Microsoft Excel sheet for analysis GUI CONFIGURATION TOOL

40.  Configure Network Traffic Generator to send limited number of known events  Receive events on the Centralized Monitoring Station  Verify that all event messages have been successfully transmitted TESTING

41.  Link the GUI Configuration Tool with the operational software  Expand the GUI to allow configuration of node address, alarm address and time NEXT PHASE

42. QUESTIONS ? Honeywell Network Traffic Generator