Data lost from trend
I have a problem with the trend data on 800xa 5.1 , some trends has stopped to archive even if the the values are shown on faceplate but not on trend.
I checked the history folder (basic history) to check and I have remarcked that some trends has old modification date (date trend stopped).
I checked also with Advhtarchivetool.exe to check and find some log files with error (image attached)
what could be the problem? the opc on cs?
Thank you in advance
Voted best answer
The regular Basic History service has no archiving support (but the feature has been provided to select customers) so we should probably not use the word "archiving" if we mean regular logging of data from an OPC DA source, unless you are one of the recipients of the Archiving Feature for Basic History.
Use the Service Provider Statistics object in the Service Structure to check that all logs are enabled. If not, find the inactive logs and activate them (e.g. using Log Summary aspect).
Its no match making a small PG2 graphic making those figures much easier to read - here below an example where all logs are enabled.
The purpose of the AdvHtArchiveTool is not to open a running historian's data folder (in fact, using it there to insert data to logs would be a "Catch 22").
- See to that all logs are enabled.
- Give the Basic History service a restart
- Keep a watch on the [Workplace Structure]Web System Workplace:System Event List
- Eventually, have a support case logged with your regional ABB support center.
Restart the basic history services, one at a time. Wait till the service is fully running before starting the other.
There are many reasons why Basic History may stop. The most common reason is when you make a large number of configuration changes. Restarting the services resolves most problems.
I assume you run Basic History (not the new historian - 800xAHistory). If problem remains after restart of services, you might have to reconfigure your LogConfigs. However, this will make your old history data orphaned and not possible to access. So be aware of this and if possible, extract it before this action (DataDirect or other tool).
Under specific circumstances, the OPC looses the connection to the LogConfig properties (or vice-versa) and stops updating the BasicHistory subscription. Opening a faceplate etc starts a new subscription in the OPC and will work as you discribed.
This typically occures if you, for instance do a restore of system, starts all services (incl OPC and Basic History) before you perform a download (of application) to the controller, which holds the data for your BasicHistory properties.
I've to this date, havent found a way to restart these subscriptions.
If there are no other reasons (file security, disk full etc) I'm afraid you have to reconfigure...