Logic Machine Forum
LM5 polling rate KNX - Printable Version

+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: LM5 polling rate KNX (/showthread.php?tid=1794)

LM5 polling rate KNX - gs@el-24.no - 18.12.2018

Hi,

Does LM5 have a parameter for setting the maximum polling rate for KNX objects via multicast? 
I've noticed that LM5 really pushes the capacity of the sublines.

RE: LM5 polling rate KNX - Daniel - 18.12.2018

(18.12.2018, 09:15)gs@el-24.no Wrote: Hi,

Does LM5 have a parameter for setting the maximum polling rate for KNX objects via multicast? 
I've noticed that LM5 really pushes the capacity of the sublines.

Hi
LM does not pool any object unless you program it like that. It monitors live every telegram.
BR

RE: LM5 polling rate KNX - gs@el-24.no - 18.12.2018

(18.12.2018, 10:53)Daniel. Wrote:
(18.12.2018, 09:15)gs@el-24.no Wrote: Hi,

Does LM5 have a parameter for setting the maximum polling rate for KNX objects via multicast? 
I've noticed that LM5 really pushes the capacity of the sublines.

Hi
LM does not pool any object unless you program it like that. It monitors live every telegram.
BR

Correct, but Im using it for polling of 1000+ objects. I would like to limit the amount of telegrams pr second

RE: LM5 polling rate KNX - Daniel - 18.12.2018

How do you do it?

RE: LM5 polling rate KNX - gs@el-24.no - 18.12.2018

(18.12.2018, 11:06)Daniel. Wrote: How do you do it?

Ive done a mass edit of the objects I need to poll by using the function "read during startup" and "poll intervall"

RE: LM5 polling rate KNX - Daniel - 18.12.2018

Then do it via script.
Tag all objects which you want to pool with tag 'Read' and make a schedule script which will run as often as you want.  just make sure it will not run faster then time of execution of the script.  1000 X Delay 

Code:
myobjects = grp.tag('Read')


for _, object in pairs(myobjects) do

 -- send read request to object
 grp.read(object.address)

 os.sleep(1) --dealy in seconds

end
You can add also to start up script to read on boot.

RE: LM5 polling rate KNX - gs@el-24.no - 18.12.2018

(18.12.2018, 11:24)Daniel. Wrote: Then do it via script.
Tag all objects which you want to pool with tag 'Read' and make a schedule script which will run as often as you want.  just make sure it will not run faster then time of execution of the script.  1000 X Delay 

Code:
myobjects = grp.tag('Read')


for _, object in pairs(myobjects) do
 log(object.address)
 -- send read request to object
 grp.read(object.address)

 os.sleep(1) --dealy in seconds

end
You can add also to start up script to read on boot.

Thanks. But how will this reduce bustraffic when polling?

RE: LM5 polling rate KNX - Daniel - 18.12.2018

In here os.sleep(1) --dealy in seconds  you specify how often you will make read request and it will go over all objects one by one with this delay.
Obviously disable all the previous pool settings.
I deleted not needed log in original script

RE: LM5 polling rate KNX - admin - 18.12.2018

Keep in mind that with 1000 objects and 1 second delay each object will be polled once in 17 minutes. The question is why do you need polling instead of devices sending object values on change and/or by their own timer?

RE: LM5 polling rate KNX - gs@el-24.no - 18.12.2018

(18.12.2018, 11:36)admin Wrote: Keep in mind that with 1000 objects and 1 second delay each object will be polled once in 17 minutes. The question is why do you need polling instead of devices sending object values on change and/or by their own timer?

Because all devices doesnt have cyclic sending for all objects, and the BMS does not support polling trough KNX protocol. Thats why we poll via LM5. BMS turns on their updateflag so that values get updated in the BMS, for example after restart or crash.

RE: LM5 polling rate KNX - admin - 18.12.2018

Ok then use what Daniel suggested. You can lower delay in os.sleep to 0.5 or less, depending on overall bus/system load.