65   Deadband calculation of a Vector and trigger option

This tissue has following status: green

Created: 15 Mar 2005

Links:

Page:

Clause: General

Paragraph:

Category: Issue for edition 2 of this part

Issue: Deadband calculation of a Vector and trigger option

It is not explicitly defined that the two components cVal.mag and cVal.ang trigger reports and log entries independently. This should be defined in a note.

We have different scales for instCVal.mag/instCVal.mag (magSVC) and instCVal.ang/cVal.ang (angSVC) but we have just one db configuration value for both. It seems that we need also two, one for instCVal.mag and one for instCVal.ang

Proposal: In 7-3 a definition is missing were the trigger belongs too, ang or mag. It is a general issue for structured attributes.

Discussion Created Status
?
Ballot until Editor
During the WG meeting in Seoul, this TISSUE was rediscussed and it was agreed to add a different db configuration parameter for the ang attribute. The attribute is called dbAng 27 Apr 07 green
set to green after ballot closed 22 May 05 green
Ballot date added 11 May 05 final proposal 17 May 05
Final Proposal:
accepted as proposed by Christoph Brunner 29.03.05
Text will be added.
01 Apr 05 final proposal
(1) There are more places, where a data attribute triggering a report has several values (attribute components) that can trigger the report individualy. Just another example is the quality. We may improve the explanation in 7-2, table 19 by adding the following NOTE: "if a data attribute is a composite component, the change or update of a data attribute has to be understood as the change or update of one of the primitive components of the data attribute".
(2) Since dB configuration parameter is defined as a percent value, I believe we can keep one configuration parameter. Table 49 of 61850-7-3 already defines that the deadband calculation for cVal is done on the two components individually.
(3) The need for angSVC is questionable. The value range of ang is more or less always identical (basically -180° .. +180°). Could we define a fixed scaling?
I propose the following text for the final proposal:
"Partly accepted. (1) IEC 61850-7-2, Table 19 will be amended with the following note: "if a data attribute is a composite component, the change or update of a data attribute has to be understood as the change or update of one of the primitive components of the data attribute." (2) The configuration parameter db applies for both .mag as well as .ang. The text in IEC 61850-7-3, table 49, explaining cVal will be improved as follows: "The deadband calculation is done both on instCVal.mag as well as on instCVal.ang independently based on the same configuration parameter db""
29 Mar 05 red
Still an open issue. 15 Mar 05 red

 

Privacy | Contact | Disclaimer