Linking facilities
The "System coupling" service can be used to transmit group address telegrams from one BAB device to another via a UDP Unicast connection. Thanks to the Unicast connection, communication via network domains can be established at a lower cost than would be the case with a KNXnet/IP routing connection. System coupling is currently supported by the following BAB devices:
EIBPORT
FACILITYMASTER
LINKMODULE
Note: Communication with system coupling is group address based. Physically addressed telegrams will not be transmitted. Programming of KNX devices using the ETS is not possible via system coupling.
Using system coupling via BAB SECURELINK provides added security with respect to the connection. See chapter BAB SECURELINK.
Requirements
The following requirements must be met to enable a connection between BAB devices:
Complete network settings in both devices (Standard Gateway, DNS)
Free communication on UDP port 1735
Fixed external address of the target device (fixed IP address / dynamic DNS address / VPN IP)
Set up and enabled SECURELINK connection if desired.
To receive system coupling telegrams no settings must be made in the opposite device.
Parametrization
Parametrization of facility linking will be done by the integrated job editor – job “Linking facilities”. All parameters always be parameterised out of the sight of local EIB-installation in direction to aimed EIB-equipment.
Should the EIB installation 1 be connected with one EIB installation 2 and reverted, so you have to configure always the service “Linking facilities” in both EIBPORT s.
Job Name
Required field. Assign a unique name for the job. The name must not contain more than 15 characters.
Gate Group Addresses
By Gate Group Addresses job will be released or blocked. The release object releases or locks the job. It is about an EIS1 object:
Field blank = Job is released.
Field completed, value 1 = Job released.
Field completed, value 0 = job locked.
Field completed, no value = job locked.
As soon as one address is filled in, release will behave respective to the value of the group address. If no value was sent to the address and the address is presently without values, job will be blocked.
Hostname / IP-address
Hostname or IP-address from the destination EIBPORT of the facility linking. (As soon as DNS of EIBPORT will be supported, name of destination EIBPORT could be entered here).
Get Host by name instantly
enabled: by starting the EIBPORT resolution of name happens immediately.
disabled: Name resolution only takes place by activating the job.
Always get host by name
enabled: Every start of the job will cause the name resolving again (only useful by dynamic resolution).
disabled: Hostname will only be resolute by the first start of the service.
Allow loop backs
enabled: Permits loopbacks via LAN.
disabled: Loopbacks via LAN will be suppressed.
Connection type
Direct (LAN): Equipment linkage via Ethernet.
Target system ID
Can currently only be used for EIBPORT and FACILITYMASTER. Unique KNX system ID (0 - 25) (no entry: Target system ID = 0)
Rules / transformations
The transmission rules can be used to filter and transform communication to the opposite device. In this way, real group addresses from the source world can, for example, be transformed into virtual addresses (see below) in the target world to avoid unnecessary workloads or overlapping group addresses. When entering the rules, wild cards can be used. The "*" symbol is used as wild card. Depending on its position (before or after the "/"), the "*" represents the KNX main group or sub-group.
Rule | Meaning |
*/*/* -> */*/* | All main groups and sub-groups of KNX system 1 are coupled 1:1 into KNX system 2. Important: In the target world, all incoming telegrams (from the real address range) are sent on KNX again! |
6/*/* -> 6/*/* | All group addresses of main group 6 of KNX system 1 are coupled into main group 6 of KNX system 2. |
7/* /* -> 17/*/* | All group addresses of main group 7 of KNX system 1 are coupled into the virtual main group 17 of KNX system 2. This prevents overlapping group addresses! |
*/*/1 -> */*/1 | The addresses 0/0/1; 1/1/1; 2/2/1...32/7/1 are coupled into KNX system 2 |
Virtual group addresses
Virtual group addresses are the main groups 16-32 They are only available in EIBPORT and they are not transferred to the KNX interface. Virtual group addresses can be used with system coupling to avoid unnecessary workloads and overlapping group addresses.
Example
If, for example, a light scene is to be started from system 1 (LINKMODULE) in system 2 (EIBPORT), then the light scene in system 2 is assigned a virtual group address (e.g. 17/1). The following rule could then be parameterised in the LINKMODULE of system 1:
e.g. 2/3 -> 17/1. The real group address in system 1 (e.g. assigned to a push-button) is translated into the virtual group address in system 2 (the light scene).
No settings must be made in the opposite device to receive system coupling telegrams.
System coupling via BAB SECURELINK
If system coupling is established via BAB SECURELINK, communication between the two system parts is safe from interception. To do this, please proceed as described below.
Define VPN server and VPN client.
Initialise VPN server in both devices (see chapter Initialising VPN SSL server)
Establish SECURELINK from client to server (see chapter Establishing SECURELINK connection)
Establish system coupling specifying the VPN IP addresses (!)
If the VPN IP addresses are specified, the system coupling communicates via the secured SECURELINK tunnel.