M-Bus to BACnet IP and MSTP QuickServer Gateway (16 Devices)

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.

Every BACnet device must have a Device Object, which provides details about the device and its functionalities to other networked devices. Before engaging in control communications, a BACnet device must acquire pertinent information from the Device Object of the target device. Unlike other Objects, the Instance number of the Device Object must be unique across the entire BACnet internetwork, serving as the device's distinct identifier. This uniqueness facilitates easy identification of the BACnet device during installation and operation.

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 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 M-Bus driver allows the FieldServer to transfer data to and from devices using M-Bus protocol. The fieldbus connection is included with the FieldServer. The FieldServer can emulate either a Slave or a Master.

The M-Bus QuickServer Gateway is configurable to act as both a Master and a Slave M-Bus device. As an M-Bus Master the number of devices supported is limited to 64 devices since the FieldServer provides power to the M-Bus. The M-Bus Master interrogates the Slave devices as the gateway acts as a Master. It will request information from the Slave devices and receive and process only the expected responses. As an M-Bus Slave the maximum number of devices is limited to the M-Bus standard of 250. The Gateway will act as a Slave and will respond only to requests from M-Bus Master devices.