GBZ26157.3-2010 English PDFUS$1829.00 · In stock
Delivery: <= 13 days. True-PDF full-copy in English will be manually translated and delivered via email. GBZ26157.3-2010: Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 2: ControlNet and EtherNet/IP specification -- Part 3: Data link layer Status: Valid
Basic dataStandard ID: GB/Z 26157.3-2010 (GB/Z26157.3-2010)Description (Translated English): Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 2: ControlNet and EtherNet/IP specification -- Part 3: Data link layer Sector / Industry: National Standard Classification of Chinese Standard: N10 Classification of International Standard: 25.040 Word Count Estimation: 83,858 Date of Issue: 2011-01-14 Date of Implementation: 2011-06-01 Quoted Standard: GB/T 9387; ISO/IEC 8802-4-1990; GB/T 15629.3-1995; GB/Z 26157.5-2010; GB/Z 26157.2-2010; GB/Z 26157.9-2010 Adopted Standard: IEC 61158-2003, MOD Regulation (derived from): ?National Standard Approval Announcement 2011 No.2 Issuing agency(ies): Ministry of Health of the People's Republic of China Summary: This standard specifies the requirements on data link layer control network nodes with certainty. The technical guidance document applies to deterministic control network data link layer corresponds to GB/T 9387 consistent with the OSI seven-layer model of the second layer definition. Figure 5 shows the location of the OSI model data link layer. GBZ26157.3-2010: Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 2: ControlNet and EtherNet/IP specification -- Part 3: Data link layer---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 2. ControlNet and EtherNet/IP specification. Part 3. Data link layer ICS 25.040 N10 People's Republic of China national standardization of technical guidance documents Measure and control digital data communications Industrial control system with fieldbus Part 3. data link layer (IEC 61158..2003 TYPE 2, MOD) Posted on.2011-01-14 2011-06-01 implementation General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China China National Standardization Administration released Directory Foreword Ⅲ Introduction IV 1 Scope 1 2 MAC frame 1 2.1 format 1 2.2 Preamble 2 2.3 Separator 2 2.4 bytes and sorting 2 2.5 Source MACID 2 2.6 The total size of all Lpackets 2 2.7 cyclic redundancy check 2 2.8 abnormal stop MAC frame 2 3 Lpacket 3 3.1 format 3 3.2 Size 3 3.3 Control 3 3.4 Label 4 3.5 Link Data 5 4 Coordinator Lpacket 5 4.1 format 5 5 Modeling Language (informative) 6 6 external interface 7 6.1 Sending Services 7 6.2 queue maintenance service 8 6.3 Label filtering management 8 6.4 Receiving Service 8 6.5 network synchronization service 9 6.6 Synchronization parameters change 9 6.7 Incident Report 10 6.8 invalid CRC indication 11 6.9 Current Coordinator Indication 11 6.10 Power 11 6.11 Enable Coordinator 12 6.12 only listen to 12 Access Control Machine (ACM) 12 8 TxLLC 43 9 RxLLC 49 10 Transmitter (TxM) 53 Receiver (RxM) 59 12 parallel serial converter 68 13 serial-parallel converter 71 13.1 Byte Construction 71 13.2 CRC check 71 13.3 Frame processing ends 71 DLL Management 71 Figure 1 NUT structure Ⅳ Figure 2 Medium access during scheduling period Ⅴ Figure 3 Media Access during Non-Scheduled Ⅴ Figure 4 data link layer internal structure Ⅶ Figure 5 and the ISO /OSI model of the relationship 1 Figure 6 MAC frame format 2 Figure 7 aborts one MAC frame 3 during transmission Figure 8 Lpacket format 3 Figure 9 fixed label Lpacket format 4 Figure 10 Universal Label Lpacket format 5 Table 1 data link layer assembly Ⅵ Table 2 fixed label service definition 4 Table 3 DLL Events 10 ForewordIEC 61158..2003 "Fieldbus for the Measurement and Control of Digital Data Communications for Industrial Control Systems" includes 10 fieldbus types. --- Type 1. IEC Technical Report; --- Type 2. ControlNet and Ethernet/IP; --- Type 3. PROFIBUS; --- Type 4. P-Net; --- Type 5. FFHSE; --- Type 6. SwiftNet; --- Type 7. WorldFIP; --- Type 8. Interbus; --- Type 9. FFAL; --- Type 10. PROFINET. The standardization of technical guidance to modify the use of IEC 61158..2003 "Measurement and Control Digital Data Communications Industrial Control System Fieldbus Type 2. ControlNet and EtherNet/IP Specification Part 3. Data Link Layers. " IEC 61158 series of standards will be 10 kinds of fieldbus technology mixed together to write, not easy to domestic engineering and technology Off personnel on a variety of bus technology reading and understanding of the National Industrial Process Measurement and Control Standardization Technical Committee in the use of international standards On time, only the technical aspects of Type 2. ControlNet and EtherNet/IP specifications, which are widely used in China, have been adopted. According to the habits of technology developers will be divided into 10 parts to prepare. In technical content and international standards no difference, for the convenience of me National users, in the text of the structure of the layout of the appropriate adjustments, and according to GB/T 1.1 requirements for the preparation. GB /Z26157 "Measurement and Control Digital Data Communications Fieldbus for Industrial Control Systems Type 2. ControlNet and Ether- Net/IP specification "is divided into the following 10 parts. GB /Z26157.1 general description; GB /Z26157.2 physical layer and media; GB /Z26157.3 data link layer; GB /Z26157.4 network layer and transport layer; GB /Z26157.5 data management; GB /Z26157.6 object model; GB /Z26157.7 equipment line rules; GB /Z26157.8 spreadsheet; GB /Z26157.9 station management; GB /Z26157.10 object library. This guidance document is Part 3. This guidance document is proposed by China Machinery Industry Federation. This Guidance Document is governed by the National Technical Committee for Standardization and Measurement of Industrial Processes (SAC/TC124). The guidance of technical documents Drafted by. Machinery Industry Instrumentation Technology and Economy Institute, Tsinghua University, Southwest University, Beijing Steel Iron Design and Research Institute, China Instrument Association, China Mechatronics Technology Applications Association, Shanghai Automation Instrumentation Co., Ltd., Shanghai Industrial Automation Instrumentation Institute, Shanghai Electric Institute of Science (Group) Co., Ltd., Rockwell Automation Research (Shanghai) Co., Ltd. The main drafters of this Guidance Document are Zheng Xu, Mei Ke, Chen Kai Tai, Wang Jinbiao, Peng Yu, Liu Feng, Bao Weihua, Xia Dehai, Dong Jingchen, Ruan Yu Dong, Li Baihuang, Wang Chunxi, Wang Yumin.IntroductionThe main task of the data link layer (DDL) is to collaborate with other data link layers on the same link to decide to allow it on the medium Send authorization. In its interface with the upper layer, DDL provides service data unit (SDU) for network layer, transport layer and station management to receive and hand over Pay the service. The DDL protocol is based on a fixed, repeated period of time called the Network Update Time (NUT). NUT all on the link Keep strict synchronization in the node. If the NUT of a node is not consistent with the NUT used on the current link, the node does not allow Sent on the media. Different links may have different NUTs. Each node contains a timer that is synchronized with the NUT of the local link. Media access is divided by the local NUT access slots To decide. The media access is based on the node's MACID sorting order. In order to allow a temporary MACID for Zero nodes perform link maintenance, adding specific behaviors in the access protocol. The MACID of all nodes on a link is the only one One. Once detected duplicate MACID DLL, then immediately stop sending. An implicit token passing mechanism is used to authorize access to media. Each node monitors the source MAC ID of each MAC frame received. At the end of the MAC frame, each DLL sets an "Implicit Token Register" equal to the MACID of the received source MACID + 1. If the implicit token register is equal to the local MACID, then the node can send a MAC frame. In other cases, the section Point or wait for a new MAC frame from the node specified by the Implicit Token Register, or wait for a timeout if the specified section If the point fails to send. In either case, the "hidden token" is automatically incremented to the next MACID. All nodes "hidden token Register "contains the same value to avoid media conflicts. The timeout period (called "slot time") is based on the sum of the following required times. The current node listens to the end of the previous node's sending; The current node starts sending; The next node listens for the start of the current node transmission; The slot time is adjusted to compensate for the total length of the media because the propagation delay of the media affects the first and last items listed above. Note. The calculation of the time slot in GB /Z26157.9-2010 station management provisions. Each NUT is divided into three main sections. scheduled, unscheduled, and maintained, as shown in Figure 1. This sequence is in every NUT repeat. Implicit token passing mechanisms are used to authorize access to media at scheduled and non-scheduled intervals. Data link layer protocol Figure 1 NUT structure In the part of NUT scheduling, every node starting from node 0 and ending at node SMAX has a chance to send a message to time Strict requirements (scheduling) data. SMAX is the MACID of the highest numbered node that can access the media on the part of the NUT schedule. In every In a NUT, nodes between 0 and SMAX have only one opportunity to send scheduled data, and each node in the scheduled period of time on the media The chances of visit are equal. This allows the data sent in the NUT scheduled part to be transmitted in a predictable and deterministic manner. Figure 2 Shows how authorization is allowed to be sent during the scheduling period. Network Layer and Transport Layer Tuning Each node can during this scheduled token pass The amount of data sent. Figure 2 Media access during the scheduling period In the non-scheduled portion of NUT, every node from 0 to UMAX has the ability to send in a round robin fashion with no strict requirements on time Data opportunities until the assigned NUT time runs out. UMAX is the highest number of media that can be accessed on the non-scheduled portion of the NUT The MACID of the node. Each node from 0 to UMAX may have zero, one or more opportunities to transfer non-scheduled data depending on How much is left for this NUT after the scheduled period has been completed? In each NUT, the opportunity to access the media during non-scheduled time periods is per node Can be different. Figure 3 shows how to grant permission to send during a non-scheduled period. For each NUT, the non-scheduled portion of the NUT The MACID of the starting node increases by 1 each time. The non-scheduled tokens are defined by the non-scheduled start register (USR) of the previous coordinated frame MACID start. The USR modulo UMAX + 1 modulo each NUT plus one modulo. If the USR is reached before maintaining the segment UMAX, then it returns to 0 and token passing continues. Figure 3 Media access during non-scheduling When reaching the maintenance segment, all nodes stop sending. If a transmission can not be completed before the beginning of the maintenance section, the node is not allowed Start this send. During the maintenance of the segment, the node with the lowest MACID (called the "coordinator") sends a maintenance message Tune the frame "), it does the following two things. --- Keep all nodes NUT timer synchronization; --- Release key link parameters, so that all members of the local DLL group can share a common version of the important DLL value, such as NUT, slot time, SMAX, UMAX and so on. The coordinator sends a coordination frame, resynchronizes all nodes, and restarts the NUT. After receiving a valid coordination frame, each node will Its internal value is compared to the value sent by the reconciliation frame. Nodes that use link parameters that are not consistent with the coordinator themselves can not work. If at Coordination frames are not received in two consecutive NUTs, then the node with the lowest MACID plays the coordinator role. In the 3rd NUT The maintenance section starts sending coordination frames. Once the coordinator node finds that another node is online and sends frames whose MACID is lower than their own , Immediately cancel its own coordinator role. Typical situations that may cause DLL access protocol interruption include. --- The noise introduced on the link; --- poor quality cable or terminal; --- When the network is running physically connect the two links together. The usual result of this interruption is the node on which nodes may cause inconsistencies in the sending problem, which is referred to as the " Another potential problem arises when a node does not meet the same link configuration parameters.A link parameter that is sent with the coordinator Inconsistent nodes are called "free nodes" and stop sending immediately. The DLL access protocol will attempt to repair a free node and bring it back To online. At the data link layer, the access controller (ACM) is primarily responsible for detecting and repairing network outages. ACM's main tasks are. --- Ensure local nodes detect and make full use of the protocol assigned to its slot; --- Make sure that the local node will not interfere with the sending of other nodes, especially the coordinator node; --- Whether the coordination frame is received, start the next NUT on time; --- If the local node is the coordinator, then send each coordination frame on time. The data link layer consists of the components of Table 1. Table 1 Data link layer components Component Description The Access Control Machine (ACM) receives and sends control frames and header information, determines the schedule and duration of the transmission Send LLC (TxLLC) Buffer SDUs from station management, network layer and transport layer, decide the next SDU to be sent The receiving LLC (RxLLC) performs the task of verifying the received link packets until they are validated by a good CRC Transmitter (TxM) Receives the request to send the MAC frame header, trailer, and Lpacket from the ACM, breaking it down to be sent to Byte converter request The receiver (RxM) assembles the byte symbols received from the serial-to-parallel converter into the received Lpackets and submits them to RxLLC Parallel serial converter The byte symbols are received, encoded and serialized, and they are sent to the physical layer as MAC symbols. Also responsible Generate CRC Serial Parallel Converter Receive MAC symbols from the physical layer, convert MAC symbols into bytes and send them to the receiver. Meanwhile also Responsible for checking CRC DLL management interface to maintain the station management variables belonging to the DLL to help manage the change of the synchronization parameters of the link The internal arrangements of these components and their interfaces are shown in Figure 4. The arrows indicate the main directions of control and data flow. Figure 4 data link layer internal structure Measure and control digital data communications Industrial control system with fieldbus Part 3. data link layer1 ScopeThis guidance document defines the data link layer requirements for nodes with deterministic control over the network. The guidance document is applicable to deterministic control network data link layer corresponds to GB/T 9387 in line with the OSI seven-mode The second layer of definition. Figure 5 shows the location of the data link layer in the OSI model. Note. Most terms and models in the data link layer use terms from ISO /IEC 8802-4..1990 or GB/T 15629.3-1995. Used The data type is described in GB /Z 26157.5-2010. Data Management. Figure 5 and the ISO /OSI model of the relationship2 MAC frame2.1 format The MAC frame shown in FIG. 6 is a protocol data unit (PDU) transmitted by the peer process at the data link layer. MAC frame Sections are sent in the following order. preamble, start delimiter, source MACID, zero or more Lpackets, CRC, and end delimiter. ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GBZ26157.3-2010_English be delivered?Answer: Upon your order, we will start to translate GBZ26157.3-2010_English as soon as possible, and keep you informed of the progress. The lead time is typically 9 ~ 13 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GBZ26157.3-2010_English with my colleagues?Answer: Yes. The purchased PDF of GBZ26157.3-2010_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. |
