Project

General

Profile

Issues #670

T1702 - Limit LTRK to one instance on a server

Added by Bruce Muschlitz almost 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Bruce Muschlitz
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
14.1
61850 Standard:
Triggering Tissue:
https://iec61850.tissue-db.com/tissue...
Final Decision:
Add sMdl22 test to match Tissue 1702 resolution
Initial Test Document:
http://www.ucaiug.org/org/TechnicalO/...
Updated Test Document:
Server Ed2.1 TP1.2
Test Case ID:
sMdl22
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

ssue

Issue has been raised by Adhoc Task Force Communication Supervision during the teleconference 18th of June 2020.
It is not expected to have several instances of LTRK in the server. However, this is not state clearly in the standard. Client IED should be able to find all service tracking objects in the same instance of LTRK on the server.

Proposal

Make a clear statement in 7-2 to indicate that at most one instance of LTRK shall exist in a server.

Files

TestProcedure_sMdl22_rev1.docx TestProcedure_sMdl22_rev1.docx 12.7 KB New sMdl22 Bruce Muschlitz, 05/13/2021 04:35 PM
#1

Updated by Richard Schimmel almost 3 years ago

  • Status changed from New to In Progress

I agree with the proposal attached. The server may have LPHD.proxy=T. So limit LTRK to one instance for all logical devices with LPHD.proxy=F

#2

Updated by Richard Schimmel almost 3 years ago

  • Status changed from In Progress to Resolved

TPWG agreement to resolve

#3

Updated by Bruce Muschlitz almost 2 years ago

  • Status changed from Resolved to Closed
  • Discuss in Upcoming Meeting changed from Yes to No
  • Updated Test Document set to Server Ed2.1 TP1.2
  • Closed Reason Test Procedure Update added
  • Closed Reason deleted (--Not Set---)

Also available in: Atom PDF