The method depends on the Linux distribution you use to connect to UMC. General information here.

Example:

sshfs user@remotehost:/path/to/directory /local/path

The archive contains a test version of the server for Windows. Added DisconnectReq processing. Check that this version works with your KNX device. Build only for tests, not for industrial use.

iRidiumServer32.7z

Добрый день.

Вы обращаетесь к несуществующему объекту, т. к. в панельном проекте у вас нет драйвера "KNX".

В проекте у вас 'iRidium Server", его и используйте. В качестве имени канала/фидбэка укажите то, что написано в поле Full name.

Hello.

From the available services on UMC, you can use an ssh server. Use ssh to mount the desired directory on the remote server.

Hello.

Can you attach a link to the documentation for your KNX device?

Добрый день.

У вас есть ещё вопросы?

Hello.

We will examine whether the driver can handle a device disconnect request. It makes sense for you to find out the reason for the performance decline. To do this, upload the project to the server without diagrams and scripts and check whether the error will be repeated.

Drivers do not have priority over other server operations. Is there at the moment, the scripts and schema in the project? If the cause of the error is in the driver, the project without scripts and schemas will repeat the same error after the same time.

On request disable: how do you think this should be handled by the driver? To Do Disconnect? Then work with the KNX bus stop. After Disconnect, do Connect again? After what time? Reconnecting again will poll all addresses, i.e. your question will not be solved.

Hello.

Thank you for the detailed analysis. As far as we know, iRidium does not process the BAOS disconnect request in any way. We will clarify this issue separately and let you know if we are wrong in understanding the driver. However, even handling the BAOS disconnect request by the driver will not solve your problem. Because after disconnecting, the connection will be reconnected again and this will again poll all addresses. In your case, you need to check the network status: connect BAOS directly to the iRidium server, replace the cable, exclude other packets from the traffic. Another solution is to use multiple iRidium servers, each of which will have disjoint KNX address groups. Then disconnecting and reconnecting one of them will not cause the entire bus to fail, only those addresses that are in the server project will be polled.