Communication Protocols used in BMS
LIST OF PROTOCOLS USED IN BMS
BACnet (Building Automation and Control Network)
- developed by an ASHRAE committee composed of representatives from industry, end-users and consulting engineers
- may be used by head-end computers, general purpose direct digital controllers, application specific or unitary controllers, and smart sensor/actuator devices with equal effect
- defines data communication services and protocol for computer equipment used for monitoring and controlling HVAC, refrigeration and other building systems.
- defines an abstract object-oriented representation of information communicated between such equipment
- provides a comprehensive set of messages for conveying encoded binary, analog, and alphanumeric data between devices.
- its communication media is defined to be Ethernet devices, ARCnet devices, or a specially-defines RS-485 asynchronous protocol for twisted-pair wiring that will operate at up to 78,000 bits per second.
BatiBUS - Building Bus (France)
- developed by a manufacturers group led by Merlin Gerin and Landis & Gyr. The group formed Club BatiBUS, an association composed primarily of vendors, consulting engineers and energy companies.
- more than 5000 installations throughout France and the rest of Europe with products being manufactured by more than 30 firms.
- designed for commercial, institutional and industrial use.
- uses an asynchronous transmission mode that can have 240 addressable points and up to 1000 nodes per network.
- 4800 bits per second data rate and operates in a distributed fashion without a master node.
- protocol and applications are implemented on standard microprocessors that include a serial I/O channel.
CAB - Canadian Automated Building Protocol
- originally known as the Public Works Canada/Standard Communications Protocol or PWC/SCP
- a published PWC standard and is a requirement for all Government of Canada or Crown Agencies projects incorporating “Building Automation” systems.
- provides for the day-to-day functional needs for the supervision, operation and maintenance of building systems.
- a means of providing linkage to other computer-based processes, executing, energy performance analysis, building equipment diagnostic assessment, or other real time audit or management accounting systems.
- a bridge may link multiple PWC LANs into a common LAN or WAN
CEBus - Consumer Electronics Bus
- an interim standard (IS-60) under development by the Electronics Industries Association (EIA) primarily for use in the residential market.
- a special language deemed particularly suitable for home automation functions has been developed and is part of the interim standard.
- goals are to accommodate a variety of communication media such as power lines, twisted-pair wiring, infrared signaling, and radio frequency signaling, to allow appliances with varying capabilities to use subsets of the CEBus facilities, to encourage the development of low-cost interface devices, and to separate the intelligent operation of devices from the communication infrastructure.
- the protocol signaling devices use a proprietary signaling method devised by the CEBus committee that operates at 6700 bits per second. Since the same signaling method is used on all transmission media, it is felt this scheme is good for implementing home automation in both new home construction and retrofit construction. Both the protocol software and the application language are designed to be implemented on standard microprocessors and to use CEBus-specified transmission media.
EIB - The European Installation Bus
- developed by Siemens and other group of companies
- goals were to provide a collection of hardware and software components that meets the need for control of “installation” products i.e. lighting, shutters, heating, signaling, alarms, and load management, without requiring central controllers which resulted in a distributed system with intelligence in each device and a hierarchical bus connection scheme.
- designed to provide a simple, upwardly compatible, flexible and low-cost system able to deal with elementary functions in a restricted space ,like the home, and capable of extension to handle complex functions in large buildings.
- currently supports only twisted-pair wiring, and the protocol is limited to 10,000 bits per second
- relatively complex hardware and software is needed to form the hierarchy of simple networks into a large network
- Siemens has stated that the 10 kbps EIB protocol is adequate for interlinking different building systems into one and to interlink sensors, actuators and other equipment. Sub-systems for such application in buildings should, in order to stay economically viable, not be burdened with an overhead necessary to permit high-speed file transfers.
- EIB position is that more than one protocol is needed in buildings, for instance, easily enabling an upward compatibility via gateways to high-speed data buses of building management systems.
- complete EIB systems specifies packages, connectors, wiring, etc. for many types of system components which will help manufacturers design interchangeable components
- lighting control components and temperature sensors and controls are presently available from companies supporting EIB in Germany
ESPRIT (European Strategic Program Research and Development Information Technologies /Eureka)
- not a protocol as such, but rather a broad range of technical R&D activities, in this case focused on the technology for controlling devices in homes and buildings
FACN (Facilities Automation Communication Network)
- an integrated energy management control system using IBM computers for central coordination
- adapts to data acquisition laboratory automation, quality control, production monitoring, process analysis, and process control
- intended for connection of “instrumentation subsystems” (typically DDCs) for building control with a central computer
- connects DDC building control systems supplied by many manufacturers
- the IBM PC host operates as the master and the DDCs operate as slaves
FIP (Factory Instrumentation Protocol)
- a process fieldbus that provides hardware and software for distributing control functions over various sites by proving for their communication needs and also providing a real time distributed database. The distributed database contains all functions and state information to provide all control for each device on the bus
- the bus system is intended to operate in hierarchy of communication sub-functions to provide automation and reporting necessary for real time control
- all changes in state of devices is reflected in changes of database variable across the network. Thus all devices have free access to data allowing FIP to provide functions in any subscriber without perturbing the data provider.
data link functions are provided on terminated twisted-pair wiring at speeds 31/23 kbps, 1.0 mbps, and 2.5 mbps.
FND (Firm-Neutral Data Transmission)
- developed by the German Department of Software Development in Stuttgart, Germany
- connects DDC building systems with a central control station
- the network provides an energy management and operation control system composed of building systems that may be incompatible with each other
- each DDC is considered an “island” with custom LAN linking substations which control a number of physical nodes consisting of sensors and actuators. Each island is represented by “an island central station” which routes messages to/from island nodes and the FND network. Each island is linked to the FND network via a gateway using a specified communications protocol.
HBS - Home Bus System
- utilizes coaxial and twisted pair cables in single family dwellings.
- Interphone communications in the home (energy control and communications) control the home by connecting AV devices or systems to the HBS. Broadcasting networks, telephone networks, CATV networks and communication systems between TV, telephones, and CATV converters connect to the HBS.
- separate specifications are planned for the transmission of information after establishment of link since it depends on application and is outside the scope of this standard.
LonTalk - Echelon’s Lon Works Protocol
- developed by Echelon as part of the LonWorks product line to provide low-cost distributed control and communication sensor and actuator networks used in building, home, factory, and instrumentation applications
- presented to programmers and installers as a collection of services that may be optionally invoked. Services may be chosen by the programmer and fixed at compile time.
- follows the ISO-OSI reference Model, containing all seven layers
- designed to support twisted-pair wiring, power-line wiring, radio frequency and infrared communication, and coaxial and fiber optic media.
- since LonTalk protocol is designed for multiple physical media to be interconnected within the same network and components are available for speed ranges from 5 kbps to 1.25 mbps, a wide range of application and cost points can be addressed
- the ability to create flexible bandwidth as needed allows the same protocol to be used to solve problems ranging from interconnecting high-level controllers to economically interconnecting low-level sensors and actuators.
- implemented in a dedicated VLSI component, the Neuron chip (offered by Motorola and Toshiba) for computing and communication and supports numerous transceivers for different physical media.
- LonWorks products include extensive development tools, software, physical layer transceivers, and network management tools.
MAP - (Machine Automation Protocol)
- developed by General Motors and Boeing Corporation to manage the interaction of equipment and computers in a production line.
- messaging service of MAP links cells on a factory floor that interact with each other
- uses the 7 layers of the OSI Reference Model
- Map 3.0 offers an alternate architecture that uses the 3 layers of the OSI Reference Model which is called the mini/MAP
- Enhance Performance Architecture (EPA) supports both the 7-layer and 3-layer OSI model
- there are hundreds of major operational MAP installations throughout the world, including North America, Japan and Europe.
PROFIbus - (Process Field Bus)
- developed by Siemens, Bosch, and Klockner Moeller and was agreed upon as a German National Standard Proposal by ZVEI, the German National (DIN) Trial Use Standard in August 1987. Work continued with support from BMFT (Federal Ministry for Research and Technology) and expanded to include 13 manufacturers and 5 technical institutes.
- goal is to allow low-cost support of a broad range of services and to provide interoperability and a transparent application program environment for Field bus devices
- a combination of token passing ring and master-slave data link control software that can be implemented on general purpose microprocessors and supports data rates of 9.6, 19.2, 90, 187.5, and 500 kbps. Separate application processors are needed for the higher speed data rates.
- initial specifications propose a 2, 4 or 6-wire physical bus using EIA RS-485 compatible links. All transmission is asynchronous character transmission
- designed to support up to 127 physical addresses, but has had several extensions proposed to add additional physical bus segments.
Originally, most of the major HVAC suppliers were backing BACnet and ARCnet, but recently seem to have a change of heart. The biggest of Satchwell’s competitors are now using LonWorks as their chosen control network technology, the reason being the much reduced development costs and times. As already mentioned certain building managers are now specifying LonWorks for all their building systems components.
In order to compete in this lucrative market, Satchwell is currently developing gateways to BACnet, LonWorks and Ethernet, so that when necessary, Satchwell BMS can integrate with third party systems operating on such protocols.
Other Pages....
Return to Home Page
Satchwell Controls BMS
First Philippine Energy Corporation
Email: melprotacio@mailexcite.com
