Hi

Apologies for the delay 

To clarify, what is happening is that after the server has been running for a couple of days, its gets into a state where it disconnects and makes a new tunnel connection every minute - obviously in this state the system is completely unusable

Here's what the Server console reports

And here's a Wireshark capture

IridiumKNX.pcapng

Use this filter

ip.addr==192.168.14.111

PC Server IP.  192.168.14.25

KNX IP interface 192.168.14.111

Line 14627 - new tunnel connection setup

data requests are then OK until line 16016

here the Iridium server writes to 10/6/0, and the bus is slow to respond, so it retries

but the IP interface sends a disconnect request (line 16224)

followed by ACKs for the writes

The server then carries on sending commands, but gets errors, until line 27442, when it checks the connection state and opens a new tunnel

This sequence then repeats (different group address that is retried each time)

So it seems its the IP interface that requests the disconnection - but I don't understand why

and the server then doesn't honour this and tries to carry on (with multiple failures) for approx 30 seconds, until it opens a new tunnel

We're gathering some network logs using traceviewer. Will get back to you tomorrow.

Just realised my colleague was running a server that was converted to using the new iRidium studio - and in the conversion process, the 'delayBetweenPolls' property was lost, and set to 0. I've now set this back to 500, but no change to the problem was seen.

BAOS was restarted, with no change to the issue we are seeing.

On arriving to the property today, the same problem was seen again. KNX Driver disconnecting and re-connecting every minute, with around 30s of polling going through correctly before we see no more activity from the KNX driver.

We will try restarting the BAOS later this morning without restarting the server, to see what effect that has.

Ok, thanks for the clarification. Nothing else connects to the BAOS at this time.

I tried running the server using the new iRidium 2019 server (without saving the server project through the new editor), and we are at almost a day without seeing this problem!

Will keep you updated, but fingers crossed the new server has a fix.

We are using a Weinzierl KNX IP BAOS 777, which allows up to 8 simultaneous connections.I'm not sure how the KNX Router handles connections breaks.

Are you saying that if the device is unavailable for a few seconds, the driver automatically disconnects? If this is the case, why does it not attempt to re-connect until its tries to send its next ping?

The next time we see this issue (likely tomorrow morning, I will restart the KNX device instead of the iRidium server, see what happens.

KNX IP Router has an IP that was assigned via DHCP, but has been reserved via MAC.

Host is an IP address

Hi Vladimir,

The server was running perfectly for close to 24 hours, but from Saturday evening we were seeing the same problems where the KNX driver was regularly disconnecting, preventing control of any devices through KNX from iRidium.

I'm setting up a KNX address that changes value every 30 seconds, to which the iRidium server responds when noticing this change by setting unix time to a 2nd new address - essentially acting as a ping to detect when these problems start happening, but would appreciate any more advice you might have

Ah I see what you mean - server build is 1.3.10.18280.

For now, I will be sticking with the old version of studio, as I understand that the structure of saved projects is changed completely, and I am using a few of my own scripts to parse the old structure, allowing multiple people to simultaneously work on the same project.

The server has been running for an hour, and control via KNX seems a lot more stable. In the server logs, the KNX failed to connect once around 20 minutes ago - so will keep an eye on it for today. Thanks for your help so far