EN

Operation and installation manual

KNX ENO 626 secure
(Art. # 5269)
Bidirectional Gateway with 8+8 channels between EnOcean and KNX Bus

o Environmental sensors
o Digital inputs
 Link from KNX to EnOcean actuator
(channels 1-8)
o Emulation of EnOcean switch module
for
 Switching
 Dimming
KNX ENO 626 secure
 Shutter
Application o Emulation of EnOcean window contact
The KNX ENO 626 is a bidirectional gateway between EnOcean o Bidirectional EnOcean switching, dim-
radio devices and the KNX bus. It transfers commands and ming and shutter actuator
measured values of EnOcean wireless sensors to the KNX bus,
for example, to control KNX actuators. EnOcean wireless actua- o Bidirectional EnOcean HVAC drives for
tors can also be controlled via KNX. valves

The EnOcean communication is based on the EnOcean Equip-  Control / logic (channels 1-16)
ment Profiles (EEP). This profile is usually specified in the data o Timer
sheet of the EnOcean device.
 Switch-on delay
For the controlling of EnOcean actuators corresponding EEPs
are emulated. This means that the gateway sends radio tele-  Switch-off delay
grams like a push button or a window contact.
o Control
Encrypted communication on EnOcean is supported, encryption
can be enabled for each sensor or actuator channel separately.  2-point regulator (byte and
float)
Further information to the EnOcean Equipment Profiles can be
found on http://www.enocean-alliance.org.  Continuous regulator (float)

In addition the gateway supports logical and control functions  Heat requisition
and includes radio-repeater functionality. The KNX ENO 626 is  Lighting control
divided in 16 channels: channels 1-8 can be used for gateway
functions as well as for control/logic functions, channels 9-16 o Logical functions
only have control/logic functionality:
 Gates (e.g. AND, OR, XOR)
 Inverter
 Link from EnOcean sensor to KNX (channels 1-8)
 Flip-flop (Toggle)
o Switch functions
o Special
 Switching
 Valuator
 Dimming
 Trigger
 Shutter
 Watchdog
 Scene
 Filter
 Valuator
The configuration of the device and the channels is performed
o Window handles using the ETS software via the KNX Bus. To configure the wire-
o Window contacts less components the keys and the LEDS in the device are used.

o Access card switches

o Press switches 1. Installation and connection
o Temperature sensors The device can be flush-mounted, the housing has the appropri-
ate housing size for mounting in a 60 mm flush-mounted socket
o Humidity sensors
When choosing the installation location the RF range of
o Light sensors EnOcean devices to be associated with the gateway has to be
o Presence sensors considered. Shielding objects (e.g. metal cabinets) or interfering
transmitters (e.g. computers, electronic transformers, ballasts)
o Gas sensors near the gateway should be avoided.
o Room control panels More information on range planning and RF interference can be
found in the data sheets of the devices and on
o Automated meter devices www.enocean.com.

©2021 WEINZIERL ENGINEERING GmbH Page 1/20

The connection to the KNX bus is made with a bus connector. up briefly white without repeater function, if repeater function is
The correct polarity of the terminal referred to the printing inside activated, the LED lights up briefly blue.
the unit has to be considered.
When learning/deleting Enocean devices, the LED indicates the
The KNX ENO 626 features the following controls and displays:
ETS configuration of the currently selected channel:

❶ Switch P KNX Prog

LED Status Meaning
❷ LED P KNX Prog
LED lights green ETS configuration „Link from EnOcean Sensor to KNX“
❸ KNX bus connector LED lights red ETS configuration „Link from KNX to EnOcean actuator“
❹ LED S State LED lights blue ETS configuration „Control/Logic“
❺ LEDs Channels 1-8
❻ Switch A Exit/Del During an ETS download, this LED flashes green.
❼ Switch B Activ/Add
During normal operation, the channel LEDs 1-8 indicate whether
a received EnOcean or KNX telegram is linked to one or more
This device is powered only by the KNX bus. gateway channels. If so, the LED of the linked channel will light
up briefly green.

The device is not working without KNX bus power.

E. Linking to EnOcean devices

Before linking to EnOcean devices, the functions have to be

A. KNX Programming mode programmed for each channel with the ETS. Per channel typical-
ly only one EnOcean device can be linked. For switches, window
The KNX programming mode is activated/deactivated by press-
handles and window contacts up to four links per channel are
ing the KNX programming button P ❶ possible.
When the programming mode is active, the programming LED If the EnOcean device sends encrypted telegrams “Channel
❷ lights red, this LED blinks red, when the application is not encryption” has to be enabled for the selected channel.
running, e.g. after a failed ETS download.
For unidirectional actuator channels any number, for bidirectional
A gateway ex-factory has the default individual address only one RF actuator can be learnt. Encrypted control of actuator
15.15.255. There are no group addresses and no connections to channels is supported and can be enabled by parameter in the
RF sensors and actuators programmed. selected channel.
Encrypted communication in EnOcean uses one continuous
B. Button functions independent counter (Rolling Code, RLC) in the transmitter and
receiver, which is synchronized in the teach-in in both devices.
The configuration during the teach-in process can be done with If the meter reading of learned transmitter and receiver has a
the buttons A ❻ and B ❼. difference greater than 60 then no tele-grams are accepted by
this transmitter. In order to synchronize the RLC again, it is
Key press A long (Del.): Delete the stored device from the sufficient if the sender sends the gateway a learning telegram
current channel and the gateway does not have to be put into the learning mode.
Key press A short (Exit): Leave channel/linking mode It should be noted that the RLC in the gateway cannot be count-
ed further if its voltage supply is interrupted. If a learned RPS
Key press B long (Add.): Start linking mode button is pressed more than 30 times in this state, the button and
gateway must be synchronized again by sending a learning
Key press B short (Active): Activate or change the channels 1- telegram.
32

Key press P (KNX Prog. Mode): Activate “KNX Prog. mode”

F. Linking mode for RF sensors
A long key press is detected when a button is pressed for longer
than 1 second. The configuration during the teach-in process can be done with
the buttons A ❻ and B ❼.

C. LEDs for state and channels 1-8 If the device is in normal mode, the push button B activates the
channel mode by short key press and changes to the next chan-
The LEDs state ❹ and channel 1-8 ❺ are used for commis- nel, the currently active channel is indicated by one of the LEDs
sioning and system diagnostics. ❺. If the channel is configured as a sensor channel via the
ETS, the status LED also lights up green.
The main menu shows the device name, the operation mode By long key press on button B on the desired channel, the learn-
(e.g. “Running”) and the KNX individual address. ing mode is activated, and the corresponding channel LED starts
to flash green if the channel still has free connections. A RF
D. Defined operation modes sensor can now be connected to the channel, for this purpose
the sensor type set in the ETS must match the profile of the
If the flashing programming LED ❺ indicates a problem during sensor to be connected. A connection is created by pressing the
the last ETS download the ETS application should be reloaded. learn-button of the sensor. Window handles and switches must
The device start is signaled by a short green flashing of all LEDs be operated for teach-in because they do not have a separate
learn button.
❹ and ❺
To avoid that other transmitting devices are stored by accidental
In normal operation, the status LED is used as a display for a
activation during the programming phase, devices can be pro-
received EnOcean telegram, for every telegram, this LED lights
grammed only after 3-times activation. For this purpose in the
general parameters ‘Link switches/handles (RPS) after 3 tel.’

©2021 WEINZIERL ENGINEERING GmbH Page 2/20

must be selected. The sensor has to send three telegrams within The learning mode must first be activated at the actuator. When
10 seconds to be linked. emulating an RPS switch, the learning mode in the gateway is
activated by long press of button B at the desired channel. In the
The link mode is terminated by a short press of the left key A, as
RPS function, the channel LEDs indicate the pressure point of
well as automatically after 5 minutes without operation.
the emulated switch by flashing, 2 LEDs are always combined:
Quick guide linking mode for RF-sensors
Channel LEDs Pressure point
1. Button B short press to select the desired channel.
1-2 Rocker A top
2. Button B long press to activate the learning mode 5-6 Rocker A bottom
("Wait for ENO ..."). 3-4 Rocker B top
7-8 Rocker B bottom
3. Activate the learning mode in the RF-sensor.
The desired pressure point can be selected by short press on
4. The sensor is now programmed. button B; by long button press, up to 3 EnOcean telegrams are
sent to teach the actuator.

G. Deleting links for RF sensors - 1BS input contact (D5-00-01)

Links with RF sensors can be deleted in several ways. With a The learning mode must first be activated at the actuator. When
long press on button A the delete mode is activated for the cur- emulating a 1BS contact, the EnOcean telegram for teach-in is
rent channel. The sensor can now be deleted from the visible sent by long press of button B long at the desired channel. This
channel by pressing the learn button on the RF sensor. It is also is indicated by brief flickering of the channel LED.
possible to delete all assignments of the selected channel by - VLD actuators (D2-01-XX)
pressing B ("All"). It is not required to operate the RF sensors.
- VLD actuators (D2-05-XX)
Learned sensors can be erased by several ways. A long press
on button A activates the delete mode for the current channel, The learning mode must first be activated at the actuator. When
the corresponding channel LED starts flashing green if the chan- these bi-directional actuators are integrated, the learning tele-
nel is linked to RF sensors. The sensor can now be deleted from gram is triggered by long press of button B of the desired chan-
the visible channel by pressing the learn button on the RF sen- nel, and the triggering of the telegram is indicated by a brief
sor. It is also possible to delete all learned sensors of the select- flickering of the corresponding channel LED.
ed channel by short press on button B with activated delete
Attention: Some actuators on the market trigger learning from
mode. For this, the sensors do not have to be actuated. After
their side, this is not supported by the gateway.
successful deletion, the channel LED switches back to steady
light. - HVAC actuator for valve (A5-20-01)

By programming the application program via the ETS all pro- - HVAC actuator for valve (A5-20-04)
grammed sensors of all channels will be deleted, when the
The teach-in of these bi-directional devices is initiated by the
"Delete all links after download" function in the general parame-
actuator, i.e. the teach-in process takes place as in the case of a
ter is enabled.
sensor channel: The channel LED of the selected channel be-
If the function of a channel has been changed, programming the gins to flicker with a long press on button B, then a learning
parameters with the ETS deletes the links of the modified chan- telegram must be triggered at the actuator. If the teach-in was
nel. successful, the channel LED switches back to permanent light.

The link mode is terminated by a short press of the left key A, as The learning mode is terminated by a short operation of the left
well as automatically after 5 minutes without operation. button A as well as automatically after 5 minutes without opera-
tion.
Quick guide linking mode for RF sensors:
The activation of the learning mode of the actuator can be found
1. Button B short press to select the desired channel.
in the data sheet of the respective actuator.
2. Button A long press to activate the delete mode
(Channel LED flashes red).
3. Activate the learning mode at the desired RF sensor to I. Deleting links for RF actuators
delete.
The selection of the channel when deleting connections to actua-
Alternatively: tors is the same as for teach-in of sensors. Here, in addition to
the channel LED of the selected channel, the status LED is red if
Button B long press to delete all taught-in RF sensors from the
the channel is set to an actuator function. The teach-in is de-
selected channel.
pending on the emulated sensor type selected.

- RPS switch (F6-02-01 / D2-03-00)

H. Linking mode for RF actuators
- 1BS input contact (D5-00-01))
The selection of the channel during the teach-in of actuators is
the same as for teach-in of sensors. Here, in addition to the The links of these unidirectional actuator channels are stored in
channel LED of the selected channel, the status LED is red if the the respective actuators. These can be deleted locally for many
channel is set to an actuator function. The teach-in is depending types on the device without the gateway. In some actuators it is
on the emulated sensor type selected: also possible to delete individual links by learning telegrams. In
this case, the deletion of actuators works the same way as the
- RPS switch (F6-02-01 / D2-03-00)
teach-in.

- VLD actuators (D2-01-XX)

- VLD actuators (D2-05-XX)

©2021 WEINZIERL ENGINEERING GmbH Page 3/20

The learning mode must first be activated at the actuator. When M. Repeater function
links to these bi-directional actuators are deleted, the learning
telegram is triggered by long press of button A of the desired The repeater function is used for extend distances between
channel, and the triggering of the telegram is indicated by a brief sensors and actuators. The KNX ENO 626 is a level-1 radio
flickering of the corresponding channel. repeater. This means, that only telegrams that come directly
from a transmitter will be repeated. Telegrams sent by other
Attention: Some actuators on the market trigger deleting from
repeaters are not repeated again.
their side, this is not supported by the gateway.

- HVAC actuator for valve (A5-20-01)

- HVAC actuator for valve (A5-20-04)

3. Reset to factory device settings
It is possible to reset the device to its factory settings:
Here also for these bi-directional devices, the teach-in procedure
is initiated by the actuator: The channel LED of the selected  Disconnect the KNX Bus connector ❸ from device
channel begins to flicker with a long press on button A, after that  Press button A ❻ and keep it pressed down
a learning telegram can be triggered at the actuator or the chan-  Reconnect the KNX Bus connector ❸ of device
nel can be erased without a learning telegram from the actuator
 Keep button A ❻ pressed until state LED ❹ lights red
by short press on button B. If the deletion was successful, the
channel LED changes to continuous light.
If button A is released, a short flashing of all LEDs ❷,❹ and
❺ visualizes the successful reset of the device to factory de-
2. Normal operation fault settings.
J. RF sensors

When in normal operation mode, each received EnOcean tele-

4. ETS database
gram will be compared to see if it has been assigned to a chan- The ETS database (for ETS 4.2 and 5) can be downloaded from
nel. If so, the corresponding channel LED flashes. Depending on the product website of the KNX ENO 626 (www.weinzierl.de) or
the configured function there will be one or more telegrams sent from the ETS online catalogue.
on the bus. The gateway only sends telegrams to the KNX bus
when a corresponding EnOcean telegram has been received.
The transmission frequency on the bus is determined by the
EnOcean sensor.

If a received EnOcean telegram is not assigned to a channel,

only the status LED flashes white briefly.

K. RF actuators

If a channel is set to switch or input contact and the gateway

receives a telegram from the KNX bus, which is assigned to this
actuator channel, a RF telegram will be sent for this channel. If a
channel is set to HVAC actuator, the channel waits for a request
of the actuator, then he sends the actual values to KNX and
EnOcean.

For the other actuator channels, the communication is bidirec-

tional: Each telegram from KNX or EnOcean triggers a telegram
on the other medium. Each time a KNX telegram is received on
an object of a gateway channel, the appropriate channel LED
lights up briefly.

L. Internal links

For some use cases it is necessary to link KNX data points

(communication objects) of different channels. Thus, values of
sensor channels can be connected with inputs from control
channels. But also wireless sensors can be connected with RF The following pages and parameters are visible in the ETS.
actuators.
Data points can be linked in the ETS by assigning the same
group address to an output and an input object. In this case the
values will also be sent to the bus.
In contrast, the internal links are foreseen to link communication
objects directly without sending tele-grams via the KNX bus. For
this purpose no group addresses have to be assigned in the
ETS. Internal links can be created in the parameter dialog of the
ETS. In the receiving channel, the communication object number
of the output channel can be selected. The value of the selected
object is copied internally into the receiving object and imple-
ments the associated function.

©2021 WEINZIERL ENGINEERING GmbH Page 4/20

N. Device description If the EnOcean sensor transmits encrypted telegrams, this must
be activated by the parameter "Channel encryption".
The first page shows general information about the device.

Sensor type “RPS Switch”

The type of device to be used can be selected via the parameter
switch type. It is possible to learn devices with a single switch,
two or four rockers.
The channel encryption can also be activated in the parameter, it
should be noted that at the moment only the PTM 215 of the
switch modules of EnOcean is able to communicate encrypted.
Switching the PTM 215 to encrypted communication:
1. Simultaneously press both contact O
tabs from either channel A or B
1.
A or B
2. By activating the energy bow, trigger
the learning telegram and activate the I
2.

Common encryption

 Device name (30 Characters) Switching the PTM 215 to unencrypted communication:

An arbitrary name can be assigned for the KNX ENO 1. Simultaneously press all contact tabs
O
626. The device name should be meaningful, e.g. „Liv- from channel A and B
ing Room. 2. By activating the energy bow, trigger A 1. B

 Delete all links after download the learning telegram and deactivate
the encryption I
2.
If this parameter is active, all linked EnOcean devices
in all sensor channels are erased after ETS download.
Switch type “1 Push button (F6-01-01)”
 Link switches/handles (RPS) after 3 tel.
This parameter selects whether an EnOcean switch or
handle has to be operated 1x or 3x times for teach-in.
 RF-Repeater
With this parameter the repeater function is switched
on or off.

The parameters "KNX function" define which KNX telegrams are

O. Gateway functions triggered when the push button is pressed and released:
For each of the first 8 channels one of the following function can Switching (On on pressed)
be selected
Group Object Type KNX Size Direction
 Inactive Switch Sensor channel - Switching on 1.001 1 Bit To KNX

 Link from EnOcean sensor to KNX

Switching (Off on pressed)
 Link from KNX to EnOcean actuator
Group Object Type KNX Size Direction
 Control/Logic Switch Sensor channel - Switching off 1.001 1 Bit To KNX

Channels 9-16 support only Control/Logic functionality.

Switching Toggle
If a channel function is enabled, a name of up to 15 characters
can be assigned to the channel by parameter „Displayed text“. Group Object Type KNX Size Direction
This name should be clear and meaningful; it is shown in the Switch Sensor channel - Switching 1.001 1 Bit To KNX
toggle
ETS in the object names of the channel.
The 1st channel will be described below, the functioning of the
other 15 channels is according to the 1st. Dimming
On short button press, a switching telegram is sent via object
switching. On long button press, a relative dimming is sent over
Gateway functions on channel type “Link from EnOcean the entire dimming range to object dimming. When releasing
sensor to KNX” after long button press, a dimming stop telegram is sent via
object dimming. Both objects are linked, each switching on or
In this operating mode EnOcean sensors can be integrated into increase of brightness is followed by a switching off or decreas-
a KNX system. ing of brightness on next button press.
When pressing the learn button most EnOcean sensors send Group Object Type KNX Size Direction
their EEP to prevent linking of the sensor to an incompatible Switch Sensor channel - Switching on/off 1.001 1 Bit To KNX
gateway channel. The compatible profile is written in the pa- Switch Sensor channel - Dimming 3.007 4 Bit To KNX
brighter/darker
rameter sensor type in the ETS database. If an attempt is made
to teach a sensor with an EEP that does not match the channel,
the gateway does not establish the connection. If during the ETS
configuration, the EEP of a channel is changed, the next down-
load will delete learned sensors on the channel.
During operation, the gateway forwards the data sent on
EnOcean of a linked sensor via one or more objects on KNX.

©2021 WEINZIERL ENGINEERING GmbH Page 5/20

Shutter
On each long button press the shutter moves up or down alter- Group Object Type KNX Size Direction
Switch Sensor channel - Switching on/off 1.001 1 Bit To KNX
natively. If the shutter is moving, it is stopped on short button
Switch Sensor channel - Dimming 3.007 4 Bit To KNX
press, if the shutter is stopped, every short button press sends a brighter/darker
step command in up direction.
Group Object Type KNX Size Direction Shutter - up
Switch Sensor channel - Shutter 1.008 1 Bit To KNX
Group Object Type KNX Size Direction
up/down
Switch Sensor channel - Shutter up 1.008 1 Bit To KNX
Switch Sensor channel - Shutter 1.007 1 Bit To KNX
step/stop Switch Sensor channel - Shutter 1.007 1 Bit To KNX
step/stop

Scene Shutter - down

Group Object Type KNX Size Direction
Short button press triggers a scene command. Furthermore, it is
Switch Sensor channel - Shutter down 1.008 1 Bit To KNX
selected by parameter whether a command to learn a scene is Switch Sensor channel - Shutter 1.007 1 Bit To KNX
sent on long button press. step/stop

Group Object Type KNX Size Direction

Switch Sensor channel - Scene 18.001 1 Byte To KNX Shutter - (one-key control)
On each long button press the shutter moves up or down alter-
natively. If the shutter is moving, it is stopped on short button
Byte value
press, if the shutter is stopped, every short button press sends a
Group Object Type KNX Size Direction step command in up direction.
Switch Sensor channel - Byte value 5.xxx 1 Byte To KNX
Group Object Type KNX Size Direction
Switch Sensor channel - Shutter 1.008 1 Bit To KNX
up/down
Switch type “2 Rockers (F6-02-01)” Switch Sensor channel - Shutter 1.007 1 Bit To KNX
step/stop

Scene
Short button press triggers a scene command. Furthermore, it is
selected by parameter whether a command to learn a scene is
sent on long button press.
Group Object Type KNX Size Direction
Switch Sensor channel - Scene 18.001 1 Byte To KNX

Byte value
Group Object Type KNX Size Direction
Switch Sensor channel - Byte value 5.xxx 1 Byte To KNX
Each pressure point of the 2 rockers can be individually as-
signed to KNX functions by the parameters “KNX function Switch Switch type “4 Rockers (F6-03-01)”
pressure point”:
Disabled
Switching - on
Group Object Type KNX Size Direction
Switch Sensor channel - Switching on 1.001 1 Bit To KNX

Switching - off
Group Object Type KNX Size Direction
Switch Sensor channel - Switching off 1.001 1 Bit To KNX

Switching - toggle
The configuration of a 4-fold rocker is analogous to the 2-fold
Group Object Type KNX Size Direction
rocker (F6-02-01), however, it must be noted that for the com-
Switch Sensor channel - Switching on/off 1.001 1 Bit To KNX
plete integration, 2 channels must be used in the gateway, one
channel for rockers A-B, another channel for rockers C-D. When
Dimming - brighter
using a 4-fold rocker, channel encryption is not supported.
Group Object Type KNX Size Direction
Switch Sensor channel - Switching on 1.001 1 Bit To KNX Sensor type “Special switches and contacts”
Switch Sensor channel - Dimming 3.007 4 Bit To KNX
brighter
The parameter switch/contact type can be used to select which
type of device is to be used, the following profiles are available:
Dimming - darker
Group Object Type KNX Size Direction
 1BS Window contact (D5-00-01)
Switch Sensor channel - Switching off 1.001 1 Bit To KNX
Switch Sensor channel - Dimming darker 3.007 4 Bit To KNX
 4BS Window and door contact (A5-14-xx)
 RPS Window handle (F6-10-00)
Dimming - (one-key control)
 VLD multi sensor window handle (D2-06-01)
On short button press, a switching telegram is sent via object
switching. On long button press, a relative dimming is sent over  RPS Key card switch (F6-04-01)
the entire dimming range to object dimming. When releasing
after long button press, a dimming stop telegram is sent via  RPS Pressure switch (F6-04-01)
object dimming. Both objects are linked, each switching on or  RPS Pressure switch group (F6-04-01)
increase of brightness is followed by a switching off or decreas-
ing of brightness on next button press.  RPS Liquid leakage sensor (F6-05-01)

©2021 WEINZIERL ENGINEERING GmbH Page 6/20

  VLD Push Button (D2-03-0A, as of ETS database A5-14-0A open/closed/tilt/alarm
V1.1)
Group Object Type KNX Size Direction
Special Sensor channel - Window group 1.002 1 Bit To KNX
 Generic (RORG-FUNC-TYPE, as of ETS database open state 1
V1.1) Special Sensor channel - Window group 1.002 1 Bit To KNX
open state 2
Switch/contact type “1BS Window contact (D5-00-01)” Special Sensor channel - Alarm 1.005 1 Bit To KNX
Special Sensor channel - Battery low 1.002 1 Bit To KNX

Switch/contact type “RPS Window handle (F6-10-00)”

For window handle sensors, three states can be detected: win-
dow open, tilted or closed. When turning the handle in a position
the corresponding state will be mapped to two communication
objects and transmitted. Up to four handles can be taught to a
channel.
For window contacts, up to 4 contacts can be taught into one
channel. The gateway detects a common state of all contacts The gateway calculates a common state of all handles assigned
learned in the channel and sends the value "closed" only when to the channels. Following some examples from the state table:
all windows are closed. Window 1 Window 2 Window 3 Window 4 Common
state
Group Object Type KNX Size Direction Open Open Open Open Open
Special Sensor channel - Window group 1.0019 1 Bit To KNX Open Tilted Open Open Open
open Open Closed Tilted Closed Open
Closed Closed Closed Tilted Tilted
Closed Closed Closed Closed Closed
Switch/contact type “4BS Window and door contact
(A5-14-xx)”
For window handles the following communication objects are
available:
Group Object Type KNX Size Direction
Special Sensor channel - Window group 1.002 1 Bit To KNX
open state 1
Special Sensor channel - Window group 1.002 1 Bit To KNX
open state 2

The following telegrams are sent via these objects in the various
states of the window group:
Window closed Window tilted Window open
For this device type, up to 4 contacts can be taught into one Window group Off On On
channel. The gateway detects a common state of all contacts open state 1
Window group Off Off On
learned in the channel and sends the value "closed" only when open state 2
all windows are closed.
The position of the handle is dependent on the installation condi-
The following devices of this profile family are supported: tion. This is described in the datasheet of the window handle.
A5-14-01 open/closed The handle is mounted correctly if two Off-telegrams via both
data points are sent when the window is closed.
Group Object Type KNX Size Direction
Special Sensor channel - Window group 1.0019 1 Bit To KNX
open Switch/contact type “VLD multi sensor window handle
Special Sensor channel - Battery low 1.002 1 Bit To KNX (D2-06-01)“

A5-14-03 open/closed/alarm
Group Object Type KNX Size Direction
Special Sensor channel - Window group 1.0019 1 Bit To KNX
open
Special Sensor channel - Alarm 1.005 1 Bit To KNX
Special Sensor channel - Battery low 1.002 1 Bit To KNX

A5-14-07 open/closed/locked
Group Object Type KNX Size Direction
Special Sensor channel - Door group 1.002 1 Bit To KNX
open
Special Sensor channel - Door group 1.002 1 Bit To KNX
locked
Special Sensor channel - Battery low 1.002 1 Bit To KNX On selecting this devices type following objects are available:
Group Object Type KNX Size Direction
A5-14-08 open/closed/locked/alarm Special Sensor channel - Window open 1.002 1 Bit To KNX
state 1
Group Object Type KNX Size Direction
Special Sensor channel - Window open 1.002 1 Bit To KNX
Special Sensor channel - Door group 1.002 1 Bit To KNX state 2
open
Special Sensor channel - Temperature 9.001 2 Byte To KNX
Special Sensor channel - Door group 1.002 1 Bit To KNX
Special Sensor channel - Humidity 9.007 2 Byte To KNX
locked
Special Sensor channel - Alarm 1.005 1 Bit To KNX
Special Sensor channel - Alarm 1.005 1 Bit To KNX
Special Sensor channel - Battery low 1.002 1 Bit To KNX
Special Sensor channel - Battery low 1.002 1 Bit To KNX

A5-14-09 open/closed/tilt Depending on parameter “KNX function buttons” the 2 buttons

on the device can execute the following functions:
Group Object Type KNX Size Direction
Special Sensor channel - Window group 1.002 1 Bit To KNX
open state 1
Special Sensor channel - Window group 1.002 1 Bit To KNX
open state 2
Special Sensor channel - Battery low 1.002 1 Bit To KNX

©2021 WEINZIERL ENGINEERING GmbH Page 7/20

Switching  Switching On
Group Object Type KNX Size Direction Group Object Type KNX Size Direction
Special Sensor channel - Switching 1.001 1 Bit To KNX Special Sensor channel - Switching on 1.001 1 Bit To KNX
on/off  Switching Off

Dimming Group Object Type KNX Size Direction

Special Sensor channel - Switching off 1.001 1 Bit To KNX
Group Object Type KNX Size Direction  Switching Toggle
Special Sensor channel - Switching 1.001 1 Bit To KNX
on/off Group Object Type KNX Size Direction
Special Sensor channel - Dimming 3.007 4 Bit To KNX Special Sensor channel - Switching 1.001 1 Bit To KNX
brighter/darker toggle
Each time the key is pressed, the last value sent is inverted and
Shutter sent (toggle function).
Group Object Type KNX Size Direction  Dimming
Special Sensor channel - Shutter 1.008 1 Bit To KNX
up/down Group Object Type KNX Size Direction
Special Sensor channel - Shutter 1.007 1 Bit To KNX Special Sensor channel - Switching 1.001 1 Bit To KNX
step/stop on/off
Special Sensor channel - Dimming 3.007 4 Bit To KNX
brighter/darker
Scene
Each time the button is pressed, the last dimming direction sent
Group Object Type KNX Size Direction by both objects is evaluated: If the last value sent was a switch
Special Sensor channel - Scene 18.001 1 Byte To KNX
on or an increase in brightness, the next value to be sent is a
switch off or a decrease in brightness. A short keystroke sends
Switch/contact type “RPS Key card switch (F6-04-01)” telegrams for switching on/off, a long keystroke sends telegrams
On selecting this devices type following object is available for dimming brighter/darker.

Group Object Type KNX Size Direction  Shutter

Special Sensor channel - Key card 1.002 1 Bit To KNX
inserted Group Object Type KNX Size Direction
Special Sensor channel - Shutter 1.008 1 Bit To KNX
up/down
Switch/contact type “RPS Pressure switch (F6-04-01)” Special Sensor channel - Shutter 1.007 1 Bit To KNX
step/stop
On selecting this devices type following object is available If the button is pressed long, the last value sent is inverted and
Group Object Type KNX Size Direction sent via the "Shutter up/down" object. If the button is pressed
Special Sensor channel - Pressed 1.002 1 Bit To KNX short, either a current move command is interrupted via the
"Shutter step/stop" object or the blind moves one step in the
Switch/contact type “RPS Pressure switch group opposite direction to the last move command via the "Shutter
(F6-04-01)” up/down" object.
On selecting this devices type following object is available  Szene
Group Object Type KNX Size Direction Group Object Type KNX Size Direction
Special Sensor channel - Pressed 1.002 1 Bit To KNX Special Sensor channel - Scene 18.001 1 Byte To KNX
In this operating mode of the pressure switch it is possible to When this function is selected, a parameter for selecting the sent
determine via parameter which number of switches must be scene appears. In addition, it can be set via parameters whether
activated in order to send an ON telegram a command for saving the set scene is to be sent via a long
keystroke.
Switch/contact type “RPS Liquid leakage sensor
(F6-05-01)”  Byte value
The following object is available with this device type: Group Object Type KNX Size Direction
Special Sensor channel - Byte value 5.* 1 Byte To KNX
Group Object Type KNX Size Direction When selecting this function, a parameter for setting the value to
Special Sensor channel - Alarm 1.005 1 Bit To KNX send appears.
The following KNX functions can be selected for double button
Switch/contact type „VLD Push Button (D2-03-0A)“ presses:
As of database V1.1
 Switching On
Group Object Type KNX Size Direction
Special Sensor channel - Switching on 1.001 1 Bit To KNX
(double press)
 Switching Off
Group Object Type KNX Size Direction
Special Sensor channel - Switching off 1.001 1 Bit To KNX
(double press)
 Switching Toggle
Group Object Type KNX Size Direction
Special Sensor channel - Switching 1.001 1 Bit To KNX
toggle (double press)
This profile supports push buttons with short/long and double
Each time the key is pressed double, the last value sent is in-
key press. The following object is available for monitoring the
verted and sent (toggle function).
battery status:
 Scene
Group Object Type KNX Size Direction
Special Sensor channel - Battery low 1.002 1 Bit To KNX Group Object Type KNX Size Direction
Special Sensor channel - Scene (double 18.001 1 Byte To KNX
The battery status is transmitted each time the button is pressed. press)

The following KNX functions can be selected for short/long key When this function is selected, a parameter for selecting the sent
presses: scene appears.

©2021 WEINZIERL ENGINEERING GmbH Page 8/20

  Byte value These two parameters are used to set the range of the
value in the EnOcean telegram. This range must be
Group Object Type KNX Size Direction
Special Sensor channel - Byte value 5.* 1 Byte To KNX taken from the technical description of the EnOcean
(double press) device.
When selecting this function, a parameter for setting the value to - Scale to KNX min
send appears. - Scale to KNX max
These two parameters are used to set the scaling of
Switch/contact type „Generic (RORG-FUNC-TYPE)“ the value from the EnOcean telegram to the value in
As of ETS database V1.1 the KNX telegram.

Sensor type “4BS Temperature sensors”

Various temperature ranges are supported for the temperature

sensors. The temperature value is mapped to a 2 byte floating-
point value.
The following profiles are supported:
 A5-02-01: -40 .. 0°C
 A5-02-02: -30 .. +10°C
This function can be used to integrate data from EnOcean sen-
sors with EEPs not supported by the gateway, or to evaluate  A5-02-03: -20 .. +20°C
data from sensors with supported EEPs that deviate from the
 A5-02-04: -10 .. +30°C
specification.
The EEP of the device to be evaluated must be known and sent  A5-02-05: 0 .. +40°C
by the EnOcean device during the teach-in process. For setting
the EPP the parameters RORG, FUNC and TYPE are available,  A5-02-06: +10 .. +50°C
e.g. if the device sends the EEP A5-08-01 during teach-in, the  A5-02-07: +20 .. +60°C
following must be set:
- RORG: A5  A5-02-08: +30 .. +70°C
- FUNC: 08
- TYPE: 01  A5-02-09: +40 .. +80°C
From the received EnOcean telegram, either individual bits can  A5-02-0A: +50 .. +90°C
be evaluated or contiguous bits can be combined as bit fields up
to a length of 1 byte and interpreted as a value.  A5-02-0B: +60 .. +100°C
The following object types are available for sending on KNX:
- 1 bit - value  A5-02-10: -60 .. +20°C
Group Object Type KNX Size Direction
Special Sensor channel - Generic 1 bit - 1.* 1 Bit To KNX
 A5-02-11: -50 .. +30°C
value
If 1 bit - value is selected, a parameter also appears for setting  A5-02-12: -40 .. +40°C
whether the bit from the EnOcean telegram is to be sent inverted  A5-02-13: -30 .. +50°C
or not inverted to KNX.
- 1 byte - Integer value / Percent  A5-02-14: -20 .. +60°C
Group Object Type KNX Size Direction
Special Sensor channel - Generic 1 Byte 5.* 1 Byte To KNX  A5-02-15: -10 .. +70°C
- Integer value / Percent
- 2 byte - Integer value  A5-02-16: 0 .. +80°C
Group Object Type KNX Size Direction
Special Sensor channel - Generic 2 Byte 7.* 2 Byte To KNX  A5-02-17: +10 .. +90°C
- Integer value
- 2 byte - Float value  A5-02-18: +20 .. +100°C
Group Object Type KNX Size Direction
Special Sensor channel - Generic 2 Byte 9.* 2 Byte To KNX
 A5-02-19: +30 .. +110°C
- Float value
 A5-02-1A: +40 .. +120°C
- Raw - Integer value
Group Object Type KNX Size Direction
 A5-02-1B: +50 .. +130°C
Special Sensor channel - Generic 1 Byte 5.* 1 Byte To KNX
- Integer value (raw)
 A5-02-20: -10 .. 41,2°C
To select one or more bits to be evaluated, there are the follow-  A5-02-30: -40 .. 62,3°C
ing 2 parameters:
- Bit offset
Specifies the offset from the MSB of the first received For all temperature sensors the following communication object
data byte at which the evaluation is to start. is available:
- Count of bits (only for group object type 1 byte or 2
bytes) Group Object Type KNX Size Direction
Specifies the number of bits that are to be combined Temp Sensor channel - Temperature 9.001 2 Byte To KNX
from the set offset and interpreted as a value.
To convert the value from EnOcean telegram to a value in a KNX
group telegram, the following parameters are available:
- Scale from EnOcean min
- Scale from EnOcean max

©2021 WEINZIERL ENGINEERING GmbH Page 9/20

Sensor type “4BS Temperature and humidity sensors“ Sensor type “4BS Light/Temperature/ Occupancy sensor“

The following profiles can be selected: Following profiles are supported here:
 A5-04-01: 0 .. 40°C, 0 .. 100%  A5-08-01: 0 .. 510lx, 0 .. 51°C
 A5-04-02:-20 .. 60°C, 0 .. 100%  A5-08-02: 0 .. 1020lx, 0 .. 51°C
 A5-04-03:-20 .. 60°C, 0 .. 100%  A5-08-03: 0 .. 1530lx, -30 .. 50°C
(As of ETS database V1.1)
Light intensity and temperature are each mapped to a communi-
The measured values are sent via two different communication cation object with a 2 bytes float value. Presence and motion
objects: detectors send 1-bit values:
Group Object Type KNX Size Direction Group Object Type KNX Size Direction
Hum Sensor channel - Humidity 9.007 2 Byte To KNX LTO Sensor channel - Illuminance 9.004 2 Byte To KNX
Hum Sensor channel - Temperature 9.001 2 Byte To KNX LTO Sensor channel - Temperature 9.001 2 Byte To KNX
LTO Sensor channel - Occupancy 1.018 1 Bit To KNX
LTO Sensor channel - Motion detector 1.001 1 Bit To KNX
Sensor type “4BS Light sensors“

Sensor type “4BS Gas sensors“

The following profiles can be selected:

For all sensors, the gas concentration is available via object.
 A5-06-01: 300 .. 60000 lx Depending on the EPP of the sensor, further measured values
 A5-06-02: 0 .. 1020 lx can be sent to KNX:

The measuring of light intensity is done in lux (lx). The measured A5-09-01: CO sensor
value is available as a 2-byte float value: Group Object Type KNX Size Direction
Gas Sensor channel - Gas concentration 9.008 2 Byte To KNX
Group Object Type KNX Size Direction Gas Sensor channel - Temperature 9.001 2 Byte To KNX
Light Sensor channel - Illuminance 9.004 2 Byte To KNX

A5-09-04: CO2 sensor

Sensor type “4BS Occupancy sensor“ Group Object Type KNX Size Direction
Gas Sensor channel - Gas concentration 9.008 2 Byte To KNX
Gas Sensor channel - Temperature 9.001 2 Byte To KNX
Gas Sensor channel - Humidity 9.007 2 Byte To KNX

A5-09-05: VOC sensor

Group Object Type KNX Size Direction
Gas Sensor channel - Gas concentration 9.008 2 Byte To KNX

A5-09-08: CO2 sensor

The following profiles are supported here:
Group Object Type KNX Size Direction
 A5-07-01: Occupancy Gas Sensor channel - Gas concentration 9.008 2 Byte To KNX

Occupancy is transmitted via following object: A5-09-09: CO2 sensor

Group Object Type KNX Size Direction
Group Object Type KNX Size Direction
Occ Sensor channel - Occupancy 1.018 1 Bit To KNX
Gas Sensor channel - Gas concentration 9.008 2 Byte To KNX
 A5-07-02: Occupancy (As of ETS database V1.1) Gas Sensor channel - Battery low 1.002 1 Bit To KNX

Occupancy is transmitted via following object:

Group Object Type KNX Size Direction Sensor type “4BS Room operating panels“
Occ Sensor channel - Occupancy 1.018 1 Bit To KNX
 A5-07-03: Occupancy + Light (As of ETS database
V1.1)
The occupancy and light intensity are sent via the following
objects:
Group Object Type KNX Size Direction
Occ Sensor channel - Occupancy 1.018 1 Bit To KNX
Occ Sensor channel - Illuminance 9.004 2 Byte To KNX

©2021 WEINZIERL ENGINEERING GmbH Page 10/20

A variety of room control panels can be used with the gateway, A5-10-0B: Temperature/Contact
depending on the configuration level and EPP of the device,
Group Object Type KNX Size Direction
various objects are displayed. Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Contact 1.019 1 Bit To KNX
If a profile supports temperature set point, the limit values that
are sent to KNX at the left and right stop of the set point adjuster
A5-10-0C: Temperature/Occupancy
can be determined via parameters.
Group Object Type KNX Size Direction
If a change of the fan stages is available in the profile, the per- Room Sensor channel - Temperature 9.001 2 Byte To KNX
centage values can be set with 3 parameters, which are sent Room Sensor channel - Occupancy 1.018 1 Bit To KNX
when switching to the respective fan stage.
A5-10-0D: Temperature/Day-Night
A5-10-01: Temperature/Set point/Fan/Occupancy
Group Object Type KNX Size Direction
Group Object Type KNX Size Direction Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Fan speed 5.001 1 Byte To KNX Room Sensor channel - Night 1.002 1 Bit To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX A5-10-10: Temperature/Humidity/Set point/Occupancy
Room Sensor channel - Occupancy 1.018 1 Bit To KNX
Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX
A5-10-02: Temperature/Set point/Fan/Day-Night temperature
Room Sensor channel - Humidity 9.007 2 Byte To KNX
Group Object Type KNX Size Direction Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Fan speed 5.001 1 Byte To KNX Room Sensor channel - Occupancy 1.018 1 Bit To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX A5-10-11: Temperature/Humidity/Set point/Day-Night
Room Sensor channel - Night 1.002 1 Bit To KNX
Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX
A5-10-03: Temperature/Set point temperature
Room Sensor channel - Humidity 9.007 2 Byte To KNX
Group Object Type KNX Size Direction Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX Room Sensor channel - Night 1.002 1 Bit To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
A5-10-12: Temperature/Humidity/Set point
A5-10-04: Temperature/Set point/Fan Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX
Group Object Type KNX Size Direction temperature
Room Sensor channel - Fan speed 5.001 1 Byte To KNX Room Sensor channel - Humidity 9.007 2 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX Room Sensor channel - Temperature 9.001 2 Byte To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
A5-10-13: Temperature/Humidity/Occupancy
A5-10-05: Temperature/Set point/Occupancy Group Object Type KNX Size Direction
Room Sensor channel - Humidity 9.007 2 Byte To KNX
Group Object Type KNX Size Direction Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX Room Sensor channel - Occupancy 1.018 1 Bit To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX A5-10-14: Temperature/Humidity/Day-Night
Group Object Type KNX Size Direction
A5-10-06: Temperature/Set point/Day-Night Room Sensor channel - Humidity 9.007 2 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Group Object Type KNX Size Direction Room Sensor channel - Night 1.002 1 Bit To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX Temperature/Set point
Room Sensor channel - Night 1.002 1 Bit To KNX
Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX
A5-10-07: Temperature/Fan temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX A5-10-16: Temperature/Set point/Occupancy
A5-10-08: Temperature/Fan/Occupancy Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX
Group Object Type KNX Size Direction
temperature
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX Room Sensor channel - Occupancy 1.018 1 Bit To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX

A5-10-17: Temperature/Occupancy
A5-10-09: Temperature/Fan/Day-Night
Group Object Type KNX Size Direction
Group Object Type KNX Size Direction
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Night 1.002 1 Bit To KNX
A5-10-18: Temperature/Set point/Fan/Occupancy/Illuminance
A5-10-0A: Temperature/Set point/Contact Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX temperature
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX
Room Sensor channel - Contact 1.019 1 Bit To KNX
Room Sensor channel - Fan automatic 1.001 1 Bit To KNX
Room Sensor channel - Illuminance 9.004 2 Byte To KNX

©2021 WEINZIERL ENGINEERING GmbH Page 11/20

A5-10-19: Temperature/Fan/Occupancy/Humidity A5-10-23: Temperature/Set point/Fan/Occupancy/Humidity
Group Object Type KNX Size Direction Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX Room Sensor channel - Set point 9.001 2 Byte To KNX
temperature temperature
Room Sensor channel - Humidity 9.007 2 Byte To KNX Room Sensor channel - Humidity 9.007 2 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX Room Sensor channel - Occupancy 1.018 1 Bit To KNX

A5-10-1A: Temperature/Set point/Fan/Occupancy

Sensor type “4BS Automated meter reading (AMR) “
Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX

A5-10-1B: Temperature/Fan/Occupancy/Illuminance
Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX
Room Sensor channel - Fan automatic 1.001 1 Bit To KNX
Room Sensor channel - Illuminance 9.004 2 Byte To KNX
A maximum of three counter channels are supported for each
channel. The counter channels that the EnOcean device trans-
A5-10-1C: Temperature/Set point mits must be known and set in the parameter. Two communica-
Light/Fan/Occupancy/Illuminance tion objects are available for each counter channel, one for the
Group Object Type KNX Size Direction current consumption and for the total consumption.
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
Room Sensor channel - Set point light 9.004 2 Byte To KNX The profiles have the following objects per channel:
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX A5-12-00: Counter
Room Sensor channel - Fan automatic 1.001 1 Bit To KNX
Room Sensor channel - Illuminance 9.004 2 Byte To KNX Group Object Type KNX Size Direction
AMR Sensor channel - Cumulative 12.001 4 Byte To KNX
counter [1]
A5-10-1D: Temperature/Set point Humidi- AMR Sensor channel - Counter rate [1/s] 12.001 4 Byte To KNX
ty/Fan/Occupancy/Humidity
Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX
A5-12-01: Electricity
Room Sensor channel - Set point 9.007 2 Byte To KNX Group Object Type KNX Size Direction
humidity
AMR Sensor channel - Cumulative 13.0013 4 Byte To KNX
Room Sensor channel - Humidity 9.007 2 Byte To KNX energy [kWh]
Room Sensor channel - Temperature 9.001 2 Byte To KNX AMR Sensor channel - Current energy 9.024 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX [kW]

A5-10-1E: Temperature/Fan/Occupancy/Illuminance
Group Object Type KNX Size Direction
A5-12-02: Gas
Room Sensor channel - Fan speed 5.001 1 Byte To KNX Group Object Type KNX Size Direction
Room Sensor channel - Temperature 9.001 2 Byte To KNX AMR Sensor channel - Cumulative gas 14.0076 4 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX [m3]
Room Sensor channel - Fan automatic 1.001 1 Bit To KNX AMR Sensor channel - Current gas [l/h] 9.025 2 Byte To KNX
Room Sensor channel - Illuminance 9.004 2 Byte To KNX

A5-10-1F: Temperature/Set point/Fan/Occupancy A5-12-03: Water

Group Object Type KNX Size Direction Group Object Type KNX Size Direction
Room Sensor channel - Fan speed 5.001 1 Byte To KNX AMR Sensor channel - Cumulative water 14.0076 4 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX [m3]
temperature AMR Sensor channel - Current water 9.025 2 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX [l/h]
Room Sensor channel - Occupancy 1.018 1 Bit To KNX

A5-10-20: Temperature/Set point/Occupancy Sensor type “4BS Environmental application “

Group Object Type KNX Size Direction

Room Sensor channel - Set point 9.001 2 Byte To KNX
temperature
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX

A5-10-21: Temperature/Set point/Fan/Occupancy/Humidity

Group Object Type KNX Size Direction
Room Sensor channel - Set point 9.001 2 Byte To KNX The following environmental sensors can be used with the gate-
temperature
Room Sensor channel - Humidity 9.007 2 Byte To KNX
way:
Room Sensor channel - Temperature 9.001 2 Byte To KNX
Room Sensor channel - Occupancy 1.018 1 Bit To KNX
A5-13-01: Weather station
Group Object Type KNX Size Direction
A5-10-22: Temperature/Set point/Fan/Humidity Env.App. Sensor channel - Dawn 9.004 2 Byte To KNX
Env.App. Sensor channel - Outdoor 9.001 2 Byte To KNX
Group Object Type KNX Size Direction temperature
Room Sensor channel - Fan speed 5.001 1 Byte To KNX Env.App. Sensor channel - Wind speed 9.005 2 Byte To KNX
Room Sensor channel - Set point 9.001 2 Byte To KNX Env.App. Sensor channel - Night 1.002 1 Bit To KNX
temperature Env.App. Sensor channel - Rain 1.002 1 Bit To KNX
Room Sensor channel - Humidity 9.007 2 Byte To KNX
Room Sensor channel - Temperature 9.001 2 Byte To KNX

©2021 WEINZIERL ENGINEERING GmbH Page 12/20

A5-13-02: Sun intensity, North hemisphere same radio telegrams as an EnOcean push button for example.
Here, each channel uses its own sender ID.
Group Object Type KNX Size Direction
Env.App. Sensor channel - Sun West 9.004 2 Byte To KNX
In addition, bidirectional EnOcean actuators with the following
Env.App. Sensor channel - Sun South 9.004 2 Byte To KNX
Env.App. Sensor channel - Sun East 9.004 2 Byte To KNX EEP families are supported:
 D2-01-XX: Switching/dimming actuators
A5-13-03: Date
 D2-05-XX: Shutter actuators
Group Object Type KNX Size Direction
Env.App. Sensor channel - Date 11.001 3 Byte To KNX  A5-20-01 and A5-20-04: HVAC actuators for drives
The following actuator functions are available in the parameters:
A5-13-04: Time and Day
Group Object Type KNX Size Direction Emulated sensor type “RPS switch (F6-02-01 / D2-03-00)“
Env.App. Sensor channel - Time 10.001 3 Byte To KNX

A5-13-05: Direction
Group Object Type KNX Size Direction
Env.App. Sensor channel - Elevation 8.011 2 Byte To KNX
Env.App. Sensor channel - Azimuth 8.011 2 Byte To KNX

A5-13-06: Geographic position

Group Object Type KNX Size Direction
Env.App. Sensor channel - Latitude 14.007 4 Byte To KNX
Env.App. Sensor channel - Longitude 14.007 4 Byte To KNX With this profile, a complete RPS switch with 2 rockers can be
emulated. Each rocker is separately configurable, the following
functions are available:
Sensor type “4BS Digital input“
Switching - Rocker top/bottom (on/off)
In both "Switching" operating modes, an object is available for
rocker A and B:
Group Object Type KNX Size Direction
RPS Actuator channel - Switch 1.001 1 Bit From KNX

In the case of a switching telegram via KNX, the telegram of the

EnOcean rocker is sent for "key pressed" and shortly thereafter
The following profiles can be used in this category: for "key released":
A5-30-01: Single input contact, Battery monitor KNX telegram EnOcean telegrams (RPS Data)
Rocker A Switch on 0x10 -> 0x00
Group Object Type KNX Size Direction
Rocker A Switch off 0x30 -> 0x00
Dig. Inp Sensor channel - Contact 1.009 1 Bit To KNX
Rocker B Switch on 0x50 -> 0x00
Dig. Inp Sensor channel - Battery low 1.002 1 Bit To KNX
Rocker B Switch off 0x70 -> 0x00

A5-30-02: Single input contact

Switching - Rocker top/bottom (off/on)
Group Object Type KNX Size Direction
Dig. Inp Sensor channel - Contact 1.009 1 Bit To KNX In the case of a switching telegram via KNX, the telegram of the
EnOcean rocker is sent for "key pressed" and shortly thereafter
A5-30-03: 4 Digital Inputs, Wake and Temperature for "key released":
Group Object Type KNX Size Direction KNX telegram EnOcean telegrams (RPS Data)
Dig. Inp Sensor channel - 1.009 1 Bit To KNX Rocker A Switch on 0x30 -> 0x00
Switch/Contact 1 Rocker A Switch off 0x10 -> 0x00
Dig. Inp Sensor channel - 1.009 1 Bit To KNX Rocker B Switch on 0x70 -> 0x00
Switch/Contact 2 Rocker B Switch off 0x50 -> 0x00
Dig. Inp Sensor channel - 1.009 1 Bit To KNX
Switch/Contact 3
Dimming - Rocker top/bottom (brighter/darker)
Dig. Inp Sensor channel - 1.009 1 Bit To KNX
Switch/Contact 4
Dig. Inp Sensor channel - 1.002 1 Bit To KNX
In both "Dimming" operating modes, two objects are available for
Switch/Contact Wake each rocker A and B:
Dig. Inp Sensor channel - Tempera- 9.001 2 Byte To KNX
ture Group Object Type KNX Size Direction
RPS Actuator channel - Switch 1.001 1 Bit From KNX
RPS Actuator channel - Dimming 3.007 4 Bit From KNX

A5-30-04: 3 Digital Inputs, 1 Byte (As of ETS database V1.1)

In the case of a switching telegram via KNX, the telegram of the
Group Object Type KNX Size Direction EnOcean rocker is sent for "key pressed" and shortly thereafter
Dig. Inp Sensor channel - Switch/Contact 1.009 1 Bit To KNX for "key released".
1
Dig. Inp Sensor channel - Switch/Contact 1.009 1 Bit To KNX KNX telegram EnOcean telegrams (RPS Data)
2 Rocker A Switch on 0x10 -> 0x00
Dig. Inp Sensor channel - Switch/Contact 1.009 1 Bit To KNX Rocker A Switch off 0x30 -> 0x00
3 Rocker B Switch on 0x50 -> 0x00
Dig. Inp Sensor channel - Byte value 5.* 1 Byte To KNX Rocker B Switch off 0x70 -> 0x00

In the case of a dimming telegram via KNX, the telegram of the

Gateway functions on channel type “Link from KNX to EnOcean EnOcean rocker is sent for "key pressed", "dimming stop" via
actuator” KNX triggers an EnOcean telegram for "key released".
To control EnOcean actuators the gateway can emulate the KNX telegram EnOcean telegrams (RPS Data)
corresponding sensor profiles. This means the device sends the Rocker A Dimming brighter 0x10,

©2021 WEINZIERL ENGINEERING GmbH Page 13/20

 Rocker A Dimming darker 0x30 Emulated sensor type “1BS input contact (D5-00-01)“
Rocker A Dimming stop 0x00
Rocker B Dimming brighter 0x50
Rocker B Dimming darker 0x70
Rocker B Dimming stop 0x00

Dimming - Rocker top/bottom (darker/brighter)

In the case of a switching telegram via KNX, the tele-gram of the
EnOcean rocker is sent for "key pressed" and shortly thereafter
for "key released". With this profile, a 1BS contact input is emulated, this profile is
KNX telegram EnOcean telegrams (RPS Data)
e.g. used by many simple EnOcean window contacts. One object
Rocker A Switch on 0x10 -> 0x00 is available:
Rocker A Switch off 0x30 -> 0x00
Group Object Type KNX Size Direction
Rocker B Switch on 0x50 -> 0x00
Contact Actuator channel - Window open 1.019 1 Bit From KNX
Rocker B Switch off 0x70 -> 0x00
KNX telegrams over this object are mapped to EnOcean as
In the case of a dimming telegram via KNX, the telegram of the follows:
EnOcean rocker is sent for "key pressed", "dimming stop" via KNX telegram EnOcean telegrams (1BS Data)
KNX triggers an EnOcean telegram for "key released". Window open 0x08
Window closed 0x09
KNX telegram EnOcean telegrams (RPS Data)
Rocker A Dimming brighter 0x10,
Rocker A Dimming darker 0x30 Emulated sensor type “VLD actuators (D2-01-XX)“
Rocker A Dimming stop 0x00
Rocker B Dimming brighter 0x50 With this profile, various bidirectional EnOcean switching or
Rocker B Dimming darker 0x70 dimming actuators of this EEP family can be used.
Rocker B Dimming stop 0x00

Shutter - Rocker top/bottom (up/down)

In both "Shutter" operating modes, two objects are available for
each rocker A and B:
Group Object Type KNX Size Direction
RPS Actuator channel – Up/Down 1.008 1 Bit From KNX
RPS Actuator channel – Step/Stop 1.007 1 Bit From KNX

For a move command via KNX the telegram of the EnOcean

rocker is sent for "key released" and shortly thereafter for "key
pressed":
KNX telegram EnOcean telegrams (RPS Data)
Rocker A Up 0x00 -> 0x30 Depending on the device type, the following objects are available
Rocker A Down 0x00 -> 0x10 for switching or dimming, some profiles also have an energy
Rocker B Up 0x00 -> 0x70
counter:
Rocker B Down 0x00 -> 0x50

A command for the adjustment of the slats via KNX releases 3

telegrams via EnOcean: "Key released," then "key pressed" and Group Object Type KNX Size Direction
VLD Actuator channel - Switching on/off 1.001 1 Bit From KNX
then again "key released": VLD Actuator channel - Dimming 3.007 4 Bit From KNX
brighter/darker
KNX telegram EnOcean telegrams (RPS Data)
VLD Actuator channel - Dimming 5.001 1 Byte From KNX
Rocker A Decrease 0x00 -> 0x30 -> 0x00 absolute
Rocker A Increase 0x00 -> 0x10 -> 0x00 VLD Actuator channel - Switching status 1.001 1 Bit To KNX
Rocker B Decrease 0x00 -> 0x70 -> 0x00 VLD Actuator channel - Dimming status 5.001 1 Byte To KNX
Rocker B Increase 0x00 -> 0x50 -> 0x00 VLD Actuator channel - Current energy 9.024 2 Byte To KNX
[kW]
Shutter - Rocker top/bottom (down/up) VLD Actuator channel - Cumulative 13.013 4 Byte To KNX
energy [kWh]
For a move command via KNX the telegram of the EnOcean
rocker is sent for "key released" and shortly thereafter for "key The channel used by the EnOcean device must be set in the
pressed": parameters, alternatively it can be selected that the gateway
KNX telegram EnOcean telegrams (RPS Data) channel is to control all channels of an EnOcean device. If the
Rocker A Up 0x00 -> 0x10 EnOcean device has several channels, a separate gateway
Rocker A Down 0x00 -> 0x30
Rocker B Up 0x00 -> 0x50 channel can be used for each.
Rocker B Down 0x00 -> 0x70

A command for the adjustment of the slats via KNX releases 3 Emulated sensor type “VLD actuators (D2-05-XX)“
telegrams via EnOcean: "Key released," then "key pressed" and
then again "key released": With this profile, bidirectional EnOcean shutter actuators of this
EEP family can be used.
KNX telegram EnOcean telegrams (RPS Data)
Rocker A Decrease 0x00 -> 0x10 -> 0x00
Rocker A Increase 0x00 -> 0x30 -> 0x00
Rocker B Decrease 0x00 -> 0x50 -> 0x00
Rocker B Increase 0x00 -> 0x70 -> 0x00

©2021 WEINZIERL ENGINEERING GmbH Page 14/20

 drives 10 minutes are fixed) and sends its battery status and
temperature at the same time, which are immediately forwarded
to KNX.
If while the waiting time for the request a new valve position was
received by KNX, the valve moves to the last received position
after the request.
In addition, the threshold for message "battery low" over KNX
can be set in the parameters of this profile.
Emulated sensor type “HVAC actuator for valve (A5-20-06)“
As of ETS database V1.1

The following objects are available for this device type:

Group Object Type KNX Size Direction
VLD Actuator channel - Shutter up/down 1.008 1 Bit From KNX
VLD Actuator channel - Shutter step/stop 1.007 1 Bit From KNX
VLD Actuator channel - Shutter position 5.001 1 Byte From KNX
VLD Actuator channel - Slats angle 5.001 1 Byte From KNX
VLD Actuator channel - Shutter position 5.001 1 Byte To KNX
status With this profile, various bi-directional EnOcean actuators can be
VLD Actuator channel - Slats angle 5.001 1 Byte To KNX
status used, the following objects are available:
Group Object Type KNX Size Direction
The channel used by the EnOcean device must be set in the HVAC Actuator channel - Valve 5.001 1 Byte From KNX
parameters, alternatively it can be selected that the gateway HVAC Actuator channel - Temperature 9.001 2 Byte To KNX
channel is to control all channels of an EnOcean device. If the HVAC Actuator channel - Battery low 1.002 1 Bit To KNX
EnOcean device has several channels, a separate gateway HVAC Actuator channel - Setpoint 9.002 2 Byte To KNX
(relative)
channel can be used for each. HVAC Actuator channel - Summer 1.001 1 Bit From KNX

In addition, it can be determined by parameter whether the

actuator is to approach positions directly or via a reference run, The drive cyclically asks the gateway for new data for set value
and the operating time of a step command can also be set. of the valve and summer mode (in many drives 10 minutes are
fixed) and sends its battery status, temperature and rel. setpoint
of temperature at the same time, which are immediately forward-
Emulated sensor type “HVAC actuator for valve (A5-20-01)“ ed to KNX.
If while the waiting time for the request a new valve position was
received by KNX, the valve moves to the last received position
after the request.

Gateway functions on channel type “Control/Logic“

With this profile, various bi-directional EnOcean actuators can be Several control / logic functions can be selected here. They
used, the following objects are available: include time, control, logic, valuator, trigger and watchdog func-
tions. These functions can be operated with a sensor or actuator
Group Object Type KNX Size Direction channel in the device or externally via KNX telegrams.
HVAC Actuator channel - Valve 5.001 1 Byte From KNX
HVAC Actuator channel - Temperature 9.001 2 Byte To KNX
HVAC Actuator channel - Battery low 1.002 1 Bit To KNX
HVAC Actuator channel - Summer 1.001 1 Bit From KNX
Control/Logic type “Timer“

The drive cyclically asks the gateway for new data for set value
of the valve and summer mode (in many drives 10 minutes are
fixed) and sends its battery status and temperature at the same
time, which are immediately forwarded to KNX.
If while the waiting time for the request a new valve position was
received by KNX, the valve moves to the last received position
after the request.

Emulated sensor type “HVAC actuator for valve (A5-20-04)“ Here it is possible to realize a switch-on or switch-off delay. The
time is set in seconds.
2 objects are available:
Group Object Type KNX Size Direction
Timer Regelung/Logik 1- Verzögerung 1.001 1 Bit From KNX
Eingang
Timer Regelung/Logik 1- Verzögerung 1.001 1 Bit To KNX
Ausgang

With this profile, various bi-directional EnOcean actuators can be

used, the following objects are available: Control/Logic type “Controller“
Group Object Type KNX Size Direction Various control algorithms are available:
HVAC Actuator channel - Valve 5.001 1 Byte From KNX
HVAC Actuator channel - Temperature 9.001 2 Byte To KNX  Two-point float
HVAC Actuator channel - Battery low 1.002 1 Bit To KNX
 Continuous float
The drive cyclically asks the gateway for new data (in many

©2021 WEINZIERL ENGINEERING GmbH Page 15/20

  Heat requisition This controller channel has the following objects:
 Lighting control Group Object Type KNX Size Direction
Control Control/Logic - Controller on/off 1.001 1 Bit From KNX
Control Control/Logic - Set point 9.001 2 Byte From KNX
Control Control/Logic - Temperature 9.001 2 Byte From KNX
Control algorithm “Two-point float“ actual value
Control Control/Logic - Night 1.002 1 Bit From KNX
Control Control/Logic - Presence 1.018 1 Bit From KNX
Control Control/Logic - Window open 1.019 1 Bit From KNX
Control Control/Logic - Control variable 5.001 1 Byte To KNX
The channel uses a PI controller, which operates with the con-
figuration via parameter "control speed" and a fixed cycle time of
5 minutes.
The controller channel is active on device start, without actual
value, the control variable is 50% for heating, 0% for cooling.
The controller can be deactivated via object "Controller on/off".
On deactivation, the control variable 0% is sent to close the
valve, and the channel will not react to any other input objects
during deactivation. If the controller has been deactivated, any
changes to the input objects are processed on activation, and
the output switches according to its configuration.
If the object "Open window" is received via object, the control
The controller channel has the following objects: variable 0% is sent on the next regular transmission, the control-
ler continues to work according to its configuration on "Window
Group Object Type KNX Size Direction
closed".
Control Control/Logic - Controller on/off 1.001 1 Bit From KNX
Control Control/Logic - Set point 9.001 2 Byte To KNX
Control Control/Logic - Value actual 9.001 2 Byte To KNX
When a 1 is received via the "Night" object, the controller goes
Control Control/Logic - Switch 1.001 1 Bit To KNX into the night lowering / raising, whereby the current Set point
value is reduced or increased by the value specified in the pa-
The channel is active on device start, and can be deactivated via rameter.
object "Controller on/off". When deactivated, the "Switch" object
With every received 1 via input "Presence", the delay time starts
sends an off telegram and the channel reacts to no changes via
again, the controller switches to the night lowering / raising at the
the "Actual/Set point" objects during deactivation. If the controller
end of the delay time.
has been deactivated, any changes to the input objects are
processed on activation, and the output switches according to its On device start, the Set point from parameters is active, the
configuration. parameter "Set point via group object" defines how a new Set
point via a telegram is treated:
The parameter "Operating mode" or "Output" can be used to
determine whether the output switches off or on when the actual  Relative: Set point from parameter +/- value from tele-
value is over Set point. If the actual value is below Set point with gram
a fixed hysteresis of -1K, the output is switched on or off.
 Absolute: Set point from parameter will be overwritten
On device start, the Set point from parameters is active, the by value from telegram
parameter "Set point via group object" defines how a new Set
point via a telegram is treated: In the operating mode "Heating", frost protection is also active: If
the actual temperature falls below +5°C, the "Control variable"
 Relative: Set point from parameter +/- value from tele- output sends 50% to protect the heating system, if the actual
gram temperature exceeds +6°C when frost protection is active, the
controller returns to normal operation.
 Absolute: Set point from parameter will be overwritten
by value from telegram

Control algorithm “Heat requisition“

Control algorithm “Continuous float“

This controller channel has the following objects:

Group Object Type Size Direction
KNX
Control Control/Logic - Control value 1 5.001 1 Byte From KNX
Control Control/Logic - Control value 2 5.001 1 Byte From KNX
Control Control/Logic - Control value 3 5.001 1 Byte From KNX
Control Control/Logic - Control value 4 5.001 1 Byte From KNX
Control Control/Logic - Control value 5 5.001 1 Byte From KNX
Control Control/Logic - Control value 6 5.001 1 Byte From KNX
Control Control/Logic - Demand 1.002 1 Bit From KNX
Control Control/Logic - Max value 5.001 1 Byte To KNX

©2021 WEINZIERL ENGINEERING GmbH Page 16/20

The maximum input value from the objects "Control value 1-6" is top, an off telegram and the value from parameter
sent to the "Max value" output, whereby the object "Demand" "Dim value low" are sent.
sends a 1 if the maximum value>0, a 0 if the maximum value is
0.  Automatic lighting control:
This state is activated on receiving presence.
Control algorithm “Lighting control“ The monitoring of the upper threshold is always active
in this state. Additionally in operating mode full-
automatic control, ON telegram and the value from pa-
rameter "Dim value high" are sent if the actual value
falls below the lower threshold.
Each time presence is received, the delay time pres-
ence is restarted. When this delay time expires, the
channel falls back to state standby. At this, an OFF
telegram and the value from parameter "Dim value
low" are sent.
 Manual override
This state is activated when a telegram is received on
object "light on/off", this telegram is forwarded to the
switching output, additionally "dim value low/high" is
sent. Each time light on/off is received, the delay time
of manual operation is restarted. While this delay time
is active, the processing of the light value is disabled.
When the delay time expires, the channel falls back in-
to standby.
Several functions can be implemented:
 Full-automatic control
Control/Logic type “Logic element“
A typical application for the fully automatic control is
the lighting of a corridor. Various logic functions can be used here:
The light is turned on in presence when the current  Gate
brightness value is below the threshold. By manual
operation, the light can be switched on or off for a spe-  Inverter
cific time.
 Toggle flip-flop
 Semi-automatic control
The semiautomatic mode allows the user or residents Logic type “Gate“
to turn the lights on and off manually. The semiauto-
matic only intervenes when the light was ‘forgotten’. A
typical application is an office room with several desks.
The light will not be switched on automatically. The
semi-automatic switches the light off when the current
brightness value is above the threshold or when for a
defined time presence is no longer detected.
 Simple control
The simple control only evaluates the brightness and
can be used, for example, for a store window. The light
turns on if it is too dark, and automatically turns off
when the brightness limit is reached.
Each gate channel has 2 gates with individually configurable
This controller channel has the following objects: type:
Group Object Type KNX Size Direction  AND gate
Control Control/Logic - Controller on/off 1.001 1 Bit From KNX
Control Control/Logic - Light on/off 1.001 1 Bit From KNX  OR gate
Control Control/Logic - Presence 1.018 1 Bit From KNX
Control Control/Logic - Light actual value 9.004 2 Byte From KNX  XOR gate
Control Control/Logic - Switch 1.001 1 Bit To KNX
Control Control/Logic - Dimm value 5.001 1 Byte To KNX  NAND gate

The lighting control has the following states:  NOR gate

 Deactivated:  XNOR gate

The channel can be deactivated via object "Controller Each gate of a channel has 2 input and 1 output object:
On/Off". When deactivated, the object "Switch" sends Group Object Type KNX Size Direction
off telegram and the object "Dimming value" sends the Logic Control/Logic - Gate input A1 1.002 1 Bit From KNX
value from the parameter "Dim value low". During de- Logic Control/Logic - Gate input A2 1.002 1 Bit From KNX
activation, the channel does not react to changes on Logic Control/Logic - Gate output A 1.002 1 Bit To KNX
Logic Control/Logic - Gate input B1 1.002 1 Bit From KNX
the input objects of presence and light value, but can Logic Control/Logic - Gate input B2 1.002 1 Bit From KNX
be manually overridden. Logic Control/Logic - Gate output B 1.002 1 Bit To KNX

 Standby:
The states at the inputs are linked according to the selected logic
The channel is in standby on startup and awaits pres- function, the result is sent to the output at each input telegram.
ence, the value from parameter "Light Set point top" is
active: If the actual value exceeds the light Set point

©2021 WEINZIERL ENGINEERING GmbH Page 17/20

Logic type “Inverter“ Special type “Valuator“

Each gate channel supports up to 4 separate inverters:

Group Object Type Size Direction
KNX
Logic Control/Logic - Inverter input A 1.002 1 Bit From KNX
Logic Control/Logic - Inverter output A 1.002 1 Bit To KNX
Logic Control/Logic - Inverter input B 1.002 1 Bit From KNX
Logic Control/Logic - Inverter output B 1.002 1 Bit To KNX
Logic Control/Logic - Inverter input C 1.002 1 Bit From KNX
Logic Control/Logic - Inverter output C 1.002 1 Bit To KNX
Logic Control/Logic - Inverter input D 1.002 1 Bit From KNX
Logic Control/Logic - Inverter output D 1.002 1 Bit To KNX
Each channel supports up to 4 valuators to output byte values,
The inverter sends each telegram at the input inverted to the or up to 2 valuators to output 2-byte float values:
output. Group Object Type KNX Size Direction
Special Control/Logic channel - Valuator 1.002 1 Bit From KNX
Logic type “Toggle flip-flop“ binary in A
Special Control/Logic channel - Valuator 5.* 1 Byte To KNX
value out A
Special Control/Logic channel - Valuator 1.002 1 Bit From KNX
binary in B
Special Control/Logic channel - Valuator 5.* 1 Byte To KNX
value out B
Special Control/Logic channel - Valuator 1.002 1 Bit From KNX
binary in C
Special Control/Logic channel - Valuator 5.* 1 Byte To KNX
value out C
Special Control/Logic channel - Valuator 1.002 1 Bit From KNX
binary in D
Special Control/Logic channel - Valuator 5.* 1 Byte To KNX
value out D

Each gate channel supports up to 4 separate toggle flip-flops:

Group Object Type KNX Size Direction
Group Object Type KNX Size Direction Special Control/Logic channel - Valuator 1.002 1 Bit From KNX
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit From KNX binary in A
input A Special Control/Logic channel - Valuator 9.* 2 Byte To KNX
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit To KNX value out A
output A Special Control/Logic channel - Valuator 1.002 1 Bit From KNX
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit From KNX binary in B
input B Special Control/Logic channel - Valuator 9.* 2 Byte To KNX
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit To KNX value out B
output B
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit From KNX The value sent by the output object can be individually config-
input C
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit To KNX
ured for each valuator on 0 and 1 telegram at the input.
output C
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit From KNX Special type “Trigger“
input D
Logic Control/Logic - Toggle flip-flop 1.002 1 Bit To KNX
output D

The toggle flip-flop changes between on/off telegram at the

output at every on telegram at the input. An off telegram at the
input is ignored.

Control/Logic type “Special“

Various functions can be configured here:
 Valuator
 Trigger
 Watchdog
 Filter

©2021 WEINZIERL ENGINEERING GmbH Page 18/20

Each channel supports up to 4 triggers for evaluation of byte Special type “Filter“
values, or up to 2 triggers for evaluation of 2-byte float values:
Group Object Type KNX Size Direction
Special Control/Logic channel - Trigger 5.* 1 Byte From KNX
value in A
Special Control/Logic channel - Trigger 1.001 1 Bit To KNX
binary out A
Special Control/Logic channel - Trigger 5.* 1 Byte From KNX
value in B
Special Control/Logic channel - Trigger 1.001 1 Bit To KNX
binary out B
Special Control/Logic channel - Trigger 5.* 1 Byte From KNX
value in C
Special Control/Logic channel - Trigger 1.001 1 Bit To KNX
binary out C
Special Control/Logic channel - Trigger 5.* 1 Byte From KNX
value in D
Special Control/Logic channel - Trigger 1.001 1 Bit To KNX
binary out D

Group Object Type KNX Size Direction

Special Control/Logic channel - Trigger 9.* 1 Bit From KNX
value in A Each channel supports up to 3 filter functions. These functions
Special Control/Logic channel - Trigger 1.001 2 Byte To KNX are primarily intended for internal links to prevent frequent
binary out A
Special Control/Logic channel - Trigger 9.* 1 Bit From KNX transmission to the KNX bus. The following input types can be
value in B selected:
Special Control/Logic channel - Trigger 1.001 2 Byte To KNX
binary out B
Filter type 1 Bit
Group Object Type KNX Size Direction
It is individually configurable for each trigger, at which threshold Special Control/Logic channel - Filter A 1.001 1 Bit From KNX
value on the input object a 0 or 1 telegram is sent by the output input
Special Control/Logic channel - Filter B 1.001 1 Bit From KNX
object. input
Special Control/Logic channel - Filter C 1.001 1 Bit From KNX
Special type “Watchdog“ input
Special Control/Logic channel - Filter A 1.001 1 Bit To KNX
output
Special Control/Logic channel - Filter B 1.001 1 Bit To KNX
output
Special Control/Logic channel - Filter C 1.001 1 Bit To KNX
output

Filter type 1 Byte

Group Object Type KNX Size Direction
Special Control/Logic channel - Filter A 5.* 1 Byte From KNX
input
Special Control/Logic channel - Filter B 5.* 1 Byte From KNX
input
Special Control/Logic channel - Filter C 5.* 1 Byte From KNX
input
Special Control/Logic channel - Filter A 5.* 1 Byte To KNX
output
Special Control/Logic channel - Filter B 5.* 1 Byte To KNX
output
Special Control/Logic channel - Filter C 5.* 1 Byte To KNX
Each channel supports up to 4 functions to monitor the transmis- output
sion frequency of EnOcean devices:
Group Object Type KNX Size Direction
Filter type 2 Byte
Special Control/Logic channel - Watch- 1.002 1 Bit To KNX
dog A alarm Group Object Type KNX Size Direction
Special Control/Logic channel - Watch- 1.002 1 Bit To KNX Special Control/Logic channel - Filter A 7.* 2 Byte From KNX
dog B alarm input
Special Control/Logic channel - Watch- 1.002 1 Bit To KNX Special Control/Logic channel - Filter B 7.* 2 Byte From KNX
dog C alarm input
Special Control/Logic channel - Watch- 1.002 1 Bit To KNX Special Control/Logic channel - Filter C 7.* 2 Byte From KNX
dog D alarm input
Special Control/Logic channel - Filter A 7.* 2 Byte To KNX
output
The inputs must be internally linked to output objects of Special Control/Logic channel - Filter B 7.* 2 Byte To KNX
output
EnOcean devices. Each reception of an EnOcean telegram Special Control/Logic channel - Filter C 7.* 2 Byte To KNX
restarts the monitoring time. The alarm on KNX is triggered if no output

EnOcean telegram was received within the monitoring time.

Filter type 2 Byte Float
Group Object Type KNX Size Direction
Special Control/Logic channel - Filter A 9.* 2 Byte From KNX
input
Special Control/Logic channel - Filter B 9.* 2 Byte From KNX
input
Special Control/Logic channel - Filter C 9.* 2 Byte From KNX
input
Special Control/Logic channel - Filter A 9.* 2 Byte To KNX
output
Special Control/Logic channel - Filter B 9.* 2 Byte To KNX
output
Special Control/Logic channel - Filter C 9.* 2 Byte To KNX
output

©2021 WEINZIERL ENGINEERING GmbH Page 19/20

For input type 1 bit, 1 and 2 bytes, an output telegram is sent
only if the input value has changed. For input type 2 byte float, it
is also possible to set the minimum change of the input value for
an output telegram. WARNING
In addition, the sending of an output telegram can be completely
 The device must be mounted and commis-
blocked via the object "blocking".
sioned by an authorized electrician.
Group Object Type KNX Size Direction  The prevailing safety rules must be heeded.
Special Control/Logic channel - Blocking 1.001 1 Bit From KNX
 The device must not be opened.
 For planning and construction of electric in-
stallations, the relevant guidelines, regulations
and standards of the respective country are to
be considered.

ETS4/5 Database Weinzierl Engineering GmbH

www.weinzierl.de/en/products/636/ets4 D-84508 Burgkirchen / Alz
Germany
Datasheet www.weinzierl.de
www.weinzierl.de/en/products/636/datasheet [email protected]
CE Declaration
www.weinzierl.de/en/products/636/ce-declaration
Configuration Tool 2021/09/27
www.weinzierl.de/en/products/636/software

©2021 WEINZIERL ENGINEERING GmbH Page 20/20