IP Tunneling setting help needed

[miklosbakos]

Hi Team, That's a super beginner question I need help with. Previously the LSS100100 worked well, I was able to program individual devices on the KNX network, and the LSS100100 listened to the network traffic and update GA values, so everything was fine.
Now, I'm not able to even download the application in ETS sw. The settings and issues explained below:

LSS100100 KNX network settings (please find screenshot):

Mode=IP Tunneling

Tunneling router IP: the IP of the LSS100100

KNX address is set

Enabled IP routing, Enabled passed individual telegrams, and accepted IP Tunneling.

Topology: there are 15 devices on KNX simple line network (red/black wires), plus the LSS100100 connected, my PC and LSS100100 are connected through a wifi router.

With the above settings, the ETS software cannot discover the device, so I added manually, Test=OK. However, when I try to download an app to a previously programmed device (blind control) it gave an error message saying "The current subnetwork of the interface does not exist in your project. Do you want to change your local settings now? Interface: New Connection - 192.168.1.162:3671(15.15.100)", I accept the changes but it brings back the Individual address panel to set it up, and it just in this loop, error/change the local setting/ask for induvidual address/starts again...

I know this settings is very basic, but I spent hours on this, I tried a bunch of different things, but now I don't have more options...

There is a KNX/IP interface device (MTN6502-0105) on the Network as well (disconnected from the router now), with that device the ETS software works fine.

Can you please help me with the right KNX network settings of the LSS100100?

Thank you

BR

Miklos

[Erwin-vd-Zwart]

Why is the device in tunnel mode?

Just set it to TPUART and make sure KNX IP Routing is enabled, then it will work like your other IP interface

[miklosbakos]

Thank you for your reply.

I’ve tested it earlier but there is an error: no TPUART connection, would you like to switch to KNXIP instead?

By the way, there are 3 settings below TPUART that’s related to KNXIP, should I enable all?

The bus and the installed devices work well, the LSS100100 is installed in the middle of the bus, so the physical connection has to be right.

Any idea how can I do some debug to find the issue? Or any other way I can connect the LSS100100 to the KNX bus?

Thank you

BR

Miklos

[Cristiano_Carli_Ballola · Accepted solution]

Two main issues on your LSS100100 configuration:

1. as already mentioned by @Erwin-vd-Zwart , if your Wiser for KNX controller is connected to the bus via the KNX cable, the KNX connection has to be set as TP-UART
2. The individual address of the controller must match the topology:
   you probably do not have an area 15 and a line 15 in your system.
   Therefore, change the individual address so that it indicates its actual position in your project.
   This is also the reason for the ETS error message.

[Erwin-vd-Zwart]

Can you try replace the red/grey KNX connector with another one, if your bus is powered, working and connected to the Wiser then you should not have the error on TPUART so either you have a bad TP connection or the device is malfunctioning, probably the first…

[miklosbakos]

Thank you for both.

Unfortunately, I've already tried the TPUART, but either ETS says no connection with the KNX device when I try to download, OR the LSS100100 shows an error message: "KNX/TP is not connected. Scripting, visualization and other features may not work. DO you want to switch to KNX/IP instead?". So it seems the LSS100100 doesn't communicate with the TPUART network at all. Wire connections are fine.

So the only solution I have is to try to establish the connection through KNX/IP routing (or maybe tunneling). I would buy a new device only if it is really necessary.

Is there any way I can communicate with KNX devices on the TPUART network with utilising the LSS100100 and the working KNX/IP device?

Any advice is appreciated.

Thank you

Miklos

[Erwin-vd-Zwart]

If you have devices and PSU connected to the TP of the controller and you get the TP disconnected message you either need to check the connection and check 30V , also check when you have a PSU with secondary power output that you have connected the BUS otherwise the choke is missing (i have seen this more often), if all of this still give you the message on TPUART your device is probably damaged ..

[miklosbakos]

Yes I swap the terminals of LSS100100 and the well-operating KNXIP Gateway, the result is the same, I can communicate through the KNXIP properly but not with LSS100100. Yes I said it is a hardware issue. Is there any settings I can utilise the LSS100100 with the KNXIP gateway to get a solution for this hardware issue? Or the only solution is to buy another device?

[miklosbakos]

Thank you all for your helpful replies.

The device is damaged.

So the final solution is that I set up the KNXIP gateway as the IP Tunneling router, please have a look at the screenshot attached.

BR

Miklos

[DCD110]

Dear community,

since today I have exactly the same issue. My traffic lights have been in red with 520% total percentage of controller total utilization. So I followed this guide and enabled ACK in all telegroups.

This has solved the traffic light issue. But now I have no more control over my Wiser for KNX device. I cannot access it remote. I've been trying to fix it for hours now, unfortunately without success.

Can someone please tell me what I need to do? Thank you!!

[Erwin-vd-Zwart]

@DCD110 Does it work normal when locsl? You mentioned that the traffic light issue is solved, i assume you can still access the controller to determine that..

How do you approach the controller remotely? Via VPN or port forwarding, do you approach it with ETS or via a web browser?

in other words can you give more details in the problem you are facing as changing the ACK setting normally can’t result in your issue in any way..