OpenWebNet Training India, March 2009 Eng. Lorenzo Pini

OpenWebNetTraining

India, March 2009

Eng. Lorenzo Pini

2

Open Web Net

Syntax / Messages

3

OpenWebNet Protocol – Syntax

An OpenWebNet message is structured with successive fields that gradually specify the details of the information contained therein:

*field1*field2*...*fieldn##

• A message begins with the character ‘ ** ’

• It’s characterized by a structure with fields of varying length

• The characters accepted in the fields are• numbers numbers :{ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 }• the character ‘ ## ’

• Every field is separated by the character ‘ ** ’

• A message is closed by ‘ #### ’

For example, for switching ON a light: * 1 * 1 * 23 ##* 1 * 1 * 23 ##

4


Following field types are accepted:

WHOWHO WHEREWHERE WHATWHAT DIMENSIONDIMENSION VALUEVALUE

Every field has a precise meaning:

- Function concerned (lights, thermo, alarm, ...)

- Action to carry out (light ON, shutter UP, … )

- Receiver (actuator, amplifier, probe, …)

- Values to read (temperature, alarm type, …)

5


The combination of these fields allows to write a series of standard messages, thus permitting to control the home automation system.

Example:- Switch OFF room light

* who * what * where ##* 1 * 0 * 31 ##

- Reading of amplifier volume

* who * where * dimension * values ##* #16 * where * #1 * volume ##

- Request of burglar alarm status

* who * where ##* #5 * 0 ##

6


WHOWHO MyHome FunctionMyHome Function

0 Scenarios

1 Lighting

2 Automatisms

3 Loads Control

4 Thermo Regulation

5 Alarms

6 Basic Video Door Entry system

8 Video DES / Telephony

9 Auxiliaries

13 Device Management

15 CEN Commands

16 Sound Diffusion

18 Energy Management

It picks out the function of the home automation plant concerned by the OpenWebNet message in question.

For example : WHO = 1 , picks out the messages for the lighting management.

Field WHOField WHO

7

Table of the OpenWebNet WHO

0 SCENARIOS

1 LIGHTING

2 AUTOMATION SYSTEMS

3 APPLIANCES

4 HEATING ADJUSTMENT

5 ALARMS

6 Video Door entry system

7 MULTIMEDIA

8 Video Door entry system over IP

9 AUXILIARIES

10 NAVIGATION

11 ENERGY DISTRIBUTION

13 EXTERNAL INTERFACE DEVICES

14 SPECIAL COMMANDS

15 HOME AUTOMATIONMAIN CONTROL UNIT(“centrale domotica”)

16 SOUND SYSTEM

17 HOME AUTOMATIONMAIN CONTROL UNIT(“centrale domotica”)

18 UPS

19 Interface

21 Telephony

22 Multimedia

23 Access Control

24 Lighting Control Unit

99 SERVICE IDENTIFICATION

1001 DIAGNOSTIC OF LIGHTING SYSTEM

1004 DIAGNOSTIC OF HEATING SYSTEM

1013 DIAGNOSTIC OF DEVICE SYSTEM

8


For every WHO (and thus for every function) is specified a table of the WHERE.

It locates the devices as a whole interested by the message.

It may be a single object, a group of objects, the whole system, a specific ambient, etc.

The WHERE tag may also include some parameters (optional) specified as follows:

WHERE#PAR1#PAR2 ... #PARn.

Example of WHERE: all lights of group 1 where = #1,the slave probe 2 of zone 1 of the thermo regulation system where = 201

Field WHEREField WHERE

9


For every WHO (and thus for every function) is specified a table of the WHAT.

Pick out either an action to carry out or a status to read.

The field WHAT may also contain some parameters (optional) specified as follows:

WHAT#PAR1#PAR2…#PARn.

Example of actions:switch ON light A=1, PL=2 what=1, with whom=1 and where=12 *1*1*12##

Examples of states:alarm in zone 2 what = 15 , with whom = 5 and where = #4 *5*15*#2##

Field WHATField WHAT

10


For every WHO (and thus for every function) is specified a possible table of the SIZES.

Pick out a dimension that characterizes the object which the message refers to.

It’s possible to request/read/write the value of a dimension.A pre-set number of values is associated to every dimension, specified by the field VALUE.

Example of a dimension:the temperature of a probe *#4*12*14*0250*1##the volume of a loudspeaker *#16*31*1*10##the firmware version of a device *#1013**2*2*0*54##

Field SizeField Size

11

OpenWebNet Protocol – Messages

We can pick out 4 types of OpenWebNet messages:

Command / State Messages

State request messages

Messages of dimension request / reading / writing

Acknowledgement messages

12


Command MessagesCommand Messages

*WHO*WHAT*WHERE## *4**303*#0##

When such a message is sent, an action is carried out on the controlled home automation plant.

State MessagesState Messages

*WHO*WHAT*WHERE## *2*0*77##

This message is sent when an action is carried out on the plant, or when the status of a single device changes, or when this status is specifically requested.

13


State Request MessagesState Request Messages

*#WHO*WHERE## *#5*0##

Further to the sending of this message, the interested devices reply by transmitting their status through one or more status message(s).

For instance: if you ask for the status of the lights in area 1, all the actuators present there will reply

by transmitting their status. if you ask for the status of the control unit of the Burglar Alarm system, this will reply

with a series of status messages that make clear the situation of the installation.

14


Messages to request the dimensionMessages to request the dimension

*#WHO*WHERE*SIZE##

This Message is sent to request the value of a specific dimension of a device within the home automation system.

Further to this message, the interested devices will reply by transmitting the value of the requested dimension with one or more dimension reading messages.

For instance: you ask for the value of the temperature read by a probe you ask for the frequency on which the radio is tuned.

15


Messages of dimension readingMessages of dimension reading

*#WHO*WHERE*SIZE*VALUE1*...*VALUEn##

This message is sent when an action is carried out on the installation, varying the value of a dimension, or when this value of any device changes spontaneously, or when this value is specifically requested.

For instance: If you change the volume from an amplifier, the new value is sent automatically If you change the temperature read by a probe If you require the firmware version of a device, this replies.

16


Messages of dimension writingMessages of dimension writing

*#WHO*WHERE*#SIZE*VALUE1*...*VALUEn##

This message is sent to change the dimension value of a device.

For instance: plan the set point of a thermo regulation zone set the time of a Web Server set the radio station to listen to set the switching ON speed of a dimmer

17


Acknowledge messagesAcknowledge messages

ACK*#*1##

NACK*#*0##

These are used to specify the result of a communication between an Open Server and an Open Client who set up a session with each other.

18

Open Web Net

Lights Function

WHO = 1

19

0 SCENARIOS

1 LIGHTING

2 AUTOMATISMS

3 LOADS MANAGEMENT

4 THERMO REGULATION

… …

13 INTERFACE DEVICES WITH OUTSIDE

16 SOUND DIFFUSION

… …

0 OFF

0#x OFF at speed x

1 ON

1#x On at speed x

2 Dimmer 20%

… …

10 Dimmer 100%

11 timed ON - 1 Min

… …

18 timed ON - 0.5 sec

19 no load

20 Flashing 0.5 sec

… …

30 1 level UP (valid for dimmers)

30#x#y y levels DOWN at speed x

31 1 level DOWN (valid for dimmers)

31#x#y y levels UP at speed x

WHOWHAT for WHO =1

OpenWebNet Protocol – Tabel WHO

20

OpenWebNet : table of DIMENSIONS for WHO = 1

Dim Description Read / Write

1 go to level y with speed x R / W

2 Timing R / W

3 Lights ON R

4 Dimmer Status 100 levelswith ON/OFF speed R

5 Sensitivity of movement sensor R / W

6 Lux of brightness sensor R / W

7 Granularity of presence sensor R / W

9 Max life of a lamp R / W

21

OpenWebNet : table of WHERE for WHO = 1

0 General

1 Area 1

… …

9 Area 9

11 Light point 11

12 Light point 12

… …

99 Light point 99

#1 Group 1

#2 Group 2

... ...

#9 Group 9

Within the light system, you may address the Messages to the following “group” of addresses:

GeneralGeneral all the devices on the installation (riser and possible local buses)

AreaArea all the devices in area A

GroupGroup all the devices belonging to group G

Light pointLight point Messages point-to-point to be understood as PL device in Area A A+PL

Extension to the local BusExtension to the local Bus: it’s also possible to address the Messages to the devices present on the local buses, how?

by adding “#4#interface” after the address…

for instance light A=1 , PL=3, Int = 03 where = 13#4#03

22

OpenWebNet : WHERE for WHO = 1

The GeneralGeneral command spreads on the installation with following rules:

0 All the devices of the installation, riser and local buses. 0#3 All the devices of the riser only 0#4#06 All the devices of the local bus, address interface I3I4 = 06

The GroupGroup command spreads on the installation with following rules:

#1 All the devices of the group 1 of the whole plant #1#3 All the devices of the group 1 of the riser #1#4#06 All the devices of the group 1 of the local bus, address interface I3I4 = 06

The AreaArea command spreads on the installation with following rules:

1 All the devices of the area 1 of the riser 1#3 All the devices of the area 1 of the riser, address interface I3I4 = 06 1#4#06 All the devices of the area 1 of the local bus, address interface I3I4 = 06

The Point-to-PointPoint-to-Point command spreads on the installation with following rules:

11 The device with PL = 1 of the area 1 of the riser 11#3 The device with PL = 1 of the area 1 of the riser, piloted by a local bus 11#4#06 The device with PL = 1 of the area 1 of the local bus, address interface I3I4 = 06

23

OpenWebNet Protocol – addressing

s : *1*1*11#4#01##

r: *1*1*11#3##

r: *1*1*11##s : *1*1*11##

r : *1*1*11##r :*1*1*11#4#01##

r :*1*1*11#4#01##

r : *1*1*11#4#01##

24

OpenWebNet for Dummy

Light tricky

- I push a command configured to control a light:- no information are translated in OWN- if there is the actuator, this changes his status

a Client Open sees this information

- Point to point and group commands- actuators communicate status change

- General and enviroment commands- Actuators don’t communicate status chage

- Actuator configured with M=PUL- actuator reads only point to point commands- It’s necessary to configure in Eth Gateway this information

25


Light tricky

- Does actuator inform if a load is disconnected?- Yes, dimmers do it- Normal actuators don’t it

- Is it possible to use an actuator as “memory”?- Yes, why not?

- How I can know the status of a clear contact?- Use a 3477 that control an actuator in PUL mode- Use a 3476, it has an actuator inside, this give the

status of the contact

26


Light tricky

I need to execute something when I push a command

How to do?

There are 2 available solutions:

- CEN command (using MH200)

- Scenario command (using F420)

- ( future development configuration )

27


Light tricky

MH200 solution

- Configure a command with M=CEN- Add an MH200 on the system- Monitor with an OpenWebNet Client the system

- Push the first button of the command- On Monitor connection client see this frame:

*15*01*address##

It’s possible to use this information to start an action / a customized scenario

For each address are available 99 “actions”

28

Light tricky

F420 solution

- Use a H4680 and a F420- Monitor with an OpenWebNet Client the system

- Push the first button of the command- On Monitor connection client see this frame:

*0*1*address##

It’s possible to use this information to start an action / a customized scenario

For each address are available 16 “actions”


29


Heating System tricky

- Is it possible to use probe without central unit?- Yes, but a probe doesn’t control his actuator without the CU

- Does probe inform automatically about measured temperature?- If there is a central unit every 15 minutes- If there isn’t a central unit only if a client request it (polling)- If the probe is configured as slave, automatically every 10

minutes.

- How many slave probes is it possible to configure?- 8 for each zone- This means 8*99 = 792 possible probes

- How many external probes is it possible to configure?- 9 for each systems- Must be configured in zone ZERO

30


Heating System tricky

- Is it possible to control a termo actuator?- Now it’s possible with USB/Serial interface L4686SDK and

fw 1.10.1- It will be possible with the next F453AV firmware- If there is a master probe in the zone of the actuator, probe

always forces the status of the actuator

- Is it possible to control FAN speed?- Yes, using L4686SDK, Touch Screen H4684, with the next

version of F453AV firmware- The probe to be used is 4692FAN (vith “VIRT” LOG).

31


Alarm System tricky

- Is it possible to arm/disarm the burglar alarm system?- No, this function is not available using a gateway

- Is it possible to use alarm device without CU? - No, this is not possible.

- What is it possible to do with OpenWebNet?- Know and request the status of the whole system- Know about an alarm

- What is it possible to do if I customized the TS SDK?- TS is directly connected to SCS BUS, so it’s possible to do all

that burglar alarm system allows.

32


DES System tricky

- Is it possible realize a Internal Software Unit?- No, there is a Bticino Software for such application

- Is it possible to see the camera’s image? - Yes, it’s possible- The image is 320x240 jpg image- It’s necessary to update this image to have a video

flow

- Is it possible to open the DES door?- Yes, it is.

Documents

OpenWebNet Training India, March 2009 Eng. Lorenzo Pini