800xA DCS Time Resync
Dear,
the time in system shifted one year to the future; because of a problem in GPS NTP, now all events and trends logged the shifted time, which make trouble for us.
Could you please guide me to get rid of asynced-logged data without could restart the controllers?
Thanks in advance.
Asked 12 days ago
Voted best answer
3
For events stored in Event Storage of 800xA Base, you can simply remove the contents of the \OperateITData\EventStorage\{SingleGUID} while having the service stopped/disabled.
You can also perform a selective clean for a subset of categories only (maybe only one or two categories need to be cleaned keeping the remainder intact?). The event category is shown in the Event Details... window you can call by right clicking any alarm or event.
The below image details how to use the afwapplogviewer.exe to query for all known categories and translate the decimal category ID into hexadecimal used by Event Storage on disk
For events stored in other historians (IM, 800xA History, etc.) you probably have to use low level database commands to remove database rows having future data. Sorry no examples. Please ask your regional ABB support center to assist you.
Alarms are not stored on disk in 800xA HMI (only events are persistently stored across restarts); if you have future alarms in your lists you must likely restart the OPC AE servers to have them to forget the future alarms and report back to the HMI. If the PLC still have such alarms in "non-idle" state, they may be refreshed at restart. In that case you must get the alarms back to "idle" (inactive, acknowledged). There is a "Delete Alarm" command on the context menu of alarm lists, this delete will not propagate to any underlying OPC AE server. Hence, don't use Delete Alarm if the OPC AE server still knows about it. Restart the OPC AE server, possibly also the PLC.
For trends stored in Basic History there is a "Remove Future Timestamps" operation in afwapplogviewer.exe (a not documented troubleshooting tool). It has been mentioned in previous threads, search for information on AKS. It may take 20 minutes for all logs to have been purged. Have patience. We mention this tool in our E143 Troubleshooting System 800xA Expert Workshops.
The IM has a "Remove Future Stimestamps" function built into its command line hsdbmaint.exe tool; lookup chapter 13.14.18 Purge History Data in the IM Configuration User's Guide, 3BUF001092-610A.
For further assistance, please ask your regional ABB support center to assist you.
You can also perform a selective clean for a subset of categories only (maybe only one or two categories need to be cleaned keeping the remainder intact?). The event category is shown in the Event Details... window you can call by right clicking any alarm or event.
The below image details how to use the afwapplogviewer.exe to query for all known categories and translate the decimal category ID into hexadecimal used by Event Storage on disk
For events stored in other historians (IM, 800xA History, etc.) you probably have to use low level database commands to remove database rows having future data. Sorry no examples. Please ask your regional ABB support center to assist you.
Alarms are not stored on disk in 800xA HMI (only events are persistently stored across restarts); if you have future alarms in your lists you must likely restart the OPC AE servers to have them to forget the future alarms and report back to the HMI. If the PLC still have such alarms in "non-idle" state, they may be refreshed at restart. In that case you must get the alarms back to "idle" (inactive, acknowledged). There is a "Delete Alarm" command on the context menu of alarm lists, this delete will not propagate to any underlying OPC AE server. Hence, don't use Delete Alarm if the OPC AE server still knows about it. Restart the OPC AE server, possibly also the PLC.
For trends stored in Basic History there is a "Remove Future Timestamps" operation in afwapplogviewer.exe (a not documented troubleshooting tool). It has been mentioned in previous threads, search for information on AKS. It may take 20 minutes for all logs to have been purged. Have patience. We mention this tool in our E143 Troubleshooting System 800xA Expert Workshops.
The IM has a "Remove Future Stimestamps" function built into its command line hsdbmaint.exe tool; lookup chapter 13.14.18 Purge History Data in the IM Configuration User's Guide, 3BUF001092-610A.
For further assistance, please ask your regional ABB support center to assist you.
Add new comment