I have two questions. The first concerns exporting data via BACnet IP.
I have a building with three Logic Machine 5 controllers connected. Each controller has been assigned a static IP address of the following type:
192.168.0.11
192.168.0.12
192.168.0.13
We have also created a VPN using the OpenVPN client to access it through the router located in the building.
My question is this: we need all three Logic Machines to export data via BACnet IP to a remote BMS. For some reason, only Logic Machine number one is exporting data. I'm not sure what I'm doing wrong, but I need Logic Machines 2 and 3 to also export a series of group IP addresses.
My second question concerns the filters. The group addresses loaded into logic machines 1, 2, and 3 are exactly the same. This is because we've placed the SCADA screens on logic machine 1, so logic machines 2 and 3 have to send data to logic machine 1 to be displayed on the screen loaded on logic machine 1.
My question here is this: I more or less understand, but I want to be sure. I want the following to happen:
LM2 and LM3 send data to LM1.
The data sent to LM1 should not be sent back to LM2 and LM3.
LM1 does not send data to LM2 and LM3.
How should the IP filters be configured? Thank you very much for everything.
BACnet:
Make sure that each LM has a unique Device ID (System config > Network > BACnet settings).
KNX/IP filtering:
Make sure that each LM has a unique KNX address (System config > Network > KNX connection).
On LM2 and LM3 set "IP > Local" SRC policy to "Drop" and put LM1 address into the "Ind. address list". You can also block LM2 from LM3 and LM3 from LM2 the same way if needed.
(31.03.2026, 10:27)admin Wrote: BACnet:
Make sure that each LM has a unique Device ID (System config > Network > BACnet settings).
KNX/IP filtering:
Make sure that each LM has a unique KNX address (System config > Network > KNX connection).
On LM2 and LM3 set "IP > Local" SRC policy to "Drop" and put LM1 address into the "Ind. address list". You can also block LM2 from LM3 and LM3 from LM2 the same way if needed.
Okay, the KNX addresses for LM_1, 2, and 3 are 1.1.250, 1.2.250, and 1.3.250. I'm going to attach an image of the KNX configuration for LM_2, and you can tell me if it's set up correctly to block data coming from 1.1.250, that is, data coming from LM_1.
You can easily test this by changing a common group address value in LM1 and see if it changes in LM2/LM3.
Keep in mind that this will only block telegrams from LM1 itself. Any telegrams coming from KNX devices connected to LM1 via KNX/TP will still pass the filter. If you want to block all communication from LM1 then change the filter value to 1.1.*
Do you really need to poll values for 0/0/11 and other group addresses? Multiple LMs are polling these addresses which creates even more unnecessary traffic.
To fix this disable "Poll interval" option for relevant objects on all LMs.
10 hours ago(This post was last modified: 10 hours ago by ALEJANDRO.)
Those addresses are readings from temperature, humidity, and CO2 sensors. I need those values for some displays.
When you say "To fix this, disable the 'Poll interval' option for relevant objects on all LMs," are you referring to what I sent you in the image?
How can disable that?
10 hours ago(This post was last modified: 10 hours ago by ALEJANDRO.)
If what you're asking is whether I use those group addresses in scripts, then yes, I use them to average temperatures, set alarms, etc.
How can I disable the poll interval?
9 hours ago(This post was last modified: 9 hours ago by ALEJANDRO.)
I've checked the entire list of scripts loaded in the LM; I never use gp.read, it's always grp.getvalue or event.getvalue.
You can see a typical script
