This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

Problems with the communication of an IP interface with Logic Machine
#1
Hi guys

I wirite to ask you about the comunication betwen an ip interface and a Logic Machine, I need help with this. I configured both in the same network but It's not possible the comunication. Must I do an special configuration? 

My IP Interface is a Zennio IP interface (https://www.zennio.com/productos/sistema...face-pless). The idea is to have several lines with their respective ip interfaces and these will send information to the Logic Machine, through IP and the logic machine can write in any of these lines if necessary through the ip interfaces.

I have already tried placing the LM in Routing mode, EIBnet / IP Tunneling, but it asks me for an IP tunneling routing, which I do not know what it is. With none of the previous configurations I managed to update a group address that I have in the logic machine. It should be noted that the IP interface works, because with the help of a BMS from Netx Automation, if I can have the updates of the group addresses.

Thanks.
Reply
#2
You need an IP router if you want to connect several KNX/TP lines to LM. LM can connect to IP interface via tunnelling, but only to one and LM KNX/TP cannot be used in this case.
Reply
#3
The previous thing there is no way that it can be avoided, either with some script, library or some hardware, since for a project it thought in the logic machine so that it collected the information of each line by means of an ip interface and then the LM write in each line to know the ip of each ip interface, especially because in all lines is an obligation to repeat the group addresses and only change the ip of the interface and if you have to do it by ip router, touch filter table and it would be much more complicated. One last question, this inconvenient of not being able to use the ip interface directly, unlike Netx Automation, is a limitation of software or hardware?
Reply
#4
LM can only connect to a single IP interface. You need to use IP routers otherwise. This is a software limitation.
Reply
#5
This is limitation of KNX. LM act as KNX IP router and if you want other lines to communicate to it you have to use routing not tunneling. This is advantage as to send telegrams between lines you don't need any middle ware like NETx to pass data between lines. Less points of failure.
Reply
#6
Hi, I ask for help)
I want to use the spacelYnk as a gateway for knx / ip. Can a Logicmachine work with a knx bus through a spacelYnk and control knx devices? I set LM to the knx / ip routing mode, and the spacelink to the knx / tp mode, but there is no connection ...
Reply
#7
What do you mean by no connection? If both use the same multicast and KNX IP is enabled then all telegrams will go trough. I assume you do not use any filters.
Reply
#8
I mean, telegrams from the knx do not go to the LM head unit. I did not apply filters, knx/ ip included ....
Reply
#9
Then as I mentioned, make sure the multicast is the same and KNX IP enabled. I assume you didn't put ant encryption key.
Reply
#10
Hi Danie.l Please see the configuration. What am I doing wrong?
I do not see telegrams on the LM bus.

Attachment


Attached Files
.pdf   Screen.pdf (Size: 131.67 KB / Downloads: 21)
.pdf   Screen11.pdf (Size: 128.21 KB / Downloads: 14)
Reply
#11
Looks OK, what about of filter table?
Reply
#12
I did not include filters
Reply
#13
Please show the screenshots.
PS switch language to EN.
Reply
#14
Switch might cause issues with multicast traffic. Set one LM to tunnelling mode and connection IP to other LM. Check if KNX traffic shows up.
Reply
#15
Attachment

In tunnel mode it works! Admin, Daniel thanks !


Attached Files
.pdf   Screen.pdf (Size: 124.33 KB / Downloads: 9)
.pdf   Screen11.pdf (Size: 125.56 KB / Downloads: 8)
.pdf   Screen22.pdf (Size: 110.84 KB / Downloads: 7)
Reply
#16
Another thing to try is to run Wireshark on the same network using ip.addr==224.0.23.12 filter to check KNX multicast traffic
Reply
#17
Ok, I'll try!
Reply
#18
Why do you have high CPU load?
Reply
#19
I myself can’t understand. Sometimes it rises to 1.7, but usually 0.34
Reply
#20
You can install System load app from the store and monitor CPU activity in real time.
Reply


Forum Jump: