1582   RCB/GCB: Write of DatSet to the same value

Created: 24 May 2017

Status: Not Applicable

Part: Part 7-2 (2010; Edition 2)

Links:

Page: 133

Clause: 18.2.1.6

Paragraph:

Category: Issue for edition 2 of this part

Issue

For GCB, it is stated that "If the value of DatSet is set through a SetGoCBValues service to the same value, the ConfRev
value shall still be incremented.".

That sentence is not present for RCBs. It seems reasonable to have the same behaviour for GCBs and RCBs.

Proposal

Two options:

1) Remove the sentence "If the value of DatSet is set through a SetGoCBValues service to the same value, the ConfRev
value shall still be incremented." from 18.2.1.6 if it doesn´t make sense.

2) Add a new sentence to 17.2.2.7: "If the value of DatSet is set through a SetBRCBValues service to the same value, the ConfRev
value shall still be incremented."

Discussion Created Status
no controversial issue 30 Jun 17 Not Applicable
There is a major difference between the RCB and the GCB. In RCB case, only the client that reserved the RCB is allowed to modify the attributes of the RCB and only the client configuration is affected, while in the GCB case any client could modify the attributes of the GCB, and all the subscriber will be affected.
There is no technical need to harmonize the definitions. IEC 61850-7-2 Ed2.1 has been circulated for comments through the national commitees.
Modification of the standard should be done over that path.
12 Jun 17 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1