LEGRAND KNX User Manual

5/5
Technical data sheet: S000113312EN-1 Updated: Created: 13/01/2021
Cat. No(s): 0 035 45
KNX routeur IP DIN
7. COMMUNICATION OBJECTS continued
7.2.3 KNX Multicast Address
ETS-Text
Range
[Default value]
Comment
Byte 1 [224 … 239]
224…239
System: [224]
Individual: [239]
First byte of the IP routing multicast
address.
If System multicast address used:
"224" is permanently set.
If Individual multicast address used:
"239" is permanently set.
Byte 2 [0 … 255]
0…255
[0]
Second byte of the IP routing
multicast address.
Can only be set manually if an
individual multicast address is used.
Byte 3 [0 … 255]
0…255
[23]
Third byte of the IP routing multicast
address.
Can only be set manually if an
individual multicast address is used.
Byte 4 [0 … 255]
0…255
[12]
Fourth byte of the IP routing
multicast address.
Can only be set manually if an
individual multicast address is used.
Table 4: KNX Multicast Address
Note:
The Multicast IP address 224.0.23.12 is the defined address for the
KNXnet/IP from the KNX Association in conjunction with the IANA.
This address should stay as defined and only changed if it becomes
necessary due to the existing network.
By commissioning, it should be regarded that all KNX IP devices
which should communicate with one another via IP must use the
same IP routing multicast address.
7.2.4 Settings for coupler
ETS-Text
Range
[Default value]
Comment
Fallback time for manual
operation
10 min, 1 hour,
4 hours, 8 hours
[1 hour]
Time duration required to exit from
“manual operation”
Manual function
Disabled
Pass all telegrams
Pass physical telegrams
Pass group telegrams
[pass all telegrams]
Telegram routing configuration for
the manual function.
Table 5: Parameter General
7.2.5 Main Line
ETS-Text
Range
[Default value]
Comment
Configuration
- groups: filter, physical:
block
- groups, physical: filter
- groups: route, physi-
cal: filter
- groups, physical: route
- Configure
[groups, physical:
filter]
- Block: no telegram is routed.
- Filter: Only telegrams are routed
which are entered in the filter table.
- Route: the telegrams are routed.
- Configure: the following
parameters can be set individually.
Group telegrams
1. transmit all (for
testing only)
2. Block
3. filter
[filter]
1. All group telegrams are
transmitted.
2. No group telegram is transmitted.
3. Only group telegrams are routed
which are entered in the filter
table.
The ETS 4/5 produces the filter table
automatically.
Main group telegrams 14/15
1. transmit all
2. block
[transmit all]
1. Group telegrams with the main
group 14 or 15 (e.g. 14/1) are
routed.
2. Group telegrams with the main
group 14 or 15 (e.g. 14/1) are not
routed.
Physical telegrams
1. transmit all (for
testing only)
2. Block
3. filter
[filter]
1. All physical telegrams are
transmitted.
2. No physical telegram is
transmitted.
3. Only physical telegrams are routed
based on physical address.
Table 6: Main Line
7. COMMUNICATION OBJECTS continued
7.2.6 Sub Line
ETS-Text
Range
[Default value]
Comment
Configuration
- groups: filter, physical:
block
- groups, physical: filter
- groups: route, physi-
cal: filter
- groups, physical: route
- Configure
[groups, physical:
filter]
- Block: no telegram is routed.
- Filter: Only telegrams are routed
which are entered in the filter table.
- Route: the telegrams are routed.
- Configure: the following
parameters can be set individually.
This parameter is to be set
depending on the planed
configuration.
Group telegrams
1. transmit all (for
testing only)
2. Block
3. filter
[filter]
1. All group telegrams are
transmitted.
2. No group telegram is transmitted.
3. Only group telegrams are routed
which are entered in the filter
table. The ETS 4/5 produces the
filter table automatically.
Sub group telegrams 14/15
1. transmit all
2. block
[transmit all]
1. Group telegrams with the main
group 14 or 15 (e.g. 14/1) are
routed.
2. Group telegrams with the main
group 14 or 15 (e.g. 14/1) are not
routed.
Physical telegrams
1. transmit all (for
testing only)
2. Block
3. filter
[filter]
1. All physical telegrams are
transmitted.
2. No physical telegram is
transmitted.
3. Only physical telegrams are routed
based on physical address.
Physical: Repetition
if errors on sub line
1. no
2. normal
3. reduced
[normal]
If a transmission error (e.g. due to
missing receiver) is found when
sending a physical telegram on the
sub line:
1. The physical telegram is not
repeated.
2. The physical telegram is repeated
up to 3 times.
3. The physical telegram will be
repeated only one time.
Group: Repetition
if errors on sub line
1. no
2. normal
3. reduced
[normal]
If a transmission error (e.g. due to
missing receiver) is found when
sending a group telegram on the
sub line:
1. The group telegram is not
repeated.
2. The group telegram is repeated up
to 3 times.
3. The group telegram will be
repeated only one time.
Telegram confirmations on line
1. if routed
2. always
[if routed]
1. Only telegrams which are to be
routed are confirmed on the sub
line (ACK).
2. Each telegram on the sub line is
confirmed (ACK).
Send confirmation on own
telegrams
1. yes
2. no
[no]
1. Every telegram on the sub line is
confirmed with its own ACK (from
the Line coupler).
2. No confirmation with own ACK
Table 7: Sub Line
Note:
If the parameter “Send confirmation on own telegrams” is set yes,
IP Router will send an ACK systematically when sending any own
routed telegram.
CONTENTS

LEGRAND KNX Specifications

General

Brand	LEGRAND
Model	KNX
Category	Relays
Language	English