Project

General

Profile

Issues #656

Publish/subscribe enum with value > 127

Added by Richard Schimmel over 1 year ago. Updated about 2 months ago.

Status:
In Progress
Priority:
Low
Due date:
10/04/2022 (Due in 5 days)
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
8-1
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

Item 6 from Christophe Camelis list;
Is such enum value allowed by the standard?


Related issues

Related to Server - Issues #657: Publish/subscribe enum with negative valueIn ProgressRichard Schimmel10/04/2022Actions
#1

Updated by Thierry Dufaure over 1 year ago

8-1 does not prevent it.
Even fixedLength encoding forsees 2 bytes for the transmission of enumeration value - allowing a range of: -32768 to 32767.

#2

Updated by Joel Greene 2 months ago

  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel
  • Priority changed from Normal to Low

There are no enum values > 127 currently.

Makes sense to test for forward compatibility - GOOSE, client, tool.

#3

Updated by Joel Greene 2 months ago

GOOSE subscriber, including Fixed length.

#4

Updated by Joel Greene 2 months ago

  • Related to Issues #657: Publish/subscribe enum with negative value added
#5

Updated by IEC 61850 TPWG about 2 months ago

  • Due date set to 10/04/2022
  • Closed Reason Test Procedure Update added
  • Closed Reason deleted (--Not Set---)
#6

Updated by John Bruder about 2 months ago

This could really complicate the MMS mapping.
8-1 says "the MMS data type shall be the minimum size required to contain the maximum standardized value".
Currently, all Enums map to an 8-bit signed integer.
But if one attribute exceeds 127, it will need a different MMS data type than all other Enums. This can be done, but users will need to know the "maximum standardized value" for each Enum.

Also available in: Atom PDF