BACNET IP and IP filters comm

[ALEJANDRO]

1.6.250 is LM_GARAGE, 1.4.250 is another LM we must disconnect

[Daniel]

you can change knx multicast address on them to be invisible for other LMs.

[ALEJANDRO]

To rewind a bit:

How can I prevent LM1 from sending data to LM2 and LM3?

I'm observing that LM2 and LM3 are indeed requesting address readings from groups of KNX objects connected to LM1.

How can I block this or make it request at longer intervals?

---

How could I make it ask at much longer intervals in time? It's practically every second.

[Daniel]

One option is filter table and second is changing multicast address, but why do you want to send the read requests? I'm sure your sensor sends its value on change and periodically anyway.

[ALEJANDRO]

I'll answer in parts. Yes, the sensors and displays send CO2 readings every 2 minutes and every 30 seconds, as per the default settings in ETS6.

Regarding why I want to send reading requests, it's simple: I want LM2 and LM3 to send the temperature, CO2, and humidity values ​​from the sensors connected via KNX to LM2 and LM3. Why do I want this on LM1? Because I created the SCADA displays on LM1.

What I need is to filter what data I want to receive and send from LM1, and especially to do so over longer intervals.

[admin]

You don't need any read requests at all, they are just generated junk traffic.
When sensor sends new value LM will forward it from KNX/TP to KNX/IP and all other LMs will receive this.

In your setup it would make more sense to have a central LM that uses only KNX/IP and all other LMs acting as KNX/IP routers with some local logic if needed. This way all visualization and alerting can be done in one place.

[ALEJANDRO]

Can you explain your proposal to me again?

[admin]

This is a standard approach to medium-sized installations. Each KNX/TP line is connected to KNX/IP either via KNX/IP Router or LM. A central LM does not use KNX/TP at all. Filtering is configured in a way that the communication between different TP lines is blocked but central LM can access all TP lines.

For this to work each KNX/TP line must have unique group addresses. And it might not work for you if you need many trends logs because you will be limited by a single LM.

[ALEJANDRO]

We hadn't considered that idea. My company received an architectural plan that included a logic machine at each entrance of an apartment building and one in the garage. My idea was for one logic machine (LM1) to receive data for the centralized SCADA screens, and for the garage logic machine (LM_Garage) to receive alerts. Finally, each logic machine would send its own data remotely via BACnet. We have four logic machines: LM_1, LM_2, LM_3, and LM_Garage.