Well in the statistics I screenshotted above there was a total of 1 TP repeat so it doesn't account for 11% deviation between the script load and the UI load calculation.
About the 30 telegrams per second - this is the assumption that the UI makes (and also my script) - in the last minute it shows:
TP RX (92) + TX (58) + IP RX (0) + IP TX (150) / divided by 60 seconds / divided by the "TP Load" of 16.67% == 30 seconds assumption
(92+58+150)/60/16.67 = 0.299...
This means the current user interface makes the same assumption: that there are 30 telegrams per second. And it also proves that it uses the IP statistics (RX/TX) in the calculation of the TP load - which is a mistake.
About the 30 telegrams per second - this is the assumption that the UI makes (and also my script) - in the last minute it shows:
TP RX (92) + TX (58) + IP RX (0) + IP TX (150) / divided by 60 seconds / divided by the "TP Load" of 16.67% == 30 seconds assumption
(92+58+150)/60/16.67 = 0.299...
This means the current user interface makes the same assumption: that there are 30 telegrams per second. And it also proves that it uses the IP statistics (RX/TX) in the calculation of the TP load - which is a mistake.
Thank you!
Morkov
Morkov