thermokon STC-KNX Bidirectional Gateway with 32 Channels Between EnOcean and KNX Bus Instruction Manual

thermokon STC-KNX Bidirectional Gateway with 32 Channels Between EnOcean

and KNX Bus

Product Information

The STC-KNX is a bidirectional gateway between EnOcean radio devices and the KNX bus. It allows for the transfer of commands and measured values from EnOcean wireless sensors to the KNX bus, enabling control of KNX actuators. Additionally, EnOcean wireless actuators can also be controlled via KNX. The EnOcean communication is based on the EnOcean Equipment Profiles (EEP), which are specified in the data sheet of each EnOcean device. The gateway supports encrypted communication on EnOcean and can be enabled for each sensor or actuator channel separately. It also includes logical and control functions, as well as radio-repeater functionality.

The STC-KNX is divided into 32 channels, and each channel can be assigned to various functions including link from EnOcean sensor to KNX, link from KNX to EnOcean actuator, and control/logic functions. It supports a range of devices such as switches, dimmers, shutters, window handles, temperature sensors, humidity sensors, light sensors, presence sensors, gas sensors, room control panels, automated meter devices, environmental sensors, digital inputs, and more. The configuration of the device and channels is done using the ETS software via the KNX Bus.

Product Usage Instructions

Installation and Connection:

1. Mount the STC-KNX on a wall surface using the provided mounting holes. The holes match those of a 55 mm flush-mounted box.
2. Choose an installation location that considers the RF range of the EnOcean devices associated with the gateway. Avoid mounting near shielding objects (e.g., metal cabinets) or interfering transmitters (e.g., computers, electronic transformers, ballasts).
3. Connect the STC-KNX to the KNX bus using a bus connector. Ensure correct polarity of the terminal referred to the printing inside the unit.
4. The device is powered by the bus and does not require an external or additional power supply.

For more information on range planning and RF interference, refer to the data sheets of the devices and visit www.enocean.com.

The STC-KNX features the following controls and displays:

• Display
• Switch T1 (Exit/Del)
• Switch T2 (Activ/Add)
• Switch T3 (KNX Prog.)
• LED KNX Prog.
• KNX bus connector

Operation and installation manual

STC-KNX

Bidirectional Gateway with 32 channels between EnOcean and KNX Bus

Application

The STC-KNX is a bidirectional gateway between EnOcean radio devices and the KNX bus. It transfers commands and measured values of EnOcean wireless sensors to the KNX bus, for ex-ample, to control KNX actuators. EnOcean wireless actuators can also be controlled via KNX.

The EnOcean communication is based on the EnOcean Equipment Profiles (EEP). This profile is usually specified in the data sheet of the EnOcean device.
For the controlling of EnOcean actuators corresponding EEPs are emulated. This means that the gateway sends radio telegrams like a push button or a window contact.

Encrypted communication on EnOcean is supported; encryption can be enabled for each sensor or actuator channel separately.
Further information to the EnOcean Equipment Profiles can be found on http://www.enocean-alliance.org.
In addition the gateway supports logical and control functions and includes radio-repeater functionality. The STC-KNX is divided in 32 channels. Each channel can be assigned to one of the following functions:

• Link from EnOcean sensor to KNX
  • Switch functions
  • Switching
  • Dimming
  • Shutter
  • Scene
  • Valuator
  • Window handles
  • Window contacts
  • Access card switches
  • Press switches
  • Temperature sensors
  • Humidity sensors
  • Light sensors
  • Presence sensors
  • Gas sensors
  • Room control panels
  • Automated meter devices
  • Environmental sensors
  • Digital inputs
• Link from KNX to EnOcean actuator
  • Emulation of EnOcean switch module for
  • Switching
  • Dimming
  • Shutter
  • Emulation of EnOcean window contact
  • Bidirectional EnOcean switching, dim-ming and shutter actuator
  • Bidirectional EnOcean HVAC drives for valves
• Control / logic
  • Timer
  • Switch-on delay
  • Switch-off delay
  • Control
  • 2-point regulator (byte and float)
  • Continuous regulator (float)
  • Heat requisition
  • Lighting control
  • Logical functions
  • Gates (e.g. AND, OR, XOR)
  • Inverter
  •  Flip-flop (Toggle)
  • Special
  • Valuator
  • Trigger
  • Watchdog
  • Filter

The configuration of the device and the channels is performed using the ETS software via the KNX Bus. To configure the wire-less components the keys and the display in the device are used.

Installation and connection

The mounting can be done on a wall surface (e.g. brick-work or wood). The mounting holes match those of a 55 mm flush-mounted box.
When choosing the installation location the RF range of EnOcean devices to be associated with the gateway has to be considered. Shielding objects (e.g. metal cabinets) or interfering transmitters (e.g. computers, electronic transformers, ballasts) near the gateway should be avoided.

More information on range planning and RF interference can be found in the data sheets of the devices and on www.enocean.com.
The connection to the KNX bus is made with a bus connector. The correct polarity of the terminal referred to the printing inside the unit has to be considered. The device is powered by the bus, and does not require an external or additional power supply.
The STC-KNX features the following controls and displays:

1. Display
2. Switch T1 Exit/Del
3. Switch T2 Activ/Add
4. Switch T3 KNX Prog.
5. LED KNX Prog.
6. KNX bus connector

This device is powered only by the KNX bus.

The device is not working without KNX bus power.

A. KNX Programming mode
The KNX programming mode is activated/deactivated by pressing the KNX programming button T3 ❹.
When the programming mode is active, the programming LED 5 lights red, this LED blinks red, when the application is not running, e.g. after a failed ETS download.

A gateway ex-factory has the default individual address 15.15.255. There are no group addresses and no connections to RF sensors and actuators programmed.

B. Button functions

The buttons inside the device are only needed for the commissioning phase and are not accessible when closed.
Key press T1 long (Del.): Delete the stored device from the current channel
Key press T1 short (Exit): Leave channel/linking mode
Key press T2 long (Add.): Start linking mode
Key press T2 short (Active): Activate or change the channels 1-32

Key press T3 (KNX Prog. Mode): Activate “KNX Prog. mode”
A long key press is detected when a button is pressed for longer than 1 second.

C. LCD Display

The integrated display is used for commissioning and system diagnostics. In normal operation, it is not required and is not visible when the device is closed.

The main menu shows the device name, the operation mode (e.g. “Running”) and the KNX individual address.

D. Defined operation modes

mally.

Loading| ETS download is running
Pending| Last ETS download was not successful; additionally,

programming LED flashes red

Unloaded| ETS application unloaded; additionally, programming

LED flashes red

If the flashing programming LED ❺ indicates a problem during the last ETS download the ETS application should be reloaded.
The signal strength of received radio telegrams is visualized as a bar at the bottom of the display. If the received telegram corresponds to one or more channels, it will be shown in a channel matrix on the display.

When a channel is selected the first line of the display shows the channel number and the text configured in the ETS. In the second line the channel type (sensor/actuator) and associated EnOcean equipment profiles (EEP) is shown. The channel type is displayed on the right edge as a graphical symbol.
In the third line, the number of the allocated and available channel links is displayed. If encryption is enabled for a channel, the next line shows a lock. The signal strength bar is displayed in the last line.

E. Linking to EnOcean devices

Before linking to EnOcean devices, the functions have to be programmed for each channel with the ETS. Per channel typically only one EnOcean device can be linked. For switches, window handles and window contacts up to four links per channel are possible.
If the EnOcean device sends encrypted telegrams “Channel encryption” has to be enabled for the selected channel.
For unidirectional actuator channels any number, for bidirectional only one RF actuator can be learnt. Encrypted control of actuator channels is supported and can be enabled by parameter in the selected channel.

Encrypted communication in EnOcean uses one continuous in-dependent counter (Rolling Code, RLC) in the transmitter and receiver, which is synchronized in the teach-in in both devices.
If the meter reading of learned transmitter and receiver has a difference greater than 60 then no telegrams are accepted by this transmitter. In order to synchronize the RLC again, it is sufficient if the sender sends the gateway a learning telegram and the gateway does not have to be put into the learning mode.
It should be noted that the RLC in the gateway cannot be counted further if its voltage supply is interrupted. If a learned RPS button is pressed more than 30 times in this state, the button and gateway must be synchronized again by sending a learning telegram.

F. Linking mode for RF sensors

The operation of the gateway during the teach-in of wireless sensors is done using the two buttons below the display.
If the device is in normal mode, the push button T2 activates, by short key press, the channel mode and changes to the next channel. The display shows the current channel number and the number of connected devices. Also the ETS configured text will be shown for every channel.
With a long press of T2 on the visible channel, the linking mode is activated. If the device matches the selected function via the parameter configuration, a transmitting device can be connected to the current channel. A connection is created by pressing the learn-button of the sensor. Window handles and switches must be operated for teach-in because they do not have a separate learn button.

To avoid that other transmitting devices are stored by accidental activation during the programming phase, devices can be programmed only after 3-times activation. For this purpose in the general parameters ‘Link switches/handles (RPS) after 3 tel.’ must be selected. The sensor has to send three telegrams within 10 seconds to be linked.
The link mode is terminated by a short press of the left key T1, as well as automatically after 5 minutes without operation.

Quick guide linking mode for RF-sensors

1. T2 short press to select the desired channel.
2. T2 long press to activate the learning mode (“Wait for ENO …”).
3. Activate the learning mode in the RF-sensor.
4. The sensor is now programmed.

G. Deleting links for RF sensors
Links with RF sensors can be deleted in several ways. With a long press on T1 the delete mode is activated for the current channel. The sensor can now be deleted from the visible channel by pressing the learn button on the RF sensor. It is also possible to delete all assignments of the selected channel by pressing T2 (“All”). For this, it is not required to operate the RF sensors.

By programming the application program via the ETS all programmed sensors of all channels will be deleted, when the “Delete all links after download” function in the general parameter is enabled.

If the function of a channel has been changed, programming the parameters with ETS deletes the links of the modified channel.
The link mode is terminated by a short press of the left key T1, as well as automatically after 5 minutes without operation.

Quick guide linking mode for RF sensors:

1. T2 short press to select the desired channel.
2. T1 long press to activate the delete mode (“Wait for ENO or del all links…”).
3. Activate the learning mode at the desired RF sensor to delete.

Alternatively:
T2 long press to delete all taught-in RF sensors from the selected channel.

H. Linking mode for RF-actuators

The selection of the channel during the teach-in of actuators is the same as for the teach-in of sensors, additionally the EnOcean ID of the selected channel is displayed. The teach-in is depending on the emulated sensor type selected:

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

When emulating an RPS switch, the learning mode in the gateway is activated by pressing T2 long at the desired channel. The “Select key:” selection appears in the display. The pressure point (top or bottom) of the learning telegram can be selected here with the T2 button. For some actuators, several pressure points must be separated separately.
Now the T2 button is pressed long to send up to 3 learning telegrams to the actuator in the learning mode (“RF” appears briefly in the display). Once this has been done, the learning mode of the actuator can be terminated again and the actuator is taught-in.

• 1BS input contact (D5-00-01)

The learning mode must first be activated at the actuator. When emulating a 1BS contact, the EnOcean telegram for teach-in is sent by pressing button T2 short on the desired channel, the dis-play briefly shows “RF”.

• VLD actuators (D2-01-XX)
• VLD actuators (D2-05-XX)

The learning mode must first be activated at the actuator. When the bi- directional VLD actuators are teached-in, the learning telegram is triggered by a long button press of T2 in the desired channel (a short “RF” appears in the display), a successful connection is displayed on the links (“Links 1/1”).
Attention: Some actuators on the market trigger learning from their side – this is not supported by the gateway.

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

The teach-in procedure for these bi-directional devices is initiated by the actuator. This means that the teach-in process is the same as for a sensor channel. The message “Wait for ENO …” appears with long button press on button T2, then a learning telegram must be triggered at the actuator. If the teach- in was successful, the display switches back to the channel view.
The learning mode is terminated by a short press of the left but-ton T1, as well as automatically after 5 minutes without operation.

I. Deleting links for RF actuators

The selection of the channel when deleting connections to actuators is the same as for the teach-in of sensors. The teach-in is de-pending on the emulated sensor type:

• RPS switch (F6-02-01 / D2-03-00)
• 1BS input contact (D5-00-01)

The links of these unidirectional actuator channels are stored in the respective actuators. These can be deleted locally for many types on the device without the gateway. In some actuators it is also possible to delete individual links by learning telegrams. In this case, the deletion of actuators works the same way as the teach-in.

• VLD actuators (D2-01-XX)
• VLD actuators (D2-05-XX)

The learning mode must first be activated at the actuator. When the connections of these bidirectional actuators are deleted, the learning telegram is triggered by a long push-button press of T2 in the desired channel (a short “RF” appears in the display), a successful deletion is indicated on the links (“Links 0/1”).
Attention: Some actuators on the market trigger deleting from their side, this is not supported by the gateway.

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

Here also for these bi-directional devices, the teach-in procedure is initiated by the actuator: The message “Wait for ENO …” ap-pears with long press on button T1, then a learning telegram can be triggered at the actuator or the channel can be erased without a learning telegram from the actuator by short press on button T2. If the deletion was successful, the display switches back to the channel view.

Normal operation

J. RF sensors

When in normal operation mode, each received EnOcean telegram will be compared to see if it has been assigned to a channel. If so, the channel is shown shortly in a matrix on the LCD display. Depending on the configured function there will be one or more telegrams sent on the bus. The gateway only sends telegrams to the KNX bus when a corresponding EnOcean telegram has been received.
If an EnOcean telegram is not assigned to any channel, only the signal strength is shown in the display with a bar.

K. RF actuators

If a channel is set to switch or input contact and the gateway re-ceives 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 re-quest of the actuators then it sends the actual values to KNX and EnOcean.
For the other actuator channels, the communication is bidirectional: Each telegram from KNX or EnOcean triggers a telegram on the other medium.

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 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 telegrams 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 implements the associated function.

M. Repeater function

The repeater function is used for extend distances between sensors and actuators. The STC-KNX is a level-1 radio repeater. This means, that only telegrams that come directly from a transmitter will be repeated. Telegrams sent by other repeaters are not repeated again.

The repeater function of the STC-KNX is activated by the general parameters in the ETS. If the function is enabled it will be displayed in the main menu of the display left under the individual address.

Bus monitor function

The integrated bus monitor function is used for system diagnostics directly on the device. The device can display both EnOcean and KNX telegrams.
A short press of T1 in menu activates the dual EnOcean and KNX bus monitor (“ENO+KNX BUSMON”). The last five incoming and outgoing messages are displayed at the bus monitor.
A short press of T2 switches between the operating modes of the bus monitor:

• Dual EnOcean and KNX bus monitor (ENO + KNX BUSMON)
• EnOcean bus monitor (ENO BUSMON)
• KNX bus monitor (KNX BUSMON)
• EnOcean bus monitor for teach-in telegrams (ENO TEACH-IN BUSMON)

Long button press of T2 clears all currently displayed telegrams. To return to the main menu of the gateway, the T1 button is used. The bus monitor is automatically closed after 5 minutes of inactivity.

N. EnOcean bus monitor

If a telegram is received from an EnOcean device, the signal strength (RSSI) value is shown in the first position of the line. The RSSI (Received Signal Strength Indication) is represented by a value between 1 and 4 (1 = min., 4 = best). The first 8 digits of numeric value is the hexadecimal ID of the sending device. The transmitted data is displayed also in hexadecimal coding in the second numeric part.

If a message is sent by the gateway, it is displayed in the first position of the line with an “S”. The ID used by the gateway and the transferred data are also shown.

O. KNX bus monitor
The KNX bus monitor displays the messages at object level. Therefore, only group telegrams are visible which address the gateway or which are sent by it.
If a telegram is received from KNX bus, it will be shown in the KNX bus monitor with an “I”. Behind it the decimal group object number and the data packet will be shown with up to 4 hexadecimal bytes.
If a KNX group address is associated with several group objects in the gateway, one line will be shown for each link.
When sending a message to the KNX bus, an “O” is displayed with the decimal object number and the data packet in hexadecimal coding. If two objects are linked via an internal connection and a telegram is transmitted via this connection, this is indicated with an “M”, the decimal object number of the receiving object and the data packet in hexadecimal coding.

P. EnOcean bus monitor for teach-in telegrams
In this operating mode only EnOcean telegrams are displayed which are sent by the device on pressing the learn button. By this the supported EnOcean Equipment Profile (EEP) of the de-vice can be read directly from the display.

The first 8 digits of numeric value is the hexadecimal ID of the sending device, the next block shows the received EEP number if it could be evaluated.
Summary of displayed messages in bus monitor:
Receiving of EnOcean telegram (ENO BUSMON)
(1-4) Device ID Data packet
Sending of EnOcean-telegram (ENO BUSMON)
S Device ID Data packet
Receiving of EnOcean teach-in telegram (ENO TEACH-IN BUSMON)

Device ID EEP
Receiving of KNX-telegram (KNX BUSMON)
I GO No. Data packet
Sending of KNX-telegram (KNX BUSMON)
O GO No. Data packet
Receiving of internal connected telegram (KNX BUSMON) M GO No. Data packet

Reset to factory device settings

It is possible to reset the device to its factory settings:

• Disconnect the KNX Bus connector ❻ from device
• Press button T1 ❷ and T2 ❸ and keep them pressed down
• Reconnect the KNX Bus connector ❻ of device
• Keep button T1 ❷ and T2 ❸ pressed, until display ❶ is illuminated

If the buttons are released, “MASTER RESET” appears in the display to visualize the successful reset of the device to factory default settings.

ETS database

The ETS database (for ETS 4.2 and 5) can be downloaded from the product website of the STC-KNX (www.weinzierl.de) or from the ETS online catalogue

The following pages and parameters are visible in the ETS.

Q. Device description
The first page shows general information about the device.

Common

• Device name (30 Characters)
  An arbitrary name can be assigned for the STC-KNX. The device name should be meaningful, e.g. „Living Room“. This helps the clarity of the ETS project and this name is also shown in the main view on the inter-nal display.

• Delete all links after download
  If this parameter is active, all linked EnOcean devices in all sensor channels are erased after ETS download.

• 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.

R. Gateway functions
For each of the 32 channels one of the following function can be selected

• Inactive
• Link from EnOcean sensor to KNX
• Link from KNX to EnOcean actuator
• Control/Logic

If a channel function is enabled, a name of up to 15 characters can be assigned to the channel by parameter „Displayed text“. This name should be clear and meaningful, it is shown in the dis-play in the channel view of the selected channel, in addition also in ETS in the object names of the channel.
The 1st channel will be described below, the functioning of the other 31 channels is according to the 1st.

Gateway functions on channel type “Link from EnOcean sensor to KNX”
In this operating mode EnOcean sensors can be integrated into a KNX system.
When pressing the learn button most EnOcean sensors send their EEP to prevent linking of the sensor to an incompatible gateway channel. The compatible profile is written in the param-eter 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.
If the EnOcean sensor transmits encrypted telegrams, this must be activated by the parameter “Channel encryption”.

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 tabs from either channel A or B
2. By activating the energy bow, trigger the learning telegram and activate the encryption

Switching the PTM 215 to unencrypted communication:

1. Simultaneously press all contact tabs from channel A and B
2. By activating the energy bow, trigger the learning telegram and deactivate the encryption

Switch type “1 Push button (F6-01-01)”

The parameters “KNX function” define which KNX telegrams are triggered when the push button is pressed and released:

Switching (On on pressed)

__

Switching (Off on pressed)

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Switching off| 1.001| 1 Bit| To KNX
__

Switching Toggle

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Switching toggle| 1.001| 1 Bit| To KNX

Dimming
On short button press, a switching telegram is sent via object switching. On long button press, a relative dimming is sent over the entire dimming range to object dimming. When releasing af-ter long button press, a dimming stop telegram is sent via object dimming. Both objects are linked, each switching on or increase of brightness is followed by a switching off or decreasing of brightness on next button press.

Shutter
On each long button press the shutter moves up or down alter-natively. If the shutter is moving, it is stopped on short button press, if the shutter is stopped, every short button press sends a step command in up direction.

Switch Sensor channel – Shutter up/down

Switch Sensor channel – Shutter step/stop

| 1.008

1.007

| 1 Bit

1 Bit

| To KNX

To KNX

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

Switch Sensor channel – Scene

| Type KNX

18.001

| Size

1 Byte

| Direction

To KNX

---|---|---|---

Byte value

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Byte value| 5.xxx| 1 Byte| To KNX

Switch type “2 Rockers (F6-02-01)”

Each pressure point of the 2 rockers can be individually assigned to KNX functions by the parameters “KNX function Switch pressure point”:

Disabled

Switching – on

__

Switching – off

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Switching off| 1.001| 1 Bit| To KNX
__

Switching – toggle

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Switching on/off| 1.001| 1 Bit| To KNX
__

Dimming – brighter

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Switching on| 1.001| 1 Bit| To KNX
Switch Sensor channel – Dimming brighter| 3.007| 4 Bit| To KNX
__

Dimming – darker

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Switching off| 1.001| 1 Bit| To KNX
Switch Sensor channel – Dimming darker| 3.007| 4 Bit| To KNX

Dimming – (one-key control)
On short button press, a switching telegram is sent via object switching. On long button press, a relative dimming is sent over the entire dimming range to object dimming. When releasing after long button press, a dimming stop telegram is sent via object dimming. Both objects are linked, each switching on or increase of brightness is followed by a switching off or decreasing of brightness on next button press.

Shutter – up

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Shutter up| 1.008| 1 Bit| To KNX
Switch Sensor channel – Shutter step/stop| 1.007| 1 Bit| To KNX

Shutter – down

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Shutter down

Switch Sensor channel – Shutter step/stop

| 1.008

1.007

| 1 Bit

1 Bit

| To KNX 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 press, if the shutter is stopped, every short button press sends a step command in up direction.

Switch Sensor channel – Shutter

step/stop

| 1.007| 1 Bit| To KNX

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.

Byte value

| | |
Group Object| Type KNX| Size| Direction
Switch Sensor channel – Byte value| 5.xxx| 1 Byte| To KNX

Switch type “4 Rockers (F6-03-01)”

The configuration of a 4-fold rocker is analogous to the 2-fold rocker (F6-02-01), however, it must be noted that for the complete integration, 2 channels must be used in the gateway, one channel for rockers A-B, another channel for rockers C-D. When using a 4-fold rocker, channel encryption is not supported.

Sensor type “Special switches and contacts”
The parameter switch/contact type can be used to select which type of device is to be used, the following profiles are available:

• 1BS Window contact (D5-00-01)
• 4BS Window and door contact (A5-14-xx)
• RPS Window handle (F6-10-00)
• VLD multi sensor window handle (D2-06-01)
• RPS Key card switch (F6-04-01)
• RPS Pressure switch (F6-04-01)
• RPS Pressure switch group (F6-04-01)
• RPS Liquid leakage sensor (F6-05-01)
• VLD Push Button (D2-03-0A, as of ETS database V1.1)
• Generic (RORG-FUNC-TYPE, as of ETS database V1.1)

Switch/contact type “1BS Window contact (D5-00-01)”

For window contacts, up to 4 contacts can be taught into one channel. The gateway detects a common state of all contacts learned in the channel and sends the value “closed” only when all windows are closed.

Switch/contact type “4BS Window and door contact (A5-14-xx)” For this device type, up to 4 contacts can be taught into one channel. The gateway detects a common state of all contacts learned in the channel and sends the value “closed” only when all windows are closed.
The following devices of this profile family are supported:
A5-14-01 open/closed

A5-14-03 open/closed/alarm

| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Window group open| 1.0019| 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

A5-14-07 open/closed/locked

| | |
Group Object

Special Sensor channel – Door group open

| Type KNX

1.002

| Size

1 Bit

| Direction

To KNX

Special Sensor channel – Door group locked| 1.002| 1 Bit| To KNX
Special Sensor channel – Battery low| 1.002| 1 Bit| To KNX

A5-14-08 open/closed/locked/alarm

| |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Door group open| 1.002| 1 Bit| To KNX
Special Sensor channel – Door group locked| 1.002| 1 Bit| To KNX
Special Sensor channel – Alarm

Special Sensor channel – Battery low

| 1.005

1.002

| 1 Bit

1 Bit

| To KNX

To KNX

A5-14-09 open/closed/tilt

| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Window group open state 1| 1.002| 1 Bit| To KNX
Special Sensor channel – Window group open state 2| 1.002| 1 Bit| To KNX
Special Sensor channel – Battery low| 1.002| 1 Bit| To KNX

A5-14-0A open/closed/tilt/alarm

Special Sensor channel – Window group

open state 2

| 1.002| 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

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.
The gateway calculates a common state of all handles assigned to the channels. Following some examples from the state table:

Window 1| Window 2| Window 3| Window 4| Common state
---|---|---|---|---
Open| Open| Open| Open| Open
Open| Tilted| Open| Open| Open
Open| Closed| Tilted| Closed| Open
Closed| Closed| Closed| Tilted| Tilted
Closed| Closed| Closed| Closed| Closed

For window handles the following communication objects are available:

Special Sensor channel – Window group

open state 2

| 1.002| 1 Bit| To KNX

The following telegrams are sent via these objects in the various states of the window group:

| Window closed| Window tilted| Window open
---|---|---|---
Window group open state 1| Off| On| On
Window group open state 2| Off| Off| On

The position of the handle is dependent on the installation condi-tion. This is described in the datasheet of the window handle. The handle is mounted correctly if two Off-telegrams via both data points are sent when the window is closed.

Switch/contact type “VLD multi sensor window handle (D2-06-01)“ On selecting this devices type following objects are available:

Special Sensor channel – Window open

state 2

| 1.002| 1 Bit| To KNX
Special Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Special Sensor channel – Humidity| 9.007| 2 Byte| To KNX
Special Sensor channel – Alarm| 1.005| 1 Bit| To KNX
Special Sensor channel – Battery low| 1.002| 1 Bit| To KNX
| | |

Depending on parameter “KNX function buttons” the 2 buttons on the device can execute the following functions:

Switching

__

Dimming

| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Switching on/off| 1.001| 1 Bit| To KNX
Special Sensor channel – Dimming brighter/darker| 3.007| 4 Bit| To KNX
__

Shutter

| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Shutter up/down| 1.008| 1 Bit| To KNX
Special Sensor channel – Shutter

step/stop

| 1.007| 1 Bit| To KNX
__

Scene

| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Scene| 18.001| 1 Byte| To KNX

Switch/contact type “RPS Key card switch (F6-04-01)” On selecting this devices type following object is available

Switch/contact type “RPS Pressure switch (F6-04-01)” On selecting this devices type following object is available

Switch/contact type “RPS Pressure switch group (F6-04-01)”
On selecting this devices type following object is available

In this operating mode of the pressure switch it is possible to determine via parameter which number of switches must be activated in order to send an ON telegram

Switch/contact type “RPS Liquid leakage sensor (F6-05-01)”
The following object is available with this device type:

Switch/contact type „VLD Push Button (D2-03-0A)“ As of ETS database V1.1

This profile supports push buttons with short/long and double key press. The following object is available for monitoring the battery status:

The battery status is transmitted each time the button

The following KNX functions can be selected for short presses:

§   Switching On

| is pressed.

/long key

Group Object| Type KNX| Size| Direction
Special Sensor channel – Switching on| 1.001| 1 Bit| To KNX
§   Switching Off| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Switching off| 1.001| 1 Bit| To KNX
§   Switching Toggle| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Switching tog- gle| 1.001| 1 Bit| To KNX
Each time the key is pressed, the sent (toggle function).

§   Dimming

| ast value sent is inverted and
Group Object| Type KNX| Size| Direction
Special Sensor channel – Switching on/off| 1.001| 1 Bit| To KNX
Special Sensor channel – Dimming

brighter/darker

| 3.007| 4 Bit| To KNX

Each time the button is pressed, the last dimming direction sent by both objects is evaluated: If the last value sent was a switch 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 telegrams for switching on/off, a long keystroke sends telegrams for dimming brighter/darker.

Shutter

If the button is pressed long, the last value sent is inverted and sent via the “Shutter up/down” object. If the button is pressed short, either a current move command is interrupted via the
“Shutter step/stop” object or the blind moves one step in the opposite direction to the last move command via the “Shutter up/down” object.

Szene

When this function is selected, a parameter for selecting the sent scene appears. In addition, it can be set via parameters whether a command for saving the set scene is to be sent via a long key-stroke.

Byte value

When selecting this function, a parameter for setting the value to send appears.

The following KNX functions can be selected for double button presses:

Switching On

KNX
Each time the key is pressed double, the last value sen and sent (toggle function).

§   Scene

| t is inverted
Group Object| Type KNX| Size| Direction
Special Sensor channel – Scene (double press)| 18.001| 1 Byte| To KNX
When this function is selected, a parameter for selecti scene appears.

§   Byte value

| ng the sent
Group Object| Type KNX| Size| Direction
Special Sensor channel – Byte value (double press)| 5.*| 1 Byte| To KNX

When selecting this function, a parameter for setting the value to send appears.

Switch/contact type „Generic (RORG-FUNC-TYPE)“ As of ETS database V1.1

This function can be used to integrate data from EnOcean sensors with EEPs not supported by the gateway, or to evaluate data from sensors with supported EEPs that deviate from the specification. The EEP of the device to be evaluated must be known and sent by the EnOcean device during the teach-in process. For setting the EPP the parameters RORG, FUNC and TYPE are available, e. g. if the device sends the EEP A5-08-01 during teach-in, the fol-lowing must be set:

• RORG: A5
• FUNC: 08
• TYPE: 01

From the received EnOcean telegram, either individual bits can be evaluated or contiguous bits can be combined as bit fields up to a length of 1 byte and interpreted as a value.
The following object types are available for sending on KNX:

• -1 bit – value

If 1 bit – value is selected, a parameter also appears for setting  whether the bit from the EnOcean telegram is to be sent inverted or not inverted to KNX|

– 1 byte – Integer value / Percent

Special Sensor channel – Generic 1 Byte

– Integer value / Percent

| 5.*| 1 Byte| To KNX
–       2 byte – Integer value| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Generic 2 Byte

– Integer value

| 7.*| 2 Byte| To KNX
–       2 byte – Float value| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Generic 2 Byte

– Float value

| 9.*| 2 Byte| To KNX
–       Raw – Integer value| | |
Group Object| Type KNX| Size| Direction
Special Sensor channel – Generic 1 Byte

– Integer value (raw)

| 5.*| 1 Byte| To KNX

To select one or more bits to be evaluated, there are the following 2 parameters:

• Bit offset
  Specifies the offset from the MSB of the first received data byte at which the evaluation is to start.

• Count of bits (only for group object type 1 byte or 2 bytes)
  Specifies the number of bits that are to be combined 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
  These two parameters are used to set the range of the value in the EnOcean telegram. This range must be taken from the technical description of the EnOcean device.

• Scale to KNX min

• Scale to KNX max
  These two parameters are used to set the scaling of the value from the EnOcean telegram to the value in 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
• A5-02-03: -20 .. +20°C
• A5-02-04: -10 .. +30°C
• A5-02-05: 0 .. +40°C
• A5-02-06: +10 .. +50°C
• A5-02-07: +20 .. +60°C
• A5-02-08: +30 .. +70°C
• A5-02-09: +40 .. +80°C
• A5-02-0A: +50 .. +90°C
• A5-02-0B: +60 .. +100°C
• A5-02-10: -60 .. +20°C
• A5-02-11: -50 .. +30°C
• A5-02-12: -40 .. +40°C
• A5-02-13: -30 .. +50°C
• A5-02-14: -20 .. +60°C
• A5-02-15: -10 .. +70°C
• A5-02-16: 0 .. +80°C
• A5-02-17: +10 .. +90°C
• A5-02-18: +20 .. +100°C
• A5-02-19: +30 .. +110°C
• A5-02-1A: +40 .. +120°C
• A5-02-1B: +50 .. +130°C
• A5-02-20: -10 .. 41,2°C
• A5-02-30: -40 .. 62,3°C

For all temperature sensors the following communication object is available:

Sensor type “4BS Temperature and humidity sensors“

The following profiles can be selected:

• A5-04-01: 0 .. 40°C, 0 .. 100%
• A5-04-02:-20 .. 60°C, 0 .. 100%
• A5-04-03:-20 .. 60°C, 0 .. 100%
  (As of ETS database V1.1)

The measured values are sent via two different communication objects:

Group Object

Hum Sensor channel – Humidity

| Type KNX

9.007

| Size

2 Byte

| Direction

To KNX

---|---|---|---
Hum Sensor channel – Temperature| 9.001| 2 Byte| To KNX

Sensor type “4BS Light sensors“

The following profiles can be selected:

• A5-06-01: 300 .. 60000 lx
• A5-06-02: 0 .. 1020 lx

The measuring of light intensity is done in lux (lx). The measured value is available as a 2-byte float value:

Sensor type “4BS Occupancy sensor“

The following profiles are supported here:

• A5-07-01: Occupancy

Occupancy is transmitted via following object:

§   A5-07-02: Occupancy (As of ETS database Occupancy is transmitted via following object:

|

V1.1)

Group Object| Type KNX| Size| Direction
Occ Sensor channel – Occupancy| 1.018| 1 Bit| To KNX

§   A5-07-03: Occupancy + V1.1)

The occupancy and light intensity jects:

| Light (As of ETS database are sent via the following ob-
Group Object

Occ Sensor channel – Occupancy

| Type KNX

1.018

| Size

1 Bit

| Direction

To KNX

Occ Sensor channel – Illuminance| 9.004| 2 Byte| To KNX

Sensor type “4BS Light/Temperature/ Occupancy sensor“ Following profiles are supported here:

• A5-08-01: 0 .. 510lx, 0 .. 51°C
• A5-08-02: 0 .. 1020lx, 0 .. 51°C
• A5-08-03: 0 .. 1530lx, -30 .. 50°C

Light intensity and temperature are each mapped to a communication object with a 2 bytes float value. Presence and motion detectors send 1-bit values:

LTO Sensor channel – Illuminance

LTO Sensor channel – Temperature

| 9.004

9.001

| 2 Byte

2 Byte

| To KNX

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 Gas sensors“ For all sensors, the gas concentration is available via object. Depending on the EPP of the sensor, further measured values can be sent to KNX:
A5-09-01: CO sensor

__

A5-09-04: CO2 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

|  |  |
Group Object| Type KNX| Size| Direction
Gas Sensor channel – Gas concentration| 9.008| 2 Byte| To KNX
__

A5-09-09: CO2 sensor

|  |  |
Group Object| Type KNX| Size| Direction
Gas Sensor channel – Gas concentration| 9.008| 2 Byte| To KNX
Gas Sensor channel – Battery low| 1.002| 1 Bit| To KNX

Sensor type “4BS Room operating panels“

A variety of room control panels can be used with the gateway, depending on the configuration level and EPP of the device, various objects are displayed.
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 can be determined via parameters.
If a change of the fan stages is available in the profile, the percentage values can be set with 3 parameters, which are sent when switching to the respective fan stage.

A5-10-01: Temperature/Set point/Fan/Occupancy

__

A5-10-02: Temperature/Set point/Fan/Day-Night

|
Group Object| Type KNX| Size| Direction
Room Sensor channel – Fan speed| 5.001| 1 Byte| To KNX
Room Sensor channel – Set point temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Night| 1.002| 1 Bit| To KNX

A5-10-03: Temperature/Set point

__

A5-10-04: Temperature/Set point/Fan

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Fan speed| 5.001| 1 Byte| To KNX
Room Sensor channel – Set point temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
__

A5-10-05: Temperature/Set point/Occupancy

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point 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
__

A5-10-06: Temperature/Set point/Day-Night

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Night| 1.002| 1 Bit| To KNX
__

A5-10-07: Temperature/Fan

|  |  |
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-08: Temperature/Fan/Occupancy

|  |
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
__

A5-10-09: Temperature/Fan/Day- Night

|  |
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 – Night| 1.002| 1 Bit| To KNX
__

A5-10-0A: Temperature/Set point/Contact

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Contact| 1.019| 1 Bit| To KNX
__

A5-10-0B: Temperature/Contact

|  |  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Contact| 1.019| 1 Bit| To KNX
__

A5-10-0C: Temperature/Occupancy

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Occupancy| 1.018| 1 Bit| To KNX
__

A5-10-0D: Temperature/Day- Night

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Night| 1.002| 1 Bit| To KNX

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

A5-10-11: Temperature/Humidity/Set point/Day-Night

__

A5-10-12: Temperature/Humidity/Set point

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point tem- perature| 9.001| 2 Byte| To KNX
Room Sensor channel – Humidity| 9.007| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
__

A5-10-13: Temperature/Humidity/Occupancy

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Humidity| 9.007| 2 Byte| To KNX
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
Room Sensor channel – Humidity| 9.007| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Night| 1.002| 1 Bit| To KNX
__

Temperature/Set point

|  |  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
__

A5-10-16: Temperature/Set point/Occupancy

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point 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
__

A5-10-17: Temperature/Occupancy

|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Occupancy| 1.018| 1 Bit| To KNX

A5-10-18: Temperature/Set point/Fan/Occupancy/Illuminance

__

A5-10-19: Temperature/Fan/Occupancy/Humidity

|
Group Object| Type KNX| Size| Direction
Room Sensor channel – Fan speed| 5.001| 1 Byte| To KNX
Room Sensor channel – Set point temperature| 9.001| 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 – Occupancy| 1.018| 1 Bit| To KNX
__

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

|
Group Object| Type KNX| Size| Direction
Room Sensor channel – Fan speed| 5.001| 1 Byte| To KNX
Room Sensor channel – Set point 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
__

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

A5-10-1C: Temperature/Set point Light/Fan/Occupancy/Illuminance

__

A5-10-1E: 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
__

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

|
Group Object| Type KNX| Size| Direction
Room Sensor channel – Fan speed| 5.001| 1 Byte| To KNX
Room Sensor channel – Set point 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
A5-10-20: Temperature/Set point/Occupancy|  |
Group Object| Type KNX| Size| Direction
Room Sensor channel – Set point 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

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

__

A5-10-22: Temperature/Set point/Fan/Humidit

| __

y

|
Group Object| Type KNX| Size| Direction
Room Sensor channel – Fan speed| 5.001| 1 Byte| To KNX
Room Sensor channel – Set point temperature| 9.001| 2 Byte| To KNX
Room Sensor channel – Humidity| 9.007| 2 Byte| To KNX
Room Sensor channel – Temperature| 9.001| 2 Byte| To KNX

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

Sensor type “4BS Automated meter reading (AMR) “

A maximum of three counter channels are supported for each channel. The counter channels that the EnOcean device trans-mits must be known and set in the parameter. Two communica-tion objects are available for each counter channel, one for the current consumption and for the total consumption.
The profiles have the following objects per channel:

A5-12-00: Counter

AMR Sensor channel – Cumulative counter [1]

AMR Sensor channel – Counter rate [1/s]

| 12.001

__

12.001

| 4 Byte

__

4 Byte

| To KNX

__

To KNX

__

A5-12-01: Electricity

|  |  |
Group Object| Type KNX| Size| Direction
AMR Sensor channel – Cumulative energy [kWh]

AMR Sensor channel – Current energy [kW]

| 13.0013

__

9.024

| 4 Byte

__

2 Byte

| To KNX

__

To KNX

__

A5-12-02: Gas

|  |  |
Group Object| Type KNX| Size| Direction
AMR Sensor channel – Cumulative gas [m3]| 14.0076| 4 Byte| To KNX
AMR Sensor channel – Current gas [l/h]| 9.025| 2 Byte| To KNX
__

A5-12-03: Water

|  |  |
Group Object| Type KNX| Size| Direction
AMR Sensor channel – Cumulative water [m3]| 14.0076| 4 Byte| To KNX
AMR Sensor channel – Current water [l/h]| 9.025| 2 Byte| To KNX

Sensor type “4BS Environmental application “The following environmental sensors can be used with the gate-way:

A5-13-01: Weather station

A5-13-02: Sun intensity, North hemisphere

|  |
Group Object| Type KNX| Size| Direction
Env.App. Sensor channel – Sun West| 9.004| 2 Byte| To KNX
Env.App. Sensor channel – Sun South| 9.004| 2 Byte| To KNX
Env.App. Sensor channel – Sun East| 9.004| 2 Byte| To KNX

A5-13-03: Date

__

A5-13-04: Time and Day

|  |  |
Group Object| Type KNX| Size| Direction
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

Sensor type “4BS Digital input“The following profiles can be used in this category:
A5-30-01: Single input contact, Battery monitor

__

A5-30-02: Single input contact

|  |  |
Group Object| Type KNX| Size| Direction
Dig. Inp Sensor channel – Contact| 1.009| 1 Bit| To KNX

A5-30-03: 4 Digital Inputs, Wake and Temperature

Dig. Inp Sensor channel – Switch/Contact 3

Dig. Inp Sensor channel – Switch/Contact 4

| 1.009

__

1.009

| 1 Bit

__

1 Bit

| To KNX

__

To KNX

Dig. Inp Sensor channel – Switch/Contact Wake| 1.002| 1 Bit| To KNX
Dig. Inp Sensor channel – Tempera-

ture

| 9.001| 2 Byte| To KNX

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

Dig. Inp Sensor channel – Switch/Contact

2

| 1.009| 1 Bit| To KNX
Dig. Inp Sensor channel – Switch/Contact 3| 1.009| 1 Bit| To KNX
Dig. Inp Sensor channel – Byte value| 5.*| 1 Byte| To KNX

Gateway functions on channel type “Link from KNX to EnOcean actuator”
To control EnOcean actuators the gateway can emulate the corresponding sensor profiles. This means the device sends the same radio telegrams as an EnOcean push button for example. Here, each channel uses its own sender ID.
In addition, bidirectional EnOcean actuators with the following EEP families are supported:

• D2-01-XX: Switching/dimming actuators
• D2-05-XX: Shutter actuators
• A5-20-01 and A5-20-04: HVAC actuators for drives

The following actuator functions are available in the parameters:

Emulated sensor type “RPS switch (F6-02-01 / D2-03-00)“

With this profile, a complete RPS switch with 2 rockers can be emulated. Each rocker is separately configurable, the following functions are available:
Switching – Rocker top/bottom (on/off)
In both “Switching” operating modes, an object is available for rocker A and B:

In the case of a switching telegram via KNX, the telegram of the EnOcean rocker is sent for “key pressed” and shortly thereafter for “key released”:

Switching – Rocker top/bottom (off/on)
In the case of a switching telegram via KNX, the telegram of the EnOcean rocker is sent for “key pressed” and shortly thereafter for “key released”:

Dimming – Rocker top/bottom (brighter/darker)
In both “Dimming” operating modes, two objects are available for each rocker A and B:

In the case of a switching telegram via KNX, the telegram of the EnOcean rocker is sent for “key pressed” and shortly thereafter for “key released”.

In the case of a dimming telegram via KNX, the telegram of the EnOcean rocker is sent for “key pressed”, “dimming stop” via KNX triggers an EnOcean telegram for “key released”.

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”.

In the case of a dimming telegram via KNX, the telegram of the EnOcean rocker is sent for “key pressed”, “dimming stop” via KNX triggers an EnOcean telegram for “key released”.

Shutter – Rocker top/bottom (up/down)
In both “Shutter” operating modes, two objects are available for each rocker A and B:

For a move command via KNX the telegram of the EnOcean rocker is sent for “key released” and shortly thereafter for “key pressed”:

A command for the adjustment of the slats via KNX releases 3 telegrams via EnOcean: “Key released,” then “key pressed” and then again “key released”:

Shutter – Rocker top/bottom (down/up)
For a move command via KNX the telegram of the EnOcean rocker is sent for “key released” and shortly thereafter for “key pressed”:

A command for the adjustment of the slats via KNX releases 3 telegrams via EnOcean: “Key released,” then “key pressed” and then again “key released”:

Emulated sensor type “1BS input contact (D5-00-01)“With this profile, a 1BS contact input is emulated, this profile is e.g. used by many simple EnOcean window contacts. One object is available:

KNX telegrams over this object are mapped to EnOcean as follows:

Emulated sensor type “VLD actuators (D2-01-XX)“
With this profile, various bidirectional EnOcean switching or dim-ming actuators of this EEP family can be used.Depending on the device type, the following objects are available for switching or dimming, some profiles also have an energy counter:

VLD Actuator channel – Dimming abso-

lute

| 5.001| 1 Byte| From KNX
VLD Actuator channel – Switching status| 1.001| 1 Bit| To KNX
VLD Actuator channel – Dimming status| 5.001| 1 Byte| To KNX
VLD Actuator channel – Current energy [kW]| 9.024| 2 Byte| To KNX
VLD Actuator channel – Cumulative energy [kWh]| 13.013| 4 Byte| To KNX

The channel used by the EnOcean device must be set in the parameters, alternatively it can be selected that the gateway channel is to control all channels of an EnOcean device. If the EnOcean device has several channels, a separate gateway channel can be used for each.

Emulated sensor type “VLD actuators (D2-05-XX)“
With this profile, bidirectional EnOcean shutter actuators of this EEP family can be used. The following objects are available for this device type:

The channel used by the EnOcean device must be set in the parameters, alternatively it can be selected that the gateway channel is to control all channels of an EnOcean device. If the EnOcean device has several channels, a separate gateway channel can be used for each.
In addition, it can be determined by parameter whether the actuator is to approach positions directly or via a reference run, and the operating time of a step command can also be set.
Emulated sensor type “HVAC actuator for valve (A5-20-01)“With this profile, various bi-directional EnOcean actuators can be used, the following objects are available:

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)“ With this profile, various bi-directional EnOcean actuators can be used, the following objects are available:

The drive cyclically asks the gateway for new data (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.
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.1With this profile, various bi-directional EnOcean actuators can be used, the following objects are available:

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, temperature and rel. setpoint of temperature at the same time, which are immediately for-warded 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“
Several control/logic functions can be selected here. They include time, control, logic, valuator, trigger and watchdog functions. These functions can be operated with a sensor or actuator channel in the device or externally via KNX telegrams.

Control/Logic type “Timer“ Here it is possible to realize a switch-on or switch-off delay. The time is set in seconds.
2 objects are available:

Control/Logic type “Controller“
Various control algorithms are available:

• Two-point float
• Continuous float
• Heat requisition
• Lighting control

Control algorithm “Two-point float“The controller channel has the following objects:

The channel is active on device start, and can be deactivated via object “Controller on/off”. When deactivated, the “Switch” object sends an off telegram and the channel reacts to no changes via the “Actual/Set point” 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.
The parameter “Operating mode” or “Output” can be used to determine whether the output switches off or on when the actual value is over Set point. If the actual value is below Set point with a fixed hysteresis of -1K, the output is switched on or off.
On device start, the Set point from parameters is active, the parameter “Set point via group object” defines how a new Set point via a telegram is treated:

• Relative: Set point from parameter +/- value from telegram
• Absolute: Set point from parameter will be overwritten by value from telegram

Control algorithm “Continuous float“ This controller channel has the following objects:

The channel uses a PI controller, which operates with the configuration 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 variable 0% is sent on the next regular transmission, the controller continues to work according to its configuration on “Window closed”.
When a 1 is received via the “Night” object, the controller goes into the night lowering/raising, whereby the current Set point value is reduced or increased by the value specified in the parameter.
With every received 1 via input “Presence”, the delay time starts again, the controller switches to the night lowering/raising at the end of the delay time.
On device start, the Set point from parameters is active, the parameter “Set point via group object” defines how a new Set point via a telegram is treated:

• Relative: Set point from parameter +/- value from telegram
• Absolute: Set point from parameter will be overwritten by value from telegram

In the operating mode “Heating”, frost protection is also active: If the actual temperature falls below +5°C, the “Control variable” output sends 50% to protect the heating system, if the actual temperature exceeds +6°C when frost protection is active, the controller returns to normal operation.

Control algorithm “Heat requisition“ This controller channel has the following objects:

The maximum input value from the objects “Control value 1-6” is sent to the “Max value” output, whereby the object “Demand” sends a 1 if the maximum value>0, a 0 if the maximum value is 0.
Control algorithm “Lighting control“Several functions can be implemented:

• Full-automatic control
  A typical application for the fully automatic control is the lighting of a corridor.
  The light is turned on in presence when the current brightness value is below the threshold. By manual operation, the light can be switched on or off for a specific time.

• Semi-automatic control
  The semiautomatic mode allows the user or residents to turn the lights on and off manually. The semiautomatic 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.

This controller channel has the following objects:

The lighting control has the following states:

• Deactivated:
  The channel can be deactivated via object “Controller On/Off”. When deactivated, the object “Switch” sends off telegram and the object “Dimming value” sends the value from the parameter “Dim value low”. During de- activation, the channel does not react to changes on the input objects of presence and light value, but can be manually overridden.

• Standby:
  The channel is in standby on startup and awaits presence, the value from parameter “Light Set point top” is active: If the actual value exceeds the light Set point top, an off telegram and the value from parameter “Dim value low” are sent.

• Automatic lighting control:
  This state is activated on receiving presence.
  The monitoring of the upper threshold is always active in this state. Additionally in operating mode full-auto-matic control, ON telegram and the value from parameter “Dim value high” are sent if the actual value falls below the lower threshold.
  Each time presence is received, the delay time presence 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 into standby.

Control/Logic type “Logic element“
Various logic functions can be used here:

• Gate
• Inverter
• Toggle flip-flop

Logic type “Gate“Each gate channel has 2 gates with individually configurable type:

• AND gate
• OR gate
• XOR gate
• NAND gate
• NOR gate
• XNOR gate

Each gate of a channel has 2 input and 1 output object:

The states at the inputs are linked according to the selected logic function, the result is sent to the output at each input telegram.
Logic type “Inverter“Each gate channel supports up to 4 separate inverters:

The inverter sends each telegram at the input inverted to the output.
Logic type “Toggle flip-flop“Each gate channel supports up to 4 separate toggle flip-flops:

Logic Control/Logic – Toggle flip-flop out- put A

Logic Control/Logic – Toggle flip-flop in- put B

| 1.002

1.002

| 1 Bit

1 Bit

| To KNX

From KNX

Logic Control/Logic – Toggle flip-flop out- put B| 1.002| 1 Bit| To KNX
Logic Control/Logic – Toggle flip-flop in- put C| 1.002| 1 Bit| From KNX
Logic Control/Logic – Toggle flip-flop out-

put C

| 1.002| 1 Bit| To KNX
Logic Control/Logic – Toggle flip-flop in- put D| 1.002| 1 Bit| From KNX
Logic Control/Logic – Toggle flip-flop out-

put D

| 1.002| 1 Bit| To KNX

The toggle flip-flop changes between on/off telegram at the out-put 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

Special type “Valuator“ Each channel supports up to 4 valuators to output byte values, or up to 2 valuators to output 2-byte float values:

Special Control/Logic channel – Valuator binary in B

Special Control/Logic channel – Valuator value out B

| 1.002

__

5.*

| 1 Bit

__

1 Byte

| From KNX

__

To KNX

Special Control/Logic channel – Valuator

binary in C

| 1.002| 1 Bit| From KNX
Special Control/Logic channel – Valuator value out C| 5.| 1 Byte| To KNX
Special Control/Logic channel – Valuator binary in D| 1.002| 1 Bit| From KNX
Special Control/Logic channel – Valuator value out D| 5.| 1 Byte| To KNX
 |  |  |
Group Object| Type KNX| Size| Direction
Special Control/Logic channel – Valuator binary in A| 1.002| 1 Bit| From KNX
Special Control/Logic channel – Valuator value out A| 9.*| 2 Byte| To KNX
Special Control/Logic channel – Valuator binary in B

Special Control/Logic channel – Valuator value out B

| 1.002

__

9.*

| 1 Bit

__

2 Byte

| From KNX

__

To KNX

The value sent by the output object can be individually configured for each valuator on 0 and 1 telegram at the input.
Special type “Trigger“Each channel supports up to 4 triggers for evaluation of byte values, or up to 2 triggers for evaluation of 2-byte float values:

Special Control/Logic channel – Trigger binary out A

Special Control/Logic channel – Trigger value in B

| 1.001

5.*

| 1 Bit

1 Byte

| To KNX

From KNX

Special Control/Logic channel – Trigger binary out B| 1.001| 1 Bit| To KNX
Special Control/Logic channel – Trigger value in C| 5.| 1 Byte| From KNX
Special Control/Logic channel – Trigger binary out C| 1.001| 1 Bit| To KNX
Special Control/Logic channel – Trigger value in D| 5.| 1 Byte| From KNX
Special Control/Logic channel – Trigger

binary out D

| 1.001| 1 Bit| To KNX
 |  |  |
Group Object| Type KNX| Size| Direction
Special Control/Logic channel – Trigger value in A| 9.*| 1 Bit| From KNX
Special Control/Logic channel – Trigger

binary out A

| 1.001| 2 Byte| To KNX
Special Control/Logic channel – Trigger value in B

Special Control/Logic channel – Trigger binary out B

| 9.*

1.001

| 1 Bit

2 Byte

| From KNX

To KNX

It is individually configurable for each trigger, at which threshold value on the input object a 0 or 1 telegram is sent by the output object.
Special type “Watchdog“Each channel supports up to 4 functions to monitor the transmission frequency of EnOcean devices:

Special Control/Logic channel – Watch-

dog B alarm

| 1.002| 1 Bit| To KNX
Special Control/Logic channel – Watch- dog C alarm| 1.002| 1 Bit| To KNX
Special Control/Logic channel – Watch-

dog D alarm

| 1.002| 1 Bit| To KNX

The inputs must be internally linked to output objects of EnOcean devices. Each reception of an EnOcean telegram re-starts the monitoring time. The alarm on KNX is triggered if no EnOcean telegram was received within the monitoring time.
Special type “Filter“Each channel supports up to 3 filter functions. These functions are primarily intended for internal links to prevent frequent transmission to the KNX bus. The following input types can be selected:
Filter type 1 Bit

Special Control/Logic channel – Filter B

input

| 1.001| 1 Bit| From KNX
Special Control/Logic channel – Filter C input| 1.001| 1 Bit| From KNX
Special Control/Logic channel – Filter A output| 1.001| 1 Bit| To KNX
Special Control/Logic channel – Filter B output| 1.001| 1 Bit| To KNX
Special Control/Logic channel – Filter C output| 1.001| 1 Bit| To KNX

Filter type 1 Byte

|  |  |
Group Object| Type KNX| Size| Direction
Special Control/Logic channel – Filter A input| 5.*| 1 Byte| From KNX
Special Control/Logic channel – Filter B input

Special Control/Logic channel – Filter C input

| 5.*

5.*

| 1 Byte

1 Byte

| From KNX

From KNX

Special Control/Logic channel – Filter A

output

| 5.| 1 Byte| To KNX
Special Control/Logic channel – Filter B output| 5.| 1 Byte| To KNX
Special Control/Logic channel – Filter C output| 5.*| 1 Byte| To KNX

Filter type 2 Byte

Special Control/Logic channel – Filter B

input

| 7.| 2 Byte| From KNX
Special Control/Logic channel – Filter C input| 7.| 2 Byte| From KNX
Special Control/Logic channel – Filter A

output

| 7.| 2 Byte| To KNX
Special Control/Logic channel – Filter B output| 7.| 2 Byte| To KNX
Special Control/Logic channel – Filter C output| 7.*| 2 Byte| To KNX

Filter type 2 Byte Float

|  |  |
Group Object| Type KNX| Size| Direction
Special Control/Logic channel – Filter A input

Special Control/Logic channel – Filter B input

| 9.*

9.*

| 2 Byte

2 Byte

| From KNX

From KNX

Special Control/Logic channel – Filter C input| 9.*| 2 Byte| From KNX
Special Control/Logic channel – Filter A

output

| 9.| 2 Byte| To KNX
Special Control/Logic channel – Filter B output| 9.| 2 Byte| To KNX
Special Control/Logic channel – Filter C

output

| 9.*| 2 Byte| To KNX

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.
In addition, the sending of an output telegram can be completely blocked via the object “blocking”.

WARNING

• The device must be mounted and commissioned by an authorized electrician.
• The prevailing safety rules must be heeded.
• The device must not be opened.
• For planning and construction of electric installations, the relevant guidelines, regulations and standards of the respective country are to be considered.

Thermokon Sensortechnik GmbH
D-35756 Mittenaar Germany
http://www.thermokon.de
email@thermokon.de 

References

• EnOcean Alliance - Building Smarter Connectivity - EnOcean Radio
• EnOcean – EnOcean Relaunch
• Thermokon – Home of Sensor Technology
• Weinzierl Engineering GmbH

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>