OWN Full

Open Web Net Language
My Open Web Net Introduction
www.myopen-legrandgroup.com 1
Document History
Version Date Author

2.0.0 14/11/2011 My Open Staff
Updating description: Second Version
Index
INTRODUCTION....................................................................................................................3
Examples of Integration......................................................................................................... 3
SYNTAX OF AN OPEN MESSAGE....................................................................................... 5
COMMUNICATION SESSIONS.............................................................................................8
Example of communication stream........................................................................................9
Commands/Actions session................................................................................................. 11
Event session....................................................................................................................... 12
Programmed Scenario Session........................................................................................... 13
Particular Open Messages...................................................................................................14
ACK message...................................................................................................................... 14
NACK message....................................................................................................................14
........................................................................................................................................... 15
COMMAND / STATUS OPEN FRAMES.............................................................................. 16
Tag WHO:.............................................................................................................................16
Tag WHAT:............................................................................................................................16
Tag WHERE:........................................................................................................................ 17
Examples .............................................................................................................................17
STATUS REQUEST OPEN FRAME.................................................................................... 18
Examples .............................................................................................................................18
DIMENSION REQUEST OPEN FRAME............................................................................. 20
Examples..............................................................................................................................20
DIMENSION WRITING OPEN FRAME............................................................................... 21
FUNCTIONS DEVELOPED THANKS TO OPEN WEB NET...............................................23
Table of WHO....................................................................................................................... 23
........................................................................................................................................ 23
License................................................................................................................................. 25
Disclaimers...........................................................................................................................25
INTRODUCTION
In the last decades BTicino invested on the technological research and on development of
Home Automation Systems.
To let anyone who has knowledge about programming language to interact with the
systems we thought to implement a communication language called Open Web Net
OPEN = Open Protocol for Electronic Networks
Thanks to the Open Web Net it is possible to exchange data and to send commands
between a remote unity and the My Home System. The protocol is thought to be
independent from the communication way, considering using DTMF tones on the normal
phone line PSTN as a minimum requirement. Up to now the devices which are using this
protocol are the web servers and the phone actuators.
This language has been implemented also to allow the integration with third party systems
and functions or to let, some devices; as PC, Smart phones and tablets, communicate with
My Home out of a LAN network.
The Open Web Net has been introduced to provide an abstract level which allows the
supervision and the control of My Home systems focusing on functions without caring
about the configuration details and without knowing deeply the SCS technology.
Examples of Integration
Knowing the syntax protocol it is possible to use a own software to control My Home
system.
SYNTAX OF AN OPEN MESSAGE
An Open frame is composed by characters belonging to the following collection:
{0, 1, 2, 3, 4, 5, 6, 7, 8, 9, *, #};
It starts with the character ‘*’, and ends with the couple ‘##’.
The character ‘*’ is also used as a separator among the tags.

An Open message is built in this way:
*tag1*tag2*tag3*...*tagN##
A tag is composed by characters belonging to this set:
{0, 1, 2, 3, 4, 5, 6, 7, 8, 9, #}.
A tag can’t have the couple ‘##’. A tag may be omitted, creating Open message similar to
this one:
*tag1*..*..*tag4*...*tagN**##
The table shows the different kinds of messages that can be sent or received in a Open
Client-Server conversation.
ACK *#*1##
NACK *#*0##
NORMAL *WHO*WHAT*WHERE##
STATUS REQEUST *#WHO*WHERE##
DIMENSION REQUEST *#WHO*WHERE*DIMENSION##
DIMENSION WRITING *#WHO*WHERE*#DIMENSION*VAL1*VAL2*...*VALn##
COMMUNICATION SESSIONS
The TCP-IP gateway offers the Open Server on the 20000 port.
There are three main phases to establish a session:
- connection
- identification
- communication
The Open Client can establish two different kinds of sessions:
- Command Session (actions): used to send commands, status requests, dimen-

sion requests and writing
- Event Session: used by the Open Client to read all what happens on the home au-
tomation bus in a asynchronous way.
Example of communication stream
The identification phase changes if, in the Open Server, is configured an IP range that
allows the communication without the need of the OPEN password.
[For further information:

http://www.myopen-legrandgroup.com/resources/tutorials/m/mediagallery/33995.aspx]
Whether you have to exchange an OPEN password, the OPEN Client must know the
authentication algorithm.
Commands/Actions session
After have chosen a TCP-IP connection between a Client and a Server; the
communication flow will be the following:
Example connection commands session:
Event session
After having established a TCP-IP connection between a Client and a Server; the
Example Event Session:
Programmed Scenario Session

This kind of session it can be used only if a Scenario module (F420 for BTicino; 03551 for
Legrand) is in configuration modality and there is the necessity to program it trough
Ethernet.
After having established a TCP-IP connection between a Client and a Server; the
Example Programmed Scenario Session:
Particular Open Messages

In addition to the commands messages there are particular messages that will be sent
during the communication flow: ACK and NACK frames
ACK message
The Acknowledgement Open message has the following syntax:
*#*1##
This frame indicates that the Open message, sent by the Client, or received by the Server,
is semantically and syntactically correct.
Furthermore it is used as an ended message when it is the answer to an Open frame
which involves the forwarding of one or more messages in sequence (status or dimension
requests).
NACK message
The Open Message of not-acknowledge (NACK) is
*#*0##
This frame means that the Open message, sent by the Client to the Server, is semantically
or syntactically wrong. Furthermore it is used as an ended message when it is the answer
to an Open frame which involves the forwarding of one or more messages in sequence
(status or dimension requests).
In this case, the Client may consider invalid any message received before the NACK .
COMMAND / STATUS OPEN FRAMES
The Open message, that has this function is so structured:
*WHO*WHAT*WHERE##
This frame is used both in the action/commands session and in the events one.
• Events session: indicates that a My Home system object has changed its status.
• Commands / Actions session:

o Message sent by the Server to the Client as response to a status request.
o Message sent by the Client to the Server to require an action execution.
Tag WHO:
The Tag WHO identifies the Home automation system’s area involved by the Open frame
used.
Tag WHAT:
The tag WHAT, identifies the action to make (ON lights, OFF lights, dimmer at 20%,
shutters UP, shutters DOWN, set program 1 in thermoregulation central, etc...)
For each WHO (and so for every function) is described a WHAT table.
The WHAT tag can contain other parameters:
WHAT#PAR1#PAR2...#PARn.
Tag WHERE:
The tag WHERE detects the objects involved by the frame (environment, room, single
object, whole system).
For each WHO (and so for every function) is described a WHAT table.
The WHERE tag can contain other parameters
WHERE#PAR1#PAR2...#PARn.
Examples
OPEN Description
*1*1*12## Command to switch ON light 12 / report light status 12, ON
*2*1*41#4#2## Command shutter 41 UP on local bus interface 2
*1*0*0## Command OFF whole system
*7*0*4000## Command ON cam whose address is 4000
*4*303*1## Command OFF room 1(thermoregulation function)
STATUS REQUEST OPEN FRAME
The status request Open message is so structured:
*#WHO*WHERE ##
The Client sends this message in the Command/action session to require information on
the status of a single object or the entire system. The Server replies to this request by
sending one or more Open status messages.
The reply must end with an ACK or NACK frame.
If the field WHERE isn’t specified, the request is generic and sent to the whole system.
Examples
OPEN Desciption
*#1*12## Request status light 12
*1*1*12## Reply status light 12, light ON.

ACK The flow is closed with an ACK only if the frame is correctly
sent.
*#1*41#4#2## Request status light 41on local bus interface 2
*#1*0## Request status light function
*#4*1## Request status zone 1 thermoregulation function
DIMENSION REQUEST OPEN FRAME
The OPEN message to require the dimension is so structured:
*#WHO*WHERE*DIMENSION##
The client sends in the commands session to require information about the dimension
value of both one single object or an entire system.
The server replies by sending one or more Open status messages, so structured:
*#WHO*WHERE*DIMENSION*VAL1*...*VALn##
The number of VAL fields depends on the DIMENSION requested.
The answer message is followed by the ACK.
If there is an error in the dimension request then it will be displayed the NACK frame.
The reply message is generically sent even in the Events connections.

The Open Server forwards the dimension message if there are variation on that dimension
or simply if the device has to signal periodically his dimension status (for example the
thermo probe has to communicate a value every 15 minutes).
Examples
OPEN Description
*#13**1## Request date of the device that implements the Open
Server.
*#13**1*D*G*M*A## The reply message has 4 parameters which represent day of
ACK the week, month , year.
The flow is ended by an ACK if the reply is correctly sent.
*#4*1*0## Request temperature in the zone 1of the thermoregulation
function.
*#4*1*0*0215*3## The reply message includes the temperature value 21,5°
ACK written in the first parameter.
*#4*1*14*0250## Temperature Zone 1 of the thermoregulation function set at
25°.
DIMENSION WRITING OPEN FRAME
The OPEN message to write the dimension is so structured:
*#WHO*WHERE*#DIMENSION*VAL1*...*VALn##
The message implies a modification only for the dimensions which can be modified.
The Client sends this message in the Commands/actions session to modify the dimension
values of a single object or the whole system.
The Server will answer with an ACK or NACK message.
OPEN Description
*#13**#0*21*10*00*01## Set the device time which implements the OPEN server at
21.10.00
*#4*#0*#0*0250*1## Set the Thermo Central Unit temperature at 25 degrees in
heating mode.
FUNCTIONS DEVELOPED THANKS TO OPEN WEB NET

Table of WHO
Code Description
0 Scenarios
1 Lightning
2 Automation
3 Controllo carichi *
4 Temperature Control
5 Alarm
6 VDES
13 Gateway Management
15 CEN commands
16 / 22 Sound diffusion**
17 MH200N scenarios
18 Energy management
25 CEN plus/ scenarios plus/ dry contacts
1001 Automation diagnostic
1004 Thermoregulation diagnostic
1013 Device diagnostic
License
By using and/or copying this document, you (the licensee) agree that you have read, understood,
and will comply with the following terms and conditions:
Permission to copy, and distribute the contents of this document, in any medium for any purpose
and without fee or royalty is hereby granted, provided that you include the following on ALL copies
of the document, or portions thereof, that you use:
A link or URL to the www.myopen-legrandgroup.com.
The copyright notice of the original author, or if it doesn't exist, a notice (hypertext is preferred,
but a textual representation is permitted) of the form: "Copyright © [date-of-document]
www.myopen-legrandgroup.com. All Rights Reserved".
When space permits, inclusion of the full text of this NOTICE should be provided. We request that
authorship attribution be provided in any software, documents, or other items or products that you
create pursuant to the implementation of the contents of this document, or any portion thereof.
Any contributions to the document (i.e. translation, modifications, improvements, etc) has to be
submitted to and accepted by the My Open staff (using the forum of the community or sending an
email via the www.myopen-legrandgroup.com dedicated section) . Once the improvement has been
accepted the new release will be published in the My Open Community web site.
.
Disclaimers
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRE-
SENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIM-
ITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PUR-
POSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT
ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CON-
TENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADE-
MARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL
OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR
THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or publicity
pertaining to this document or its contents without specific, written prior permission. Title to
copyright in this document will at all times remain with copyright holders.
Open Web Net Protocol
ZigBee
OpenWebNet frames
Brand Item
Legrand 088328
BTicino
Document History
Version Date Author

1.0.0 14/03/2012 My Open Staff
Updating description: FIRST VERSION
Index
DESCRIPTION .................................................................................................................... 4
What: ............................................................................................................................ 5
OPEN WEB NET WHO = 0.................................................................................................. 7
ACTION CONNECTION ...................................................................................................... 8
1.1. Scenario 1 to 32:..................................................................................................... 8
1.2. Start recording X scenario: ..................................................................................... 8
1.3. End recording X scenario: ...................................................................................... 8
1.4. Delete all scenarios: ............................................................................................... 9
1.5. Delete X scenario: .................................................................................................. 9
1.6. Unavailable scenarios Central Unit: ........................................................................ 9
1.7. Memory full of Scenario Central Unit: ..................................................................... 9
OPEN WEB NET WHO = 1................................................................................................ 10
2.1. Light OFF .............................................................................................................. 10
2.2. Light off at X speed: .............................................................................................. 11
2.3. Light on: ................................................................................................................ 11
2.4. Light on at X speed: .............................................................................................. 12
2.5. Light ON at 20%: .................................................................................................. 12
2.6. Light ON at 30%: .................................................................................................. 13
2.7. Light ON at 40%: .................................................................................................. 13
2.8. Light ON at 50%: .................................................................................................. 14
2.9. Light ON at 60%: .................................................................................................. 14
2.10. Light ON at 70%: .................................................................................................. 15
2.11. Light ON at 80%: .................................................................................................. 15
2.12. Light ON at 90%: .................................................................................................. 16
2.13. Light ON at 100%: ................................................................................................ 16
2.15. DIMENSION TABLE: ............................................................................................ 17
2.16. Dimension Part: ........................................................................................................ 17
2.16.1 Light statut request: ............................................................................................. 17
2.16.2. Get/Set dimming level and speed: ................................................................. 17
OPEN WEB NET WHO = 13 .......................................................................................... 18
4.1. Reset Device: .......................................................................................................... 18
4.2. Create Network: ...................................................................................................... 18
4.3. Close Network: ........................................................................................................ 19
4.4. Open Network: ........................................................................................................ 19

4.5. Join Network:........................................................................................................... 19
4.6. Leave Network: ....................................................................................................... 20
4.7. Keep connect: ......................................................................................................... 20
4.8. Scan: ....................................................................................................................... 20
4.9. Supervisor: .............................................................................................................. 20
4.10. DIMENSION TABLE: ................................................................................................ 21
4.12. Dimension Part: .................................................................................................... 21
4.11.1.Mac address: ....................................................................................................... 21
4.11.2. Firmware version: ........................................................................................... 22
4.11.3. Hardware version: .......................................................................................... 22
4.11.4. Who implemented: ......................................................................................... 23
4.11.5. Product information: ....................................................................................... 23
4.11.6. Get number of network product: ..................................................................... 23
4.11.7. Identify:........................................................................................................... 24
4.11.8. Zigbee channel:.............................................................................................. 24
DESCRIPTION
1) Introduction:
The Usb Dongle is a gateway between open web net and Zigbee Legrand private profile
over USB, it allows to interact with Legrand/Bticino Zigbee Devices.
Using a software application connected to port COM, you will be able to manage your
Zigbee installation remotely.
2) Hardware aspects:
The dongle uses an USB connector to make the connection with the PC, and also to
provide the power.
The button is used for several actions in the Zigbee Network (create, open, close, join,
leave).
The two leds indicates to the user the actions:

The green Led: indicates the link activity.
The orange one: indicates the different action made in the network.
3) Serial communication parameters:
The parameters used to communicate with the CP2102 are:
-19200 bauds,
-8 bits
-1 stop bit
-No parity
It is advisable to add a delay of 100ms between 2 requests.
4) Open Web Net remind:
The string transmitted, is the structured with successive fields that progressively specify
the details of the information contained. The following logic is used:
*WHO*WHAT*WHERE##
The OpenWebNet string must start with”*” and must finish by “##”.
4.1. / Who:
The field WHO is the selected function such as Lighting, Automation, and Management.
The table below show admitted WHO value for ZigBee interface.
WHO FUNCTION
0 Scenario
1 Lighting
13 Management
1000 Diagnostic
What:
The field WHAT characterizes an action to do or a status. For every WHO there is a
specific WHAT table.
Where:
It characterizes the set of objects to which the OpenWebNet message is referred. It can be
a single object, a group of objects, a specific environment, the entire system, etc.
In our case the WHERE field is divided into parameters to identify the destination or
sender and the transmission type command.
WHERE = (TX) ADDR (SYS)

 TX:
TX DESCRIPTION
- No parameter, transmission is UNICAST, ADDR is the destination
address
# (Not implemented) The transmission is in MULTICAST, ADDR is the
destination address
0# The transmission is in BROADCAST, ADDR is the UNIT you want to
control. All products do an action on the selected UNIT.
 ADDR:
ADDR is the four last bytes of the MAC address of the product converted in decimal
format + the unit you want to control.
The UNIT is always on 2 length string;
There are two ways to discover this address:
-You can see this ZigBee ID address in front of the product (example: ID000501F8
converted in decimal format = 328184).
-You can discover it after send PRODUCT INFORMATION OpenWebNet command

(see WHO=13 WHAT = 66).
In broadcast mode if you want to send to all units, you have to send unit equal to 00.
 SYS:
SYS is the family type, in our case SYS is always equal to #9 corresponds to ZigBee.
Command / Status Message

*WHO*WHAT*WHERE##
Status Request Message
*#WHO*WHERE##
Acknowledge Message ACK:
*#*1##
None Acknowledge Message NACK:
*#*0##
Example of frame:
Transmission unicast in ZigBee, command light ON and ID = 0x000501F8 (0d328184) and
you want to control the UNIT 2
*1*1*32818402#9##
Transmission unicast in ZigBee, command light ON and ID = 0x000501F8 (0d328184) and
you want to control the all UNIT
*1*1*32818400#9##
Transmission broadcast in ZigBee, command light OFF and you want to control the UNIT
1
*1*0*0#01#9##
Transmission broadcast in ZigBee, command light OFF and you want to control the all
UNIT
*1*0*0#00#9##
OPEN WEB NET WHO = 0

Scenarios
WHAT TABLE
VALUE DESCRIPTION
1 Scenario 1
2 Scenario 2
3 Scenario 3
… …
32 Scenario 32
40#scenario id Start recording scenario (scenario id = 1 to 32)
41#scenario id End recording scenario (scenario id = 1 to 32)
42 Erase all scenario
42#scenario id Erase scenario (scenario id=1 to 32)
… …
45 Unavailable scenarios Central unit
46 Memory full of scenarios Central unit
ACTION CONNECTION
1.1. Scenario 1 to 32:

Action
Open Frame Note
Connection
Scenario = [1 to 32] allow to enable the

Client Server *0*scenario*##
scenario .
ACK if the command is sent to the dongle.

*#*1##
Or
Client Server Or
NACK if the command is not sent to the
*#*0##
dongle.
1.2. Start recording X scenario:

Action
Open Frame Note
Connection
scenario permit to start recording the
Client Server *0*40#scenario*## scenario id.

*#*1##
Or
Client Server Or
*#*0##
dongle.
1.3. End recording X scenario:

Action
Open Frame Note
Connection
scenario permit to end recording the
Client Server *0*41#scenario*## scenario id.

*#*1##
Or
Client Server Or
*#*0##
dongle.
1.4. Delete all scenarios:

Action
Open Frame Note
Connection
*0*42**## Delete all the scenario recorded.
Client Server
*#*1##
Or
Client Server Or
*#*0##
dongle.
1.5. Delete X scenario:

Action
Open Frame Note
Connection
Delete the scenario id = scenario
Client Server *0*42#scenario*##
recorded.
*#*1##
Or
Client Server Or
*#*0##
dongle.
1.6. Unavailable scenarios Central Unit:
Action
Open Frame Note
Connection
Client Server
The scenario can not be supported by The
Client Server *0*45**##
dongle
1.7. Memory full of Scenario Central Unit:

Action Connection Open Frame Note
Client Server
The memory of the dongle is full it can not
Client Server *0*45**##
accept anymore scenario.

Lighting
WHAT TABLE
VALUE DESCRIPTION
0 OFF
0#speed OFF at x speed
1 ON
1#speed ON at x speed
2 20%
3 30%
4 40%
5 50%
6 60%
7 70%
8 80%
9 90%
10 100%
… …
2.1. Light OFF
Action
Open Frame Note
Connection
where is the destination:
if unicast :
where=MAC addr in decimal + UNIT
Client Server *1*0*where#9## if broadcast :
where=0# + UNIT
All UNIT = 00.

*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
where is MAC addr in decimal + UNIT of
Client Server *1*0*where#9##
the controlled actuator address.
2.2. Light off at X speed:

Action
Open Frame Note
Connection
speed is the switching off speed 1-254 the
execution speed is calculated by
multiplying the value by 10ms.
Client Server *1*0#speed*where#9## if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
2.3. Light on:

Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
2.4. Light on at X speed:
Action
Open Frame Note
Connection
speed is the switching off speed 1-254 the
execution speed is calculated by
multiplying the value by 10ms.
Client Server *1*1#speed*where#9## if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
2.5. Light ON at 20%:
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection

Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
Action
Open Frame Note
Connection
if unicast :
Client Server 1*8*where#9##
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
2.13. Light ON at 100%:
Action
Open Frame Note
Connection
if unicast :
if broadcast :
where=0# + UNIT
All UNIT = 00.
*#*1##
Or
Client Server Or
*#*0##
dongle.
Event
Open Frame Note
Connection
2.15.DIMENSION TABLE:
PARAMETER DESCRIPTION
- Light status request
1 Get / Set dimming level and speed
… …
2.16. Dimension Part:
2.16.1 Light statut request:

Action
Open Frame Note
Connection
Client Server *#1*where#9## if unicast :
where=MAC addr in decimal + UNIT.
Client Server *#*0##
dongle.
Event
Open Frame Note
Connection
what is the level for dimmer or state for
On/Off actuator.
Client Server *#1*what*where#9##
2.16.2. Get/Set dimming level and speed:

Action
Open Frame Note
Connection
*#1*where#9*#1*level*spe
Client Server if unicast :
ed##
where=MAC addr in decimal + UNIT.
dongle.
Event
Open Frame Note
Connection
On/Off actuator.
Client Server *#1*what*where#9##

Management
WHAT TABLE
VALUE DESCRIPTION
22 Reset Device
30 Create Network
31 Close Network
32 Open Network
33 Join Network
34 Leave Network
60 Keep connect
65 Scan
66 Supervisor
… …
4.1. Reset Device:

Action
Open Frame Note
Connection
Client Server *13*22*## This command permits to reset the dongle.
Client Server *#*1## ACK before reset.
4.2. Create Network:

Action
Open Frame Note
Connection
This command permits to create the
Client Server *13*30*##
ZigBee network.
**#*1## ACK if the dongle is in a ZigBee network.

Client Server Or Or
*#*0## NACK if the dongle is not in a ZigBee
network.
4.3. Close Network:

Action
Open Frame Note
Connection
This command permits to close the ZigBee
network where the dongle is.
*#*1## ACK if the dongle is in a ZigBee network.

Client Server Or Or
network.
4.4. Open Network:

Action
Open Frame Note
Connection
This command permits to open the ZigBee
network where the dongle is.

Client Server Or Or
network.
4.5. Join Network:

Action
Open Frame Note
Connection
This command permits to join a ZigBee
Client Server *13*33*## network. To join a network, you have to
open it before.

Client Server Or Or
network.
4.6. Leave Network:

Action
Open Frame Note
Connection
This command permits to leave a ZigBee
network.

Client Server Or Or
network.
4.7. Keep connect:

Action
Open Frame Note
Connection
This command permits to know if the
dongle is ready to read commands

Client Server Or Or
network.
4.8. Scan:
Action
Open Frame Note
Connection
*13*65*## This command permits to scan the ZigBee
Client Server
network.

Client Server Or Or
network.
Event
Open Frame Note
Connection
value is the number of product discovered
Client Server *#13**67*value##
in the ZigBee network.
4.9. Supervisor:
This command permits to receive any

Client Server *13*66*## change of product’s state in the ZigBee
network.

Client Server Or Or
network.
4.10. DIMENSION TABLE:
VALUE DESCRIPTION
12 MAC address
16 Firmware version
17 Hardware version
26 Who Implemented
66 Product information
67 Get number of network product
70 Identify
71 ZigBee Channel
… ...
4.12. Dimension Part:
4.11.1.Mac address:
Action
Open Frame Note
Connection
This command permits to have the MAC
Client Server *#13**12##
address of the dongle.
*#*0## NACK if the command is not sent to the
dongle
*#13**12*value1
Client Server
*value2*value3*value4 Value1-6: MAC address in decimal.
*value5*value6##
*#*1##
Event
Open Frame Note
Connection
*#13*where#9*12*value1
On/Off actuator.
Client Server *value2*value3*value4
*value5*value6##
4.11.2. Firmware version:

Action
Open Frame Note
Connection
if where field is null then the command is
*#13*where#9*16## sent for the dongle
Client Server *#*1## if unicast :
UNIT always equal 00 .
*#*0## dongle
.
Client Server Value1: is the firmware version.
*value2*value3## Value2: is the release version.
Value3: is the build version
Event
Open Frame Note
Connection
Client Server
4.11.3. Hardware version:

Action
Open Frame Note
Connection
if unicast :
Client Server *#13*where#9*17##
*#*0## dongle
Client Server *#13*where#9*17*value1 Value1: is the major version.

*value2*value3## Value2: is the minor version.
*#*1## Value3: is the release version
Event
Open Frame Note
Connection
Client Server *value2*value3##
4.11.4. Who implemented:

Action
Open Frame Note
Connection
if unicast :
*#*0## dongle
Client Server *#13*where#9*26*value Value-N : is the who which are

*valueN## implemented in this device..
*#*1##
Event
Open Frame Note
Connection
*#13*where#9*26*value
Client Server
*valueN##
4.11.5. Product information:

Action
Open Frame Note
Connection
*#13**66*value## value is the index of a scanned product.
Client Server
The index started at 0.
*#13*where*66*value## if UNIT equals 0, we don’t know how many
*#*1## units have the product.
Client Server
Value: is the function family if it is known
(Lighting, Automation)
Event
Open Frame Note
Connection
Client Server *#13*where*66*value##
4.11.6. Get number of network product:

Action
Open Frame Note
Connection
This command permits to know how many
products are there in the ZigBee network.
*#13**67*value## value is the number of product discovered.

Client Server
*#*1##
Event
Open Frame Note
Connection
Client Server *#13**67*value## .
4.11.7. Identify:
Action
Open Frame Note
Connection
Only unicast :
Client Server *#13*where#9*70## where=MAC addr in decimal + UNIT
NB : the identified product has it green
light blinking slowly during 5 min.
*#*0##
dongle
Client Server
*#13*where#9*70##
*#*1##
Event
Open Frame Note
Connection
4.11.8. Zigbee channel:

Action
Open Frame Note
Connection
This command permit to know the ZigBee
network channel
NACK if the Dongle is not in a ZigBee
Network.
*#13**71*value1## Value1 : is the number of the channel. [11
Client Server
*#*1## up to 26]
Read only
Event
Open Frame Note
Connection
Client Server
License
By using and/or copying this document, you (the licensee) agree that you have read,
understood, and will comply with the following terms and conditions:
Permission to copy, and distribute the contents of this document, in any medium for any
purpose and without fee or royalty is hereby granted, provided that you include the
following on ALL copies of the document, or portions thereof, that you use:
The copyright notice of the original author, or if it doesn't exist, a notice (hypertext is
preferred, but a textual representation is permitted) of the form: "Copyright © [date-of-
document] www.myopen-legrandgroup.com. All Rights Reserved".
When space permits, inclusion of the full text of this NOTICE should be provided. We
request that authorship attribution be provided in any software, documents, or other items
or products that you create pursuant to the implementation of the contents of this
document, or any portion thereof.
Any contributions to the document (i.e. translation, modifications, improvements, etc) has
to be submitted to and accepted by the My Open staff (using the forum of the community
or sending an email via the www.myopen-legrandgroup.com dedicated section) . Once the
improvement has been accepted the new release will be published in the My Open
Community web site.
.
Disclaimers
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS
OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE
IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY
PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT
OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or
publicity pertaining to this document or its contents without specific, written prior
permission. Title to copyright in this document will at all times remain with copyright
holders.
My Open Web Net Introduction
Brand Item
Legrand 03551
88301
F420
BTicino
IR interface 3456
Document History
Version Date Author

2.0.0 01/10/2010 My Open Staff
Updating description: SECOND VERSION
Index
WHO = 0 SCENARIOS................................................................................................... 3
1. Table WHAT............................................................................................................ 3
2. Table WHERE ......................................................................................................... 3
3. Open messages: commands session ..................................................................... 4
3.1 Scenario activation command (WHAT 1-16/20) ......................................... 4
4. Commands only for Scenarios module F420 .......................................................... 5
4.1 Start recording Scenarios (WHAT 40#1-40#20)......................................... 5
4.2 End recording Scenarios (WHAT 41#1-41#20) .......................................... 6
4.3 Erase all the Scenarios (WHAT 42) ........................................................... 7
4.4 Erase a single Scenario X (WHAT 42#1-42#20) ........................................ 7
4.5 Lock Scenario Central Unit (WHAT 43) ..................................................... 8
4.6 Unlock Scenarios Central Unit (WHAT 44) ................................................ 8
5. Open messages: events sessions........................................................................... 9
5.1 Enable scenarios (WHAT 1-16/20) ............................................................ 9
5.2 Start programming Scenarios (WHAT 40#1 – 40#16)................................ 9
5.3 End programming Scenarios (WHAT 41#1 – 41#16) ............................... 10
5.4 Erase all the Scenarios (WHAT 42) ......................................................... 10
5.5 Erase single scenario X (WHAT 42#1-42#16) ......................................... 10
WHO = 0 SCENARIOS
In this document you can find the Open frames which implement the Scenario scheduling
through the Scenarios modules (F420/ IR 3456).
1. Table WHAT
1 Scenario 1*
2 Scenario 2*
3 Scenario 3*
4 Scenario 4*
… …
16 Scenario 16*
… …**
20 Scenario 20**
Commands only for F420
40#X Start recording X scenario
41#X End recording X scenario
42 Erase all the scenarios
42#X Erase X scenario
43 Lock Scenarios central unit
44 Unlock Scenarios central unit
45 Unavailable Scenarios central unit
46 Memory full of Scenarios central unit
2. Table WHERE
01 Control Panel 01
02 Control Panel 02
… …
99 Control Panel 99
3. Open messages: commands session
3.1 Scenario activation command (WHAT 1-16/20)
Commands session Open frame Notes

WHAT = Enable selected scenario (1-16/20)
WHERE:
TCP/IP
*0*WHAT*WHERE## 01-99 Scenario module Point to Point
Client -> Server
Scenario module on Local Bus

01-99#4#I
(level 4) with Interface I
*#*1##
TCP/IP ACK: the command has been sent to Bus.
or
Server -> Client NACK: the command has not been sent to Bus.
*#*0##
Events session Open frame Notes
TCP/IP
*0*WHAT*WHERE##
Server -> Client
For the module F420 (03551) it is available the configuration up to 16 different

scenarios; on the other side the IR 3456 (88301) interface can handle up to 20
scenarios.
4. Commands only for Scenarios module F420

Whether you have to program the scenario module you have to open a specific connection
with this frame *99*9##
(read the document OpenWebNet_introduction)
4.1 Start recording Scenarios (WHAT 40#1-40#20)
Only with F420 (03551) because the 3456 (88301) module doesn’t support this frame
Enable selected scenario X = (1-16)
WHERE:
TCP/IP
*0*40#X*WHERE## 01-99 Scenario module Point to Point
Client -> Server

01-99#4#I
*#*1##
or
*#*0##
TCP/IP
*0*40#X*WHERE##
Server -> Client
4.2 End recording Scenarios (WHAT 41#1-41#20)
Disable selected scenario X = (1-16)
WHERE:
TCP/IP
*0*41#X *WHERE## 01-99 Scenario module Point to Point
Client -> Server

01-99#4#I
*#*1##
or
*#*0##
TCP/IP
*0*41#X #0*WHERE##
Server -> Client
4.3 Erase all the Scenarios (WHAT 42)
WHERE:
TCP/IP
*0*42 *WHERE## 01-99 Scenario module Point to Point
Client -> Server

01-99#4#I
*#*1##
or
*#*0##
TCP/IP
*0*42 *WHERE##
Server -> Client
4.4 Erase a single Scenario X (WHAT 42#1-42#20)
Erase the selected scenario X = (1-16)
WHERE:
TCP/IP
Client -> Server

01-99#4#I
*#*1##
or
*#*0##
TCP/IP
*0*42#X*WHERE##
Server -> Client
4.5 Lock Scenario Central Unit (WHAT 43)
WHERE:
TCP/IP
*0*43*WHERE## 01-99 Scenario module Point to Point
Client -> Server

01-99#4#I
*#*1##
or
*#*0##
TCP/IP
*0*43*WHERE##
Server -> Client
4.6 Unlock Scenarios Central Unit (WHAT 44)
WHERE:
TCP/IP
Client -> Server

01-99#4#I
*#*1##
or
*#*0##
TCP/IP
*0*44*WHERE##
Server -> Client
5. Open messages: events sessions
5.1 Enable scenarios (WHAT 1-16/20)
For the module F420 (03551) it is available the configuration up to 16 different scenarios;
on the other side the IR 3456 (88301) interface can handle up to 20 scenarios.
Enable selected scenario (1-16)
WHERE:
TCP/IP
*0*WHAT*WHERE## 01-99 Scenario module Point to Point
Server -> Client

01-99#4#I
5.2 Start programming Scenarios (WHAT 40#1 – 40#16)
Start programming the selected scenario
X = (1-16)
WHERE:
TCP/IP
*0*40#WHAT*WHERE## 01-99 Scenario module Point to Point
Server-> Client

01-99#4#I
5.3 End programming Scenarios (WHAT 41#1 – 41#16)
End programming the selected scenario
X =(1-16)
WHERE:
TCP/IP
Server -> Client

01-99#4#I
5.4 Erase all the Scenarios (WHAT 42)
Erase all the scenarios
WHERE:
TCP/IP
Server -> Client

01-99#4#I
5.5 Erase single scenario X (WHAT 42#1-42#16)
Erase the selected scenario X = (1-16)
WHERE:
TCP/IP
Server -> Client

01-99#4#I
NOTES
* In the F420 (03551) it is possible to program up to 16 scenarios.
** In the IR 3456 (88301) it is possible to recall up to 20 different scenarios.
License
.
Disclaimers

REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE
DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION
OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
1
Who = 1
LIGHTING
Version 1.1
My Open Staff
November 17, 2014

www.myopen-legrandgroup.com
Contents
1 Introduction 4
1.1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 WHO 1 6
2.1 WHAT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 DIMENSION Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 WHERE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Allowed OPEN messages Session 8

3.1 Command session - Light Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.1 Turn OFF - What = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.2 Turn ON - What = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.3 ON timed 1 min - What = 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.4 ON timed 2 min - What = 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.5 ON timed 3 min - What = 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.6 ON timed 4 min - What = 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.7 ON timed 5 min - What = 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.8 ON timed 15 min - What = 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.9 ON timed 30 min - What = 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.10 ON timed 0.5 sec - What = 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.11 Blinking on 0.5 sec - What = 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.12 Blinking on 1 sec - What = 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.21 Command translation - What = 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Command session - Dimmer Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.1 Turn OFF - What = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.2 Turn ON - What = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.3 Turn OFF at x SPEED for step - What = 0# . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.4 Turn ON at x SPEED - What = 1# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.5 20% - What = 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.6 30% - What = 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.7 40% - What = 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.8 50% - What = 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.9 60% - What = 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.10 70% - What = 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.11 80% - What = 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.12 90% - What = 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.13 100% - What = 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.14 ON timed 1 min - What = 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.15 ON timed 2 min - What = 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2
CONTENTS
3.2.16 ON timed 3 min - What = 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.2.17 ON timed 4 min - What = 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.18 ON timed 5 min - What = 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.19 ON timed 15 min - What = 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.20 ON timed 30 sec - What = 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2.21 ON timed 0.5 sec - What = 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2.22 Up one level - What = 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2.23 Up of x levels at y SPEED for step - What = 30#x#y . . . . . . . . . . . . . . . . . . . . 17
3.2.24 Down one level - What = 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.25 Down of x levels at y SPEED for step - What = 31#x#y . . . . . . . . . . . . . . . . . . 18
3.3 Status request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.1 Light status request command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.2 Dimmer status request command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Dimension writing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4.1 Set up the level at X speed - Dimension = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4.2 Temporization command - Dimension = 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.4.3 Max working time lamp - Dimension = 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5 Dimension request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.1 Set up the level at X speed - Dimension = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2 Temporization request - Dimension = 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.3 Required Only ON Light - Dimension = 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.4 Working time lamp - Dimension = 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.5.5 Max working time lamp - Dimension = 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6 Event session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6.1 Light status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6.2 Luminous intensity change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6.3 Light temporization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 WHO 14 21
4.1 WHAT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2 WHERE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.1 Command session - Special Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1.1 Disable - What = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1.2 Enable - What = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3
CHAPTER 1. INTRODUCTION
Chapter 1
Introduction
This file is available from http://www.myopen-legrandgroup.com. The purpose of this document is to describe
the Open Web Net Message for WHO = 1 - LIGHTING. In particular, the document contains the "1.1 Abbrevi-
ations" section which describe some terms, with the relative values, used within the open message. The second
chapter, "WHO 1", contains the "WHAT", "DIMENSION" and "WHERE" tables, finally the chapter 3, "Allowed
OPEN messages Session", contains command and event session, status request, dimension writing and request.
1.1 Abbreviations
Name Description Range of Values

<dimmerSpeed> Turn off (or on) the light at a pre- [0-255]:
established speed
• 0 → Last speed used
• from 1 to 254 → Actual speed
• 255 → Default speed
<dimmerLevel10> Dimmer’s level [2-10]:

• 2 → 20%
• 3 → 30%
• 4 → 40%
• 5 → 50%
• 6 → 60%
• 7 → 70%
• 8 → 80%
• 9 → 90%
• 10 → 100%
<dimmerLevel100> The increase of the luminosity [100-200]:

intensity of the light point; ex-
pressed as a percentage value • 100 → Switching off
• 200 → Maximum luminosity in-
tensity
<hour> It indicate show many hours the [0-255]

actuator has to stay ON
4
<min> It indicate show many minutes [0-59]

the actuator has to stay ON
<sec> It indicate show many seconds [0-59]
the actuator has to stay ON
<status> It indicates the status of actuator Status [0-1]:
or dimmer
• 0 → OFF
• 1 → ON
<workingTime> The working time of the device [1-100000]

in hours
5
CHAPTER 2. WHO 1
Chapter 2
WHO 1
2.1 WHAT Table
Value Description
0 Turn off
0#x Turn off at x speed for step
1 Turn on
1#x Turn on at x speed for step
2 20%
3 30%
4 40%
5 50%
6 60%
7 70%
8 80%
9 90%
10 100%
11 ON timed 1 Min
12 ON timed 2 Min
13 ON timed 3 Min
14 ON timed 4 Min
15 ON timed 5 Min
16 ON timed 15 Min
17 ON timed 30 Sec
18 ON timed 0.5 Sec
20 Blinking on 0.5 sec
21 Blinking on 1 sec
30 Up one level
30#x#y Up of x levels at y speed for steep
31 Down one level
31#x#y Down of x levels at y speed for step
1000 It accepts a parameter that is the value of what table
6
CHAPTER 2. WHO 1
2.2 DIMENSION Table
Value Description
1 Set up the level at X speed
2 Temporization
3 Required Only ON Light
4 Status dimmer 100 levels with ON/OFFspeed
8 Working time lamp
9 Max working time lamp
2.3 WHERE Table
Description Value
Interface Int = I3I4:
• I3 = 0; I4 [1 − 9]
• I3 = 1; I4 [1 − 5]
General
• 0 → General of system
• 0#4#<Int>→ General of local bus
Area A [00, 1 − 9, 100]:

• <A>→ Area of private riser
• <A>#4#<Int>→ Area of local bus
Group G [1 − 255]
• #<G>→ Group of private riser

• #<G>#4#<Int>→ Group of local bus
Point to point A; PL:

• A = 00; PL [01 − 15]
• A [1 − 9]; PL [1 − 9]
• A = 10; PL [01 − 15];

• A [01 − 09]; PL [10 − 15]
• <A><PL>→ Point to point of private riser
• <A><PL>#4#<Int>→ Point to point of local bus
7
CHAPTER 3. ALLOWED OPEN MESSAGES SESSION
Chapter 3
Allowed OPEN messages Session
3.1 Command session - Light Frames

3.1.1 Turn OFF - What = 0
Command Open Frame

Client → Server *1*0*<where>##
Server → Client Ack
Event Session Open Frame

Server → Client *1*0*<where>##
3.1.2 Turn ON - What = 1
Command Open Frame


3.1.3 ON timed 1 min - What = 11
Command Open Frame


Server → Client *1*<status>*<where>##
Command Open Frame

8

Command Open Frame


Command Open Frame


Command Open Frame


Command Open Frame


Command Open Frame

9

3.1.10 ON timed 0.5 sec - What = 18
Command Open Frame


3.1.11 Blinking on 0.5 sec - What = 20
Command Open Frame


3.1.12 Blinking on 1 sec - What = 21
Command Open Frame


Command Open Frame


Command Open Frame

10

Command Open Frame


Command Open Frame


Command Open Frame


Command Open Frame


Command Open Frame


11
Command Open Frame


3.1.21 Command translation - What = 1000
Command Open Frame Note

Client → Server *1*1000#<what>*<where>## This command is valid for dim-
mer too

Server → Client *1*1000#<what>*<where>##
3.2 Command session - Dimmer Frames

Command Open Frame


Command Open Frame


Server → Client *1*<dimmerLevel10>*<where>##
3.2.3 Turn OFF at x SPEED for step - What = 0#
Command Open Frame

Client → Server *1*0#<dimmerSpeed>*<where>##

Server → Client *#1*<where>*1*<dimmerLevel100>*<dimmerSpeed>##
12
3.2.4 Turn ON at x SPEED - What = 1#
Command Open Frame

Client → Server *1*1#<dimmerSpeed>*<where>##

13
3.2.5 20% - What = 2
Command Open Frame


3.2.6 30% - What = 3
Command Open Frame


3.2.7 40% - What = 4
Command Open Frame


3.2.8 50% - What = 5
Command Open Frame


3.2.9 60% - What = 6
Command Open Frame


14
3.2.10 70% - What = 7
Command Open Frame


3.2.11 80% - What = 8
Command Open Frame


3.2.12 90% - What = 9
Command Open Frame


3.2.13 100% - What = 10
Command Open Frame


Command Open Frame


15
Command Open Frame


Command Open Frame


Command Open Frame


Command Open Frame


Command Open Frame

16

3.2.20 ON timed 30 sec - What = 17
Command Open Frame


3.2.21 ON timed 0.5 sec - What = 18
Command Open Frame


3.2.22 Up one level - What = 30
Command Open Frame


Server → Client *1*<dimmerLevel10 + 1>*<where>##
3.2.23 Up of x levels at y SPEED for step - What = 30#x#y
Command Open Frame

Client → Server *1*30#<dimmerLevel10>#<dimmerSpeed>*<where>##

17
3.2.24 Down one level - What = 31
Command Open Frame


Server → Client *1*<dimmerLevel10 - 1>*<where>##
3.2.25 Down of x levels at y SPEED for step - What = 31#x#y
Command Open Frame

Client → Server *1*31#<dimmerLevel10>#<dimmerSpeed>*<where>##

3.3 Status request

3.3.1 Light status request command
Command Open Frame

Client → Server *#1*<where>##

3.3.2 Dimmer status request command
Command Open Frame


3.4 Dimension writing

3.4.1 Set up the level at X speed - Dimension = 1
Command Open Frame

Client → Server *#1*<where>#1*<dimmerLevel100><dimmerSpeed>##
18

3.4.2 Temporization command - Dimension = 2
Command Open Frame

Client → Server *#1*<where>*#2*<hour>*<min>*<sec>##

Server → Client *1*<state>*<where>##
Server → Client *#1*<where>*#2*<dimmerLevel100>*<dimmerSpeed>## (only for dimmer)
3.4.3 Max working time lamp - Dimension = 9
Command Open Frame

Client → Server *#1*<where>*#9*<workingTime>##

Server → Client *#1*<where>*#9*<workingTime>##
3.5 Dimension request

3.5.1 Set up the level at X speed - Dimension = 1
Command Open Frame

Client → Server *#1*<where>*1##

3.5.2 Temporization request - Dimension = 2
Command Open Frame


Server → Client *#1*<where>*2*<hour>*<min>*<sec>##
3.5.3 Required Only ON Light - Dimension = 3
Command Open Frame

Server → Client *1*<dimmerLevel10>*<where>## (only if some dimmer is ON)
Server → Client *1*<status>*12<where>## (only if some lights is ON, status=1)
19
3.5.4 Working time lamp - Dimension = 8
Command Open Frame

Server → Client *#1*<where>*8*<workingTime>##

3.5.5 Max working time lamp - Dimension = 9
Command Open Frame


3.6 Event session

3.6.1 Light status

Server → Client *1*<what>*<where>##
3.6.2 Luminous intensity change

3.6.3 Light temporization

Server → Client *#1*<where>*2*<hour>*<min>*<sec>##
20
CHAPTER 4. WHO 14
Chapter 4
WHO 14
4.1 WHAT Table
Value Description
0 Disable
1 Enable
4.2 WHERE Table
Description Value
General
• 0 → General of system
Area A [00, 1 − 9, 100]:

• <A>→ Area
Point to point A; PL:

• <A><PL>→ Point to point
21
Chapter 5
5.1 Command session - Special Commands

5.1.1 Disable - What = 0
Command Open Frame

Event Session Open Frame Note

Server → Client *14*0*<where>## if the command is addressed to
APL there won’t be any answer
in the monitor session.
5.1.2 Enable - What = 1
Command Open Frame


Server → Client *14*1*<where>## if the command is addressed to
APL there won’t be any answer
in the monitor session.
22
License
By using and/or copying this document, you (the licensee) agree that you have read, understood, and will
comply with the following terms and conditions:
Permission to copy, and distribute the contents of this document, in any medium for any purpose and without
fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or
portions thereof, that you use: A link or URL to the www.myopen-legrandgroup.com.
The copyright notice of the original author, or if it doesn’t exist, a notice (hypertext is preferred, but a textual
representation is permitted) of the form: "Copyright c [date-of-document] www.myopen-legrandgroup.com.
All Rights Reserved".
When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship
attribution be provided in any software, documents, or other items or products that you create pursuant to the
implementation of the contents of this document, or any portion thereof.
Any contributions to the document (i.e. translation, modifications, improvements, etc) has to be submit-
ted to and accepted by the My Open staff (using the forum of the community or sending an email via the
www.myopen-legrandgroup.com dedicated section) . Once the improvement has been accepted the new release
will be published in the My Open Community web site.
Disclaimers
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTA-
TIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TI-
TLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT
THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSE-
QUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE
OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to
this document or its contents without specific, written prior permission. Title to copyright in this document
will at all times remain with copyright holders.
23
My Open Web Net Who = 2
Brand Item
Legrand
BTicino
Document History
Version Date Author

2.0.0 16/11/2011 My Open Staff
Updating description: SECOND VERSION
Index
WHO = 2 AUTOMATION ................................................................................................ 3

1. Table WHAT............................................................................................................ 3
2. Table WHERE ......................................................................................................... 4
3. Open messages: commands session ..................................................................... 5
Commands UP / DOWN / STOP (WHAT 0,1,2) ................................................ 5
4. Open messages: Events session ............................................................................ 9
WHO = 2 AUTOMATION
In this document you will find all the Open frames that describe the Automation functions of
a My Home System.
1. Table WHAT
0 STOP
1 UP
2 DOWN
2. Table WHERE
0 General
1 Environment 1
… …
9 Environment 9
11 Automation Point 11
… …
… …
… …
… …
… …
… …
… …
… …
… …
99 Automation point 99
#1 Group 1
#2 Group 2
… …
#9 Group 9
3. Open messages: commands session
Commands UP / DOWN / STOP (WHAT 0,1,2)
Command session Open frame Notes
If the actuator is set in the PUL configuration, the

General or the Environment command can’t be
performed with automation points controlled by the
actuator.
.
If an automation point is disabled the command can’t be
performed.
WHERE:
General command (Every system
0
automation points)
Environment command (only automation

1-9 points belonging to a specific raiser of the
environment)
TCP/IP: Group command (every automation point

*2*[0-2]*WHERE## #1 - #9 belonging to a specific group of the entire
Client -> Server
system)
11 -99 Point to Point command
General command on Local Bus (level 4)

0#4#I
with I interface
Environment command on Local Bus with

1 - 9#4#I
I interface
Group command on Local Bus with I

#1 -#9#4#I
interface
Point to Point command on Local Bus

11 - 99#4#I
with I interface

WHERE = Actuator controller address.
If it is a General, Environment or Group command, on

events connection is sent the same frame as on
command connection.
If it is a General or Environment command, on events

TCP/IP: *2*[0-2]*WHERE## connection is not sent the actuators status.
Server -> Client
If it is a Group command, on events connection, is sent
the status of the actuators belonging to the specified
group.
If it is a Point to Point command, on events connection,

is sent the automation point commanded status.
Automation points status request Command

WHERE:
General request (every system

0
automation points)
Environment request (only automation

1-9 points belonging to the specified raiser of
the environment)
Group request (every automation point

#1 - #9 belonging to the specified group of the
entire system)
TCP/IP: 11 -99 Point to Point request

*#2*WHERE##
Client -> Server
General request on Local Bus (level 4)
0#4#I
with I interface.
Environment request on Local Bus with I

1 - 9#4#I
interface
Group request on Local Bus with I

#1 -#9#4#I
interface
Point to Point request on Local Bus with I

11 - 99#4#I
interface

WHAT = [0-2] (automation point status).
WHERE= [11-99] (automation points address
belonging to the Raiser)
=[11-99#4#I] (automation points address belonging to
the Local Bus)
If a General type request is sent, it returns the

automation points status that belong to Raiser and
possible Local Bus
*2*WHAT*WHERE1##
If an Environment type request is sent, it returns the
…
automation points status that belong to the specified
*2*WHAT*WHEREn##
Environment.
TCP/IP:
If a Group type request is sent, it returns the
Server -> Client
automation points status that belong to specify Group.
*#*1##
If a single point status request is sent, it returns the
o
single automation point status.
*#*0##
If there are no automation points, NACK is return.
If the actuator is set in the PUL configuration, General

Environment or Group command does not return any
answer by the automation points controlled by the
actuator.
If an automation point is disabled, the status is not

sent.
Sessione Eventi Frame Open Note
*2*WHAT*WHERE1##
TCP/IP:
… See upper notes.
Server -> Client
*2*WHAT*WHEREn##
4. Open messages: Events session
WHAT= [0-2] (automation status point)
WHERE = [11-99] automation points

address belong to Raiser;
[11-99#4#I] automation points address
belong to Local Buses.
TCP/IP:
*2*WHAT*WHERE ##
Server -> Client
The frame is sent while an event is
happening, for example the raise of a
shutter.
A frame, sent in the events session,

indicates that the status of the specified
automation point has changed.
License
By using and/or copying this document, you (the licensee) agree that you have read, understood, and
will comply with the following terms and conditions:
Permission to copy, and distribute the contents of this document, in any medium for any purpose and
without fee or royalty is hereby granted, provided that you include the following on ALL copies of
the document, or portions thereof, that you use:
.
Disclaimers

PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT
ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH
CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.
!
!" #$% &
' ( )*
# % +,& - .
""" $. /%
0-1 2 '#1 -,3
!
" #$ !
% & '
( ) * + , - .
+/0 1 2 .
! + 3 1 2 .
&%) 4% 1 2 .
. /11 ( $$ $2 $ $$ 5
. 6 7 5
.! 8 1$ $ 9 $ 5
. ( $ $ 9 $ 5
.. /11 $ $ 9 $
.5 : 1 9 $
. 9 $
.; ( 9 $ ;
. 9 $ ;
5 /11 ( $$ $2 ) $ $$
5 6 $ 1
5! 6 1
5 6 7
5. 4 1 7
55 8 1"
!
!"
# ! $ !"
% &
" & '&
( )
( )
(# )#
(* )*
(+ )+
(, ),
(- )-
(. ).
&/ &/ !
$ 0 !
" & !
# !
* & 0) !
.
! " !
# $ %& & !
0 % 2 < <!< # == # , >= = ? # $ #

1→4
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % < <!< # ==
1 ←
4
' ! % ( % )(
0 % 2 <= ==
1 →4
0 % < <> A ?< # == # , >= = ? # $ # B
1 ←4 C # $ $$ # $ 7 $ $
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % < <> A ?< # ==

1 ←
4
%" %" * ( % )(
0 % 2 <= < # == # , >= = ? # $ #

1 →4
0 % < <> A ?< # == # , >= = ? # $ #
1 ←4 1 $ $ 9 $ $$
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % < <> A ?< # == # , >= = ? # $ #

1 ← C # $ $$ # $ 7 $ $
5
4
" ! " ! % )(
0 % 2 <= < < ==

1 →4
0 % <= < < <0< <(< == 0,) $ : 1 * $ 2: 1-
1 ←4 ,) $ * $ 2/ -
(,) $ ( * $ 2 -
,) $
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % <= < < <0< <(< == 0,) $ : 1 * $ 2: 1-

1 ← ,) $ * $ 2/ -
4 (,) $ ( * $ 2 -
,) $
+ , % )(
0 % 2 <= < < ==

1→4
0 % <= < < <0== 0,) $ : 1 * $ 2: 1-
1 ←4
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % <= < < <0== 0,) $ : 1 * $ 2 1-

1 ←
4
- (%% ! % )(
0 % 2 <= < <!==
1 →4
0 % <= < <!< == ,) $ * $ 2/ -
1 ←4
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % <= < <!< == ,) $ * $ 2/ -

1 ←
4
. % % )(
0 % 2 <= < < ==

1 →4
0 % <= < < <(== (,) $ ( * $ 2 -
1 ←4
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % <= < < <(== (,) $ ( * $ 2 -

1 ←
4
/ ! % * % )(
0 % 2 <= < <.==

1 →4
0 % <= < <.< == ,) $
1 ←4
0 % <=< == <=< == 7 $$ @ $
1 ←4 7 $ $ @ $
0 % <= < <.< == ,) $

1 ←
4
;
+ !" % " !
+ # "
0 % < < < # == # , >= = ? # $ #

1 ←
4
+ # !
0 % < < < # == # , >= = ? # $ #

1 ←
4
+ # $ %&
0 % < <!< # == # , >= = ? # $ #

1 ←
4
+ 0 $ %&
0 % < < < # == # , >= = ? # $ #

1 ←
4
++ ' ! % 10 "!
0 % < <> A ?< # == # , >= = ? # $ #
1 ← C # $ $$ # $ 7 $ $
4
My Open Web Net Who = 4
Brand Item
Legrand
BTicino
Updating history
Version Date Author
1.0.0 05/19/2006 Bticino S.p.A.
Direzione Marketing e Sviluppo Prodotti (Sviluppo Software
Embedded)
Via L. Manara, 4
Erba (CO) Italy
1.0.1 06/07/2012 Bticino S.p.A.
Direzione Marketing e Sviluppo Prodotti (Sviluppo Software
Embedded)
Via L. Manara, 4
Erba (CO) Italy
Updating description:
Added the dimesion = 22
2.0.0 27/11/2013 My Open Staff
Added the dimesion = 11
INDEX
Updating history ................................................................................................................... 2
INDEX .................................................................................................................................. 3
Heating adjustment (WHO = 4) ............................................................................................ 5
1.1 WHAT table: ............................................................................................................ 5
1.2 WHERE table: ......................................................................................................... 6
1.3 DIMENSION table: .................................................................................................. 7
1.4 Allowed OPEN messages Command Session : Zones set up ................................ 8
1.4.1 Manual setting of “N” zone to T temperature ......................................... 8
1.4.2 Set the “N” zone in automatic mode ...................................................... 9
1.4.3 Set the “N” zone in off mode ................................................................ 10
1.4.4 Set the “N” zone in antifreeze mode .................................................... 10
1.4.5 Set the “N” zone in thermal protection mode ....................................... 11
1.4.6 Set the “N” zone in generic protection mode........................................ 12
1.4.7 “N” zone local release probe ................................................................ 13
1.5 Allowed OPEN messages Command Session: Zones dimensions and status
request ........................................................................................................................... 14
1.5.1 “N” zone measures temperature request command ............................ 14
1.5.2 “N” zone set-point temperature adjusts with local offset and operation mode
request command ............................................................................................. 15
1.5.3 “N” zone local offset status request command ..................................... 16
1.5.4 “N” zone set point temperature request command ............................... 18
1.5.5 “N” zone status request command ....................................................... 19
1.5.6 N” zone valves status request command ............................................. 21
1.6 Allowed OPEN messages Command Session: Central Unit set up ...................... 23
1.6.1 Manual setting of central unit to T temperature.................................... 23
1.6.2 Set the central unit in off mode ............................................................ 24
1.6.3 Set central unit in thermal protection ................................................... 26
1.6.4 Set central unit in antifreeze mode ...................................................... 27
1.6.5 Weekly conditioning program activation command ............................. 29
1.6.6 Weekly heating program activation command ..................................... 30
1.6.7 Weekly program activation command (without specific mode) ............ 31
1.6.8 Last set up weekly program activation command ................................ 33
1.6.9 Conditioning scenario activation command.......................................... 35
1.6.10 Heating scenario activation command ............................................. 36
1.6.11 Scenario activation command (without specific mode) .................... 37
1.6.12 Last set up scenario activation command ........................................ 39
1.6.13 (Heating) holiday mode activation command with weekly program return at
midnight 40
1.6.14 (Conditioning) holiday mode activation commend with weekly program
return at midnight ............................................................................................. 42
1.6.15 Holiday mode activation command with weekly program return at midnight
43
1.6.16 (Heating) N days holiday mode activation command with weekly program
return at holiday mode deadline ....................................................................... 45
1.6.17 (Conditioning) N days holiday mode activation command with weekly
program return at holiday mode deadline ......................................................... 47
1.6.18 N days holiday mode activation command with weekly program return at
holiday mode deadline...................................................................................... 49
1.6.19 Holiday mode deactivation command with weekly “N” program return51
1.6.20 Holiday mode deactivation command with last weekly program return52
1.6.21 Set holiday deadline date ................................................................ 54
1.6.22 Set holiday deadline hour ................................................................ 54
1.7 Allowed OPEN messages Command Session: dimensions and status request at
Central Unit .................................................................................................................... 55
1.7.1 “N” zone operation mode request of central unit .................................. 55
1.7.2 Central unit operation mode request command ................................... 55
1.7.3 Holiday deadline date request command ............................................. 57
1.7.4 Holiday deadline hour request command ............................................ 58
1.8 Allowed OPEN messages Monitor Session........................................................... 59
1.8.1 “N” zone measures temperature .......................................................... 59
1.8.2 “N” zone set point temperature adjusts with local offset ...................... 60
1.8.3 “N” zone local offset status .................................................................. 60
1.8.4 “N” zone set point temperature ............................................................ 61
1.9 “N” zone valves status ............................................................................. 62
1.9.1 “N” zone operation mode ..................................................................... 62
1.9.2 Central unit operation mode................................................................. 64
1.9.3 “N” zone operation mode by central unit .............................................. 65
1.10 Frames in order to control Split ......................................................................... 66
1.10.1 Request Split Control (Dimension 22) ............................................. 66
1.10.2 Set control Split (Dimension 22) ...................................................... 67
1.11 Frames to update the staus of the Split ............................................................ 68
1.11.1 Control status split (Dimension 22) .................................................. 68
1.12 Diagnostic of Heating adjustment (WHO=1004) ............................................... 69
1.13 WHERE table .................................................................................................... 69
1.14 DIMENSION table ............................................................................................. 69
1.15 Allowed OPEN messages command session: Diagnostic Request .................. 69
1.15.1 Central unit diagnostic request command ....................................... 69
1.15.2 Zone failure diagnostic request command ....................................... 70
1.15.3 N zone diagnostic request command .............................................. 71
1.15.4 Every zone diagnostic request command ........................................ 71
1.15.5 Failure / not answer zones number request command .................... 72
1.16 Allowed OPEN messages monitor session ....................................................... 73
1.16.1 Central unit diagnostic ..................................................................... 73
1.16.2 Central unit autodiagnostic .............................................................. 73
1.16.3 N zone diagnostic ............................................................................ 73
1.16.4 N zone autodiagnostic ..................................................................... 74
1.16.5 Failure / Not answer zones number ................................................. 74
Heating adjustment (WHO = 4)
1.1 WHAT table:
0 Conditioning Mode
1 Heating Mode
102 Anti Freeze
202 Thermal Protection
302 Protection (generic)
103 OFF – Heating Mode
203 OFF – Conditioning Mode
303 OFF (Generic)
110 Manual-adjustment Mode – Heating
210 Manual-adjustment Mode – Conditioning
310 Manual-adjustment Mode (Generic)
111 Programming Mode – Heating
211 Programming Mode - Conditioning
311 Programming Mode (generic)
115 Holiday daily plan – Heating Mode
215 Holiday daily plan – Conditioning Mode
315 Holiday daily plan
13xxx Vacation scenario for xxx days – Heating mode (Xxx=0…999)
23xxx Vacation scenario for xxx days – Conditioning mode (xxx=0….999)
33xxx Vacation scenario for xxx days (xxx=0….999)
3000 Vacation scenario disabled
11xx Heating program x (x=1…3)
21xx Conditioning program x (x=1…3)
31xx Last activated program
3100 Scenario xx (xx=1…16)
12xx Scenario xx (xx=1...16)
22xx Last activated scenario
32xx Holiday scenario for xxx days – Heating mode (Xxx=0…999)
3200 Holiday scenario for xxx days – Conditioning mode (xxx=0….999)
20 Remote control disabled
21 Remote control enabled
22 At least one probe OFF
23 At least one probe in Anti Freeze
24 At least one probe in Manual
30 Failure discovered
31 Central Unit battery KO
40 Release of sensor local adjustment
1.2 WHERE table:
0 General probes (all probes)

1 Zone 1 master probe
… …
… …
001 All probes (master and slave) belonging to Zone 1
… …
… …
101 Probe 1 of Zone 1
… …
… …
… …
… …
#0 Central Unit
#1 Zone 1 via Central Unit
… …
… …
1.3 DIMENSION table:
0 Measures Temperature R
11 Fan coil Speed R
12 Complete probe status R
13 Local set offset R
14 Set Point temperature R/W
19 Valves status R
20 Actuator Status R
22 Split Control R/W
30 End date Holiday Scenario R/W
1.4 Allowed OPEN messages Command Session : Zones set up
1.4.1 Manual setting of “N” zone to T temperature
Command
Open Frame Note
Session
where = [#1 - #99] Setup zone by
Central Unit.
T = Zone operation temperature not ad
just by local offset.
The T field is composed from 4 digits:
c1c2c3c4, included between “0050” (5°
temperature) and “0400” (40°
temperature).
c1 is always equal to 0, it indicates a
positive temperature.
Tcp/Ip: The c2c3 couple indicates the
*#4*where*#14*T*M##
Client  Server temperature values between [05° - 40°].
c4 indicates the decimal Celsius degree
by 0.5° step.
M = operation mode
1  heating mode
2  conditional mode
3  generic mode
Example:
You set up 10 zone at 21.5°C in heating
mode: *#4*#10*#14*0215*1##
TCP/IP: ACK if command is sent to Bus.
*#*1## or *#*0##
ClientServer NACK if command is not sent to Bus.
Monitor Session Open Frame Note
*#4*where*0*T## N zone’s temperature acquire frame:
where = [1-99]
T = Zone operation temperature not
adjust by local offset.
Tcp/Ip
temperature).
Client monitor 
Server
The c2c3 couple indicates the
temperature values between [00° - 50°].
c4 indicates the decimal Celsius degree
by 0.1° step.
*4*what*where##
“N” zone operation mode by central unit

frame:
where = [#1 - #99] Setup zone by
Central Unit.
what =
110  Manual heating
210  Manual Conditioning
310 Manual Generic
1.4.2 Set the “N” zone in automatic mode
Command
Open Frame Note
Session
Tcp/Ip: where = [#1 - #99] Setup zone by Central
*4*311*#where##
Client  Server Unit.
*#*1## or *#*0##
frame:
where = [#1-#99]
what =
111  Automatic heating
211  Automatic Conditioning
311  Automatic Generic
*4*what*where##
N zone’s temperature acquire frame:
where = [1-99]
Tcp/Ip
Client monitor 
Server
*#4*where*0*T##
temperature).
The c2c3 couple indicates the temperature
values between [00° - 50°].
c4 indicates the decimal Celsius degree by
0.1° step.
1.4.3 Set the “N” zone in off mode
Command
Open Frame Note
Session
*4*303*where##
*#*1## or *#*0##
where = [1-99].

frame:
where = [#1-#99]
what =
103  Off Heating
203  Off Conditioning
*4*303*where##
“N” zone’s temperature acquire frame:
*4*what*where## (ONLY IF THE PROBE IS SET UP WITH
LOCAL OFFSET DIFFERENT FROM
Tcp/Ip
ZERO):
Client monitor 
where = [1-99]
Server
*#4*where*0*T## c1c2c3c4, included between “0000” (0°
temperature).
0.1° step.
1.4.4 Set the “N” zone in antifreeze mode
Command
Open Frame Note
Session
where = [#1 - #99] Setup zone by Central
Tcp/Ip: Unit.
*4*102*where##
Client  Server If Central Unit is set up in Conditioning
mode, this command does not run.
*#*1## or *#*0##

“N” zone status / operation mode frame:
where = [1-99]
what =
102  Antifreeze
303  Generic OFF

Unit.
*4*what*where##
(ONLY IF THE PROBE IS SET UP WITH
Tcp/Ip
ZERO):
Client monitor  where = [1-99]
Server
*4*102*where## T = Zone operation temperature not ad
temperature).
0.1° step.
1.4.5 Set the “N” zone in thermal protection mode
Command
Open Frame Note
Session
Tcp/Ip: Unit.
*4*202*where##
Client  Server If Central Unit is set up in Heating mode,
this command does not run.
*#*1## or *#*0##
*4*what*where## “N” zone status / operation mode frame:
where = [1-99]
what =
Tcp/Ip 202  Thermal Protection
Client monitor  303  Generic OFF
Server
*4*202*where## where = [#1 - #99] Setup zone by Central
Unit.
*#4*where*0*T## N zone’s temperature acquire frame:

ZERO):
where = [1-99]
temperature).
0.1° step.
1.4.6 Set the “N” zone in generic protection mode
Command
Open Frame Note
Session
*4*302*where##
*#*1## or *#*0##
“N” zone status / operation mode frame:
where = [1-99]
what =
*4*what*where## 102  Antifreeze
302  Thermal Protection
303  Generic OFF

Unit.
Tcp/Ip
what =
Client monitor 
*4*what*where## 102  Antifreeze
Server

*#4*where*0*T## ZERO):
where = [1-99]

temperature).
0.1° step.
1.4.7 “N” zone local release probe
Command
Open Frame Note
Session
Tcp/Ip: where = [1-99]
*4*40*where##
Client  Server
*#*1## or *#*0##
where = [1-99]
what =
0  Conditioning
1  Heating
102  Antifreeze
303  Generic OFF
*4*what*where## N zone’s temperature acquire frame:

Tcp/Ip ZERO):
Server T = Zone operation temperature not ad
temperature).
0.1° step.
1.5 Allowed OPEN messages Command Session: Zones

dimensions and status request
1.5.1 “N” zone measures temperature request command
Command
Open Frame Note
Session
Master probe temperature request:
where = [1-99]
Slave probe temperature request:

where = [1-8]+[01-99]
All slave probes temperature request:

where = 0+[01-99]
Tcp/Ip:
*#4*where*0##
Client  Server Examples:
“1” zone temperature request:
*#4*1*0##
“1” zone’s “3” slave probe temperature
request:
*#4*301*0##
“1” zone’s all slave probes temperature
request:
*#4*001*0##
Master probe N zone’s temperature
acquire frame:
where = [1-99]
“S” Slave probe N zone’s temperature

acquire frame:
where = S+N = [1-8]+[1-99]
T = Zone operation temperature not adjust

by local offset.
Tcp/Ip
Client  Server
temperature).
0.1° step.
If is required the all slave probes’
temperature, we will get the same number
of frames as number of slave probes are.
Example:
“1” zone’ temperature acquired is 20,5°C:
*#4*1*0*0205##
“3” zone’ temperature acquired is 27,0°C:
*#4*301*0*0270##
ACK If received almost one request
Tcp/Ip answer
*#*1## or *#*0##
Client  Server NACK if not received answer or if the
frame is not sent.
Tcp/Ip
*#4*where*0*T##
Client monitor  See upper comment.
Server
1.5.2 Speed of the Fan Coil
Command
Open Frame Note
Session
Tcp/Ip: where = [1-99].
*#4*where*11##
Client  Server
Speed:
 0 = Auto
Tcp/Ip  1 = vel 1
*#4*where*11*speed*##
Client  Server  2 = vel2
 3 = vel3
 15 = OFF
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*#4*where*11*speed*##
Server
1.5.3 “N” zone set-point temperature adjusts with local offset and operation mode request
command
Command
Open Frame Note
Session
Tcp/Ip: where = [1-99].
*#4*where*12##
Client  Server
where = [1-99]
T = Zone operation temperature with
*#4*where*12*T*3##
temperature).
Tcp/Ip values between [02° - 43°].
Client  Server c4 indicates the decimal Celsius degree by
0.1° step.
Zone operation mode acquire frame:

where = [1-99]
what =
*4*what*where##
0  Conditioning
1  Heating
102  Antifreeze
303  Generic OFF
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*#4*where*12*T*3##
*4*what*where##
Server
1.5.4 “N” zone local offset status request command
Command
Open Frame Note
Session
*#4*where*13##
Client  Server
where = [1-99]
OL = Local Offset (knob status):
00  knob on 0
01  knob on +1 (degree)
11  knob on -1 (degree)
Tcp/Ip *#4*where*13*OL## 02  knob on +2 (degree)
Client  Server 12  knob on -2 (degree)
4  knob on Local OFF
5  knob on Local protection

Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*#4*where*13*OL##
Server
1.5.5 “N” zone set point temperature request command
Command
Open Frame Note
Session
*#4*where*14##
Client  Server
where = [1-99]
T = n zone set point temperature.
Tcp/Ip *#4*where*14*T*3## temperature).
Client  Server c1 is always equal to 0, it indicates a
0.1° step.
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*#4*where*14*T*3##
Server
1.5.6 “N” zone status request command
Command
Open Frame Note
Session
*#4*where##
Client  Server
Tcp/Ip *#4*where*0*T## where = [1-99]
Client  Server T = Zone operation temperature not adjust
by local offset.
temperature).
0.1° step.
*#4*where*12*T*3##
Zone operation temperature with adjust by
local offset frame:
where = [1-99]
temperature).
0.1° step.
*4*what*where##

where = [1-99]
what =
0  Conditioning
1  Heating
102  Antifreeze
*#4*where*13*OL## 303  Generic OFF
Local offset acquire frame:

where = [1-99]
00  knob on 0
*#4*where*14*T*3## 5  knob on Local protection
Set-point temperature acquire frame:

where = [1-99]
T = N zone set point temperature.
temperature).
0.1° step.

Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
*#4*where*12*T*3##
Tcp/Ip
*4*what*where##
*#4*where*13*OL##
Server
*#4*where*14*T*3##
1.5.7 N” zone valves status request command
Command
Open Frame Note
Session
Tcp/Ip:
*#4*where*19## where = [1-99]
Client  Server
where = [1-99]
CV, HV = Valves’ status, CV: Conditioning
Valve and HV: Heating Valve
CV, HV = 0  OFF
CV, HV = 1  ON
Tcp/Ip *#4*where*19*CV*HV## CV, HV = 2  Opened
Client  Server CV, HV = 3  Closed
CV, HV = 4  Stop
CV, HV = 5  OFF Fan Coil
CV, HV = 6  ON speed 1
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*#4*where*19*CV*HV##
Server
1.5.8 Actuator status
Command
Open Frame Note
Session
where =
 Actuators N of zone Z
[Z#N] = [0-99#1-9]
Tcp/Ip:
*#4*where*20##  All the actuators of zone F
Client  Server
[Z#0]
 All the actuators
[0#0]
Where= see upper comments
Val=
 0= OFF
 1= ON
 2= Opened
 3= Closed
Tcp/Ip *#4*where*20*Val##
 4= Stop
Client  Server
 5= Off Fan Coil
 6= ON Vel 1
 7= ON Vel 2
 8= ON Vel 3
 9= ON Fan Coil

Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*#4*where*20*Val##
Server
1.6 Allowed OPEN messages Command Session: Central Unit

set up
1.6.1 Manual setting of central unit to T temperature
Command
Open Frame Note
Session
T = set point temperature by Central Unit
temperature).
Tcp/Ip:
*#4*#0*#14*T*M## The c2c3 couple indicates the temperature
Client  Server
0.5° step.
M = operation mode
1  heating mode
2  conditional mode
3  generic mode
*#*1## or *#*0##
*4*what#T*#0## what =
110  Manual mode - Heating
210  Manual mode - Conditioning
T = Central Unit operation temperature
temperature).
Tcp/Ip The c2c3 couple indicates the temperature
Client monitor  values between [00° - 50°].
Server c4 indicates the decimal Celsius degree by
0.1° step.
*4*[20-21]*#0##
This frame indicates the Remote control
status:
what =
20  Remote control disabled
*4*what1*#0## 21  Remote control enabled
…
*4*whatn*#0## This optional frame indicates the system
status:
what =
22  At least one probe OFF
23  At least one probe in protection
24  At least one probe in manual
*4* what* where1## 30  Failure discovered
… 31  Central Unit battery KO
*4* what* wheren##
This optional frame indicates the changing
status’s zone
where = [1-99]
what =
*#4*where1*0*T## 0  Conditioning
… 1  Heating
*#4*wheren*0*T##
This frame indicates the all zone
temperature’s acquired:
where = [1-99]
temperature).
0.1° step.
1.6.2 Set the central unit in off mode
Command
Open Frame Note
Session
Tcp/Ip:
*4*303*#0##
Client  Server
*#*1## or *#*0##
*4*[20-21]*#0## This frame indicates the Remote control
status:
what =
Tcp/Ip 20  Remote control disabled
Client monitor  21  Remote control enabled
Server *4*what1*#0##
… This optional frame indicates the system
*4*whatn*#0## status:
what =

30  Failure discovered
31  Central Unit battery KO
103  OFF Heating
*4*303* where1## 203  OFF Conditioning
…
*4*303* wheren# where = [1-99]
*#4*where1*0*T##
…
*#4*wheren*0*T## The follows frames are displayed only if
the local offset’s probe is different from 0:
where = [1-99]
temperature).
*#4* where1*12*T*3## c4 indicates the decimal Celsius degree by
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.3 Set central unit in thermal protection
Command
Open Frame Note
Session
Tcp/Ip: If Central Unit is set up in Heating mode,
*4*202*#0##
Client  Server this command does not run.
*#*1## or *#*0##
*4*202*#0##
*4*[20-21]*#0##
status:
what =
21  Remote control enabled
*4*what1*#0##
…
This optional frame indicates the system
*4*whatn*#0##
status:
what =
*4* what* where1##
…
*4* what* wheren##
Tcp/Ip This optional frame indicates the changing
Client monitor  status’s zone
Server where = [1-99]
what =
*4*what* where1##
0  Conditioning
…
*4*what* wheren##
where = [1-99]
what =
*#4*where1*0*T##
303  Generic OFF
…
*#4*wheren*0*T##
The follows frames are displayed only if
where = [1-99]
temperature).

*#4* where1*12*T*3## values between [00° - 50°].
… c4 indicates the decimal Celsius degree by
*#4* wheren*12*T*3## 0.1° step.
where = [1-99]
temperature).
0.1° step.
1.6.4 Set central unit in antifreeze mode
Command
Open Frame Note
Session
Tcp/Ip: If Central Unit is set up in Conditioning
*4*102*#0##
Client  Server mode, this command does not run.
*#*1## or *#*0##
*4*102*#0##
*4*[20-21]*#0##
status:
what =
*4*what1*#0##
Tcp/Ip
…
Client monitor  This optional frame indicates the system
*4*whatn*#0##
Server status:
what =
*4* what* where1##
…
*4* what* wheren##

status’s zone
where = [1-99]
*4*what* where1## what =
… 1  Heating
*4*what* wheren##
where = [1-99]
what =
*#4*where1*0*T## 102  Antifreeze
… 303  Generic OFF
*#4*wheren*0*T##
The follows frames are displayed only if
where = [1-99]
temperature).
*#4* wheren*12*T*3## 0.1° step.
where = [1-99]
temperature).
0.1° step.
1.6.5 Weekly conditioning program activation command
Command
Open Frame Note
Session
If Central Unit is set up in Heating mode,
Tcp/Ip: this command does not run.
Client  Server what = [2101 – 2103] set in program.
*4*what*#0##
*#*1## or *#*0##
*4*what*#0##
what = [2101 – 2103] set in program.
*4*what*#0##
status:
what =
*4*what1*#0##
…
*4*whatn*#0##
status:
what =
*4* what* where1##
…
*4* what* wheren##
Tcp/Ip This optional frame indicates the changing
Client monitor  status’s zone
Server where = [1-99]
what =
*#4*where1*0*T##
0  Conditioning
…
*#4*wheren*0*T##
where = [1-99]
temperature).
*#4* where1*12*T*3##
…
0.1° step.
*#4* wheren*12*T*3##
This frame is displayed only if the local

offset’s probe is different from 0:
where = [1-99]
temperature).
0.1° step.
1.6.6 Weekly heating program activation command
Command
Open Frame Note
Session
If Central Unit is set up in Conditioning
Tcp/Ip: mode, this command does not run.
Client  Server *4*what*#0## what = [1101 – 1103] set in program.

*#*1## or *#*0##
*4*what*#0## what = [1101 – 1103] set in program.
*4*what*#0## This frame indicates the Remote control

status:
what =
*4*what1*#0##
Tcp/Ip *4*whatn*#0# status:
Client monitor  what =
Server 22  At least one probe OFF
*4* what* where1## 31  Central Unit battery KO
…
*4* what* wheren## This optional frame indicates the changing
status’s zone:
where = [1-99]
what =
*#4*where1*0*T## 1  Heating
…
*#4*wheren*0*T## where = [1-99]
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.7 Weekly program activation command (without specific mode)
Command
Open Frame Note
Session
Tcp/Ip: *4*what*#0## what = [3101 – 3103] set in program.
Client  Server
*#*1## or *#*0##
*4*what*#0## what = [3101 – 3103] set in program.
Tcp/Ip *4*what*#0## This frame indicates the Remote control

Client monitor  status:
Server what =
*4*what1*#0##
what =
…
status’s zone:
where = [1-99]
what =
0  Conditioning
…
*#4*wheren*0*T## where = [1-99]
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.8 Last set up weekly program activation command
Command
Open Frame Note
Session
Tcp/Ip: *4*3100*#0##
Client  Server
*#*1## or *#*0##
*4*what*#0## If Central Unit is set in Heating mode:
If Central Unit is set in Conditioning mode:

status:
what =
*4*what1*#0##
what =
Tcp/Ip
…
Client monitor 
Server
status’s zone:
where = [1-99]
what =
0  Conditioning
…
*#4*wheren*0*T## where = [1-99]
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.9 Conditioning scenario activation command
Command
Open Frame Note
Session
Tcp/Ip: *4*what*#0##
Client  Server
what = [2201-2216]
*#*1## or *#*0##
what = [2201 – 2216] scenario set in.
*4*what*#0##
*4*what*#0## status:
what =
*4*what1*#0## This optional frame indicates the system

… status:
*4*whatn*#0## what =
*4* what* where1##
… This optional frame indicates the changing
Tcp/Ip *4* what* wheren## status’s zone:
Server what =
0  Conditioning
*#4*where1*0*T##
… where = [1-99]
*#4*wheren*0*T## T = Zone operation temperature not ad
temperature).
*#4* where1*12*T*3## 0.1° step.
…
*#4* wheren*12*T*3## This frame is displayed only if the local
where = [1-99]
temperature).
0.1° step.
1.6.10 Heating scenario activation command
Command
Open Frame Note
Session
Tcp/Ip:
*4*what*#0## mode, this command does not run.
Client  Server what = [1201-1216]
*#*1## or *#*0##
*4*what*#0## what = [1201 – 1216] scenario set in.

status:
what =
*4*what1*#0##
what =
Tcp/Ip
Client monitor 
Server
…
status’s zone:
where = [1-99]
what =
…
*#4*wheren*0*T## where = [1-99]

temperature).
… 0.1° step.
*#4* wheren*12*T*3##
offset’s probe is different from 0
where = [1-99]
temperature).
0.1° step.
1.6.11 Scenario activation command (without specific mode)
Command
Open Frame Note
Session
Tcp/Ip: what = [3201 – 3216]
*4*what*#0##
Client  Server
*#*1## or *#*0##
Tcp/Ip
Client monitor  *4*what*#0## This frame indicates the Remote control
Server status:
what =
*4*what1*#0##

what =
…
status’s zone
where = [1-99]
what =
0  Conditioning
…
*#4*wheren*0*T## where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.12 Last set up scenario activation command
Command
Open Frame Note
Session
Tcp/Ip:
*4*3200*#0##
Client  Server
*#*1## or *#*0##

status:
what =
*4*what1*#0##
what =
Tcp/Ip
…
Client monitor 
Server
status’s zone:
where = [1-99]
what =
0  Conditioning
…
*#4*wheren*0*T## where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.13 (Heating) holiday mode activation command with weekly program return at midnight
Command
Open Frame Note
Session
Tcp/Ip:
*4*what*#0## what = 115#parameter
Client  Server parameter = [1101 – 1103] returned
program
*#*1## or *#*0##
*4*what*#0##
what = 115#[1 – 3] (example: if the 1103
program is selected, number 3 is returned)
*4*what*#0##
status:
what =
Tcp/Ip *4*what1*#0##
Client monitor  …
Server *4*whatn*#0##
status:
what =
*4* what* where1##
…
*4* what* wheren##

status’s zone
where = [1-99]
*#4*where1*0*T## what =
… 1  Heating
*#4*wheren*0*T##
where = [1-99]
by local offset.
temperature).
*#4* wheren*12*T*3## 0.1° step.

where = [1-99]
temperature).
0.1° step.
1.6.14 (Conditioning) holiday mode activation commend with weekly program return at
midnight
Command
Open Frame Note
Session
Tcp/Ip:
*4*what*#0## what = 215#parameter
Client  Server
parameter = [2101 – 2103] returned
program
*#*1## or *#*0##
*4*what*#0##
what = 215#[1 – 3] (example: if the 2103
*4*what*#0##
status:
what =
*4*what1*#0##
…
*4*whatn*#0##
status:
what =
*4* what* where1##
Tcp/Ip 31  Central Unit battery KO
…
Client monitor 
*4* what* wheren##
Server This optional frame indicates the changing
status’s zone:
where = [1-99]
what =
*#4*where1*0*T##
0  Conditioning
…
*#4*wheren*0*T##
where = [1-99]
by local offset.
temperature).
*#4* where1*12*T*3##

*#4* wheren*12*T*3## 0.1° step.

where = [1-99]
temperature).
0.1° step.
1.6.15 Holiday mode activation command with weekly program return at midnight
Command
Open Frame Note
Session
what = 315#parameter
Tcp/Ip:
*4*what*#0## parameter = [3101 – 3103] returned
Client  Server
program
*#*1## or *#*0##
*4*what*#0## If it is Heating mode: what =
o 115#parameter
*4*what*#0##
If it is Conditioning mode: what =
215#parameter
parameter = [1 – 3] (example: if the 2103

Tcp/Ip *4*what*#0##
Client monitor  This frame indicates the Remote control
Server status:
what =
*4*what1*#0## 21  Remote control enabled
…
*4*whatn*#0## This optional frame indicates the system
status:
what =

*4* what* where1## 30  Failure discovered
… 31  Central Unit battery KO
*4* what* wheren##
status’s zone:
where = [1-99]
what =
*#4*where1*0*T## 0  Conditioning
… 1  Heating
*#4*wheren*0*T##
where = [1-99]
by local offset.
temperature).
*#4* wheren*12*T*3## 0.1° step.

where = [1-99]
temperature).
0.1° step.
1.6.16 (Heating) N days holiday mode activation command with weekly program return at
holiday mode deadline
Command
Open Frame Note
Session
what = parameter1#parameter2
parameter1 = [13001-13255] Holiday days
from 1 to 255
Tcp/Ip:
*4*what*#0## parameter2 = [3101-3103] returned
Client  Server
program from 1 to 3
Example:
Enable 2 days holiday (without the current
day) with number 3 weekly program return
*4*13002#3103*#0##
*#*1## or *#*0##
*4*what*#0## what = parameter1+1 Day (it is also
included the current day)
Example:
As Previous example explains, the holiday
days are 3 because it is considered the
current day.
*4*13003*#0##

status:
what =
*4*what1*#0##
Tcp/Ip
Client monitor 
Server
what =
…
status’s zone:
where = [1-99]
what =
*4*what* where1## 1  Heating
…
*4*what* wheren## where = [1-99]
what =
*#4*where1*0*T## 303  Generic OFF
…
*#4*wheren*0*T## This frame is displayed only if the local
where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.17 (Conditioning) N days holiday mode activation command with weekly program
return at holiday mode deadline
Command
Open Frame Note
Session
from 1 to 255
Tcp/Ip:
*4*what*#0## parameter2 = [3101-3103] returned
Client  Server
program from 1 to 3
Example:
*4*23002#3103*#0##
*#*1## or *#*0##
Example:
current day.
*4*23003*#0##

status:
what =
*4*what1*#0##
Tcp/Ip
Client monitor 
Server
what =
…
status’s zone
where = [1-99]
what =
*4*what* where1## 0  Conditioning
…
what =
102  Antifreeze
303  Generic OFF
*#4*where1*0*T##
…
where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.18 N days holiday mode activation command with weekly program return at holiday
mode deadline
Command
Open Frame Note
Session
from 1 to 255
parameter2 = [3101-3103] returned
Tcp/Ip:
*4*what*#0## program from 1 to 3
Client  Server
Example:
*4*33002#3103*#0##
*#*1## or *#*0##
Example:
current day.
*4*33003*#0##

status:
what =
*4*what1*#0##
Tcp/Ip
Client monitor 
what =
Server
…
status’s zone:
where = [1-99]
what =
0  Conditioning
*4*what* where1## 1  Heating
…
what =
102  Antifreeze
*#4*where1*0*T## 303  Generic OFF
…
where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.19 Holiday mode deactivation command with weekly “N” program return
Command
Open Frame Note
Session
Tcp/Ip: *4*3000#what*#0## what = [3101 – 3103]
Client  Server
*#*1## or *#*0##
*4*what*#0## what = [3101 – 3103] weekly program.

status:
what =
*4*what1*#0##
what =
*4* what*where1## 31  Central Unit battery KO
…
*4* what*wheren## This optional frame indicates the changing
status’s zone
Tcp/Ip
where = [1-99]
Client monitor 
what =
Server
0  Conditioning
…
*#4*wheren*0*T## where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.20 Holiday mode deactivation command with last weekly program return
Command
Open Frame Note
Session
Tcp/Ip:
*4*3000*#0##
Client  Server
*#*1## or *#*0##
*4*what*#0## what = [2101 – 2103] weekly program in
case of it is in Conditioning mode.
or
what = [1101 – 1103] weekly program in
case of it is in Heating mode.

status:
what =
Tcp/Ip *4*what*where1##
Client monitor  … This optional frame indicates the changing
Server *4*what*wheren## status’s zone:
what =
0  Conditioning
1  Heating
where = [1-99]
*4*what1*#0##
what =
*#4*where1*0*T## 31  Central Unit battery KO
…
*#4*wheren*0*T## where = [1-99]
by local offset.
temperature).
… 0.1° step.
*#4* wheren*12*T*3##
where = [1-99]
temperature).
0.1° step.
1.6.21 Set holiday deadline date
Command
Open Frame Note
Session
parameter = Day*Month*Year
Day = [01-31]
Tcp/Ip: *#4*#0*#30*parameter## Month = [01-12]
Client  Server Year = [2000-2099]
Example: 12 June 2005 is holiday end date
*#4*#0*#30*12*06*2005##
*#*1## or *#*0##
Tcp/Ip
Client monitor  *#4*#0*30*parameter## See upper comment.
Server
1.6.22 Set holiday deadline hour
Command
Open Frame Note
Session
parameter = Hour*Minutes
Hour = [00-23]
Tcp/Ip:
*#4*#0*#31*parameter## Minutes = [00-59]
Client  Server
Example: 8:59 is holiday end time
*#4*#0*#31*08*59##
*#*1## or *#*0##
Tcp/Ip
Server
1.7 Allowed OPEN messages Command Session: dimensions

and status request at Central Unit
1.7.1 “N” zone operation mode request of central unit
Command
Open Frame Note
Session
where = [#1 - #99] Request zone by
Tcp/Ip:
*#4*where## Central Unit.
Client  Server
Central Unit.
what =
110  Manual Heating
Tcp/Ip *4*what*#where##
111  Automatic Heating
Client  Server
103  Off Heating
102  Antifreeze
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
*4*what*#where##
Server
1.7.2 Central unit operation mode request command
Command
Open Frame Note
Session
Tcp/Ip:
*#4*#0##
Client  Server
status:
what =
Tcp/Ip
*4*what1*#0##
Client  Server
what =

*4*what*#0## 30  Failure discovered
This frame indicates the Central Unit’s

operation mode, the what field can
assume one of the follow values:
what =
110#T  Manual Heating
210#T  Manual Conditioning
103  Off Heating
102  Antifreeze
115#parameterH  Holiday Heating
215#parameterC  Holiday Conditioning
parameterH = [1101-1103]
parameterC = [2101-2103]
[13001-13255]  Holiday days in Heating
mode
[23001-23255]  Holiday days in
Conditioning mode
[1101-1103]  Memo program in Heating
mode
[2101-2103]  Memo program in
Conditioning mode
[1201-1216]  Memo scenario in Heating
mode
[2201-2216]  Memo scenario in
Conditioning mode

with adjust by local offset.
temperature).
0.1° step.
ACK If received almost one request answer
Tcp/Ip
*#*1## or *#*0## NACK if not received answer or if the frame is
Client  Server not sent.
Tcp/Ip *4*what*#0## See upper comment.
Client monitor 
Server *4*what1*#0##
…
*4*whatn*#0##
*4*what*#0##
1.7.3 Holiday deadline date request command
Command
Open Frame Note
Session
Tcp/Ip:
*#4*#0*30##
Client  Server
parameter = Day*Month*Year
Day = [01-31]
Month = [01-12]
Tcp/Ip
*#4*#0*30*parameter## Year = [2000-2099]
Client  Server
Example: 12 June 2007 is holiday end
date
*#4*#0*#30*12*06*2007##
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
Server
1.7.4 Holiday deadline hour request command
Command
Open Frame Note
Session
Tcp/Ip:
*#4*#0*31##
Client  Server
parameter = Hour*Minutes
Hour = [00-23]
Tcp/Ip
*#4*#0*31*parameter## Minutes = [00-59]
Client  Server
Example: 8:59 is holiday end time
*#4*#0*#31*08*59##
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
Server
1.8 Allowed OPEN messages Monitor Session
1.8.1 “N” zone measures temperature

“N” zone’s Master probe temperature
acquire:
where = [1-99]
“N” zone’s “S” slave probe temperature

acquire:
where = S+N = [1-8]+[1-99]

by local offset.
Tcp/Ip
Client monitor  *#4*where*0*T##
temperature).
Server
0.1° step.
Example:
“1” zone’s temperature acquired is 20,5°C:
*#4*1*0*0205##
“3” zone’s temperature acquired is 27,0°C:
*#4*301*0*0270##
1.8.2 Speed Fan Coil

Speed:
 0 = Auto
Tcp/Ip  1 = vel 1
*#4*where*11*speed##
Client  Server  2 = vel2
 3 = vel3
 15 = OFF
1.8.3 “N” zone set point temperature adjusts with local offset

Temperature with adjust by local offset
acquire frame:
where = [1-99]
Tcp/Ip
*#4*where*12*T*3## temperature) and “0430” (43°
Client  Server
temperature).
0.1° step.
1.8.4 “N” zone local offset status

Local offset acquire frame:
where = [1-99]
00  knob on 0
Tcp/Ip 11  knob on -1 (degree)
*#4*where*13*OL##
Client  Server 02  knob on +2 (degree)
5  knob on Local protection
1.8.5 “N” zone set point temperature

where = [1-99]
T = N zone set point temperature.
Tcp/Ip *#4*where*14*T*3## temperature).
Client  Server c1 is always equal to 0, it indicates a
0.1° step.
1.9 “N” zone valves status

where = [1-99]
CV, HV = Valves’ status, CV: Conditioning
Valve and HV: Heating Valve
CV, HV = 0  OFF
CV, HV = 1  ON
Tcp/Ip CV, HV = 2  Opened
*#4*where*19*CV*HV## CV, HV = 3  Closed
Client  Server
CV, HV = 4  Stop
CV, HV = 5  OFF Fan Coil
1.9.1 Actuator Status

where =
 Actuators N of zone Z
[Z#N] = [0-99#1-9]
 All the actuators of zone F
[Z#0]
 All the actuators
[0#0]
Val=
Tcp/Ip  0= OFF
*#4*where*20*Value## 
Client  Server 1= ON
 2= Opened
 3= Closed
 4= Stop
 5= Off Fan Coil
 6= ON Vel 1
 7= ON Vel 2
 8= ON Vel 3
 9= ON Fan Coil
1.9.2 “N” zone operation mode

where = [1-99]
what =
Tcp/Ip 0  Conditioning
*4*what*where##
Client  Server 1  Heating
102  Antifreeze
303  Generic OFF
1.9.3 Central unit operation mode

status:
what =

status:
what =
This frame indicates the Central Unit’s

operation mode, the what field can
assume one of the follow values:
what =
110#T  Manual Heating
210#T  Manual Conditioning
103  Off Heating
Tcp/Ip 203  Off Conditioning
*4*what*#0##
Client  Server 102  Antifreeze
115#parameterH  Holiday Heating
215#parameterC  Holiday Conditioning
parameterH = [1101-1103]
parameterC = [2101-2103]
[13001-13255]  Holiday days in Heating
mode
[23001-23255]  Holiday days in
Conditioning mode
[1101-1103]  Memo program in Heating
mode
[2101-2103]  Memo program in
Conditioning mode
[1201-1216]  Memo scenario in Heating
mode
[2201-2216]  Memo scenario in
Conditioning mode

with adjust by local offset.

temperature).
0.1° step.
1.9.4 “N” zone operation mode by central unit

Central Unit.
what =
110  Manual Heating
Tcp/Ip
*4*what*where## 111  Automatic Heating
Client  Server
103  Off Heating
102  Antifreeze
1.10 Frames in order to control Split
1.10.1 Request Split Control (Dimension 22)
Command
Open Frame Note
Session
Tcp/Ip: Where= 3#<where actuators>

*#4*where*22##
Client  Server Where actuators= Z#N = [0-99]#[1-9]
Where= 3#<where actuators>

Where actuators= Z#N = [0-99]#[1-9]
MOD can assume the following values:

0: Off
1: Winter
2: Summer
3: Fan
4: Dehumidification
5: Auto
NULL: Current modality
SP is the temperature regulated expressed

in Celsius and 0,5° C range:
000: 0°C
005: 0,5°C
Tcp/Ip 010: 1°C
*#4*where*22*MOD*SP*VEL*SWING##
Client  Server …
1265: 126,5°C
1270: 127°C
NULL: current or insignificant set point
VEL is the speed to set on the split:

0: Auto
1: minimum speed
2: medium speed
3: maximum speed
4: silent mode
NULL: current or insignificant speed
SWING is the setting of the Fan Swing

0:off
1: on
NULL: current or insignificant swing

Tcp/Ip answer
*#*1## or *#*0##
Client  Server NACK if not received answer or if the frame
is not sent.
1.10.2 Set control Split (Dimension 22)
Command
Open Frame Note
Session
Where= 3#<where actuators>


0: Off
1: Winter
2: Summer
3: Fan
4: Dehumidification
5: Auto

000: 0°C
005: 0,5°C
Tcp/Ip 010: 1°C
*#4*where*#22*MOD*SP*VEL*SWING##
Client  Server …
1265: 126,5°C
1270: 127°C

0: Auto
1: minimum speed
2: medium speed
3: maximum speed
4: silent mode

0:off
1: on

Tcp/Ip answer
*#*1## or *#*0##
is not sent.
1.11 Frames to update the staus of the Split
1.11.1 Control status split (Dimension 22)
Monitor
Open Frame Note
Session

0: Off
1: Winter
2: Summer
3: Fan
4: Dehumidification
5: Auto

000: 0°C
005: 0,5°C
010: 1°C
Tcp/Ip
*#4*where*22*MOD*SP*VEL*SWING## …
Client  Server
1265: 126,5°C
1270: 127°C

0: Auto
1: minimum speed
2: medium speed
3: maximum speed
4: silent mode

0:off
1: on

Tcp/Ip answer
*#*1## or *#*0##
is not sent.
1.12 Diagnostic of Heating adjustment (WHO=1004)
1.13 WHERE table

… …
#0 Central unit
#1 Zone 1 via central unit
… …
1.14 DIMENSION table
7 Central Unit Diagnostic R

11 Central Unit Auto diagnostic R
20 Probe diagnostic (only zones with failures) R
21 Probe diagnostic (all zones) R
22 Auto diagnostic of failures R
23 Number of zone with failures R
1.15 Allowed OPEN messages command session: Diagnostic

Request
1.15.1 Central unit diagnostic request command
Command
Open Frame Note
Session
Tcp/Ip:
*#1004*#0*7##
Client  Server
The BIT field is composed by BIT1 ... BIT24.
The most important bits are:
Bit13  if is 0 there is a probe failure
Bit14  if is 0 a probe not answer
Tcp/Ip
*#1004*#0*7*BIT## Bit15  if is 0 Central Unit battery is KO
Client  Server
Bit16  if is 0 EEPROM read/write failure
Bit21  if is 0 system generic trouble
Bit22  if is 0 configuration trouble
Bit23  if is 0 hardware failure
Bit24  if is 0 device is busy
ACK If received almost one request answer

Tcp/Ip
*#*1## or *#*0## NACK if not received answer or if the frame
Client  Server
is not sent.
Tcp/Ip
Client monitor  *#1004*#0*7*BIT## See upper comment.
Server
1.15.2 Zone failure diagnostic request command
Command
Open Frame Note
Session
Tcp/Ip:
*#1004*#0*20##
Client  Server
where = [#1 - #99]

Failure zones detected by Central Unit.
*#1004*#0*20## The BIT field is composed by BIT1 ... BIT16.
Tcp/Ip
*#1004*where1*21*BIT## Bit11  if is 0 a probe does not answer
Client  Server
… Bit12  if is 0 a pump does not answer
*#1004*wheren*21*BIT## Bit13  if is 0 EEPROM read/write failure
Bit14  if is 0 temperature out of range
Bit15  if is 0 a slave probe does not
answer
Bit16  if is 0 an actuator does not answer
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
Client monitor  *#1004*where*21*BIT## See upper comment.
Server
1.15.3 N zone diagnostic request command
Command
Open Frame Note
Session
where = [#1 - #99]
Tcp/Ip:
*#1004*where*21## Zones requested by Central Unit.
Client  Server
where = [#1 - #99]
Zones requested by Central Unit.
Bit11  if is 0 a probe does not answer
Tcp/Ip
*#1004*where*21*BIT## Bit12  if is 0 a pump does not answer
Client  Server
answer
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
Tcp/Ip
Client monitor  *#1004*where*21*BIT## See upper comment.
Server
1.15.4 Every zone diagnostic request command
Command
Open Frame Note
Session
Tcp/Ip:
*#1004*#0*21##
Client  Server
where = [#1 - #99]

*#1004*#0*21## Zones requested by Central Unit.
*#1004* where1*21*BIT## The most important bits are:
Tcp/Ip
… Bit11  if is 0 a probe does not answer
Client  Server
*#1004* wheren*21*BIT## Bit12  if is 0 a pump does not answer
answer
Tcp/Ip *#*1## or *#*0##
answer

frame is not sent.
*#1004*#0*21##
Tcp/Ip
Client monitor  *#1004* where1*21*BIT## See upper comment.
Server …
*#1004* wheren*21*BIT##
1.15.5 Failure / not answer zones number request command
Command
Open Frame Note
Session
Tcp/Ip:
*#1004*#0*23##
Client  Server
*#1004*#0*23## Parameter1 = The number of non-
Tcp/Ip answering probes
Client  Server *#1004*#0*23*parameter1 Parameter2 = The number of failure
*parameter2## probes
Tcp/Ip answer
*#*1## or *#*0##
frame is not sent.
*#1004*#0*23##
Tcp/Ip
*#1004*#0*23*parameter1
Server
*parameter2##
1.16 Allowed OPEN messages monitor session
1.16.1 Central unit diagnostic

Bit14  if is 0 a probe not answer
Tcp/Ip Bit15  if is 0 Central Unit battery is KO
*#1004*#0*7*BIT##
Client  Server Bit16  if is 0 EEPROM read/write failure
1.16.2 Central unit autodiagnostic

This frame is sent from Central Unit when a
system failure is detected.

Tcp/Ip
*#1004*#0*11*BIT## Bit14  if is 0 a probe not answer
Client  Server
Bit15  if is 0 Central Unit battery is KO
1.16.3 N zone diagnostic

where = [#1 - #99]
The BIT field is composed by BIT1 ...

BIT16. The most important bits are:
Tcp/Ip Bit11  if is 0 a probe does not answer
*#1004*where*21*BIT##
Client  Server Bit12  if is 0 a pump does not answer
answer
Bit16  if is 0 an actuator does not

answer
1.16.4 N zone autodiagnostic

This frame is sent from Central Unit when
a failure of N zone is detected.
where = [#1 - #99]
The BIT field is composed by BIT1 ...

BIT16. The most important bits are:
Tcp/Ip
*#1004*where*22*BIT## Bit11  if is 0 a probe does not answer
Client  Server
Bit12  if is 0 a pump does not answer
answer
Bit16  if is 0 an actuator does not
answer
1.16.5 Failure / Not answer zones number

Parameter1 = The number of non-
Tcp/Ip *#1004*#0*23*Parameter1* answering probes
Client  Server Parameter2## Parameter2 = The number of failure
probes
License
.
Disclaimers

Nome Documento OpenWebNet_Community_7_burglar alarm_v1_0_0_EN .doc
Data ultima emissione 13/02/08
Versione ultime emissione 1.0.0
OPEN PROTOCOL FOR ELECTRIC NETWORKS OpenWebNet_Community_7_burglar alarm_v1_0_0_EN .doc 13/02/2008
page 1/9
Updating History
Versione Data Autore

1.0.0 13/02/2007 Bticino S.p.A.
Direzione Marketing e Sviluppo Prodotti (Sviluppo Software Embedded)
Via L. Manara, 4
Erba (CO) Italy
www.myopenbticino.it
Descrizione modifiche apportate:
PRIMA VERSIONE.
page 2/9
INDEX
Updating History.................................................................................................................................2
1. MyHome Burglar Alarm (WHO= 5)................................................................................................4
1.1. Table of WHAT........................................................................................................................4
1.2. TABLE OF WHERE................................................................................................................5
1.3. Messages on Command Session...............................................................................................6
1.3.1. Status Request Frame .......................................................................................................6
1.3.1.1. Status request zone N (web server answer without system request)......................... 6
1.3.1.2. Central Unit Status Request (web server answer without system request)..............6
1.3.1.3. Central Unit Status Request (central unit direct answer).......................................... 7
1.3.1.4. Auxiliaries Status Request (web server answer without system request)................7
1.4. Messages on Monitor Session...................................................................................................8
1.4.1. Status changes Zone 1 4...................................................................................................8
1.4.2. Status Changes Zone 5 8..................................................................................................8
1.4.3. Asynchronous Event...........................................................................................................9
1.4.4. System Led – battery status................................................................................................9
1.4.5. Technical Alarms................................................................................................................9
1.4.6. Alarm Signalling or Asynchronous Event..........................................................................9
page 3/9
1. MyHome Burglar Alarm (WHO= 5)
1.1. Table of WHAT
0 MAINTENANCE
1 ACTIVATION
2 DISACTIVATION
3 DELAY END
4 SYSTEM BATTERY FAULT
5 BATTERY OK
6 NO NETWORK
7 NETWORK PRESENT
8 ENGAGE
9 DISENGAGE
10 BATTERY UNLOADS
11 ACTIVE ZONE
12 TECHNICAL ALARM
13 RESET TECHNICAL ALARM
14 NO RECEPTION - ACK PERIPHERAL DEVICE
15 INTRUSION ALARM
16 ALARM 24h / TAMPERING
17 ANTI-PANIC ALARM
18 NON-ACTIVE ZONE
26 START PROGRAMMING
27 STOP PROGRAMMING
31 SILENT ALARM
page 4/9
1.2. TABLE OF WHERE
GENERIC/SYSTEM
1 CONTROL PANEL
#0..8 ZONE 0..8 CENTRAL
#1..9 AUX1..9
WHO = 9
01 INPUT ZONE: DEVICE 1
0n INPUT ZONE: DEVICE n
11 ZONE 1: SENSOR n°1
1n ZONE 1: SENSOR n°n
81 ZONE 8: SENSOR n°1
8n ZONE 8: SENSOR n°n
#12 ZONE C / AUX C
#15 ZONE F / AUX F
Zone 0 is for inputs and the 3 internal sirens
Zone C (zone 12) is a special zone comprising: power feeder, external sirens, mechanical key,
communicator
page 5/9
1.3. Messages on Command Session
1.3.1. Status Request Frame
1.3.1.1.Status request zone N (
web server answer without system request
)
Session Frame OpenWebNet Comments

Tcp/Ip: *#5*#N## N=1..8
Client → Server
Open
Tcp/Ip *5*11*#N## If zone N engaged
Client ← Server *5*18*#N## If zone N divided
*#*1##
Open
1.3.1.2. Central Unit Status Request (
)

Tcp/Ip: *#5##
Client → Server
Open
Tcp/Ip *5*0**## If system on maintenance
Client ← Server *5*1**## If system active

Open *5*8**## If system engaged
*5*9**## If system disengaged

*5*4**## If battery fault
*5*5**## If battery OK
*5*10**## If battery KO

*5*6**## If no network
*5*7**## If network OK

*5*11*#n## If zone N engaged
*5*18*#n## If zone N divided

*5*15*#n## If zone n in Intrusion alarm
*5*16*#n## If zone n in Tampering alarm
*5*17*#n## If zone n in Antipanic alarm
*5*12*#x## If aux n in Technical alarm
*5*31*#x## Silent alarm from aux x
*#*1##
page 6/9
1.3.1.3.Central Unit Status Request (central unit direct answer)

The frame is mainly used on process start to align with Burglar Alarm system status

Tcp/Ip: *#5*0##
Client → Server
Open
Tcp/Ip *5*0**## If system on maintenance
Client ← Server *5*1**## If system active

Open *5*8**## If system engaged
*5*9**## If system disengaged

*5*4**## If battery fault
*5*5**## If battery OK
*5*10**## If battery KO

*5*6**## If no network
*5*7**## If network OK

Tcp/Ip *5*15*#n## If zone n in Intrusion alarm

Client ← Server *5*16*#n## If zone n in Tampering alarm
*5*17*#n## If zone n in Antipanic alarm
Open *5*12*#x## If aux n in technical alarm
*5*31*#x## Silent alarm from aux x
*5*14*ZN## Failed inerconnection of device N of zone Z
*5*14*D## Failed Interconnection from device D
*#*1##
1.3.1.4. Auxiliaries Status Request (
)

Tcp/Ip: *#9##
Client → Server
Open
Tcp/Ip *9*k*1## K= 0; OFF
Client ← Server *9*k*2## K = 1; ON
*9*k*3## K = 2; TOGGLE
Open *9*k*4## K = 3; STOP
*9*k*5## K = 4; UP
page 7/9
*9*k*6## K = 5; DOWN
*9*k*7## K = 6; ENABLED
*9*k*8## K = 7; DISABLED
*9*k*9## K = 8; RESET_GEN
*#*1## K = 9; RESET_BI
K = 10; RESET_TRI
1.4. Messages on Monitor Session
1.4.1. Status changes Zone 1 4

Tcp/Ip *5*1**## If system active
Client_monitor ←
*5*8**## If system engaged
Server Open *5*9**## If system disengaged

1.4.2. Status Changes Zone 5 8

Tcp/Ip *5*1**## If system active
Client_monitor ←
*5*8**## If system engaged
Server Open *5*9**## If system disengaged

page 8/9
1.4.3. Asynchronous Event

Tcp/Ip *5*6*## No network
Client_monitor ← *5*7*## Network OK

Server Open *5*10*## Battery KO

*5*26**## Start Programming
*5*27**## Stop Programming
1.4.4. System Led – battery status

Tcp/Ip *5*4*## Battery fault
Client_monitor ← *5*5*## Battery OK
Server Open
1.4.5. Technical Alarms

Tcp/Ip *5*12*#N## If aux n in technical alarm is ON
Client_monitor ← *5*13*#N##
If aux in technical alarm Reset
Server Open
1.4.6. Alarm Signalling or Asynchronous Event

Tcp/Ip *5*3*## If delay end
Client_monitor ← *5*2*0## If silent alarm
*5*0*0## If system disactivated
Server Open
*5*15*#Zn## If Intrusion Alarm Zone N
*5*16*#Zn## If Tampering alarm Zone N
*5*17*#Zn## If Antipanic alarm Zone N
page 9/9
Open Web Net

WHO=7
Brand Item
Legrand
BTicino F453AV
Document History
Version Date Author

1.0.0 01/10/2010 My Open Staff
Version Date Author

1.0.1 01/12/2011 My Open Staff
Updating description: UPDATE Video Server
Index
WHO = 7 MULTIMEDIA SYSTEM ................................................................................. 3

1. WHAT Table............................................................................................................ 3
2. WHERE Table ......................................................................................................... 4
3. Commands session ................................................................................................. 5
3.1 Received Video command (WHAT = 0) ..................................................... 5
3.2 Free video channel / Free audio and video resource command (WHAT = 9) 5
3.3 Zoom IN command (WHAT = 120)............................................................. 5
3.4 Zoom OUT command (WHAT = 121)......................................................... 6
3.5 Increase X coordinate command (WHAT = 130) ....................................... 6
3.6 Decrease X coordinate command (WHAT = 131) ...................................... 6
3.7 Increase Y coordinate command (WHAT = 140) ....................................... 7
3.8 Decrease Y coordinate command (WHAT = 141) ...................................... 7
3.9 Increase luminosity command (WHAT = 150) ............................................ 7
3.10 Decrease luminosity command (WHAT = 151) ...................................... 8
3.11 Increase contrast command (WHAT = 160) ........................................... 8
3.12 Decrease contrast command (WHAT = 161) ......................................... 8
3.13 Increase color command (WHAT = 170)................................................ 9
3.14 Decrease color command (WHAT = 171) .............................................. 9
3.15 Increase image quality command (WHAT = 180) .................................. 9
3.16 Decrease image quality command (WHAT = 181) ............................... 10
3.17 Display DIAL X-Y command (WHAT = 3XY) ....................................... 10
4. Video Server ......................................................................................................... 11
WHO = 7 MULTIMEDIA SYSTEM
In this document you can find all the OpenWebNet frames used to control the camera of
the Video Door Entry system catalogue.
1. WHAT Table
WHAT Description
0 Receive Video
9 Free Audio/Video Resources
… …
120 Zoom In
121 Zoom Out
… …
130 Increases X coordinate of the central part of the image to be zoomed
131 Decreases X coordinate of the central part of the image to be zoomed
… …
140 Increases Y coordinate of the central unit part of the image to be
zoomed
141 Decreases Y coordinate of the central part of the image to be zoomed
… …
150 Increases luminosity
151 Decreases luminosity
… …
160 Increases contrast
161 Decreases contrast
… …
170 Increases color
171 Decreases color
… …
180 Increases image quality
181 Decreases image quality
… …
311 Display DIAL 1-1
… …
… …

… …
… …
2. WHERE Table
WHERE Description
4000 Camera 00
4001 Camera 01
4002 Camera 02
4003 Camera 03
… …
4099 Camera 99
3. Commands session
3.1 Received Video command (WHAT = 0)
Command Session Open Frame Notes

TCP/IP:
*7*0*WHERE*## WHERE = [4000-5000]
Client -> Server
*#*1##
TCP/IP: ACK: if the command is sent to the Bus
or
Server -> Client NACK: if the command is not sent to the Bus
*#*0##
Events Session
TCP/IP:
*7*0*WHERE*## WHERE = [4000-5000]
Server -> Client
3.2 Free video channel / Free audio and video resource command (WHAT = 9)

TCP/IP:
*7*9**##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*9**##
Server -> Client
3.3 Zoom IN command (WHAT = 120)

TCP/IP:
*7*120##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*120##
Server -> Client
3.4 Zoom OUT command (WHAT = 121)

TCP/IP:
*7*121##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*121##
Server -> Client
3.5 Increase X coordinate command (WHAT = 130)

TCP/IP:
*7*130##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*130##
Server -> Client
3.6 Decrease X coordinate command (WHAT = 131)

TCP/IP:
*7*131##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*131##
Server -> Client
3.7 Increase Y coordinate command (WHAT = 140)

TCP/IP:
*7*140##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*140##
Server -> Client
3.8 Decrease Y coordinate command (WHAT = 141)

TCP/IP:
*7*141##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*141##
Server -> Client
3.9 Increase luminosity command (WHAT = 150)

TCP/IP:
*7*150##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*150##
Server -> Client
3.10 Decrease luminosity command (WHAT = 151)

TCP/IP:
*7*151##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*151##
Server -> Client
3.11 Increase contrast command (WHAT = 160)

TCP/IP:
*7*160##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*160##
Server -> Client
3.12 Decrease contrast command (WHAT = 161)

TCP/IP:
*7*161##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*161##
Server -> Client
3.13 Increase color command (WHAT = 170)

TCP/IP:
*7*170##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*170##
Server -> Client
3.14 Decrease color command (WHAT = 171)

TCP/IP:
*7*171##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*171##
Server -> Client
3.15 Increase image quality command (WHAT = 180)

TCP/IP:
*7*180##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*180##
Server -> Client
3.16 Decrease image quality command (WHAT = 181)

TCP/IP:
*7*181##
Client -> Server
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*181##
Server -> Client
3.17 Display DIAL X-Y command (WHAT = 3XY)

X and Y can be assigned these following
values:
TCP/IP: 11, 12,13,14;
*7*3XY##
Client -> Server 21, 22, 23, 24;
31, 32, 33, 34;
41, 42, 43, 44;
*#*1##
or
*#*0##
Events Session
TCP/IP:
*7*3XY## See upper comments.
Server -> Client
4. Video Server
The web server makes available the pictures coming from selected camera. The pictures are
encapsulated in HTTP/HTTPS protocol and it is in JPEG format.
In particular, once the camera has been activated with the proper OpenWebNet command
(*7*0*where##), the picture can be recovered at the following url:
https://IPaddress/telecamera.php?CAM_PASSWD=password
or
http://IPaddress/telecamera.php?CAM_PASSWD=password
Where “IPaddress” is the url of the web server (numeric or alphanumeric as well), and “password”
is the password that must be activated and configured using the configuration software and/or
through the web pages (in the “configuration” area of the web pages). Please see the devices’s
manual for further details.
The answer is composed from a header followed by the image in format JPEG.
The header is composed:
HTTP/1.1 200 OK\r\n\

Server: grabtofile\r\n\
Connection: close\r\n\
Content-Length: <length_image>\r\n\
Content-Type: image/jpeg\r\n\r\n
If any password is configured, the pictures can be recovered at the following urls:
https://IPaddress/telecamera.php
or
http://IPaddress/telecamera.php
We strongly suggest to configure a password.
License
.
Disclaimers

!" #$% &
' ( )*
# % +,& - .
""" $. /%
0-1 2 '#1 -,3

!
" # $
% ! & !' ( ) * + ,
#"- ." & ,
/&& 0 1 2 ,
3"- 4 5 .3 ( )/3 * + ,
#/3 4 5 .3 ( )/3 * + 6
"1 4 5 .3 ( )/3 * + 6
, 3-/.7 4 5 .3 ( )/3 * +
6 -/ /##4 .. 4 5 .3 ( )/3 * +
- # 8 4 5 .3 ( )/3 * 6+
9 :"4- /4 ; 4." 4 5 .3 ( )/3 * + 9
< 13"- 4 5 .3 ( )/3 * =+ 9
= #/3 >3"- 4 5 .3 ( )/3 * + <
7 4 8 ; 4." 4 5 .3 ( )/3 * + <
#".34"? 3" ; 4." 4 5 .3 ( )/3 * ,+ =
3"- . 3 ( )/3 * + =
#/3 . 3 ( )/3 * +
, #/3 >3"- . 3 ( )/3 * +
!"
'! & ' !
4 * 4 /#2 # ! && 0
* 4"3 2 # 0! && 0
! "#
$ %
#
& ' # (! "#
) *+ "# ! "#
! "#$ % &'
3 " 2 @A @@ AA
&→. ! !
3 " @A @@ @)@-@.@3AA
& ←. ! ! ) ' 0 ('!
@A@ AA +
- ' 0 ('!
6=+
. ' 0 ('!
6=+
3 ' ! 3
'! ' B
! ! ! &
( ' &
' & + 3 ' && 0
% & !B : ! % & 2
& ' ! C! 0 - !
3 D & E ! (C-3F +G &
' ! C! 0 - ! 3
D& E ! (C-3H +
3 " @A @@ @)@-@.@3AA . !
& ! ←
. ! !
! "#$ % '
3 " 2 @A @@ AA
&→. ! !
3 " @A @@ @ @#@-@/AA
& ←. ! ! ' 0 (
@A@ AA . I . ! +
# ' 0 ('!
+
- ' 0 ('!
+
J '' !
3 " @A @@ @ @#@-@JAA . !
& ! ←
. ! !
( ! "#$ % &'
3 " 2 @A @@ AA
& →. ! !
3 " @A @@ @"1 @"1 @"1 @"1,A "1 ! ' !
& ←. ! ! A & 2
@"1 @"1 @"1 @"1,@
@A@ AA : ! % & ' "1 ! = < I
' && 02
@ = @ <@ @
3 " @A @@ @"1 @"1 @"1 @"1,A . !

& ! ← A
. ! !
) * ! "#$ % '
3 " 2 @A @@ AA
&→. ! !
3 " @A @@ @-/.7 @-/.7 3 K
& ←. ! ! @-/.7 @-/.7,AA ' ! & 2
@-/.7 @-/.7 @-/.7 @-/.7,@
@A@ AA : ! % & ' "1 ! 66 66 66
& ' && 02
@ 66@ 66@ 66@
3 " @A @@ @-/.7 @-/.7 . !

← @-/.7 @-/.7 AA
,
& !
. ! !
+ ! "#$ % '
3 " 2 @A @@ AA
&→. ! !
3 " @A @@ @-/ @-/ @- -/ / ! %
& ←. ! ! / @-/ ,@-/ 6@-/ A & 2
A @-/ @-/ @-/ @-/ ,@-/ 6@-/
4 !2 % & ! '
@A@ AA &
% & 2 -/ / ! *
2 2::2 <2 2 2 G 1 *
@ @ @ 66@ @ @ @
3 " @A @@ @-/ @-/ @- . !

← / @-/ @-/ @-/ A
, 6
& !
. ! ! A
, - ! "#$ % +'
3 " 2 @A @@ 6AA
& →. ! !
3 " @A @@ 6@- # 88 AA - &4 L
& ←. ! ! & I0 ! - # 8' & & ' !
@A@ AA . ! ! 2
-). ! !
, -)
:,6
9 :,6 ;
-). ! !
), <,
3 " @A @@ 6@- # 88 AA . !
& ! ←
. ! !
./ # 0 ! "#$ % ,'
3 " 2 @A @@ AA
& →. ! !
3 " @A @@ @;@4@?AA :! 0 ! ; ! 4 L
& ←. ! ! ! & I ' !
@A@ AA ! & 1 ! !
3 & ! ! 2
; . ' ! !
4 . ' !! &
? . ' ! &
3 " @A @@ @;@4@?AA . !
& ! ←
. ! !
1 ! "#$ % 2'
3 " 2 @A @@ =AA 4 L
& →. ! ! ' ! & 2" ' & &
!H
3 " @A @@ =@#@)@-@.AA 1 ! !2
& ←. ! ! # '! & !H (
@A@ AA 0 '! +
) '! & !H (
0 '! +
- '! & !H (
0 '! 6=+
. '! & !H (
0 '! 6=+
3 " @A @@ =@#@)@-@.AA . !
& ! ←
. ! !
2 3 ! "#$ % '
3 " 2 @A @@ AA
& →. ! !
3 " @A @@ @)@ @.@3@ @# #/3 >3"- 4 L
& ←. ! ! @-@JAA & 2
)@ @.@3@ @#@-@J
@A@ AA ) ' 0 ('!
+
' 0 ('!
6=+
. ' 0 ('!
6=+
3 ' ! 3
'! ' B
! ! ! &
( ' &
' & + 3 ' && 0
% & !B : ! % & 2
& ' ! C! 0 - !
3 D & E ! (C-3F +G &
' ! C! 0 - ! 3
D& E ! (C-3H +
' 0 (
. I . ! +
# ' 0 ('!
+
- ' 0 ('!
+
J '' !
3 " @A @@ @)@ @.@3@ @# . !

& ! ← @-@JAA
. ! !
& * -0 ! "#$ % ('
3 " 2 @A @@ AA
& →. ! !
3 " @A @@ @;@4@?AA 7 ! & ; ! 4 L
& ←. ! ! ! & 2
@A@ AA ; . ' ! !
4 . ' !! &
? . ' ! &
3 " @A @@ @;@4@?AA . !
& ! ←
. ! !
4 0 ! "#$ % )'
3 " 2 @A @@ ,AA
&→. ! !
3 " @A @@ ,@;@4@?AA # ! ; ! 4 L
& ←. ! ! ! & 2
@A@ AA ; . ' ! !
4 . ' !! &
? . ' ! &
3 " @A @@ ,@;@4@?AA . !
& ! ←
. ! !
! "#$ % &'
3 " 2 @A @@A @)@-@.@3AA

& →. ! ! ) ' 0 ('!
+
- ' 0 ('!
6=+
. ' 0 ('!
6=+
3 ' !
3 '! ' B
! ! !
& ( ' &
' & + 3 ' && 0
% & ! B : !
% & 2 & ' !
C! 0 - ! 3 D & E
! (C-3F +G & ' !
C! 0 - ! 3 D& E
! (C-3H +
3 " @A@ AA
& ←. ! !
3 " @A @@A @)@-@.@3AA . !

& ! ←
. ! !
( ! "#$ % '
3 " 2 @A @@A @#@C@-@/AA

& → 4C ' 0 (
. I . ! +
# ' 0 ('!
+
- ' 0 ('!
+
J '' !
3 " @A@ AA
& ← 4C
3 " @A @@A @#@C@-@/AA . !

& ! ←
. ! !
) 3 ! "#$ % '
3 " 2 @A @@A @)@ @.@3@ @

& →. ! ! #@-@JAA ) ' 0 ('!
+
' 0 ('!
6=+
. ' 0 ('!
6=+
3 ' !
3 '! ' B
! ! !
& ( ' &
' & + 3' && 0
% & ! B : !
% & 2 & ' !
C! 0 - ! 3 D & E !
(C-3F +G & ' !
C! 0 - ! 3 D& E
! (C-3H +
' 0
( . I . ! +
# ' 0 ('!
+
- ' 0 ('!
+
J '' !
3 " @A@ AA
& ←. ! !
3 " @A @@A @)@ @.@3@ @ . !
& ! ← #@-@JAA
. ! !
CEN Frames
Open Web Net frames for Scenario Scheduler
Brand Item
Legrand 03565
BTicino MH200, MH200N
Document History
Version Date Author

1.0.0 01/10/2010 My Open Staff
Index
DESCRIPTION .................................................................................................................... 3
OPEN WEB NET WHO = 15 ............................................................................................... 5
1.1. Virtual pressure....................................................................................................... 7
1.2. Virtual release after short pressure ......................................................................... 7
1.3. Virtual release after an extended pressure ............................................................. 7
1.4. Virtual extended pressure ....................................................................................... 8
EVENT CONNECTION ........................................................................................................ 9
2.1. Pressure ................................................................................................................. 9
2.2. Release after short pressure .................................................................................. 9
2.3. Release after an extended pressure ....................................................................... 9
2.4. Extended pressure.................................................................................................. 9
EXAMPLE .......................................................................................................................... 10
OPEN WEB NET WHO = 25 ............................................................................................. 13
ACTION CONNECTION .................................................................................................... 16
3.1. Virtual short pressure ( < 0.5 seconds ) ................................................................ 16
3.2. Virtual start of extended pressure ( >= 0.5 seconds ) ........................................... 16
3.3. Virtual extended pressure ..................................................................................... 17
3.4. Virtual released after a extended pressure ........................................................... 17
EVENT CONNECTION ...................................................................................................... 18
4.1. Short pressure ( < 0.5 seconds ) .......................................................................... 18
4.2. Start of extended pressure ( < 0.5 seconds ) ........................................................ 18
4.3. Extended pressure................................................................................................ 18
4.4. And of extended.................................................................................................... 18
EXAMPLE .......................................................................................................................... 19
General Information about devices configured in CEN Mod .............................................. 22
Devices that allow CEN pressure and CEN PLUS ............................................................. 24
How a Touch Screen allows to send CEN messages ........................................................ 24
Gateways that allow pressure information and CEN PLUS ............................................... 24
IMPORTANT NOTE ........................................................................................................... 25
DESCRIPTION
The Scenario Scheduler is a Home Controller with instructions called scenarios.

This scenarios are managed by receiving CEN Frames from command modules or from
software to activate, deactivate, enable and disable each scenario.
CEN Frames can be send on the SCS BUS using SCS Devices (as a normal SCS
Command) or using an Open Web Net / SCS Gateway.
The Scenario Scheduler reads these frames on the bus, analyzes them, manages
scenarios.
The Scenario Scheduler works also as an Ethernet Gateway 1 .

It monitors all the SCS Frames traveling in the SCS bus, and all the Open Web Net
Frames arriving from IP socket connections. The received SCS Frames are process and
routed according to the CEN source address and the key pressure information.
CEN Frames can be used for integration between My Home System and 3rd party
Systems.
Installing My Home Commands in the system, configured as CEN, it’s possible to forward
the information of pressure of a Command to a 3rd part System using a Scenario
Scheduler as Ethernet Gateway.
This information can be used to control functions of other System.
1
MH200 doesn’t manage this function
A SCS Command configured in modality CEN generates a CEN messages when one of
his push button is pressed.
This schema helps to understand the meaning of the new functions available with the
evolved CEN and CEN PLUS
BASIC CEN
1. Start pressure
EVOLVED CEN
1. Start pressure
2. Release after an extended pressure
3. Extended pressure
4. Release after short pressure
CEN PLUS
1. Short pressure
2. Start of extended pressure
3. Extended pressure
4. Release after an extended pressure

BASIC & EVOLVED CEN
WHAT TABLE
CONNECTION 3
VALUE DESCRIPTION
ACTION EVENT
00 Button Number W R
… W R
31 Button Number W R
CONNECTION 3
ACTION EVENT
1
1 Release after short pressure W R
2 Release after an extended pressure 1 W R
3 Extended pressure 1 - 2 W R
WHERE TABLE
VALUE DESCRIPTION
A – PL [1-9][1-9] Normal Area – Light Point
A – PL [00][01-15] Zone 0 : Advanced A-PL 1
A – PL [10][01-15] Zone 10 : Advanced A-PL 1
A – PL [01-09][10-15] Light Point 10-15 : Advanced A-PL 1
#3 Private Raiser BUS 1
#4#[01-15] Local BUS where SCS/SCS Interface has address I4
1
MH200 doesn’t manage this function
2
To have an extended pressure of a command, the push button has to be pressed for 0.5s.
From the first pressure, to the release, every 0.5s the relative frames is sent on the SCS BUS.
3
W = Write , R = Read
ACTION CONNECTION
1.1. Virtual pressure

WHAT = virtual pressure of the push button n
N value = [00-31]
Client → Server *15*WHAT*WHERE##
WHERE = push button virtual address
values = all the values in the WHERE Table
Client ← Server *#*1##
Event Connection Open Frame Note
The OWN/SCS Gateway informs each Client with
Client ← Server *15*WHAT*WHERE## an opened Event Connection that a CEN Frame is
read on the SCS BUS
1.2. Virtual release after short pressure

N value = [00-31]
Client → Server *15*WHAT#1*WHERE##
Client ← Server *15*WHAT#1*WHERE## an opened Event Connection that a CEN Frame is
read on the SCS BUS
1.3. Virtual release after an extended pressure

N value = [00-31]
read on the SCS BUS
1.4. Virtual extended pressure

N value = [00-31]
read on the SCS BUS
EVENT CONNECTION
2.1. Pressure
This frame is sent to a Client if:
- a physical push button is pressed
Client ← Server *15*WHAT*WHERE##
- a OWN client sends a virtual pressure on
the bus
2.2. Release after short pressure

- a physical push button is released after a
Client ← Server *15*WHAT#1*WHERE## short pressure
- a OWN client sends a virtual release after
a short pressure on the bus
2.3. Release after an extended pressure

- a physical push button is released after an
Client ← Server *15*WHAT#2*WHERE## extended pressure
- a OWN client sends a virtual release after
a long pressure on the bus
2.4. Extended pressure

- a physical push button is keep pressing
Client ← Server *15*WHAT#3*WHERE##
- a OWN client sends a virtual keep pressing
on the bus
EXAMPLE
The following schema helps to understand how the Scenario

enario Scheduled translates in Open
Web Net frames the actions done on the systems, when a push button of SCS Command
configured with M = CEN is pressed or a Software send CEN Message to the System.
SCS COMMAND
1 2 3
4 5 6
When the push button n° 1 of SCS Command 1 is pressed, keep pressed, then released
an Open Web Net Client reads the following sequence of OWN Frames:
Event Connection Time OWN Frame Action

Client ← Server 17:07:48:140 *15*01*0001## Pressure
Client ← Server 17:07:48:687 *15*01#3*0001## Extended Pressure
Client ← Server 17:07:49:499 *15*01#2*0001## Release
When the push button n° 4 of Command SCS 1 is pressed and released an Open Web
Net Client reads the following sequence of OWN Frames:



Client ← Server 17:06:54:883 *15*06*36#4#01## Pressure
Client ← Server 17:06:55:125 *15*06#1*36#4#01## Release

Client ← Server 17:06:56:232 *15*03*0112#4#12## Pressure
Client ← Server 17:06:56:418 *15*03#1*0112#4#12## Release
When an OWN Client sends a Virtual Pressure of Button=31, A=02, PL=15, each Client
with an Event Connection opened reads the following OWN Frame:
Action Connection Time OWN Frame Action

Client Æ Server 17:21:05:528 *15*31*0215## Virtual Pressure
Client ← Server 17:21:05:044 *15*31*0215## Virtual Pressure
When an OWN Client sends a Virtual Short Release of Button=3, A=10, PL=01, each
Client with an Event Connection opened reads the following OWN Frame:

Virtual Short
Client Æ Server 17:21:07:041 *15*03#1*1001##
Release
Virtual Short
Client ← Server 17:21:07:062 *15*03#1*1001##
Release
When an OWN Client sends a Virtual keep pressing of Button=0, A=00, PL=10, each

Virtual Extended
Client Æ Server 17:21:11:916 *15*00#3*0010##
Pressure
Virtual Extended
Client ← Server 7:21:11:932 *15*00#3*0010##
Pressure
When an OWN Client sends a Virtual Release after an Extended Pressure of Button=20,
A=03, PL=03, I4 = 02, each Client with an Event Connection opened reads the following
OWN Frame:

Virtual Release after
Client Æ Server 17:21:07:041 *15*20#2*33#4#02##
Extended Pressure
Virtual Release after
Client ← Server 17:21:07:062 *15*20#2*33#4#02##
Extended Pressure

CEN PLUS
WHAT TABLE
CONNECTION
VALUE DESCRIPTION
ACTION EVENT
21 Short pressure ( < 0.5 seconds ) W R
22 Start of extended pressure ( >= 0.5 seconds ) W R
23 Extended pressure W R
24 Released after an extended pressure W R
25 Rotary selector in slow clockwise rotation W R
26 Rotary selector in fast clockwise rotation W R
27 Rotary selector in slow counter-clockwise rotation W R
28 Rotary selector in fast counter-clockwise rotation W R
CONNECTION
ACTION EVENT
0-31 Virtual Pushbutton W R
WHERE TABLE
VALUE DESCRIPTION
Virtual Address has a value done with the union of:
2 [0-2047]
[ 2 ] [ Object ]
ACTION CONNECTION
3.1. Virtual short pressure ( < 0.5 seconds )

WHAT = action # object
pushbutton = virtual pressure of the push button n
N value = [0-31]
Client → Server *25*21#pushbutton*WHERE##
WHERE = [2] [object]
object = push button virtual address = [0-2047]
Client ← Server *25*21#pushbutton *WHERE## an opened Event Connection that a CEN PLUS
Frame is read on the SCS BUS
3.2. Virtual start of extended pressure ( >= 0.5 seconds )

N value = [0-31]
3.3. Virtual extended pressure

N value = [0-31]
3.4. Virtual released after a extended pressure

N value = [0-31]
EVENT CONNECTION
4.1. Short pressure ( < 0.5 seconds )

- a physical push button configured as CEN
Client ← Server *25*21#object*WHERE## PLUS is short pressed
- a OWN client sends a virtual short
pressure on the bus
4.2. Start of extended pressure ( < 0.5 seconds )

Client ← Server *25*22#object*WHERE## PLUS is pressed (>=0.5 seconds)
- a OWN client sends a virtual start of
extended pressure on the bus
4.3. Extended pressure

Client ← Server *25*23#object*WHERE## PLUS is keep pressed
- a OWN client sends a virtual extended
pressure on the bus
4.4. And of extended

PLUS is released after an extended
Client ← Server *25*24#object*WHERE##
pressure
- a OWN client sends a virtual end of
extended pressure on the bus
EXAMPLE
The following schema helps to understand how the Scenario Scheduled translates in Open
Web Net frames the actions done on the systems, when a push button of SCS Command
configured with M = CEN PLUS is pressed or a Software send CEN Message to the
System.
When the push button n° 1 of SCS Command 1 is pressed, keep pressed, then released

Client ← Server 14:44:00:051 *25*22#1*21## Pressure
When the push button n° 2 of SCS Command 2 is pressed and released after 0.5 seconds

When the push button n° 3, address 3, of SCS Command is pressed and released in less
than 0.5 seconds an Open Web Net Client reads the following sequence of OWN Frames:

When an OWN Client sends a Virtual Short Pressure of Button=31, WHERE = 1, each

Virtual short
Client Æ Server 16:11:07:528 *25*21#31*21##
pressure
Virtual Short
Client ← Server 16:11:07:044 *25*21#31*21##
Pressure
When an OWN Client sends a Virtual Start of extended pressure of Button=3, WHERE =
2010, each Client with an Event Connection opened reads the following OWN Frame:

Start of a virtual
Client Æ Server 16:11:09:041 *25*22#3*22010##
extended pressure
Start of a virtual
Client ← Server 16:11:09:062 *25*22#3*22010##
extended pressure
When an OWN Client sends a Virtual extended pressure of Button=0, WHERE = 0, each

Virtual extended
Client Æ Server 16:11:21:926 *15*23#0*20##
pressure
Virtual extended
Client ← Server 16:11:21:942 *15*23#0*20##
pressure
When an OWN Client sends a Virtual Release after extended pressure of Button=10,
WHERE = 101, each Client with an Event Connection opened reads the following OWN
Frame:

End of a virtual
Client Æ Server 16:15:57:142 *15*24#10*2101##
extended pressure
End of a virtual
Client ← Server 16:15:57:163 *15*24#10*2101##
extended pressure
General Information about devices configured in CEN Mod
ADVANCED CEN CONFIGURATION
• CEN devices configured with Advanced Virtual Configuration don’t use an address
on the SCS BUS
• CEN devices configured with Basic Virtual Configuration use an address on the
SCS BUS
• CEN devices configured with Physical Jumper use an address on the SCS BUS
Advanced Virtual Configuration
Address Æ WHERE Æ Object (TiMH200N)
Button n Æ WHAT Æ Action (Button) (TiMH200N)
CEN PLUS CONFIGURATION
• CEN Plus device can be configured only with Advanced Virtual Configuration and
don’t use and address on the BUS
Advanced Virtual Configuration
CEN Number Æ WHERE Æ Pushbutton (TiMH200N)
Button n Æ WHAT parameter Æ Object (TiMH200N)
Devices that allow CEN pressure and CEN PLUS
BTicino Legrand Data

H / L / N / NT 4652/2 573974 – 67241 09W46
H / L / N / NT 4652/3 573975 09W37
H / L / N / NT 4651M2 573976 – 67242 All
H / L / N / NT 4680 573902/3 – 67217/8 09W08
3477 573996 10W04
F428 03553 09W50
How a Touch Screen allows to send CEN messages
CEN
BTicino Legrand FW CEN CEN PLUS
PRESSURE
TS 3.5’’ TS 3.5’’ 5.0.33 YES NO NO
Only Short
TS 3.5’’ TS 3.5’’ 6.0.7 YES NO
Pressure
TS 10’’ TS 10’’ 1.0.36 NO NO NO
Only Short
TS 10’’ TS 10’’ 2.0.x YES NO
Pressure
Gateways that allow pressure information and CEN PLUS
CEN
BTicino Legrand CEN CEN PLUS
PRESSURE
MH200 YES NO NO
MH200N 03565 YES YES YES
F453AV (v1.0.19) YES NO NO
F453AV (v2.1.7) 573992 (v2.1.7) YES YES YES
F453 YES YES YES
F452V YES NO NO
F452 YES NO NO
IMPORTANT NOTE
CEN frames are always delivered via SCS to a Scenario Scheduler.
Without a Scenario Scheduler connected on the SCS BUS, the other gateways are not
able to read from the SCS System the CEN frames.
For example, if a command is configured as CEN a F453 can forward OWN CEN Frames
to a Client only if an MH200N is on the BUS. Else when the pushbutton of a command is
pressed, the F453 doesn’t translate this information.
Document name OpenWebNet_Community_4_soundsystem_v1_0_1_EN.doc

Last date modify 11/24/2011
Last version 1.0.1
Pag.1 di 19
Updating history
Version Date Author

1.0.0 05/19/2006 Bticino S.p.A.
Direzione Marketing e Sviluppo Prodotti (Sviluppo Software Embedded)
Via L. Manara, 4
Erba (CO) Italy
www.myopen-bticino.it
FIRST VERSION
1.0.1 11/24/2011 Legrand
R&D dept
REMOVED WHAT 3001/4016
ADD LICENCES
Pag.2 di 19
INDEX
Updating history................................................................................................................................... 2
INDEX ................................................................................................................................................. 3
1. Sound system (WHO = 16) .......................................................................................................... 4
1.1. WHAT table: ........................................................................................................................ 4
1.2. WHERE table:...................................................................................................................... 6
1.3. DIMENSIONS table: ........................................................................................................... 6
1.4. Allowed OPEN messages Command session: Amplifiers and sources set in ..................... 7
1.4.1. AMPLIFIERS/SOURCES ON Command ................................................................... 7
1.4.2. AMPLIFIERS/SOURCES OFF Command ................................................................. 8
1.4.3. SOURCES CYCLE Command .................................................................................... 8
1.4.4. SLEEP ACTIVATION Command............................................................................... 9
1.4.5. SLEEP DEACTIVATION Command ......................................................................... 9
1.4.6. FOLLOW ME Command ............................................................................................ 9
1.4.7. RDS START-SEND Command ................................................................................. 10
1.4.8. RDS STOP-SEND Command .................................................................................... 10
1.4.9. VOLUME UP Command ........................................................................................... 10
1.4.10. VOLUME DOWN Command ................................................................................... 11
1.4.11. FREQUENCY UP Command .................................................................................... 11
1.4.12. FREQUENCY DOWN Command............................................................................. 11
1.4.13. STATION UP Command ........................................................................................... 12
1.4.14. STATION DOWN Command ................................................................................... 12
1.5. Allowed OPEN messages Command session: Dimensions and status request and
dimensions written ......................................................................................................................... 13
1.5.1. VOLUME REQUEST Command .............................................................................. 13
1.5.2. STATUS REQUEST Command ................................................................................ 13
1.5.3. FREQUENCY REQUEST Command ....................................................................... 14
1.5.4. STATION REQUEST Command .............................................................................. 14
1.5.5. RDS REQUEST Command ....................................................................................... 15
1.5.6. VOLUME WRITE Command ................................................................................... 15
1.5.7. FREQUENCY WRITE Command ............................................................................ 15
1.5.8. STATION WRITE Command ................................................................................... 16
1.5.9. STATION MEMORIZED Command ........................................................................ 16
1.6. Allowed OPEN messages Monitor Session ....................................................................... 17
1.6.1. VOLUME INFORMATION...................................................................................... 17
1.6.2. STATUS INFORMATION ....................................................................................... 17
1.6.3. STATUS AND FREQUENCY INFORMATION ..................................................... 17
1.6.4. RDS INFORMATION ............................................................................................... 18
License ............................................................................................................................................... 19
Disclaimers......................................................................................................................................... 19
Pag.3 di 19
1. Sound system (WHO = 16)
1.1. WHAT table:
0 ON amplifier / source “base band”

3 ON amplifier / source stereo channel
10 OFF amplifier / source “base band”
13 OFF amplifier / source stereo channel
20 source cycle (“base band”)
23 source cycle (channel stereo)
30 Sleep on “base band”
33 Sleep on channel stereo
40 Sleep OFF
50 Follow me “base band”
53 Follow me channel stereo
100 source Busy
101 Start send RDS
102 Stop send RDS
1001 Delta volume: +1

… …
1101 Delta volume: -1
… …
2001 Delta high tones: +1

… …
2101 Delta high tones: -1
… …
Pag.4 di 19
5000 Find the first free frequency greater than the

selected one
5001 Delta frequency: +0.05Mhz
… …
5100 Find the first free frequency less than the selected
one
5101 Delta frequency: -0.05Mhz
… …
6001 Delta radio station or track: +1

… …
6101 Delta radio station or track: -1
… …
Pag.5 di 19
1.2. WHERE table:
0 General amplifiers
#0 0 Environment amplifiers
01 01 Amplifier
…. ….
99 99 Amplifier
100 General source

101 1 Source
102 2 Source
103 3 Source
104 4 Source
105 5 Source
106 6 Source
107 7 Source
108 8 Source
109 9 Source
1.3. DIMENSIONS table:
1 Volume
2 High Tones
3 Low Tones
4 Balance
5 State
6 Frequency
7 Radio station / track
8 RDS
9 Frequency + Radio station / track
10 Radio station
Pag.6 di 19
1.4. Allowed OPEN messages Command session: Amplifiers and

sources set in
1.4.1. AMPLIFIERS/SOURCES ON Command

Command Session Open Frame Note
Tcp/Ip: *16*what*where## what = 0, 3
Client Server where =
0 Amplifiers general command
#0 - #9 Amplifiers environment command
01 - 99 Amplifiers point to point command
101 - 109 Sources point to point command
Tcp/Ip: *#*1## or *#*0## ACK if command is sent to Bus.
Client Server NACK if command is not sent to Bus.
Tcp/Ip *16*what*where1## It is sent the activate amplifiers and sources
Client monitor … status.
Server *16*what* wheren## where = point to point amplifiers or commanded
source address.
what = 0, 3
*#16*where*1*parameter## where = [01 – 99]

parameter = [0 – 31] it indicates the amplifier
volume’s.
*#16*where*8*parameter## where = [101 - 109]

parameter = it indicates the RDS string and it
includes 8 ASCII characters.
Example: enabled RDS on 101 source.
*#16*101*8*32*67*65*80*73*84*65*76##
Pag.7 di 19
1.4.2. AMPLIFIERS/SOURCES OFF Command

Tcp/Ip: *16*what*where## what = 10, 13
100 Sources general command
Tcp/Ip *16*[10-15]*where1## It is sent the deactivate amplifiers and sources
Client monitor … status.
Server *16*[10-15]* wheren## where = point to point amplifiers or commanded
source address.
1.4.3. SOURCES CYCLE Command

Tcp/Ip: *16*what*100## what = 20, 23
Client Server
Tcp/Ip *16*what*where## If activated source:
Client monitor what = 0, 3
Server where = [101 – 109]
*16*what*where1## If deactivated source:

… what = 10, 13
*16*what*wheren## where = [101 -109]
(preceding source compared with the actual
source)
*#16*where*6*0*parameter These 2 frames are optional and they depend

## from activated source:
where = [101 – 109]
parameter = it indicates the listen frequency
expressed in Hz. It is composed by 6 digits:
Example: set 107.00 frequency
*#16*where*#6*0*107000##
*#16*where*7*0*parameter If the radio station is memorized then:

## where = [101 – 109]
Pag.8 di 19
parameter = it indicates the memory number

that the actual radio station is saved.
1.4.4. SLEEP ACTIVATION Command

Tcp/Ip: *16*what*where## what =
Client Server 30  “base band” Sleep activation
33  “stereo channel” Sleep activation
where =
Tcp/Ip *16*what*where1## where = Commanded amplifier address
Client monitor … what =
Server *16*what*wheren## 30 (sent)  0 (response)
33 (sent)  3 (response)
*#16*where1*1*parameter## where = [01 – 99]

… parameter = [0 – 31] it indicates the amplifier
*#16*wheren*1*parameter## volume’s.
1.4.5. SLEEP DEACTIVATION Command

Tcp/Ip: *16*40*where## where =
Client Server 0 Amplifiers general command
Tcp/Ip *16*13*where## where = Commanded amplifier address
Client monitor
Server
1.4.6. FOLLOW ME Command

Tcp/Ip: *16*53*100##
Client Server
Pag.9 di 19

Tcp/Ip *16*what*where## what =
Client monitor 0  Base band ON
Server 3  Stereo channel ON
13  OFF
where = [101 – 109]
1.4.7. RDS START-SEND Command

Tcp/Ip: *16*101*where## where = [101 – 109]
Client Server
Tcp/Ip *#16*where*8*0*parameter where = [101 - 109]
Client monitor ## parameter = it indicates the RDS string and it
Server includes 8 ASCII characters.
*#16*101*8*32*67*65*80*73*84*65*76##
1.4.8. RDS STOP-SEND Command

Tcp/Ip: *16*102*where## where = [101 - 109]
Client Server
Tcp/Ip
Client monitor
Server
1.4.9. VOLUME UP Command

Tcp/Ip: *16*what*where## what = [1001 – 1015]
Pag.10 di 19

Tcp/Ip *#16*where1*1*parameter## where = [01 – 99]
Client monitor … parameter = [0 – 31] it indicates the amplifier
Server *#16*wheren*1*parameter## volume’s.
1.4.10. VOLUME DOWN Command

Server *#16*wheren*1*parameter## volume’s.
1.4.11. FREQUENCY UP Command

Tcp/Ip: *16*what*where ## what = [5000 – 5015]
Client Server where = [101 - 109]
Tcp/Ip *#16*where*6*0*parameter where = [101 – 109]
Client monitor ## parameter = it indicates the listen frequency
Server expressed in Hz. It is composed by 6 digits:
Example: 107.00 frequency
*#16*where*6*0*107000##

## where = [101 – 109]
1.4.12. FREQUENCY DOWN Command

Pag.11 di 19

*#16*where*6*0*107000##

## where = [101 – 109]
1.4.13. STATION UP Command

*#16*where*6*0*107000##

## where = [101 – 109]
1.4.14. STATION DOWN Command


*#16*where*6*0*107000##

## where = [101 – 109]
Pag.12 di 19

1.5. Allowed OPEN messages Command session: Dimensions and

status request and dimensions written
1.5.1. VOLUME REQUEST Command

Tcp/Ip: *#16*where*1## where =
Tcp/Ip *#16*where1*1*parameter## If environment or general request, we get as a lot
Client Server … of frames as the active amplifiers are available:
*#16*wheren*1*parameter## where = [01 – 99]
volume’s.
Tcp/Ip *#16*where1*1*parameter## See upper comment.
Client monitor …
Server *#16*wheren*1*parameter##
1.5.2. STATUS REQUEST Command

Tcp/Ip: *#16*where*5## where =
100 Sources general command
Tcp/Ip *16*what*where## If environment or general request, we get as a lot
Client Server of frames as the active amplifiers are available:
what =
0  Base band ON
3  Stereo channel ON
13  OFF
where = [01 – 99] and [101 – 109]

Pag.13 di 19

Tcp/Ip *16*what*where## See upper comment.
Client monitor
Server
1.5.3. FREQUENCY REQUEST Command

Tcp/Ip: *#16*where*6## Se where:
Client Server 100 Sources general command
*#16*where*#6*0*107000##

## where = [101 – 109]
1.5.4. STATION REQUEST Command

Tcp/Ip: *#16*where*7## Se where:
Client Server 100 Sources general command
Tcp/Ip *#16*where*7*0*parameter If the radio station is memorized then:
Client Server ## where = [101 – 109]
*#16*where*#6*0*107000##

## where = [101 – 109]
Pag.14 di 19
1.5.5. RDS REQUEST Command

Tcp/Ip: *#16*where*8## where = [101 – 109]
Client Server
Tcp/Ip *#16*where*8*parameter## where = [101 - 109]
Client Server parameter = it indicates the RDS string and it
*#16*101*8*32*67*65*80*73*84*65*76##
Tcp/Ip *#16*where*8*parameter2# See upper comment.
Client monitor #
Server
1.5.6. VOLUME WRITE Command

Tcp/Ip: *#16*where*#1*parameter* where =
Client Server ## 0 Amplifiers general command
volume’s that we want to set in
Server *#16*wheren*1*parameter## volume.
1.5.7. FREQUENCY WRITE Command

Tcp/Ip: *#16*where*#6*0*paramete where = [101 – 109]
Client Server r## parameter = it indicates the frequency that we
want to set in and it is expressed in Hz. It is
composed by 6 digits:

*#16*where*#6*0*107000##
Pag.15 di 19

*#16*where*#6*0*107000##
*#16*where*8*parameter## If available:
where = [101 - 109]
includes 8 ASCII.
*#16*101*8*32*67*65*80*73*84*65*76##
1.5.8. STATION WRITE Command

Tcp/Ip: *#16*where*#7*parameter# where = [101 – 109]
Client Server # parameter = [1 – 5] it indicates the radio
station that we want to listen.
*#16*where*#6*0*107000##
*#16*where*7*0*parameter where = [101 – 109]

## parameter = it indicates the memory number
If available:
*#16*where*8*parameter## where = [101 - 109]
*#16*101*8*32*67*65*80*73*84*65*76##
1.5.9. STATION MEMORIZED Command

Tcp/Ip: *#16*where*#10*parameter where = [101 – 109]
Client Server ## parameter = [1 – 5] it indicates the radio
station that we want to listen.
Pag.16 di 19

*#16*where*#6*0*107000##
*#16*where*7*0*parameter where = [101 – 109]

## parameter = it indicates the memory number
1.6. Allowed OPEN messages Monitor Session
1.6.1. VOLUME INFORMATION

Tcp/Ip *#16*where*1*parameter## where = [01 – 99]
Client monitor parameter = [0 – 31] it indicates the amplifier’s
Server volume that we want to set in.
1.6.2. STATUS INFORMATION

Tcp/Ip *16*what*where## what =
Client monitor 0  Base band ON
Server 3  Stereo channel ON
13  OFF
where = [01 – 99] e [101 – 109]
1.6.3. STATUS AND FREQUENCY INFORMATION

*#16*where*#6*0*107000##

## where = [101 – 109]
Pag.17 di 19
1.6.4. RDS INFORMATION

Tcp/Ip *#16*where*8*0*parameter where = [101 - 109]
Client monitor parameter = it indicates the RDS string and it
Server includes 8 ASCII characters.
*#16*101*8*32*67*65*80*73*84*65*76##
Pag.18 di 19
License
.
Disclaimers

Pag.19 di 19
Energy Management Functions
Brand Item
Legrand
BTicino F80/x, F520, F521, F522,
F523, 3522
Document History
Version Date Author

1.0.0 15/07/2011 My Open Staff
Index
Sommaire
1 DESCRIPTION ............................................................................................................. 4
2 WHERE TABLE ............................................................................................................ 4
3 WHAT TABLE ............................................................................................................... 4
4 DIMENSION TABLE ..................................................................................................... 5
5 ACTION CONNECTION ............................................................................................... 6
5.1 Command to be sent: ............................................................................................. 6
5.1.1 Activation of the automatic reset ...................................................................... 6
5.1.2 Deactivation of the automatic reset .................................................................. 6
5.1.3 Start sending daily totalizers on an hourly basis for 16-bit for daily graphics ... 6
5.1.4 Start sending Average monthly on an hourly basis for 16-bit for media daily
graphics: ....................................................................................................................... 6
5.1.5 Start sending monthly totalizers current year on a daily basis for 32-bit for
monthly graphics: ......................................................................................................... 7
5.1.6 Start sending monthly totalizers on a daily basis, last year compared to 32-bit
graphics Previous Year :............................................................................................... 7
5.1.7 Actuator Enable:............................................................................................... 7
5.1.8 Forced Actuator for X Time: ............................................................................. 7
5.1.9 Forced actuator for Default Time:..................................................................... 8
5.1.10 End forced Actuator: ..................................................................................... 8
5.1.11 Reset totalizers: ............................................................................................ 8
5.2 Dimensions request ................................................................................................ 9
5.2.1 Request Status Stop & Go ............................................................................... 9
5.2.2 Request Status Stop & Go (open or close) .................................................... 10
5.2.3 Request Status Stop & Go (failure or no failure) ............................................ 10
5.2.4 Request Status Stop & Go (block or close) .................................................... 11
5.2.5 Request Status Stop & Go (open for CC between the N or close) ................. 11
5.2.6 Request Status Stop & Go (opened Ground fault or close) ............................ 12
5.2.7 Request Status Stop & Go (open for Vmax or close) ..................................... 12
5.2.8 Request Status Stop & Go (Self test disabled or Self test abled) ................... 13
5.2.9 Request Status Stop & Go (automatic reset off or on) ................................... 14
5.2.10 Request Status Stop & Go (Check off or on) .............................................. 14
5.2.11 Request Status Stop & Go (waiting for closing or close)............................. 15
5.2.12 Request Status Stop & Go (first 24 hours of opening or close) ................... 15
5.2.13 Request Status Stop & Go (Power failure downstream or close) ................ 16
5.2.14 Request Status Stop & Go (Power failure upstream or close) .................... 17
5.2.15 Start sending instantaneous consumption: ................................................. 17
5.2.16 Stop sending the instantaneous consumption ............................................ 18
5.2.17 Request the daily totalizers on an hourly basis for 16-bit for daily graphics 18
5.2.18 Request active power: ................................................................................ 18
5.2.19 Request energy / unit Totalizer: .................................................................. 19
5.2.20 Request Totalizer energy /units per month: ................................................ 19
5.2.21 Request partial Totalizer for current month: ................................................ 19
5.2.22 Request partial Totalizer for current day: .................................................... 19
5.2.23 Request actuators status: ........................................................................... 20
5.2.24 Request totalizers: ...................................................................................... 21
5.2.25 Request differential current level:................................................................ 22
5.3 Setup dimension ................................................................................................... 22
5.3.1 Automatic Update size: .................................................................................. 22
5.3.2 End Automatic Update size: ........................................................................... 22
6 EVENT CONNECTION............................................................................................... 24
6.1 Actuators status: ................................................................................................... 24
6.2 totalizers: .............................................................................................................. 24
6.3 Differential Current Level: ..................................................................................... 25
6.4 Answer to the active power request: ..................................................................... 25
6.5 Answer to the energy / unit totalizer request: ........................................................ 25
6.6 Answer to the totalizer energy/units per month request: ....................................... 25
6.7 Answer to the partial totalizer for current month request: ..................................... 25
6.8 Answer to the partial totalizer for current day request: .......................................... 25
1 DESCRIPTION
The following document describes the system of supervision (who=18). This system is
composed of various devices:
STOP&GO;
Centrale Energy Saving, load control, energy counters;
Actuators Energy saving;
Each of these devices will be identified by a different WHERE.
2 WHERE TABLE
VALUE DESCRIPTION
1N N=[1-127] Stop & Go

Energy Management Central Unit, Pulse Counter, Power
Meter:
5N N= [1-255]
Bticino reference: F520, F523, 3522.
Legrand reference:03555,03557, 03554
Energy Management Actuators:
7N#0 N= [1-255] Bticino reference: F522, F523
Legrand reference: 03558, 03559
3 WHAT TABLE
VALUE DESCRIPTION
26 Activation of the automatic reset
27 Deactivation of the automatic reset
Start sending daily totalizers on an hourly basis for 16-bit Daily
57
graphics
Start sending monthly on an hourly basis for 16-bit graphics average
58
Daily
Start sending monthly totalizers current year on a daily basis for 32-bit
59
Monthly graphics
Start sending monthly totalizers on a daily basis, last year compared
510
to 32-bit graphics TouchX Previous Year
71 Enable Actuator
73 Forced actuator for X Time
74 End forced Actuator

75 Reset totalizers
4 DIMENSION TABLE
VALUE DESCRIPTION
113 Active Power
1200 End Automatic Update size
51 Energy/Unit Totalizer
52 Energy/Unit pe month
53 Partial totalizer for current month
54 Partial totalizer for current day
71 Actuators info
72 Totalizers
73 Differential current level
250 Status Stop&Go (Général)
251 Status Stop&Go (open/close)
252 Status Stop&Go (failure/no failure)
253 Status Stop&Go(block/not block)
254 Status Stop&Go(open for CC between the N/not open for CC between the N/)
255 Status Stop&Go(opened ground falt/ not opened ground falt)
256 Status Stop&Go(open for Vmax/Not open for Vmax)
257 Status Stop&Go(Self-test disabled/close)
258 Status Stop&Go(Automatic reset off/close)
259 Status Stop&Go(check off/close)
260 Status Stop&Go(Witing for closing/close)
261 Status Stop&Go(First 24hours of opening/close)
262 Status Stop&Go(Power failure downstream/close)
263 Status Stop&Go(Power failure upstream/close)
511 Daily totalizers on an hourly basis for 16-bit Daily graphics
512 Monthly average on an hourly basis for 16-bit Media Daily graphics
513 Monthly totalizers current year on a daily basis for 32-bit Monthly graphics
Monthly totalizers on a daily basislast year compared to 32 bit graphics TouchX
514
Previous Year
5 ACTION CONNECTION
5.1 Command to be sent:

5.1.1 Activation of the automatic reset
Open Frame Note

Action Connection
Client Server *18*26*where## Stop&GO
5.1.2 Deactivation of the automatic reset

Client Server *18*27*where## Stop&GO
5.1.3 Start sending daily totalizers on an hourly basis for 16-bit for daily
graphics

<M> month
Client Server *18*57#<M>#<D>*where##
<D> day
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>##
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>## <Tag> number of the measure: 1 to 24
Client Server …. <Val> Watt/h
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>## <TOT> Daily Total Unit
*#18*<Where>*511#<M>#<D>*25*<TOT>##
5.1.4 Start sending Average monthly on an hourly basis for 16-bit for media
daily graphics:

Client Server *18*58#<M>*where## <M> month
<M> month
*#18*<Where>*512#<M>*<Tag>*<Val>##
Client Server <Tag> number of the measure: 1 to 24
*#18*<Where>*512#<M>*25*<MED>##
<Val> Watt/h average on a month
<MED> Monthly Average Wh /

Unit
5.1.5 Start sending monthly totalizers current year on a daily basis for 32-bit
for monthly graphics:

*#18*<Where>*513#<M>*<Tag>*<Val>##
*#18*<Where>*513#<M>*<Tag>*<Val>## <M> month
Client Server *#18*<Where>*513#<M>*<Tag>*<Val>## <Tag> the day from: 1 to 31
…
5.1.6 Start sending monthly totalizers on a daily basis, last year compared to
32-bit graphics Previous Year :

*#18*<Where>*514#<M>*<Tag>*<Val>## <M> month
*#18*<Where>*514#<M>*<Tag>*<Val>## <Tag> number of the measure: 1 to 31
Client Server *#18*<Where>*514#<M>*<Tag>*<Val>##
…
5.1.7 Actuator Enable:

*18*71*where##
Client Server
5.1.8 Forced Actuator for X Time:

<Time>
*18*73#<Time>*where## Expressed in Tens of min
Client Server values from 1 to 254
from 10m to 2h 20m
5.1.9 Forced actuator for Default Time:

*18*73*where##
Client Server
5.1.10 End forced Actuator:

*18*74*where##
Client Server
5.1.11 Reset totalizers:

*18*75#<Tot_N>*where## <Tot_N>
Client Server
Totalizer Number: values from 1 to 2
5.2 Dimensions request
5.2.1 Request Status Stop & Go

Client Server *#18*where*250## request Status control module systems
MASC: 13-bit mask that indicates the
device status
b13b12b11b10b9b8b7b6b5b4b3b2b1
The meaning of each bit is:
b1open
b2failure
b3block
b4Open for CC between the N
Client Server *#18*<Where>*250*<MASC>## b5Opened Ground Fault
b6Open for Vmax
b7Self-test disabled
b8Automatic reset off
b9Check off
b10Waiting for closing
b11First 24 hours of opening
b12Power failure downstream
b13Power failure upstream
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*253*<b3>## b2failure
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*255*<b5>## b4Open for CC between the N
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
b5Opened Ground Fault
*#18*<Where>*258*< b8>## b6Open for Vmax
*#18*<Where>*259*< b9>## b7Self-test disabled
*#18*<Where>*260*< b10>## b8Automatic reset off
*#18*<Where>*261*< b11>## b9Check off
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.2 Request Status Stop & Go (open or close)

Client Server *#18*where*251##
b1 = 1 means open
Client Server *#18*<Where>*251*<b1>##
b1 = 0 means close
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.3 Request Status Stop & Go (failure or no failure)

b2= 1 means failure
b2= 0 means no failure
*#18*<Where>*250*<MASC>## MASC: 13-bit mask that indicates the
*#18*<Where>*251*<b1>## device status
*#18*<Where>*252*<b2>## b13b12b11b10b9b8b7b6b5b4b3b2b1
*#18*<Where>*253*<b3>##
*#18*<Where>*254*<b4>##
*#18*<Where>*255*<b5>## b1open
Client Server
*#18*<Where>*257*< b7>## b3block
*#18*<Where>*258*< b8>## b4Open for CC between the N
*#18*<Where>*259*< b9>##
*#18*<Where>*260*< b10>##
b9Check off
5.2.4 Request Status Stop & Go (block or close)

b3= 1 means block
b3= 0 means close
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
b12Power failure in the valley
5.2.5 Request Status Stop & Go (open for CC between the N or close)

b4 = 1 means Open for CC between the N
b4= 0 means Close
Client Server
*#18*<Where>*253*<b3>## The meaning of each bit is:
*#18*<Where>*254*<b4>## b1open
*#18*<Where>*256*<b6>##
*#18*<Where>*257*< b7>##
b3block
*#18*<Where>*259*< b9>## b5Opened Ground Fault
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
b8Automatic reset off
b9Check off
5.2.6 Request Status Stop & Go (opened Ground fault or close)

b5 = 1 means opened ground fault
b5= 0 means close
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.7 Request Status Stop & Go (open for Vmax or close)

b6 =1 means open for Vmax

b6= 0 means close
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.8 Request Status Stop & Go (Self test disabled or Self test abled)

b7 =1 means self test disabled
b7= 0 means self test abled
device status
*#18*<Where>*250*<MASC>## b13b12b11b10b9b8b7b6b5b4b3b2b1
*#18*<Where>*251*<b1>## The meaning of each bit is:
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*253*<b3>##
*#18*<Where>*254*<b4>##
b2failure
*#18*<Where>*255*<b5>## b3block
Client Server
*#18*<Where>*259*< b9>##
*#18*<Where>*260*< b10>##
*#18*<Where>*263*< b13>## b10Waiting for closing
5.2.9 Request Status Stop & Go (automatic reset off or on)

b8 =1 means automatic reset off
b8= 0 means automatic reset on
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.10 Request Status Stop & Go (Check off or on)

b9 =1 means check off
b9= 0 means check on
*#18*<Where>*253*<b3>##
*#18*<Where>*255*<b5>## b1open
*#18*<Where>*257*< b7>## b3block

*#18*<Where>*261*< b11>##
*#18*<Where>*262*< b12>##
b9Check off
5.2.11 Request Status Stop & Go (waiting for closing or close)

b10 =1 Waiting for closing
b10= 0 means close
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.12 Request Status Stop & Go (first 24 hours of opening or close)

b11 =1 means first 24 hours of opening
b11= 0 means close

device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.13 Request Status Stop & Go (Power failure downstream or close)

b12 =1 Power failure downstream
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.14 Request Status Stop & Go (Power failure upstream or close)

b13 =1 Power failure upstream
device status
*#18*<Where>*250*<MASC>##
*#18*<Where>*251*<b1>##
*#18*<Where>*252*<b2>## b1open
*#18*<Where>*254*<b4>## b3block
*#18*<Where>*256*<b6>##
Client Server
*#18*<Where>*257*< b7>##
*#18*<Where>*262*< b12>##
*#18*<Where>*263*< b13>##
5.2.15 Start sending instantaneous consumption:

Time: Indicates after how many minutes
it sends the consumption if it changes.
*#18*<Where>*#1200#<Type>* Values from 1 to 255
Client Server <Time>##
Type: 1 = active power

*#18*<Where>*1200#<Type>*
Client Server
<Time>##
Val = Watt
Client Server *#18*<where>*113*<Val>##
5.2.16 Stop sending the instantaneous consumption

*#18*where*#1200#<Type>*0# Type = Type of Energy
Client Server #
1 = active power
*#18*where*1200#<Type>*0##
Client Server
5.2.17 Request the daily totalizers on an hourly basis for 16-bit for daily
graphics

*#18*<Where>*511#<M>#<D>## <M> month
Client Server
<D> day
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>##
Client Server …. <Val> Value Unit Watt/h
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>## <TOT> Daily Total Watt/h
*#18*<Where>*511#<M>#<D>*25*<TOT>##
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>##
Client Server …. <Val> Value Unit Watt/h
*#18*<Where>*511#<M>#<D>*<Tag>*<Val>## <TOT> Daily Total Watt/h
*#18*<Where>*511#<M>#<D>*25*<TOT>##
5.2.18 Request active power:

Client Server *#18*<Where>*113##
Client Server *#18*<Where>*113*<Val>## <Val> =WATT

Client Server *#18*<Where>*113*<Val>##
<Val> =Watt
5.2.19 Request energy / unit Totalizer:

*#18*where*51*<Val>##
Client Server Val> =Watt
Client Server *#18*where*51*<Val>##

Val> =Watt
5.2.20 Request Totalizer energy /units per month:

*#18*where*52#<Y>#<M>## <Y> Year in yy format
Client Server
<M> Month
*#18*where*52#<Y>#<M>*<Val < Val> =Watt
Client Server >##

*#18*where*52#<Y>#<M>*<Val Val> =Watt
Client Server >##
5.2.21 Request partial Totalizer for current month:

*#18*where*53##
Client Server Request partial totalizers for current month
*#18*where*53*<Val>##
*#18*where*53*<Val>##
5.2.22 Request partial Totalizer for current day:
*#18*where*54## request Status control module systems

Client Server
*#18*where*54*<Val>##
*#18*where*54*<Val>## Val> =Watt
Client Server
5.2.23 Request actuators status:

*#18*where*71##
Client Server
Disabled:
• 1 = Disabled
• 0 = Enabled
Forcing:
•1 = Forced
•0 = Not Forced
Threshold:
•1 = Below Threshold
*#18*where*71*<disabled>* •0 = Above Threshold
<forcing>*
Client Server
<threshold>*<protection>* Protection:
<phase>*<advanced>## •1 = Protection
•0 = Not Protection
phase
•1 = Disable of Local Phase
•0 = Disable of Other Phase
advanced
•1 = Advanced
•2 = Basic

Disabled:
• 1 = Disabled
*#18*where*71*<disabled>*
• 0 = Enabled
<forcing>*
Client Server
<threshold>*<protection>*
<phase>*<advanced>##
Forcing:
•1 = Forced
•0 = Not Forced
Threshold:
•0 = Above Threshold
Protection:
•1 = Protection
phase
advanced
•1 = Advanced
•2 = Basic
5.2.24 Request totalizers:

*#18*where*72#<Tot_N>## <Tot_N>
Client Server
<Tot_N>
<Energy>
Energy from the reset expressed in
*#18*where*72#<Tot_N>*<Energy>* Wh
Client Server <D>*<M>*<Y>*<H>*<m>##
<D>Day of the last reset
<M>Month of the last reset
<Y>Year of the last reset
<H>Hour of the last reset
<m> Minute of the last reset

<Tot_N>
*#18*where*72#<Tot_N>*<Energy>* <Energy>
Client Server <D>*<M>*<Y>*<H>*<m>##
Energy from the reset expressed in
Wh

5.2.25 Request differential current level:

*#18*where*73##
Client Server
*#18*where*73*<level >## <level >
Client Server
Values from 1 to 3
Client Server
Values from 1 to 3
5.3 Setup dimension
5.3.1 Automatic Update size:

Time: Indicates after how many minutes
it inform the status update.
values from 1 to 255.
*#18*<Where>*#1200#<Type>*
Client Server <Time>## Type: Type of Energy:
1 = active power

Val = Watt
Client Server *#18*<where>*113*<Val>##
5.3.2 End Automatic Update size:

*#18*where*#1200#<Type>*0# Type: Type of Energy:
Client Server #
1 = active power

*#18*where*#1200#<Type>*0#
Client Server #
6 EVENT CONNECTION
6.1 Actuators status:
Disabled:
• 1 = Disabled
• 0 = Enabled
Forcing:
•1 = Disabled
•0 = Enabled
Threshold:
*#18*where*71*<disabled>* •0 = Above Threshold
<forcing>*
Client Server
<threshold>*<protection>* Protection:
<phase>*<advanced>## •1 = Protection
phase
advanced
•1 = Advanced
•2 = Basic
6.2 totalizers:
<Tot_N>
<Energy>
*#18*where*72#<Tot_N>*<Energy>* Energy from the reset expressed in
Client Server <D>*<M>*<Y>*<H>*<m>## Wh
6.3 Differential Current Level:

Client Server
Values from 1 to 3
6.4 Answer to the active power request:

Client Server *#18*<Where>*113*<Val>##

Request active power
Val = Watt
6.5 Answer to the energy / unit totalizer request:

Client Server *#18*where*51*<Val>##

Request energy / unit Totalizer
Val = Watt
6.6 Answer to the totalizer energy/units per month request:

*#18*where*52#<Y>#<M>*<Val Request Totalizer energy /units per month
Client Server >## Val = Watt
6.7 Answer to the partial totalizer for current month

request:
Client Server
*#18*where*53*<Val>## Request partial Totalizer for current month
Val = Watt
6.8 Answer to the partial totalizer for current day request:

Client Server
*#18*where*54*<Val>## Request partial Totalizer for current day
Val = Watt
License
.
Disclaimers

1
Who = 22
Sound Diffusion
Version 1.1
My Open Staff
June 12, 2014

Contents
1 Introduction 4
1.1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 WHO 22 7
2.1 WHAT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 DIMENSION Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 WHERE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.1 Command session - Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 Turn OFF - What = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.2 Turn ON - What = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.3 Frequency Up - What = 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.4 Frequency Down - What = 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.5 Next Station - What = 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.6 Previous Station - What = 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.7 Next Track - What = 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.8 Previous Track - What = 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.9 Go To Source - What = 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.10 Start RDS message - What = 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.11 Stop RDS message - What = 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.12 Store Station - What = 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Command session - Speaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.1 Turn OFF - What = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.2 Turn ON - What = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.3 Increase Volume - What = 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.4 Decrease Volume - What = 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.5 Turn ON whit Follow me - What = 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.6 Turn ON Amplifier to certain source - What = 35 . . . . . . . . . . . . . . . . . . . . . . 13
3.2.7 Increment Low Tones - What = 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.8 Decrement Low Tones - What = 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.9 Increment Mid Tones - What = 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.10 Decrement Mid Tones - What = 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.11 Increment High Tones - What = 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.12 Decrement High Tones - What = 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.13 Increment Balance: Left > Right - What = 42 . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.14 Decrement Balance: Left < Right - What = 43 . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.15 Next Preset - What = 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.16 Previous Preset - What = 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Status request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3.1 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3.2 Speaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4 Dimension writing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4.1 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4.1.1 State Memorized Station - Dimension = 11 . . . . . . . . . . . . . . . . . . . . . 16
3.4.1.2 Device state - Dimension = 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4.2 Speakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2
CONTENTS
3.4.2.1 Volume - Dimension = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.4.2.2 High tones - Dimension = 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4.2.3 Medium tones - Dimension = 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4.2.4 Low tones - Dimension = 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4.2.6 Balance - Dimension = 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4.2.7 Preset - Dimension = 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4.2.8 Loudness - Dimension = 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5 Dimension request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5.1 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5.1.1 State frequency - Dimension = 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5.1.2 State station/track - Dimension = 6 . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5.1.3 State memorized station - Dimension = 11 . . . . . . . . . . . . . . . . . . . . . 18
3.5.2 Speakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2.1 Volume - Dimension = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2.2 High tones - Dimension = 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2.3 Medium tones - Dimension = 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2.4 Low tones - Dimension = 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2.6 Balance - Dimension = 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5.2.7 Preset - Dimension = 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5.2.8 Loudness - Dimension = 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3
Chapter 1
Introduction
This file is available from http://www.myopen-legrandgroup.com. The purpose of this document is to describe
the Open Web Net Message for WHO = 22 - Sound Diffusion System. In particular, the document contains the
"1.1 Abbreviations" section which describe some terms, with the relative values, used within the open message.
The second chapter, "WHO 22", contains the "WHAT", "DIMENSION" and "WHERE" tables, finally the chapter
3, "Allowed OPEN messages Session", contains command and event session, status request, dimension writing
and request for source and speakers.
1.1 Abbreviations
Name Description Range of Values

<mmtype> Multimedia type [1-4]; 11:
• 1 → Voice
• 2 → Canal Right
• 3 → Canal Left
• 4 → Canal Stereo
• 11 → All Source
<sourceID> Source address [1-4]

<area> Represents the output area [1-9]
where the source is ON
<point> Represents the speaker’s fonic [1-9]
point
<deviceState> Represents state of device [0-1]:
• 0 = OFF;
• 1 = ON
4
<freqStep> Frequency step value [1-15]:

• 1 = 50Hz;
• 2 = 100Hz;
• 3 = 150Hz;
• .........;
• .........;
• 15 = 750Hz
<freqValue> Frequency of the selected station

<modulation> Modulation type [1-4]:
• 1 = FM;
• 2 = AM-LW;
• 3 = AM-MW;
• 4 = AM-SW
<station> Number of memorized station [1-5]:
• F500
[1-15]:
• F500N
<track> Represents the number of track [1-999]

to select
<volumeStep> Represent the step of the volume [1-31]
increase
<volume> Volume of speaker [0-31]
<tonesValue> Indicates the values of tones [1-63]
<balanceValue> Indicates the values of balance [1-63]
<presetType> Indicates the number of selected [2-11]:
preset
• 2 = Normal;
• 3 = Dance;
• 4 = Pop;
• 5 = Rock;
• 6 = Classic;
• 7 = Techno;
• 8 = Party;
• 9 = Soft;
• 10 = Full bass;
• 11 = Full treble;
• 16-25 = User defined preset
<3dLevel> Level of 3D effect [0-10]
5
<loudness> Represent the state of loudness [0-1]:

• 0 = OFF;
• 1 = ON
<equalizationX> Equalization X[1-3]

<band> if X values in equalization is:
• 1→band=BAND1*BAND2*
BAND3;
• 2→band=BAND4*BAND5*
BAND6;
• 3→band=BAND7*BAND8;
Ack The command has been sent to *#*1##

Bus
6
CHAPTER 2. WHO 22
Chapter 2
WHO 22
2.1 WHAT Table
Value Description
0 Turn off
1 Turn on
2 Source turned on
3 Increase volume
4 Decrease volume
5 Automatic tuner search towards higher frequencies
6 Manual tuner search towards lower frequencies
9 Go to a following station
10 Go to a previous station
11 Go to a following track
12 Go to a previous track
22 Sliding request
31 Ask a source to start telling RDS message
32 Ask a source to stop telling RDS message
33 Store the presently tuned frequency on a certain station
34 Turn ON Amplifier with follow me method
35 Turn ON Amplifier to a certain source
36 Increment Low Tones
37 Decrement Low Tones
38 Increment Mid Tones
39 Decrement Mid Tones
40 Increment High Tones
41 Decrement High Tones
42 Increment balance (left>right)
43 Decrement balance (left<right)
55 Next Preset
56 Previous Preset
2.2 DIMENSION Table
Value Description
1 Volume
2 High Tones
3 Medium Tones
4 Low Tones
5 Frequency
6 Track/station
7
CHAPTER 2. WHO 22
7 Play status
11 Frequency and Station
12 Device state
17 Balance
18 3D
19 Preset
20 Loudness
2.3 WHERE Table
Description Value
Source 2#sourceID
Speaker 3#area#point
Speaker Area 4#area
General 5#sender_address
All Source 6
8
Chapter 3
3.1 Command session - Source

Command Open Frame

Client → Server *22*0#<mmtype>#<area>*2#<sourceID>##

Server → Client *#22*2#<sourceID>*12*<deviceState>*<mmtype>##
Command Open Frame


Server → Client *22*21#<mmtype>#<area>*5#2#<sourceID>##
3.1.3 Frequency Up - What = 5

Client → Server *22*5#*2#<sourceID>## source allowed: radio
the search is automatic
Client → Server *22*5#<freqStep>*2#<sourceID>## source allowed: radio

Server → Client *#22*where*5*<modulation>*<freqValue>##
9
3.1.4 Frequency Down - What = 6

the search is automatic
Client → Server *22*6#<freqStep>*2#<sourceID>##

Server → Client *#22*where*5*<modulation>*<freqValue>##
3.1.5 Next Station - What = 9


Server → Client *#22*5#2#<sourceID>*5*<modulation>*<freqValue>##
Server → Client *#22*5#2#<sourceID>*11*<modulation>*<freqValue>*<station>##
Server → Client *#22*2#<sourceID>*6*<station>##
3.1.6 Previous Station - What = 10


3.1.7 Next Track - What = 11

Client → Server *22*11#*2#<sourceID>## source allowed:
• Aux;
• Multimedia SCS Source
Client → Server *22*11#<freqStep>*2#<sourceID>## source allowed:

• Aux;

• <freqStep>= if not speci-
fied the step is = 1
10

Server → Client No event session
3.1.8 Previous Track - What = 12

Client → Server *22*12#*2#<sourceID>## source allowed:
• Aux;
Client → Server *22*12#<freqStep>*2#<sourceID>## source allowed:
• Aux;
• <freqStep>= if not speci-
fied the step is = 1

3.1.9 Go To Source - What = 22


3.1.10 Start RDS message - What = 31

Client → Server *22*31#<sourceID>## source allowed: radio

Server → Client *#22*where*10*VAL1*VAL2*VALn##
3.1.11 Stop RDS message - What = 32

Client → Server *22*32#<sourceID>## source allowed: radio
11

3.1.12 Store Station - What = 33

Client → Server *22*33#<station>*2#<sourceID>## source allowed: radio

Server → Client *#22*2#<sourceID>*6*station##
3.2 Command session - Speaker

Command Open Frame

Client → Server *22*0#<mmtype><area>*3#<area><point>##

Server → Client *#22*3#<area>#<point>*12*<deviceState>*<mmtype>##
Command Open Frame

Client → Server *22*1#<mmtype><area>*3#<area><point>##

Server → Client *#22*3#<area>#<point>*1*<volume>*##
3.2.3 Increase Volume - What = 3
Command Open Frame

Client → Server *22*3#<volumeStep>*3#<area>#<point>##

3.2.4 Decrease Volume - What = 4
Command Open Frame

Client → Server *22*4#<volumeStep>*3#<area>#<point>##
12

3.2.5 Turn ON whit Follow me - What = 34
Command Open Frame

Client → Server *22*34#<mmtype>#<area>*3#<area>#<point>##

3.2.6 Turn ON Amplifier to certain source - What = 35
Command Open Frame

Client → Server *22*35#4#<area>#<sourceID>*3#<area>#
<point>##

Server → Client *22*2#<mmtype>#area*5#2#<sourceID>##
Server → Client *#22*3#<area>#<point>*1*<volume>##
3.2.7 Increment Low Tones - What = 36
Command Open Frame

Client → Server *22*36#<tonesValue>*3#<area>#<point>##

Server → Client *#22*3#<area>#<point>*2*<tonesValue>##
3.2.8 Decrement Low Tones - What = 37
Command Open Frame


13
3.2.9 Increment Mid Tones - What = 38
Command Open Frame


3.2.10 Decrement Mid Tones - What = 39
Command Open Frame


3.2.11 Increment High Tones - What = 40
Command Open Frame


3.2.12 Decrement High Tones - What = 41
Command Open Frame


3.2.13 Increment Balance: Left > Right - What = 42
Command Open Frame

Client → Server *22*42#<balanceValue>*3#<area>#<point>##

Server → Client *#22*3#<area>#<point>*17*<value>##
14
3.2.14 Decrement Balance: Left < Right - What = 43
Command Open Frame

Client → Server *22*43#<balanceValue>*3#<area>#<point>##

Server → Client *#22*3#<area>#<point>*17*<value>##
3.2.15 Next Preset - What = 55
Command Open Frame

Client → Server *22*55##<area>#<point>##

Server → Client *#22*3#<area>#<point>*19*<presetType>##
Server → Client *#22*3#<area>#<point>*18*<3dLevel>##
Server → Client *#22*3#<area>#<point>*20*<loudness>##
Server → Client *#22*3#<area>#<point>*21#1*<band>##
3.2.16 Previous Preset - What = 56
Command Open Frame

Client → Server *22*56##<area>#<point>##

3.3 Status request

3.3.1 Source
Command Open Frame


Server → Client *#22*2#<sourceID>*12*<deviceState>*<mmtype>## if where is 5#2#sourceID in sta-
tus request then we have a di-
mension 12 for each source and
speaker
15
3.3.2 Speaker
Command Open Frame

Client → Server *#22*3#<area>#<point>##

3.4 Dimension writing

3.4.1 Source
3.4.1.1 State Memorized Station - Dimension = 11
Command Open Frame

Client → Server *#22*5#2#<sourceID>*#11*<modulation>*<freqValue>*<station>##

3.4.1.2 Device state - Dimension = 12
Command Open Frame

Client → Server *#22*5#2#<sourceID>*#12*<deviceState>*<mmtype>##

3.4.2 Speakers
3.4.2.1 Volume - Dimension = 1
Command Open Frame

Client → Server *#22*3#<area>#<point>#1*<volumeStep>##

Server → Client *#16*<area><point>*1*<volume>##
3.4.2.2 High tones - Dimension = 2
Command Open Frame

Client → Server *#22*3#<area>#<point>#2*<tonesValue>##
16

Server → Client *#22*3#<area>#<point>*4*4##
3.4.2.3 Medium tones - Dimension = 3
Command Open Frame


3.4.2.4 Low tones - Dimension = 4
Command Open Frame


Command Open Frame

Client → Server *#22*3#<area>#<point>*#12*<deviceState>*<mmtype>##

3.4.2.6 Balance - Dimension = 17
Command Open Frame

Client → Server *#22*3#<area>#<point>*#17*<balanceValue>##

Server → Client *#22*3#<area>#<point>*17*<balanceValue>##
3.4.2.7 Preset - Dimension = 19
Command Open Frame

Client → Server *#22*3#<area>#<point>*#19*<presetType>##
17

Server → Client *#22*3#<area>#<point*18*<3dLevel>##
Server → Client *#22*3#<area>#<point*19*<presetType>##
Server → Client *#22*5#3#<area>#<point*21#<equalization1>*<band>##
3.4.2.8 Loudness - Dimension = 20
Command Open Frame

Client → Server *#22*3#<area>#<point>*#20*<loudness>##

3.5 Dimension request

3.5.1 Source
3.5.1.1 State frequency - Dimension = 5
Command Open Frame

Client → Server *#22*5#2#<sourceID>*5##

Server → Client *#22*2#<sourceID>*11*<modulation>*<freqValue>*<station(or track)>##
3.5.1.2 State station/track - Dimension = 6
Command Open Frame

Server → Client *#22*5#2#<sourceID>*6*<station(or track)>##

Server → Client *#22*2#<sourceID>*5*<modulation>*<freqValue>##
Server → Client *#22*2#<sourceID>*6*<station(or track)>##
Server → Client *#22*2#<sourceID>*11*<modulation>*<freqValue>*<station(or track)>##
3.5.1.3 State memorized station - Dimension = 11
Command Open Frame

Server → Client *#22*5#2#<sourceID>*11*<modulation>*<freqValue>*<station(or track)>##
18

Server → Client *#22*5#2#<sourceID>*11*<modulation>*<freqValue>*<station(or track)>##
Command Open Frame


3.5.2 Speakers
3.5.2.1 Volume - Dimension = 1
Command Open Frame

Client → Server *#22*3#<area>#<point>*1##

Server → Client *#16*<area><point>*1*<volume>##
3.5.2.2 High tones - Dimension = 2
Command Open Frame


3.5.2.3 Medium tones - Dimension = 3
Command Open Frame


3.5.2.4 Low tones - Dimension = 4
19
Command Open Frame

Client → Server *#22*3#<area>#<point>*4*<tonesValue>##

20
Command Open Frame


Server → Client *16*3*<area><point>##
3.5.2.6 Balance - Dimension = 17
Command Open Frame


Server → Client #22*3#<area#<point>*17*<balanceValue>##
3.5.2.7 Preset - Dimension = 19
Command Open Frame


3.5.2.8 Loudness - Dimension = 20
Command Open Frame


21
My Open Web Net

WHO = 24
Brand Item
Legrand
BTicino
Document History
Version Date Author

1.0.0 30/03/2012 My Open Staff
Updating description: First Version
Index
WHO = 24 LIGHTING MANAGEMENT ....................................................................... 4
1 Table WHAT ............................................................................................................... 4
2 Table WHERE ............................................................................................................ 4
2.1 Examples................................................................................................................ 4
3 Table DIMENSIONS ................................................................................................... 5
4 Open messages: command session ........................................................................... 6
4.1 Set up Switch On Level .......................................................................................... 6
4.2 Set up Max Lux Level ............................................................................................. 7
4.3 Set up Maintained Level ......................................................................................... 8
4.4 Set Auto Switch On Enable/Disable ...................................................................... 9
4.5 Set up Switch On Delay........................................................................................ 10
4.6 Set Auto Switch Off Enable/Disable .................................................................... 11
4.7 Set up Switch Off Delay........................................................................................ 12
4.8 Set up Delay Timer ............................................................................................... 13
4.9 Set up Stand-by Timer.......................................................................................... 14
4.10 Set up Stand-by Value ..................................................................................... 15
4.11 Set up OFF Value............................................................................................. 16
4.12 Set up Slave Offset (GAP) value ...................................................................... 17
4.13 Set State ......................................................................................................... 19
4.14 Set Centralised lux-value ................................................................................ 21
4.15 Activation Profile Frame ................................................................................... 23
4.16 Enable/Disable Slave Offset............................................................................. 24
5 Open messages: Request commands ...................................................................... 25
5.1 Switch ON level request ....................................................................................... 25
5.2 Max Lux Level request ......................................................................................... 26
5.3 Maintained Level request ..................................................................................... 27
5.4 Request Auto Switch On Enable/Disable ............................................................ 28
5.5 Switch On Delay request ...................................................................................... 28
5.6 Request Auto Switch Off Enable/Disable ............................................................. 30
5.7 Switch Off Delay request ...................................................................................... 31
5.8 Delay Timer request ............................................................................................. 32
5.9 Stand-by Timer request ........................................................................................ 33
5.10 Stand-by Value request .................................................................................... 34
5.11 OFF Value request ........................................................................................... 35
5.12 Slave Offset (GAP) value request .................................................................... 36
5.13 State request .................................................................................................... 37
5.14 Centralised lux-value request ........................................................................... 39
6 Open messages: Event sessions ............................................................................. 40
6.1 State change ........................................................................................................ 40
6.2 Centralised lux-value ............................................................................................ 41
License.............................................................................................................................. 42
Disclaimers ....................................................................................................................... 42
WHO = 24 LIGHTING MANAGEMENT

In this document you can find the Open frames which implement lightning function of a My
Home system.
1 Table WHAT
1#PROFILE_ID Profile Frame

2#[0-1] Slave Offset Enable/Disable
2 Table WHERE
RECIPIENT SENDER
LM_zone_num # dev_type & sys_addr #00# LM_zone_num # dev_type & sys_addr
LM_zone_num
Code Description
0 No zones
1000+zone number Zone selection
1000 Every zones
dev_type
Code Description
1 BMNE500/002645 device
99991 Lighting Console
9991 Virtual Configurator
4 Broadcast
8 Unknown
sys_addr
From number 1 to 9
2.1 Examples
• Configuration software: maintained level set frame: *#24*1001#8#00#0#8*#3*200##

• Lighting console: new maintained level value for a zone:
*#24*1001#11#00#0#999911*#3*200## (Sys_addr of BMNE500 is 1, sys_addr of
lighting console is 1 too)
• Lighting console: request of zone’s maintained level value:

*#24*1001#11#00#0#999911*3##
• BMNE500: response to Lighting console request of zone’s maintained level value:
*#24*0#99991#00#1001#11*3*200##
• BMview: request of Centralised LUX-value frame
*#24*1000#4#00#0#8*18#65##
• BMNE500: answer for BMview request
*#24*0#8#00#1001#11*18#65*297*0##
3 Table DIMENSIONS
1 Switch ON
2 Max Lux
3 Maintained Level
4 Automatic Switch ON
5 Switch ON Delay
6 Automatic Switch OFF
7 Switch OFF Delay
8 Delay Timer
9 Stand-by Timer
10 Stand-by value
11 Off value
12 Slave Offset (GAP) value
17 State (Automatic/Manual/Stop)
18 Centralised Lux value
4 Open messages: command session
4.1 Set up Switch On Level
Commands session Open frames Notes
WHERE:
zone_num # dev_type & sys_addr

#00#
TCP/IP: The increase of the

*#24*WHERE*#1*Switch_on##
Client -> Server luminosity intensity of the
light point at switch on for
presence; expressed as a
Switch_on percentage value:
1-100
1= lower luminosity
intensity
100=maximum luminosity
intensity
*#*1## ACK: if the command is sent to the Bus

TCP/IP
or NACK: if the command is not sent to the
Server -> Client
*#*0## Bus
WHERE:

#00#

*#24*WHERE*1*Switch_on##
Server -> Client luminosity intensity of the
light point at switch on
1-100
1= lower luminosity
intensity
intensity
4.2 Set up Max Lux Level
WHERE:

#00#
TCP/IP:
*#24*WHERE*#2*Max_lux##
Client -> Server
Maximum level supplied by
lamps; expressed in LUX
value:
Max_lux
1-2000 1= lower luminosity
intensity
intensity

TCP/IP
Server -> Client
*#*0## Bus
WHERE:
1000 + zone_num # dev_type & sys_addr

#00#
1000 + zone_num # dev_type & sys_addr
TCP/IP:
*#24*WHERE*2*Max_lux##
Server -> Client
value:
Max_lux
intensity
intensity
4.3 Set up Maintained Level
WHERE:

#00#
TCP/IP:
*#24*WHERE*#3*Maint_lev##
Client -> Server
Default light level to be
maintained; expressed as
LUX value:
Maint_lev
intensity
intensity

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*3*Maint_lev##
Server -> Client
LUX value:
Maint_lev
intensity
intensity
4.4 Set Auto Switch On Enable/Disable
WHERE:

#00#
TCP/IP:
*#24*WHERE*#4*Auto_sw_on##
Client -> Server
Automatic switch on of
Auto_sw_on lamps :
0-1
0= disable
1=enable

TCP/IP
Server -> Client
*#*0## Bus

TCP/IP:
*#24*WHERE*4* Auto_sw_on ## WHERE:
Server -> Client

#00#
Auto_sw_on lamps :
0-1
0= disable
1=enable
4.5 Set up Switch On Delay
WHERE:

#00#
TCP/IP:
*#24*WHERE*#5*Sw_on_delay##
Client -> Server
Delay of answer occurring

Sw_on_delay when the light level is
0-300 varying; expressed in
seconds

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*5*Sw_on_delay##
Server -> Client

seconds
4.6 Set Auto Switch Off Enable/Disable
WHERE:

#00#
TCP/IP:
*#24*WHERE*#6*Auto_sw_off##
Client -> Server
Automatic switch off of

Auto_sw_off lamps :
0-1
0= disable
1=enable

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*6* Auto_sw_off##
Server -> Client

Auto_sw_off lamps :
0-1
0= disable
1=enable
4.7 Set up Switch Off Delay
WHERE:

#00#
TCP/IP:
*#24*WHERE*#7*Sw_off_delay##
Client -> Server
Time after which the
central unit switches off the
Sw_off_delay lights if the automatic
0-900 switch is selected;
expressed in seconds

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*7*Sw_off_delay##
Server -> Client
4.8 Set up Delay Timer
WHERE:

#00#
TCP/IP:
*#24*WHERE*#8*Delay_timer##
Client -> Server
Time after which, if the

Delay_timer sensor does not detect
0-3600 any presence, it takes
lights to OFF value;

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*8*Delay_timer##
Server -> Client
sensor does not detect
Delay_timer any presence, it takes
0-3600 lights to OFF value;
4.9 Set up Stand-by Timer
WHERE:

#00#
TCP/IP:
*#24*WHERE*#9*Standby_timer##
Client -> Server
any presence, it drops
Standby_timer the light level to a level
0-900 which is lower than the
default one ; expressed
in seconds
*#*1##
TCP/IP ACK: if the command is sent to the Bus
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*9*Standby_timer##
Server -> Client
sensor does not detect any
Standby_timer presence, it drops the light
0-900 level to a level which is
lower than the default one ;
4.10 Set up Stand-by Value
WHERE:

#00#
TCP/IP:
*#24*WHERE*#10*Standby_val## Light level to which lights
Client -> Server
are dimmed after a
certain stand-by
timer;expressed as a
Standby_val percentage value:
0-100
1= lower luminosity
intensity
100=maximum
luminosity intensity
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*10*Standby_val##
Server -> Client Light level to which lights
are dimmed after a certain
stand-by timer; expressed
Standby_val as a percentage value:
0-100
1= lower luminosity
intensity
intensity
4.11 Set up OFF Value
WHERE:

#00#
TCP/IP:
*#24*WHERE*#11*Off_val##
Client -> Server
It is the light value at
switch OFF; expressed
as a percentage value:
Off_val
intensity
100=maximum
luminosity intensity
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*11*Off_val##
Server -> Client
switch OFF; expressed as
a percentage value:
Off_val
intensity
intensity
4.12 Set up Slave Offset (GAP) value
WHERE:

#00#
TCP/IP:
*#24*WHERE*#12*Slave_offset##
Client -> Server
Level which dimmers in
master mode shall reach
Slave_offset before the switching-on
0-100 of dimmers in slave
mode; expressed as a
percentage value
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*12*Slave_offset##
Server -> Client
master mode shall
Slave_offset reach before the
0-100 switching-on of dimmers
in slave mode;
expressed as a
percentage value
4.13 Set State
Commands
session Open frames Notes
WHERE:

#00#
Functioning mode of the zone:

MOD
0 STOP
0-2
1 AUTOMATIC
TCP/IP: 2 MANUAL
Client -> *#24*WHERE*#17*MOD*EXIT*TIME##
Server
Condition to return to Automatic
mode:
EXIT
1 TIME mode
1-5
2 FOR mode
3 PROFILE mode
4 NORMAL mode
5 NEVER mode
TIME
Time or duration for Exit mode
[0-23]*[0-
(“time” or “for”)
59]*[0-59]
TCP/IP *#*1##
ACK: if the command is sent to the Bus
Server -> or
NACK: if the command is not sent to the Bus
Client *#*0##
Commands
WHERE:

#00#

MOD
0 STOP
0-2
1 AUTOMATIC
TCP/IP: 2 MANUAL
Server-> *#24*WHERE*17*MOD*EXIT*TIME##
Client
mode:
EXIT
1 TIME mode
1-5
2 FOR mode
3 PROFILE mode
4 NORMAL mode
5 NEVER mode
TIME
[0-23]*[0-
59]*[0-59]
4.14 Set Centralised lux-value
Commands
WHERE:

#00#
Address of the sensor

Sensor_addr
TCP/IP:
*#24*WHERE*#18*
Client ->
Sensor_addr*Lux_level*Err ##
Server
Light intensity wants to set;
Lux_level
expressed in LUX value
0 - all sensors have every

parameters needed
Err
1 - sensor is not in configuration
0-2
2 - sensor present but doesn't
have all parameters needed
TCP/IP *#*1##
Server -> or
Client *#*0##
Commands
WHERE:

#00#

Sensor_addr
TCP/IP:
*#24*WHERE*18*
Server ->
Sensor_addr*Lux_level*Err ##
Client
Light intensity seted; expressed
Lux_level
in LUX value

parameters needed
Err
0-2
4.15 Activation Profile Frame
WHERE:

#00#
TCP/IP: zone_num # dev_type & sys_addr
*24*1#Profile_ID*WHERE##
Client -> Server
Identification profile
Profile_ID number
*#*1##
or
*#*0##
4.16 Enable/Disable Slave Offset
WHERE:

#00#

*24*2#Slave_offset_flag*WHERE##
Client -> Server
Enable/disable Slave
Offset
Slave_offset_flag
0-1 0 Disable
1 Enable

TCP/IP
Server -> Client
*#*0## Bus
5 Open messages: Request commands
5.1 Switch ON level request
WHERE:

*#24*WHERE*1##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#

*#24*WHERE*1*Switch_on##
Server -> Client luminosity intensity of the
light point at switch on
1-100
1= lower luminosity
intensity
intensity
5.2 Max Lux Level request
WHERE:

*#24*WHERE*2##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*2*Max_lux##
Server -> Client
value:
Max_lux
intensity
intensity
5.3 Maintained Level request
WHERE:

*#24*WHERE*3##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*3*Maint_lev##
Server -> Client
LUX value:
Maint_lev
intensity
intensity
5.4 Request Auto Switch On Enable/Disable
WHERE:

*#24*WHERE*4##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*4* Auto_sw_on ##
Server -> Client
Auto_sw_on lamps :
0-1
0= disable
1=enable
5.5 Switch On Delay request
WHERE:

*#24*WHERE*5##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*5*Sw_on_delay##
Server -> Client

seconds
5.6 Request Auto Switch Off Enable/Disable
WHERE:

*#24*WHERE*6##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*6* Auto_sw_off##
Server -> Client

Auto_sw_off lamps :
0-1
0= disable
1=enable
5.7 Switch Off Delay request
WHERE:

*#24*WHERE*7##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*7*Sw_off_delay##
Server -> Client
5.8 Delay Timer request
WHERE:

*#24*WHERE*8##
Client -> Server
#00#

TCP/IP
Server -> Client
*#*0## Bus
WHERE:

#00#
TCP/IP:
*#24*WHERE*8*Delay_timer##
Server -> Client
Delay_timer any presence, it takes
0-3600 lights to OFF value;
5.9 Stand-by Timer request
WHERE:

*#24*WHERE*9##
Client -> Server
#00#
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*9*Standby_timer##
Server -> Client
sensor does not detect any
Standby_timer presence, it drops the light
0-900 level to a level which is
lower than the default one ;
5.10 Stand-by Value request
WHERE:

*#24*WHERE*10##
Client -> Server
#00#
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*10*Standby_val##
Server -> Client Light level to which lights
are dimmed after a certain
stand-by timer; expressed
Standby_val as a percentage value:
0-100
0= lower luminosity
intensity
intensity
5.11 OFF Value request
WHERE:

*#24*WHERE*#11*Off_val##
Client -> Server
#00#
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*11*Off_val##
Server -> Client
switch OFF; expressed as
a percentage value:
Off_val
intensity
intensity
5.12 Slave Offset (GAP) value request
WHERE:

*#24*WHERE*12*##
Client -> Server
#00#
*#*1##
or
*#*0##
WHERE:

#00#
TCP/IP:
*#24*WHERE*12*Slave_offset##
Server -> Client
master mode shall
Slave_offset reach before the
0-100 switching-on of dimmers
in slave mode;
expressed as a
percentage value
5.13 State request
Commands
WHERE:
TCP/IP:
Client -> *#24*WHERE*17## zone_num # dev_type & sys_addr
Server #00#
TCP/IP *#*1##
Server -> or
Client *#*0##
Commands
WHERE:

#00#

MOD
0 STOP
0-2
1 AUTOMATIC
TCP/IP: 2 MANUAL
Client
mode:
EXIT
1 TIME mode
1-5
2 FOR mode
3 PROFILE mode
4 NORMAL mode
5 NEVER mode
TIME
[0-23]*[0-
59]*[0-59]
5.14 Centralised lux-value request
Commands
WHERE:
TCP/IP: #00#
Client -> *#24*WHERE*18*Sensor_addr## zone_num # dev_type & sys_addr
Server
Sensor_addr Address of the sensor
TCP/IP *#*1##
Server -> or
Client *#*0##
Commands
WHERE:

#00#

Sensor_addr
TCP/IP:
*#24*WHERE*18*
Server ->
Sensor_addr*Lux_level*Err##
Client
Light intensity detected;
Lux_level

parameters needed (NO errors)
Err
0-2
6 Open messages: Event sessions
6.1 State change
Commands
WHERE:

#00#

MOD
0 STOP
0-2
1 AUTOMATIC
TCP/IP: 2 MANUAL
Client
mode:
EXIT
1 TIME mode
1-5
2 FOR mode
3 PROFILE mode
4 NORMAL mode
5 NEVER mode
TIME
[0-23]*[0-
59]*[0-59]
6.2 Centralised lux-value
Commands
WHERE:

#00#

Sensor_addr
TCP/IP:
*#24*WHERE*18*
Server ->
Sensor_addr*Lux_level*Err##
Client
Light intensity detected;
Lux_level

parameters needed (no errors)
Err
0-2
License
.
Disclaimers

DRY CONTACT AND IR STATE

FUNCTIONS
Brand Item
573996, 03553
Legrand 067513, 003573
573936, 573937
573938, 573939
3477, F428
BTicino 3480, F482,
IR 4610, 4611, 4640
Document History
Version Date Author

1.0.0 01/11/2010 My Open Staff
Index
Document History ................................................................................................................ 2

DESCRIPTION .................................................................................................................... 3
OPEN WEB NET WHO = 25 ............................................................................................... 4
1.1 Virtual ON / IR Detection ........................................................................................ 5
1.2 Virtual OFF / IR not/end Detection .......................................................................... 5
1.3 Request of Contact / IR State ................................................................................. 5
EVENT CONNECTION ........................................................................................................ 6
2.1 State On / IR Detection after a system event .......................................................... 6
2.2 State ON / IR Detection after a state request ......................................................... 6
2.3 State OFF / IR end Detection after a system event ................................................ 6
2.4 State OFF / IR not Detection after a state request .................................................. 6
EXAMPLE ............................................................................................................................ 7
General Information about devices configuration............................................................... 10
Devices that allow the function .......................................................................................... 13
How a Touch Screen manages the function ...................................................................... 13
Gateways that allow the function ....................................................................................... 13
DESCRIPTION
Dry Contact Interfaces and some IR Interfaces are able to provide the state of their
contacts / IR.
The last version of My Home gateways are able to translate the state of these devices in
Open Web Net messages.
This function is really useful to know the state of the system and to execute or condition
scenarios.
The alarm devices are able to provide the state information in any case, when the burglar
alarm system is engaged or not engaged.
For example, if a dry contact interface is used to detect an intrusion on a window, this
device can be used to know the status of the windows: opened / closed.
This information can be used:
- to run a scenario: when the window is opened, heating off
- to monitor the window state from a remote application

DRY CONTACT
WHAT TABLE
CONNECTION 3
VALUE DESCRIPTION
ACTION EVENT
31 ON / IR Detection W/R R
32 OFF / IR not/end Detection W/R R
CONNECTION 3
ACTION EVENT
0 State if requested R R
State if an event happens in the
1 W/R R
System
WHERE TABLE
VALUE DESCRIPTION
For automation dry contact interface
(3477 and F428, 573996 and 03553)
3 [1-201]
WHERE is configured only using
Virtual Configurator Software
For alarm dry contact interface and IR
(3480, F482, IR 4610, 4611, 4640
3 [1-9][1-9] 067513, 003573, 573936, 573937,573938, 573939)
WHERE is configured using Z and N
with physical configurators
ACTION CONNECTION
Command messages
1.1 Virtual ON / IR Detection

Client → Server *25*31#1*WHERE##
Client ← Server *25*31#1*WHERE##
1.2 Virtual OFF / IR not/end Detection

Client → Server *25*32#1*WHERE##
Request massage
1.3 Request of Contact / IR State

Client → Server *#25*WHERE##
VALUE
Client ← Server *25*VALUE#0*WHERE## 31 if ON / IR Detection
32 if OFF / IR no Detection
Client ← Server *25*VALUE#0*WHERE##
EVENT CONNECTION
2.1 State ON / IR Detection after a system event

2.2 State ON / IR Detection after a state request

2.3 State OFF / IR end Detection after a system event

2.4 State OFF / IR not Detection after a state request

EXAMPLE
IR x1 on Alarm BUS IR x2 on automation BUS

Z 1 Z 9
N 1 N 9
MOD Empty MOD AUX
AUX AUX AUX AUX
Alarm Dry Contact Interface Automation Dry Contact Interface

Z1 2 Channel 1 1
N1 2 Channel 2 201
MOD1 AUX
IR x1 detects presence, after 6 seconds it ends.
Event Connection Time OWN Frame Event

Client ← Server 16:51:08:975 *25*31#1*311## Presence detection
Client ← Server 16:51:14:861 *25*32#1*311## Presence end
A Software requests the state of the IR x1.

Client Æ Server 16:45:11:990 *#25*311## State request
Client ← Server 16:45:12:068 *25*31#0*311##* State requested
Client ← Server 16:45:12:068 *25*31#0*311## State requested
IR x2 detects presence, after 62 seconds it ends

Client ← Server 17:02:49:788 *25*31#1*399## Presence detection
Client ← Server 17:03:51:209 *25*32#1*399## Presence end
A Software requests the state of IR x2 during the presence detected.

The Alarm Dry Contact Interface close the contact and then open it.

Client ← Server 16:52:04:171 *25*31#1*322## Contact closing
Client ← Server 16:53:01:110 *25*32#1*322## Contact opening
A software request the state of the contact of the Alarm Dry Contact Interface.

The Automation Dry Contact Interface – Channel 1, closes and opens the contact.

A software requests the state of the contact – channel 1 while it’s opened.

The Automation Dry Contact Interface – Channel 2 closes and opens the contact.

A software request the state of the Dry Contact – Channel 2 while it’s closed.

General Information about devices configuration

The following configurations are required to use the state information coming from dry
contact interfaces and IR devices.
AUTOMATION DRY CONTACTS CONFIGURATION
ALARM DRY CONTACTS CONFIGURATION
Just contact function Alarm plus contact function

Zx 1-9 Zx 1-9
Nx 1-9 Nx 1-9
MODx AUX MODx 4-7
ALARM IR CONFIGURATION
Just contact function Alarm plus contact function

Z 1-9 Z 1-9
N 1-9 N 1-9
MOD AUX MOD empty
AUX AUX AUX AUX
Devices that allow the function
BTicino Legrand Data

3477 573996 10W14
F428 03553 10W14
3480 067513 All
F482 003573 All
H / L / N 4610 / AM5790 573936 / 573937 01W08
H / L / N 4611 / AM5791 573938 / 573939 01W08
N4640 01W08
How a Touch Screen manages the function
BTicino Legrand FW Function Available

TS 3.5’’ TS 3.5’’ 5.0.33 NO
TS 3.5’’ TS 3.5’’ 6.0.7 YES
TS 10’’ TS 10’’ 1.0.36 NO
TS 10’’ TS 10’’ 2.0.x YES
Gateways that allow the function
BTicino Legrand Function Available

MH200 NO
MH200N 03565 YES
F453AV (v1.0.19) NO
F453AV (v2.1.7) 573992 (v2.1.7) YES
F453 YES
F452V NO
F452 NO

OWN Full

Uploaded by

Copyright:

Available Formats

You might also like

OWN Full

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OWN Full

Uploaded by

Copyright:

Available Formats

Open Web Net Language

My Open Web Net Introduction

Version Date Author

Updating description: Second Version

OPEN = Open Protocol for Electronic Networks

SYNTAX OF AN OPEN MESSAGE

An Open frame is composed by characters belonging to the following collection:

The character ‘*’ is also used as a separator among the tags.

A tag is composed by characters belonging to this set:

The Open Client can establish two different kinds of sessions:

- Command Session (actions): used to send commands, status requests, dimen-

Example of communication stream

[For further information:

Example connection commands session:

Example Event Session:

Programmed Scenario Session

Example Programmed Scenario Session:

Particular Open Messages

COMMAND / STATUS OPEN FRAMES

The Open message, that has this function is so structured:

• Commands / Actions session:

STATUS REQUEST OPEN FRAME

The status request Open message is so structured:

*1*1*12## Reply status light 12, light ON.

DIMENSION REQUEST OPEN FRAME

The OPEN message to require the dimension is so structured:

The reply message is generically sent even in the Events connections.

DIMENSION WRITING OPEN FRAME

The OPEN message to write the dimension is so structured:

FUNCTIONS DEVELOPED THANKS TO OPEN WEB NET

Version Date Author

Updating description: FIRST VERSION

4.4. Open Network: ........................................................................................................ 19

The two leds indicates to the user the actions:

3) Serial communication parameters:

The parameters used to communicate with the CP2102 are:

4) Open Web Net remind:

WHERE = (TX) ADDR (SYS)

-You can discover it after send PRODUCT INFORMATION OpenWebNet command

Command / Status Message

OPEN WEB NET WHO = 0

1.1. Scenario 1 to 32:

Scenario = [1 to 32] allow to enable the

ACK if the command is sent to the dongle.

1.2. Start recording X scenario:

ACK if the command is sent to the dongle.

1.3. End recording X scenario:

ACK if the command is sent to the dongle.

1.4. Delete all scenarios:

1.5. Delete X scenario:

1.6. Unavailable scenarios Central Unit:

1.7. Memory full of Scenario Central Unit:

OPEN WEB NET WHO = 1

2.1. Light OFF

ACK if the command is sent to the dongle.

2.2. Light off at X speed:

2.3. Light on:

2.4. Light on at X speed:

11*12## Reply status light 12, light ON.

#1## ACK if the dongle is in a ZigBee network.

#1## ACK if the dongle is in a ZigBee network.

#1## ACK if the dongle is in a ZigBee network.

#1## ACK if the dongle is in a ZigBee network.

#1## ACK if the dongle is in a ZigBee network.

#1## ACK if the dongle is in a ZigBee network.

#1## ACK if the dongle is in a ZigBee network.

Client Server #13where#917value1 Value1: is the major version.

Client Server #13where#926value Value-N : is the who which are