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.
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
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
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:
1234567891011
myobjects = grp.tag('Read')
for_, objectinpairs(myobjects) do-- send read request to objectgrp.read(object.address)
os.sleep(1) --dealy in secondsend
You can add also to start up script to read on boot.
(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:
1234567891011
myobjects = grp.tag('Read')
for_, objectinpairs(myobjects) dolog(object.address)
-- send read request to objectgrp.read(object.address)
os.sleep(1) --dealy in secondsend
You can add also to start up script to read on boot.
Thanks. But how will this reduce bustraffic when polling?
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
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?
(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.