Predefined PowerConfigs
A large number of predefined PowerConfigs are supplied with the software version. The PowerConfigs included with WinCC OA are normally sufficient for configuration of a project, because they have been designed to cover practically all settings. A few predefined PowerConfigs contain fixed parameters that cannot be changed again during configuration at the master data point (for example, Smoothing: type cannot be changed; Alert handling: ranges cannot be set - instead you must select a PowerConfig having the required ranges). Nevertheless a facility is provided for extending an existing PowerConfig or creating a new PowerConfig. A dedicated Editor is available for editing purposes (see PowerConfig Editor, basics).
The table below describes the predefined PowerConfigs and contains information on the dynamic attributes, which can be changed. (The Fixed option can be selected for every PowerConfig - see also Inserting a DPE PowerConfig).
In addition, the table lists the data types of the data point elements for which the PowerConfig concerned can be used (B, S, F - Bool, String, Float):
| Config | PowerConfig | Description | Applies to | Name |
| Archive settings | Archive settings | The archives and archive activation can be changed at each DP. When this PowerConfig is created, archival is enabled automatically at the data points, even if this option has not been selected at the master DP (logically archival is not performed at the master DP). | B, S, F | _da_archive |
|
Alert handling GENERAL: If you configure and activate an alert handling for a master DP, it is possible to delete only if you answer "yes" for the previous security question. The possible pending alerts are acknowledged and the alert (message) is set inactive and erased before deleting. If a configured alert handling is set inactive for a master DP element, this does not affect the respective DPs (the AH remains active because alerts could queue). Selecting the "Fixed" option transmits all changes of a master DP to the data points. Setting the AH of a master DP to inactive also sets the data points inactive. |
Alert handling | Alert handling can be activated at each DP. | B | _da_alert_hdl |
| Alert handling Var:alert class | With this option, it is possible to change alert handling activation and the alert class at each DP. | B | _da_alert_hdl_class | |
| Group alert handling | The data point lists and the activation of group alert handling can be changed. When specifying a DP pattern for the group alert handling, the notation _mp_DPT.** can be used for example. At the data points themselves the pattern is replaced by the data point name (the dot after the name of the master DP is crucial, otherwise the name is not substituted). For example: Configure alert handling at each element of the master DP, insert group alert handling at the root node of the master DP using the pattern specified above --> group alert handling that includes all elements of the DP is inserted at all data points of the root node. | S | _da_alert_hdl_sum | |
| Alert handling with 3 ranges | Alert handling activation and the upper and lower alarm limit can be changed subsequently. | F | _da_alert_hdl_3 | |
| Alert handling with 4 ranges | Alert handling activation, the upper and lower alarm limit and the lower warning limit can be changed. | F | _da_alert_hdl_4 | |
| Alert handling with 5 ranges | Alert handling activation, the upper and lower alarm limit and the upper and lower warning limit can be changed. | F | _da_alert_hdl_5 | |
| Alert handling discrete (pattern list) | Activation of discrete alert handling. The alert activation and the pattern list can be changed. | F | _da_alert_hdl_discrete | |
| Enum - 5 values (alerts inactive) | Deactivation of the alert handling. Five enum alert texts can be set. Enum values (integer - 0, 1, 2, 3, 4) can be set in the master data point only. Thereby the value in the 0 range will be set to minInt/minFloat. | F | _da_alert_hdl_enum | |
|
Periphery address Driver number: If a driver is configured with another driver number as with that given in the default session of the PowerConfig, no default values exist. The right curve has to be created manually especially at the interpolation curves. The remaining default values of msg_conv, cmd_conv and smooth are likewise empty. Address activation: The set active flag is assigned to all DPs when adding a PowerConfig (like it is in case of PowerConfig variables). If you now change the active flag of the master DP, the change is not assigned to DPs anymore. If you anyway want to have this change in your DPs, you can do this by choosing the "Transfer to all DPEs" entry from the context menu of the master data point (right mouse button on the master data point). |
free bus address | The driver type is first selected in the Configuration panel. After configuration, address activation, periphery address, subindex and address mode can be changed at each DP. | B, S, F | _da_address |
| <driver> input | The drivers supported by WinCC OA are available for <driver>. When this PowerConfig is created, the following Configs are created: address, distribution Config, smoothing. Address activation, periphery address, subindex and smoothing time (0 = old/new comparison, or for input > 0 then old/new comparison and time for flicker suppression enabled) can be changed afterwards. | B, F | _da_address_DRVIDENT_in | |
| <driver> input simple | Only the periphery address and the distribution Config are created (no sub-PowerConfigs). Address activation, periphery address and subindex can be changed afterwards. | B | _da_address_DRVIDENT_in_simple | |
| <driver> output | When this PowerConfig is created, the following Configs are created: address, distribution Config. Only the periphery address is configured (no sub-PowerConfigs). Address activation, periphery address and subindex can be changed afterwards. | B, F | _da_address_DRVIDENT_out | |
| <driver> output simple | Only the periphery address and the distribution Config are created (no sub-Configs). Address activation, periphery address and subindex can be changed afterwards. | B | _da_address_DRVIDENT_out_simple | |
| <driver> input | When this PowerConfig is created, the following Configs are created: address, distribution Config, conversion, smoothing. Address activation, periphery address, subindex and smoothing time (0 = old/new comparison, or for input > 0 then value-dependent filtering in % of the WinCC OA value range is enabled), WinCC OA and PLC value range (message conversion: interpolation curve) can be changed afterwards. Note that for PowerConfig configuration at the data point, the set WinCC OA value range is automatically used as the input range for interpolation-curve conversion after you have adopted the modified values (the values configured when the PowerConfig was inserted are overwritten). | F | _da_address_DRVIDENT_in | |
| <driver> input simple | Only the periphery address and the distribution Config are created (no sub-PowerConfigs). Address activation, periphery address and subindex can be changed afterwards. | F | _da_address_DRVIDENT_in_simple | |
| <driver> output | When this PowerConfig is created, the following Configs are created: address, distribution Config, conversion, WinCC OA value range. Address activation, periphery address, subindex, WinCC OA and PLC value range (command conversion: interpolation curve) can be changed afterwards. Note that for PowerConfig configuration at the data point, the set WinCC OA value range is automatically used as the input range for interpolation-curve conversion after you have adopted the modified values (the values configured when the PowerConfig was inserted are overwritten). | F | _da_address_DRVIDENT_out | |
| <driver> output simple | Only the periphery address and the distribution Config are created (no sub-PowerConfigs). Address activation, periphery address and subindex can be changed afterwards. | F | _da_address_DRVIDENT_out_simple | |
| Command conversion | Command conversion | An interpolation curve is inserted as the conversion type. The parameters (WinCC OA Minimum, PLC Minimum, WinCC OA Maximum and PLC Maximum) can be changed afterwards. | F | _da_cmd_conv |
| Message conversion | Message conversion | An interpolation curve is inserted as the conversion type. The parameters (WinCC OA Minimum, PLC Minimum, WinCC OA Maximum and PLC Maximum) can be changed afterwards. | F | _da_msg_conv |
| Default value | Var: default value; Fix: auto set | The default value can be changed for each DP if required. The default value is set automatically. | B, S, F | _da_default |
| Var: default value, auto set | The default value can be changed for each DP if required. Also with this PowerConfig, automatic setting of the default value can be enabled/disabled for each DP. | F | _da_default_always | |
| Data point function | DPF variable entry | Configuration of a DPE connection or statistical function for a DP. Afterwards can be changed all values, functions or results for each DP. | B, S, F | _da_dp_fct_variabel |
| WinCC OA value range | Value range | Adds a min.-max. value range to the element. The limits (value range maximum and minimum) can be changed later. | F | _da_pv_range |
| Smoothing | Smoothing | Smoothing time (value 0 = old/new comparison, or values > 0 then old/new comparison and the time for the flicker suppression) can be changed afterwards. | B | _da_smooth |
| Smoothing | Inserts value-dependent filtering with specification of the dead-band value. The tolerance can be changed subsequently (value 0 means old/new comparison, value > 0 equals the value of the dead band in value-dependent filtering). | F | _da_smooth | |
| User value range | - | - | - | - |
| Authorizations | - | - | - | - |
| Description, unit, (format) | Var: description, unit (and format) | Description, units and format can be changed at each DP. The pages Inserting a DPE PowerConfig and Example of mass configuration contain a detailed description of these PowerConfigs and how they work. | S, F | _da_common |
| Var: description, unit (and format) | Description and units can be changed subsequently at each DP. The format cannot be set for boolean DPEs and is thus not available as a dynamic attribute (that is why the format is placed in brackets). | B | _da_common | |
| Var: unit (and format); Auto: description | Units and format can be changed later. An automatic description is applied to each DPE. | B, S, F | _da_common_2 | |
| Var: description; Fix: unit (and format) | The description can be changed at each DP. Units and format remain fixed (unchangeable) at each DP. | B, S, F | _da_common_3 | |
| Var: description | The description can be changed at each DP. For PowerConfig configuration at the data point, an empty string is set after adopting the settings for units and format. | B, S, F | _da_common_4 | |
| Var: alias, unit, format and description | Alias, unit, format and description can be changed at each DP. | S, F | _da_common_5 | |
| Var: alias, unit, format and description | Alias, unit, format and description can be changed subsequently at each DP. | B | _da_common_5 | |
| Var: alias, unit (and format); Auto: description | Alias, unit and format can be changed at each DP. The format cannot be set for boolean DPEs and is thus not available as a dynamic attribute. An automatic description is applied to each DPE. | B, S, F | _da_common_6 | |
| Var: alias, description; Fix: unit (and Format) | Alias and description can be changed at each DP. Units and format remain fixed (unchangeable) at each DP. | B, S, F | _da_common_7 | |
| Var: alias | Alias can be changed at each DP. For PowerConfig configuration at the data point, an empty string is set after adopting the settings for description, units and format. | B, S, F | _da_common_8 | |
| General | not used at present | |||
| DPT-PC | The DPT-PC (data point type PowerConfig) can only be inserted at the root node of the master data point (node = data-type string) and allows the configuration of multiple elements that have been defined in the structure of the data point. Such a PowerConfig, covering the complete type, is included in the software version for the data point type ANALOG2 (S - ANALOG2 - DPT-PC). The DPT-PC check box is only operable if there is a DPT PowerConfig for the data point type concerned and no conflicts arise with other Configs. You can find more information on PowerConfigs covering the complete data point type on the pages Inserting a DPT PowerConfig or Creating a new PowerConfig for a DPT. | S | _da_DPT_ANALOG2 (predefined PowerConfig for ANALOG2 covering the complete data point type) |
There can be only one data point type PowerConfig for each data point type in WinCC OA. If a PowerConfig already exists at a data point element of a particular DPT that would also be set by a DPT-PC defined for this DPT, then the DPT-PC cannot be inserted. Using a DPT-PC, all the parameters of a data point can be set in one step.
