Introduction

You can use the Excel file to add history extensions to a point and set its properties.

The system creates (column "model" is then mandatory) or updates (column "name" is then mandatory) a history extension.

You can create an extension

  • Using a Typespec
  • Using a template

You can wrap both into variables.

Example

In the following example:

  • We create a BooleanCov extension from a variable
  • We create a NumericInterval extension from the bog file history
  • We update an existing extension called "NumericCov" with a new changeTolerance.
History
Create/Update a history extension
modelnameintervalchangeTolerance








$BooleanCov
900
myNumericInterval
900

NumericCov
0.2

This is the model used in the templates folder for the NumericInterval:


Since the 46.17, the "history/" prefix is not needed anymore to target a component in the history.bog


Columns syntax

Create a column named "History" on the first line. Then you can define those following subcolumns

  • model: component which will be used to create/update the history extension (Mandatory only for a creation).

  • name: name of the history extension (Mandatory for an update).

  • capacity: capacity of the history extension.

  • changeTolerance: change tolerance of the numeric cov history extension (will be ignored for other types of history extensions).

  • interval: interval of the interval history extension (will be ignored for a cov history extension).

  • info subColumn.

  • slot subColumn.

Accepted values

  • model: (by priority during the export)

    • variable from the history column.

    • path to a template (from the history.bog).

  • name: String value (can be omitted  for a creation, in this case, the name from the Type or the template will be used).

  • capacity

    • String 'unlimited' (without quote) for an unlimited capacity.

    • or an integer value for a record count.

  • changeTolerance: double value.

  • interval: integer value in seconds.

  • info values.

  • slot values.

IMPORT

Create an History Extension

The model used to create the extension will be stored inside an “excelTemplate” slot. Therefore, the system knows how the extension was created when you do an export.

Change the type of an existing HIstory Extension

If the value in the model cell is different from the value previously saved in the history extension, the extension will be deleted and a new one with the desired type will be created.

Be careful with the model value,

  • ANY DIFFERENCE between the cell and the saved value will trigger the change. All the previous slot values will be lost.
  • if the sub component was not created using excel, importing the sub component with a model value will change the type the sub component in the station. Again, the previous slot values will be lost.

EXPORT

If they’re absent, some SubColumns will be added under certain circumstances:

  • the name SubColumn will always be added

  • If there is a change tolerance a changeTolerance SubColumn will be added

  • If there is an interval, an interval SubColumn will be added

Similarly to the Alarm Column, if there is at least one History Column and a component has more history extension than available History Columns, new History Columns will be created


Try it yourself !

Here is the file used in the above import example. Download it, try importing it and see the result.

For the 7th line, you will need to add an NumericInterval named myNumericInterval in the history template

For the 8th line, you will need to add a NumericCov named NumericCov in ModbusClientNumericWritable1 (import the file, add the alarm and import again to see the update in the alarm extension)

setHistoryExtensions.xlsx

Play a bit with it:

  • Add another History column and add a second history extension to a component.

setHistoryExtensions-solution.xlsx