SNMP (std) 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 SNMP-STD driver allows the FieldServer to transfer data to and from devices over Ethernet using the SNMP Version V1 or V2c protocol. The FieldServer can emulate a Server (SNMP Agent) or Client (NMS Network Management Station).
The FieldServer provides a generic MIB (Management Information Base) file that sets out the OID (Object Identifiers) structure. The FieldServer Enterprise ID is 6347. A selection of standard MIB-2 OID’s are supported to allow interaction with popular Network Management packages.
When configured as an SNMP Agent (Server) the SNMP-STD driver allows SNMP Get, GetNext (walk) and Set commands to access Data Arrays using the Integer type. The SNMP v1 protocol does not make provision for Floats.
The SNMP-STD driver can send SNMP traps. The structure for SNMP Traps is provided in the FieldServer’s generic MIB file.
The FieldServer also supports custom MIBs and the automatic generation of the MIB file. It supports setting a custom enterprise ID, object names and custom traps or informs. In custom configurations the FieldServer supports various data types as specified in Section 6.1 of the Manual.
When configured as a Client, the FieldServer can read objects from the Server using Get, GetNext (walk) or GetBulk commands. The GetBulk command is very useful to transfer large amounts of data. The FieldServer can update objects in Agent using the Set command.
The FieldServer can accept any trap or inform as long as all the objects in the message are encoded with a full OID.
The Client side of the driver is considered as a custom configuration.
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.