Project

General

Profile

Issues #6816

cBr31 is mandatory but for not applicable "small" client controllers

Added by Richard Schimmel 5 months ago. Updated 4 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
7-2
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
cBr31
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

Some small client controllers are never interested in outdated/old reports and only need the actual values. The easiest method to get actual values after an association loss is to purge the buffer and GI.
Proposal: change cBr31 to conditional with condition: PIXIT-Resynch EntryID (add a new PIXIT entry).

The client shall either support writing the EntryID and/or PurgeBuf+GI.

#1

Updated by IEC 61850 TPWG 4 months ago

  • Status changed from New to Rejected

Rejected. Ability to recover data during loss of association is fundamental to buffered reporting.

Also available in: Atom PDF