05.11.2021, 14:09
Hi
The situation described above by KNXUser is a serious design issue. I've reported it few years ago and it looks there's still no solution at all. I think his idea with limiting ACKs is great.
Today I found new strange behavior of ACKing:
I've two LMs connected to the same line. The first one has "ACK All group telegram" turned on. The second one (backup) has it turned off.
My first LM (Version: 20180822) shows 4 repeats per hour
My backup LM shows (Version: 20211014) shows 4000 repeats per hour.
If I turn "ACK All group telegram" on at the backup LM then this counter drops significantly down.
It seems to me that internal changes require ACKing too.
The situation described above by KNXUser is a serious design issue. I've reported it few years ago and it looks there's still no solution at all. I think his idea with limiting ACKs is great.
Today I found new strange behavior of ACKing:
I've two LMs connected to the same line. The first one has "ACK All group telegram" turned on. The second one (backup) has it turned off.
My first LM (Version: 20180822) shows 4 repeats per hour
My backup LM shows (Version: 20211014) shows 4000 repeats per hour.
If I turn "ACK All group telegram" on at the backup LM then this counter drops significantly down.
It seems to me that internal changes require ACKing too.
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259