Mean Well KSR-01IP Instruction Manual

KSR-01IP

KNX IP Router

Instruction manual

KSR-01IP Instruction Manual

Content

1.Product Description

2.KNXnet/IP

3.Operational Description

1.1 Front Panel

2.1 IP Tunnelling

3.1 IP Coupler Application

3.2 IP Network

3.3 KNX Network Installation

3.4 Programming

3.5 Function Button

3.4.1 Program Button

3.4.2 PhysicalAddress Assignment

3.5.1 Manual Function

3.5.2 Factory Reset

3.5.3 Boot Mode Activation

3.5.4 LED Status Display

2.2 IP Routing

2.3 IP Bootloader / Boot Mode

1.2 LED Indication

1.3 Commissioning

1.4 Feature Summary

..............................................................................

.............................................................................................

........................................................................

.....................................................................................

...................................................................................

.....................................................................

......................................................................................

................................................................

..................................................................................

...............................................................................

......................................................................

................................................

.....................................................................

.........................................................................

..............................................................

.................................................................

.......................................................................................

..............................................................

................................................................................

...............................................................................

............................................................................

1

4

5

1

4

5

5

6

7

8

7

8

8

9

9

10

4

4

2

2

3

Aug. 2018 Version 0

KSR-01IP Instruction Manual

Content

5.WEB Front-End

6.State of Delivery

7.FAQ

5.1 Accessing the KSR-01IP Web Front-End

5.2 Device Info

5.3 KNX

5.4 (Firmware) Update / Boot Mode

5.5 IP Tunnelling Address Assignment

6.1 Default Factory Setting

6.2 Technical Datasheet

6.3 Technical Drawings

5.1.1 via Windows Network UPnP

5.1.2 via IP Address

5.1.3 via MAC Address

.....................................................................................

....................................................................................

......................................................................................................

........................................

......................................................................................

.................................................................................................

......................................................

..................................................

...................................................................

.......................................................................

.........................................................................

....................................................

.........................................................................

.....................................................................

16

23

25

16

18

19

19

21

23

24

24

16

17

17

4.ETS Database Parameters

4.1 General

4.2 IP Configuration

4.3 KNX Multicast Address

4.4 Main Line (IP)

4.5 Subline (KNX TP)

................................................................

.....................................................................................

........................................................................

..............................................................

............................................................................

......................................................................

10

10

11

12

13

14

1

1.Product Description

The KNX IP Router KSR-01IP works as a KNX line/area coupler to provide a bi­directional data connection between KNXnet/IP line (main line) and KNX TP line
(subline). KNX IP and KNX TP are coupled having a galvanic isolation in between.
The flexible KSR-01IP can be used as a KNX TP line coupler to connect several KNX
TP lines but also as a KNX TP area coupler to connect several TP areas or different
KNX TP installation systems via an IP Backbone/Ethernet/Internet. Telegram
filtering is accomplished according to the installation place in the hierarchy
(Physical Telegrams) and according to the built in filter tables for group
communication (Group Telegrams). For detailed diagnosis all operational
modes/states are shown by a duo-LED display.

With the ETS (or compatible commissioning tool) KSR-01IP also works as the KNX
programming interface having no KNX communication objects for itself. Connecting
a personal computer to the KNX TP bus can ideally be done via Ethernet/Internet.
For Tunnelling and Routing up to four tunnelling addresses can be used. To ease
commissioning and troubleshooting the Manual Function for short-time telegram
filter switch-off and special routing/repetition/confirmation settings are available. A
comfortable Web front-end to watch the busload history, to identify KSR-01IP in a
network and to update the firmware via IP is provided.

Note: In this document, physically addressed telegrams are named Physical
Telegrams Note: In this document, group oriented telegrams are named Group
Telegrams.

1.1 Front Panel

Figure 1: Front View

Front Panel Elements :

+

-

+

-

KSR- IP01

KNX IP Router

I

Function

Bus State

IP TP

Traffic

GA PA

Prog.

MEUADE IN

A1

A3

A5

A7

A2

B1

A4

A6

B2

B3

B4

A1: State IP (Main line)

A3: Telegram traffic IP(Main line)

A4: Telegram traffic KNX TP (Subline)

A5: Group Address routing"*"

A6: Physical Address routing

A7: Programming

B1: Ethernet connector

B2: Function button

B3: Program button

B4: KNX TPconnector

* only group telegrams with main groups 0…13

A2: Bus state KNX TP(Subline)

2

1.2 LED Indication

If KSR-01IP is used as IP Router without physical address x.y.0, LED A6 (Physical

address routing) works not like described here.

Table 1: LEDs Colors

State IP (Main line)

green: Main line OK
red: Manual Function active

Bus state KNX TP (Subline)

green: Subline OK

Telegram trafc IP (Main line)

green, blink.: Telegram trafc extent
red, blink.: Transmission error

Telegram trafc KNX TP (Subline)

green, blink.: Telegram trafc extent
red, blink.: Transmission error

Group Address routing

green: Filter active
orange: Route all
red: Block all
<off>: Main line / subline different

Physical Address routing

green: Filter active
orange: Route all
red: Block all
<off>: Main line / subline different

Programming

red: Pro gram Mo de
red, blink.: No IP connection

A1

A2

A3

A4

A5

A6

A7

1.3 Commissioning

Please note for commissioning with default settings:

● The Manual Function switch-off time is 120 min

● Physical address is 15.15.0

● WARNING: Do not connect to 230 V

Figure 2: Connection Scheme

KSR-01IP

KNX cable

Ethernet

KNX
Device

+

-

3

1.4 Feature Summary

● KSR-01IP supports extended frames and long telegrams up to 240 bytes APDU
length. With all other system devices i.e. couplers and interfaces suporting long
messages e.g. for energy metering applications and visualization purposes can be
processed.

● KSR-01IP favourably replaces a common TP line/area coupler. The great

advantage is using KNX IP as a fast KNX backbone medium (for sending telegrams
between lines and areas).

● KSR-01IP works without external power supply.

● Providing IP Tunnelling to the ETS connection interface (also other tools to enable
commissioning and monitoring) the additional tunnelling addresses are not the
same used for ETS connection. Four different tunnelling connections with a
separate address for each can be realized in parallel.

● ACK sending on sent out messages is ETS configurable.

● When there is no IACK response on the subline KSR-01IP is able to repeat
messages up to three times. Repetitions can be configured for both Physical
Telegrams and Group Telegrams via ETS (to ease troubleshooting). After an IACK
response no repetition is following and the negative IACK/BUSY failure
mechanism is maintained.

● Automatic function for switching back to run-time telegram filtering after
configurable suspension period (see Manual Mode). This avoids forgetting the
reactivation of filtering.

● For an ETS configurable time period, it is possible to switch off telegram filtering
by only pressing a button on the device front panel. Without additional ETS
download filtering is suspended. This is necessary for running fast diagnostics on
site.

● Temporarily suspending telegram filtering eases commissioning and debugging.
Without ETS download temporary access to other lines becomes possible.

● UPnP is available to discover the device within the IP network. This can only be
realized by a proper network installation in terms of topology. With use of
KNXnet/IP ETS is able to recognize the communication interface device.

● Updating the firmware can easily be accomplished by a Web browser. The
available Web front-end provides informative settings and enables to switch the
device into Program Mode without use of the Program Button.

● In networks with high busload the internal amount of communication buffers are
capable of smoothing peeks in the communication load course.

● KSR-01IP's ETS database entries are available for ETS4 and later.

● KSR-01IP supports KNXnet/IP, ARP, ICMP, IGMP, HTTP, UPnP discovery, UDP/IP,
TCP/IP, DHCP und AutoIP.

4

2.KNXnet/IP

KSR-01IP is a KNX IP router. KNX IP routers are highly similar to TP line couplers.
The only difference is that they use the IP communication medium as main line and
the KNXnet/IP communication protocol. However, KNX end devices can be
integrated directly via IP. This makes the Ethernet a real KNX medium.

As documented in the KNXnet/IP protocol specifications, KNX telegrams can also
be transmitted encapsulated in IP telegrams. Ethernet networks as well as Internet
can be used to route or tunnel KNX telegrams. In this way, IP interfaces and IP
routers are an alternative to USB data interfaces and TP line/area/backbone
couplers. In the latter case, the normal TP backbone is replaced by a fast Ethernet
based line.

2.1 IP Tunnelling

The presence of the Internet Protocol (IP) has led to the definition of the KNXnet/IP
protocol. KNXnet/IP offers the possibility for point-to-point connections for the ETS
(KNXnet/IP Tunnelling) and/or between supervisory system and KNX installation.
The KNXnet/IP device management enables KNXnet/IP device configuring via the
KNX network in order to reduce the time required for complete network
configuration.

2.2 IP Routing

IP Routing is the way of interconnecting KNX lines and areas by IP network(s) via
KNXnet/IP. In IP networks the KNXnet/IP Routing defines the way of KNXnet/IP
router communication.

2.3 IP Bootloader / Boot Mode

The IP bootloader function is used to completely rewrite the flash memory content
and is not just a simple application download. Both communication stack and
application software are downloaded. The download tool is a separate tool
independent from ETS.

The firmware update procedure via IP is executed by a Web front-end and makes
use of special messages to speed up the process. To be protected, their contents
are encrypted.

Note: Entering Boot Mode is equivalent to activating the IP bootloader function.

5

3.Operational Description

In network installations KSR-01IP can be used as KNX IP area coupler or KNX IP
line coupler. With its default settings KSR-01IP operates as is supposed to.

3.1 IP Coupler Application

When KSR-01IP receives telegrams (for example during commissioning) that use
physical addresses as destination addresses, it compares the physical addresses
of the receiver with its own physical address and decides on that whether it has to
route the telegrams or not.

When KSR-01IP receives telegrams that use group addresses as destination
addresses, it reacts in accordance with the parameter settings. During normal
operation (with default settings), KSR-01IP only routes telegrams whose group
addresses are entered in the filter table.

If KSR-01IP routes a telegram and does not receive an acknowledgement, or if a bus
device discovers a transmission error, the coupler repeats telegrams up to three
times (depending on the corresponding parameter that is set by ETS). With the
parameters „Repetitions if errors...“, this function can be set separately for each
line. It is recommended to use the default parameter setting.

IP Coupler is designed for use in 10/100 BaseT networks compliant to IEEE802.3.
The AutoSensing function sets the baud rate (10 Mbit or 100 Mbit) automatically. IP
address can be received from a DHCP server. For this, the ETS automatic
assignment setting of the IP address is required. If no DHCP server is found by this
setting KSR-01IP starts an AutoIP procedure and autonomously assigns the IP
address. The IP address that KSR-01IP receives during its start-up (via DHCP or
AutoIP) is retained until next start-up (e.g. due to power off or reprogramming). If the
IP address of the KSR-01IP is supposed to have a fixed assignment a fixed IP
address (as well as subnet mask and standard gateway) can be set by ETS.

Note: ETS does not provide an unload procedure for applications.

3.2 IP Network

KSR-01IP sends telegrams from/to the TP network to/from the IP network in
accordance with the KNXnet/IP protocol specification. According to the default
setting these telegrams are sent as multicast telegrams to the multicast IP address

224.0.23.12 port 3671. The multicast IP address 224.0.23.12 is the defined address

for the KNXnet/IP by KNX Association in conjunction with the IANA. It is
recommended to use this default address as defined. Only if it becomes necessary
due to the existing network, the address can be changed as shown in chapter 4.3
KNX MulticastAddress. Important notes:

● All KNX IP devices that are intended to communicate with each other via IP must
have the same IP multicast address.

6

● Multicast IP address 224.0.23.12 may need to be changed in respect of the
network type and of the network components´ settings.

● IGMP (Internet Group Management Protocol) is used for IP configuration to

establish multicast group belonging.

● If the IP address is changed from the IP side it may happen that ETS does no

longer recognize the device and connection cannot be maintained (tunnelling uses

IP addresses).

● It is recommended to trigger a restart and to change IP addresses only from TP
side.

● If problems occur for IP address assignment please ask your network
administrator.

● According to the topology, the Tunnelling addresses always have to be assigned in
the range of subline addresses. For more information about additional physical
addresses for tunnelling please refer to IP Tunnelling Address Assignment.

● Programming devices of another line different to which the device used for
(re)programming is connected the use of a correct topology is mandatory!

3.3 KNX Network Installation

For line coupler functionality in a KNX network KSR-01IP has to use the correct
physical address of a line coupler (X.Y.0, 1≤X & Y ≤15). In ETS up to 225 addresses
can be defined (from 1.1.0 to 15.15.0).

For area coupler functionality in a KNX network KSR-01IP has to use the correct
physical address of an area coupler (X.0.0, 1≤X≤15). In ETS up to 15 areas can be
defined.

If KSR-01IP is used in a KNX system for both purposes, it is only necessary to
ensure that the KSR-01IP used as a line coupler has a line coupler address
assigned from a free addressing area. Following figure illustrates the KSR-01IP
router topology for KNX lines and KNX areas.

7

Example: If an IP router with address 1.0.0 already exists on the backbone no IP
router with address 1.X.0, 1≤X≤15 can be added here. Even if no line coupler with
address 1.1.0 exists on the subline of the 1.0.0 IP coupler. Vice versa, if a line
coupler with address 1.1.0 already exists in the installation no IP router with address

1.0.0 can be added.

3.4 Programming

3.4.1 Program Button

To download the desired physical address or an ETS setting the Program Button
must be pressed first. Successive pressing the Program Button will turn on and off
the Program Mode. LED A7 lighting in red colour indicates Program Mode is active.
When Program Mode is active ETS recognizes the device of interest for
downloading.

Note: A blinking red Programming LED indicates the Ethernet cable is not properly
con nected.

Note: Even when Boot Mode is active successive pressing the Program Button will
turn on and off Program Mode and Programming LED.

Figure 3: KSR-01IP Network Topology

KSR-01IP KSR-01IPKSR-01IP

KSC-01LKSC-01L

SublineSubline

Mainline

IP Area

IP Backbone

TP Line

TP Area

Ethernet

+++

++++

---

----

1.0.0

1.2.01.1.0

2.0.0 3.1.0

++++

----

8

3.4.2 Physical Address Assignment

To commission the device an interface connection (IP, USB) to the KNX bus system
is required. The device is supplied with the individual physical address 15.15.0. The
KNX product database entry (available for ETS4 and higher) can be downloaded
from the Meanwell website and from the KNX Online Catalog.

With the ETS the physical address can be assigned to the device by setting the
desired address in the properties window of the ETS. After starting the ETS
download and then pressing the Program Button the device restarts itself.

Figure 4: ETS Properties Window

Note: In this document only the term “physical address” is used. The term “physical
address” means the KNX physical address as well as the ETS individual address.
Both terms are used by the KNX organisation interchangeably.

3.5 Function Button

The Function Button activates KSR-01IP ´s special functions Manual Function,
Factory Reset and Boot Mode. It depends on time/number/state the Function Button
is being pressed.

3.5.1 Manual Function

A rather short press (≈ 3 sec) of the Function Button activates the Manual Function
during normal operation. With a second short button press it can be deactivated
before the Manual Function Switch-off time is expired.

9

When the Manual Function is active either all Physical Telegrams or all Group
Telegrams or both pass the KSR-01IP without filtering. After the Switch-off time
period has elapsed KSR-01IP automatically switches back to normal operation. To
configure the Manual Function and set the Switch-off time use the parameter tab
General like shown in chapter 4.1 General. After switching back from Manual
Function to normal operation the latest downloaded parameter setting / filter table
entries are active again.

3.5.2 Factory Reset

A long press (≈ 15 sec) of the Function Button soon followed by a second press for
some seconds executes the Factory Reset. After the first press the LED display
lights different (see table 4). After the second press all parameters will be set to
factory default (incl. physical address). Subsequently, LEDs show the normal
display again.

When Boot Mode is active the Function Button executes the Factory Reset in a
different way. After pressing the Button for about five seconds the LEDs light with
green color. After second press (about two seconds) the parameters will be set to
factory default (incl. physical address) and LEDs again display Boot Mode is on.

Note After a factory reset executed in Boot Mode the KSR-01IP stays in Boot Mode.

3.5.3 Boot Mode Activation

For Boot Mode activation the firmware update process must be executed. During the
process, the Function Button must be pressed to enter Boot Mode (see chapter 5.4).

Figure 5: Boot Mode is active

10

3.5.4 LED Status Display

Table 2: LED Status Display for Manual Function

Table 3: LED Status Display for Factory Reset after first Button Press

Table 4: LED Status Display for Boot Mode

4.ETS Database Parameters

All screen shots are related to the KSR-01IP database file R2-1g in ETS5.

4.1 General

If the host name is changed by a download in ETS4, a manual device restart (bus
disconnection, reset of the line) is recommended to take over this change.

Figure 6: General Tab Parameters

Number

Number

Number

LED

LED

LED

Color

Color

Color

Comment

Comment

Comment

A1

A1

A1

State IP

State IP

State IP(Main line)

orange

orange

green

orange

blinking green

blinking green

green

orange

orange

orange

orange

red

Lights red if not connected

Lights red if not connected

not the same tempo as LEDA2

Bus State KNX TP

Bus State KNX TP

State KNX TP(Subline)

Group Address Routing

Group Address Routing

Telegram Traffic IP(Main line)

Physical Address Routing

Physical Address Routing

Programming

A2

A2

A2

A5

A5

A3

A6

A6

A7

11

Table 5: General Tab Parameter Settings

Table 6: IP Configuration Tab Parameter Settings, DHCP on

4.2 IP Configuration

After an ETS download IP addresses are not updated. It is essential to execute a
manual device restart (bus disconnection, reset of the line) to get IP configuration
data updated.

Figure 7: IP Configuration Tab Parameters, DHCP on

Figure 8: IP Configuration Tab Parameters, DHCP off

Figure 9: KNX Multicast Address Tab Parameters, System Multicast on

Table 7: IP Configuration Tab Parameter Settings, DHCP off

4.3 KNX Multicast Address

For KNXnet/IP the multicast address 224.0.23.12 is the defined address from KNX
Association in conjunction with IANA. Change this address only if it becomes
necessary due to the existing network. Make sure that during commissioning all
KNX IP devices intended to communicate with each other via IP use the same
multicast address. After downloading a new multicast address a manual restart has
to be executed.

12

13

Table 8: KNX Multicast Address Tab Parameter Settings, System Multicast on

Table 9: KNX Multicast Address Tab Parameter Settings, System Multicast off

4.4 Main Line (IP)

For Group Telegrams and Physical Telegrams the setting “transmit all” is intended
only for testing purposes. Please do not use for normal operation.

Figure 10: KNX Multicast Address Tab Parameters, System Multicast off

Figure 11: Main Line (IP) Tab Parameters

14

Table 10: Main Line (IP) Tab Parameter Settings

4.5 Subline (KNX TP)

For Group Telegrams and Physical Telegrams the setting “transmit all” is intended
only for testing purposes. Please do not use for normal operation.

Figure 12: Subline (KNX TP) Tab Parameters

15

Table 11: Subline (KNX TP) Tab Parameter Settings

16

5.WEB Front-End

The Web front-end can be used to readout KSR-01IP ´s actual device parameters
(HTTP port, IP address, MAC address, …), to update its firmware and to adjust the
(additional) tunnelling addresses. To identify a particular KSR-01IP of a KNX
network the Programming LED/Program Mode can be remotely switched on without
pressing the Program Button.

Note:To switch back from Boot Mode to normal operation it is necessary to run the
firmware update procedure.

5.1 Accessing the KSR-01IP Web Front-End

There are three ways to access the KSR-01IP. It can be accessed like a Microsoft
Windows UPnP network device (Windows7 or later) and by a web browser. For
access by a web browser either the IP address or the MAC address, together with
the HTTP port, have to be known. How to use IP address and MAC address with the
browser´s URL bar is described in the following.

Note: For access via web browser the HTTP port that is set by ETS (or the factory
default parameter value) has to be used.

Note: KSR-01IP is able to use both official HTTP system ports (80 and 8080).

Note: Factory default HTTP port is 8080.

5.1.1 via Windows Network UPnP

Figure 13: KSR-01IP as UPnP network device (“KNX TP IP”)

When the UPnP network function is enabled, KSR-01IP appears in the Windows
Network. A click on the KSR-01IP network device opens the Web front-end with the
standard web browser. If KSR-01IP is not visible as an UPnP network device a
manual restart is recommended. After that, the device becomes visible in the list of
network devices.

17

5.1.2 via IP Address

When IP address and HTTP port (80 or 8080) are known, this information is
sufficient to access the KSR-01IP Web front-end by a web browser. The actual IP
address is shown in the ETS list of Discovered Interfaces.

According to KSR-01IP ´s pre-set IP configuration (HTTP port, IP address and
DHCP, respectively) in the URL bar has to be entered (without brackets):

Example1: DHCP is not used. With the latest ETS download the IP address was set
to 192.168.1.32 and HTTP port was set to 80. In the browser´s URL bar has to been
tered http://192.168.1.32:80/”.

Example2: With the latest ETS download HTTP port was set to 8080 and DHCP was
activated.

The DHCP server assigned a free IP address to KSR-01IP and ETS shows this IP
address to be 192.168.1.201. In the browser´s URL bar has to be entered
“http://192.168.1.201:8080/”.

5.1.3 via MAC Address

When NetBIOS is installed (by default on Windows systems and Linux systems
containing SAMBA) the MAC address that is printed on a label on the side of the
KSR-01IP housing can be used. Due to name resolution is mandatory to establish
communication by Host name, activation of NetBIOS is necessary.

Use the MAC address in the form of AA-BB-CC-XX-YY-ZZ and the pre-set HTTP port
to be entered in the browser´s URL bar as described here (without brackets):

Figure 14: Identifying KSR-01IP ´s IP address with ETS

18

Example: On the housing side KSR-01IP is labelled with MAC address D0-76-50-11­22-33 and the pre-set HTTP port is 8080. Then, in the web browser´s URL bar has to
be entered “http://knx-iprt-112233:8080/”.

5.2 Device Info

After accessing the Web front-end the Device Info tab is shown. All general
information about the current device settings is visible.

Figure 15: Device Info Tab

19

5.3 KNX

With a simple click on “On” or “Off” Program Mode can be switched on/off. This
function is equivalent to a Program Button press. Together with the Device Info tab it
is easy to distinguish the regarded device (with a certain IP address or MAC address
or serial number) from other similar devices in the same IP network. Also, setting
changes can easily be checked.

Four tunnelling addresses can be set. ETS sets the first tunnelling address. With a
click on “Set” the remaining ones are set. Moreover, routing multicast address,
serial number of the device and a last-60-minutes KNX busload diagram are visible.
The red curve shows the maximum busload history and the green one shows the
average busload history both of the TP side.

Figure 16: KNX Tab

Note: The web browser used has to support SVG graphics.

5.4 (Firmware) Update / Boot Mode

Under the Update tab the KSR-01IP firmware can be updated like described in
following steps 1 to 5. During the firmware update process KSR-01IP enters Boot
Mode. Then LEDs 1, 2, 3, and 7 have states as described in Table 3.

Note: If Boot Mode is already active only the Web front-end instructions from step 3
to step 5 must be followed (refresh, request update).

Note: Boot Mode is still active after device reset and after factory reset.

To exit Boot Mode it is necessary to enter the Update tab of the Web front-end. Then
either the firmware update has to be completed (if a new firmware is available) or
the firmware update process has to be stopped by a click on the “Abort” button. After
that KSR-01IP restarts and continues with normal operation.

Step 1: Open the Update tab of the Web front-end.

Step 2:Activate Program Mode (at the KNX tab or by Program Button press ).

Step 3:After Program Mode activation give a short press to the Function Button .

Then click on the “refresh” button (alternatively, refresh the browser).

Figure 17: Update Tab

Figure 18: Update Tab and activated Program Mode

Figure 19: Update Authorized

20

Step 4: When the „request update“ button appears it has to be pressed to select the

update file and enter “Boot Mode”.

Step 5: The update file can be selected and uploaded. Clicking on the „Abort“ button

cancels the firmware update procedure and the device exits Boot Mode.

5.5 IP Tunnelling Address Assignment

According to the host's physical address assignment the first tunnelling address
(additional physical address) of the KSR-01IP can only be set by ETS.

Note: Please make sure: The additional physical addresses for tunnelling and the
host´s physical address have to be different.

Step 1: Open the ETS Bus tab and select KSR-01IP as the “Current Interface”. In the

“IP Tunneling” window the already assigned host physical address can be
read.

Figure 20: Request Update

Figure 21: Select Update File

21

22

Figure 22: First Additional Physical Address (First Tunnelling Address)Assignment

Figure 23:Additional Tunnelling Address Assignment in the Web Front-end

Step 2: Set the first additional physical address by the “Individual Address” field.

Click on the “Test” button. If the green appears, the first tunnellingOk
address is set. In this example it is “9.1.241”.

Step 3: Now open the KNX tab of the Web front-end. Click on the “Set” button to set

the remaining three tunnelling addresses basing on the first tunnelling

address as follows.

23

6 State of Delivery

6.1 Default Factory Setting

Table 12: Default Factory Setting

24

6.2 Technical Datasheet

6.3 Technical Drawings

Note: All dimensions shown here are specified in mm.

Note: The total device width is 2 modules at 18 mm.

25

+

-

+

-

36

90

44.9

22.55

12.2

50.9

71

4

37.6

KSR- IP01

KNX IP Router

I

Function

Bus State

IP TP

Traffic

GA PA

Prog.

MEUADE IN

Figure 24: Dimension drawings

7.FAQ

◎The firmware update finished successfully but the device doesn´t work.

Turn the power off and on again (or dis-/reconnect bus line). Try to restart like this.

◎ Is it Ok to connect and disconnect the Ethernet cable quickly?

No! Don't do this. To observe, State IP LED will light green for a few seconds and
after that, the device will reset.

◎ What shows the Programming LED if the Ethernet cable is not connected?

When the cable is not properly connected, the Programming LED is blinking red.

◎ LED A2 Bus State KNX TP is continuously blinking green. Why?

This indicates KSR-01IP is in Boot Mode. For more information and how to switch
back to normal operation please refer to chapter 5.4 (Firmware) Update/Boot
Mode.

◎ I disabled DHCP and assigned a correct IP configuration, but I cannot

access the Web front-end. Why?

Reset the KSR-01IP and try again. More information about changing the IP
network configuration can be found in chapter 4.2 IP Configuration.

◎ I try to access the Web front-end but I'm not successful. What can I do?

Make sure the URL bar entry matches the correct IP address together with the
right HTTP port or use the MAC address in exactly the way as explained (see
chapter 5.1). Then wait for about 5 or 10 seconds, refresh the browser and try
again.

26

◎ Is it possible to reach the Web front-end when the device is in Boot Mode?

Yes, it is. The Web front-end is accessible also in Boot Mode (see chapter 9.4

(Firmware) Update Tab). When Boot Mode is active, the Web front-end looks like
illustrated in figure 5. To run a firmware update procedure and/or exit Boot Mode
the Web front-end Update tab must be used.

◎I was able to reach the Web front-end. But when I try to use its tabs or

buttons my browser only shows a connection error to me. What can I do?

Refresh the browser window. The Web front-end will show up again.

◎ How can I find out the actual IP address of my KSR-01IP?

The Device Info tab of the Web front-end shows the actual IP address, but also the

list of Discovered Interfaces in ETS.

No.28, Wuquan 3rd Rd., Wugu Dist., New Taipei City 248, Taiwan