You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a 104 Engineer, I aim to modify the ldName associated with a particular LDevice. Presently, CoMPAS lacks support for this functionality, necessitating the inclusion of ldName configuration within the tool. Below outlines the steps involved in configuring and altering the ldName.
It's important to note that we don't want users to modify the inst of an LDevice. Changing the ldInst might create inconsistencies across the entire SCD file. Only modifications to ldName are permitted.
Another ticket has been created for developing this feature, which can be found below. We've clearly explained how this function can operate in that ticket. Please refer to it for more detailed information. #1326 (comment)
Describe the solution you'd like
It's crucial to note that the availability of the dialog box is contingent upon the presence of the ConfLdName service within the services section of the SCD file. In the event that this service is absent, users should still have access to the dialog box. However, in this scenario, all parameters will be displayed in a grayed-out and disabled state, preventing any modifications. This limited functionality allows users only to view the current ldName and inst without the ability to make changes. An example of the services section from an SCD file is displayed below.
To provide users with more context regarding the grayed-out ldName, it would be advantageous to include additional information below the ldName, similar to the description provided for the desc parameter. In the accompanying image, this supplementary information is visible beneath the ldName.
In this scenario, a comment similar to the following examples would be ideal:
1- IED doesn't support Functional Naming
2- IED doesn't support ConfldName service
3- IED doesn't support Functional Naming (ConfldName service)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As a 104 Engineer, I aim to modify the ldName associated with a particular LDevice. Presently, CoMPAS lacks support for this functionality, necessitating the inclusion of ldName configuration within the tool. Below outlines the steps involved in configuring and altering the ldName.
It's important to note that we don't want users to modify the inst of an LDevice. Changing the ldInst might create inconsistencies across the entire SCD file. Only modifications to ldName are permitted.
Another ticket has been created for developing this feature, which can be found below. We've clearly explained how this function can operate in that ticket. Please refer to it for more detailed information. #1326 (comment)
Describe the solution you'd like
It's crucial to note that the availability of the dialog box is contingent upon the presence of the ConfLdName service within the services section of the SCD file. In the event that this service is absent, users should still have access to the dialog box. However, in this scenario, all parameters will be displayed in a grayed-out and disabled state, preventing any modifications. This limited functionality allows users only to view the current ldName and inst without the ability to make changes. An example of the services section from an SCD file is displayed below.
To provide users with more context regarding the grayed-out ldName, it would be advantageous to include additional information below the ldName, similar to the description provided for the desc parameter. In the accompanying image, this supplementary information is visible beneath the ldName.
In this scenario, a comment similar to the following examples would be ideal:
1- IED doesn't support Functional Naming
2- IED doesn't support ConfldName service
3- IED doesn't support Functional Naming (ConfldName service)
The text was updated successfully, but these errors were encountered: