CALL NOWCALL NOWCALL NOWGATEWAY SELECTORCALL NOWGATEWAY SELECTORLEARN MORELEARN MORE PROCEED TO CHECK-OUT SUBSCRIBE TO OUR RSS FEED SEARCH GATEWAYS NOW SEND MESSAGE NEWSLETTER | SUBSCRIBESUBMIT CALL NOWCALL NOWCALL NOWGATEWAY SELECTORCALL NOWGATEWAY SELECTORLEARN MORELEARN MORE PROCEED TO CHECK-OUT SUBSCRIBE TO OUR RSS FEED SEARCH GATEWAYS NOW SEND MESSAGE NEWSLETTER | SUBSCRIBESUBMIT

Notifier 3030 to BACnet IP

A FieldServer protocol gateway that provides data exchange between Notifier 3030 and BACnet IP. The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol. The NFS3030 Serial driver allo...
SKU:
FS-QS-1220-0489
Max Points
Max Points: 250, 500
Notifier 3030 to BACnet IP
This product is only available upon request Contact us now for a quote

Notifier 3030 to BACnet IP


Quickserver Gateway (Serial-Ethernet)

QuickServer is a high performance, fully configurable, cost effective Building and Industrial Automation gateway for integrators to easily interface devices to networks in commercial buildings and industrial plants.

System integrators world-wide have benefitted from the value of the powerful line of interoperability gateways offered by FieldServer. Now, QuickServer adds to that value by running the same robust FieldServer protocol conversion software on a highly cost effective platform backed by the experience, engineering expertise and proven technical support that integrators have come to expect from FieldServer.

QuickServer is available in two series. The FS-QS-10XX Series is preloaded with two BAS drivers (serial, Ethernet and/or LonWorks) from a choice of Modbus RTU, Modbus TCP, BACnet/IP®, BACnet MS/TP, LonWorks®, JCI Metasys® N2 and SNMP. Each QuickServer can handle up to 250 points.

The FS-QS-12XX Series QuickServer is available to use any Serial, Ethernet or LonWorks driver in the extensive FieldServer driver library. The FS-QS-12XX Series can handle up to 500 points and is available with a choice of RS-485, RS-232 or RS- 422 serial ports, KNX or M-Bus, in addition to Ethernet and LonWorks (optional).

Each QuickServer includes browser-based tools to make it easy to set-up QuickServer and perform diagnostics including determination of status, network settings, node information, map descriptors and more. The USB flash drive also includes the Discovery utility to determine what FieldServers are on a network.

Notifier NFS3030

The NFS3030 Serial driver allows the FieldServer to record data from Notifier Onyx Series NFS3030 Fire Panels over RS-232.

The FieldServer acts as a Passive Client receiving messages and recording the status of a Notifier 3030 Fire Alarm Panel. There is no active polling by this driver; the communications are one-way through the panel's printer port.

This driver is not capable of emulating a Notifier NFS3030 panel and the very limited Server functionality has only been implemented to facilitate FieldServer’s Quality Assurance program.

The purpose of this driver is to record the status of Fire Alarm System detectors and Modules in Data Arrays - one Data Array per loop. It is limited by the information that the Notifier NFS3030 unit sends in the form of text messages through its RS-232 printer port. The accuracy and timeliness of the data is therefore limited to the frequency of update messages that the Notifier Fire Panel issues.

Appendix A of the manual lists the Notifier message types supported by this driver and the effect on the status of points in the Data Array. The driver is capable of supporting the panel’s port supervision message if configured to do so.

The panel must output messages in English.

BACnet IP

The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol. The FieldServer can emulate either a Server or Client.

All information in a BACnet system is represented in terms of objects. The Object_Identifier is a 32-bit code that identifies the type of Object (also identified by the Object_Type Property) and its "Instance" number, which together uniquely identify the Object within its BACnet device. Theoretically, a BACnet device could have over four million Objects of a particular type. The Object_Name is a text string, which has a unique capability.

BACnet devices may broadcast queries for devices that contain Objects with a specific Object_Name. This can greatly simplify project setup.

BACnet requires one Device Object to be present in every BACnet device. The Device Object makes information about the device and its capabilities available to other devices on the networks. Before one BACnet device starts control-related communications with another, it needs to obtain some of the information presented by the other device's Device Object. Unlike other Objects, the Device Object's Instance number must be unique across the entire BACnet internetwork because it is used to uniquely identify the BACnet devices. It may be used to conveniently identify the BACnet device from other devices during installation.

Standard object types are used to hold real time data and other information. Each Object Type is referenced by a number, for example 0 represents an Analog Input. See Appendix D.1 for abbreviation list.

Each Object consists of a number of prescribed properties, the main property being the Present_Value. Objects are monitored and controlled through their properties.

The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.

Useful Links

Logos

Logo bacnet1
Logo BTL Bacnet Test Lab
Logo Notifier

Gateway Selector

Select your combination of protocols.
Protocol 1
Protocol 2

Contact Us

Contact us via phone (+1 866-383-1657) or leave a detailed message below for sales, support, or any other needs

*Required Field
I'd like to receive the newsletter. *Check email for confirmation.
*Required Field
Preferred Time To Be Contacted (PST)
8:00am - 12:00pm 12:00pm - 5:00pm