Issues #6276

sGop13 does not consider that dataset with maximumAttributes number of FCD may be too big for GOOSE

Added by Hua Qin about 1 year ago. Updated about 2 months ago.

Due date:
Discuss in Upcoming Meeting:
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:


redmine 652 ( adds a mandatory test case sGop13 to configure GoCB with a dataset with at least maxAttribtues number of FCD dataset elements.
And it expects the DUT to send GOOSE messages.

But this does not consider the situation that the dataset may be too big to fit into a single GOOSE message and conflict with test case sGopN2.

The maxAttribtues is not only used for GOOSE but also for dataset used in RCB.
RCB can have a very big dataset because it can send out segment but GOOSE can not.

Suggest to update the test case with words "if accepted"



Updated by IEC 61850 TPWG about 1 year ago

  • Due date set to 03/21/2023
  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel

Needs further review.


Updated by IEC 61850 TPWG about 1 year ago

Needs further review. sGop13 likely nonconformant.

definition of maxAttributes, particularly note at the bottom of the table in part 6 may need a TISSUE.

sGop13 effectively restricts the size of all datasets in the device to 1518 when GOOSE is supported, which seems wrong.

max PDU size has implication here also for getDataSetValues.


Updated by IEC 61850 TPWG about 1 year ago

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

652 / sGop13 must be revised to consider PDU size as a limit to maxAttributes.


Updated by IEC 61850 TPWG 11 months ago

  • Status changed from In Progress to Resolved



Updated by Richard Schimmel about 2 months ago

  • Status changed from Resolved to Closed
  • Updated Test Document set to TP1.3

Also available in: Atom PDF