MDT Technologies SCN-IP100.03 User manual

MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
State 12/2020 Version 1.1
Technical Manual
MDT IP Router
SCN-IP100.03
Further Documents :
Datasheets :
https://www.mdt.de/EN_Downloads_Datasheets.html
Assembly and Operation Instructions :
https://www.mdt.de/EN_Downloads_Instructions.html
Solution Proposals for MDT products:

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
2
2
1 Contents
1 Contents ............................................................................................................................................... 2
2 Overview.............................................................................................................................................. 5
2.1 Possible applications IP-Router..................................................................................................... 5
2.2 Possible applications E-Mail Client .............................................................................................. 5
2.3 Possible applications Timeserver .................................................................................................. 5
2.4 Overview LEDS & Operation....................................................................................................... 6
2.5 Commissioning without Data Secure............................................................................................ 7
2.6 Commissioning with Data Secure................................................................................................. 8
2.7 Firmware Update........................................................................................................................... 9
2.8 Topology ..................................................................................................................................... 10
2.8.1 Line coupler.......................................................................................................................... 10
2.8.2 Area coupler......................................................................................................................... 11
2.8.3 Mixed use............................................................................................................................. 12
2.8.4 Bus access function (KNXnet/IP Tunneling)....................................................................... 13
2.8.5 Installation - Example........................................................................................................... 13
3 Safety –IP Secure/Data Secure.......................................................................................................... 14
3.1 Safety mechanisms –IP Secure/Data Secure.............................................................................. 14
3.2 Basic terms.................................................................................................................................. 14
3.2.1 FDSK.................................................................................................................................... 14
3.2.2 Secured Mode - Secure Mode .............................................................................................. 14
3.2.3 Non-secured mode - Plain Mode.......................................................................................... 14
3.2.4 Backbone Key ...................................................................................................................... 14
3.2.5 Commissioning Password .................................................................................................... 15
3.2.6 Authentication Code............................................................................................................. 15
3.2.7 Commissioning/ Secure Commissioning ............................................................................. 16
3.2.8 Tunneling/Secure Tunneling................................................................................................ 16
3.3 Mixed operation .......................................................................................................................... 17
3.4 Commissioning............................................................................................................................ 17
3.5 Advanced security mechanisms .................................................................................................. 19
3.6 Requirements for KNX IP Secure/Data Secure........................................................................... 19
4 Settings –IP-Router ........................................................................................................................... 20
4.1 Settings IP Router with Secure.................................................................................................... 20
4.1.1 General ................................................................................................................................. 20
4.1.2 Device –Settings.................................................................................................................. 22
4.1.3 Device –IP Configuration.................................................................................................... 23

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
3
3
4.2 Settings IP Interface without Secure ........................................................................................... 24
4.2.1 General ................................................................................................................................. 24
4.2.2 IP Configuration................................................................................................................... 25
4.3 Example of assigning IP addresses.............................................................................................. 26
4.4 KNX Multicast Address.............................................................................................................. 27
4.5 Main line...................................................................................................................................... 28
4.6 Sub line........................................................................................................................................ 30
4.7 Communication settings.............................................................................................................. 32
4.7.1 Procedure ETS 4................................................................................................................... 32
4.7.2 Procedure ETS 5................................................................................................................... 34
4.7.3 Set tunneling connections..................................................................................................... 35
4.7.3.1 Procedure for IP Router without Secure........................................................................ 35
4.7.3.2 Procedure for IP Router with Secure............................................................................. 36
5 Parameter –> E-Mail Client ............................................................................................................... 37
5.1 General Settings .......................................................................................................................... 37
5.1.1 General ................................................................................................................................. 37
5.1.2 Web Interface....................................................................................................................... 38
5.1.3 Time/Date............................................................................................................................. 39
5.2 E-Mail Functions......................................................................................................................... 40
5.2.1 Status elements..................................................................................................................... 40
5.2.2 Bit Alarms ............................................................................................................................ 42
5.2.2.1 Macros........................................................................................................................... 43
5.2.3 Text Alarms.......................................................................................................................... 44
5.2.4 Status Reports....................................................................................................................... 45
5.2.5 Specific behavior and error handling ................................................................................... 46
5.3 Overview Communication Objects ............................................................................................. 47
5.4 Secure Group Address Communication...................................................................................... 48
6 Web-Interface..................................................................................................................................... 49
6.1 Call of the Web-Interface............................................................................................................ 49
6.2 Overview Web-Interface............................................................................................................. 50
6.3 Settings of E-Mail functionality.................................................................................................. 51
6.4 E-Mail –Error codes & remedy.................................................................................................. 54
6.5 Receive E-Mail as push message ................................................................................................ 54
6.6 Receive E-Mail as SMS .............................................................................................................. 54

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
4
4
7 Index................................................................................................................................................... 55
7.1 Register of illustrations ............................................................................................................... 55
7.2 List of tables................................................................................................................................ 56
8 Attachment ......................................................................................................................................... 57
8.1 Statutory requirements ................................................................................................................ 57
8.2 Disposal routine........................................................................................................................... 57
8.3 Assemblage ................................................................................................................................. 57
8.4 History......................................................................................................................................... 57

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
5
5
2 Overview
The MDT IP Router, SCN IP100.03, has 2 parallel applications.
On the one hand there is the application for the IP Router which allows access to the bus via Ethernet.
The second application is on the TP side and can send by KNX triggered emails, serve as a time server
and provides access to the device via a Web Interface.
Important: As these are 2 different applications, both applications must be programmed
independently. The IP Router must get 2 physical addresses!
Specifics:
Use as a time server
Extensive email functionality with status information from the KNX bus
Supplied completely from the KNX bus, no additional power supply required!
IP Secure for Interface application
Data Secure for the email application
2.1 Possible applications IP-Router
The MDT IP Router connects the KNX bus with an Ethernet network. Through the network, KNX
telegrams can be sent to other devices or received from. For communication, the device uses the
KNXnet / IP protocol of the KNX Association. It thus operates as a programming interface and
replaces a RS232 or USB interface.
The IP Router includes apart from the tunneling function for point-to-point connection additionally
the function of a line coupler (routing). This allows the IP Router to send/receive telegrams
throughout the network to/from other lines and areas.
The power is supplied via the KNX bus.
Please note: Only the group monitor is supported in the ETS, not the bus monitor.
The bus monitor requires an IP interface or a USB interface.
The IP router protocol does not support the bus monitor according to KNX specification.
2.2 Possible applications E-Mail Client
The email client can emit status reports, bit alarms and text alarms. All email events can be triggered
via KNX telegrams. In addition, status reports can also be sent at fixed times - the email client has the
functionality to work as a clock-master. All e-mails can be sent to up to 3 addresses simultaneously.
The settings of the e-mail functionality can be carried out comfortably via the web interface.
2.3 Possible applications Timeserver
The IP Router receives the date and time of the NTP server and can distribute them as the "master"
to further KNX devices via the bus.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
6
6
2.4 Overview LEDS & Operation
The figure below shows the structure of the device and the location of the LEDs:
1. LED Bus State - LAN
2. LED Bus State - KNX
3. LED Traffic - LAN
4. LED Traffic - KNX
5. Routing of group telegrams
6. Routing of physical addressed telegrams
7. Function button
8. Programming LED
9. Programming button
Figure 1: Structure –Hardware module
Functionality of the Programming-button:
Short press: programming LED lights steadily red -> IP interface is in the programming mode
Long press: programming LED flashes red -> E-Mail client is in the programming mode
Functionality of the Function-button:
Press the button for 3 seconds: IP router is set to “manual”with functionality according to the
settings in the menu "General". By repeated pressing of the function button for 3 seconds, the router
is switched back.
Reset device:
If, for example, the applications are loaded in the wrong order or you want to switch from "Secure"
to "without Secure", the IP interface must be reset.
Otherwise, programming errors may occur.
The procedure is as follows:
- Press the function button for at least 15 seconds, the LEDs 1, 2, 5, 6 lights up red/orange.
- Now release the function button (LEDs continue to light up as before).
- Now press the function button again for at least 3 seconds until all LEDs go out.
- The unit restarts. In the ETS it disappears under "Discovered interfaces".
Shortly afterwards it appears again with the default address (IP Router 15.15.0).
The unit is now reset to factory settings.
The master reset also resets the secure settings to the FDSK (Factory Default Setup Key). This means
that the device can only be downloaded with the FDSK

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
7
7
Green
Red
LED 1
Bus State - LAN
Off: LAN Error
On: LAN OK
On: Manual Mode active
LED 2
Bus State - KNX
Off: KNX Bus: Error or not connected
On: KNX Bus OK
LED 3
Traffic - LAN
Flashing: Bus load at LAN-side
Off: No Bus load at LAN-side
Speed up to 10 Mbit/s
Flashing: Transmission error at LAN
side
LED 4
Traffic - KNX
Flashing: Bus load at KNX side
Off: No Bus load at KNX side
Flashing: Transmission error at KNX
side
LED 5
Forwarding of
group telegrams
Forwarding of group telegrams
- Off: LAN and KNX different
- Filter table activ
Lock
Green and Red: forwarding all
LED 6
Forwarding of
physical addresses
Forwarding of physical addresses
- Off: LAN and KNX different
- Filter table activ
Yellow: Lock
Green and Yellow: forwarding all
Table 1: Overview LEDs
2.5 Commissioning without Data Secure
The following procedure is recommended for commissioning the SCN-IP100.03:
1. Insert the application „SCN-IP000.03 –KNX IP Router“
2. Configuration of the IP-Router:
3. Transfer of the physical address and the application of the IP Router. For this, the
programming button must be pressed shortly. The programming LED lights steadily red.
4. After successful transfer of the physical address and the application, the red LED turns off
again.
5. Insert the application „SCN-IP000.03 –KNX IP Router with email function“
6. Configuration of the E-Mail Client:
7. Transfer of the physical address and the application of the E-Mail Client. For this, the
programming button has to be pressed long. The programming LED flashes red.
8. After successful transfer of the physical address and the application, the red LED turns off
again.
9. Accessing the Web client to configure the e-mail addresses by opening an Internet browser
and call the address: http:\\IP address: port, for example: http: \\192.168.1.178:8080 for the
IP address 192.168 .1.178 and the http port 8080
Important: If the IP address of the IP Router gets changed subsequently, the device must perform a
reboot. This restart is not performed automatically by the application programming in the ETS4/5.
Here, a manual restart will be required, which either by right-clicking on the device and selecting
"Reset device" is executed or a short removing of the bus connector.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
8
8
2.6 Commissioning with Data Secure
The following procedure is recommended for commissioning the SCN-IP100.03:
1. Insert the application „SCN-IP100.03 –KNX IP Router with Secure“
2. Input of the FDSK (see sticker on the side of the device)
3. Configuration of the IP Router.
4. Transfer of the physical address and the application of the IP Router. For this, the
programming button has to be pressed shortly. The programming LED lights steadily red.
5. After successful transfer of the physical address and the application, the red LED turns off
again.
6. Insert the application „SCN-IP000.03 –KNX IP Router with email function“
7. Input of the FDSK (see sticker on the side of the device)
8. Configuration of the E-Mail Client.
9. Transfer of the physical address and the application of the E-Mail Client. For this, the
programming button has to be pressed long. The programming LED flashes red.
10. After successful transfer of the physical address and the application, the red LED turns off
again.
11. Accessing the Web client to configure the e-mail addresses by opening an Internet browser
and call the address: http:\\IP address: port, for example: http: \\192.168.1.178:8080 for the
IP address 192.168 .1.178 and the http port 8080
FDSK Info: The IP Router has two FDSK (Factory Default Setup Key), one for each application.
Therefore you will find two different keys on the right and left side of the interface.
Important: By deactivating "Secure commissioning" in the properties -> settings of the device, the
device is operated "unsecure", i.e. in "plain mode". If you are prompted to enter the FDSK of the
device, you can skip this dialog by clicking the "Later" button. Data Secure/IP Secure can also be
activated later by activating "Secure commissioning" and the FDSK is present.
Further details about IP Secure/Data Secure can be found at “3 Safety –IP Secure/Data Secure”

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
9
9
2.7 Firmware Update
If there is a new firmware version for the IP Router, the update can be carried out directly on the
device.
The required update file is available in "hex" format in the download area.
Link to the firmware files (Current devices):
https://www.mdt.de/EN_Downloads_Productdata.html
The firmware update itself is performed via the web browser:
A detailed description with procedure is available as a solution proposal at
Important:
After an update, the unit is reset to factory settings. The physical address and application have to
be reloaded!
Also, all settings in the web browser such as e-mail addresses etc. are reset to default settings.
Therefore, make a note of the entered addresses etc. in advance.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
10
10
2.8 Topology
2.8.1 Line coupler
The following figure shows the IP router as line coupler:
Figure 2: IP Router as line coupler
The IP Router in KNX installations can assume the function of a line coupler. For this it needs to get
the physical address of a line coupler (1.1.0 ... 15.15.0). Currently, in an ETS project up to 225 lines
can be applied.
This topology is described as a flat topology as there are KNX main- or backbone lines. The telegrams
of the KNX line are transmitted directly to the Ethernet

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
11
11
2.8.2 Area coupler
The following figure shows the IP router as an area coupler:
Figure 3: IP Router as area coupler
In larger KNX installations the IP router can assume the function of an area coupler. For this it needs
to get the physical address of an area coupler (1.0.0 ... 15.0.0). Currently, in an ETS project up to 15
areas can be applied with area couplers.
In the above example each area got 2 subordinated lines, which e.g. can be linked with the line
coupler SCN LK001.01.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
12
12
2.8.3 Mixed use
The following figure shows the IP router as area coupler (IP Router 1.0.0.) and line coupler
(IP Router 2.1.0):
Figure 4: IP Router as area- and line coupler
Is it within a KNX system needed to use the IP Router at one location e.g. an Office as an area coupler
and elsewhere, e.g. a distant building as a line coupler, so two different IP Routers can assume this
function.
It needs to be noted that the IP Router as a line coupler gets the physical address from an open area,
such as shown in picture above 2.1.0.
The IP router as an area coupler (1.0.0) can get further lines subordinated

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
13
13
2.8.4 Bus access function (KNXnet/IP Tunneling)
The KNX IP Router can be used as an interface to KNX. It can be accessed from anywhere on the LAN
to the KNX. Therefore a second physical address has to be allocated. This is described in more detail
in the following chapters.
2.8.5 Installation - Example
The following figure shows the exemplary structure of a network with two IP Routers used in each
case as an area coupler:
Figure 5: Installation example

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
14
14
3 Safety –IP Secure/Data Secure
3.1 Safety mechanisms –IP Secure/Data Secure
KNX Data Security distinguishes between two mechanisms: IP Secure and Data Secure.
KNX IP Secure allows to encrypt and to authenticate messages sent by KNX devices to transmit them
securely over the IP layer. This ensures that KNX tunneling or routing messages on IP cannot be read
or manipulated. KNX IP Secure forms an additional "security shell" that protects the complete
KNXnet IP data traffic.
KNX Data Secure enables the secure commissioning of devices that support data security and the
encrypted transmission of group addresses between two devices that support Data Secure.
For 2 devices to communicate securely with Data Secure, both devices must support Data Secure.
However, it is also possible for a Data Secure device to communicate with a device that does not
support Data Secure. In this case, however, only via an unsecured connection.
3.2 Basic terms
3.2.1 FDSK
Every Secure device is delivered with the "Factory Device Setup Key" (FDSK). The system
integrator/installer enters this key into the ETS, which generates a device-specific tool key from it.
The ETS sends the tool key via the KNX bus to the device to be configured. This transmission is
encrypted and authenticated with the FDSK key. After this initial commissioning, the device only
accepts the received tool key. The FDSK is no longer required for further transmission - unless the
device is reset via the master reset.
After initial commissioning, the FDSK of all devices in a project should be detached from the device
sticker and stored in a project-specific manner. The IP interface has two FDSKs for each application
one, therefore you will find two different keys on the right and left side of the interface.
3.2.2 Secured Mode - Secure Mode
If a device is parameterised in such a way that it only transmits encrypted data, this is known as
secure mode.
3.2.3 Non-secured mode - Plain Mode
If a device is parameterised in such a way that it only transmits in unencrypted form, this is known as
non-secured mode (plain mode).
3.2.4 Backbone Key
If a KNX bus is connected to Data Secure via 2 IP Routers, they communicate encrypted with the
backbone key. This key must be identical in all devices. The key is assigned independently by the ETS
and cannot be changed.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
15
15
3.2.5 Commissioning Password
The commissioning password is required in the ETS for the entire process/download during
commissioning / device security of a KNX IP Secure device. It is also used to authenticate the ETS to
the device.
It has to be different from passwords of possible secured, additional interfaces and represents the
so-called management level for the device configuration by the ETS.
Only the ETS itself knows the commissioning password and can make changes to the device.
Passwords of secured additional interfaces can be distributed, e.g. to an external visualisation.
The commissioning password can be adapted by the user and is visible in the tab “Device ->
Properties -> IP”:
Figure 6: Commissioning Password/ Authentication Code
It is recommended to give each device an individual commissioning password and not a universal one
in the entire project or even across projects. The ETS automatically assigns an individual password.
3.2.6 Authentication Code
The authentication code is required for authenticating KNX IP Secure devices.
As the FDSK is known outside of ETS, for example as QR Code or imprint on the device, this key has to
be changed in the ETS project.
The FDSK is replaced by an individual authentication code for this ETS project and this KNX IP Secure
device. Subsequent communication of the device with the ETS will then be done with this (new)
authentication code (instead of the initial FDSK).
Each KNX IP Secure device therefore has an individual* authentication code after commissioning
which is different from the initial FDSK.
* if not overwritten by the ETS user - in case of multiple devices - with an identical authentication
code
The authentication code can be changed in ETS in the same way as the commissioning password, see
Figure 2 above.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
16
16
3.2.7 Commissioning/ Secure Commissioning
It can be decided for each device whether commissioning should be carried out in a secure or
unsecured manner. If the commissioning is not secured, the device can be used as a normal device
without Data Secure.
By default, the ETS sets all devices to Secure commissioning when inserted. This item can be changed
by the user under Device ->Properties ->Settings:
Figure 7: Secure Commissioning/Secure Tunneling
3.2.8 Tunneling/Secure Tunneling
Tunneling refers to a KNX point-to-point connection on the TCP/IP network. For each IP Secure
device, it can be decided whether the tunneling connections are transmitted "Secure" or "Plain", see
Figure 3 above.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
17
17
3.3 Mixed operation
IP Secure
Secured devices can only communicate with devices that are also secured. Mixtures of e.g. secured
KNX IP Secure couplers with unsecured KNX IP Secure devices or normal KNX IP devices will not work.
Data Secure
With Data Secure, devices that support Data Secure can also communicate with devices that do not
support Data Secure. A mixed operation in one project is therefore possible.
However, if all data of a group address are to be transmitted in encrypted form, all devices whose
objects are connected to this group address must support Data Secure.
3.4 Commissioning
ETS requires the following procedure to put Secure devices into operation:
1. Load product data
When loading the product database, you will normally be asked directly to enter the FDSK of
the device:
Figure 8: Enter FDSK
You can enter the FDSK manually or read the QR code from a camera. If you do not want to
read the FDSK directly or if you do not have it at hand, you can do this later by confirming
this dialogue with "Later".

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
18
18
To enter the FDSK later, select the respective project and choose the tab Security:
Figure 9: Subsequent input FDSK
Here you can now select the "Add" button and enter the FDSK or scan the QR Code. If the
FDSK was detected correctly, the ETS decodes the FDSK into serial number and factory key.
The ETS automatically assigns which key belongs to which device. Thus, you can simply enter
all FDSK used in the project one after the other.
2. Remove sticker/device certificate
To prevent sabotage, the device certificate has to be kept in a safe place. It is therefore
important to remove it before installing the device and keep it for the project.
3. Adapt Commissioning Password/Authentication Code (optional)
The Commissioning Password per device and Authentication Code per device can now be
customized by the user. However, the ETS assigns initial passwords, so this does not
necessarily have to be done. However, individual passwords should be assigned for each
device.
4. Download the application
Now the application can be downloaded into the device.
5. Distributing the Commissioning Password and Authentication Code
If visualisation or remote access is required, the commissioning password and (optionally)
the authentication code (authorisation of the other party for access to the project) need to
be entered before the connection is established.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
19
19
3.5 Advanced security mechanisms
In addition to the use of KNX IP Secure, the following guidelines should be taken into account during
planning:
Do not allow any ports of routers to access the Internet
Secure LAN/WLAN system via a firewall
If no external access to the KNX installation is required, the default gateway can be set to the
value 0. This prevents communication to the Internet.
Access to the KNX installation from the Internet should be realised via a VPN connection
3.6 Requirements for KNX IP Secure/Data Secure
ETS 5.7.2 is required for commissioning Data Secure/IP Secure.

Technical Manual –IP Router SCN-IP100.03
MDT technologies GmbH • 51766 Engelskirchen • Papiermühle 1
Tel.: [phone] • Fax: [phone] • [e-mail] • www.mdt.de
20
20
4 Settings –IP-Router
The settings of the application "IP Router without Secure" and "IP Router with Secure" differ. Both
settings are described below.
4.1 Settings IP Router with Secure
4.1.1 General
The following parameters can be set in the submenu "General":
Figure 10: General Settings –IP Router
The table below shows the settings for this submenu:
ETS-Text
Dynamic Range
[Default value]
Comment
Enable slow connections
yes
no
Adjust the timeout for tunneling
connections. By default, slow
connections are not supported
and a short timeout is used for
the UDP connection. This can be
increased by supporting slow
connections which may be
necessary especially for tunnel
connections over the internet.
Manual Function
disabled
pass all telegrams
pass all physical telegrams
pass all group telegrams
Defines the behavior after
manual changeover
Switch-off time for
Manual Function
10 min
1 hour
4 hours
8 hours
Setting of the automatic release
time from manual mode to
automatic mode