Superseded

GB/Z 29619.4-2013Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 8: INTERBUS specification -- Part 4: Data Link protocol specification (English PDF)

Preview PDF

This is a limited preview

Buy now to download the full PDF (110 pages)

Need quotation for your management?

Get a formal quotation for GB/Z 29619.4-2013 in 30 minutes.

Issued by

General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China, China National Standardization Administration

Level / Type

National · Recommended

Issue date

July 19, 2013

Implementation date

December 15, 2013

Scope

GB/Z 29619.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) is available as an English-translated PDF.

GB/Z 29619.4-2013 — 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.

Found what you need?

Document preview — GB/Z 29619.4-2013

National Standard of the People's Republic of China

ICS: 25.040
Classification: N 10

Issued by: General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China, China National Standardization Administration

Introduction
Introduction
1 Scope
2 Normative references
3 Terms and definitions
3.1 Reference Model Terms and Definitions
3.2 Service Conventions Terms and Definitions
3.3 Other terms and definitions
4 Symbols and abbreviations
4.1 General Symbols and Abbreviations
4.2 Local Variables, Clocks, Counters, and Queues
5 Data Link Layer Protocol DL-protocol
5.1 Summary
5.2 DL-service interface (DLI)
5.3 Peripheral Equipment Data Link (PDL)
5.4 Basic Link Layer (BLL)
5.5 Media Access Control (MAC)
5.6 Layer 2 Peripheral Equipment Network Management (PNM2)
5.7 DLL parameters and monitoring time
Appendix A (informative) Possibility of implementation of the PNM2 function
References
Figure 1 data link layer and the relationship between other layers
Figure 2 data link layer entity
Figure 3 DLI in the DLL position
Figure 4 DLI state transition diagram
Figure 5 PDL in the DLL position
Figure 6 PDL link between master and slave
Figure 7 Interface between PDL-user (DLI) and PDL in a layered model
Figure 8 PDL Service Overview
Figure 9 PDL_Data_Ack Service Between Master and Slave
Figure 10 PDL_Data_Ack service parallel processing
Figure 11 PSM and GSM Services for Buffer Access
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
Figure 14 Interface between PDL and PNM2 in a layered model
Figure 15 Reset, SetValue and GetValuePDL Services
Figure 16 EventPDL service
Figure 17 Master and slave transmission FCB and receive FCB
Figure 18 Master -> Slave Data Transfer with SWA
Figure 19 Master -> Slave Data Transfer Timing with SWA
Figure 20 Slave with RWA/SWA telegram -> Master data transfer
Figure 21 Slave -> Master Data Transfer with RWA/SWA telegram
Figure 22 PDL protocol machine and the allocation of data cycle action
Figure 23 Message Transfer. Master -> Slave
Figure 24 Message Transfer Slave -> Master
Figure 25 Code octet 26 for a PDLPDU
Figure 26 Structure of a word length message
Figure 27 Structure of a SPA message
Figure 28 SVA message structure
Figure 29 Structure of FCB_SET message
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
Figure 38 PDL Protocol Machine
Figure 39 TRANSMIT Protocol Machine
Figure 40 RECEIVE Protocol Machine
Figure 41 BLL Location in the DLL
Figure 42 Interface between PDLs and BLLs in a layered model
Figure 43 BLL_Data Service
Figure 44 Interface Between PNM2 and BLL in Hierarchical Model
Figure 45 Reset, SetValue and GetValue BLL Services
Figure 46 EventBLL service
Figure 47 Master BLL Operation Protocol Machine
Figure 48 BLL-BAC Protocol Machine
Figure 49 Slave BLL Operation Protocols
Figure 50 MAC in the DLL position
Figure 51 Model Details for Tier 1 and Tier 2
Figure 52 DLPDU cycle of error-free data sequence
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
Figure 56 Check Sequence DLPDU
Figure 57 Return Word (LBW)
Figure 58 Master generated checksum status
Figure 59 Master checksum status
Figure 60 MAC protocol master station. Message transmission
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
Figure 67 Slave MAC Sublayer Status Transitions
Figure 68 Status Transition of Slave MAC Sublayer. Check Sequence
Figure 69 Interface between MAC-user and MAC in a hierarchical model
Figure 70 Interaction on the MAC-user interface (master)
Figure 71 Interaction on MAC-user Interface (Slave)
Figure 72 Interface between MAC and PNM2 in a layered model
Figure 73 Reset, SetValue, and GetValueMAC Services
Figure 74 EventMAC Service
Figure 75 Location of PNM2 in the DLL
Figure 76 Interface between PNM2-user and PNM2 in a layered model
Figure 77 Reset, SetValue, GetValue, and GetActiveConfiguration Services
Figure 78 EventPNM2 Service
Figure 79 SetActiveConfiguration, GetCurrentConfiguration Service
Figure 80 active_configuration parameter
Figure 81 Device Code Structure
Figure 82 Data Width, Relationship Between Process Data Channels and Parameter Channels
Figure 83 Structure of Control Code
Figure A.1 DL-subnetwork configuration in the form of a tree structure
Figure A.2 Get the current configuration of the state machine
Figure A.3 compares two configured state machines
Figure A.4 compares two state machines 108 that configure one row of the matrix
Table 1 DLS-/DLMS-user primitives posted to DLI
Table 2 Primitives for DLI Publishing to DLS-/DLMS-user
Table 3 DLI Status Table --- Sender Transaction
Table 4 DLI Status Table - Recipient Transaction
Table 5 GetOffset features
Table 6 GetLength function
Table 7 GetRemAdd function
Table 8 GetDlsUserId function
Table 9 PDL_Data_Ack
Table 10 PDL_Data_AckL_status value
Table 11 PSM
Table 12 GSM
Table 13 PDL_Reset
Table 14 PDL_Set_Value
Table 15 PDL Variables
Table 16 PDL_Get_Value
Table 17 PDL_Event
Table 18 Events
Table 19 L_status code
Table 20 FCL Codes - Types
Table 21 PDL Basic Protocol Machine State Transfer
Table 22 PDL Protocol Machine Counter
Table 23 "connection" sign meaning
Table 24 PDL Protocol Machine State Transition
Table 25 TRANSMIT Protocol Machine State Transition
Table 26 RECEIVE Protocol Machine State Transitions
Table 27 BLL_Data
Table 28 BLL_Data
Table 29 BLL_Reset
Table 30 BLL_Set_Value
Table 31 BLL Variables
Table 32 BLL_Get_Value
Table 33 BLL_Event
Table 34 BLL_Event
Table 35 Status Conversion of Master BLL Operation Protocol Machine
Table 36 Status Transitions for BLL-BAC Protocols
Table 37 Slave BLL Operation Protocol Machine Status Transition
Table 38 MAC_Reset
Table 39 MAC_Set_Value
Table 40 MAC Variable
Table 41 MAC_Get_Value
Table 42 MAC_Event
Table 43 MAC_Event
Table 44 PNM2_Reset
Table 45 M_status value of PNM2_Reset
Table 46 PNM2_Set_Value
Table 47 Value of M_status for PNM2_Set_Value
Table 48 PNM2_Get_Value
Table 49 M_status value of PNM2_Get_Value
Table 50 PNM2_Event
Table 51 MAC Events
Table 52 PNM2_Get_Current_Configuration
Table 53 PNM2_Get_Active_Configuration
Table 54 PNM2_Set_Active_Configuration
Table 55 Data Direction
Table 56 Number of octets occupied in the parameter channel
Table 57 Equipment
Table 58 Control Data
Table 59 Data Width
Table 60 Media Control
Table A.1 DL-SUBNETWORK CONFIGURATION IN MATRIX
Table A.2 Acquire_Configuration
Table A.3 Obtains the state transition of the currently configured state machine
Table A.4 Check_Configuration
Table A.5 Compare_Slave
Table A.6 compares state transitions for two configured state machines
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.

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.

1 Figure, 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]

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 110 pages — is available in the English PDF.

Referenced standards

Normative references

GB/T 9387.3-2008Information technology -- Open systems interconnection -- Basic reference model -- Part 3: Naming and addressing

GB/T 9387.1-1998 · IEC 7498 · ISO/IEC 7498 · GB/T 17967-2000 · IEC 10731

Cited by

GB/Z 29619.3-2013Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 8: INTERBUS specification -- Part 3: Data Link service definition

How to Download GB/Z 29619.4-2013

1
Add to cart
Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.
2
Checkout
Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).
3
Instant delivery (0–9 sec)
Delivery is automatic: within seconds of payment you'll receive an email with a secure download link. The link stays valid for 72 hours.
4
Invoice included
A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.