Bug #3101: IEC61850.Tissue #1755 Event driven schedules – Add DO to stop schedule by event - IEC 61850 User Feedback Task Force - UCAIug Issue Tracking System

Bug #3101

IEC61850.Tissue #1755 Event driven schedules – Add DO to stop schedule by event

Added by Henry Dawidczak over 3 years ago. Updated over 1 year ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Start date:

08/10/2021

Due date:

02/10/2022 (over 2 years late)

% Done:

Estimated time:

ID:

Source:

TissueDB

TF Unique ID:

3 # TissueDB

WG10 Proposal:

Estimated Completion:

Discuss in Upcoming Meeting:

To discuss in WG10:

Short Proposal:

Include in edition 3 - not very urgent

Standard(s):

IEC 61850-7-4

Needs More Information:

Assigned TF:

Description

Part 7-4, page 169/482, clause 6.6.9 table 70:
The possibility to stop an event driven schedule by another event is missing.
Defining an additional DO would allow that starting and stopping a event driven schedule could be represented by two independent trigger events.

Example: A local DO event may represent a communication failure. The transition (False to True) of the DO referenced by InSyn could indicate that the communication has a failure (which should start a specific schedule). The transition (False to True) of the DO referenced by (new) DO InSynStop could indicate that the communication is again operating properly (which should cause the schedule to stop immediately).

Proposal descriptions

Add a new DO InSynStop after InSyn with the CDC ORG.
Presence condition shall be optional or conditional [C:if InSyn is modelled].

Add DO description:
“Object reference of the external trigger to stop the schedule
if the schedule is triggered by an event.
The Type of the external trigger Data Attribute
shall be BOOLEAN.”

Add Note: This Data Attribute may be located in the same IED (local issue how the event is communicated) or in another IED (needs GOOSE or Report to communicate the event from one IED to another IED).

Related issues