This tech note from InSource shows how to view History Blocks created by the Wonderware Historian.
- Author: Michael Walker
- Published: 12/17/2015
- Applies to: Wonderware Historian - All Versions
To view history block information perform the following tasks:
1 In the System Management Console tree, expand a server group and then expand a server.
2 Expand Management Console and then select History Blocks. The history block information appears in the details pane.
Column descriptions are as follows:
The starting timestamp for the history block.
The ending timestamp for the history block.
The path to the storage location. The circular storage location must be a local drive on the server machine, and the path must be specified using normal drive letter notation (for example, c:\Historian\Data\Circular). While the alternate, buffer, and permanent storage locations can be anywhere on the network, it is strongly recommended to have the alternate storage location configured on a dedicated physical drive locally attached by a high-speed interface to the Historian Server or configured to be on a different internal hard drive. If you use a network location, then the ArchestrA user must have full access to the network location. The locations must be specified using UNC notation. Mapped drives are not supported.
The time span for the history block.
The time zone of the history block.
The time offset from Coordinated Universal Time.
The data shown in the details pane is not automatically refreshed. To refresh the list from the history block information held by the Configuration Manager, right-click on History Blocks in the console tree and then click Refresh. In most cases, this type of refresh is all that is needed.
A yellow icon for a history block indicates that all tag information is loaded into memory, and you can query and insert data for that block. The block is considered to be “online.” If the icon is grey, the tag information is not loaded, and the block is considered to be “offline.” If you have enabled memory management for the system, tag information is loaded as needed for requested blocks. For more information on memory management, see Memory Management for Classic Storage.