Project

General

Profile

Issues #3115

Forward compatibility to Amd1 server with pre-assigned URCB/BRCB

Added by Richard Schimmel about 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
7-2
Triggering Tissue:
Final Decision:
Split cRp16/cBr16 in a) and b) part and added PIXIT entry
Initial Test Document:
Updated Test Document:
Test Case ID:
cRp16, cBr16
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

An Ed2 Client shall also write the BRCB.resvTms and URCB.resv when these are pre-assigned in an Ed2Amd1 server.
For an Ed2 server such write will result in a response failure!
To be forward compatible the Ed2 client has 2 options:
1) always write resvTms/resv and ignore the response-
2) determine the server is Ed2Amd1 and reserve or Ed1/Ed2 and don't reserve


Files

#1

Updated by Richard Schimmel about 1 year ago

Discussed over e-mail with Bruce/Herb: UCAiug can't force Ed2 client to implement Amd1 behavior. We propose to add a PIXIT entry and add a conditional test case to make this behavior visible on the certificate. For sure Amd1 behavior shall not fail the Ed2 test.

#3

Updated by Bruce Muschlitz about 1 year ago

(new) PIXIT entry Rp25 only allows both or neither URCB and BRCB to support Ed2.1 SCL-reserved case. Should this be into separate responses for URCB and BRCB cases?
a) A Ed2.0 client might support only 1 of the 2 URCB/BRCB cases (and therefore PIXIT entry should be split)
b) It would be less confusing if we only pass devices which do both or neither (and therefore no change)

#4

Updated by Richard Schimmel about 1 year ago

TPWG solution updated to make cRp16a and cRp16b conditions mutually exclusive

#5

Updated by Bruce Muschlitz 5 months ago

  • Discuss in Upcoming Meeting changed from Yes to No

Also available in: Atom PDF