Hello
I have a problem with high TP repeats. It seems that LM5 does not send acknowledge although I have enabled that function.
You can see all the repeat telegrams on the screenshot below. For testing purposes, KNX line LM5 is connected to has no other devices than KNX power supply and USB interface.
Firmware version is 20240426. There are 4 different LM5 on this installation, and all 4 has the same issue.
I have tried multiple settings with no luck.
08.11.2024, 13:58 (This post was last modified: 08.11.2024, 14:02 by msybilla.)
(08.11.2024, 13:43)Daniel Wrote: Are these telegrams sent by LM to the bus?
No, these are sent by Siemens IP routers to the multicast.
Note that we didn't use standard multicast due to multiple KNX installations at the same network (customer requirement).
But both IP routers and LM5s are set up with the same multicast address.
It might be worth mentioning that we use GA filtering to filter away group addresses we don't use. But I got same issue without filter.
The ACK is only for TP telegrams sent from the line LM is connected too. LM cannot ack itself. These telegrams goes from IP to TP via LM and are not TP telegrams only IP so are treated as LM telegram. The only thing you can do it to use filter table and block not needed telegrams.
(08.11.2024, 14:11)Daniel Wrote: The ACK is only for TP telegrams sent from the line LM is connected too. LM cannot ack itself. These telegrams goes from IP to TP via LM and are not TP telegrams only IP so are treated as LM telegram. The only thing you can do it to use filter table and block not needed telegrams.
These repetitions comes through LM5 for every group address allowed in filter table in LM5.
Also it is imposible to turn off repetitions on Siemens IP routers.
05.10.2025, 20:30 (This post was last modified: 05.10.2025, 21:02 by Bba.)
Hello,
I have a problem with TP repeats like as you can see in photo.
Also i found one IP from ARP table which is very strange for me.
What i did three months ago, i use this LM as master and 192.168.0.101 as slave and i read information by a script from LM.
After that, i turn off both LMs, and few days ago after turn on LM as a simple LM not a server, TP repeats look like in this photo. This LM is now alive on a project. The KNX is works fine but i don't know what happened. I deleted all old scripts and old variables which i used in my exercise with master and slave.
Do you think this IP makes this noise on TP repeats?
Later edit 1: I saw if i try ping to 192.168.0.102 and 150, the LM put these ips in arp table with strange MAC.
So, how delete these strange IPs?
TP repeats count both transmitted and received telegrams that weren't acknowledged.
For received telegrams you can temporary enable "ACK all group telegrams" in LM KNX connection settings and see if the number of repeats changes.
For transmitted telegrams check which LM group addresses are not needed on KNX/TP side. Either disable "Write to bus" option where possible or use virtual group addresses.
You don't need to do anything to the ARP table, it's managed by the OS automatically.
