Button event DCS Communicator
Contents

1.Description

This module is used in conjunction with the DCS IP gateway (Gira Article No. 2620xx). Door opener commands of a DCS Communicator can be evaluated and downstream functions in the HS/FS or KNX can be run. The button events Light, Door opener, Call acceptance and End of call are evaluated.
With the optional assignment of the Inputs 2 to 5, the arriving telegrams can be filtered with regard to the following properties:
  • Bus addresses
  • Button event
  • DCS Communicator number
  • Target address
This means that: With inputs set, only telegrams are evaluated which match the filter properties. Here it is irrelevant whether one or more inputs are assigned.
Example:
With the bus address "0xABCDEF" set, only telegrams are evaluated which were sent from the bus address "0xABCDEF" and triggered by a button event of a DCS Communicator.

Application example:
When a door call is triggered, the music sources in all rooms are muted.
The module allows you to evaluate in which room the door conversation was accepted and the sound of the multiroom system can be switched on again in the other rooms.
Note
If no filters are set, all telegrams are evaluated!
Important
The module requires the firmware version of the DCS IP gateway 1.11 or higher!
Determination of the optional filter parameters
Two different methods are available for determining the filter parameters:
  1. Use of the HomeServer cheat sheet in the DCS IP gateway.
  2. Use of the logic node Display basic parameters in the "Door communication\Additional nodes" folder.
After the parameters are known, it is recommended that the inputs be assigned either group addresses or fixed values.

2.Inputs

No.NameInitialisationDescription
1Door communication Receive""
(14 bytes – Text)
Here the internal communication object Door communication Receive is assigned by the DCS IP gateway.
2Bus address""
(14 bytes – Text)

Optional specification of a bus address to which filtering should be applied.
The bus address must have the following format:
Example: 0xABCD07 or 0x42A305
Note
If this input remains free, the telegrams of random bus addresses are evaluated.
If a communication object is assigned but is not written to or provided with an initialisation value, then the object is considered not to be set. This means the incoming telegrams of all bus addresses are evaluated.
3Button event0
Optional specification of a button event to which filtering is to be applied.
The following values are possible here:

1=Pressing of the light button
2=Pressing of the door opener button
16=Pressing of the end of call button
17=Pressing of the call acceptance button

The input is pre-initialised with the value 0, i.e., all telegrams are evaluated.
If a group address is linked to the input, the initialisation value or object value is used for the filter property.
4DCS Communicator number0
Optional specification of a number of the DCS Communicator to which filtering is to be applied.
The input is pre-initialised with the value 0, i.e. all telegrams are evaluated.
Note
The number (value range 1-255) is assigned in the configuration level in the DCS IP gateway.
5Target address""
(14 bytes – Text)

Optional specification of a bus address to which filtering should be applied.
The bus address must have the following format:
Example: 0xABCD07 or 0x42A305
Note
If this input remains free, the telegrams of random bus addresses are evaluated.
If a communication object is assigned but is not written to or provided with an initialisation value, then the object is considered not to be set. This means the incoming telegrams of all bus addresses are evaluated.
6Release1
Release: This input enables the module to be blocked with regard to the telegram evaluation (e.g. for time-controlled evaluation).

Input value is not equal to 0
The module is completely calculated. Output 1 is calculated depending on the default values. Output 2 sends no telegram!

Input value = 0
The module is not completely calculated. Output 2 is calculated depending on the default values. Output 1 sends no telegram!

3.Outputs

No.NameInitialisationSBCDescription
1Trigger - Module active0s
A 1 is sent on this output when the input telegram matches all filter properties. If filters are missing, then a 1 is sent each time a floor call telegram is received. For input telegrams which do not meet the filter criteria, the output sends a 0.
2Trigger - Module inactive0s
In the case of a blocked module, the output sends a 1 when the input telegram complies with all filter properties. In the case of a blocked module, the output sends a 0 when the telegram does not comply with the filter properties.
3Bus address""s
(14 bytes – Text)
Output of the bus address in the format: Gira 0xABEF07
4Button event0s
A value is sent. This specifies which action was carried out:

1=Pressing of the light button
2=Pressing of the door opener button
16=Pressing of the end of call button
17=Pressing of the call acceptance button
5DCS Communicator number0s
Number of the DCS Communicator on which the button event was triggered.
Note
The number (value range 1-255) is assigned in the configuration level in the DCS IP gateway.
6Target address""s
(14 bytes – Text)
Output of the target address in the format: Gira 0xABEF07
7Error output0s
The output can be routed to the outside as a diagnostic output if necessary or during start-up in order to obtain information about possible errors.
Values in the value range 0 to 4 are sent.
0 = An error has not occurred.
1 = The default values must be checked.
2 = The characters of the bus or target address must be checked.
3 = A telegram with a different structure has been received (e.g. a light call).
4 = The logic is blocked.
s = send, sbc = send by change

4.Other

Recalculation during start:No
Module is retentive:No
Internal designation:16936
Category:Door communication\Receive

5.Similar functions

Receive
Receive\Evaluate code from code keypad
Send
Additional modules