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 #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 #6606 (New): CPU monitoringhttps://redmine.ucaiug.org/issues/66062023-11-21T14:40:37ZVladan Cvejic
<p>Add a LN allowing to monitor CPU state of an IED (CPU load, temperature, available RAM and disc space, ...).<br />These informations could be used in client as local / remote HMI to monitor the substation.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6562 (New): Missing LN for Miniature Circuit Breaker (MCB)https://redmine.ucaiug.org/issues/65622023-10-26T10:17:53ZKeith Gray61850-7-5 and 61850-7-500 - IEC61850-7-5 #6560 (New): Multiple information sourceshttps://redmine.ucaiug.org/issues/65602023-10-26T09:02:25ZKeith Gray
<p>Today, each protection relay comes with its own XCBR model included. In a system, where Main1, Main2, Backup protections are provided from three devices, which XCBR model gets the preference?</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6559 (New): Modelling of a Lockout/trip seal-in relayhttps://redmine.ucaiug.org/issues/65592023-10-26T09:01:50ZKeith Gray61850-7-5 and 61850-7-500 - IEC61850-7-5 #6558 (New): How to model composed functionshttps://redmine.ucaiug.org/issues/65582023-10-26T09:01:23ZKeith Gray
<p>Ex.: undervoltage controlled busbar protection - The main protection principle is PDIF, but how to address the voltage aspect?</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6557 (New): Modelling of various MCB tripshttps://redmine.ucaiug.org/issues/65572023-10-26T09:00:49ZKeith Gray61850-7-5 and 61850-7-500 - IEC61850-7-5 #6377 (New): Update the Switchgear / Breaker Modelhttps://redmine.ucaiug.org/issues/63772023-06-14T13:17:15ZVladan Cvejic
<p>There exist the LNs XCBR/XSWI ("operative model") and the "supervision" LNs SCBR and SOPM. In addition, there are trip and control circuits. The number of instances needed depends on the switchgear technology (single phase switching/tripping and three phase control/tripping). The DOs in the LNs are not always in line with allocated tasks of the LNs. Therefore, a careful consistent and comprehensive remodeling is needed.</p>