IEC 104 section

Another remarkable feature of OpenSCD is the IEC 104 plugin, depicted in Figure below, which has been meticulously crafted in alignment with the IEC 61850-80-1 standard document. This plugin serves a critical role by facilitating the translation of device-oriented data models outlined in IEC 61850 onto the predefined ASDUs and services of IEC 60870-5-104 or IEC 60870-5-101 standards. This translation process allows users to seamlessly map attributes of CDCs onto the defined ASDUs of IEC 60870-5-104. By leveraging this plugin, users can effectively bridge the gap between different communication protocols, ensuring interoperability and compatibility between systems.

Once the necessary 104 points are incorporated using this plugin, users can utilize the Pro-mode feature to gain real-time visibility into the integration process. This means that as points are added, users can monitor their inclusion into the SCL file. This level of transparency empowers users to closely track the integration progress and ensure that the desired functionality is accurately represented in the final configuration.

to add the a 104 value, the following steps should be taken:

Navigate to the 104 editor plugin.
Click on the Add 104 Address button located in the bottom right corner.
Select the proper IED, Access Point, Logical Device, Logical Node and Data Object.
Choose the desired DO you wish to add.

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 in the example CDC below, the dialog box offers options for selecting both 35 and 36 in the "Monitor Ti" section, illustrating the flexibility of the protocol. It's worth mentioning that for the measurement values, the "Created Inverted Addresses (Monitor)" feature is not enabled, but it should be enabled for the digital points.

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 instance, for the specific CDC=ENC, there is only one Data Attribute for each Ti number that require the assignment of CASDU number and IOA addresse. But 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.