Stop Logging / Trends in 800xA ver. 4.1
Is it possible to stop logging / trends in 800xA ver. 4.1 in order to look them for longer period?
The system has no additional History services (IMS) included, only integrated in 800xA Base History.
The trends/logs are configured now for 1 month period.
Due to process trouble, the production line is stopped for longer period - e.g. 3 months. Actually there are no new "real" records for the trends, but the time is going on, and after 1 month the logs/trends will be overwritten by the actual values. It will not be a possible to analyze the trends at the moment of trouble.
Is there any way, different from copy to Excel, to look the trends for longer period? Or to save them (not by print screen)?
If configure the logs for longer period, the old data is cleared.
Same is with alarms - they are already overwritten by new alarms - the maximum number (10'000) is already reached.
Voted best answer
Unlike many of its "competitors" Basic History allows for runtime change of more or less all parameters there are to tune&tweak. Hence, you can easily change log period from 1 month up to a year or two (if disk space allows; 24 bytes disk space per log entry is required). Keep total storage less than 50 GB.
If a secondary log with averaged data, e.g 1 minute is acceptable you can simply add the secondary log to the template, online. Again, keep the total storage volume below 50 GB. Large configuratons of Basic History benefit from a simpler log hierachy with just one or two secondaries.
A backup of Basic History data (or a copy of its data folder, taken when service is offline) can be interpreted manually using the AdvHtLogDataViewer.exe tool.
Theoretically, the history backup can be restored into a clone of the system and viewed there. A lot can be accomplished with today's tools (VMware runtime converter standalone, VMware Player, et.c)
Event Storage can be tuned to store more events. Up to 50.000 events per category following the user's guide, maybe a bit more if the customer accepts less performance in event lists.
There are several "event loggers" available on the 3rd party market. I recommend using the OPC AE interface over a logger using some serial port emulator in combination with the Alarm Logger service.