BACnet to Other Protocol Gateway

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.

The BACnet Master-Slave/Token-Passing (MS/TP) driver implements a data link protocol that uses the services of the RS-485 physical layer. See the FieldServer BACnet PIC statement for the level of conformance that this driver implements.

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.

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 Analog Input Object is representative of the Objects involved directly with control elements and many of its Properties reflect this.

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

The 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.

The QuickServer FS-QS-3X10-F series is available at four different point capacities. Each QuickServer is preloaded with 140 different drivers, such as Modbus, BACnet, SNMP, EtherNet/IP and many more. See page 3 for the complete list. The FS-QS-3010-F can support up to 250 points. The FS-QS-3110-F can support up to 500 points. The FS-QS-3210-F can support up to 1,000 points. The FS-QS-3310-F can support up to 3,000 points. The FS-QS-3410-F can support up to 5,000 points. The FS-QS-3510-Fire can support up to 10,000 points.

With two Ethernet ports, the QuickServer allows data to move seamlessly across disparate subnets, using a dedicated port for Cloud connectivity. This port isolation allows for enhanced LAN security from the BMS/WAN/Cloud. An embedded OpenVPN Server enables secure remote access to Ethernet devices in the field.

Every 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.

BTL Mark is registered to the MSA BACnet Driver for MSA QuickServer line of products

The 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 (Serial-Ethernet) is available in two series:

The QuickServer FS-QS-2X10 series is available at four different point capacities. Each QuickServer is preloaded with two drivers (serial and/or Ethernet) from a customer’s choice of 140 different drivers, E.G. Modbus, BACnet, SNMP, EtherNet/IP and many more.

The FS-QS-2010 with 2 RS485 and 1 ethernet port can support up to 250 points. The FS-QS-2210 can support up to 500 points. The FS-QS-2310 can support up to 3,000 points. The FS-QS-2410 can support up to 5,000 points.

Equivalently the FS-QS-2020 with 1 RS485, 1 RS232 and 1 ethernet port can support up to 250 points. The FS-QS-2220 can support up to 500 points. The FS-QS-2320 can support up to 3,000 points. The FS-QS-2420 can support up to 5,000 points.

Every 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.

BTL Mark is registered to the MSA BACnet Driver for MSA QuickServer line of products

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 worldwide 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 (Serial-Ethernet) is available in two series:

The FS-QS-1X10 Series is preloaded with two BAS drivers (two RS485 serial ports and one Ethernet port) Drivers from a list of over 150 protocols. There is a basic QuickServer that can handle up to 250 points and an enhanced QuickServer that can handle 500 points.

The FS-QS-1220 Series is preloaded with two BAS drivers (one RS485 serial port, one RS232 serial port, and one Ethernet port) Drivers from a list of over 150 protocols. Each QuickServer can handle up to 500 points.

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.

BTL Mark is registered to the MSA BACnet Driver for MSA QuickServer line of products

Can't find the protocol you are looking for? Give us a call. We regularly add new drivers to our protocol library and may already support what you are looking for. Even if we do not currently support it, we develop custom drivers on demand. Give us a call, we can write drivers for just about any device.

Below is a list of potential Protocols. Many of them, we already have and the rest, we can develop.

Allen-Bradley CSP, Armstrong FA403, ATMI ACM and TGM, BACnet Arcnet, Barrington MicroSTAR, Barrington LanSTAR, Canatal, Caterpillar, ControlNet, Cummins, Data Highway Plus (DH), Data Highway Plus (DH+), DeviceNet, DF1, DNP3, Edwards, Federal Signal Ultravoice, Fike Cheetah, Gamewell FCI, GE SNP (SNPx), GE SRTP, GE TLC, GE-EGD, HTTP, KNX, Kohler, M-Bus, McQuay Microtech, MetOne Particle Counters, Mircom FX2000, Modbus ASCII, Modbus Plus (MB), Modbus Plus (MB+), Multistack Compu25, National Time and Signal, Notifer 320/640, Notifer Legacy Panels, Notifier 3030, Omron FINS, OPC, Optomux Opto22, Profibus, Rapid Engineering ICSII, SIA Security Industry, Siemens Fire Safety, Silent Knight Fire, SNMP, Stulz, TAC I-Net, Telnet, TL1, TOA VS900, XML, Cleaver-Brooks Hawk, Carrier DataLink, EST3 Serial, Veeder Root, DNP 3.0, Mudbus Jbus, Profibus DP Slave, Notifier INA, Data Aire DAP, Data Aire DART, Secutron, RussElectric Model 2000, Notifier Italia AM6000, Notifier 200/300/400, Lutron Machine, Gardner Denver, Grinnell TFX Minerva, Modbus Tek-Air, Hochiki Serial Driver, Notifier 1010/2020, Zellweger Infratox, Notifier NCA, Notifier Onyx 640, Metasys N2, BACnet PTP Serial

The BACnet Arcnet driver (obsolete) allows the FieldServer to transfer data to and from devices using BACnet protocol over an Arcnet highway. The Arcnet card is included with the FieldServer. The FieldServer can emulate either a Server or Client. 

It is possible to connect a BACnet device to any of the eight RS232 ports or two RS485 ports. These ports just need to be configured for BACnet in the configuration file. Configure the PLC according to manufacturer’s instructions