27.10.2017, 09:17
Hello everybody
In the appendix, you see a rough principle of Spacelynks and KNX.
I can not load the KNX device 1.1.1 from line 1.2.0, the same problem is when I am with the laptop on IP network and over the multicast address try to load the KNX device 1.1.1 as well as 1.2.1. Both do not work.
Clearly there is a solution via ETS IP tunneling to select the respective Spacelynk and load the KNX device on the line, now comes the big but! in a very big project where nearly 150 Spacelynks are used as KNX couplers (and of course Bacnet / Modbus etc.) and I have over 4000 KNX devices is it no longer fun to change the interface every time.
Is there a simple solution here?
I think hardware should be no problem but most likely the security is to blame?
Spacelynk V1.4 / V1.3
Version: 2.1.0
BIG THX