Open jeanetiennelemaire opened 3 years ago
I'd like to read more about "The LDevice naming parameter : "Functional related naming" or "Product related naming"" Is it examplaind somewhere? The issue looks good to me.
I'd like to read more about "The LDevice naming parameter : "Functional related naming" or "Product related naming"" Is it examplaind somewhere? The issue looks good to me.
Hello, the difference between the two naming conventions are explained in the 61850-6 p.47 §8.5.3.
The purpose of this EPIC is to reconfigure an IED.name with all its dependencies which have been already imported within the EPIC RSR-51.
Prerequisites : an existing SCD file with at least one IED.name which contains at least one LDevice.inst and its associated DataTypeTemplates
The inputs of this service are:
A previous existing SCD file (required) defined by Header.id, Header.version and Header.revision The old IED.name of the new IED.name to rename (required) The LDevice naming parameter : "Functional related naming" or "Product related naming" (required) If LDevice naming parameter "Functional related naming" rename the /SCL/IED/AccessPoint/Server/LDevice.ldName as defined in RSR-15 elseIf LDevice naming parameter : "Product related naming" rename the /SCL/IED/AccessPoint/Server/LDevice.ldName as defined in RSR-15 This EPIC includes the
US RSR-16 : Rename the IED.name attribute as given in the input of the service "S21 : configure (edit) IED names)" in /IED.name section. Check that the new IED.Name is unique within the whole SCD file (IEC61850-6 p117). Rename the old IED.name attribute with the new IED.name as given as input of the service "S21 : configure (edit) IED names" in /Communication/SubNetwork/ConnectedAP.iedName US RSR-15 to rename the /SCL/IED/AccessPoint/Server/LDevice.ldName as defined in the input of the US. All new LD.ldName are unique within the subnetwork (IEC61850-6 ed.2.1 p47) The output of this EPIC is an updated SCD file.