800xA Trends are taking long time to load
Voted best answer
Where are the logs stored? In 800xA History DCN/history server or only Basic History? Please clarify.
Basic History usually have pretty good retrieval performance... are you using very large time scopes and Ext/Momentary trend treatment (which imply reading all raw points from primary log only instead of utilizing less dense data from secondary logs)?
Network bandwidth OK? Performance poor also when reading log on historian node itself?
If you are using 800xA History, I suggest creating a few Basic History based logs to circle the problem to be 800xA History, then file a support case with your regional ABB support center.
Answers
I found the Windows Time is no disabled in the connectivity server, should be it the problem?
I have two control networks, In one of them the trend are working normal and this one Windows time is disabled, the other one that Windows Time is started I have had problems to load the trends.
Windows time must be disabled in all nodes, doesn't it?
Hi Stefan,
I have no idea what I should to check, the trends take 2 - 10 minutes to load.
I found just one problem that was windows time in the connectivity server.
I am avoiding to restart the connectivity server because if I do the trend back to normal, but I can not find the root cause.
Stefan,
In our system there are 2 control networks and for each one there are two connectivity services. Affinity is not set up here, so both connectivity for each control network are in service, is it correct?
I guess should be one in service and the other one in standby if there is not affinity.
Add new comment