Issues #5153
Backward Compatibility of 61869-9 with 9-2 LE
Added by Herbert Falk over 2 years ago.
Updated over 2 years ago.
Discuss in Upcoming Meeting:
No
Closed Reason:
No Action Taken
Description
61869-9 is an edition 2.1 related standard. 61850-9-2 Edition 2.1 makes smpSyncSourceID optional as a protocol element, but in clause 9, makes it mandatory if the unit is synchronized via PTP. IEC 61850-6 ED 2.1 allows a SampledValue Control block to have the transmission of the srcID turned off.
Edition 1 of 9-2LE did not have a "..." within the ASDU sequence and therefore, for backward compatibility, the additional fields in 9-2 Ed 2.1 must be able to be disabled from being sent.
There is a need to provide a mechanism for 61869-9 to produce a true 9-2LE compatible stream.
It is proposed that the Clause 9 of 9-2 be changed to allow the additional fields to not be sent in order to be able to provide a backward compatible 9-2LE stream via SCL. Additionally, it is proposed that the protocol element be changed from OPTIONAL to DEFAULT NULL.
Facts:
1. 61869-9Ed1 normatively references 61850-9-2:2011 whose definition of SynchSourceID does not exist (it was added in Am1 and alternatly named gmidentity)
2. 61850-9-2 + Am1 clause 9 does not make it mandatory to use SynchSourceID/gmIdentity when PTP is used but merely "is strongly recommended"
3. 61850-6 + Am1 adds to Ed2.0 ability to specify Smvopts@synchSourceId (defaults to false) which allows inclusion of SynchSourceID/gmIdentity to SMV packet
Opinion: 61869-9 configuration requires use of "<SmvOpts sampleSynchronized="true" refreshTime="false" sampleRate="false" dataSet="false" security="false" synchSourceId=true/>" if the new field is desired. Omission of the synchSourceId=true (or assignment to false) guarantees that the field will not be sent.
Recommendation: A TISSUE against 61869-9 should be generated which prohibits SmvOpts@synchSourceId=true from appearing in the SampleValueControl specifying a backwards compatible configuration rate/nofASDUs/dataset regardless of whether PTP is enabled for the time synchronization mechanism
- Status changed from New to In Progress
- 61850 Standard deleted (
6)
I see no need to change a test procedure. move to tissue database?
- Status changed from In Progress to Closed
- Closed Reason No Action Taken added
- Closed Reason deleted (
--Not Set---)
TPWG 9-2 Ed2 Amd1 makes this configurable (table 14). No change required in the test procedures
Also available in: Atom
PDF