UCAIug Issue Tracking System: Issueshttps://redmine.ucaiug.org/https://redmine.ucaiug.org/favicon.ico?15861924492024-02-07T10:55:45ZUCAIug Issue Tracking System
Redmine 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 #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 #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 #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 #6556 (New): How to impact the data quality of a data wi...https://redmine.ucaiug.org/issues/65562023-10-26T09:00:10ZKeith Gray
<p>Ex: For a client, how to invalidate the data qualities of the data of an IED which cannot be reached any longer?</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 #6537 (New): Harmonizing expressions in 7-500 Ed.1https://redmine.ucaiug.org/issues/65372023-10-06T13:13:34ZMichael Haecker
<p>In IEC/TR 61850-7-500 Ed.1<br />the term</p>
<pre><code>"BIED" (Breaker IED means process near circuit breaker controller same as CBC)<br />is used in a mix with the term<br /> "CBC" (Process near circuit breaker controller IED according to IEC 62271-3 instead of BIED (breaker IED))</code></pre>
<p>and the term</p>
<pre><code>"SIED" (Switch IED means process near disconnector/earthing switch controller same as DCC and/or ESC)<br />is used in a mix with the terms<br /> "DCC" (Process near disconnector controller IED according to IEC 62271-3<br />instead of SIED (switch IED)) and<br /> "ESC" (Process near earthing switch controller IED according to IEC 62271-3 instead of SIED (switch IED)).</code></pre>
<p>In drawings only one of the parallel terms is used.</p>
<p>This is to propose to use only one of the parallel terms and to put a general note referring to the other one.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6497 (New): Explanation text of IEC/TR 61850-7-500 clau...https://redmine.ucaiug.org/issues/64972023-08-02T15:43:25ZMichael Haecker
<p>The explanation text to IEC/TR 61850-7-500 Figure 10 provided in clause 10.1.1.2 is not clear enough.<br />The last graph needs to be explained in a better way.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6408 (New): Clarification of addCausehttps://redmine.ucaiug.org/issues/64082023-06-20T13:37:59ZVladan Cvejic
<p>1. The standard identifies addCause, but its use should be explicitly defined by requirements associated to the application. The use and the expected behavior may be different for CB or disconnectors and also depend on other criteria.<br />example: "invalidPosition": depending on the object, a rejection of the command may be wished for a disconnector, but not for an opening command of a CB.</p>
<p>2. Besides, some cases has to be clarified:<br />25 "none" : why is this addCause necessary, normally they are associated at a refusal. Clarify use?<br />23 "abortion by communication loss": this addCause cannot be sent in case of loss of communication. Clarify use. Log?<br />26 "inconsistent parameter" conform if used for test of parameters of command or for sequence number of command (cybersecurity)<br />20 "non access authority" -> which are the associated controls?<br />=> Associated controls need to be explicitly specified for each addCause for interoperability reasons. Specially important for 20 and 26.</p>
<p>3. At least, how to access to addCause for other functions than the client and server concerned. Proposal : creation of attribute ENUM associated to addCause ?</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6382 (New): Clarification on the ctlModel 1/3https://redmine.ucaiug.org/issues/63822023-06-14T13:18:49ZVladan Cvejic
<p>What is the purpose of 'ctlModel' at X group level, Y group level respectively? Operator switchgear controls are managed by CSWI LN, so a Select to allow the operator to think twice before Operate is not needed on X group level.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6380 (New): Clarification on the ctlModel 2/3https://redmine.ucaiug.org/issues/63802023-06-14T13:18:12ZVladan Cvejic
<p>Add a statement about the relation between the 'ctlModel' of the controller LN and the 'ctlModel' of the proxy LN, e.g. CSWI.Pos--XCBR.Pos or ATCC.TapPos--YLTC.TapPos .The ctlModels can be different/must be the same?</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6379 (New): Clarification on the ctlModel 3/3https://redmine.ucaiug.org/issues/63792023-06-14T13:17:56ZVladan Cvejic
<p>Add a statement about the use of the 'ctlModel' that it is applicable for XCBR.Pos when subscribing to CSWI.Sel* and CSWI.Op*, but is bypassed when subscribing to PTRC.Tr . Note that both the Operate and the trip are of CDC ACT.</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>