IEC 61850-7-3：电力自动化通信架构与通用数据类规范

5星 · 超过95%的资源需积分: 9 13 浏览量更新于2024-07-25 1 收藏 2.62MB PDF 举报

IEC TC57 61850-7-3标准，也被称为"电力系统自动化通信网络与系统 - 第7-3部分：基础通信结构 - 共享数据类 (IEC 61850-7-3:2010)"，是国际电工委员会（IEC）为电力系统自动化领域制定的一系列规范之一。该标准旨在定义一个分层的变电站通信架构，以提供抽象的数据类和服务定义，使得这些规范能够独立于特定的通信协议栈和对象。这种设计思想的关键在于，它允许不同厂商使用的通信协议和对象模型进行互操作，提高了整个系统的灵活性和标准化程度。该标准详细描述了变电站内的数据交换模型，包括过程层（IEC 61850-9-x）和站控层（IEC 61850-8-x）之间的接口。通过使用通用的数据类，如测量值、控制命令和状态信息，这些不同的通信层次能够无缝协作，从而支持智能电网的高效运行。基础通信结构确保了信息的可靠传输和一致性，对于保护系统安全、提高效率以及实现高级功能至关重要。 2011年的版本更新了标准的内容，提供了英文版EN61850-7-3:2011，同时考虑到了国际化的需求，包括法语和英语的翻译，以适应全球电力行业的应用。此外，该标准还强调了版权和复制的限制，所有标准的销售和分销由贝思出版公司独家负责，且旧版本DIN EN61850-7-3:2004-02被此新版本取代。在实施IEC 61850-7-3时，系统集成商和设备制造商必须确保他们的产品和服务符合这些共同数据类的要求，以保证变电站通信系统的兼容性和互操作性。这对于现代电力系统的可靠运行和数字化转型具有重要意义。同时，标准的遵循也促进了技术的标准化，降低了系统的维护成本和升级难度，提升了整体电网的性能和安全性。

DIN EN 61850-7-3:2011-08

EN 61850-7-3:2011

6.2.3 Detail quality

The reason for an invalid or questionable value of an attribute may be specified in more detail with

further quality identifiers. If one of these identifiers is set then validity shall be set to invalid or

questionable. Table 3

Table 3 – Relation of the detailed quality identifiers with invalid or questionable quality

shows the relation of the detailed quality identifiers with invalid or

questionable quality.

detailQual invalid questionable

overflow

outOfRange

X X

badReference

X X

oscillatory

X X

failure

OldData

inconsistent

inaccurate

overflow: this identifier shall indicate a quality issue that the value of the attribute to which the

quality has been associated is beyond the capability of being represented properly (used for

measurand information only).

EXAMPLE A measured value may exceed the range that may be represented by the selected data type, for example the

data type is a 16-bit unsigned integer and the value exceeds 65 535.

outOfRange: this identifier shall indicate a quality issue that the attribute to which the quality has

been associated is beyond a predefined range of values. The server shall decide if validity shall be

set to invalid or questionable (used for measurand information only).

EXAMPLE A measured value may exceed a predefined range, however the selected data type can still represent the

value, for example the data type is a 16-bit unsigned integer, the predefined range is 0 to 40 000, if the value is between

40 001 and 65 535 it is considered to be out of range.

badReference: this identifier shall indicate that the value may not be a correct value due to a

reference being out of calibration. The server shall decide if validity shall be set to invalid or

questionable (used for measurand information and binary counter information only).

oscillatory: to prevent overloading of event driven communication channels, it is desirable to detect

and suppress oscillating (fast changing) binary inputs. If a signal changes in a defined time (t

osc

)

twice in the same direction (from 0 to 1 or from 1 to 0) then it shall be defined as an oscillation and

the detail quality identifier “oscillatory” shall be set. If a configured number of transient changes is

detected, they shall be suppressed. In this time, the validity status "questionable” shall be set. If the

signal is still in the oscillating state after the defined number of changes, the value shall be left in

the state it was in when the oscillatory flag was set. In this case, the validity status "questionable”

shall be reset and “invalid” shall be set as long as the signal is oscillating. If the configuration is

such that all transient changes should be suppressed, the validity status “invalid” shall be set

immediately in addition to the detail quality identifier “oscillatory” (used for status information only).

failure: this identifier shall indicate that a supervision function has detected an internal or external

failure.

oldData: a value shall be oldData if an update is not made during a specific time interval. The value

may be an old value that may have changed in the meantime. This specific time interval may be

defined by an allowed-age attribute.

NOTE "Fail silent" errors, where the equipment stops sending data, will cause an oldData condition. In this case, the last

received information was correct.

inconsistent: this identifier shall indicate that an evaluation function has detected an inconsistency.

B55EB1B3E14C22109E918E8EA43EDB30F09DCCB7EF86D9

NormCD - Stand 2012-08

DIN EN 61850-7-3:2011-08

EN 61850-7-3:2011

inaccurate: this identifier shall indicate that the value does not meet the stated accuracy of the

source.

EXAMPLE The measured value of power factor may be noisy (inaccurate) when the current is very small.

6.2.4 Source

Source shall give information related to the origin of a value. The value may be acquired from the

process or be a substituted value.

process: the value is provided by an input function from the process I/O or is calculated from some

application function.

substituted: the value is provided by input of an operator or by an automatic source.

NOTE 1 Substitution may be done locally or via the communication services. In the second case, specific attributes with a

FC SV are used.

NOTE 2 There are various means to clear a substitution. As an example, a substitution that was done following an invalid

condition may be cleared automatically if the invalid condition is cleared. However, this is a local issue and therefore not

within the scope of this standard.

6.2.5 Test

Test shall be an additional identifier that may be used to classify a value being a test value and not

to be used for operational purposes. The processing of the test quality in the client shall be as

described in IEC 61850-7-4. The bit shall be completely independent from the other bits within the

quality descriptor.

6.2.6 Frozen by operator

operatorBlocked: this identifier shall be set if further update of the value has been blocked by an

operator. The value shall be the information that was acquired before blocking. If this identifier is

set, then the identifier oldData of detailQual shall also be set.

The operator shall use the data attribute blkEna to block the update of the value.

NOTE Both an operator as well as an automatic function may freeze communication updating as well as input updating. In

both cases, detailQual.oldData will be set. If the blocking is done by an operator, then the identifier operatorBlocked is set

additionally. In that case, an operator activity is required to clear the condition.

EXAMPLE An operator may freeze the update of an input, to save the old value before the auxiliary supply is switched off.

B55EB1B3E14C22109E918E8EA43EDB30F09DCCB7EF86D9

NormCD - Stand 2012-08

DIN EN 61850-7-3:2011-08

EN 61850-7-3:2011

6.2.7 Quality in the client server context

Communication

network

Client

Server

Input

unit

Information

source

Invalid /

questionable

overFlow

outOfRange

badReference

oscillatory

failure

Questionable

oldData

Substituted

IEC 808/03

Figure 1 – Quality identifiers in a single client-server relationship

Figure 1

The quality identifier shall reflect the quality of the information in the server, as it is supplied to the

client. shows potential sources that may influence the quality in a single client-server

relationship. "Information source" is the (hardwired) connection of the process information to the

system. The information may be invalid or questionable as indicated in Figure 1. Further abnormal

behaviour of the information source may be detected by the input unit. In that case, the input unit

may keep the old data and flag it accordingly.

In a multiple client-server relationship, as shown in Figure 2, information may be acquired over a

communication link (with client B). If that communication link is broken, client B will detect that error

situation and qualify the information as questionable/old data.

Communication

network

Client A

Server A

Input

unit

Information

source

Questionable

oldData

Client B

Communication

network

IEC 809/03

Figure 2 – Quality identifiers in a multiple client-server relationship

In the multiple client-server relationship, the quality of the data received from server A shall reflect

both the quality of the server B (acquired with client B) as well as its own quality. Therefore,

handling of prioritisation of quality from different levels may require further specification beyond that

included in this standard. For the identifier validity, the value invalid shall dominate over the value

questionable, since this is the worst case. For the identifier source, the higher level of the multiple

client-server relationship shall dominate over the lower level.

EXAMPLE Let A be the higher level and B the lower level. The quality from server B is invalid. If now the communication

fails (questionable, oldData) between server B and client B, the quality will remain invalid and not become questionable,

since the last information was not correct. Server A therefore will report the information as invalid.

B55EB1B3E14C22109E918E8EA43EDB30F09DCCB7EF86D9

NormCD - Stand 2012-08

DIN EN 61850-7-3:2011-08

EN 61850-7-3:2011

6.2.8 Relation between quality identifiers

Validity and source have a prioritized relation. If source is in the “process” state, then validity shall

determine the quality of the origin value. If source is in the “substitute” state, then validity shall be

overruled by the definition of the substituted value. This is an important feature, since substitution is

used to replace invalid values with substituted values that may be used by the client such as good

values.

EXAMPLE 1 If both questionable and substituted are set, this means that the substituted value is questionable. This may

happen if, in a hierarchical configuration, a substitution is performed at the lowest level and the communication fails on a

higher level.

EXAMPLE 2 If an invalid value is substituted, the invalid field will be cleared and the substituted field will be set to

indicate the substitution.

The quality identifier operatorBlocked is independent of the other quality identifiers.

EXAMPLE 3 An oscillating input may cause the invalid field to be set. Due to the continuing changes in the value, many

reports are generated, loading the communication network. An operator may block the update of the input. In this case, the

field operatorBlocked will also be set.

An example for the interaction between the quality identifiers and the impact of multiple client-server

relation is shown in Figure 3. In this example, it is assumed that a bay level device acts as a client

of the process level server and as a server to the station level client.

NOTE This is one example of a multiple client-server relationship; other multiple client-server relationships may exist, but

the behaviour will not change.

In case A, the input is blocked, the quality of the information is marked as questionable and oldData.

In case B, a substitution is done at process level. Now, the quality of the information to the next

higher level (the bay level) is marked as substituted (but good).

In case C, the communication between process and bay level fails. Between bay level and station

level, the information is still marked as substituted. In addition, questionable and oldData is set to

indicate that the (substituted) information may be old.

In case D, a new substitution is made at bay level. Now the quality of the information to the next

higher level is marked as substituted (and good) and is independent from the first substitution.

B55EB1B3E14C22109E918E8EA43EDB30F09DCCB7EF86D9

NormCD - Stand 2012-08

剩余84页未读，继续阅读

Abudoush

粉丝: 0
资源: 9

IEC 61850-7-3：电力自动化通信架构与通用数据类规范

IEC TC57 61850

IEC61850

IEC TC57 61850-7-1

IEC TC57 61850-7-2

IEC TC57 61850-7-4

IEC TC57 61850-8-1

IEC TC57 61850-9-1

IEC 61850-9-2

IEC 61850-3 - edition 2.pdf

IEC 61850-7-3：电力系统控制与通信相关数据模型标准

最新资源