OpenWebNet Training 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: *field 1 *field 2 *...*field n ## * 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 ‘ ## ’ * 1 * 1 * 23 ## For example, for switching ON a light: * 1 * 1 * 23 ##

4 OpenWebNet Protocol – Syntax Following field types are accepted: WHO  WHO  WHERE  WHAT  DIMENSION  VALUE 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 OpenWebNet Protocol – Syntax 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 OpenWebNet Protocol – Syntax WHO MyHome Function 0Scenarios 1Lighting 2Automatisms 3Loads Control 4Thermo Regulation 5Alarms 6Basic Video Door Entry system 8Video DES / Telephony 9Auxiliaries 13Device Management 15CEN Commands 16Sound Diffusion 18Energy 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 WHO

7 Table of the OpenWebNet WHO 0SCENARIOS 1LIGHTING 2AUTOMATION SYSTEMS 3APPLIANCES 4HEATING ADJUSTMENT 5ALARMS 6Video Door entry system 7MULTIMEDIA 8Video Door entry system over IP 9AUXILIARIES 10NAVIGATION 11ENERGY DISTRIBUTION 13EXTERNAL INTERFACE DEVICES 14SPECIAL COMMANDS 15HOME AUTOMATION MAIN CONTROL UNIT (“centrale domotica”) 16SOUND SYSTEM 17HOME AUTOMATION MAIN CONTROL UNIT (“centrale domotica”) 18UPS 19Interface 21Telephony 22Multimedia 23Access Control 24Lighting Control Unit 99SERVICE IDENTIFICATION 1001DIAGNOSTIC OF LIGHTING SYSTEM 1004DIAGNOSTIC OF HEATING SYSTEM 1013DIAGNOSTIC OF DEVICE SYSTEM

8 OpenWebNet Protocol – Syntax 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#PAR 1 #PAR 2... #PAR n. 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 WHERE

9 OpenWebNet Protocol – Syntax 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 WHAT

10 OpenWebNet Protocol – Syntax 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 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 OpenWebNet Protocol – Messages Command 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 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 OpenWebNet Protocol – Messages State 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 OpenWebNet Protocol – Messages Messages 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 OpenWebNet Protocol – Messages Messages of dimension reading *#WHO*WHERE*SIZE*VALUE 1 *...*VALUE n ## 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 OpenWebNet Protocol – Messages Messages of dimension writing *#WHO*WHERE*#SIZE*VALUE 1 *...*VALUE n ## 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 OpenWebNet Protocol – Messages Acknowledge 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 0SCENARIOS 1LIGHTING 2AUTOMATISMS 3LOADS MANAGEMENT 4THERMO REGULATION …… 13INTERFACE DEVICES WITH OUTSIDE 16SOUND DIFFUSION …… 0 OFF 0#xOFF at speed x 1ON 1#xOn at speed x 2Dimmer 20% …… 10Dimmer 100% 11timed ON - 1 Min …… 18timed ON sec 19no load 20Flashing 0.5 sec …… 301 level UP (valid for dimmers) 30#x#yy levels DOWN at speed x 311 level DOWN (valid for dimmers) 31#x#yy levels UP at speed x WHO WHAT for WHO =1 OpenWebNet Protocol – Tabel WHO

20 OpenWebNet : table of DIMENSIONS for WHO = 1 DimDescriptionRead / Write 1go to level y with speed xR / W 2TimingR / W 3Lights ONR 4 Dimmer Status 100 levels with ON/OFF speed R 5Sensitivity of movement sensorR / W 6Lux of brightness sensorR / W 7Granularity of presence sensorR / W 9Max life of a lampR / W

21 OpenWebNet : table of WHERE for WHO = 1 0General 1Area 1 …… 9Area 9 11Light point 11 12Light point 12 …… 99Light point 99 #1Group 1 #2Group 2... #9Group 9 Within the light system, you may address the Messages to the following “group” of addresses: General General  all the devices on the installation (riser and possible local buses) Area Area  all the devices in area A Group Group  all the devices belonging to group G Light point Light point  Messages point-to-point to be understood as PL device in Area A  A+PL Extension to the local Bus Extension 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 General  The General command spreads on the installation with following rules:  0All the devices of the installation, riser and local buses.  0#3All the devices of the riser only  0#4#06All the devices of the local bus, address interface I 3 I 4 = 06 Group  The Group command spreads on the installation with following rules:  #1All the devices of the group 1 of the whole plant  #1#3All the devices of the group 1 of the riser  #1#4#06All the devices of the group 1 of the local bus, address interface I 3 I 4 = 06 Area  The Area command spreads on the installation with following rules:  1All the devices of the area 1 of the riser  1#3All the devices of the area 1 of the riser, address interface I 3 I 4 = 06  1#4#06All the devices of the area 1 of the local bus, address interface I 3 I 4 = 06 Point-to-Point  The Point-to-Point command spreads on the installation with following rules:  11The device with PL = 1 of the area 1 of the riser  11#3The device with PL = 1 of the area 1 of the riser, piloted by a local bus  11#4#06The device with PL = 1 of the area 1 of the local bus, address interface I 3 I 4 = 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##

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 OpenWebNet for Dummy 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 OpenWebNet for Dummy 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 OpenWebNet for Dummy 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” OpenWebNet for Dummy

29 OpenWebNet for Dummy 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 OpenWebNet for Dummy Heating System tricky -Is it possible to control a termo actuator? -Now it’s possible with USB/Serial interface L4686SDK and fw 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 OpenWebNet for Dummy 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 OpenWebNet for Dummy 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.