Datapoint Groups

Advantage:

With the aid of groups it is easier to manage and edit related datapoints. You can define datapoint groups any way you want to. You can also define groups within groups (see defining group filters). A collection of groups, for example, might include the following:

• All aggregates in hall A

• All datapoint elements intended for a trend display

• All motors in a workshop hall

• All pilot valves

• All meters

Filtering options

The filter searches for the specified term, for example, the datapoint type or specified pattern. A detailed description of using wildcards is given in the chapter on SQL.

What is the datapoint type?

Specify any existing datapoint type or leave the filter empty. In this case, the filter returns all datapoints of all types matching the DP pattern.

What patterns are valid?

The DP pattern (datapoint name filter) may be all DP string patterns valid in WinCC OA (for example, *.alert).

What group filters are allowed?

The filter can be any defined group. In this case, the DP pattern is left empty and the group is "resolved" internally, i.e. the definitions of the filter group are interpreted. The recursion depth of the group definition is limited to 20 levels. The number of datapoint groups per level is also limited to 20.

The levels are used to group multiple groups. This division facilitates selection of the desired groups. This allows you to pre-filter the main groups in the DP selector.

Also aliases can be used as group filters. All existing aliases corresponding to the filter criteria are shown.

You can also use datapoint groups to improve the filtering of the data to be displayed in the event and alarm fields. There is another filtering option that allows to display events and alerts for a specific datapoint group.

It is also possible to "query by groups" (see SQL panel ) for SQL queries.