Page is loading ...
GB
¼
DANGER
Risk of fatal injury from electrical current.
All work carried out on the device may only be
performed by skilled electricians. The country-
specific regulations and the valid KNX guidelines
must be followed.
½CAUTION
Safety clearance must be guaranteed as per DIN-
EN-60664-1. A distance of at least 4 mm must be
maintained between individual cores of the 230
V cable and the KNX line.
½CAUTION
Adjacent devices can be damaged. Devices in-
stalled with next to the switch actuator must
have at least basic insulation.
The KNX/IP router enables telegrams to be forwarded
between different lines via a LAN (IP) as a rapid
backbone. The device can additionally serve as a
programming interface in order to connect a PC with
the KNX bus (e.g. for ETS programming). The IP
address can be assigned via a DHCP server or via
manual configuration (ETS).
The Internet protocols ARP, ICMP, IGMP, UDP/IP and
DHCP are supported. The device operates in
accordance with the KNXnet/IP specification using
core, device management, tunnelling and routing.
Power is supplied externally (12 V to 24 V AC / 12 V to
30 V DC) or alternatively via power over Ethernet (IEEE
802.3af).
For your safety
Getting to know the KNX/IP router
1First plug the KNX/IP router on top of the DIN rail
and then let it snap in below.
2Connect the KNX.
¼
CAUTION
Risk of fatal injury from electrical current.
The
device may become damaged. A safety clear-
ance from the KNX line to 230 V cables must be
guaranteed. Always place the cable cover over
the KNX connecting terminal
.
3Connect the Ethernet patch cable to the RJ 45
socket.
|Note: The connection of an external power sup-
ply is only necessary if the switch used does not
support a power over Ethernet.
4Attach an external power supply if the switch used
does not support a power over Ethernet.
Connections, displays and
operating elements
AConnection of external power supply
(12 V to 24 V AC / 12 V to 30 V DC)
BBus connecting terminal
CProgramming button
DProgramming LED (red)
ELED display for KNX (green):
- lights up when bus voltage is present
- flashes during telegram communication
FLED display for LAN (green):
- lights up when Ethernet connection is present
- flashes during telegram communication
GRJ 45 socket for connecting an Ethernet patch ca-
ble
How to install the KNX/IP-Router
G
E
F
AB
C
D
1
2
230 V
4 mm
KNX
Coupler function (KNX/IP routing)
The KNX/IP router can work as a line or backbone
coupler. In both cases the LAN (IP) is used as a
backbone.
The assignment of the physical address of the KNX/IP
router determines if the device works as a line coupler
or a backbone coupler. If the physical address has the
form x.y.0 (x, y: 1..15), the router works as a line coupler.
If the physical address has the format x.0.0 (x: 1..15), it
is a backbone coupler.
|Note: If the KNX/IP router is used as a backbone
coupler (x.0.0), no KNX/IP router may be located
topologically below it. For example, if a KNX/IP
router has the physical address 1.0.0, a KNX/IP
router with the address 1.1.0 is not permitted.
|Note: If the KNX/IP router is used as a line
coupler (x.y.0), no KNX/IP router may be located
topologically above it. For example, if a KNX/IP
router has the physical address 1.1.0, a KNX/IP
router with the address 1.0.0 is not permitted.
The KNX/IP router has a filter table and thus helps
reduce the bus load. The filter table is automatically
generated by the ETS.
Because of the speed difference between Ethernet (10
Mbit/s) and KNX (9.6 kbit/s), far more telegrams can be
transmitted on the IP. If there several telegrams in a
short row for the same line, they must be buffered in
the router in order to avoid telegram losses. For this, the
KNX/IP router has memory for 150 telegrams (from IP
to KNX).
KNX/IP router as line coupler
KNX/IP router as Backbone coupler
Switch
KNX
LAN
1.1.1
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.7
1.1.12
1.1.11
1.1.10
1.1.9
1.1.8
KNX IP
Router
1.1.0
KNX IP
Router
2.1.0
KNX
2.1.1
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
2.1.7
2.1.12
2.1.11
2.1.10
2.1.9
2.1.8
Switch
LAN
KNX IP
Router
1.0.0
KNX IP
Router
2.0.0
KNX
1.1.0 1.2.0
1.2.1
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.1.1
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
KNX
2.1.0 2.2.0
2.2.1
2.2.6
2.2.5
2.2.4
2.2.3
2.2.2
2.1.1
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
KNX/IP-Router REG-K
Operating instructions
Art. no. MTN680329
V6803-561-00 12/07
V6803_561_00_GB.fm Seite 1 Dienstag, 12. Februar 2008 11:22 11
1
KNX/IP-Router backbone and line coupler
Function as bus access (KNXnet/IP tunnelling)
The KNX/IP router can be used as an interface to the
KNX. The KNX can be accessed from any point in the
LAN. A second physical address must be assigned for
this purpose. This is explained in the application de-
scription.
|Note on removal: To remove, prise out the shut-
ter on the lower side A of the KNX/IP router. Use
a screwdriver for this. Then simply take the KNX/
IP router off the DIN rail.
Removal:
1Load the physical address from the ETS into the
KNX/IP router via the KNX.
2Make the configuration settings in ETS and trans-
fer them.
Starting up the KNX/IP router
S
Switch
LAN
KNX IP
Router
1.0.0
KNX
1.1.0 1.2.0
1.2.1
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.1.1
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
KNX IP
Router
2.1.0
KNX
2.1.1
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
2.1.7
2.1.12
2.1.11
2.1.10
2.1.9
2.1.8
2
3
1
Technical data
Supply from: DC 24 V / approx. 10 mA
External power supply
Voltage: AC 12-24V
DC 12-30V
Power consumption: max. 800 mW
Alternative power supply: Power over Ethernet
Connections
KNX: Via two 1 mm pins for bus
connecting terminal
External power supply: Two screw terminals for
the power supply
LAN: A LAN connection RJ-45
Ambient temperature
Operation: -5 °C to +45 °C
Storage: -25 °C to +55 °C
Transport: -25 °C to +70 °C
Environment: The device is designed for
use at elevations of up to
2000 m above sea level
(MSL)
Max. humidity: 93%, no moisture conden-
sation
Type of protection: IP 20 in accordance with EN
60529
Dimensions: 90x36x65 mm (HxWxD)
Mounting width: 2 pitches
EC guideline: 89/336/EEC
If you have technical questions, please contact the
Customer Care Center in your country.
www.schneider-electric.com
This product must be installed, connected and used in
compliance with prevailing standards and/or installation
regulations. As standards, specifications and designs
develop from time to time, always ask for confirmation
of the information given in this publication.
Schneider Electric Industries SAS
V6803-561-00 12/07
V6803_561_00_GB.fm Seite 2 Dienstag, 12. Februar 2008 11:22 11
2
KNX / IP router 7125/1.0
© 2008 Schneider Electric
●Function
This section lists the functional explanation of the
parameters of the ETS application with their nominal
values and default settings.
General tab
Device name:
You can choose any name for the KNX/IP router REG-
K. The name may be at most 30 characters long. The
name is used to identify individual devices in a
network. The device name should be informative (e.g.
KNX/IP_router_line_1.1.x), so that when several KNX/
IP routers are used, each device can be uniquely
identified and assigned to a line.
Support for unparameterised interfaces:
An interface with a physical address that does not
match the line topology can be used (e.g. for startup).
Parameters: block, enable
Monitoring for bus voltage failure:
If a failure of the KNX is determined, this is reported on
IP. The bus voltage recovery is reported in the same
way.
Parameters: block, enable
IP address assignment:
Automatic (DHCP):
The IP address is automatically assigned via DHCP, i.e.
no additional settings are necessary for it. In order for
this function to be used, there must be a DHCP server
located in the LAN (e.g. many DSL routers have an
integrated DHCP server).
Manual:
Here the IP address, the subnetwork and the gateway
IP address must be entered by hand.
IP configuration tab
IP routing multicast address:
This address is used for routing telegrams to IP. The
multicast IP address 224.0.23.12 was reserved for this
purpose (KNXnet/IP) by the IANA (Internet Assigned
Numbers Authority). If a different multicast IP address
is desired, it must be in the range between 239.0.0.0
and 239.255.255.255.
IP address:
This is the IP address of the KNX/IP router REG-K. It is
only displayed if the IP address assignment in the
"General" tab is set to manual.
IP subnetwork:
The subnetwork mask is to be entered here. This
mask allows the device to determine if a
communication partner is located in the local network.
If there is no partner in the local network, the device
does not send the telegrams directly to the partner,
but to the gateway, which takes over the routing.
IP gateway address:
The gateway's IP address is to be provided here.
|Note: If the KNX/IP router is only used in the
local LAN, the entry 0.0.0.0 can remain.
Example for assigning IP addresses:
A PC should be used to access the KNX/IP router.
IP address of the PC: 192.168.1.30
Subnetwork of the PC: 255.255.255.0
The KNX/IP router is located in the same local LAN, i.e.
it uses the same subnetwork. The assignment of the
IP address is limited by the subnetwork, i.e. in this
example the IP address of the KNX/IP router must be
192.168.1.xx, where xx can be a number from 1 to 254
(except 30, which is already used). Make sure that no
address is assigned twice.
IP address of the KNX/IP router: 192.168.1.31
Subnetwork of the KNX/IP router: 255.255.255.0
KNX / IP router 7125/1.0 General
Parameter Setting
Device name KNX/IP router REG-K
Support for unparameterised
interfaces
block
enable
Monitoring for bus voltage
failure
block
enable
IP address assignment manual
automatic (DHCP)
3
KNX / IP router 7125/1.0
© 2008 Schneider Electric
If the IP address assignment in the "General" tab is set
to manual:
Register routing (KNX -> IP)
Group telegrams (main group 0 to 13):
Group telegrams (main group 14 to 15):
Group telegrams (main group 16 to 31):
|Note: The group addresses of the main groups
16 to 31 are reserved addresses that can be
used in special applications (e.g. in Easy mode).
These group addresses are not available in the
ETS.
Physically addressed telegrams:
Broadcast telegrams:
Acknowledgement (ACK) of group telegrams:
Acknowledgement (ACK) of physically addressed
telegrams:
|Note: In the case of "Answer with NACK", the
parameterisation must take place via IP.
IP configuration 1
Parameter Setting
IP routing multicast address
Byte 1 0–255, 224 default setting
Byte 2 0–255, 0 default setting
Byte 3 0–255, 23 default setting
Byte 4 0–255, 12 default setting
IP address
Byte 1 0–255, 0 default setting
Byte 2 0–255, 0 default setting
Byte 3 0–255, 0 default setting
Byte 4 0–255, 0 default setting
IP configuration 2
Parameter Setting
IP subnetwork
Byte 1 0–255, 0 default setting
Byte 2 0–255, 0 default setting
Byte 3 0–255, 0 default setting
Byte 4 0–255, 0 default setting
IP gateway address
Byte 1 0–255, 0 default setting
Byte 2 0–255, 0 default setting
Byte 3 0–255, 0 default setting
Byte 4 0–255, 0 default setting
Block: No group telegram of these main groups is routed
to IP.
Route: All group telegrams of these main groups are
routed to IP independently of the filter table. This
setting should be used only for test purposes.
Filter: Here the filter table is used to check if the
received group telegram is routed to IP.
Block: No group telegram of the main groups 14 and 15
is routed to IP.
Route: All group telegrams of the main groups 14 and 15
are routed to IP.
Block: No group telegram of these main groups is routed
to IP.
Route: An additional page appears where the routing of
the main groups 16 to 31 can be blocked or
enabled in pairs.
Block: No physically addressed telegram is routed to IP.
Route: All physically addressed telegrams are routed to
IP.
Filter: The physical address is used to check if the
received physically addressed telegram is routed
to IP.
Block: No received broadcast telegram is routed to IP.
Route: All received broadcast telegrams are routed to IP.
Always: An acknowledgement is always generated when
group telegrams are received (from KNX).
Only when
routing:
When group telegrams are received (from KNX),
an acknowledgement is only generated in case of
routing to IP.
Always: An acknowledgement is always generated when
physically addressed telegrams are received
(from KNX).
Only when
routing:
When physically addressed telegrams are
received (from KNX), an acknowledgement is only
generated in case of routing to IP.
Answer with
NACK:
Every physically addressed telegram received
(from KNX) is answered with NACK (not
acknowledge). That means communication with
physically addressed telegrams on the
corresponding KNX line is no longer possible. The
group communication (group telegrams) is not
affected by it. This setting can be used to prevent
manipulation attempts.
Routing (KNX -> IP)
Parameter Setting
Group telegrams
(Main group 0 to 13)
block
route
filter
Group telegrams
(Main group 14 to 15)
block
route
Group telegrams
(Main group 16 to 31)
block
route
(see next page)
Physically addressed telegrams block
route
filter
Broadcast telegrams block
route
Acknowledgement (ACK) of group
telegrams
always
only when routing
Acknowledgement (ACK) of
physically addressed telegrams
only when routing
always
Answer with NACK
4
KNX / IP router 7125/1.0
© 2008 Schneider Electric
If group telegrams (main group 16 to 31) in the
"Routing (KNX-> IP)" tab is set to route:
Register routing (IP -> KNX)
Group telegrams (main group 0 to 13):
Group telegrams (main group 14 to 15):
Group telegrams (main group 16 to 31):
|Note: The group addresses of the main groups
16 to 31 are reserved addresses that can be
used in special applications (e.g. in Easy mode).
These group addresses are not available in the
ETS.
Physically addressed telegrams:
Broadcast telegrams:
Repeat sending of group telegrams:
Repeat sending of physically addressed telegrams:
Repeat sending of broadcast telegrams:
Group tel. 16 to 31
(KNX -> IP)
Parameter Setting
Group telegrams
(Main group 16 to 17)
block
enabled
Group telegrams
(Main group 18 to 19)
block
enabled
Group telegrams
(Main group 20 to 21)
block
enabled
Group telegrams
(Main group 22 to 23)
block
enabled
Group telegrams
(Main group 24 to 25)
block
enabled
Group telegrams
(Main group 26 to 27)
block
enabled
Group telegrams
(Main group 28 to 29)
block
enabled
Group telegrams
(Main group 30 to 31)
block
enabled
Block: No group telegram of these main groups is routed
to KNX.
Route: All group telegrams of these main groups are
routed to KNX independently of the filter table.
This setting should be used only for test
purposes.
Filter: Here the filter table is used to check if the
received group telegram is routed to KNX.
Block: No group telegram of the main groups 14 and 15
is routed to KNX.
Route: All group telegrams of the main groups 14 and 15
are routed to KNX.
Block: No group telegram of this main group is routed to
KNX.
Route: An additional page appears where the routing of
the main groups 16 to 31 can be blocked or
enabled in pairs.
Block: No physically addressed telegram is routed to the
KNX.
Route: All physically addressed telegrams are routed to
the KNX.
Filter: The physical address is used to check if the
received physically addressed telegram is routed
to the KNX.
Block: No received broadcast telegram is routed to the
KNX.
Route: All received broadcast telegrams are routed to the
KNX.
Block: In the event of an error, the received group
telegram is not sent repeatedly to the KNX.
Enable: In the event of an error, the received group
telegram is repeated up to three times.
Block: In the event of an error, the received physically
addressed telegram is not sent repeatedly to the
KNX.
Enable: In the event of an error, the received physically
addressed telegram is repeated up to three times.
Block: In the event of an error, the broadcast telegram is
not sent repeatedly to the KNX.
Enable: In the event of an error, the broadcast telegram is
repeated up to three times.
Routing (IP -> KNX)
Parameter Setting
Group telegrams
(Main group 0 to 13)
block
route
filter
Group telegrams
(Main group 14 to 15)
block
route
Group telegrams
(Main group 16 to 31)
block
route
(see next page)
Physically addressed telegrams block
route
filter
Broadcast telegrams block
route
Repeat sending of group
telegrams
block
release
Repeat sending of physically
addressed telegrams
block
release
Repeat sending of broadcast
telegrams
block
release
5
KNX / IP router 7125/1.0
© 2008 Schneider Electric
If group telegrams (main group 16 to 31) in the
"Routing (IP ->KNX)" tab is set to route:
●Bus access (KNXnet/IP tunnelling)
If the IP configuration of the KNX/IP router REG-K is
valid, it can be used as an interface to the KNX. In order
for this function to be used, the following steps should
be followed in the ETS (from version 3.0c):
– In the ETS under Tools ->Options, select the
Communication tab.
– Click the Configure interface button.
The ETS Connection Manager opens.
– Create a new connection.
– Under Type, select KNXnet/IP.
The ETS begins with the automatic search of all
KNXnet/IP devices. All devices found are displayed.
Select the required device.
Create a second physical address:
The KNX/IP router REG-K needs a second physical
address in order to access the KNX. This second
physical address is used only for bus access and is to
be set as follows:
– In the ETS under Tools ->Options, select the
Communication tab.
– Select a communication interface with type
KNXnet/IP.
– Click the Settings button.
The Settings window of the local interface opens.
– Enter an unused physical address here.
|Note: Make sure that this address is
topologically in the same line but is not used by
another device. If necessary, insert a dummy
device in the ETS project to reserve this
address.
Group tel. 16 to 31
(IP -> KNX)
Parameter Setting
Group telegrams
(Main group 16 to 17)
block
enabled
Group telegrams
(Main group 18 to 19)
block
enabled
Group telegrams
(Main group 20 to 21)
block
enabled
Group telegrams
(Main group 22 to 23)
block
enabled
Group telegrams
(Main group 24 to 25)
block
enabled
Group telegrams
(Main group 26 to 27)
block
enabled
Group telegrams
(Main group 28 to 29)
block
enabled
Group telegrams
(Main group 30 to 31)
block
enabled
6
/
