home and building automation system an overview -...

Home and Building Automation System – an Overview Ambient intelligence: technology and design

Fulvio Corno, Dario Bonino

Politecnico di Torino, 2013/2014

Outline

• Wired systems

– MyOpen

– KNX

– ModBus

• Wireless systems

– ZigBee

– EnOcean

2013/2014 Ambient intelligence: technology and design 2

MyOpen BTICINO PROTOCOL FOR MYHOME SYSTEM

MyOpen / OpenWebNet

• MyOpen system

– Initially proposed by Bticino (Legrand group)

– Proprietary bus (SCS)

– Proprietary low-level protocol

– Simple configuration • Jumpers (can be carried by electricians)

• Software

– Accessible via OpenWebNet gateways


OpenWebNet

• Allows external applications to communicate, monitor and control MyHome devices

• Open Specification

• Open protocol designed to work on minimal network requirements

– E.g., phone connections


OpenWebNet

• DTMF compatible

– E.g., *1*1*12## Light 12, On

• Defines 2 types of communication sessions

– Command session • To send commands

• To ask for device states

• To require measure values

– Event session • To monitor all the bus events, asynchronously


OpenWebNet - Messages

• Tag structure – *tag1*tag2*tag3*...*tagN##

• Tag – Allowed characters

• {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, #}

– Delimitator • *

– Message end • ##

• Content and structure changes for – Commands / State requests

– Requests of measure values


OpenWebNet – Commands/States • 3-tag structure

– *WHO*WHAT*WHERE##

• WHO – The command/request functionality

(among a set of pre-defined values)

• WHAT – The action to perform – Possible actions are specified for each

WHO value

• WHERE – Identifies the message destination

• Single device, device groups, scenarios, zones, etc.

• WHAT and WHERE can have additional parameters – WHAT#PAR1#PAR2...#PARn – WHERE#PAR1#PAR2...#PARn


WHO Functionality Description

0 Scenarios

1 Lighting

2 Actuators

3 Load control

4 Temperature control

5 Anti-burglar systems

6 Intercom

7 Multimedia

13 Gateway management

15 CEN commands

16 / 22 Sound diffusion

17 Scenarios for MH200N gateways

18 Energy management

25 CEN plus/ plus scenarios/ clean contacts

1001 Automation diagnostics

1004 Thermal control diagnostics

1013 Device diagnostics

OpenWebNet – Commands/States

• Switch on the lamp with id=12

– *1*1*12##

• Switch on the webcam with id=4000

– *7*0*4000##

• Switch off the temperature control for the zone 1

– *4*303*1##

• Switch off all lights

– *1*0*0##


Idiosyncrasies / Peculiarities

• Explicit State Notion • Same format for State changes and Commands

• State change events only in monitoring sessions

• State change events only for “active devices”, buttons and switches do not generate events.

• States and commands only “defined” for “active” devices

– Buttons and switches do not have an explicit state (independent from the controlled object)


More info

• Open community at

– http://www.myopen-legrandgroup.com/

– Free registration

• Documentation, software, discussion groups, application showcase

• Direct contact with Bticino engineers


http://www.myopen-legrandgroup.com/




KNX THE EUROPEAN DE-FACTO STANDARD (ALMOST)

KNX is a standardized (EN 50090, ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BâtiBUS, and the European Installation Bus (EIB or Instabus). The KNX standard is administered by the KNX Association..

KNX


• Formal merger of 3 leading systems for Home and Building Automation

– EIB

– EHS

– BatiBus

KNX


• All devices carry a “bit” of intelligence on-board

• 2 Operating modes

– S-MODE (System Mode) • Requires centralized binding & parameterization (with ETS)

– E-MODE • Simple manipulation without PCs

• Similar to MyOpen

Basic Principles

• Based on the idea of distributed applications

• Every device carries a BIT of «intelligence» on board

• 2 Main operating modes


S-MODE (System Mode)

E-MODE

• Requires centralized binding & parameterization (with ETS software)

• Simple manipulation without PCs

• Similar to MyOpen

Logic Architecture


S-MODE E-MODE

CONFIGURATION

APPLICATION

LINK

Application

• Device implement “Distributed Applications”

– Based on Datapoints

• Distributed Applications = Datapoint Binding

• Datapoints:

– Represent process and control variables in the system

– May be inputs, outputs, parameters, diagnostic data,…

– Standardized Datapoint types

– Grouped into Functional Blocks


KNX – Application (2)


• Communication System and Protocol offer a reduced instruction set to

– Read and Write (set and get) Datapoint values

• Application semantics is mapped to

– Data format

– Bindings

• 3 binding schemes – Free

– Structured

– Tagged binding

Datapoint Addressing example


Functional blocks: Lighting

2013/2014 Ambient intelligence: technology and design 20 * Excerpt from 07_20_02 Lighting Actuators v1.4 AS – The KNX 2.0 specification

Datapoints: Lighting


* Excerpt from 07_20_02 Lighting Actuators v1.4 AS – The KNX 2.0 specification

Datapoint specification: Blinds


Application = Datapoints Binding


GroupAddress

(multicast access to

a datapoint)

GroupAddress

(multicast access to

a datapoint)

Binding

KNX - Binding


• Free binding: – No a priori prescription on which Datapoints may be linked – Free addressing – Customized multicast grouping at the level of individual

Datapoints – Central to S-Mode

• Structured binding – Precise pattern for linking a whole set of Datapoints, usually

corresponding to a Functional Block or Channel – Free-address

• E.g., Controller and Push-button Modes

• Tagged binding – … too complex …

Link - Connections


TP 1 Twisted pair cabling

SELV network and supply system

Asynchronous character

oriented data transfer and half

duplex bi-directional

communication

Transmission rate: 9600 bit/s

CSMA/CA collision avoidance

All topologies may be used and

mixed (line, star, tree, ….)

PL 110 Communication over the mains

supply network

Spread frequency shift keying

signaling

Asynchronous transmission of data

packets and half duplex bi-

directional communication

Central frequency 110 kHZ

Transmission rate: 1200 bit/s

CSMA, compliant to EN 50065-1

RF 868,3 MHz band for Short

Range

Frequency Shift Keying,

maximum duty cycle of 1%

32768 cps (chips per second)

Manchester data encoding

KNXNet/IP Standard protocol for KNX devices

connected to an IP network

IP network as a fast backbone in

KNX installations

Tunnels KNX Frames over IP

KNX – Network technology


• TP 1 (basic medium inherited from EIB)

– Twisted pair cabling

– SELV network and supply system

– Asynchronous character oriented data transfer and half duplex bi-directional communication

– Transmission rate: 9600 bit/s

– CSMA/CA collision avoidance

– All topologies may be used and mixed (line, star, tree, ….)



• PL 110

– Communication over the mains supply network

– Spread frequency shift keying signaling

– Asynchronous transmission of data packets and half duplex bi-directional communication

– Central frequency 110 kHZ

– Transmission rate:1200 bit/s

– CSMA, compliant to EN 50065-1


• RF

– 868,3 MHz band for Short Range

– Frequency Shift Keying, maximum duty cycle of 1%

– 32768 cps (chips per second)

– Manchester data encoding



• KNXnet/IP

– Standard protocol for KNX devices connected to an IP network

– IP network as a fast backbone in KNX installations

– Tunnels KNX Frames over IP


Link - Topology

• LINE

• Up to 256 devices

• Connected into Areas via a Main Line

• AREA

• Up to 16 lines per area

• Up to 16 Areas

• Connected via a Backbone Line

• Max. Number of devices

• 65536


KNX on Stage




• Implicit State Notion – Only a subset of device states can be queried

• State Events • State change events can be published by carefully configuring the KNX devices

– S-MODE – Specific group address for notifications – Pass-through gateway configuration

• All devices can publish state changes • In-operation events available

• KNXNet/IP – Tunnel mode event-based – Supports partial device discovery

• EIBNet/IP – Requires participation to a multicast delivery group:

• 239.192.39.238

Modbus ONE OF THE MOST DIFFUSED INDUSTRIAL PROTOCOLS

Modbus is a serial communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs). Simple and robust, it has since become a de facto standard communication protocol, and it is now a commonly available means of connecting industrial electronic devices

Basic Principles

• Application layer messaging protocol (level 7 of the OSI model)

– client/server communication between devices

– different types of buses or networks

• Industry serial de facto standard since 1979

• Request/reply protocol

– Services specified by function codes


Logic Architecture


Modbus - Addressing


• precise PDU addressing rules – Each data block is

addressed from 0 to 65535

– Each element within a data block is numbered from 1 to n

• pre-mapping between the MODBUS data model and the device application is totally vendor device specific

Data Model

• 4 primary tables

– up to 65536 data items, each

• Distinctions between

– inputs and outputs

– bit-addressable and word-addressable data items

• Read or write of items can span multiple consecutive data blocks


Function codes

• Function Code

– Indicates to the server what kind of action to perform

– Is coded in one byte

– Valid codes are in the range of 1 ... 255 decimal • the range 128 – 255 is reserved and used for exception responses

– Function code "0" is not valid

– Sub-function codes are added to some function codes to define multiple actions


Function Codes


Request/reply protocol


SUCCESSFUL TRANSACTION

FAILING TRANSACTION

Protocol structure

• Simple protocol data unit (PDU)

– Independent of the underlying communication layers

– Specific buses can introduce additional fields on the application data unit (ADU)


Modbus – Data Model


Multiple data blocks Single data block

Modbus - Transaction


Link - Connection


RS485 Serial cable (1 or 2 pairs)

Variable transmission speed from 9600 to 115200 baud

Modbus TCP/IP Ethernet cable (Fiber for longer distances)

Transmission speed depends on the underlying

hardware / network

Modbus – Network technology (2)


• TCP/IP over Ethernet

• Asynchronous serial transmission over a variety of media

– wire : EIA/TIA-232-E, EIA-422, EIA/TIA-485-A

– fiber, radio, etc.

• MODBUS PLUS

– high speed token passing network

Link - Topology

• Depends on the link technology

– RS485 • serial (daisy chain)

• 1 master, many slaves (up to 255)

– Modbus TCP/IP • Multiple masters

• Multiple slaves


Network Architecture


Modbus on Stage



• Explicit State Notion – Can only be queried (read)

• No command notion – Only write operations on registers

• Client/Server approach – Does not support event-based interaction

• Polling

• No explicit device notion – Registers exposed through a Modbus Gateway – Devices identified by their slave id

• No device discovery – Available registers are defined by the vendor


Wireless systems

A comparison (source: Z-Wave)


ZigBee WIRELESS CONTROL THAT SIMPLY WORKS (?)

ZigBee is a specification for a suite of high level communication protocols used to create personal area networks built from small, low-power digital radios. ZigBee is based on an IEEE 802.15 standard. Though low-powered, ZigBee devices often transmit data over longer distances by passing data through intermediate devices to reach more distant ones, creating a mesh network; i.e., a network with no centralized control or high-power transmitter/receiver able to reach all of the networked devices.

Basic Principles

• Low cost, very low power consumption, two way, wireless communications standard

– Built on top of IEEE 802.15.4

• Secure

– Messages are encrypted

• Defines several profiles

– Standard: Home Automation, Smart Energy, etc.

– Custom

• Each profile includes one or more ZCL (ZigBee Cluster Library) specification


Basic principles


ZigBee Profiles

ZigBee Cluster Libraries

Group of devices / functionalities

pertaining a given application domain, e.g.,

Home Automation (ZigBee HA), Smart

Energy (ZigBee SE), etc.

Device functionalities

described in terms of

client-server interactions

Logic Architecture


ZDO – ZigBee Device Objects


Assemble configuration information from

the end applications to determine and

implement discovery, security

management, network management, and

binding management.

Initialize the application support

sub-layer (APS), the network

layer (NWK),

and the Security Service

Provider.

interface

APPLICATION OBJECTS

interface

LOWER PORTIONS

OF THE ZIGBEE

PROTOCOL STACK

Application Framework


Agreements for messages, message formats, and

processing actions that enable developers to create an

interoperable, distributed application employing

application entities that reside on separate devices. These

application profiles enable applications to send commands,

request data, and process commands and requests.

ZigBee Profiles

Clusters are identified by a cluster identifier, which is

associated with data flowing out of, or into, the device.

Cluster identifiers are unique within the scope of a

particular application profile.

ZigBee Clusters

THE ENVIRONMENT IN WHICH APPLICATION OBJECTS ARE HOSTED ON ZIGBEE DEVICES

Profiles


HOME AUTOMATION This profile defines device descriptions and standard

practices for applications needed in a residential or

light commercial environment. Installation scenarios

range from a single room to an entire home up to

20,000 square feet (approximately 1850m2).

The key application domains included in this initial

version are lighting, HVAC, window shades

and security.

This profile defines device descriptions and standard

practices for Demand Response and Load

Management “Smart Energy” applications needed

in a Smart Energy based residential or light

commercial environment. Installation scenarios range

from a single home to an entire apartment complex.


version are metering, pricing and demand

response and load control applications.

SMART ENERGY

The E@H features extend the HA and SE ZigBee

profiles in order to build a new class of devices, i.e.

White Goods for Energy@Home.

ENERGY@HOME

Profiles









and security.










SMART ENERGY




ENERGY@HOME

Teaser:

Next week (Thursday, June 5th) the director of the Energy@Home consortium will present

their activities.

Clusters

• Cluster – Collection of attributes and commands – Defines a communications interface between two devices – Devices implement server and client sides of the interface

• Client – A cluster interface which is listed in the output cluster list of the

simple descriptor on an endpoint. – Sends commands that manipulate the attributes on the

corresponding server cluster.

• Server – A cluster interface which is listed in the input cluster list of the

simple descriptor on an endpoint. – Typically this interface supports all or most of the attributes of

the cluster.


Cluster Definition: OnOffSwitch


I O

Cluster Definition: OnOffOutput


Link - Topology


STAR TREE

MESH

• coordinator is

responsible for starting

the network and for

choosing certain key network

parameters

• the network may be

extended through the use

of ZigBee routers

• hierarchical routing

strategy

• beacon-oriented

communication

• full peer-to-peer communication

• routers in mesh networks do not

currently emit regular IEEE

802.15.4-2003 beacons

• the network is controlled by

one single device called the

ZigBee coordinator

• the ZigBee coordinator is

responsible for initiating and

maintaining the devices on

the network

EnOcean The inventor of patented energy harvesting wireless technology

First ISO/IEC wireless standard optimized for solutions with ultra-low power consumption and energy harvesting .

Approach

• EnOcean modules combine micro-energy converters with ultra low power electronics and reliable wireless communications

• (nearly) Self-powered wireless sensor solutions


Energy?


• And more…

• Pressure

• Rotation (wheels, gas meters)

• Vibrations

Software architecture


Radio technology


Transmission protocol


Short messages: reliability


More information


enocean-energyharvesting.pdf

Open standard, multiple vendors


http://www.enocean-alliance.org/en/products/

Wanna play?


http://www.enocean.com/en/enocean-pi/

License


• These slides are distributed under a Creative Commons license “Attribution – NonCommercial – ShareAlike (CC BY-NC-SA) 3.0”

• You are free to: – Share — copy and redistribute the material in any medium or format – Adapt — remix, transform, and build upon the material – The licensor cannot revoke these freedoms as long as you follow the license

terms.

• Under the following terms: – Attribution — You must give appropriate credit, provide a link to the license,

and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.

– NonCommercial — You may not use the material for commercial purposes. – ShareAlike — If you remix, transform, or build upon the material, you must

distribute your contributions under the same license as the original. – No additional restrictions — You may not apply legal terms or technological

measures that legally restrict others from doing anything the license permits.

• http://creativecommons.org/licenses/by-nc-sa/3.0/

http://creativecommons.org/licenses/by-nc-sa/3.0/













home and building automation system an overview -...

Documents