23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

26-6 Industrial Communication Systems<br />

(and their specific profiles), or Modbus are used at this level. As a software interface into BMS software,<br />

OPC [19] has reached importance. Today, also Web technologies are used, for example, for management<br />

and configuration of DDC stations. However, these are still of limited use for machine-tomachine<br />

<strong>communication</strong>.<br />

One fact that must not be neglected is the long life cycle of a building and its respective services.<br />

When faced with a future extension or change of the system, access to all new data points must be<br />

preserved. In this case, only an open system can guarantee that one does not find oneself tied to the<br />

contractor that originally installed the system. With BACnet• [9,11], KNX• [6,10,19], and LonWorks<br />

[1,5,20], three major, open standards exist in the field of building automation. While these standards<br />

cover multiple application domains, and hence a broad range of applications, also several domainspecific<br />

busses are emerging. These replace the interfaces that were traditionally used to connect field<br />

devices to controllers. Since they are designed for the use in a specific application domain, they often<br />

provide additional functionality, which makes them especially appealing and cost-effective to install.<br />

A prominent example of these application-specific standards is Digital Addressable Lighting Interface<br />

(DALI) [7]. DALI allows control of up to 64 electronic ballasts for fluorescent lamps and intends to<br />

replace the classical 1–10.V interface. Another example is M-Bus [4], which has been designed in Europe<br />

for (remote) meter reading. The Standard Motor Interface (SMI) bus [22] is mainly used for shutters,<br />

protection <strong>systems</strong>, and sunblinds.<br />

Another trend is the tighter integration of BAS between building service domains. Previously, each<br />

building service domain such as HVAC had its own dedicated control system based on a specific technology.<br />

Other domains might have used different technologies. A set of arriving new functions requires<br />

cross-<strong>communication</strong> between the BAS domains. It is, for instance, no longer acceptable that presence<br />

detectors from the lighting domains are not accessible for intrusion detection <strong>systems</strong>. Another example<br />

is constant light control, which can benefit from integration with shading. If two domains are not based<br />

on the same <strong>communication</strong> technology, the use of gateways is mandatory (e.g., to provide a set of<br />

DALI registers to BACnet). If two domains use the same technology, but different address domains, the<br />

use of proxies is required (e.g., provide network variables of LonWorks domain A to domain B). The<br />

problem with gateways is that the number of translations between <strong>systems</strong> is of quadratic order. Also,<br />

configuring gateways is challenging, as the mapping between technologies can never be a 1:1 mapping,<br />

and therefore information is always lost. A new trend is to equip those devices, which shall integrate the<br />

singular functions, with network technologies of both domains. For example, the DALI constant light<br />

controller may provide both a LonWorks and BACnet interface for transparent access by the respective<br />

system. The advantage is no extra configuration as the device already knows about its data points and<br />

no loss of information into the other system has to be faced.<br />

It is the task of the project engineer to choose among a variety of applicable protocols as well as<br />

various options regarding network topology and function distribution. One may opt to use a common<br />

protocol throughout the system and only varying the network layer according to the expected traffic<br />

load, or one may choose to interconnect multiple trade-specific and level-specific solutions using<br />

gateways. The project engineer also has the choice between using DDC stations to implement the automation<br />

functions or using intelligent field devices instead. However, these decisions are not entirely<br />

independent and therefore should not be made arbitrarily. For each specific project, related requirements<br />

finally determine which approach is suited best.<br />

26.2.4 applications<br />

Today’s BAS have gone a long way from simple HVAC <strong>systems</strong> and become more complex. For once,<br />

centralized control has been replaced by distributed controls. Typical zones for building services now<br />

range from entire building wings down to rooms or window axles. A building service might have different<br />

requirements in different zones, for example, room control may have to be considered separately<br />

from corridors or stairwells. This typically results in different designs for rooms and corridors.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!