Project

General

Profile

Support #464

There is an issue about differentiation between “fixed” /preconfigured DataSets and those that can be changed in a SCT. Some ICT

Added by Herbert Falk over 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Already captured with TISSUE
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
21
Source:
IOP_2013
TF Unique ID:
21 # IOP_2013
WG10 Proposal:

Closed with 2015 IOP Tissues 1444 & 1445

Estimated Completion:
Discuss in Upcoming Meeting:
To discuss in WG10:
Short Proposal:

Tissue #1298
As summary: for an IED all data sets are either fix (modify=false) and then must be preconfigured, or they are always modifiable, deletable and creatable to the limit.
Proposed solution: change the explanation of ConfDataSet.modify by removing the word 'preconfigured'.

That means an IED has either ONLY fixed data sets and control blocks, or can be freely configured – which means also that all preconfigured data sets and control blocks can be removed and modified accordingly.

This interpretation is new for Ed. 2 and may be incompatible with ED. 1 implementations.

Standard(s):
Needs More Information:
Assigned TF:

Description

There is an issue about differentiation between “fixed” /preconfigured DataSets and those that can be changed in a SCT. Some ICTs expect specific DataSets to be returned to them. If the SCT changes these, the file will not import.
The issue is that there is currently no mechanism standardized to allow an ICT to declare that a specific DataSet must not be changed or deleted. The group believes that the valimport syntax should be added to DataSet definitions.

#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from New to Closed

Also available in: Atom PDF