xxter enOcean ANE01 User manual

1
xxter enOcean manual
xxter b.v.
Elandsgracht 73 I
1016 TR Amsterdam
The Netherlands
Tel. [phone]
www.xxter.com
[e-mail]
This manual is a general instruction for connecting the antenna and configuring xxter with
enOcean. If required enOcean can also be combined with a KNX installation.
To make use of enOcean, please note the following prerequisites:
1) An xxter module type HC01C or newer
2) An xxter enOcean ANE01 antenna
3) The latest configuration tool (version 1.8.3 or newer)
4) The latest firmware (version 1.8.3 or newer)
Connecting the antenna
The enOcean ANE01 antenna has a serial connector and a power split cable, which both
need to be connected. Please follow the following instructions:
1) Make sure the xxter is disconnected from the power.
2) Attach the serial connector of the ANE01 to the serial (RS232) port of your xxter.
3) Attach the power split cable to the xxter unit.
4) Attach the power adapter of the xxter unit to the split cable.
Now the power adaptor can be reconnected to the power socket and the xxter unit as well as
the enOcean antenna will have power.

2
Using the repeater function
The ANE01 has three options for repeating:
1) No repeating (default), both dip-switches to OFF (number side)
2) Repeat only original telegrams (level 1), only dipswitch 1 to ON
3) Repeat original and 1-time repeated telegrams: both dipswitches to ON
A disconnect and reconnect of the power of the ANE01 is required before changes to these
dipswitches will take effect.
Verifying the enOcean antenna
When the beta firmware is installed, the enOcean function will automatically be activated.
This option can be turned on or off on the basic settings page of the xxter unit. On the status
page you can see whether xxter has properly recognised and connected to the antenna.
Short introduction to the enOcean telegram format
With the new configuration tool you can configure enOcean components. Every enOcean
device (a switch, actor, dimmer, sensor, etc.) can either transmit or receive telegrams or do
both.
Every telegram has a sender address and a channel number, which is used to identify every
device. In xxter you can create an alias for every device, for easier recognition.
Every enOcean telegram also has a specific type and function, which depends on the used
hardware of the device. xxter now supports a great number of different types of telegrams
and more will added in the near future. In case you want to apply a certain type of hardware
that is not yet supported, please inform us and we will add it to the configuration options.
For xxter it is important to know which types of telegrams are supported by which device.
Newer devices will automatically supply the type of the telegram, when the device is teached
in. Older devices however do not support this feature and the type needs to be selected
manually.
To look up the telegram type, a list of all supported brands and devices are included in
addendum 2. In case you cannot find the device you want to configure, please let us know so
we can further expand this list.

3
Every enOcean telegram has three separate parts: the first, main, part (RORG) and the parts
FUNC and TYPE. The last two are only used for specific telegram types.
The first part (RORG) has three options:
RPS – switching command, used by switches (also called F6 / 05)
BS1 – 1bit telegrams, for single binary inputs (not often used, also called D5 / 06)
BS4 – 4byte telegrams, for all other types of telegrams (also called A5 / 07)
The FUNC and TYPE parts are only used for BS4 telegrams. In other cases these parts will
be left blank.
FUNC is used to indicate the telegram function, for instance: Gas sensor (09)
TYPE is used to indicate the subtype of the telegram, for instance: monoxide alarm (01)
BS4 telegrams can also contain multiple values, for instance not only the CO2concentration,
but also a temperature value. This all depends on the type of the telegram.
To recognise which value to use, xxter uses letters in addition to the telegram. Every letter
stands for another value in the telegram and can be found in addendum 1.
For instance a switch (RPS) can have one button A and another button B or a CO2sensor
(BS4 – 09 – 04) will have A as the CO2concentration, B as the temperature and C as the
humidity.
Using the xxter configuration tool
In the configuration tool, open a project or create a new one. Configure the IP address of the
xxter unit in the tool settings and connect to the xxter unit, using the button on the right hand
side of the toolbar (with the enOcean symbol). This will enable the configuration tool to
receive the enOcean teach telegrams from the xxter unit.
The configuration tool will automatically add every “teach telegram” it receives to the project.
The learned telegrams can be found on the fourth tab of the tool.
When a teach telegram contains the type, it will automatically be included. If this is not the
case, the type must be looked up in addendum 2 (only for BS4 telegrams) and selected
manually.

4
Added telegrams can be connected to actions, just as you would when using the ETS import.
Important: teached telegrams can only be received and not be transmitted. Therefor these
telegrams can only be connected to status groups of actions.
By default the letter A will be connected, since every type of telegram will always have at
least one value. The letter can be changed manually if needed.
TIP: to quickly connect telegrams to actions, select the proper status field before
sending/receiving the teach telegram. This will automatically connect the received telegram
to this action. When a switch is pressed the specific switch telegram will be sent and also the
right letter will be automatically added, for instance letter B for the second switch button.

5
Sending telegrams
To control other units with xxter, xxter will also need to send telegrams that can be teached in
by other devices.
To do this, create a new telegram in the configuration tool on the fourth tab (the enOcean
tab) by clicking the right mouse button somewhere on the sheet.
A sending telegram will always have a manufacturer ID of 0. You will need to manually select
a channel for every sending telegram, which needs to be unique. To send telegrams there
are 128 channels available, in a range from 0 to 127. When a switch telegram (RPS) is used,
four buttons van be used per channel. Therefore there are a total of 128 4byte telegrams,
512 switch commands or a combination of the two possible. This restriction only applies to
the sending telegrams.
When sending 4byte telegrams, the appropriate type and function also need to be
configured.
To teach a device the new sending telegram, activate “learning mode” on the receiving
device and send a learning telegram from the xxter configuration tool by clicking the “Send
learning telegram” button.
Of course sending telegrams can also be connected to actions using the configuration tool.

6
In the list shown on the lower right of the configuration tool you can see whether a telegram
is sending or receiving by the + and - symbols shown in front of the name. A sending
telegram is shown with a + and a receiving telegram is shown with a - symbol.
Combining KNX and enOcean
It is also possible to combine enOcean and KNX using xxter. In the actions table in the tool,
there is column titled bridge.
When you want to send a telegram or value from the KNX-bus to an enOcean device add a
separate action. In this action fill in the enOcean telegram as the sending group address and
teach in the telegram at the required enOcean device. In the status field fill in the KNX group
address and in the bridge column select the option “on change” or “always”.
When selecting the bridge option “on change” an enOcean telegram will only be sent when
the value changes. When selecting the option “always” any received telegram from the status
groups will trigger the sending of a telegram.
Sending an enOcean telegram on the KNX-bus works exactly the same, but the other way
around. Teach in the enOcean telegram in the status field and fill in the proper KNX group as
a sending group. The bridge column works the same.

!!"#$%#&'(#)&%"#*#+$),%"-.#/
01&( 2-.# 3#""#$ 4#/($5."56&
! "#$%#&'()&#*+#,+-&+
. "#$%#&'()&#*+#,+-&*&',/#*012*(-*2*34
5 "#$%#&'()&#*6347
! "#$%#&'()&#*+#,+-&*&',/#*082*(-*.2*34
5 "#$%#&'()&#*6347
8 "#$%#&'()&#*+#,+-&*&',/#*0!2*(-*!2*34
5 "#$%#&'()&#*6347
1 "#$%#&'()&#*+#,+-&*&',/#*0.2*(-*82*34
5 "#$%#&'()&#*6347
9 "#$%#&'()&#*+#,+-&*&',/#*2*(-*12*34
5 "#$%#&'()&#*6347
: "#$%#&'()&#*+#,+-&*&',/#*.2*(-*92*34
5 "#$%#&'()&#*6347
; "#$%#&'()&#*+#,+-&*&',/#*!2*(-*:2*34
5 "#$%#&'()&#*6347
< "#$%#&'()&#*+#,+-&*&',/#*82*(-*;2*34
5 "#$%#&'()&#*6347
= "#$%#&'()&#*+#,+-&*&',/#*12*(-*<2*34
5 "#$%#&'()&#*6347
5 "#$%#&'()&#*+#,+-&*&',/#*92*(-*=2*34
5 "#$%#&'()&#*6347
> "#$%#&'()&#*+#,+-&*&',/#*:2*(-*.22*34
5 "#$%#&'()&#*6347
.2 "#$%#&'()&#*+#,+-&*&',/#*0:2*(-*!2*34
5 "#$%#&'()&#*6347
.. "#$%#&'()&#*+#,+-&*&',/#*092*(-*82*34
5 "#$%#&'()&#*6347
.! "#$%#&'()&#*+#,+-&*&',/#*012*(-*12*34
5 "#$%#&'()&#*6347
.8 "#$%#&'()&#*+#,+-&*&',/#*082*(-*92*34
5 "#$%#&'()&#*6347
.1 "#$%#&'()&#*+#,+-&*&',/#*0!2*(-*:2*34
5 "#$%#&'()&#*6347
.9 "#$%#&'()&#*+#,+-&*&',/#*0.2*(-*;2*34
5 "#$%#&'()&#*6347
.: "#$%#&'()&#*+#,+-&*&',/#*2*(-*<2*34
5 "#$%#&'()&#*6347
.; "#$%#&'()&#*+#,+-&*&',/#*.2*(-*=2*34
5 "#$%#&'()&#*6347
.< "#$%#&'()&#*+#,+-&*&',/#*!2*(-*.22*34
5 "#$%#&'()&#*6347
.= "#$%#&'()&#*+#,+-&*&',/#*82*(-*..2*34
5 "#$%#&'()&#*6347

!!"#$%#&'(#)&%"#*#+$),%"-.#/
01&( 2-.# 3#""#$ 4#/($5."56&
.5 "#$%#&'()&#*+#,+-&*&',/#*12*(-*.!2*34
5 "#$%#&'()&#*6347
.> "#$%#&'()&#*+#,+-&*&',/#*92*(-*.82*34
5 "#$%#&'()&#*6347
!2 "#$%#&'()&#*+#,+-&*&',/#*0.2*(-*1.?!*34
5 "#$%#&'()&#*6347
82 "#$%#&'()&#*+#,+-&*&',/#*012*(-*:!?8*34
5 "#$%#&'()&#*6347
1 "#$%#&'()&#*',@*A)$B@B(C*+#,+-&
. "#$%#&'()&#*&',/#*2*(-*12*34*',@*A)$B@B(C*20.22D
5 E)$B@B(C*6D7
> "#$%#&'()&#*6347
! "#$%#&'()&#*&',/#*0!2*(-*:2*34*',@*A)$B@B(C*20.22D
5 E)$B@B(C*6D7
> "#$%#&'()&#*6347
: FB/A(*+#,+-&
. G',/#*822HI*(-*:2?222HI
5 JHH)$B,'(B-,*6H)I7
> K)%%HC*L-H('/#*6M7
! G',/#*2HI*(-*.2!2HI
5 JHH)$B,'(B-,*6H)I7
> K)%%HC*L-H('/#*6M7
; NOO)%',OC*+#,+-&
. NOO)%',OC
5 NOO)%',OC*62P.7
< FB/A(Q*(#$%#&'()&#*',@*-OO)%',OC*+#,+-&
. G',/#*2HI*(-*9.2HIQ*2*(-*9.*34*',@*-OO)%',OC
5 "#$%#&'()&#*6347
> JHH)$B,'(B-,*6H)I7
4 RJG*62P.7
S >)((-,*62P.7
TK)%%HC*%-U#&*6M7
! G',/#*2HI*(-*.2!2HIQ*2*(-*9.*34*',@*-OO)%',OC
5 "#$%#&'()&#*6347
> JHH)$B,'(B-,*6H)I7
4 RJG*62P.7
S >)((-,*62P.7
TK)%%HC*%-U#&*6M7

!!"#$%#&'(#)&%"#*#+$),%"-.#/
01&( 2-.# 3#""#$ 4#/($5."56&
8 G',/#*2HI*(-*.982HIQ*2*(-*9.*34*',@*-OO)%',OC
5 "#$%#&'()&#*6347
> JHH)$B,'(B-,*6H)I7
4 RJG*62P.7
S >)((-,*62P.7
TK)%%HC*%-U#&*6M7
= V'+*+#,+-&
.4N*+#,+-&
5 4-,O#,(&'(B-,*6%%$7
> 4-,O#,(&'(B-,*6%%$7
4 "#$%#&'()&#*6347
14N!*+#,+-&
5 4-,O#,(&'(B-,*6%%$7
> "#$%#&'()&#*6347
4 E)$B@B(C*6D7
.2 G--$*-%#&'(B,/*%',#H
W-(*C#(*'L'BH'XH#
..
W-(*C#(*'L'BH'XH#
.! 5)(-$'(#@*$#(#&*&#'@B,/
2 4-),(#&
5 4-),(#&*L'H)#
> 4)&&#,(*L'H)#*6.P+7
4 Y#'+)&#$#,(*OA',,#H*62??.97
. TH#O(&BOB(C
5 4)$)H'(BL#*L'H)#*6Z[A7
> 4)&&#,(*L'H)#*6[7
4 "'&B\\*B,\-*62??.97
! V'+
5 4)$)H'(BL#*L'H)#*6$87
> 4)&&#,(*L'H)#*6HP+7
4 "'&B\\*B,\-*62??.97
8 ['(#&
5 4)$)H'(BL#*L'H)#*6$87
> 4)&&#,(*L'H)#*6HP+7
4 "'&B\\*B,\-*62??.97

!!"#$%#&'(#)&%"#*#+$),%"-.#/
01&( 2-.# 3#""#$ 4#/($5."56&
.8 T,LB&-,$#,('H*5%%HBO'(B-,+
. [#'(A#&*+('(B-,
5 S'U,*+#,+-&*62??===*H)I7
> "#$%#&'()&#*6012??<2*]47
4[B,@*+%##@*62??;2*$P+7
S WB/A(*P*@'C*62P.7
T S&C*P*&'B,*62P.7
! K),**B,(#,+B(C*6,-&(A#&,*A#$B7
5 J,(#,+B(C*U#+(*6.??.92*ZH)I7
> J,(#,+B(C*+-)(A*6.??.92*ZH)I7
4 J,(#,+B(C*#'+(*6.??.92*ZH)I7
8 S'(#*#IOA',/#
5 S'C*6.??8.7
> Y-,(A*6.??.!7
4 ^#'&*6!222??!2==7
S G"4*P*VRK*-&*#_?*62P.7
1 "B$#*',@*@'(#*#IOA',/#
5 [##Z@'C*6.`Y-,@'C??;`K),@'C7
> E-)&*62??!87
4 YB,)(#*62??9=7
SK#O-,@*62??9=7
T!1*-&*.!*A-)&+*62P.7
a 5Y*-&*RY*62P.7
V G"4*P*VRK*-&*#_?*62P.7
9 SB&#O(B-,*#IOA',/#
5 TH#L'(B-,*60=2*(-*=2Q*2`A-&Bb-,7
> 5bB$)(*62*(-*89=Q*2`,-&(A7
: V#-/&'%ABO'H*%-+B(B-,*#IOA',/#
5 F'(B()@#*60=2*0*=2]7
> F-,/B()@#*60.<2*0*.<2]7
!2 EM54*4-$%-,#,(+
W-(*C#(*'L'BH'XH#
82 SB/B('H*B,%)(
. KB,/H#*B,%)(Q*X'((?*$-,B(-&
5 4-,('O(*-%#,POH-+#@*62P.7
> >'((?*FN[*P*Nc*62P.7
!KB,/H#*B,%)(
5 4-,('O(*OH-+#@P-%#,*62P.7

!!"#$%#&'(#)&%"#*#+$),%"-.#/
01&( 2-.# 3#""#$ 4#/($5."56&
8; T,#&/C*$','/#$#,(
W-(*C#(*'L'BH'XH#
8< 4#,(&'H*O-$$',@
< RE4*/'(#U'C
5 "B$#*\-&*@#H'C*',@*H-OZ*62?.*??*:998*+7
>d,H-OZ*P*H-OZ*62P.7
4 S)&'(B-,*P*@#H'C*62P.7
4 785"(9%'00:';%<=:>?
@ 45,%A)*1#%<=BB>==C?
a G'$%B,/*(B$#*62??!99*+7
V 5X+-H)(#*@B$*L'H)#*P*&#H'(BL#*62P.7
E K(-&#*L'H)#*C#+P,-*62P.7
J KUB(OA*NaaPNW*62P.7
D7#".65&"%/95E"%<F>GBH%BB%>GBI%J?
J7#"%&#8%K)/5(%/#".65&"%<=BBL>BG%MN?
3 N6&"$6*%A)$5)K*#%6A#$$5O#%<=BB>==C?
Y 4-,(&-HH#&*$-@#*62`')(-Q*.`A#'(B,/Q*!`O--HB,/Q*8`-\\7
W 4-,(&-HH#&*+('(#*62`')(-Q*.`-L#&&B@#7
N T,#&/C*A-H@*-\\*62`,-&$'HQ*.`#,#&/C*A-H@*-\\*P*@#U*%-B,(7
R NOO)%',OC*62`-OO)%B#@Q*.`),-OO)%B#@*P*!`+(',@XC7
P 0)&/.##O%<=BBQ%6$%GLL?%GLLR)1"6
"A#+#*(#H#/&'$+*'&#*-,HC*+#,@*UB(A*(A#*X-H@*OA'&'O(#&
. 4#,(&'H*+UB(OA*L'&B',(*\-&*TH('Z-*',@*N%)+*V&##,,#(
5 >H-OZ*+UB(OAB,/*+('(#*6.`XH-OZ#@Q*2*`*,-(*XH-OZ#@7
> KUB(OAB,/*+('(#*6.*`*-,Q*2*`-\\7
! 4#,(&'H*@B$*L'H)#*L'&B',(*\-&*TH('Z-*',@*N%)+*V&##,,#(
5 SB$*+%##@*62`+%##@*-\*@B$$#&Q*.`\'+(Q*!99`+H-U7
S 45,%A)*1#%<=F>==C?

xxter%&%enocean%device%list
Brand Article Telegram Brand Article Telegram
Eltako !"#$%& #'()*)+,)*)+- Eltako !".'%+)*)/&+0 12')*)#
!#$33 #'()*)+,)*)+- status !!1%-)*)/&+0 12')*)"4#
%&,,/3&+ #'()*)+,)*)+- !56%-72)*)/&+0 12')*)"4#
!8#$%& #'()*)+,)*)+- !$6%-)*)/&+0 12')*)#
!"!9%+ #'()*)+()*)+/ !$6%-4,)*)/(0 12')*)#
!8!9%&"2 #'()*)+()*)+/ !:'%-72)*)/&+0 12')*)"4#
!"$%+ #'()*)+%)*)+- !:5%-)*)/&+0 12')*)#
!"$%& #'()*)+%)*)+- !'#%-72)*)/&+0 12')*)#
!8$%& #'()*)+%)*)+- !'1%-72)*)/&+0 12')*)#
!"':%+ 12')*)# !'1%-)*)/&+0 12')*)#
!':-/ 12')*)# !'1%-4,)*)/(0 12')*)#
!':%- 12')*)# !'1%-0")*)-+" 12')*)#
!';-/. 12')*)# !'1<+=)*)-%" 12')*)#
!';33. 12')*)# !97%-72))*)/&+0 12')*)#
!6> 12')*)" !?@%-72)*)/&+0 12')*)#
!6! 12')*)" !;.%-72)*)/&+0 12')*)#
!1= 12')*)" #'()*)&,)*)+,
!''-/ #'()*)-/)*)+- A+B+/)CDEFGH
!9()A-)IJKILF 12')*)# !;.%-727)*)/&+0 12')*)#
!9(!)A-)IJKILF 12')*)# #'()*)&,)*)+,
!933)A-)IJKILF 12')*)# A+B+/)CDEFGH
!9()A/)IJKILKMF 12')*)"4#
!9(!)A/)IJKILKMF 12')*)"4# Eltako !?>%-)*)/&+0 #'()*)&,)*)+-
!933)A/)IJKILKMF 12')*)"4# central !'#-/ MJI)LNOOP)QKI
!9!33 #'()*)+/)*)+3 !'#%- MJI)LNOOP)QKI
!96 #'- !'1-/*(B*-/0).> #'()*)&,)*)+-
!9133. #'()*)-+)*)+& !;.-/727 #'()*)&,)*)+-
!9133$ #'()*)-+)*)+& #'()*)&,)*)+/
!='%- #'()*)-&)*)+- !;.%-72 #'()*)&,)*)+-
#'()*)-+)*)+& #'()*)&,)*)+/
!=5-/ #'()*)-/)*)+- !;.%-727 #'()*)&,)*)+-
!=5%- #'()*)-/)*)+- #'()*)&,)*)+/
!5' 12')*)"
R9$H1)#1"7.')"7.)9S2H')>R:87T)'RR7

!""#$%&'(")*
Use$enOcean$with$character$combination$for$switch$commands$with$xxter
+,!,-+ +./01/2
3%#4#$"'4 56""7( 8'#(9(:);<)="#"6= +'(>);<)? +'(>);<)@
! ? ?);<)A4'== A4'==);6""7()? A4'==);6""7()B
5 B ?);<)A4'== A4'==);6""7()* A4'==);6""7()C
3 * ?);<)A4'== A4'==);6""7()D A4'==);6""7()E
0 C ?);<)A4'== A4'==);6""7()F A4'==);6""7()G
. ? @);<)A4'== A4'==);6""7()? 4'H'#=');6""7()?
I B @);<)A4'== A4'==);6""7()B 4'H'#=');6""7()B
2 * @);<)A4'== A4'==);6""7()* 4'H'#=');6""7()*
J C @);<)A4'== A4'==);6""7()C 4'H'#=');6""7()C
1?KBK*)L)C @);<)4'H'#=' A4'==);6""7()D 4'H'#=');6""7()D
M?KBK*)L)C ?);<)4'H'#=' A4'==);6""7()E 4'H'#=');6""7()E
N A4'==);6""7()F 4'H'#=');6""7()F
O A4'==);6""7()G 4'H'#=');6""7()G
8 ? "7::H');<)A4'==
/ B "7::H');<)A4'==
P * "7::H');<)A4'==
Q C "7::H');<)A4'==
R D "7::H');<)A4'==
S E "7::H');<)A4'==
+ F "7::H');<)A4'==
, G "7::H');<)A4'==
Enocean$5>$xxter
.T#&AH')=U9"$%=)U9"%)"U7)V6AW>7U(X;6""7(=
Y? Y*
YB) YC
J7U)"7)A47:4#&)Y?)Z)P/K)YB)Z)PII
,<A' /#&' +'(>9(: +"#"6=
+U9"$% +? ./P[@W!K)./P[@WI
J7U)"7)A47:4#&)"7)"U7)"7::H')\6($"97(=[
,<A' /#&' +'(>9(: +"#"6=
+U9"$% +? ./P[@W8
+U9"$% +B ./P[@W/
P\)']'()#=)#)A6H=);6""7(
,<A' /#&' +'(>9(: +"#"6=
+U9"$% +? ./P[@W!K)./P[@W1
xxter$5>$enOcean
^%9$%)$7&;9(#"97()"7)6=')9=)>'A'(>9(:)7()"%')#$"6#"74
87=")#$"6#"74=)6=')"U7)>9\\'4'(");6""7(=)\74)=U9"$%9(:K)?)\74)P/K)?)\74)PII
,<A' /#&' +'(>9(: +"#"6=
+U9"$% +? ./P[@W!
WINDOWS$HANDLES$(only$status)
3%#4#$"'4 +"#"6=
- O7$Y'>)V>7U(U#4>X)Z)?
_ J#H\)7A'()V6AU#4>X)Z)?
^ PA'()V%749`7("#HX)Z)?