Issues #656

Publish/subscribe enum with value > 127

Added by Richard Schimmel over 2 years ago. Updated 7 months ago.

Due date:
03/07/2023 (about 7 months late)
Discuss in Upcoming Meeting:
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:


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 valueResolvedRichard Schimmel03/07/2023Actions

Updated by Thierry Dufaure over 2 years 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.


Updated by Joel Greene about 1 year 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.


Updated by Joel Greene about 1 year ago

GOOSE subscriber, including Fixed length.


Updated by Joel Greene about 1 year ago

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

Updated by IEC 61850 TPWG about 1 year ago

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

Updated by John Bruder about 1 year 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.


Updated by Thierry Dufaure 12 months ago

To respond to John:
"but users will need to know the "maximum standardized value" for each Enum"

It is not only about maximum standardized value, but minimum extended value. Users can check the EnumerationType from SCL since SCL Ed1.


Updated by Richard Schimmel 9 months ago

Added solution to update sGos9 with fixed length ENUM value >127 and negative.


Updated by Thierry Dufaure 9 months ago

The issue is not only for the scope of fixed-length GOOSE tests, but also for BER-encoded GOOSE tests.
Additionally, the test procedure shall indicate that the EnumType in the SCD is indicating ord values that are negative, or bigger than 129,...


Updated by IEC 61850 TPWG 8 months ago

  • Due date changed from 10/04/2022 to 02/07/2023

Updated by Richard Schimmel 8 months ago

Updated solution with new conditional test case: sGos16


Updated by Thierry Dufaure 8 months ago

I wouldn't make the test conditional ENS can be subscribed.
The ENS using values outside the INT8 range, could be in a DataSet with bolean; those boolean are indeed subscribed (application) - and ping-ponged.
When a subscriber cannot subscribe to a type, I think it is meant: the application cannot receive it, but the communication can. Otherwise it is difficut to shre and configure dataSet based on what the subscriber is allowing. Am I wrong?


Updated by IEC 61850 TPWG 8 months ago

  • Due date changed from 02/07/2023 to 02/21/2023

Test to be updated to remove ENS conditional.

Add a boolean to dataset and verify processing when ENS is not supported.


Updated by IEC 61850 TPWG 7 months ago

  • Due date changed from 02/21/2023 to 03/07/2023

Updated by Richard Schimmel 7 months ago

Updated solution - removed ENS condition and added boolean to the dataset when ENS is not supported


Updated by IEC 61850 TPWG 7 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF