Project

General

Profile

Bug #6263

GOOSE MinTime / Max Time - Probable discrepancy between Part-6 and Part-8

Added by Abhilash Appukuttan over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Standard options reduction required
Start date:
02/14/2023
Due date:
% Done:

0%

Estimated time:
ID:
Source:
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:

Update 61850-6 SCL schema

Standard(s):

IEC 61850-6

Needs More Information:
No
Assigned TF:
61850-6

Description

In Part 6, the MinTime and MaxTime is expressed as 'Decimal'

<xs:complexType name="tGSE">
<xs:complexContent>
<xs:extension base="tControlBlock">
<xs:sequence>
<xs:element name="MinTime" type="tDurationInMilliSec" minOccurs="0"/>
<xs:element name="MaxTime" type="tDurationInMilliSec" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
---
<xs:complexType name="tDurationInMilliSec">
<xs:simpleContent>
<xs:extension base="xs:decimal">
<xs:attribute name="unit" type="tSIUnitEnum" use="optional" fixed="s"/>
<xs:attribute name="multiplier" type="tUnitMultiplierEnum" use="optional" fixed="m"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>

However, in 8-1, the MinTime and MaxTime is an Unsigned32 / INT32U

MinTime Unsigned32 r o INT32U – As specified in the SCD
file for the GoCB, See 1
MaxTime Unsigned32 r o INT32U – As specified in the SCD
file for the GoCB. See 1

What shall the ICT process the values as? Input as Decimal and then pass it as Integer to the application?

Or does it makes sense to change the -6 to have these values as Integer?

If you look at Table 45 in -6, it does point to that way.

INT8, INT16, INT24, INT32,
INT64
INT8U, INT16U, INT32U

integer

An integer number, no decimal fraction (99999)


Proposal descriptions

Change MinTime and MaxTime base to Unsigned Integer 32 from Decimal in part 61850-6.

Also available in: Atom PDF