KNX LSS100100 - traffic lights - overload of the controller & repeats on KNX BUS (Over 600%)

[tiago_oesteprisma]

Hi,

I'm not able to remote control the installation using "wiser for knx" android app.

The app keep's loading, but the touch buttons don't appear.

The only sign of error is in the traffic lights, but I'can't see how this percentage can be reduced.

Any tips how we can reduce this in the installation?

Thanks in advance.

[Cristiano_Carli_Ballola]

That Red traffic light is most likely generated by the repeated telegramms.
Two tips to reduce that issue:
- enable the "ack all telegramms"  within the Controller settings.
- use virtual KNX object instead of classic KNX object when ever is possible, especially when that
object is used within the controller only

[FZetina]

Hi @tiago_oesteprisma 

When the app fails to load information on the screens, it is often due to the controller being overloaded, which disrupts communication with the app. A quick fix is to restart the controller; however, depending on the underlying cause, this issue may recur. To prevent this, please follow the best practices and recommendations that Cristiano highlighted (above) to ensure these factors do not impact your controller's performance.

Thank you!

Best,
Fernando

[tiago_oesteprisma]

@FZetina and @Cristiano_Carli_Ballola , thanks for your reply.

It worked, the controller has now values bellow 13%.

Although, the acess to the installation (touch,PC/Tablet/Smartphone), are very slow.

Take more than 3 minutes to access. It displays the icon in the image.

Acessing to the other options are working fine.

Any ideias?

[esteve_budia]

I'd like to share with you this "Repeats Guide" to help anybody with this traffic lights problem:

When we encounter this problem we must act on several guidelines:

Use the built-in tool in Wiser to know the level of repetitions:

This Tool is located in:

Configurator / System / Network / KNX Statistics

What to do then to ELIMINATE the repetitions?

1.- Eliminate shipments not recognized as orphan telegrams such as temperatures, wind speed and other telegrams that do not have an associated actuator. This can be done by activating this function:

Configurator / System / Network / KNX Connection / Enable -> ACK in all telegroups

2.- If we use Modbus profiles, it is important that all addresses here are "virtual" otherwise group addresses less than 31 would also cause repetitions.

3.- Limit the use of addresses smaller than 31 in the scripts and replace them with virtual addresses.

4.- After all this, if we still have repetitions we will have to use our USB interface to see the bus telegrams through the Bus Monitor:

In this case, it is Wiser For KNX itself who sends unrecognized telegrams since it cannot recognize itself.

Using virtual variable, more much better.

Repetitions produced by Couplers:

-------------------------------------------

It is very important to have the IP couplers/router well configured so as not to propagate telegrams or repetitions upstream of the TP connections.

Below is an example of how to configure these devices:

In both one direction and the other, the repetitions must be set to NO.

On the other hand, it is also more than advisable to always use the telegram filtering option using the route tables.

Today, you don't have to do anything else, the ETS configures everything for you to work.

Also remember that the couplers must be reprogrammed last and whenever we modify any element on the bus, they must be reprogrammed again to update the route tables.

[tiago_oesteprisma]

thanks @esteve_budia 

The tips you gave worked, and now there aren't any traffic lights.

Now the problem is accessing the installation to control it.

I've created a new user, to test and it keeps freezing everytime I enter. Any thoughts?