30.08.2021, 07:56
Well, currently the UI in my environment seems to display incorrect statistics, for example, I see around 20% of TP load, while in the scripts mentioned (I'll paste below) it's around 9% - that's quite a difference:
UI:
Using the script:
I was trying to understand what is the cause, and what I found is that W4K (incorrectly) includes IP TX/RX as part of the TP bus load, but those packets are not going over TP.
Isn't that a bug?
The script I use is a version of what you linked:
About the bus load using throughput instead of rate, well I would prefer to have 100% correct information than 99% correct, when both options are equal in complexity to deliver, but it's your choice as a vendor of course to decide on the priorities of solving different problems. I think this "good enough" logic is a bug, although of a low severity
UI:
Using the script:
I was trying to understand what is the cause, and what I found is that W4K (incorrectly) includes IP TX/RX as part of the TP bus load, but those packets are not going over TP.
Isn't that a bug?
The script I use is a version of what you linked:
Code:
-- KNX bus load
maxS = 30 -- highest assumed telegram rate pr second - same as in wiser knx stats view
maxM = maxS*60 -- needs to be equal to this script's sleep interval
data = knxlib.getstats()
if data then
sent = data.tptx -- + data.iptx -- if you want to see also KNX IP stats
received = data.tprx -- + data.iprx -- if you want to see also KNX IP stats
repeats = data.repeats
traffic = sent + received + repeats
if knx_prev then
knx_load = ((traffic - knx_prev)*100)/ maxM
grp.update('Wiser KNX bus load', knx_load)
end
knx_prev = traffic
end
About the bus load using throughput instead of rate, well I would prefer to have 100% correct information than 99% correct, when both options are equal in complexity to deliver, but it's your choice as a vendor of course to decide on the priorities of solving different problems. I think this "good enough" logic is a bug, although of a low severity
Thank you!
Morkov
Morkov