What are Communication Protocols? …and the TOP 3
If you are new to controls or maybe have only worked with one type or brand of controls systems you might be wondering what exactly is a communication protocol and what are the ones available. Communication protocols are sometimes not used in the correct context and even the term ‘protocol’ is sometimes not fully understood when it comes to Building Automation Systems.
A communications protocol is a system of digital message formats and rules for exchanging those messages in or between computing systems and in telecommunications. A protocol may have a formal description.
A protocol definition defines the syntax, semantics, and synchronization of communication; the specified behavior is typically independent of how it is to be implemented. A protocol can therefore be implemented as hardware or software or both.
Communications protocol – From Wikipedia, the free encyclopedia
In essence a communication protocol is the ‘formatting’ of how you talk. This can best be explained by relating it to the various languages we speak such as English, Spanish or French. Each language or protocol exchanges the same information such as temperatures, pressures and control signals, but formats it in its own way and therefore can only be used by devices or software that speak the same language or protocol.
Each protocol can then be looked at in more detail to see what media can they talk on and what various ways can that information be routed. Meaning we have defined that they speak English or Spanish, but do they talk on the telephone? in person? using tin cans and string? and if they can’t speak directly to the other person do they have a way of routing the information by use of other means? Kinda like using the postal mail, email or carrier pigeon.
BUT let’s get back to the protocols and I’ll worry about typing up another article about the various ways protocols actually get their information to where it is needed later.
There are 3 prominent communications protocols that stand out in the Building Automation Systems industry. Those are:
BACnet became an ASHRAE/ANSI Standard (135) in 1995 and the following years showed several DDC Controls manufacturers, such as Alerton, Automated Logic and Delta Controls with dedicated BACnet product lines. BACnet can be said to be the youngest of the group and also the only of the three that was not developed or spear headed by a ‘for proft’ corporation or organization.
BACnet is almost always associated with Buildign Automation Systems and HVAC Controls. It’s primary focus was to be used with devices and systems whose applications included heating, ventilating, and air-conditioning control, lighting control, access control, and fire detection.
LonWorks was a creation of Echelon Corporation in 1988 and was added as an ANSI standard (ANSI/CEA-709.1-B) in 1999. LonWorks is not the oldest of the three, but it is by far more robust and capable than the older Modbus protocol.
Lonworks undoubtedly has a larger number of installed devices with over 90 Million by 2010, however the applications and types of devices that use LonWorks are quite diverse such as embedded machine control, municipal and highway/tunnel/street lighting, heating and air conditioning systems, intelligent electricity metering, subway train control, stadium lighting and speaker control, security systems, fire detection and suppression, and newborn location monitoring and alarming.
Modbus was developed in 1979 by a company which manufactured PLCs, Modicon. Modbus is the grand-daddy of the controls communication protocols. Even to this day new products are being manufactured that still can be used with the Modbus protocol.
The actual base parameters of Modbus have not changed at all over the years, however it has such a large install base and an ‘everybody uses it’ stigma attached to it that it still remains a strong standard.
There are many other communications protocols available out there but the above three are what you are going to come across often while in the field. When I look at the above three I actually see three separate niches that each of them fit well into. Though LON and BACnet have been the Ford and Chevy of HVAC controls for many years and will probably continue to fight for market share in the building automation systems market.
What communications protocols have you used and how do you feel that protocol will be used in the future with Building Automation Systems?