03.12.2018, 09:37
There must be a loop somewhere, KNX backend cannot consume whole CPU otherwise. Try connecting to LM via ETS or use Wireshark with filter set to ip.addr==224.0.23.12 to see the telegrams.
|
Problem with LM3 V2
|
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Problem with LM3 V2 - by buuuudzik - 30.10.2018, 13:14
RE: Problem with LM3 V2 - by admin - 30.10.2018, 13:28
RE: Problem with LM3 V2 - by Daniel - 30.10.2018, 13:32
RE: Problem with LM3 V2 - by buuuudzik - 30.10.2018, 13:42
RE: Problem with LM3 V2 - by Daniel - 30.10.2018, 13:53
RE: Problem with LM3 V2 - by admin - 30.10.2018, 13:55
RE: Problem with LM3 V2 - by buuuudzik - 30.10.2018, 14:18
RE: Problem with LM3 V2 - by buuuudzik - 30.10.2018, 16:01
RE: Problem with LM3 V2 - by admin - 31.10.2018, 08:59
RE: Problem with LM3 V2 - by buuuudzik - 31.10.2018, 09:36
RE: Problem with LM3 V2 - by admin - 31.10.2018, 09:42
RE: Problem with LM3 V2 - by buuuudzik - 01.12.2018, 07:51
RE: Problem with LM3 V2 - by Daniel - 03.12.2018, 08:46
RE: Problem with LM3 V2 - by buuuudzik - 03.12.2018, 09:31
RE: Problem with LM3 V2 - by admin - 03.12.2018, 09:37
RE: Problem with LM3 V2 - by Daniel - 03.12.2018, 09:41
RE: Problem with LM3 V2 - by buuuudzik - 03.12.2018, 10:34
|