more quick actions
minimize quick actions
Topic starter
Hello,
One of our integrators experiences a vastly increased project startup time in a large project after having added about 900 alarm counters to the project. In fact, the startup time is now double as much as before.
It appears that this effect is due to the values of the counters being calculated right after the variable is created in memory and initialized. Even if the alarm counter variables themselves are internal, their value depends on communication variables, which is why I assume that the performance improvements for internal variables done in PcVue 11.2 probably will not apply.
Do you have any idea how to mitigate the effect? Is there any good method of delaying or skipping the initialization of the counters and continuing the startup process without?
Thanks for your help!
Posted : 07/03/2018 4:20 pm
Hello Armin,
I really think that it is better to use alarm syntheses if possible.
Dominque explained me that they are updated once per second contrary to alarm counters that are updated every time an alarm change.
So I can imagine that your startup time will not be impacted to much with alarm syntheses.
It is maybe a huge work to transform 900 alarm counters into alarm syntheses so you would better discuss that with Dominique to be sure it could really be efficient.
Posted : 08/03/2018 12:14 am
Topic starter
Thanks, Ludo.
Excuse my inaccuracy, I was in fact speaking of alarm syntheses, not alarm counters. I have updated the title of this thread accordingly.
Posted : 09/03/2018 3:31 pm
Hi Armin,
You said it double the starting time but could you give the figures please?
From what time to what time?
Nico
Posted : 12/03/2018 10:24 am