Add 104 Addresses to existing DOI/DAI (CDC = WYE and DEL)

[DavoodSooran]

Is your feature request related to a problem? Please describe.

As a 104 Engineer, I aim to incorporate Address Elements into an existing DOI/DAI that currently lacks these elements. Presently, CoMPAS does not support some critical CDCs, and we must establish their configurations within the tool. Below, the procedure for configuring CDCs=WYE and DEL have been outlined. Based on the IEC 61850-80-1 and IEC 61850-7-3 standard documents, it has been determined that these two CDCs will be mapped to IEC 104 using the CDC=CMV.

Describe the solution you'd like

The "Add 104 Address" button will appear below/right of the screen. If the user wants to add a 104 address, the user should simply click on the "Add 104 Address" button.

A new window will open, allowing you to select the DOI. This window is designed similarly to the dataset selection window. Below, you can see an example of how to select a Data Object (DO) with its Logical Node (LN), Access Point (AP), and Intelligent Electronic Device (IED).

Here, we will outline the mapping process for CDC=WYE and DEL for various DOs. When it comes to CDC=WYE, we have the option to select the DO=W, VAr, and A. The DAs will have the same naming for all three of these DOs, as this CDC is employed for Phase-to-Ground/Neutral-related measured values in a three-phase system.

For CDC=DEL, we can choose the DO=PPV, which is utilized for Phase-to-Phase-related measured values in a three-phase system. However, it's worth noting that these specific options are currently not visible or selectable within the IEC 104 module of CoMPAS.

Following this step, it is crucial to select the appropriate Monitoring Type Identifier (Ti) for the chosen DO. It's important to note that certain CDCs can be mapped to different Ti values within the IEC 104 standard. As shown below, the dialog box should offer options for selecting both 35 and 36 in the "Monitor Ti" section, illustrating the flexibility of the protocol. It's worth mentioning that for these CDCs, WYE and DEL, the "Created Inverted Addresses (Monitor)" feature should not be enabled because these represent measurement values. It's worth noting that, according to the IEC 61850-80-1 and IEC 61850-7-3 standard documents, these two CDCs will be mapped to IEC 104 using the CDC=CMV.

Upon adding the point, a new dialog box with various parameters will be presented. At this stage, it is essential to input both the CASDU number and IOA number. In some cases, specific DOs within particular CDCs may encompass more than one DA. For the specific CDC=WYE and DEL, there are three distinct Data Attributes that require the assignment of CASDU numbers and IOA addresses. These DAIs are as follows:

WYE Common Data Class: W, VAr and A data objects

• phsA.cVal.mag.f
• phsB.cVal.mag.f
• phsC.cVal.mag.f

DEL Common Data Class: PPV data object

• phsAB.cVal.mag.f
• phsBC.cVal.mag.f
• phsCA.cVal.mag.f

It's worth noting that the CASDU number serves to address a specific entity within the communication network, which could range from an entire substation down to a bay within a substation or even a single Remote Terminal Unit (RTU). Consequently, the combination of the CASDU number and IOA necessitates careful management to ensure accurate and conflict-free addressing.

For additional details on defining CASDU and IOA addresses, please refer to the following issue:
#1348

Suggestions for a specific user interaction

In scenarios where the same IOA address is employed for different DAs within the same CASDU number, the system should ideally generate an error message to alert the user. Examples of such error messages could be:

"IOA Address Already in Use"
"Duplicate IOA Detected"
"Cannot Use the Same IOA for Multiple DAs"
"IOA Address Conflict"

These messages would effectively communicate the issue and prompt the user to select a unique IOA address to ensure proper data mapping and avoid potential conflicts.

[DavoodSooran]

@Sander3003 @pascalwilbrink @Stef3st @juancho0202
FYI, the “Created Inverted Addresses (Monitor)“ feature is not applicable for the following ASDU/Ti numbers:

<20> := Packed single-point information with status change detection
<38> := Event of protection equipment with time tag CP56Time2a
<39> := Packed start events of protection equipment with time tag CP56Time2a
<40> := Packed output circuit information of protection equipment with time tag CP56Time2a

[DavoodSooran]

Both CDCs have been tested and worked fine.