Improvement #672: Create DO indicating the source of synchronisation - IEC 61850 User Feedback Task Force - UCAIug Issue Tracking System

Improvement #672

Create DO indicating the source of synchronisation

Added by Maud Merley about 4 years ago. Updated over 1 year ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Standard extension required

Start date:

05/17/2021

Due date:

10/17/2021 (over 3 years late)

% Done:

Estimated time:

ID:

Source:

RTE

TF Unique ID:

46 # RTE

WG10 Proposal:

Estimated Completion:

Discuss in Upcoming Meeting:

To discuss in WG10:

Short Proposal:

Standard(s):

TR IEC 61850-7-500

Needs More Information:

Assigned TF:

61850-7-500 Ed2

Description

Proposal to add in LTMS a DO indicating the current source of synchronisation of the IED. This should be done in a consistent way with SynSrcId added in the SV ADSU in 9-2 ed2.1.
Proposal: add new DO (> 64 bit ) to LTMS and MMXU.

Proposal descriptions

- For LTMS, 7-4 Ed2.1 already addresses the issue.
- For MMXU, it does not seem to be the best place to have the proposed new DO. Maybe the proxy TCTR or TVTR in the subscriber is the good place to have the DO indicating the time source of the sampled value stream the instance is connected to. Also LSVS could be a better place to have this information. To be discussed in WG10.
- Issue should be addressed by TF 7-500

Related issues

Updated by Carlos Rodriguez del Castillo almost 4 years ago

Discuss in Upcoming Meeting changed from No to Yes

Updated by Carlos Rodriguez del Castillo over 3 years ago

Due date set to 10/17/2021
Category set to Standard extension required
Status changed from New to In Progress
Discuss in Upcoming Meeting changed from Yes to No
Proposal descriptions updated (diff)
To discuss in WG10 changed from No to Yes
Standard(s) set to IEC 61850-7-4

2021-09-28
- RTE has an use case where they want to know if all the sources are synchronized with the same clock
- 9.2 Ed2.1 has a bit to say global or local clock source, but there could be several local clocks, for example
- We could have one clock for samples synchronization and other for other functionalities
Agreed:
- For LTMS, 7-4 Ed2.1 already addresses the issue.
- For MMXU, it does not seem to be the best place to have the proposed new DO. Maybe the proxy TCTR or TVTR in the subscriber is the good place to have the DO indicating the time source of the sampled value stream the instance is connected to. Also LSVS could be a better place to have this information. To be discussed in WG10.
- A tissue on 7-4 could be created to eliminate the 'date' reference to IEC 61850-9-3 in the normative references section. Also to reference 9-3 instead of 61588 in LTMS 'TmSrc' DO definition. TO BE DISCUSSED WITH HENRY.

Updated by Carlos Rodriguez del Castillo over 3 years ago

2021-09-28:
- A discussion about the use of this new DO is ongoing. Should be or not be used for protection purposes..

Updated by Carlos Rodriguez del Castillo over 3 years ago

ID set to 46
TF Unique ID set to 46 # RTE

TF Unique ID set

Updated by Carlos Rodriguez del Castillo over 3 years ago

- Keep the issue open and RTE will provide more detail use case
- Take into account proposals from communication supervision task force regarding extension of LSVS