Optional Values

Each of the Section Identifiers in a Trend’s definition can contain optional value(s) in addition to the Mandatory Values.

You only need specify any optional values if they are to differ from the defaults set in ViewX. Trend defaults are set using the Trends tab on the Options window (see Define the Default Settings for New Trends).

Each optional value in a TrendSpec definition has to be defined after the mandatory value(s) in the section to which they relate:

TREND
(
TRACE(<Data Mode>,<Y-axis Name>,
SOURCE (<Source Name>,<SOURCE Optional Values>), <TRACE Optional Values>),
XAXIS(<X-axis Mode>,<XAXIS Optional Values>),
YAXIS(<Y-axis Name>,<YAXIS Optional Values>),<TREND Optional Values>)
)

(You can place TRACE Optional Values before or after the SOURCE section, as long as they appear after the TRACE Mandatory Values. Place TREND Optional Values anywhere within the TREND section, so long as they appear outside of each of the other sections.)

Define each optional value using this basic format:

<Identifier> = <value>

where:

<Identifier> is a reserved word that uniquely identifies a specific property.

<value> is of the appropriate type of value for that particular Identifier.

The exact syntax varies, depending on the type of value that the optional identifier supports (see Optional Value Types and Assignments).

If you specify multiple optional values in any section, separate each entry with a comma.

The tables in the topics in this section list the Identifiers that are supported by each section in a Trend’s definition, along with the type of value that each Identifier supports. For more information, see the topics that are listed in the gray footer section at the bottom of this topic. Select the relevant entry to display the topic that you require.

You can specify any number and combination of optional values per section in your definition. Remember that you need to you use the same exact spelling for each Identifier’s name.

Any strings or expressions that reference an item in the ClearSCADA database are case sensitive. Section and other identifiers are case insensitive.

For examples that demonstrate how many of these optional values might be used in TrendSpec definitions, see Example Configuration.


Disclaimer

ClearSCADA 2017 R3