ETS 6 becomes nearly unusable with Group Monitor under high bus traffic
This post reports a serious usability and performance issue in ETS 6 related to the Group Monitor when there is high traffic on the KNX bus.
When Group Monitor is open and bus traffic is high, ETS 6 becomes almost unusable. It appears that the entire application refreshes for every single telegram sent on the bus. This results in severe performance degradation and makes normal work extremely difficult.
Practical consequences include:
-
Almost impossible to copy telegrams
-
Very difficult to read and analyze multiple telegrams
-
General lag and loss of responsiveness across the application
In high-traffic scenarios, ETS 6 becomes very difficult to use, to the point where effective monitoring and analysis is no longer practical.
This behavior does not occur in ETS 5, where Group Monitor remains usable even with high bus traffic. This suggests a regression in ETS 6 that should be investigated.
Given how critical Group Monitor is during commissioning and troubleshooting, this issue should be treated as a significant regression and usability defect that requires attention.
-
I have the same issue, sometimes I leave the ETS6 app open for a night to monitor what has happened during the night, it is almost impossible to search through it, the machine has plenty of storage, cpu, disk etc (runs on a server 24 GB ram, 16 cores etc).
Also opening a new tab is slow, even splitting a tab etc. Looks like too many GUI items are being updated when doing something with the GUI.
It is actually so slow it is not really fun to debug issues anymore. Every click takes about a second to respond.
0
Opmerkingen
1 opmerking
U moet u aanmelden om een opmerking te plaatsen.