(25.07.2019, 08:12)Daniel. Wrote: What about Memory ?
Mostly free. I don't have the exact values now, but it is low utilization.
I wanted to put all system values in trends to see what causes the reboot, but can't find a method. I can feed the values to external bacnet device that is not affected by reboots.
I'm also not sure is it something o. LM or external, the logs could give a clue about that.
According to my experience KNX packet loop through multicast IP triggers reboot very quickly. Plus you lost evidence and the source of the problem which makes it hard to discover the issue.
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
(16.08.2019, 08:31)Thomas Wrote: According to my experience KNX packet loop through multicast IP triggers reboot very quickly. Plus you lost evidence and the source of the problem which makes it hard to discover the issue.
Yes, that is true.
But I can't see where can a packet loop materialise. TP is terminated on the N146/02, from there only ethernet to the switch where everything is connected together.
If the TP is bridged somewhere, or the LM has both IP and TP connections I can understand, but it is not.