Veeder-Root to DNP 3.0 Ethernet QuickServer Gateway

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

The Dual port QuickServer takes the QuickServers to the next level with Security and Power. With two Ethernet ports, the Dual port 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.

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.

The Veeder-Root Serial Driver allows the FieldServer to transfer data to and from devices over either RS- 232 or RS-485 ports using Veeder-Root protocol as defined in Veeder- Root Document 576013-635 Revision J. The Veeder-Root Driver supports TLS350 as per Veeder-Root Document 576013-635 Revision Y, and TLS450 as per Veeder-Root Document 577013-950 Revision G. Since the data protocol is the same for the TLS-350+ as for TL-S350, it is assumed that the driver will support the TLS350+ but this has not been tested. The Driver also successfully communicates with the TLS-450 as it has the same data protocol. Please refer to the driver manual for hardware connections.

The FieldServer emulates a Client.

The Veeder-Root Serial Driver is a poll response driver. Only one query or command can be processed at a time.

A limited set of the queries and commands defined in the protocol specification have been implemented. The reason for the limitation is two-fold. Firstly, not all commands/queries will have any meaning to a Server device as they are principally defined to configure the Veeder-Root Device. Secondly, some commands return very complex data sets which cannot be processed in a method suitable for loading into the FieldServer’s Data Arrays.

The driver is capable of exposing its communications statistics which allows them to be monitored using a Server device. 

Supported Veeder-Root products

The Veeder-Root Gateway supports the following Veeder-Root Products:

• TLS-450 PLUS Automatic Tank Gauge
• TLS4i / TLS4c Automatic Tank Gauge
• TLS-350 Automatic Tank Gauge
• TLS-350 Plus Automatic Tank Gauge
• TLS-350R Automatic Tank Gauge
• TLS-300C/I Automatic Tank Gauges
• TLS-2/P Automatic Tank Gauge

The Ethernet DNP 3.0 driver allows the FieldServer to transfer data to and from devices over Ethernet using DNP 3.0 protocol. The FieldServer can emulate either a Server of Client. The DNP 3.0 Ethernet Driver adheres to and supports the framework specified by the IEEE 1815-2012 Standard for electrical power system communications.  

The following information was copied form the DNP 3.0 User Group Internet site.  

The development of DNP3 was a comprehensive effort to achieve open, standardsbased Interoperability between substation computers, RTUs, IEDs (Intelligent Electronic Devices) and master stations (except inter-master station communications) for the electric utility industry. Also important was the time frame; the need for a solution to meet today's requirements. As ambitious an undertaking as this was, we reached this objective. And since the inception of DNP, the protocol has also become widely utilized in adjacent industries such as water / waste water, transportation and the oil and gas industry.  

DNP3 is based on the standards of the International Electrotechnical Commission (IEC) Technical Committee 57, Working Group 03 who have been working on an OSI 3 layer "Enhanced Performance Architecture" (EPA) protocol standard for telecontrol applications. DNP3 has been designed to be as close to compliant as possible to the standards as they existed at time of development with the addition of functionality not identified in Europe but needed for current and future North American applications (e.g. limited transport layer functions to support 2K block transfers for IEDs, RF and fiber support). DNP3 has been selected as a Recommended Practice by the IEEE C.2 Task Force; RTU to IED Communications Protocol.  

DNP3 is an open and public protocol. In order to ensure interoperability, longevity and upgradeability of, protocol the DNP3 Users Group has taken ownership of the protocol and assumes responsibility for its evolution. The DNP3 Users Group Technical Committee evaluates suggested modifications or additions to the protocol and then amends the protocol description as directed by the Users Group members.  

DNP3 Features: DNP3 offers flexibility and functionality that go far beyond conventional communications protocols. Among its robust and flexible features DNP3 includes:  

• Output options  
  
• Secure configuration/file transfers  
• Addressing for over 65,000 devices on a single link  
• Time synchronization and time-stamped events  
• Broadcast messages  
• Data link and application layer confirmation  

DNP3 was originally designed based on three layers of the OSI seven-layer model: application layer, data link layer and physical layer. The application layer is objectbased with objects provided for most generic data formats. The data link layer provides for several methods of retrieving data such as polling for classes and object variations. The physical layer defines most commonly a simple RS-232 or RS-485 interface.  

DNP3 is very efficient for a layered protocol while ensuring high data integrity

DNP3 Benefits: Because DNP3 is based on the IEC 870-5 requirements, DNP3 is suitable for application in the entire SCADA environment. This includes RTU to IED communications, master to remote communications, and even peer-to-peer instances and network applications.  

Being an object-based application layer protocol, DNP3 has the flexibility to support multiple operating modes such as poll-response, polled report-by-exception, unsolicited responses and peer-to-peer. It permits multiple masters and encourages distributed intelligence.  

Users can expect many benefits from using DNP3. In the short term:  

• Interoperability between multi-vendor devices  
• Fewer protocols to support in the field  
• Reduced software costs  
• No protocol translators needed  
• Shorter delivery schedules  
• Less testing, maintenance and training  
• Improved documentation  
• Independent conformance testing  
• Support by independent users group and third-party sources (e.g. test sets, source code)