Path: Home > GB/T > Page535 > GB/T 42151.81-2023 || Home > Standard_List > GB/T > Page535 > GB/T 42151.81-2023
| Std ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status |
| GB/T 42151.81-2023 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Communication networks and systems for power utility automation - Part 8-1: Specific communication service mapping (SCSM) - Mappings to MMS(ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3
| Valid |
Basic data | Standard ID | GB/T 42151.81-2023 (GB/T42151.81-2023) | | Description (Translated English) | Communication networks and systems for power utility automation - Part 8-1: Specific communication service mapping (SCSM) - Mappings to MMS(ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3 | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | F21 | | Classification of International Standard | 29.240.01 | | Word Count Estimation | 254,244 | | Date of Issue | 2023-12-28 | | Date of Implementation | 2024-07-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 42151.81-2023: Communication networks and systems for power utility automation - Part 8-1: Specific communication service mapping (SCSM) - Mappings to MMS(ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
ICS 29:240:01
CCSF21
National Standards of People's Republic of China
Power automation communication network and system
Part 8-1: Specific Communication Services Mapping (SCSM)
Mapping to MMS (ISO 9506-1 and ISO 9506-2)
and ISO /IEC 8802-3
(ISO 9506-1andISO 9506-2)andtoISO /IEC 8802-3
(IEC 61850-8-1:2020, MOD)
Published on 2023-12-28 and implemented on 2024-07-01
State Administration for Market Regulation
Released by the National Standardization Administration Committee
Table of contents
Preface â…ª
Introduction XII
1 Scope 1
1:1 General 1
1:2 Namespaces and versions 1
1:3 Code component distribution 1
2 Normative references 2
3 Terms and Definitions 7
4 Abbreviations 8
5 Review 11
5:1 Overview 11
5:2 MMS communication protocol set 12
5:3 Non-MMS communication protocol set 12
5:4 MMS objects used12
6 Communication protocol stack 13
6:1 Overview of protocol usage 13
6:2 Client/Server Services and Communication Protocol Sets 14
6:3 GSE management and GOOSE service communication protocol set 17
6:4 Time synchronization 20
6:5 Sampling value management and service communication protocol set 21
7 Object 23 of IEC 61850
7:1 Server 23
7:2 Logical devices 24
7:3 Logical node 24
8 Mapping of IEC 61850-7-2 data attributes 26
8:1 Attribute mapping specified in IEC 61850-7-226
8:2 Mapping of quality common data attribute types specified in IEC 61850-7-350
9 Server Class Model 51
9:1 Server mapping 51
9:2 Server class attributes 51
9:3 Server services - reading server directory 51
10 Association Model 53
10:1 Correlations regarding communication protocol sets 53
10:2 Client/server communication protocol set bilateral association model 54
10:3 Bilateral association model for GSE management communication protocol set 56
10:4 Bilateral correlation model for time synchronization 56
10:5 Multicast association model 56
11 Logical device model 56
12 Logical node model 56
12:1 General logical node class 56
12:2 General logical node class attributes 56
12:3 General logical node services 57
13 Data objects, data attributes, and sub-data attribute models 59
13:1 Common Data Object Classes 59
13:2 Common data attribute classes 59
13:3 Common subdata attribute class 59
13:4 General Data Object Class Services 60
14 Dataset Class Model 61
14:1 Dataset Class 61
14:2 Dataset properties 61
14:3 Dataset Services 61
15 Service Tracking Model 64
15:1 Overview 64
15:2 Public Service Tracking 64
15:3 Cache Report Tracking Service Mapping 69
15:4 Uncached Report Tracking Service Mapping - UTS 70
15:5 Log control block tracking service mapping 71
15:6 Log tracking service mapping 72
15:7 GOOSE control block tracking service mapping 72
15:8 Settings Group Control Block Tracking Service Mapping 73
15:9 Multicast sample value control block tracking service mapping 73
15:10 Deprecated Unicast Sample Value Control Block Tracking Service Map 74
16 Setting group control class model 75
16:1 Setting group control block definition 75
16:2 Setting group control services 75
17 Reporting and logging model 76
17:1 Reporting Model - Reporting Control Block 76
17:2 Reporting Services 79
17:3 Log model 82
18 Mapping of the General Substation Event (GSE) model 89
18:1 Generic object-oriented substation events 89
19 Transmission of sampled value class models 100
19:1 Sample value 100
20 Control class model 105
20:1 Overview 105
20:2 Controlling Service Parameters 106
20:3 Mapping of control objects and control object references 106
20:4 Control Service Mapping 107
20:5 Select 109
20:6 Selection with value 110
20:7 Cancellation113
20:8 Operation 116
20:9 Command termination 118
20:10 Time activation operations 120
20:11 Additional cause diagnosis in negative control service response 124
20:12 Control Service Tracking 127
21 Time and time synchronization models 128
22 Naming convention 128
23 File Transfer 128
23:1 File transfer model 128
23:2 File Services 130
24 Consistency 136
24:1 Identification 136
24:2 PICS 137
24:3 PICS Statement 167
25 Substation Configuration Language (SCL) 169
25:1 SCL files and SCL extensions 169
25:2 Overview 169
25:3 SCSM specific address element definition 169
25:4 Subnet protocol types 173
25:5 SCSM namespace 173
Appendix A (normative) Application protocol specification for GOOSE and GSE management 174
A:1 ASN:1 definition 174
A:2 BER encoding rules 176
A:3 Fixed length encoded GOOSE message 177
A:4 Consistency181
Appendix B (informative) Multicast address selection 182
Appendix C (Normative) Overview of ISO /IEC 8802-3 frame structure for GSE management and GOOSE 183
C:1 Protocol Data Unit (PDU) 183
C:2 PDU field 189
Appendix D (Informative) SCL Conformance 192
Appendix E (informative) Time scale and epoch 193
Appendix F (Normative) Type extensions to ISO 9506-1:2003 and ISO 9506-2:2003 194
F:1 Overview 194
F:2 ISO 9506-1 (Service Definition) 194
F:3 ISO 9506-2 (protocol specification) 194
Appendix G (informative) SCL file use case 196
Appendix H (Informative) General Substation Status Event (GSSE) - Repealed 220
Appendix I (Informative) Certificate Management 221
Appendix J (Normative) Routable GOOSE and SV 222
J:1 Overview 222
J:2 Application Protocol Set 222
J:3 GOOSE, SV and Management Application Protocol Set 222
Appendix K (Normative) Compatibility of different versions of this document 232
K:1 Overview 232
K:2 Compatibility rules 232 of IEC 61850-8-1
K:3 Special Compatibility Rules 237
Reference 238
Figure 1 Overview of functions and protocol set11
Figure 2 OSI reference model and protocol set 13
Figure 3 Logical node mapping algorithm 24
Figure 4 Functional constraint sequence table 25
Figure 5 The relationship between LCB attributes and IEC 61850-7-2 log definition 83
Figure 6 GetGoReference service primitive 91
Figure 8 Event transmission time 96
Figure 9 SendGOOSEMessage service primitive 96
Figure 10 Publisher state machine of GOOSE service 97
Figure 11 Subscriber state machine of GOOSE service 97
Figure 12 Read multicast sample value reference service primitive 101
Figure 13 GetMsvElementNumber service primitive 103
Figure 14 Mapping from ACSI file reading to MMS file opening, file reading, and file closing 131
Figure 15 Mapping of ACSI write file service 134
Figure A:1 BER coding rule format 177
Figure A:2 Identification octet format 177
Figure C:1 GOOSE publisher’s ISO /IEC 8802-3 frame format 183
Figure C:2 ISO /IEC 8802:3 frame format for GOOSE publisher with HSR link redundancy 185
Figure C:3 ISO /IEC 8802:3 frame format for GOOSE publisher with PRP link redundancy 187
Figure C:4 VLAN flag 189
Figure C:5 Reserved 1 structure 191
Figure J:1 Universal byte order for session protocols 223
Figure J:2 Structure of the routable GOOSE/SV session protocol 224
Figure J:3 IP header format 231
Figure J:4 TOS byte field definition of RFC2474 and RFC3168 231
Table 1 MMS objects and services used in this document12
Table 2 Services that require the use of the client/server communication protocol set14
Table 3 Services and protocols for client/server communication application protocol set15
Table 4 Services and protocols for the client/server TCP/IP transport protocol set17
Table 5 Services requiring GSE management and GOOSE communication protocol set 18
Table 6 Services and protocols for GSE management and GOOSE communication application protocol set 18
Table 7 RFC1240 application protocol set option 18
Table 8 GOOSE/GSE transport protocol set 19
Table 9 UDP domain implementation requirements 20
Table 10 Time synchronization application protocol set 20
Table 11 Time synchronization transmission protocol set 21
Table 12 Services that require the use of sampled value management and sampled value communication protocol sets 21
Table 13 Services and protocols of the sample value management and multicast sample value communication application protocol set 22
Table 14 MSV transport protocol set 22
Table 15 ACSI basic type mapping 27
Table 16 Physical communication address structure for layer 2 communication 30
Table 17 Associated ACSI service error mapping 31
Table 18 Release service error map 32
Table 19 Read name list conflicts with IEC 61850 object class and object range 32
Table 20 Read Name List Service Error Mapping 33
Table 21 Reading named variable list object error mapping 34
Table 22 Writing named variable list object error mapping 34
Table 23 Define named variable list service error mapping 35
Table 24 Read Named Variable List Attribute Service Error Mapping 36
Table 25 Delete named variable list service error mapping 37
Table 26 Read service error mapping 38
Table 27 Write service error mapping 39
Table 28 Read variable access attribute service error mapping 41
Table 29 Log Service error mapping 41
Table 30 File Directory Service Error Mapping 42
Table 31 ACSI service error to get file service error mapping 43
Table 32 Mapping of open file service errors to ACSI service errors 43
Table 33 ACSI service error to read file service error mapping 44
Table 34 ACSI service error to close file service error mapping 44
Table 35 ACSI service error to delete file service error mapping 45
Table 36 IEC 61850-7-2 time quality encoding 46
Table 37 Trigger condition code 47
Table 38 Report contains reason code 47
Table 39 Log contains reason code 47
Table 40 Physical communication address 48 for UDP/IP communication
Table 41 Report control block option encoding 49
Table 42 Sample value option encoding 49
Table 43 Detection condition code 49
Table 44 IEC 61850-7-3 quality code 50
Table 45 ACSI read server (logical device) to MMS mapping 52
Table 46 ACSI read server directory (file) to MMS mapping 53
Table 47 Communication protocol set corresponding to the association model 53
Table 48 ACSI associated service to MMS mapping 54
Table 49 ACSI release service to MMS mapping 55
Table 50 Read Named Table Class 57 for reading logical node directory services
Table 51 ACSI read logical node directory (data object) service to MMS mapping 57
Table 52 ACSI read all data value service to MMS mapping 59
Table 53 Mapping of read data value service parameters 60
Table 54 Mapping of write data value service parameters 60
Table 55 Mapping of read data directory service parameters 61
Table 56 Mapping of read data set value service parameters 62
Table 57 Mapping of write data set value service parameters 62
Table 58 Create mapping of data set service parameters 63
Table 59 Deleting the mapping of data set service parameters 63
Table 60 Mapping of directory service parameters of read data set 64
Table 61 Mapping of common data class CST to MMS type definition 65
Table 62 Mapping of ACSI service type values 65
Table 63 Mapping of ACSI service error values 68
Table 64 Mapping of public data class BTS to MMS type definition 69
Table 65 Mapping of public data class UTS to MMS type definition 70
Table 66 Mapping of public data class LTS to MMS type definition 71
Table 67 Mapping of public data class GTS to MMS type definition 72
Table 68 Mapping of public data class STS to MMS type definition 73
Table 69 Mapping of public data class MTS to MMS type definition 73
Table 70 Mapping of public data class NTS to MMS type definition 74
Table 71 SGCB to MMS type definition mapping 75
Table 72 BRCB to MMS type definition mapping 76
Table 73 URCB to MMS type definition mapping 78
Table 74 Access result sequence 80 for variable list name reporting
Table 75 MMS log control block definition 83
Table 76 Mapping of log enable values 84
Table 77 ACSI log entry mapping 85
Table 78 Generic mapping for ACSI log model services 87
Table 79 Mapping of query log request parameters by time 88
Table 80 Mapping of response parameters 88
Table 81 Mapping of query log request parameters by time point 88
Table 82 Log consistency requirements 89
Table 83 MMS type description definition for GoCB MMS structure 90
Table 84 Read GOOSE reference service mapping 92
Table 85 Read GOOSE reference 92
Table 86 Read GOOSE element number service mapping 94
Table 87 Read GOOSE element number 95
Table 88 GOOSE service parameter mapping 98
Table 89 Read sample value reference service mapping 101
Table 90 Read sample value reference service 102
Table 91 Read sample value element sequence number service mapping 103
Table 92 Read sample value element number 104
Table 93 Control service parameters 106
Table 94 Mapping of IEC 61850-7-2 control model to MMS control components 106
Table 95 Control service mapping 107
Table 96 Select service parameter mapping 109
Table 97 Select service mapping 109
Table 98 Select parameter mapping with value 110
Table 99 Select service mapping with value 111
Table 100 Access result specification with value selection, operation and cancellation 113
Table 101 Cancel service parameter mapping 113
Table 102 Unmapping service 114
Table 103 Operation service parameter mapping 116
Table 104 Operation service mapping 117
Table 105 Command to terminate service mapping 119
Table 106 Time activation operation service parameter mapping 120
Table 107 Time activation operation service mapping 121
Table 108 Time activation operation termination service mapping 123
Table 109 Final application error variable structure definition 125
Table 110 Mapping of ACSI extra reason values 126
Table 111 Mapping of public data class CTS to MMS type definition 128
Table 112 Mapping of ACSI file classes to MMS file objects 129
Table 113 Reserved file suffix 129
Table 114 Mapping of ACSI read file service parameters 132
Table 115 ACSI read file service mapping 132
Table 116 Mapping between read file service errors and MMS service errors 133
Table 117 Mapping of ACSI write file parameters 134
Table 118 ACSI delete file service mapping 135
Table 119 Mapping of ACSI read file attribute value parameters 135
Table 120 Mapping of ACSI directory entry list 136
Table 121 Application protocol set PICS 137
Table 122 Time synchronization application protocol set PICS 138
Table 123 Transmission protocol set PICS 138
Table 124 MMS initialization request general parameters 139
Table 125 MMS initialization response common parameters 140
Table 126 MMS initialization error common parameters 141
Table 127 Conformance of MMS support services Table 141
Table 128 MMS parameters CBB 147
Table 129 Read name table consistency statement 148
Table 130 Reading capability table conformance statement 149
Table 131 Read domain attribute consistency statement 150
Table 132 State consistency statement 151
Table 133 Cancellation of conformance statement 151
Table 134 indicates conformance statement 152
Table 135 Environmental and General Management Conformity Statement 152
Table 136 End of Conformance Statement 153
Table 137 Variable access consistency statement 154
Table 138 Variable access selection consistency statement 154
Table 141 Non-uniform variable access specification I 157
Table 142 Non-uniform variable access specification II 157
Table 143 Variable access specification for LDevice/MHAI1:HA:phsAHar(7)[MX] 158
Table 144 Variable access specification for LDevice/MHAI1:HA:phsAHar(7)[MX] 158
Table 145 Variable access specification conformance statement 159
Table 146 Variable specification conformance statement 159
Table 147 Read Service Conformance Statement 160
Table 148 Writing Service Conformance Statement 160
Table 149 Information Reporting Conformity Statement 161
Table 150 Obtain variable access attribute conformance statement 161
Table 151 Define named variable list conformance statement 162
Table 152 Obtaining the consistency statement of the named variable list attribute 162
Table 153 Delete named variable list consistency statement 163
Table 154 Read log consistency statement 163
Table 155 Entry content consistency statement 165
Table 156 File directory consistency statement 165
Table 157 Open file consistency statement 166
Table 158 Read file consistency statement 167
Table 159 Close file consistency statement 167
Table 160 GOOSE Conformity Statement 168
Table 161 Conformance Statement for Multicast Sampled Values 169
Table 162 P type definitions that can be used for client/server addressing 170
Table 163 GSE2 layer SCL definition 171
Table 164 GSE/SMV based on UDP/IPSCL definition 172
Table A:1 Fixed length GOOSE header encoding 178
Table A:2 All data encoding of fixed-length GOOSE messages - basic data type 179
Table A:3 Data encoding example 179
Table B:1 Examples of suggested multicast addresses182
Table C:1 VLANID and priority 190
Table C:2 Ethernet type value assignment 190
Table D:1 SCL conformance level 192
Table D:2 ACSI services supported for SCL:2192
Table J:1 SPDU length encoding example 226
Table J:2 IPv4 network protocol consistency implementation description based on transport protocol set (PICS) 230
Foreword
This document complies with the provisions of GB/T 1:1-2020 "Standardization Work Guidelines Part 1: Structure and Drafting Rules of Standardization Documents"
Drafting:
This document is Part 8-1 of GB/T 42151 "Power Automation Communication Networks and Systems": GB/T 42151 has issued the following
part:
---Part 5: Functional communication requirements and device model;
---Part 8-1: Specific Communication Services Mapping (SCSM) mapping to MMS (ISO 9506-1 and ISO 9506-2) and ISO /
IEC 8802-3:
This document is equivalent to IEC 61850-8-1:2020 "Power automation communication networks and systems - Part 8-1: Specific communication service mapping"
(SCSM) is mapped to MMS (ISO 9506-1 and ISO 9506-2) and ISO /IEC 8802-3:
The technical differences between this document and IEC 61850-8-1:2020 and their reasons are as follows:
a) Added the abbreviation "x: exclude, indicating that the application should not implement this item (exclude)" (see Chapter 4);
b) Delete "This application protocol set should comply with ISO /ISP14226-1, ISO /ISP14226-2, ISO /ISP14226-3, ISO /
"Convention of IEC ISP11188-1 and ISO /IEC ISP11188-3" (see 6:2:2:2), the normatively cited standards have been abolished and deleted:
The removal will not cause ambiguity and will not affect use:
Please note that some content in this document may be subject to patents: The publisher of this document assumes no responsibility for identifying patents:
This document is proposed by the China Electricity Council:
This document is under the jurisdiction of the National Electric Power System Management and Information Exchange Standardization Technical Committee (SAC/TC82):
This document was drafted by: Beijing Sifang Relay Automation Co:, Ltd:, Nari Group Co:, Ltd:, State Grid Co:, Ltd:
Electric Power Dispatch Control Center, China Electric Power Research Institute Co:, Ltd:, China Southern Power Grid Electric Power Technology Co:, Ltd:, State Grid Zhejiang Electric Power
Co:, Ltd:, State Grid Jiangsu Electric Power Co:, Ltd:, State Grid Jilin Electric Power Co:, Ltd:, Xuji Electric Co:, Ltd:, Nanjing Nari Relay Protection
Electric Co:, Ltd:, Tianjin Jinrail Huihai Technology Development Co:, Ltd:, Guodian Nanjing Automation Co:, Ltd:, Shanghai Siyuan Hongrui Automation
Co:, Ltd:, Nanjing Dianyan Electric Power Automation Co:, Ltd:
The main drafters of this document: Ren Yanming, Shen Jian, Wang Yongfu, Du Jun, Liao Zeyou, Tang Yongjian, Yin Jun, Zhou Bin, Chen Dehui, Zhang Chunxiao,
Du Qiwei, Yang Song, Li Jinsong, Zhang Qibing, Sun Yimin, Peng Zhiqiang, Feng Shanqiang, Peng Qi, Sun Dan, Wei Jieru, Han Wei, Zhou Shaoliang, Wu Qian, Hu Daoxu:
Introduction
GB/T 42151 "Power Automation Communication Networks and Systems" aims to provide interoperability for all devices in the power automation system: simulate
Consists of the following parts:
---Part 1: Introduction: The purpose is to provide an overview of this document:
---Part 2: Terminology: The purpose is to list terms and definitions used in this document:
---Part 3: General requirements: The purpose is to introduce the overall requirements of communication networks, focusing on quality requirements:
---Part 4: Systems and Project Management: The purpose is to describe the requirements for systems and project management processes and for engineering and test
Requirements for dedicated support tools required:
---Part 5: Communication requirements for functional and device models: The purpose is to specify the communication requirements for each function of the power automation system:
---Part 6: Configuration description language for device communication in power automation systems: The purpose is to communicate in some compatible way
Descriptions of capabilities for exchanging intelligent electronic devices and descriptions of power automation systems between tools provided by different manufacturers:
---Part 7: Basic communication structure of power automation system: The purpose is to define a hierarchical class model and the
services to implement communication between devices:
---Part 8: Specific Communication Service Mapping SCSM: The purpose is to provide substation station control layer and bay layer and station control layer and
Communication mapping between bay layers:
---Part 9: Specific Communication Service Mapping SCSM: The purpose is to provide substation bay level and process level and bay level and
Communication mapping between process layers:
---Part 10: Conformance testing: The purpose is to specify standard techniques for implementing conformance testing and to be used when proposing performance parameters:
specific measurement techniques:
GB/T 42151 "Power Automation Communication Networks and Systems" defines communication networks and systems for power automation systems, especially power substations:
Communication architecture of subsystems such as station automation systems: The sum of all these subsystems can also contribute to the communication body of the entire power system management:
The architecture describes the communication between devices in these subsystems and the communication between subsystems in the entire power automation system:
Starting from the core needs of the power station, it meets a large number of requirements for all functions in the power automation system: Organize data in a data model
These requirements are raised in the data exchange and data exchange that generates services: The performance of data exchange means not only the transmission time of data exchange, but also
It also means the quality of data exchange, thereby avoiding the loss of information during communication:
This document specifies the data model and abstract communication service interface and manufacturing message specification (MMS) of the GB/T 42151 series of standards and
Implementation details of mapping between Ethernet technologies, such as the correspondence between ACSI communication services and MMS communication services, etc:, at the same time this article
The software also considers support for network security and accurate time synchronization technical solutions: This document is intended for manufacturers, users and
It is of great significance for the quality inspection center to correctly implement, use and test the products and systems of GB/T 42151:
Power automation communication network and system
Part 8-1: Specific Communication Services Mapping (SCSM)
Mapping to MMS (ISO 9506-1 and ISO 9506-2)
and ISO /IEC 8802-3
1 Scope
1:1 General
This document specifies the real-time and non-real-time capabilities of local area networks by mapping ACSI to MMS and ISO /IEC 8802-3 frames:
Methods of data exchange:
MMS services and protocols are specified to run over a fully compatible set of OSI and TCP communication protocols: MMS supports both centralized and
Distributed architecture data exchange: This document includes the exchange of real-time data indications, control operations, and report notifications:
This document specifies ACSI (Abstract Communications Services Interface, IEC 61850-7-2) objects and services to MMS (Manufacturing Message Specification,
Mapping of ISO 9506) and ISO /IEC 8802-3 frames:
This document also specifies the mapping of real-time information to non-MMS protocols: The semantics of this protocol are specified in IEC 61850-7-2: This article
The document contains protocol syntax, specifications, mapping to ISO /IEC 8802-3 frame format, and tools related to the use of ISO /IEC 8802-3:
body method:
The mapping from ACSI to MMS specifies how to use MMS concepts, objects and services to implement ACSI concepts, objects and services:
This mapping enables interoperability between functions implemented by different manufacturers:
This document specifies the standard method for data exchange using ISO 9506 services: For those specified in IEC 61850-7-2
For ACSI services directed to MMS, this document will specify other protocols: This document uses an object-oriented approach and is based on the external application of the actual device:
Conforms to data and behavior, describing the actual device: These objects themselves are abstract and can be applied in a wider range of applications: This application has exceeded
The application scope of power automation communication has been expanded:
This document provides a mapping of objects and services specified in IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4:
1:2 Namespaces and versions
This document is required for any IEC 61850 namespace (as defined in IEC 61850-7-1):
Parameters used to identify namespace versions:
---Namespace version:2003;
---Namespace revision:A;
---Namespace name: "IEC 61850-8-1:2003":
Version Release DateIEC Web Store Namespace
Version 1:0:2004-05 IEC 61850-8-1:2004 IEC 61850-8-1:2003
Version 2:0:2011-06 IEC 61850-8-1:2011 IEC 61850-8-1:2003
Revision 1 of version 2:0 2020-02 IEC 61850-8-1:2011/AMD1:2020 IEC 61850-8-1:2003
Version 2:1 2020-02 IEC 61850-8-1:2011 AMD1:2020CSV IEC 61850-8-1:2003
1:3 Code component distribution
Code components are available in both simplified and full versions:
|