SNMP Custom MIB to BACnet MS/TP Multiport Gateway
Multiport Gateway (Serial-Ethernet-LonWorks)
This protocol translator/gateway provides a wealth of features to enable data transfer between different devices and networks utilizing serial, Ethernet or LonWorks ports. The extensive library of FieldServer drivers provides easy interoperability with devices and networks used in building automation, HVAC, fire and process control industries.
The FS-B3510 is one of the FS-X30 Series FieldServers designed to meet the needs of system integrators in designing a complete interoperable system. The FS-B30 Series brings together the powerful FieldServer driver library with state-of-the-art gateway design. This FieldServer includes four serial connections (two RS-232, two RS-485), two Ethernet ports, and a LonWorks port. The multiport design allows for serial-to-serial interfaces or interface from mulitple serial products to an Ethernet or LonWorks network. The two Ethernet ports enable the integrator to connect a PC to download configuration changes without disturbing the system connections and without the additional cost of an external hub.
The SNMP driver allows the FieldServer to transfer data to and from devices over Ethernet using the SNMP version 1 protocol. The FieldServer can emulate either a Server (SNMP Agent) or Client.
Max Nodes Supported:
The Client can be configured to read values specified by their SNMP Object Identifiers (OID’s), which are defined in the MIB file (Management Information Base) of the target device. When acting as an SNMP Agent (Server), the driver makes the contents of specified integer data arrays available to any SNMP Client.
The FieldServer MIB file sets out the OIDs to use. The current version of the driver can send and receive SNMP traps.
The following SNMP data types are supported:
The maximum number of traps currently supported is 255. The FieldServer Enterprise ID is 6347. MIB files are generated automatically from the FieldServer configuration files. A selection of standard MIB-2 OIDs are supported to allow interaction with popular Network Management packages.
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.
FS-8700-73_BACnetMSTP Driver manua Rev2.01_2015
FS-8704-09 SNMP_ Manual
FieldServer FS-B3510 Start-Up Guide
FS Application Note - Bacnet Protocols supported by FieldServers
FS-8704-09 SNMP_ Datasheet
FieldServer FS-B3510 Datasheet
SNMP Test Software
SNMP Test Software Manual
SNMP Test Software - 2
SNMP Mib Browser
IBMs SNMP Manual
Dell - How to Secure SNMP
Fast Track Intro to SNMP
MG Mib Browser Tool
BACnet MSTP to IP
A BACnet Router is used to connect MSTP trunks to BACNetIP systems. The router itself is a device on the IP and on the MSTP side. The router can also act as BBMD device allowing messages to cross from one subnet to another.
BACnet messages cannot cross from one subnet to another except under special circumstances.
Most BACnet sequenc es of messages begin with a broadcast called 'who is'. All devices respond with 'I am'. That is how they are discovered. It is also how many system confirm the device is still there.
Broadcasts cant cross routers (they are blocked) and therefore devices on the other side of a router cannot e discovered.
BBMD is the name of the BACNet technology that resolves these issues. The BACNet ROuter sold by CAS provides BBMD services as do all FieldServer BACNet products when configured as clients.