História stránky

...

Editing of all objects in the D2000 CNF process is performed in the configuration dialog box, a specific part of which is common for all editable objects, and another part depends on the type of edited object.

...

A text string describing the historical value. Maximum: 128 characters.
Possibility to use the Dictionary (to open, click the CTRL+L).

Status Text

...

Transformation palette

Selection of an index to for the transformation palette. See the topic Transformation palette.

...

Technical units of historical value. Maximum: 12 symbols. Possibility to use the Dictionary (to open, click the CTRL+L).

Limits

Technological limits are effective only for historical values, which are calculated by D2000 Archiv (evaluated and statistical historical values). There are 4 limits defined: VHL, HL, LL, and VLL. The limit can be defined either directly – , by the value entered into the input field, or its value can be determined by a system object (dynamic limit) – the button right from the input field.

...

As the limits can be dynamic (determined by the object value), a situation when where the relation VLL<LL<HL<VHL is not valid (the limits crossing) can occur. The historical value is then in the the Limit Problem state.

Note: Changing the value of the dynamic limit will not cause a new evaluation of limits and possibly a new value with a changed Limits attribute. The new value of the dynamic limit is taken into account only when archiving a new value.

...

• Archive object values - (primary archives) implement archiving of values of D2000 objects. Archiving can be either periodical or on value change.
• Calculate archived values by statistical function  (statistical archives) - implement applying the application of a statistical function to a defined object of Historical value.
• Calculate archived values by defined statement (evaluated archives) - support defining a custom formula on top of existing objects of Historical value type. The formula is defined in the Statement tab. The results of the calculation are again values that will be archived.
• Fill archive from the script (Value storage) - values can be written either from an ESL script or manually from the process D2000 HI.
  Note: all types of Historical values (also primary, statistical, and evaluated) can be modified from an ESL script or manually from the process D2000 HI) process.

Kotva
parametre_archivacie parametre_archivacie

Archiving parameters

...

• Archive - if the option Archive is checked, then the defined object will be archived. If it is not checked, the object will not be archived (the archiving is disabled).
• Write Start/Stop - enables/disables automatic writing of START or STOP values.
• Depository - the option allows enabling/disabling of storing values of the historical value into the depository database.
• These values are optionally written by the D2000 Archiv process to make it clear when it was shut down (and therefore why there is no data in the archive database for a given period).
  Note: In systems with redundant D2000 Archiv processes, it is recommended to turn this option off. The Arcsynchro utility is used to patch the hole in the archive database.
• Depository - the option allows enabling/disabling of storing values of the historical value into the depository database.

• Kotva
  trezorsegment trezorsegment

  Depository Kotvatrezorsegmenttrezorsegment Depository segment - allows specifying the depository database segment the values to be stored in if the parameter Depository is checked. The parameter can be used for the Oracle platform with depository database segments enabled or for the PostgreSQL platform with depository database segments enabled.

...

Kotva
ignore_identical ignore_identical

Ignore identical

Optimization of the processing of old values of primary archives coming from communication (automatically or as a result of the the GETOLDVAL command sent to the D2000 KOM process) or values of remote tags (as a result of the TELL command command GETOLDVAL sent to the D2000 Gateway Client process).
If the checkbox is checked, during the processing of the old value, the cache or archive database is queried to see whether the same value is already present there. If it exists, the value is discarded (and recalcs of statistical or calculated archived values that use this primary archive value are not performed either).
Note: Optimisation is useful e.g., for archiving of I/O tags from communication using the the IEC62056-21:2002 File I/O protocol. Its communication files contain several historical values (which the D2000 KOM process sends as old values) and one new value for every I/O tag.

...

Definition of a D2000 system object, values of which are to be archived. The object may be defined either by typing its name into the input edit field or by selecting it from the list of objects. To open the list of objects, click the button right from of the input field.

Object to archive or value source may be:

1. An object, the value of which is a simple type (Integer, Boolean, Real,...) - just one value is archived; therefore, therefore such an archived object is called a simple historical value.
2. An item of an object of Structured variable type - there is also just one value archived; therefore, therefore such an archived object is called a a simple historical value, too.
3. A column of an object of Structured variable type (e.g., SV.Strct[0]^ColName) - there are archived all values of the column are archived. Such an archived object is called a a one-column historical value.
4. An entire object of Structured variable type (e.g., SV.Struct) - there are archived all all values of the object are archived. Such an archived object is called a a structured historical value.

Note: The above-described fact implies , that the object to archive directly specifies the type of historical value - simple, one-column, or structured historical ones. So all changes in the configuration of the historical value have a direct effect on its functionality, mainly especially if the object is used in other historical values.

...

• Periodical  - writing values in the archive are periodical. The archiving process stores the archive object value in the archive in at defined time moments. Timestamp (the time of value) is not determined by the timestamp of the archived object value (e.g., an I/O tag), but by the time when the value is periodically written into the archive.
  
  Reading the values stored periodically by means of the D2000 system (ESL: GETARCHARR, GETARCHVAL, GETARCHROW, GETARCHCOL, GETARCHSTRUCT, D2000 ObjApi: GetArchivData, D2000 VBApi: VBApiGetArchData, D2000 WorkBook) follows the rule that the archive object's value out of time moments given by the period , is unknown (invalid). The result of the data reading is therefore given by the resampling and the begin (BT) and end (ET) time as follows:
  • resampling (step) = 0
    The reading results are all the values, the time of which belongs to the interval <BT, ET>.
  • resampling (step) <> 0
    The reading result is an array of values with timestamps contiguously:
    BT+0*step, BT+1*step, BT+2*step, ..., BT+N*step.
    The number of values is given by the end of the time interval (ET). The value of the array item is invalid if a record with the same timestamps does not exist in the archive database. If such a record exists, it is returned as a value of the array item. The above facts imply that when reading periodical data, it is necessary (advisable):
    • to adjust BT exactly to some of the object archiving moments, given by the period and time offset of the archiving.
    • resampling value (step) must be an integer multiple of the archiving period.
    • ET = BT + (N-1)*step, where N is an integer number: the number of values in the final selection.
    
    Note: The statistical archive, as far as reading is concerned, behaves as a periodical archive.

• Kotva
  sa_filter1 sa_filter1

  On value change - all the value changes of the archive object, which are not filtered out by the value filter, are stored in the archive.
  
  Reading of values stored by using a filter by means of the D2000 system (ESL: GETARCHARR, GETARCHVAL, GETARCHROW, GETARCHCOL, GETARCHSTRUCT, D2000 ObjApi: GetArchivData, D2000 VBApi: VBApiGetArchData, D2000 WorkBook) follows the rule that the archive object's value at any time (t) is given by (equals to) the last historical value at or before the given time (t). The data reading result is therefore given by the resampling and the begin (BT) and end (ET) time as follows:
  • resampling (step) = 0
    The reading results are all the values, the time of which belongs to the interval <BT, ET>, and one value before BT time, in case there is no value with a time exactly equal to BT time in the archive.
  • resampling (step) <> 0
    The reading result is an array of values with timestamps continuously:
    BT+0*step, BT+1*step, BT+2*step, ..., BT+N*step.
    The number of values is given by the end ET of the time interval. If a record with the same timestamps does not exist in the archive database, the value of the array item will be equal to the last value before the specific required time (however, the timestamp will be set accordingly).

...

If the Publish values option is checked, then the historical value publishes its last archived value in a way , that depends on the object to archive, as follows:

• For a simple historical value - , the object of the the Historical value type gets the last value.
• When archiving a one-column historical value - , the last archived values of individual items are filled into the relevant items of the column of a Structured variable type object defined by the Target object parameter.
• When archiving a structured historical value - , the last archived values of individual items are filled into the relevant items of an object of Structured variable type, defined by the Target object parameter.

...

The input field is enabled if the Publish values option is checked. It allows you to define an object , that will contains publish the values of historical the Historical value. When archiving a simple historical value, the target object must not be defined. However, it must be defined for one-column historical value, and for structured historical value - the size of the target object must be the same as the size of the object defined by the parameter Object to archive.

...

If the Publish values option is checked, then the historical value publishes its last archived value in a way , that depends on the object defined by the parameter Historical value as follows:

• For a simple historical value - , the object of the the Historical value type you are configuring gets the last value (unless the parameter Historical value is defined).
• When archiving a one-column historical value - the value, the last archived values of individual items are published in the relevant items of the column of a Structured variable type object defined by the Target object parameter.
• When archiving a structured historical value - , the last archived values of individual items are published in the relevant items of a Structured variable type object defined by the Target object parameter.

Note: To ensure the correct functionality of the Publish values feature for a one-column historical value (structured HV), the number of rows (columns) of the structured variable defined in the the Target object parameter must be the same as the number of rows (columns) of the object defined by the Historical value parameter.

...

The input field is enabled if the Publish values option is checked. It allows you to define an object , that will contains publish the values of historical the Historical value. When archiving a simple historical value, the target object must not be defined. However, it must be defined for one-column historical value and for structured historical value (see the Historical value parameter parameter) - the size of the target object must be the same as the size of the object defined by the parameter the Historical value parameter.

Kotva
prepocet_zad_vyrazom prepocet_zad_vyrazom

CALCULATE ARCHIVED VALUES BY DEFINED STATEMENT

The option allows defining a mathematic allows for the definition of a mathematical expression containing objects of Historical value  value type (the Statement tab). The expression can not contain references to any other D2000 objects. Calculation of the expression provides values to be archived.

For example:
We Let's have got two measurement points - two I/O tags, which are archived as historical values H.Flow1 and H.Flow2. If you need to archive the sum of both flows, you can use two methods:

1. Create an object of Eval tag type , that adds together the values of the I/O tags and then archives it.
2. Create an object of Historical value type with the expression of „H.Flow1 + H.Flow2“.

Both methods give the same result. A problem may occur when you need to modify e.g., the value of the object H.Flow1, which is already archived. If you used the first method, you must also manually change the value of the historical value. The second method automatically recalculates the expression and corrects the sum. So the D2000 Archive keeps the calculated (and also statistical) archives in synchronization with their source archives.

...

An object of Historical value type defined in this way can be either a simple or a one-column historical value. If the object is a one-column historical value, the expression may also contain references to other structured or one-column historical values with a row index of 0. During the calculation, the index is dynamically replaced by the current row number of the one-column historical value to recalculate. That allows defining the same expression for all column items.
Example of a structured expression: H.SourceColumn[0] + H.SourceStruct[0]^ColA

Kotva
zverejnovat_hodnoty zverejnovat_hodnoty

Publish values

If the option Publish values option is checked, then the historical value will publish its last value:

• If the option is not checked, the parameter Structure size defines whether the historical value is simple or a one-column one.
  If the Structure size is not defined, the historical value is a simple one. If it is defined, the object is a one-column historical value - it is possible to define a column of a Structured variable type object, a column of a structured historical value, or a one-column historical value. The number of rows of the calculated one-column historical value is given by the number of rows of the objects defined in the parameter Structure size.
• If the option is checked, the parameter Target column specifies whether the calculated historical value is simple or one-column.
  If the Target column is not defined, the historical value will be a simple one that gets the last value.
  If it is defined, the object will be a one-column historical value - it is possible to define a column of an object of Structured variable type. So, the number of rows of the historical value is given by the number of rows of the target structured variable.

...

Target column

Definition of an object , that will contain values of the historical value - see the the Publish values parameter. The parameter will be visible only if the Publish values option is checked.

...

An object of Historical value type filled from a script can be used as a storage of values that are not generated by archiving the values of other D2000 system objects, statistical calculations, or by other expression calculations. Values can only be only filled from an ESL script or manually from the D2000 HI process.

Value storage can be simple, one-column, or structured. This is defined by the parameter Archive structure or Target structure (it depends on the parameter Publish values)

...

Checking the option Publish values "renames" the parameter Archive structure to Target structure. The functionality of the parameter to define the structure of the archive is not changed, ; however, it is not possible to define an object of Historical value type.
If the Publish values option is checked, the parameter Target structure defines whether the historical value is a simple or structured one. If the Target structure is not defined, the historical value is a simple one and gets the last value. If it is defined, the historical value is a structured one and will publish the last value into the respective item of a defined structured variable.

...

The parameter is enabled when the parameters "Inserted values are periodicaland "and "Publish values" parameters are checked. If it is checked, the historical value will not publish its last value, but the value that is valid according to the current time. (This feature supports storing data with future timestamps in an object of of Historical value type - e.g., from an ESL script - and then the object "plays" these values in real-time).

Archive structure

The parameter appears when the Publish values parameter is not checked.
If

...

a value is no longer available for the current time, the

...

last value is published again (with a new timestamp).

Performance note: If script-filled Historical values (with data for the future) are used by other calculated Historical values, these will also be calculated for the future. If other Historical values (e.g. with values from communication) that change continuously (in real time) are used by the calculated Historical values, the D2000 Archiv is forced to recalculate the values for the future, according to the script-filled Historical values. The Archive playback setting will help reduce the load in such a case, since the values for the future will not be taken into account.

Archive structure

The parameter appears when the Publish values parameter is not checked.

• If it is not defined, the historical value is a simple one.
• The historical value is a one-column one if the parameter contains a simple one.The historical value is a one-column one if the parameter contains:
  • column of a structured historical value (e.g. H.Struct[0]^ColName)
  • one-column historical value (e.g. H.ColArchiv)
  • column of an object of Structured variable type (e.g. SV.Struct[0]^ColName)
• The historical value is a structured one if the parameter contains:
  • structured historical value
  • an object of Structured variable type

Target structure

The parameter will appears appear if the the Publish values parameter is checked. It allows defining an object , that will contain values of the historical value - see the Publish values parameter. If it is not defined, the historical value itself will contain the values.

...

In the top part of the tab, an input edit field is placed. It serves for entering to enter the expression , that determines the value of the historical value. The expression can contain functions, constants, and attributes - , but objects must be of Historical value type only. The expression may also contain extended syntax.

Objects

The button allows selecting the selection of an object of the D2000 system. The selected object is to will be inserted into the expression on at the current cursor position.
Note: Expression can contain objects of Historical value type only.

...

The button allows selecting a constant. Clicking it opens the dialog box containing the list of predefined constants. The selected constant will be inserted into the expression on at the current cursor position.

...

The button allows selecting a function. Clicking it opens the "List of functions" dialog box. The selected function is to be inserted into the expression on at the current cursor position.

...

The button allows selecting an attribute. Clicking it opens the dialog box containing the list of attributes. The selected attribute is to be inserted into the expression on at the current cursor position.

...

• Continuous - continuous (on the fly) calculation. Result values are calculated on the fly, and they are automatically available (depending on the system load). A disadvantage of the method is a higher demand for computing power (especially for frequent changes of primary historical values that enter into the expression).
• On demand - the calculation is executed, and the result is stored in the archive on demand. The demand can be generated by the the CALCONDEMANDSTAT action or by the RECALC command ) command.
  Note: historical values calculated "on-demand" should not have any depending on historical values calculated continuously because their results would be wrong.
• On read - the calculation is executed as a result of a read request. An advantage of this method is that values are not stored in the database, so they don't occupy any disk space. There is no possibility of re-calculation in case of writing delayed data into the archive. A disadvantage is a the necessity to read source data and calculate it for each read request. This method should be used for objects whose values are rarely needed.
  Note: historical value calculated "on-read" should not have any depending dependent historical values calculated continuously or "on-demand", because the result could be wrong in some cases (due to delayed data) or the calculation could be ineffective (multiple calculations of a single "on-read" object if it is used by several other historical values).

...

Note 1: For archives filled from the script, this setting does not directly affect anything - the data has a timestamp with which it was stored from the script. It, however, affects the calculation of statistics and whether statistics are calculated from the value at the edge of the interval.