Jung IPR 300 SREG Operator's manual

Product documentation
ALBRECHT JUNG GMBH & CO. KG
Volmestraße 1
58579 Schalksmühle
GERMANY
Tel. [phone]
Fax [phone]
[email protected]
www.jung.de
IP router
Ref.-no.: IPR 300 SREG
IP interface
Ref.-no.: IPS 300 SREG
07/2019

Page 2 of 25IPR / IPS 300 SREG
Table of Contents
Table of Contents
1 Safety instructions and device components .................................................3
1.1 Safety instructions....................................................................................................... 3
1.2 Device components ..................................................................................................... 3
2 Function ............................................................................................................3
2.1 System information ..................................................................................................... 3
2.2 Intended use................................................................................................................. 3
2.3 Product characteristics ............................................................................................... 4
3 Information for electrically skilled persons ...................................................4
3.1 Installation and electrical connection........................................................................ 4
3.2 Mounting....................................................................................................................... 4
3.3 Connection ................................................................................................................... 4
4 Commissioning ................................................................................................5
4.1 Switching on................................................................................................................. 5
4.2 Boot procedure ............................................................................................................ 5
5 Operation ..........................................................................................................6
5.1 Display .......................................................................................................................... 6
5.2 LED displays ................................................................................................................ 6
5.3 Factory settings / reset................................................................................................ 7
6 Conguration....................................................................................................7
6.1 Topology ....................................................................................................................... 7
6.1.1 IP interface..................................................................................................................................... 7
6.1.2 IP router ......................................................................................................................................... 7
6.2 Device properties......................................................................................................... 8
6.2.1 General .......................................................................................................................................... 8
6.2.2 IP properties................................................................................................................................... 9
6.2.3 KNX IP Secure............................................................................................................................... 9
6.3 Device-specicparameters ......................................................................................10
6.3.1 IP interface...................................................................................................................................10
6.3.2 IP router .......................................................................................................................................12
7 Telnet ...............................................................................................................18
7.1 IP router and IP interface...........................................................................................18
7.2 IP router ......................................................................................................................22
8 Terms...............................................................................................................23
9 Technical data.................................................................................................24
10 Warranty ..........................................................................................................24
11 Open Source Software...................................................................................25
11.1 LWIP ............................................................................................................................25

Page 3 of 25IPR / IPS 300 SREG
Safety instructions and device components
1 Safety instructions and device components
1.1 Safety instructions
 Electricalequipmentmayonlybettedandconnectedbyelectricallyskilledpersons.
Seriousinjuries,reorpropertydamagepossible.Pleasereadandfollowmanualfully.
These instructions are an integral part of the product and must remain with the end customer.
This product is only intended for use in dry rooms.
1.2 Device components
Made in Germany
NEXTPROG
BUSPROG POWER
Fig. 1: Device components
1 KNX connection 5 LAN connection
2 NEXT button 6 PROG LED
3 Display 7 BUS LED
4 POWER LED 8 PROG button
2 Function
2.1 System information
This device is a product of the KNX system and conforms to the KNX Directives. Detailed knowledge
attained through KNX training is a prerequisite for understanding.
The device function is software-dependent.
Detailed information about software versions and the respective function scope, as well as the software itself
can be found in the manufacturer‘s product database.
The device is planned, installed and commissioned by means of KNX-certied software. Full functionality
with KNX commissioning software version ETS 5.7 f onwards.
An updated version of the product database, technical descriptions and conversion programs and other
auxiliary programs are available on our Internet website.
2.2 Intended use
- Connection between KNX devices and PC or other data processing devices via IP
- Operation as KNX area/line coupler or data interface
- Mounting on DIN rail according to EN 60715 in distribution boxes
5
4
3
2
1
7
6
8

Page 4 of 25IPR / IPS 300 SREG
Information for electrically skilled persons
2.3 Product characteristics
- KNXnet/IP routing for communication between KNX lines, areas and systems via IP network
- Support of KNX Data Secure from ETS version 5.7 upwards
- Support of KNX IP Secure from ETS version 5.7 upwards
- Telegram forwarding and ltering according to physical address or group address
- Max. 48 telegrams per second in IP secure mode
- LED display for KNX communication, Ethernet communication and programming mode
- Conguration via ETS, Telnet or software tool
- SNTP server, bu󰀨ered
- Commissioning with display support
- Max. 8 connections to IP terminal devices, e.g. for simultaneous visualisation and conguration
- Outage message of the KNX system to the IP system
- Electrical isolation between KNX and IP network
- Power consumption max. 1 W
3 Information for electrically skilled persons
3.1 Installation and electrical connection
DANGER
Electrical shock on contact with live parts in the installation environment.
Electrical shocks can be fatal.
Before working on the device, disconnect the power and cover live parts in the area!
3.2 Mounting
Mount IP router on DIN rail according to EN 60715 in distribution boxes.
3.3 Connection
Made in Germany
NEXTPROG
BUSPROG POWER
Fig. 2: Connection
1 KNX connection 2 LAN connection
Requirements:
• one Ethernet connection with 10/100 Mbit
• one KNX/EIB bus connection
For position of the connections see device components.
• Connect LAN and KNX.
2
1

Page 5 of 25IPR / IPS 300 SREG
Commissioning
4 Commissioning
Made in Germany
NEXTPROG
BUSPROG POWER
Fig. 3: Commissioning
1 Display 3 PROG LED
2 POWER LED 4 BUS LED
4.1 Switching on
After connecting, the device is switched on automatically. The product name and assigned IP address
appear on the display when switching on.
4.2 Boot procedure
The automatic boot procedure starts after switching on. The three LEDs ash on the front of the device as a
running light during the boot procedure.
PROG LED – red
BUS LED – yellow
POWER LED – green
The duration of the boot procedure is prolonged if the IP address is assigned to the IP router via DHCP.
DHCP is specied by the factory settings. The green POWER LED ashes during the assignment of the IP
address.
The IP address of the device appears in the display at the end of the boot procedure.
2
1
4
3

Page 6 of 25IPR / IPS 300 SREG
Operation
5 Operation
Made in Germany
NEXTPROG
BUSPROG POWER
Fig. 4: Operation
1 NEXT button 4 PROG LED
2 Display 5 BUS LED
3 POWER LED 6 PROG button
5.1 Display
The display switches itself o󰀨 automatically after one minute.
Switching on display:
• Press NEXT button.
Scrolling through menu:
• Press NEXT button repeatedly while the display is switched on.
Menu structure:
- Page 1:
Displaying the rmware version, IP address, physical address, serial number and tunnel connections used
- Page 2:
Displaying all IP settings
Displaying the boot-up time
- Page 3:
Information on the telegram rate
- Page 4:
Displaying the FDSK (Factory Default Setup Key)
This is only displayed if the device is still in the delivery state.
5.2 LED displays
There are three LEDs on the front of the device. The LEDs indicate the following device statuses during
operation:
- PROG LED lights up red:
Device is in programming mode.
- BUS LED ashes yellow:
Device bus is active.
- POWER LED ashes green:
Device is ready for operation.
There are two other LEDs next to the LAN connection. The LEDs indicate the following device statuses
during operation:
- green LED:
Connection to another IP device or switch is established.
- yellow LED:
IP data transfer is active.
3
2
1
5
4
6

Page 7 of 25IPR / IPS 300 SREG
Conguration
5.3 Factory settings / reset
Restoring factory settings:
• Press PROG button for 10 seconds.
PROG LED ashes red.
Device is in programming mode.
Factory settings are restored automatically.
Boot procedure is started.
6 Conguration
6.1 Topology
6.1.1 IP interface
To insert the interface into an ETS project, a TP line must exist.
6.1.2 IP router
To insert the router into an ETS project, it must have an IP backbone.
Example:
Fig. 5: Topology (left) and properties of the backbone
Line 1: Backbone Medium IP
Line 1.1: Line Medium TP
In the Properties Diagram of the Backbone (NOTE: For this click on Topology, directly above “Dynamic
Folders”, see gure 5), you will nd the settings for the Multicast of the Backbone. Network latency (see
gure 5) can be changed if the routing is over a large distributed system. In this case, increase the time
constant.
The KNX IP Secure Router supports up to eight KNX (Secure) IP tunnel connections and can be used as a
line or area coupler.

Page 8 of 25IPR / IPS 300 SREG
Conguration
6.2 Device properties
6.2.1 General
Fig. 6: Properties of the device
Function Description
Name Any name can be assigned, max. 30 characters
Secure Comissioning If activated, the encryption is active for commissioning: all
parameters are then transmitted in encrypted form, although e.g.
Tunnel connections are still unencrypted.
Secure Tunneling If activated, the tunnel connections can only be established via KNX
Secure Tunneling.

Page 9 of 25IPR / IPS 300 SREG
Conguration
6.2.2 IP properties
Fig. 7: IP Properties of the device
Function Description
Obtain an IP address
automatically
The device requires a DHCP server for IP address assignment.
Use a static IP address The user species the IP settings.
Comissioning Password A password from which the ETS generates a key. This is the key to
secure commissioning (see above).
Authentication Code With the authentication password, the user proves that he has
access to the project.
MAC Address Is a device property.
Multicast Address Is given by the backbone conguration (see gure 5).
6.2.3 KNX IP Secure
Requirements:
- Safe commissioning activated
- FDSK entered/scanned or device certicate added
Conguration of KNX IP Secure:
• Activate secure tunneling.
• Dene a password for each tunnel (max. 8 tunnels).
• Dene a password for commissioning and authentication code.
iDocument all passwords and store them securely.

Page 10 of 25IPR / IPS 300 SREG
Conguration
6.3 Device-specicparameters
6.3.1 IP interface
General settings
Fig. 8: General settings of the device
Function Options Description
(Text) The ETS has manufacturer-independent uniform
parameter descriptions for various settings. To
simplify the application, a note text is displayed
here.
Enable advanced settings o󰀨/on Advanced functions to ensure a maximum of
exibility.
Advanced settings
Fig. 9: Advanced settings of the device
Function Options Description
Max. number of telegrams
to KNX TP
5 .. 50 See parameter description

Page 11 of 25IPR / IPS 300 SREG
Conguration
Advanced settings standard tunnel preferred IP
For standard tunnel connections (before 2019) it is possible to assign each of these tunnel connections to
an IP address. In the analysis of group telegrams, this makes it easier to assign the telegrams to the sender
which „sits“ behind the tunnel, as e.g. Visualizations or smartphone apps.
iThis assignment can be resolved at any time by the ETS or a new so-called extended tunnel connection
(as of 2019).
Fig. 11: Preferred IP for Tunnelling
Function Options Description
Slow connection o󰀨/on The tunnel connections over UDP are controlled
by default with a connection timeout of
1 second. This may be too short for connections
over the Internet.
UDP connection timeout 1,0 ... 8,0 sec Setting of timeout for tunnel connection over
UDP
Preferred IP for tunnel X o󰀨/on Tunnel X should preferably be used for
communication with the parametrized IP
address.
End device IP (IP-V4 address) IP adress of end device

Page 12 of 25IPR / IPS 300 SREG
Conguration
6.3.2 IP router
General settings
Fig. 12: General settings of the device
Function Options Description
(Text) The ETS has manufacturer-independent uniform
parameter descriptions for various settings. To
simplify the application, a note text is displayed
here.
Enable advanced settings o󰀨/on Advanced functions to ensure a maximum of
exibility.

Page 13 of 25IPR / IPS 300 SREG
Conguration
Advanced settings properties of the subline
Fig. 13: Properties of the subline
Function Options Description
ACK for every telegram o󰀨/on The router acknowledges each telegram, even if
it does not forward this telegram (TP only)
ACK for routed telegram
only
o󰀨/on The router only conrms the telegrams that it
forwards (TP only)
Repeat routed telegrams if
not ACKed
o󰀨/on The router repeats unconrmed individually
addressed telegrams (TP only)
Inhibit programming from
TP side
o󰀨/on See parameter description
Max. number of telegrams
to KNX TP
5 .. 50 See parameter description

Page 14 of 25IPR / IPS 300 SREG
Conguration
Advanced settings standard tunnel preferred IP
For standard tunnel connections (before 2019) it is possible to assign each of these tunnel connections to
an IP address. In the analysis of group telegrams, this makes it easier to assign the telegrams to the sender
which „sits“ behind the tunnel, as e.g. Visualizations or smartphone apps.
iThis assignment can be resolved at any time by the ETS or a new so-called extended tunnel connection
(as of 2019).
Fig. 14: Preferred IP for Tunnelling
Function Options Description
Slow connection o󰀨/on The tunnel connections over UDP are controlled
by default with a connection timeout of
1 second. This may be too short for connections
over the Internet.
UDP connection timeout 1,0 ... 8,0 sec Setting of timeout for tunnel connection over
UDP
Preferred IP for tunnel X o󰀨/on Tunnel X should preferably be used for
communication with the parametrized IP
address.
End device IP (IP-V4 address) IP adress of end device

Page 15 of 25IPR / IPS 300 SREG
Conguration
Advanced settings routing
Fig. 15: Routing
Function Options Description
Check of topology o󰀨/on See parameter description
Enable routing algorithm
(<2018)
o󰀨/on See parameter description
Physicaladdresslter
Fig. 16: Physical address lter
Function Options Description
Physically addressed
telegrams
lter, block,
route
The physically addressed telegrams (e.g.,
actuator programming) may be routed, blocked,
or ltered via the routing. This a󰀨ects all
communication related to the device address.
Block broadcast telegrams o󰀨/on Broadcast telegrams (e.g., searching for
actuators in programming state) can be routed
or blocked through the router.

Page 16 of 25IPR / IPS 300 SREG
Conguration
Grouptelegramlter
Fig. 17: Group telegram lter
Function Options Description
IP => KNX Direction: Telegrams from the IP side to the KNX
side
Main group 0 to 13 lter, block,
route
Group telegrams can be routed, blocked or
ltered via the routing. The groups 0 to 13 are
summarized here to a block.
Main group 14 to 15 lter, block,
route
Group telegrams can be routed, blocked or
ltered via the routing. Groups 14 and 15 are
grouped together to form a block.
Main group 16 to 31 lter, block,
route
Group telegrams can be routed, blocked or
ltered via the routing. The groups 16 and 31
are here combined to form a block.
Extended group address
lter
o󰀨/on In addition to the block-oriented ltering of group
address telegrams, each group can also be
separately routed, blocked or ltered via the
routing. With this function, the parameter dialog
can be opened for this purpose.
KNX => IP Direction: Telegrams from the KNX side to the IP
side
Main group 0 to 13 lter, block,
route
Group telegrams can be routed, blocked or
ltered via the routing. The groups 0 to 13 are
summarized here to a block.
Main group 14 to 15 lter, block,
route
Group telegrams can be routed, blocked or
ltered via the routing. Groups 14 and 15 are
grouped together to form a block.

Page 17 of 25IPR / IPS 300 SREG
Conguration
Function Options Description
Main group 16 to 31 lter, block,
route
Group telegrams can be routed, blocked or
ltered via the routing. The groups 16 and 31
are here combined to form a block.
Extended group address
lter
o󰀨/on In addition to the block-oriented ltering of group
address telegrams, each group can also be
separately routed, blocked or ltered via the
routing. With this function, the parameter dialog
can be opened for this purpose.
Extendedgrouptelegramlter
Fig. 18: Extended group telegram lter
Function Options Description
Main group 00 inactive, lter,
block, forward
Group telegrams of this main group can be
routed, blocked or ltered via the routing.
If the lter is not active, the behavior of
the parameters of gure 10 and gure 11,
respectively.
Main group NN
NN = 1 ... 31
See above See above

Page 18 of 25IPR / IPS 300 SREG
Telnet
7 Telnet
Telnet is a common network protocol based on a TCP connection between a Telnet server (the device in this
case) and a client (the commissioning PC in this case).
For communication to be possible, it is necessary for the device to be administered in the network and to
be reached by the commissioning PC via IP. Settings can then be made on the device (particularly status
information) via Telnet as well as status information viewed without there being a connection to the ETS.
Telnet can either be activated as a function of the Windows operating system or used via a third party
program, e.g. PuTTY.
Telnet access is factory-protected with the password “knxsecure”.
Once the device is in secure mode, the telnet interface is disabled.
7.1 IP router and IP interface
Telnet input Description
help Displays all available commands
ifcong Displays network parameters
IP mode.......: DHCP
IP............: 192.168.33.142
Subnet mask...: 255.255.0.0
Gateway.......: 192.168.33.1
NTP server....: 192.53.103.108
Sys multicast.: 224.0.23.12
RT multicast..: 224.0.23.12
Hardware addr.: 00:50:c2:79:3f:
Sys multicast: Multicast address for System telegrams
RT multicast: Multicast address für routingt telegrams
ifcong
[help|dhcp|ip |mask]
Set network parameters via the telnet interface.
Expamples:
Setting IP Addresse with DHCP:
ifcong dhcp
Statically set the IP address to 192.168.1.2 (in this case, the gateway and
mask should also be adapted, see below)
ifcong ip 192.168.1.2
Set the gateway to 192.168.1.1:
ifcong gw 192.168.1.1
Set the mask to 255.255.255.0:
ifcong mask 255.255.255.0
tpcong Shows KNX parameters
KNX bus state.: up
KNX address...: 15.15.000
Serial number.: 00-a6-00-00-00-01
tpcong [help|set] Set KNX parameters via the telnet interface.
Set the TP address to 1.1.0:
tpcong set 1.1.0
progmode [0|1] Query or change programming mode (0 = o󰀨, 1 = on)
apdu [55..248] Read or congure the maximum length of the KNX TP telegrams. This may be
necessary if there is an incorrect implementation of a TP stack. In that case
the ETS may try to use telegrams with 248 bytes payload, but the TP device
can not process (e.g. Zennio Z35i). Default is 248 and should only be changed
if necessary.
# apdu
maximal len of a KNX telegram 248.
Usage: apdu [55 .. 248]

Page 19 of 25IPR / IPS 300 SREG
Telnet
Telnet input Description
tpratemax [5..50] Read or congure maximum telegram rate (IP => TP); 50 T / s corresponds to
100% bus load.
# tpratemax
no limit, sending with maximum performance to TP.
Usage: tpratemax [5 .. 50]
stats Shows various statistics on device and bus status
uptime: 114 days, 2:19
KNX communication statistics:
TX to IP (all)..: 333729 (ca. 233 t/m)
TX to KNX.......: 23244 (ca. 16 t/m)
RX from KNX.....: 94559 (ca. 66 t/m)
Overow to IP..: 0
Overow to KNX.: 0
TX tunnel re-req: 260
TP bus voltage..: 28.95 V
TX TP rate......: 50 T/s (= 100 %)
Uptime: Runtime of the interface since last restart
TX to IP (all): Number of all telegrams sent on IP
TX to KNX: Number of all telegrams sent on KNX
RX from KNX: number of telegrams received from the KNX bus
Overow to IP: Number of telegrams that could not be sent to IP
Overow to KNX: Number of telegrams that could not be sent to the KNX bus
TX tunnel re-req: Number of telegrams that had to be repeated in the tunnel
connections
TP bus voltage: Current bus voltage (at the time of calling stats)
TX TP rate: maximum telegram rate (TP)
free [clear] Shows statistics about the memory usage
Used stack memory...: 14 %
Allocated memory....: 64 %
Unused memory.......: 35 %
TP-Tx buer........: 0 %
TP-Tx buer max....: 0 %
TP-Rx buer max....: 0 %
Tunnel-T8 buer max: 92 %
Used stack memory: Function stack utilization
Allocated memory: Allocated device memory
Unused memory: Unused device memory
TP-Tx bu󰀨er: Currently used TP send bu󰀨er
TP-Tx bu󰀨er max:Max. Utilization of TP send bu󰀨er (IP => TP) since system
startup
TP-Rx bu󰀨er max:Max. Utilization TP receive bu󰀨er (IP <= TP) since system
startup
Tunnel-XX (XX=1..8) bu󰀨er max:Max. Utilization of the tunneling bu󰀨er. Only
tunnels whose bu󰀨er was used at all will be displayed
Clear the bu󰀨er statistics:
free clear

Page 20 of 25IPR / IPS 300 SREG
Telnet
Telnet input Description
tunnel [1..8] Shows active tunnel connections (without argument) or detailed information
about the specied tunnel connection (with argument 1..8)
# tunnel
Tunnels open: 1/8
1: 00.02.246, closed
2: 00.02.247, open (CCID: 82)
3: 00.02.248, closed
4: 00.02.249, closed
5: 00.02.250, closed
6: 00.02.251, closed
7: 00.02.252, closed
8: 00.02.253, closed
# tunnel 2
Tunnel 2..................: open (CCID 82)
KNX address...............: 00.02.247
HPAI control..............: 192.168.22.252:4808
HPAI data.................: 192.168.22.252:4808
Connect. type.............: TUNNEL_CONNECTION
Communication.............: UDP CONNECTION
TX tun req................: 23169
TX tun re-req.............: 0
RX tun req................: 821
RX tun re-req (identied): 0
RX tun req (wrong seq.)...: 0
Current tunnel buer.....: 0 %
Connected since (UTC).....: 16:26:16 29-01-2019
CCID: Connection ID of the tunnel connection
KNX address: Tunneling address
HPAI control: Control endpoint of the connection partner
HPAI data: Data endpoint of the connection partner
Connect. Type:Connection type tunnel or management connection
Communication: UDP or TCP Connection
TX tun req: Number of telegrams sent to the tunnel connection
TX tun re-req: Number of telegrams that had to be repeated in the tunnel
connections
RX tun req: Number of telegrams received from the tunnel connections
RX tun re-req: Number of telegrams received twice by the tunnel connections
RX tun req (wrong seq.):number of frames received from the tunnel
connections with wrong sequence number
Current tunnel bu󰀨er: Utilization currently of the IP bu󰀨er of the tunnel
Connected since (UTC): Time since the tunnel connection has been
established.
version Firmware version
mask Mask version
display [0|1] Query or change the display mode (0 = standard, 1 = inverted)
tunaddr 1..8 address
tunaddr reset
tunaddr setall
tunaddr help
KNX address of a tunnel read (tunaddr) or change, e.g. tunaddr 1
15.15.240, set all tunnel addresses consecutively from a certain start
address (tunaddr setall 15.15.15), or reset the KNX addresses of all
tunnels to factory settings (tunaddr reset)
# tunaddr
1: KNX address: 15.15.010
2: KNX address: 15.15.011
3: KNX address: 15.15.012
4: KNX address: 15.15.013
5: KNX address: 15.15.014
6: KNX address: 15.15.015
7: KNX address: 15.15.016
8: KNX address: 15.15.017
tunmode [std/tpblk] Read tunnel mode (without parameters) or set (tp or tpblk);
tunmode tpblock:
IP => KNX If same backbone forward to line frame
KNX => IP If same sub line send to backbone