Gamewell FCI E3 to Modbus TCP
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.
The Gamewell FCI E3 Series System Control Units are manufactured by Fire Control Instruments. A Gamewell FCI-E3 Panel with an enabled serial port can transmit data to a FieldServer which can, in turn, make the data available to other devices including those which communicate using different protocols.
Messages received from the E3 are analyzed and are then either discarded or used to update the FieldServer’s internal Data Arrays depending on the configuration of the FieldServer. Once stored in the FieldServer the data is available to be read or written using other protocols.
This passive Client driver does not poll for data, nor does it send data or commands to the E3, thus it cannot be used to acknowledge, silence or reset alarms and other events.
No automatic panel data synchronization technique exists. The data in the FieldServer and the panel status have to be synchronized manually. This typically requires a panel reset.
The driver can process messages from networked panels. The driver connects to the main panel. Subsidiary panels are configured to send event data to the main panel which then sends messages to the FieldServer. Node information is sent in the line preceding the event and the driver uses this to determine the panel at which the event originated and to store data appropriately.
The driver provides both Client and Server emulation. The Server side of the driver is intended to support FieldServer’s Quality Assurance program and is not intended to provide complete emulation of an E3 and is thus not fully documented. Should you require the Server side functionality to be documented and enhanced, please contact FieldServer’s sales group.
The Modbus TCP Driver allows the FieldServer to transfer data to and from devices over Ethernet using Modbus TCP Protocol. The Modbus TCP driver uses port 502. This port is not configurable. The driver was developed for Modbus Application Protocol Specification V1.1a" from Modbus-IDA. The specification can be found at www.modbus.org. The FieldServer can emulate both a Client and a Server simultaneously on the same ethernet port.
The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.
There are various register mapping models being followed by various vendors. To cover all these models FieldServer uses the following three Models
- Modicon_5digit – Use this format where addresses are defined in 0xxxx, 1xxxx, 3xxxx or 4xxxx format. A maximum of 9999 registers can be mapped of each type. This is FieldServer driver’s default format.
- ADU –Application Data Unit address. Use this format where addresses of each type are defined in the range 1-65536
- PDU –Protocol Data unit address. Use this format where addresses of each type are defined in the range 0-65535.
The key difference between ADU and PDU is for example if Address_Type is ADU and address is 1, the driver will poll for register 0. If Address_Type is PDU, the driver will poll for address 1.
Note 1: If vendor document shows addresses in extended Modicon (i.e. 6 digit) format like 4xxxxx then consider these addresses as xxxxx (omit the first digit) and use either ADU or PDU
Note 2: The purpose of providing 3 different ways of addressing the Modbus registers is to allow the user to choose the addressing system most compatible with the address list being used. At the protocol level, the same protocol specification is used for all three with the exception of the limited address range for Modicon_5digit.