EST Quickstart 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.
Edwards (EST) Quickstart
The EST QuickStart Serial driver allows the FieldServer to record data from Edwards Systems Technology QS1-2/4-8 and QSC Fire Panels over the RS-232 printer port. The FieldServer acts as a Passive Client receiving messages and recording the status of Fire Alarm System points connected to the EST QuickStart fire alarm control panel in bit oriented Data Arrays. The EST QuickStart panels do not support duplexed communications; therefore this driver has not been designed to respond or to generate polls.
The Driver is limited by the information that the EST QuickStart control panels broadcasts in the form of text messages through its RS-232 printer port.
The types of EST messages supported by this driver are listed in Appendix B.1. Device status to Data Array mapping is also provided. Since there are a variety of optional cards that can be selected for each EST QuickStart installation, each FieldServer application must be specifically configured before use. FieldServer data storage arrays for panel status will be allocated according to the number and type of cards implemented. Message information will also be stored according to card and panel addressing.
This driver is connection oriented; therefore, only one EST Panel may be connected to any single RS-232 FieldServer port.
The driver currently accommodates European and American Conventional/Intelligent panels using the
American English protocol with provisions for using the British English protocol at a later date
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.