| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 31230.5-2014 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Industrial ethernet fieldbus EtherCAT -- Part 5: Application Layer service definition
| Valid |
GB/T 31230.5-2014
|
PDF similar to GB/T 31230.5-2014
Basic data | Standard ID | GB/T 31230.5-2014 (GB/T31230.5-2014) | | Description (Translated English) | Industrial ethernet fieldbus EtherCAT -- Part 5: Application Layer service definition | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040 | | Word Count Estimation | 109,115 | | Date of Implementation | 4/1/2015 | | Quoted Standard | GB/T 1988-1998; GB/T 9387.1; GB/T 9387.2; GB/T 9387.3; GB/T 9387.4; GB 13000; GB/T 15969.3; GB/T 17176; GB/T 17967; IEC/TR 61158-1-2010; IEC 61158-3-12; ISO/IEC 8802-3; IEEE 802.1D; IETF RFC 791 | | Regulation (derived from) | People's Republic of China Announcement of Newly Approved National Standards 2014 No. 22 | | Issuing agency(ies) | General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China | | Summary | This Standard is suitable for time-critical communications at the application layer characteristics of conceptual and services, and as a complement to the OSI reference model to guide the service in time-critical application layer protocol development. Se | GB/T 31230.5-2014: Industrial ethernet fieldbus EtherCAT -- Part 5: Application Layer service definition
---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.
. Industrial ethernet fieldbus EtherCAT Part 5. Application Layer service definition
ICS 25.040
N10
National Standards of People's Republic of China
Industrial Ethernet fieldbus EtherCAT
Part 5. Application layer service definition
Part 5. ApplicationLayerservicedefinition
Issued on. 2014-09-30
2015-04-01 implementation
Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
Standardization Administration of China released
Table of Contents
Introduction Ⅴ
1 Scope 1
1.1 Relationship with the IEC standard part 1
1.2 Overview 1
1.3 specification 1
1.4 Consistency 2
2 Normative references 2
3 Terms, definitions, symbols, abbreviations and conventions 2
Terms and Definitions 3.1 Reference Model 2
3.2 Service agreement terms and definitions 3
3.3 application layer and the data link service terms and definitions 4
3.4 General Symbols and Abbreviations 8
3.5 Conventions 9
4 Concepts 10
4.1 General Concepts 10
4.2 10 type-specific concepts
5 datatype ASE 16
5.1 Overview 16
Formal definition of the data type of the object 16 5.2
5.3 FAL-defined data types 16
5.4 datatype ASE service specification 25
6 Communication Model Specification 25
6.1 ASE 25
6.2 AR 94
References 103
Figure 1 producer-consumer model 11
Figure 2 client-server model 11
Figure 3 servers trigger a call 11
Figure 4 Slave Reference Model 12
5 simple slave devices 13
6 complex slave devices 14
7 master function Overview 15
8 process output data sequence 26
9 Process input data sequence 26
Figure 10 CoE server model 44
11 Successful single SDO download queue 48
Single SDO Download unsuccessful sequence diagram 12 48
13 successful staging SDO download queue 49
14 successful single SDO upload sequence diagram 49
15 unsuccessful single SDO upload sequence diagram 50
16 Successful Upload SDO segment sequence 50
Figure 17 SDO information sequence 51
18 Emergency Services 51
19 sequence of commands 52
Figure 20 PDO mapping 53
21 Sync Manager PDO assignment 53
Figure 22 RxPDO service 55
Figure 23 TxPDO service 55
Figure 24 RxPDO remote transmission sequence 56
Figure 25 TxPDO remote transmission sequence 56
Figure 26 EoE sequence 76
Read Sequence Figure 27 FoE success 83
Figure 28 FoE read sequence failure 84
Figure 29 FoE success write sequence 84
Figure 30 FoE write sequence failure 85
Figure 31 FoE write sequence busy 85
32 Successful ALControl sequence 95
33 unsuccessful ALControl sequence 95
Figure 34 AL status change sequence 96
Table 1 ProcessOutputData 28
Table 2 ProcessInputData 29
Table 3 UpdateProcessInputData 30
Table 4 SIIRead 38
Table 5 SIIWrite 39
Table 6 SIIReload 40
Table 7 SDO area allocation 44
Table 8 SDODownloadExpedited 60
Table 9 SDODownloadNormal 60
Table 10 DownloadSDOSegment 62
Table 11 SDOUploadExpedited 63
Table 12 SDOUploadNormal 63
Table 13 UploadSDOSegment 65
Table 14 AbortSDOTransfer 65
Table 15 GetODList 66
Table 16 ODListSegment 67
Table 17 GetObjectDescription 68
Table 18 GetEntryDescription 69
Table 19 ObjectEntrySegment 72
Table 20 Emergency 73
Table 21 RxPDO 73
Table 22 TxPDO 74
Table 23 RxPDOremotetransmission 74
Table 24 TxPDOremotetransmission 75
Table 25 InitiateEoE 79
Table 26 EoEFragment 80
Table 27 SetIPParameter 81
Table 28 SetAddressFilter 82
Table 29 FoERead 87
Table 30 FoEWrite 87
Table 31 FoEData 88
Table 32 FoEAck 88
Table 33 FoEBusy 89
Table 34 FoEError 89
Table 35 MBXread 91
Table 36 MBXWrite 92
Table 37 MBXReadUpd 93
Table 38 AL primitive and ESM management service primitives 94
Table 39 ALControl 101
Table 40 ALstatechange 102
Foreword
GB/T 31230 "Industrial Ethernet fieldbus EtherCAT" is divided into six sections.
--- Part 1. Overview
--- Part 2. Physical layer service and protocol specification
--- Part 3. Data link layer service definition
--- Part 4. Data link layer protocol specification
--- Part 5. Application layer service definition
--- Part 6. Application layer protocol specification
This section GB/T Part of 531,230.
This section drafted in accordance with GB/T 1.1-2009 given rules.
This part is proposed by China Machinery Industry Federation.
This part of the measurement and control of Standardization Technical Committee (SAC/TC124) is administered by the National industrial processes.
This section is drafted. Machinery Industrial Instrumentation Technology and Economy Institute, comprehensive measurement instrument Beijing Technology Development Co., Southwest
University, Shanghai Automation Instrumentation Co., Ltd., Chinese Academy of Sciences (Shenyang) Institute of Automation, Tsinghua University, Beijing University of Aeronautics and Astronautics, Beijing
Jiaotong University, when Beijing and advantage systems engineering Co., Ltd., Shunde Branch of CAS Institute of Computing, Omron Industrial Automation, Beckhoff Beijing stars
The company, ETG China.
The main drafters of this section. Xiesu Fen, high mirror Mei, Liu Dan, Liu Feng, including Wei-hua, Yang family, Wang Xue, Liu Yanjiang, Fan Yu, Luo, Chen Bingbing,
Tianbing Li, Guan Peng, Fan Bin, Cheng Geng.
Industrial Ethernet fieldbus EtherCAT
Part 5. Application layer service definition
1 Scope
Relations section 1.1 and IEC standards
GB/T 31230 in this section depends on the IEC 61158 series of 12 file types in the corresponding section.
1.2 Overview
Fieldbus Application Layer (FAL) program for the user to provide an access method Fieldbus communication environment, this point of view, FAL can
As a "window corresponding between applications."
For automation environment and material EtherCAT fieldbus, the Department is divided into basic time between application and non-time critical
Exchange critical information in public elements. The term "time-critical" represents the presence of a time window within this time window required to complete one or more
There are well-defined actions specified. When the window is not completed within a specified action, it may result in failure of the application needs of the operation, and even
Effect of equipment, plant and personal safety.
This part is defined in an abstract way the externally visible service provided by different types of fieldbus application layer, contains the following aspects.
a) used to define the user to operate the service through the use of FAL application resources (objects) abstract model;
b) service primitive actions and events;
c) the primitive actions and events related to the parameters and the format they use;
d) the relationship between events and actions and effective order.
The purpose of this section is to define the following two services.
1) between the user and the fieldbus reference model FAL user at the boundary;
2) between the application layer and system management reference model fieldbus systems management at the boundary.
This section specifies the structure and services in the IEC fieldbus application layer, and with the OSI Basic Reference Model (GB/T 9387) and OSI
Application layer structure (GB/T 17176) coincide.
Contained in the application process FAL application entity (AE) provides FAL services and protocols. FALAE shall be composed of a set of object-oriented
AE and a management layer management entity (LME) composition with service unit (ASE). ASE provides a set of application operating process objects
(APO) on a communications service. There is a management ASE in FALASE, it can provide a common set of instance management class for FAL
service.
From the application point of view, even though these services define how requests and responses are published and transmitted, but they do not include information on requests and responses
The specification should be published and the application to transfer content. That is, the aspect of application behavior is not defined. Only they can send/receive even
What kind of requests and responses have been clearly defined. This allows the user more flexibility in FAL standardized objects such behavior. except this
Addition to these services, in this section also defines a number of support services, to provide access to FAL certain aspects of the operation of the control.
1.3 specification
The main purpose of this section is to define the appropriate time critical communication features in the conceptual application layer services, and as a complement to the OSI
Reference model to guide the development of time-critical services in the application layer protocol. Secondly, for the purpose from the existing industrial communication protocols
Open another path.
This part can be used as an official in accordance with the application programming interface. However, it is not a formal programming interface, the interface requires no formal solution
|