UCAIug Issue Tracking System: Issueshttps://redmine.ucaiug.org/https://redmine.ucaiug.org/favicon.ico?15861924492024-02-29T15:03:39ZUCAIug Issue Tracking System
Redmine 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6726 (In Progress): New LN of group L (as "LTED") to re...https://redmine.ucaiug.org/issues/67262024-02-29T15:03:39ZVladan Cvejic
<p>Details:<br />Some functions need to know the current topology of the substation.<br />For doing that, <br />- 1 LN LTED is instanciated for each feeder connected to the busbar and for each busbar segment.<br />- ElNodeRef indicates the reference number of the electrical node of the busbar to which the LN is associated, calculated on the base of its actual topology (disconnector and circuit breaker position). <br />- ElNodeNum indicates the total number of electrical nodes into which a busbar is splitted on the base of its actual topology (disconnector and circuit breaker position). <br />- ElNodeVTRef is used by the LD publishing voltage information (SV or PhV). Only one LD can adopt the number of the Electrical Node. This LD published the busbar voltage reference for corresponding electrical node, indicating if this voltage is to be used as voltage reference for an Electrical Node. If not, its value is set to zero.</p>
<p>Argument: Needed for some PACS functions.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6725 (In Progress): Simultaneous change of InRef.setSrc...https://redmine.ucaiug.org/issues/67252024-02-29T15:03:21ZVladan Cvejic
<p>A simple static communication description in SCD based on “Input/ExtRef” combined with later binding is not always sufficient for all applications. Indeed, one of the most important use cases is redundancy management. For example, it may be necessary for a protection function to switch the subscription between SV streams published by two redundant MU or between GOOSE streams published by two redundant SCU. <br />The associated configuration used by Rte is based on the DO “InRef”. This DO allows to point to different IEC 61850 addresses and also to manage the test streams. The dynamic change to another SV or GOOSE stream is based on updating the Data Attributes (DA) “setSrcCB” and “setSrcRef”.</p>
<p>1. It seems required to have the capability of changing simultaneously the DA setSrcRef / setSrcCB of an InRef DO.<br />If not, there is a risk that the application use the wrong input signal while setSrcRef has changed and setSrcCB has not, for instance.</p>
<p>2. It seems required to have the capability of changing simultaneously the DA setSrcRef / setSrcCB of multiple InRef DO of a same LD.<br />If not, there is a risk that the application use for instance an input signal on SAMU A, and other inputs signal from SAMU B, which is discrepant from a system perspective.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6711 (In Progress): SCL Modelling of Fault Measurements...https://redmine.ucaiug.org/issues/67112024-02-14T13:31:14ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724779">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724779</a></p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6699 (New): Behavior of a function while being dynamica...https://redmine.ucaiug.org/issues/66992024-02-07T10:55:45ZKeith Gray
<p>LN.blk is active.<br />What happens with the functionality such as timers and outputs?</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6698 (New): Integrate work from AHTF Control Between Fu...https://redmine.ucaiug.org/issues/66982024-02-07T08:08:31ZKeith Gray
<p>Collect the work created by this AHTF and integrate it into 7-5 and 7-500. We need to locate the latest draft of the document, review that draft, and determine how to integrate it with our documents.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6687 (Waiting for Release): Incorrect signal direction ...https://redmine.ucaiug.org/issues/66872024-01-29T15:27:51ZKeith Gray
<p>From the TISSUE:</p>
<p>Issue</p>
<p>In IEC 61850-7-500:2017, Table 4 shows the extension of the control model by GOOSE messages between CSWI and XCBR. The direction of the arrows on the last two rows is incorrect.</p>
<p>Proposal</p>
<p>The GOOSE message direction should be going FROM CSWI.SelOpn/Cls.stVal TO the XCBR, and not the other way around. And the GOOSE message direction should be going FROM XCBR.Pos.stSeld TO CSWI.Pos.stSeld, and not the other way around. The direction of the flow of GOOSE messages is correctly depicted in Figures 21 and 22 that are associated with Table 4.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6686 (New): Description of the different control method...https://redmine.ucaiug.org/issues/66862024-01-23T17:02:54ZHenry Dawidczak
<p><a class="external" href="https://iec61850.tissue-db.com/tissues/1892">https://iec61850.tissue-db.com/tissues/1892</a><br />Tissue requests to remove TapOpStop from LN ATCC. This bring me to the need to describe the different methods to control OLTC in manual and automatic mode.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6684 (New): Proposal to deprecate 'LocSta' in X and Y g...https://redmine.ucaiug.org/issues/66842024-01-22T08:50:33ZMichael Haecker
<p>It is the purpose of 'LocSta' to define the level of control authority (remote control center vs. substation).<br />Since controls are to be managed by the corresponding CSWI LN instances, A-group LN instances respectively, control commands are not managed by X and Y class LN instances.</p>
<p>It is proposed to deprecate 'LocSta' in X and Y group LN classes.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6607 (New): Create DO indicating the source of synchron...https://redmine.ucaiug.org/issues/66072023-11-21T14:49:30ZVladan Cvejic
<p>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.<br />Proposal: add new DO (> 64 bit ) to LTMS and MMXU.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6555 (New): Behaviour of output contacts when LN is in ...https://redmine.ucaiug.org/issues/65552023-10-26T07:52:10ZKeith Gray61850-7-5 and 61850-7-500 - IEC61850-7-5 #6554 (Waiting for Release): SwModKey seems to overwrite...https://redmine.ucaiug.org/issues/65542023-10-26T07:51:39ZKeith Gray
<p>This was assigned to 7-5/7-500 TF during the 7-5/7-500 meeting in Kista, Sweden on 2023/10/25.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6545 (Waiting for Release): Propagation of detailQualhttps://redmine.ucaiug.org/issues/65452023-10-20T16:10:53ZMichael Haecker
<p>IEC/TR 61850-7-5 Ed.1, clause 5.1.4, specifies that detailQual is not to be propagated. This statement was made having considered a couple of use cases. It is valid for all of these.</p>
<p>Now TC95 WG2 ask to consider the use case of phasors.<br />Phasors are calculated from sampled values. For the receiver of a phasor measurement is of relevance to know the detail quality provided with sampled values.<br />TC95 WG2 ask to re-consider the statement of clause 5.1.4 adding an exception for phasor calculation.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6498 (Waiting for Release): Explanation text on the usa...https://redmine.ucaiug.org/issues/64982023-08-02T15:59:10ZMichael Haecker
<p>A chapter to be added to explain the usage of SwModKey.</p>
<p>cross reference to <a class="issue tracker-13 status-2 priority-2 priority-default overdue" title="IEC61850-7-5: Clarifications on the local/remote concept 6/8 (In Progress)" href="https://redmine.ucaiug.org/issues/6392">#6392</a></p>
<p>To be clarified whether there is a dependency (out of the datamodel hierarchy) IHMI.SwModKey > LD/LLN0.SwModKey > CSWI.SwModKey</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6395 (Waiting for Release): Figure 15 SelOpn and SelCls...https://redmine.ucaiug.org/issues/63952023-06-14T14:26:03ZKeith Gray
<p>I found an inconsistency in SelOpn and SelCls definitions between IEC 61850-7-500 Ed2 and 61850-7-4 Ed2.1. Can we discuss this during today’s meeting if time permits?</p>
<p>Figure 15 in 61850-7-500 shows SelOpn and SelCls with per-phase data attributes (as if it were an ACT). However, 61850-7-4 Ed2.1 defines SelOpn and SelCls as SPS. Even for single-phase control, the selection has to be per-switch. I believe this diagram needs to be updated.</p>
<p>Thanks,</p>
<p>Priyanka Nadkar<br />Development Lead Engineer<br />Research and Development<br />Schweitzer Engineering Laboratories<br />901 Center Park Drive, Charlotte, NC 28217 USA | Office: (704)-504-6804</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6376 (New): LN PDIF – setting for nominal currenthttps://redmine.ucaiug.org/issues/63762023-06-14T13:16:51ZVladan Cvejic
<p>LN PDIF contains DO LoSet and HiSet which represent Low (resp High) operate value setting [%] relative to the nominal current. <br />As the nominal current is not a setting in PDIF, how could a user set the value of the threshold for minimal (resp. maximal) differential current ?</p>
<p>In practice, the base current for PDIF is often the highest primary nominal current of the associated TC.</p>