|
| This Web Part is required for the workspace to function properly. It should not be removed. | | There are no more meeting occurrences to select from. |
|
|
|
|
|
|
|
Subject | |
|---|
|
| | I am not a member of IEC TC57,But I want to research IEC61850 protocol. Where can I find and download the documents about IEC61850?
|
|
| | |
| | Hi Shawn,
The draft IEC documents are located on the IEC web site, but are accessed by pasword. You need to contact
or
if you are in the states, or your county IEC representative to gain access to the draft documents
Kindest regards...kc |
|
| | |
| | Please comment on the use of Paper and Electronic Tags in the operation of the electric utility system. Make your comment as replies to this discussion. I will collect the co1850mments and draft a white paper...1-2 pages on the use of tags that will be used to guide the modeling of tags in IEC 6 |
|
| | |
| | We use several types of tags. Paper Tags and Electronic Tags are both used. Paper tags for a person near the field equipment and electronic tags for the people that can initiate control remotely. There are no standards for tags across the industry. A generic tag needs to contain a tag type or classification, a tracking number, the location, equipment, person placing the... |
|
| | |
| | Tags are used to logically prevent remote control operations on equipment that is out-of-service or while safety concerns prevent such operations. Tagging provides the ability to add tags to various devices. Tags can be modeled to block controls/setpoints, issue warnings on control/setpoint actions, or simply be informational. Measurements, data sets, data sources, equipment, and station objects can... |
|
| |  |
|
|
|
|
| | There are no items to show in this view of the "Part 5 Discussion Board" discussion board. To create a new item, click "Add new discussion" below. |  |
|
|
|
|
| Subject | |
|---|
|
| | plm
Located in Montreal
User since 11 Mar 2003 - 4 posts
Posted on 12 Aug 2004 at 01:59.28 PM
Part 6 specifies that an IED which is claimed compliant to IEC 61850 should at least support the ICD and SCD files. Others files are optional.
Question :
For a given project, if configuration modifications are done to an already configured IED by means of the IED configuration tool, let’s say his communication... |
|
| | |
| | dejong
Posted on 08 Sep 2004 at 08:50.02 AM
I was wondering where I can find the online versions of SCL.xsd and the other schema's mentioned as being normative in Annex A of the standard IEC 61850-6.
I think these files should be avaible in machine-readable form for parsers/validators.
Kind regards,
Kars de Jong |
|
| | |
| | I was wondering where i can find the online versions of SCL.xsd shema's
Kinds regards
Thierry Coste |
|
| | |
|
|
|
|
| Subject | |
|---|
|
| | Itziar
Posted on 27 Dec 2002 at 05:11.19 PM
How can I define a data-set?
When you have to define a "DSMembeRef", dou you have to include the name of the data-set at the beginning of the reference of the data or data attribute?
|
|
| | |
| | schubert
Posted on 07 Jan 2003 at 05:17.38 PM
Attachment_vti_cnf (4.00 KB)
The Users Group decides to support IEC 61850. So I will give you an IEC 61850 example you can find as attachment.
Best regards
Holger
Holger Schubert
Siemens AG
Germany
|
|
| | |
| | Itziar
Posted on 27 Dec 2002 at 05:03.44 PM
When you ask for a report (a BRCB class) by a general-interrogation you get the signal that has changed, but if you need the state of more data attributes, where (how) are they sent? Dou you have to add another data-set for sending the state?
|
|
| | |
| | herbfalk
Posted on 21 May 2003 at 01:12.22 PM
The idea of a BRCB and its buffered report is that you never lose changes. Therefore, the invocation of a GI does not impact the delivery of changes that occur while the GI is being delivered (they just get buffered and will be delivered when the GI completes).
This is why the buffered reports include a sequence number and sub-sequence number (you... |
|
| | |
| | plm
Located in Montreal
User since 11 Mar 2003 - 4 posts
Posted on 13 Apr 2004 at 08:36.50 PM
Part 7-2, clause 19.3, stipulates 32 characters for the LDName, the use of the "/" character and up to 32 characters to the right which gives 65 characters, the maximum size of a MMS visible-string.
But Part 7-2, clause 19.2, stipulates 29 characters for the length definition of the FCD.
If the... |
|
| | |
| | plm
Located in Montreal
User since 11 Mar 2003 - 4 posts
Posted on 13 Apr 2004 at 08:38.03 PM
Consider the following configuration data of a MHAI logical node :
ThdOddPhV.units.multiplier which contains 24 characters.
If the value of FC (2) is added with separators, the total length is 28 characters which lets only 4 characters for the LNName. There are no more characters left for the LN prefix... |
|
| | |
| | IDA
User since 20 Aug 2003 - 5 posts
Posted on 19 Apr 2004 at 02:33.27 AM
In the device modelling, if some physical device contains only one logical device, what is the difference between the LPHD and the LLNO which belong to the same logical device? I find that these two logic nodes have some same attributes, such as the health, nameplate.
|
|
| | |
|
|
|
|
| Subject | |
|---|
|
| | kevin
Posted on 05 Jul 2003 at 12:25.21 PM
How is it possible to add an array of visible strings to enumerated set points or status points to describe the meaning / use of each enumerated value?
|
|
| | |
| | kevin
Posted on 05 Jul 2003 at 12:26.29 PM
How is it possible to add an array of visible strings to set points or status points of type BITSTRING to describe the meaning / use of each bit in the string? |
|
| | |
| | kevin
Posted on 05 Jul 2003 at 12:31.51 PM
The majority of Common Data Classes in 7-3 are related to Control, Measurements or Plant Information. This is in alignment with part 7-4 which according to $5.2 is mainly concerned with this data and less so about settings.
However, by far the largest classification of Logical Nodes are related to protection which include settings as the majority for their... |
|
| | |
| | plm
Located in Montreal
User since 11 Mar 2003 - 4 posts
Posted on 15 May 2003 at 01:40.10 PM
Gomsfe had defined a CDC class AX related to Tags, i.e. an information applied by an operator on a device to advise clients not to operate the device.
In IEC61850, there is no such a CDC. Where are gone the tags in IEC61850 ?
The issue #735 (Switch Tissues 070802) in the switches folder mentions issues... |
|
| | |
| | schubert
Posted on 20 May 2003 at 08:05.13 AM
I am not sure what is your intent. But with
IEC 61850 you have some posibilities.
One is to switch the DATA Mode (part 7-4) of a
Logical Node or a whole Logical Device. There
are 5 different Modes available. The other one
are access rights, see part 7-2 subclause
7.3 "access control".
|
|
| | |
| | herbfalk
Posted on 21 May 2003 at 01:06.50 PM
During the final editor's meeting on 61850-7-2 and 61850-7-3 it was noted that the tagging model was not defined and had never been developed (either in CASM or GOMSFE), There was an intense discussion in regards to if the model should be developed and included as part of the balloted text.
The reality was that to develop and include a comprehensive... |
|
| | |
| | Cavica
Posted on 26 Sep 2003 at 07:20.20 PM
I have some doubts about the SOE objects implementation (Event Sequence). In the document Gomsfe, for example is not detailed the parameters of object Log Control Block (LCB), used to store the event sequence.
As would be the data structure of the object to store events (LCB)?
Carlos
|
|
| | |
| | schubert
Posted on 01 Oct 2003 at 07:39.22 AM
GOMSFE document is not longer supported. Did you read IEC 61850-7-2 (international Standard) . In this document you will find the Log-Service. If you have questions or doubts about the log-service in this document please post it.
|
|
| | |
|
|
|
|
| Subject | |
|---|
|
| | kevin
In many places part 7-4 has used the ISC class to model integer based settings, but this is incorrect as the ISC class is designed for CONTROLS not SETTINGS. Additional Common Data Classes are required in part 7-3 to model standard types of settings appropriate to the protection logical nodes, such as those available in GOMSFE and these should be reflected in the part 7-4 logical nodes.
|
|
| | |
| | schubert
It seems we are a perfect editor team, because
Kevins comment was solved some days before
his posting |
|
| | |
| | kevin
I have just received part 7-3 and I see the new ISG common data class has been introduced to satisfy this requirement.
I look forward to receiving part 7-4 to review its use.
|
|
| | |
|
|
|
|
| Subject | |
|---|
|
| | yin
User since 05 Sep 2003 - 11 posts
Posted on 10 Sep 2004 at 03:19.15 AM
I find there is some difference in the mechanism of GOOSE defined in
the IEC 61850 and UCA2.0, would you please tell me the reason?
1. In UCA2.0, the concrete format of the GOOSE message is specified, but
in IEC 61850, such definition can't be found.
2. In order to realize the high reliability of the transmission of GOOSE... |
|
| | |
| | herbfalk
Posted on 13 Sep 2004 at 12:38.23 PM
The UCA 2.0 GOOSE is called GSSE (Generic Substation Status Event) in IEC 61850. The IEC 61850 GSSE and UCA 2.0 GOOSE are 100% compatible.
The reason for the name change was that UCA 2.0 GOOSE (e.g. GSSE) only sends status (e.g. 4 value discrete value pairs) and thus is used for conveying digital status only.
WG10, WG11, WG12 desired a more generic... |
|
| | |
| | herbfalk
Posted on 13 Sep 2004 at 12:43.58 PM
Sorry about missing the retransmission question.
The real answer is that due to the timeAllowedtoLive (IEC GOOSE) and "t" in (IEC GSSE) these both indicate the time in which the next transmission should be expected. Thus, as long as implementation set this value appropriately (we advise our customers to set them to 2 * the actual retransmission... |
|
| | |
|
|
|
|
| Subject | |
|---|
|
| | IDA
User since 20 Aug 2003 - 5 posts
Posted on 20 Aug 2003 at 07:31.11 AM
I have read the 9-1 in detail, and I think it is more easier to be understood than 9-2. But I still feel confused about it .
In 9-1, there are two data sets are specified,they are universal data sets and status indication data set. In the status indication data set, I notice it include the attribute of... |
|
| | |
| | BrunnerC
Posted on 02 Sep 2003 at 03:40.59 PM
The purpose of the status indication dataset in 9-1 is, to be able to transmit status indication using the sampled value model. The idea was, that devices that only support sampled value services can transmit status information.
The timestamp there has the same use like a time stamp of status information transmitted with the other services, e.g.... |
|
| | |
| | IDA
User since 20 Aug 2003 - 5 posts
Posted on 04 Sep 2003 at 06:55.11 AM
I see,thank you,Mr.Christoph,however,I don't know for the SCSM,why IEC61850-9 is divided into two parts?Does it mean 9-1 have somthing drawback that it may be not fit for
the future substation?I read and compare 9-1 and 9-2, I think the biggest difference is that 9-1 is undirectional,but 9-2 supports Bi-directional,that... |
|
| | |
| | BrunnerC
Posted on 04 Sep 2003 at 09:08.31 AM
This is the first part of the answer. The attachement explains the difference between the mappings defined in IEC 61850-8 and in 61850-9-x.
|
|
| | |
| | BrunnerC
Posted on 04 Sep 2003 at 09:12.18 AM
This is the second part of the answer. The attachement describes the difference between IEC 61850-9-1 and 9-2. |
|
| | |
|
| | | |
