Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

Line entries

  • Last UpdatedFeb 27, 2025
  • 2 minute read

The text file contains header lines to indicate the type of database object referenced by the actual data lines following the header line. The header line consists of an entity name (shown within parentheses) followed by a series of attribute identifiers. The entity name loosely corresponds to a table (or tables) in the database, while the attribute identifiers resemble the column names in the tables. Note, however, that there is no strict correspondence between database tables and header lines. For example, a line in the text file related to an analog tag contains all the fields necessary to populate the Tag, AnalogTag, and other tables.

In the text file, a header line is followed by one or more lines containing actual data for the entity shown in the header line. Any particular entity can be repeated in the text file as many times as needed. For example, you can have a set of new analog tags inserted at the beginning of the file, and another set of analog tags deleted later in the file.

When you add lines to the end of the export file, make sure that the last line in the file is terminated by a carriage return/line feed. You can do this by pressing the Enter key on your keyboard at end of the line.

The value of the DefaultTagRate for an engineering unit must be one of the valid cyclic rates for analog tags. For more information, see Understand retrieval options in the AVEVA Historian Retrieval Guide.

Note: The name "$local" appears in the export file, instead of the real computer name, for any object that has a computer name that refers to the local computer. When an import is performed, "$local" is translated into the name of the computer that is the target of the import.

TitleResults for “How to create a CRG?”Also Available in