| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/Z 29619.4-2013 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 8: INTERBUS specification -- Part 4: Data Link protocol specification
| Valid |
GB/Z 29619.4-2013
|
PDF similar to GBZ29619.4-2013
Basic data | Standard ID | GB/Z 29619.4-2013 (GB/Z29619.4-2013) | | Description (Translated English) | Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 8: INTERBUS specification -- Part 4: Data Link protocol specification | | Sector / Industry | National Standard | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040 | | Word Count Estimation | 119,122 | | Quoted Standard | GB/T 9387.1-1998; GB/T 9387.3-2008; GB/T 17967-2000 | | Adopted Standard | IEC 61158-2003, MOD | | Regulation (derived from) | National Standards Bulletin 2013 No. 10 | | Issuing agency(ies) | Ministry of Health of the People's Republic of China | | Summary | This standard applies to: INTERBUS data link protocol. Data link protocol is to provide GB/Z 29619. 3 define data link services are necessary. | GBZ29619.4-2013: Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 8: INTERBUS specification -- Part 4: Data Link protocol specification
---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.
Digital data communication for measurement and control. Fieldbus for use in industrial control systems. Type 8. INTERBUS specification. Part 4. Data Link protocol specification
ICS 25.040
N10
People's Republic of China national standardization of technical guidance documents
Measurement and control of digital data communications industrial control systems
With the fieldbus type 8.INTERBUS specification
Part 4. Data link protocol specifications
Fieldbus for use in industrial control systems-
Part 4.DataLinkprotocolspecification
(IEC 61158.2003, MOD)
2013-07-19.2013-12-15 implementation
General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
China National Standardization Administration released
Directory
Introduction Ⅶ
Introduction Ⅷ
1 Scope 1
2 Normative references 1
3 Terms and definitions 1
3.1 Reference Model Terms and Definitions 1
3.2 Service Conventions Terms and Definitions 2
3.3 Other terms and definitions 3
4 symbols and abbreviations 4
4.1 General Symbols and Abbreviations 4
4.2 Local Variables, Clocks, Counters, and Queues 6
5 Data Link Layer Protocol DL-protocol 6
5.1 Summary 6
5.2 DL-service interface (DLI) 7
5.3 Peripheral Equipment Data Link (PDL) 12
5.4 Basic Link Layer (BLL) 46
5.5 Media Access Control (MAC) 61
5.6 Layer 2 Peripheral Equipment Network Management (PNM2)
5.7 DLL parameters and monitoring time 96
Appendix A (informative) Possibility of implementation of the PNM2 function
References 110
Figure 1 data link layer and the relationship between other layers Ⅶ
Figure 2 data link layer entity 6
Figure 3 DLI in the DLL position 7
Figure 4 DLI state transition diagram 8
Figure 5 PDL in the DLL position 12
Figure 6 PDL link between master and slave 12
Figure 7 Interface between PDL-user (DLI) and PDL in a layered model 13
Figure 8 PDL Service Overview 14
Figure 9 PDL_Data_Ack Service Between Master and Slave 15
Figure 10 PDL_Data_Ack service parallel processing 15
Figure 11 PSM and GSM Services for Buffer Access 16
Figure 12 indicates Buffer_Received service 16 for successful data transfer
Figure 13 PDL_Data_Ack service data flow between PDL-user, PDL and BLL 18
Figure 14 Interface between PDL and PNM2 in a layered model 19
Figure 15 Reset, SetValue and GetValuePDL Services 20
Figure 16 EventPDL service 20
Figure 17 Master and slave transmission FCB and receive FCB 23
Figure 18 Master → Slave Data Transfer with SWA 23
Figure 19 Master → Slave Data Transfer Timing with SWA 24
Figure 20 Slave with RWA/SWA telegram → Master data transfer 24
Figure 21 Slave → Master Data Transfer with RWA/SWA telegram 24
Figure 22 PDL protocol machine and the allocation of data cycle action 25
Figure 23 Message Transfer. Master → Slave 26
Figure 24 Message Transfer Slave → Master 26
Figure 25 Code octet 26 for a PDLPDU
Figure 26 Structure of a word length message
Figure 27 Structure of a SPA message 28
Figure 28 SVA message structure 28
Figure 29 Structure of FCB_SET message 28
Figure 30 RWA message structure
Figure 31 SWA message structure
Figure 32 Structure of SPA or SVA message validation
Figure 33 FCB_SET as a confirmed structure
Figure 34 Structure of octets as requested and validated FCB_SET data
Figure 35 Message structure 30 with more than one word size
Figure 36 PDL Basic Protocol Machine
Figure 37 Location of PDL and PDL Protocols in Master and Slave 33
Figure 38 PDL Protocol Machine 34
Figure 39 TRANSMIT Protocol Machine
Figure 40 RECEIVE Protocol Machine 41
Figure 41 BLL Location in the DLL 46
Figure 42 Interface between PDLs and BLLs in a layered model 46
Figure 43 BLL_Data Service 47
Figure 44 Interface Between PNM2 and BLL in Hierarchical Model 49
Figure 45 Reset, SetValue and GetValue BLL Services 50
Figure 46 EventBLL service 50
Figure 47 Master BLL Operation Protocol Machine 54
Figure 48 BLL-BAC Protocol Machine 57
Figure 49 Slave BLL Operation Protocols 60
Figure 50 MAC in the DLL position 61
Figure 51 Model Details for Tier 1 and Tier 2 62
Figure 52 DLPDU cycle of error-free data sequence 63
Figure 53 DLPDU Period 63 for Wrong Data Sequence
Figure 54 Data sequence DLPDU 63 sent by the master
Figure 55 Master receives the data sequence DLPDU 64
Figure 56 Check Sequence DLPDU 64
Figure 57 Return Word (LBW) 64
Figure 58 Master generated checksum status 65
Figure 59 Master checksum status 65
Figure 60 MAC protocol master station. Message transmission 66
Figure 61 Master MAC Protocol Machine
Figure 62 Master MAC Sublayer
Figure 63 Data sequence DLPDU 74 received by a slave
Figure 64 Data Sequence DLPDU 74 Sent by Slave
Figure 65 Status of the checksum received 75 from the slave
Figure 66 Status of checksum generated by slave 75
Figure 67 Slave MAC Sublayer Status Transitions
Figure 68 Status Transition of Slave MAC Sublayer. Check Sequence 77
Figure 69 Interface between MAC-user and MAC in a hierarchical model 81
Figure 70 Interaction on the MAC-user interface (master) 82
Figure 71 Interaction on MAC-user Interface (Slave) 82
Figure 72 Interface between MAC and PNM2 in a layered model 85
Figure 73 Reset, SetValue, and GetValueMAC Services 86
Figure 74 EventMAC Service 86
Figure 75 Location of PNM2 in the DLL 89
Figure 76 Interface between PNM2-user and PNM2 in a layered model 89
Figure 77 Reset, SetValue, GetValue, and GetActiveConfiguration Services 91
Figure 78 EventPNM2 Service 91
Figure 79 SetActiveConfiguration, GetCurrentConfiguration Service 91
Figure 80 active_configuration parameter 95
Figure 81 Device Code Structure 97
Figure 82 Data Width, Relationship Between Process Data Channels and Parameter Channels 99
Figure 83 Structure of Control Code 100
Figure A.1 DL-subnetwork configuration in the form of a tree structure 101
Figure A.2 Get the current configuration of the state machine 103
Figure A.3 compares two configured state machines 106
Figure A.4 compares two state machines 108 that configure one row of the matrix
Table 1 DLS-/DLMS-user primitives posted to DLI 7
Table 2 Primitives for DLI Publishing to DLS-/DLMS-user 8
Table 3 DLI Status Table --- Sender Transaction 9
Table 4 DLI Status Table - Recipient Transaction 10
Table 5 GetOffset features 11
Table 6 GetLength function 11
Table 7 GetRemAdd function 12
Table 8 GetDlsUserId function 12
Table 9 PDL_Data_Ack 16
Table 10 PDL_Data_AckL_status value 16
Table 11 PSM 17
Table 12 GSM 17
Table 13 PDL_Reset 20
Table 14 PDL_Set_Value 20
Table 15 PDL Variables 21
Table 16 PDL_Get_Value 21
Table 17 PDL_Event 22
Table 18 Events 22
Table 19 L_status code 27
Table 20 FCL Codes - Types 27
Table 21 PDL Basic Protocol Machine State Transfer 32
Table 22 PDL Protocol Machine Counter 34
Table 23 "connection" sign meaning 34
Table 24 PDL Protocol Machine State Transition 35
Table 25 TRANSMIT Protocol Machine State Transition 38
Table 26 RECEIVE Protocol Machine State Transitions 42
Table 27 BLL_Data 48
Table 28 BLL_Data 51
Table 29 BLL_Reset 51
Table 30 BLL_Set_Value 52
Table 31 BLL Variables 52
Table 32 BLL_Get_Value 52
Table 33 BLL_Event 53
Table 34 BLL_Event 53
Table 35 Status Conversion of Master BLL Operation Protocol Machine 55
Table 36 Status Transitions for BLL-BAC Protocols 58
Table 37 Slave BLL Operation Protocol Machine Status Transition 61
Table 38 MAC_Reset 87
Table 39 MAC_Set_Value 87
Table 40 MAC Variable 87
Table 41 MAC_Get_Value 88
Table 42 MAC_Event 88
Table 43 MAC_Event 88
Table 44 PNM2_Reset 92
Table 45 M_status value of PNM2_Reset 92
Table 46 PNM2_Set_Value 92
Table 47 Value of M_status for PNM2_Set_Value 93
Table 48 PNM2_Get_Value 93
Table 49 M_status value of PNM2_Get_Value 93
Table 50 PNM2_Event 94
Table 51 MAC Events 94
Table 52 PNM2_Get_Current_Configuration 94
Table 53 PNM2_Get_Active_Configuration 95
Table 54 PNM2_Set_Active_Configuration 96
Table 55 Data Direction 98
Table 56 Number of octets occupied in the parameter channel 98
Table 57 Equipment 98
Table 58 Control Data 99
Table 59 Data Width 99
Table 60 Media Control 100
Table A.1 DL-SUBNETWORK CONFIGURATION IN MATRIX 102
Table A.2 Acquire_Configuration 102
Table A.3 Obtains the state transition of the currently configured state machine 103
Table A.4 Check_Configuration 105
Table A.5 Compare_Slave 105
Table A.6 compares state transitions for two configured state machines 107
Table A.7 compares state transitions for state machines 109 in two configuration matrixes
Foreword
GB /Z 29619 "Measurement and Control Digital Data Communications Industrial Control Systems Fieldbus Type 8. INTERBUS Specification"
Former divided into the following six sections.
--- Part 1. Overview;
--- Part 2. Physical layer specification and service definition;
--- Part 3. Data Link Service Definition;
--- Part 4. Data link protocol specification;
--- Part 5. Application layer service definition;
--- Part 6. Application layer protocol specification.
This section GB /Z 29619 Part 4.
This section drafted in accordance with the rules given GB/T 1.1-2009 and GB/T 20000.2-2009.
GB /Z 29619 modified using IEC 61158.2003 "Measurement and Control Digital Data Communications Industrial Control Systems Fieldbus"
Part of the content, no adjustment in the technical content, the structure is divided into 6 parts to meet the needs of different users to use alone.
For ease of use, this section made the following editorial changes.
a) According to the actual use of our country, in accordance with the provisions of GB/T 1.1-2009, the original text was edited editorial changes
The content of surgery is exactly the same
b) reference to the original text of other international standards have been adopted or modified as our standard, this part of our standard number instead
Corresponding to the international standard number, the rest have not been the same or modified to use as our standard international advanced standards, are in this section
Direct reference.
This part is proposed by China Machinery Industry Federation.
This part of the National Industrial Process Measurement and Control Standardization Technical Committee (SAC/TC124) centralized.
This part of the drafting unit. Machinery Industry Instrumentation Technology and Economy Institute, Tsinghua University, Southwest University, Beijing Iron and Steel Design and Research
General Hospital, Shanghai Automation Instrumentation Co., Ltd., Shanghai Institute of Industrial Automation Instrumentation, Nanjing Phoenix Contact Electric Co., Ltd.
The main drafters of this section. Mei Ke, Zheng Xu, Liu Feng, Bao Weihua, Li Baihuang, Liu Zhaohui.
Introduction
INTERBUS is a digital serial communication system used in control systems (such as programmable logic controllers) and industrial sensors and actuators
Communication between field devices. These devices include simple limit switches and valves, as well as measurement sensors, measurement transmitters and actuators, and also
Can include sophisticated high-tech control systems such as controllers that control drive, torque, and process.
This section describes the data link protocol specification, which is closely related to other parts of GB /Z 26919. GB /Z 26919 by the Department
The "three-layer" reference model of the fieldbus that separates the basic reference model of the system interconnection is defined based on the part of the basic reference model of the open system interconnection
type. For ease of management, both reference models subdivide the interconnection standard range into a series of canonical levels.
Through the services provided by the physical layer, the DL protocol provides data link services to data link layer users (such as the application layer). Between different layers
The relationship shown in Figure 1.
Figure 1 data link layer and other layers
The DL-protocol provides a highly optimized method of creating a ring topology between an interconnected master device and a group of slave devices
Flutter, to achieve a fixed length of the input/output data and variable length of the packet exchange. Input/output data exchange through the configuration
Is fully synchronized and is unaffected by packet traffic.
Devices are implicitly addressed by their location in the ring. Each device's numbers, logos, and features are configurable, or
In the start-time can be automatically detected.
Measurement and control of digital data communications industrial control systems
With the fieldbus type 8.INTERBUS specification
Part 4. Data link protocol specifications
1 Scope
This part of GB /Z 29619 describes the INTERBUS data link protocol. Data link protocol is to provide GB /Z 29619.3
Defined data link service required.
2 Normative references
The following documents for the application of this document is essential. For dated references, only the dated version applies to this article
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
GB/T 9387.1-1998 Information technology - Open Systems Interconnection basic reference model Part 1. Basic model (idtISO /
IEC 7498-1.1994)
GB/T 9387.3-2008 Information technology - Open Systems Interconnection Basic Reference Model Part 3. Naming and addressing (ISO /
IEC 7498-3.1997, IDT)
GB/T 17967-2000 Information Technology Open Systems Interconnection basic reference model OSI service definition convention (idtISO /
IEC 10731.1994)
3 Terms and definitions
The following terms and definitions apply to this document.
3.1 Reference Model Terms and Definitions
GB/T 9387.1-1998 and GB/T 9387.3-2008 define the following terms apply to this document.
3.1.1 DL address DL-address [GB/T 9387.3-2008]
3.1.2 DL address mapping DL-address-mapping [GB/T 9387.1-1998]
3.1.3 DL connection DL-connection [GB/T 9387.1-1998]
3.1.4 DL connection endpoint DL-connection-end-point [GB/T 9387.1-1998]
3.1.5 DL connection endpoint identifier DL-connection-end-point-identifier [GB/T 9387.1-1998]
3.1.6 DL data source DL-data-source [GB/T 9387.1-1998]
3.1.7 DL Name DL-name [GB/T 9387.3-2008]
3.1.8 DL protocol DL-protocol [GB/T 9387.1-1998]
3.1.9 DL protocol connection identifier DL-protocol-connection-identifier [GB/T 9387.1-1998]
3.1.10 DL protocol control information DL-protocol-control-information [GB/T 9387.1-1998]
3.1.11 DL protocol data unit DL-protocol-data-unit [GB/T 9387.1-1998]
3.1.12 DL service connection identifier DL-service-connection-identifier [GB/T 9387.1-1998]
3.1.13 DL service data unit DL-service-data-unit [GB/T 9387.1-1998]
|