©
2017 WEINZIERL ENGINEERING GmbH
Page 7/8
Block:
No received broadcast telegrams are routed
to IP.
Route:
All received broadcast telegrams are routed
to IP.
Acknowledge (ACK) of group telegrams
Always:
A acknowledge is generated for every re-
ceived group telegram (from KNX).
Only if routed:
A acknowledge is only generated for re-
ceived group telegrams (from KNX) if they
are routed to IP.
Acknowledge (ACK) of individually addressed telegrams
Always:
A acknowledge is generated for every re-
ceived individual addressed telegram (from
KNX).
Only if routed:
A acknowledge is only generated for re-
ceived individually addressed group tele-
grams (from KNX) if they are routed to IP.
Answer with NACK:
Every received individually addressed tele-
gram (from KNX) is responded to with NACK
(Not acknowledge). This means that commu-
nication with individually addressed tele-
grams on the corresponding KNX line is not
possible. Group communication (group tele-
grams) is not affected. This setting can be
used to block attempts at manipulation.
When using “Answer with NACK” an access to the
device via KNX TP is no longer possible. The
configuration must be performed via IP.
Routing (IP -> KNX TP)
Group telegrams (main group 0 to 13)
Block:
No group telegrams of these main groups
are routed to KNX TP.
Route:
All group telegrams of this main group are
routed to KNX TP independent of the filter
table. This setting is used for testing pur-
poses only.
Filter:
The filter table is used to check whether the
received group telegram should be routed to
KNX TP.
Group telegrams (main group 14 to 31)
Block:
No group telegrams of main groups 14 to 31
are routed to KNX TP.
Route:
All group telegrams of the main groups 14 to
31 are routed to KNX TP.
Filter:
The filter table is used to check whether the
received group telegram should be routed to
KNX TP.
Individually addressed telegrams
Block:
No individually addressed telegrams are
routed to KNX TP.
Route:
All individually addressed telegrams are
routed to KNX TP.
Filter:
The individual address is used to check
whether the received individually addressed
telegram should be routed to KNX TP.
Broadcast telegrams
Block:
No received broadcast telegrams are routed
to KNX TP.
Route:
All received broadcast telegrams are routed
to KNX TP.
Resending of group telegrams
Disable:
The received group telegram is not resent to
KNX TP in case of a fault.
Enable:
The received group telegram is resent up to
three times in case of a fault.
Resending of individually addressed telegrams
Disable:
The received individually addressed tele-
gram is not resent to KNX TP in case of a
fault.
Enable:
The received individually addressed tele-
gram is resent up to three times in case of a
fault.
Resending of broadcast telegrams
Disable:
The received broadcast telegram is not re-
sent to KNX TP in case of a fault.
Enable:
The received broadcast telegram is resent
up to three times in case of a fault.
Programming
The KNX IP LineMaster 762 can be programmed in different
ways by the ETS:
Via KNX Bus
The device only needs to be connected to the KNX bus. The
ETS requires an additional interface (for example, USB) to have
access to the bus. Via this way both the individual address and
the entire application including IP configuration can be pro-
grammed. Programming via the bus is recommended if no IP
connection can be established.
Via KNXnet/IP Tunneling
No additional interface is required. Programming via KNXnet/IP
Tunneling is possible if the device already has a valid IP configu-
ration (e.g. by using DHCP or Auto IP). In this case the device is
displayed in the interface configuration of the ETS and must be
selected. The download is executed via the ETS project as with
many other devices.
Via KNXnet/IP Routing
Programming via KNXnet/IP Routing is possible if the device al-
ready has a valid IP configuration (e.g. by using DHCP or Auto
