1. NOTIFIRE
NETWORK

2. Overview

3. NFN Network Description
Peer-to-peer network
Minimum hardware requirement:
2 nodes connected via wire or fiber
Supports 103 Nodes with a maximum capacity of 324,360 points.
It will support 54 nodes maximum when it is set up to provide live paging from a DVC node.
Each node requires a unique address and it communicates with other nodes via a network interface board.

4. 8th Edition Nodes 9th Edition Nodes AFP-200 / AFP-300 / AFP-400
AM2020, AFP-1010
NFS-3030
NFS-640
Network Control Annunciator (NCA)
Network Control Station (NCS 2.0 to 4.x)
DVC/DVC-EM
NCA-2
NFS2-3030
NFS2-640
NFS-320
Network Control Station (NCS 5.0 to 5.9)
ONYXWorks

5. Network
Hardware

6. Network Interface Boards
The physical interface which connects nodes forming a network:
NAM-232W, NAM-232F
AFP-200/300/400
SIB-NET with MIB-W, MIB-F, MIB-WF
AFP-1010/AM-2020
NCM-W, NCM-F
NFS2-3030, NFS-3030, NFS2-640, NFS-640, NFS-320, NCA-2, NCA, DVC
NCS-NCW, NCS-NCF
NFN-GW-PC-W, NFN-GW-PC-F
RPT-W, RPT-F, RPT-WF

7. Network Communications Module (NCM)
Connects to the NUP (Notifier Universal Protocol) port on Onyx Fire Alarm Panels, NCA, NCA-2 and DVC.
Mounts on a CHS-M2, CHS-M3, CHS-4, or CHS-4L
Each NCM on the network MUST be running the same version.

8. NCM-W

9. Channel A & B connections Network connection Ports (NUP)
NCM-F
Network connection Ports (NUP)
Diagnostic LEDs
Not Used

10. NFN-GW-PC-W
NFN-GW-PC-F

11. Repeaters (RPT)
Repeaters (RPT) regenerate data signals between network nodes, extending communication distances.
RPT-W two twisted pair wire ports
RPT-F two fiber optic cable ports
RPT-WF one twisted pair wire port and one fiber optic cable port.

12. RPT-W RPT-F RPT-WF Ground fault detection feed-through
Threshold Selection for Port A and Port B
Port A and Port B
Port B
24V
RPT-W
RPT-F
Port A
Threshold Selection for Port A
RPT-WF

13. System Topology

14. Network Configurations
NFN is capable of communicating using two types of wiring styles, style 4 and 7.
Style 4
A single open, wire-to-wire short, wire-to-wire short and open, wire-to-wire short and ground, or open and ground results in fragmentation of the network
Style 7
A single open, wire-to-wire short, wire-to-wire short and open, wire-to-wire short and ground, or open and ground will not result in fragmentation of the network.

15. Polarity does not matter on network wiring.
Wire Connections
Polarity does not matter on network wiring.
MUST USE E B A E B A

16. Wire Connections
WRONG

17. Point-To-Point Configuration
A point-to-point wiring configuration is defined as a twisted-pair segment with ONLY two nodes/repeaters attached to it.
Terminating resistors are required at the beginning and the end of every segment and are built into each MIB/RPT/NAM232.
Termination is done with slide switches on the NCM/NCS-NCW/NFN-GW-PC-W.
Terminate
Terminate
Terminate

18. Bus Configuration
A bus wiring configuration is defined as a twisted pair network with more than two nodes.
Termination is only required on the FIRST and LAST nodes of the bus. Remove termination on the middle nodes.
TERMINATE
Remove Termination

19. Combination Network BUS Science Building Gymnasium Point-to-Point
24V
Admin Building
Point-to-Point
Cafeteria

20. Point-To-Point Configuration
Wiring a Noti-Fire-Net in Style 7 point-to-point.

21. Fiber Connections
Rx B
Tx B
Rx A
Tx A
Rx B
Tx B
Rx A
Tx A

22. Mixing Wire and Fiber
RPT-WF
NCM-W
NCM-F
24V

23. Network Wiring Requirements
When designing the wiring layout of a NOTI-FIRE-NET system, the following limitations must be considered:
The length of each individual twisted pair or fiber optic network communication circuit segment is limited.
The system path length is limited.

24. Network Wiring Requirements1 2 3 B B A A B A B A
Network Node or repeater
Network Node or repeater
Network Node
Network Node
Point-to-point segments 1, 2, and 3.
Each segment is connected to only two nodes/repeaters and can not exceed the limits of the wire used.

25. Limit on System Path Length1
End of Network
End of Network 4 B A B A 2
Network
Node
Network
Node B A B A B A B A
Network Node or repeater
Network Node or repeater
Network Node or repeater
Network Node or repeater 3
System Path Length = Sum of the lengths of Segments 1, 2, 3, and 4.

26. Overall Distance (Feet) 450,000 400,000 350,000 300,000 250,000
200,000
150,000
100,000
50,000
Total Number of Nodes/Repeaters

27. Limit for Fiber Optic Circuits
The attenuation of cabling between two nodes/repeaters is limited by cable choice.
Fiber optic circuits are point-to-point only, NO Star or Bussing is allowed.
Use repeaters (RPT-F) to extend segments.
Attenuation limits for multimode fiber:
62.5/125µm cable = 8dB limit
50/125µm cable = 4.2dB limit
Use industry standard equipment using a test wavelength of 850 nanometers to calculate dB loss.

28. Calculating approximate dB loss
Calculate loss due to cable
Look up the rated dB loss per foot from manufacturers specifications, typically .001 dB loss per foot of fiber.
Multiply this by the length of cable between 2 nodes/repeaters to determine loss due to cable. (Loss/ft x length in ft)
E.g. There is 1800 feet of fiber between two networked nodes.
(.001 x 1800) = 1.8 dB loss

29. Calculate loss due to connectors/splices
Look up the dB loss for each connector and splice.
Connectors = 0.3 dB loss for most adhesive/polish connectors.
0.75 dB loss for most prepolished/spliced connectors.
Splices = Typically 0.3 dB loss for each splice
Add all figures to determine loss due to connectors/splices.
E.g. There are two prepolished connectors and one splice between the networked nodes
( ) = 1.8 dB loss

30. 3. Calculate total loss – Add the attenuation factors obtained in steps 1 & 2. This will provide an approximate attenuation total, which should be 8 dB or less for the standard NFN.
Step 1 (.001 x 1800) = dB loss
Step 2 ( ) = dB loss
Step 3 Approximate total loss = dB

31. Additional Equipment

32. Noti-Fire-Net Web Server (NWS-3)
USB “A” Host (J13)
USB “B” Device (J14)
Ethernet Connector (J8)
NUP A Serial Data Connector (J6)
Not Used (J7)
Not Used
TB1:
- 24 V Out
+ 24 V Out
- 24 V In
+ 24 V In

33. Noti-Fire-Net Web Server (NWS-3)
Web-based device that acts as an HTML server that allows remote viewing of the NFN network (including High Speed NFN Networks) via the Internet or an Intranet.
Communicates with NFN version 5.0 and later.
Interfaces to the Internet/Intranet using an IP-based wire Ethernet connection.
Can also be used as a web-based communication between the NFN network and VeriFire Tools.
Requires that at least one node on the NFN network be an ONYX series panel. It does not run on an NFN network with no ONYX series panels.
Is not a primary annunciator, it is ancillary in nature.
No NCM-W/F PC board is required when it connects directly to a supported Notifier panel in a stand alone configuration.

34. NWS-3 Features Sends up to 50 E-mails in response to any system event.
Supports Microsoft Internet Explorer 6.0 and above.
Built-in password security and user access record.
Up to 128 user accounts supported.
Multiple users can access the NWS-3 at the same time.
Events Tab displays 9 pieces of information:
Actual Time, Node, Point, Status, Trouble Status, Device Type, Description, Zone, and Zone Label.

35. NWS-3 Single Panel Application
Internet/Intranet
PC Browser Interface
Supported Notifier FACP with Web Server Assembly

36. NWS-3 Network Application
PC Browser Interface
CAB 3/4 Cabinet with NWS-3 Assembly and HS-NCM W/SF/MF or NCM W/F Board
Internet/Intranet
NFN Network
HS-NCM W/SF/MF or
NCM W/F
HS-NCM W/SF/MF or
NCM W/F
Supported FACP
Supported FACP

37. NFN Gateway 3 USB “A” Host (J13) USB “B” Device (J14)
Ethernet Connector (J8)
NUP A Serial Data Connector (J6)
Not Used (J7)
Not Used
TB1:
- 24 V Out
+ 24 V Out
- 24 V In
+ 24 V In

38. NFN Gateway 3 Embedded
Serves as a bridge between an ONYXWorks Workstation and an NFN network (including High Speed NFN networks).
Uses the Workstation as the primary reporting station for the network.
Translates an NFN network’s panel and device data into data that can be interpreted by the OW Workstation software application.
Configured using the NFN Config Tool.
Communicates with any OW Workstation software application via an IP connection over Ethernet networks.

39. Single Panel Architecture
ONYXWorks Workstation
IP Connection over Ethernet
Embedded Gateway
NUP connection
FACP

40. NFN Network Architecture
IP Network
ONYXWorks Workstation
ONYXWorks Workstation
Embedded Gateway
HS-NCM W/SF/MF or
NCM W/F
NFN Network
FACP
FACP
FACP

41. BACnet Gateway 3 USB “A” Host (J13) USB “B” Device (J14)
Ethernet Connector (J8)
NUP A Serial Data Connector (J6)
Not Used (J7)
Not Used
TB1:
- 24 V Out
+ 24 V Out
- 24 V In
+ 24 V In

42. BACnet Gateway 3
Provides a communiation link between networks that use the BACnet communication protocol and Fire Alarm Control Panels resident on an NFN network or High Speed NFN network.
The NFN network communicates with the gateway through an HS-NCM-W/SF/MF or NCM-W/F that is on that NFN network or through a direct connection to a single Notifier panel.
Represents physical fire devices as BACnet objects and manages the object database.
As events occur the object properties are updated in real-time and messages are sent to the appropriate BACnet report destination (BACnet computer clients are computers with the graphical user interface workstation front end).
Configured using the BACnet GW-3 Configuration Tool, an offline programming utility that is included with the BACnet GW-3 assembly when ordered.
Multiple Gateways can be used for large networks (greater than 15 panels/15,000 objects).

43. Single Panel Architecture
IP Network
BACnet /IP Client with Workstation Front End
BACnet GW-3
NUP connection
FACP

44. NFN Network Architecture
IP Network
BACnet /IP Client with Workstation Front End
BACnet /IP Client with Workstation Front End
BACnet GW-3
NUP
HS-NCM W/SF/MF or
NCM W/F
NFN Network
FACP
FACP
FACP

45. Modbus Gateway USB “A” Host (J13) USB “B” Device (J14)
Ethernet Connector (J8)
NUP A Serial Data Connector (J6)
Not Used (J7)
Not Used
TB1:
- 24 V Out
+ 24 V Out
- 24 V In
+ 24 V In

46. Modbus Gateway
The Modbus Gateway provides a communication link between networks that use the Modbus/TCP communication protocol and Fire Alarm Control Panels (FACPs) resident on an NFN network.
Compatible with standard and high speed NOTI-FIRE-NET.
Monitors four (4) compatible NFN or HS-NFN nodes not including the Modbus Gateway node itself.
NFS-320, NFS-640, NFS2-640, NFS-3030, NFS2-3030
Provides data such as event type, active/inactive, enabled/disabled, acknowledged/unacknowledged, device type, analog value (4-20ma modules only) and system troubles.
Support reads of up to 100 registers at a time. Analog values
can be read 10 registers at a time.
Reduce configuration time by auto-discovering and mapping
points.
UL listed as an ancillary device for monitor only.
Optionally Supports Acknowledge, Silence, Reset (non-UL)
Supports one Master

47. Single Panel Application
IP Network
Modbus Client
Modbus GW
NUP
FACP

48. Modbus GW on NFN IP Network Modbus Client Modbus GW HS-NCM W/SF/MF or
NUP
HS-NCM W/SF/MF or
NCM W/F
NFN Network
FACP
FACP
FACP

49. Receivers Gateway
Acts as a bridge between the supported digital alarm receivers and the ONYXWorks Network.
Processes information coming from a connected receiver and passes the information to Onyx Works components.
The Workstation annunciates events from panels to receivers using a DACT.
Receivers connect to the ONYXWorks Workstation via any unused COM port on the PC or via an optional Digiboard 8-port COM expansion board.
Up to 32 nodes connected to the BCI

50. Supported Receivers and Protocols
Ademco 685
Radionics D6600
Silent Knight 9500/9800
Teldat VisorALARM
Supported Formats
Ademco Contact ID
Internal High Speed (685/SK receivers)
D6600 Internal

51. Receivers Network Applications
ONYXWorks Workstation OR
FACP
Dialer IP

52. Intel 2.16 GHz Duo Core Processor
Two 160 GB Hard Drives
3.2 GB Video RAM
DVD-ROM / CD-RW Drive
Ethernet Card
19”Flatscreen LCD Monitor or
19” wide screen touch screen monitor
Windows XP Professional (SP2) or
Windows 7 Operating System

53. Workstation
Graphical monitoring of events and device states (up to 6 different states)
Operator security levels allow functional restriction for multiple operators
Fully customizable floor plans (.WMF, .BMP, JPEG and GIF)
Complete history of events with a variety of filtering and exporting capabilities
Supports the following languages: Arabic, French, Korean, Portuguese, Spanish, and Chinese (Traditional and simplified)
Compatible with Standard and High Speed NFN
Keep floor plans 200k or smaller
Keep max of 50 devices per screen, you can have more but slows down system

54. First Vision

55. First Vision
FIRSTVISIONTM uses a graphical user interface (GUI) approach to life safety monitoring for your building or campus.
The GUI's display method enables an authorized event responder (e.g. firefighter) to view an event in the context of the building's floor layouts.
This allows planning of routes and methods for responding to the event.
FIRSTVISION should be installed in the authorized event responder’s preferred building entry location.
Configured using the First Vision Configuration Tool.

56. First Vision
FIRSTVISION only supports SLC loop modules and devices. Only device or module events that use formats of LxxDyyy and LxxMyyy (respectively) that are reported by the types of devices listed below; are processed and annunciated by FIRSTVISION:
Fire Alarms
Supervisory
Medical
Security
Can simultaneously process up to 3,000 events.
Compatible with NFN GW version 3.11
Compatible with Rapid Eye CCTV Gateway

57. Sample First Vision Network
First Vision with CCTV Gateway
Ethernet (TCP/IP) Network
Optional Digital Video Network
NFN Gateway PC
Embedded Gateway OR
NFN Network
FACP
FACP
FACP

58. First Vision Campus View

59. First Vision Building View

60. First Vision Rapid Eye CCTV

61. First Vision

62. ? Blah,Blah,Blah, Blah,Blah,Blah. What was he talking about ?
Z z z z
z z z z
z z
Questions,
Comments,
Ideas ?
Basic Fire Alarm Technology