Protocols and Integration Solutions

or (What is the best Solution?)

Siemens Building Technologies

Building Automation

What is a Protocol?

A Protocol, or Communications Protocol, with Field Cabinets as with PCs, is an electrical signal format rigidly structured in such a way that it allows for like pieces of hardware to share information.

Siemens Building Technologies

Building Automation

As the above diagram depicts, TCP/IP is one of many communications protocols for the Intranetand the Internet, allowing many PCs, possibly each running different Operating Systems, to talk to each other.

Siemens Building Technologies

Building Automation

The Key Factors

Just because, as in the previous slide, TCP/IP creates an environment where many PCs CAN talk to each other it doesnt necessarily mean that they WILL talk to each other One of the key factors to achieving a communications link between PCs and/or Field Cabinets is the ability of each host or transmitter to have a piece of information that the recipient can and does understand and needs to use. For this we need to understand the structure of PACKETS

Siemens Building Technologies

Building Automation

The Structure of Packets

In this diagram we see a typical set of building control panels, including a graphical interface PC, residing on a TSP (Twisted Shielded Pair) network; in this case well call it a 485 - token passing protocol because that is an industry standard.

Siemens Building Technologies

Building Automation

The Structure of Packets

The information that gets broadcast onto this network by each field cabinet in turn may be useful or useless to the other field cabinets depending upon the structure of the packet the bit stream or sequence of the electrical pulses that make up the transmission.

Siemens Building Technologies

Building Automation

The Structure of Packets

This is how a typical 485 Packet might look in digital or pulse form: Each 1 represents a + pulse. The Multicast bit, if on, allows for a data packet to be received by all live nodes. This might be used when polling for active field cabinets.

Siemens Building Technologies

Building Automation

Why Cant I Communicate?

The mistake here is assuming that any two field cabinets using the basic 485 protocol can TALK to each other. The truth is that, although they are capable of talking they may not understand the data being transmitted. This is why integration devices, translators, must be created in many cases.

SIEMENS BLN/FLN

Other Vendor 485

Siemens Building Technologies

Building Automation

Why Cant I Communicate?

This same fault may occur and often does occur under systems using RS-232, BACNet and Modbus protocols.

Other issues also may occur in networks using these protocols such as the distance limitation with RS-232 being 100 feet (25 meters)

Siemens Building Technologies

Building Automation

Why Cant I Communicate?

With Modbus and BACNet, Register type and location (addressing) become the determining factors, whether two devices can actually share information or not.

In Modbus, Type of register used for specific forms of Data is somewhat rigidly controlled however location of data bits within the registers, layout of bits within the registers, and size of or quantity of registers used by the data are not controlled by the format of the protocol.

Siemens Building Technologies

Building Automation

Why Cant I Communicate?

What this means is that Controller X may put OAT data in Register 40110 using 16 bits while Controller Y may hold the data in Register 43220 using 11 bits starting at bit 4. So, without a rigid point map of these differences these two controllers can not share this information

Siemens Building Technologies

Building Automation

Modbus
In our Industry Modbus RTU Type I has emerged as something of a standard. RTU (Remote Terminal Unit) Type I uses the following format: Coding System 8 bit binary, Hexadecimal 0-9, A-F. Two hex characters contained within each 8 bit field of the message. Bits per Byte 1 Start Bit, 8 data bits (least significant sent first) 1 bit for even/odd parity; no bit for no parity 1 stop bit if parity is used; 2 bits if no parity CRC Error Check (Cyclical Redundancy Check)

Siemens Building Technologies

Building Automation

Whats a Register?

A Register is nothing more than a Memory Block, an addressed space where information is stored in a specific format usually binary.

Siemens Building Technologies

Building Automation

Modbus Registers

Modbus, in its current form, uses some 5 Memory Resister Address Sets in groups of 10,000 blocks each. Not all registers are used by every device. Developers running RTU Type 1 typically use register address sets 0000, 10000, 30000, and 40000 Each block consists of 16 bits or 2 bytes. Some data requires the use of two blocks per value this is referred to as a Double Holding Register which can be signed (+ or -) or unsigned.

Siemens Building Technologies

Building Automation

Modbus Registers

Registers, by nature of the specific version of the protocol (in this case RTU Type I), are reserved for specific types of data (however some flexibility is permitted): 0 9999: Output Coils (Digital Outputs) 10000 19999: Input Bits (Digital Inputs) 20000 29999: 30000 39999: Inputs (Analog, Floating, etc) 40000 49999: Holding Registers

Siemens Building Technologies

Building Automation

Modbus Registers
Here is a diagram of Modbus Register Layouts for the 40,000 range

Register 40000

00101100 00101100
Register 40001

11000001 00101100
Register 40002

01010011 00101100
Register 40003

00000000 00101100
Register 40004

11101111 00101100
Register 40005

00110110 00101100

Register 49998

00101100 00101100
Register 49999

00000001 00101100
Siemens Building Technologies Building Automation

Why Cant I Communicate?

BACNet, which is structured very much like Modbus, offers the same types of inconsistencies in some cases.

Even with Native BACNet controllers, some points can not be automatically resolved between multi-vendor controls because of the flexibility allowed within the protocol. This is not necessarily a bad thing but it does limit the level of integration allowable and it is a source of confusion for most of us whove been told otherwise.

Siemens Building Technologies

Building Automation

More on BACNet

And, just because two Field Cabinets speak BACNet does not guarantee that they are 100% compatible with each other on the network

Native BACNet 3rd Party Siemens BACNet

Siemens Building Technologies

Building Automation

Now, Lets Talk LON

LON, while potentially more rigid and therefore more multi-vendor friendly, is not without some potential problems when integrating multi-vendor products

First, there is no guarantee that a LON device is LON-Mark registered just because a vendor advertises LON compatibility. Without this registration, true LON compatibility may or may not be a reality. Also, programmable devices present a new (although not quite so newsee BACNet and Modbus) level of incompatibility because of the flexible nature of the devices database.

Siemens Building Technologies

Building Automation

Lets Talk LON

Add to this the requirement that each device on a LON network must be setup using the same software tool, otherwise causing potentially disastrous consequences And the fact that not all vendors subscribe to the same network layout scheme(repeaters, hubs, routers not always supported)

And you have the makings of a very confusing and difficult situation.

Siemens Building Technologies

Building Automation

LON: End Users Wishes

LON, BACNet, Modbus, Profibus, RS-485 were all conceived as means to allow multiple devices to communicate to each other.

In the case of BACNet and LON the desired purpose, was to give customers the freedom to pick and choose different vendors devices and install them on the same networks, allowing interconnectivity among the devices and expanding the end users replacement choices. This is technically achievable but not nearly as easily supported as you might hope.

Siemens Building Technologies

Building Automation

LON: End Users Wishes

Example: Take a LON network of all Vendor X Devices. One device fails. The End User wishes to buy a similar LON device from Vendor Y because of the excellent reputation that Vendor Y has cultivated over the years. The replacement device can be physically installed with little or no trouble.

Siemens Building Technologies

Building Automation

LON: End Users Wishes

However (maybe) the vendor Y device is not LON Mark registered so its point map isnt exactly the same as the removed device (maybe) the removed device had a set of points that were being shared by other devices and this bonding must be rebuilt using the new device

Siemens Building Technologies

Building Automation

LON: End Users Wishes

(maybe) the Vendor X Master device requires a custom point team descriptor in order to talk properly with the new vendor Y device (and this will most often be the case because the networks usually get installed during new construction projects and are supplied initially by one vendor). This is an additional hidden cost that the end user may not be aware of.

Siemens Building Technologies

Building Automation

LON: End Users Wishes

(maybe) the new device vendor Y recommends that his device be setup using software tool A (because thats all that vendor Y supports)

but all existing devices were setup using software tool B and the two tools are not compatible.
This will be the case in many instances.

Siemens Building Technologies

Building Automation

MLN Integration
While PC level integration is basically more flexible and powerful than Field panel level Integration there are issues that must be understood and resolved before an integration solution can be selected: How many different front-ends does your customer want the site staff to use / learn to use? The answer to this one will almost always be ONE but too often this gets overlooked altogether. Can the other vendors actually bring the integration information standard protocol types to their front-end efficiently, reliably and cost-effectively? This is far more difficult to pin down. All vendors will say YES but really very few can guarantee this level of integration.

Siemens Building Technologies

Building Automation

Field Device Programming and Setup

One of the most frustrating aspects, to the End User, of having to live with a multi-vendor device site is having to purchase, update and train employees on the various field panel programming tools. Each vendor will require a specific tool set and as multiple protocols become supported by these vendors the number of software tools may increase. Component Cost is an issue, but more important and much harder to measure, is the degree of frustration and dissatisfaction generated by the NEED to own and operate and understand these various tools. Apply the K.I.S.S*. method and youll be making a very happy end user. (*Keep It Simple Stupid)

Siemens Building Technologies

Building Automation

What is the Best Solution

What is the best solution? Thats like asking which is the best tire for my vehicle or the best grass for my yard or the best baseball player of all time? Each End User is different, each site is unique (to some degree) and each solution has its good and bad characteristics. The choice is rarely simpleand usually limited by various factors

Siemens Building Technologies

Building Automation

What is the Best Solution

While Siemens has proprietary versions of communications protocols, i.e. Profibus (PLC) and RS-485 (BAS) and Instabus (Lighting), we support LON, BACNet and Modbus RTU type I as well. Industry pressure forces BAS vendors to support and produce devices using certain protocols such as BACNet and LON while no clear nor guaranteed benefits are presented. Often these protocols cost more to install and support while offering far less in the way of valued information

Siemens Building Technologies

Building Automation

Factors to consider in any integration project: Transmission Media Protocol Point Naming Scheme Point List Commissioning Expectations

Vendor Responsibility
* Not necessarily in order of priority!

Siemens Building Technologies

Building Automation

Factors to consider in any integration project: Deciding on the transmission media should be the first step and may limit the types of protocols that can be used.

Fiber Optics
Twisted Shielded Pair Cat 5 Wireless

Siemens Building Technologies

Building Automation

Factors to consider in any integration project: Once the Transmission Media has been chosen then an integration Protocol must be selected. Not all vendors support all Protocols and not all Protocols are created equal. Modbus BACNet LON Profibus

Custom *
Siemens Building Technologies Building Automation

Factors to consider in any integration project:

Too often the success of a particular integration project or process is hindered by lack of understanding and / or communication between the involved vendors. Setting vendor responsibility at the start of the project can effectively eliminate this point of potential failure. Define Integrator (usually the front-end supplier) Define Integratee (the supplier of the equipment or device to be integrated to). Define acceptable protocol(s)

Define integration media (transmission media)

Define expectation of integration

Siemens Building Technologies

Building Automation

Factors to consider in any integration project: When a contractor is faced with a decision, he will usually take the path of least resistance. Take away the potential for misunderstanding by setting vendor responsibility at the start of the project.

Siemens Building Technologies

Building Automation

Factors to consider in any integration project:

Questions ?

Siemens Building Technologies

Building Automation