DP Description in the AES screen

[NikolayLevchenko]

The description of the alarm seems to be taken from the DP element. Is it possible to take it from the DP itself (root datapoint, not element)?

I was planning to have "_common" config filled only on the DP itself and not copy the same description into every DP element.

Doing this in CTRL isn't hard, I can just use

Code: Select all

dpGetDescription("device.")

instead of

Code: Select all

dpGetDescription("device.element")

But I can't figure out how to achieve this in the AES screen

[leoknipp]

If a datapoint contains several elements with an activated _alert_hdl config you will have for all entries in the AEScreen the same text if only the information for the root element is used.
How can you then differ between the alerts when looking at the AES table?

When using master datapoints and instances you can define a description at the master datapoint at the elements.
On the instances a description is defined at the root node. During runtime the description is created by using information for the instance and the master datapoint based on the dpGetDescriptionMode used in the project (config entry in the [general] section.
For details please have a look at the WinCC OA documenation, e.g. for the CTRL function dpGetDescription().

Best Regards
Leopold Knipp
Senior Support Specialist

[NikolayLevchenko]

Leopold Knipp wrote:

If a datapoint contains several elements with an activated _alert_hdl config you will have for all entries in the AEScreen the same text if only the information for the root element is used.
How can you then differ between the alerts when looking at the AES table?

That's pretty straightforward. Let's say I have an inlet pressure transmitter.
I would create a datapoint "100-PT-001" and add "Inlet Pressure" as a description in _common config.
This datapoint would have several elements like:
.value
.HighHigh
.High
.Low
.LowLow
.Error

I would then add _alert_hdl config to the relevant elements (in this example to all, except for the first one).
In the _alert_hdl config "Came text" I would place texts like:
"Very High Threshold Reached"
"High Threshold Reached"
"Low Threshold Reached"
"Very Low Threshold Reached"
"Hardware Fault"

And then (when an alarm is triggered) in AES I would see a table with device tag column (100-PT-001), description column ("Inlet pressure") and alert text column (e.g. "Very Low Threshold Reached").
That to me is "object-oriented" approach
Am I looking at this wrong?

Leopold Knipp wrote:

When using master datapoints and instances you can define a description at the master datapoint at the elements.
On the instances a description is defined at the root node. During runtime the description is created by using information for the instance and the master datapoint based on the dpGetDescriptionMode used in the project (config entry in the [general] section.
For details please have a look at the WinCC OA documenation, e.g. for the CTRL function dpGetDescription().

This would be a bit tricky as we are not planning to use master datapoints.