Home Cart Quotation About-Us
www.ChineseStandard.net
SEARCH

GBZ25105.1-2010 English PDF

Standard IDUSDBUY PDFLead-DaysStandard Title (Description)Status
GB/Z 25105.1-2010RFQ ASK 3 days Industrial communication networks -- Fieldbus specifications -- Type 10: PROFINET IO specifications -- Part 1: Application layer service definition Obsolete

Similar standards

GB/T 20438.5   GB/T 20438.4   GB/T 20438.3   GB/T 25105.2   GB/T 25105.1   GB/T 25105.3   

Basic data

Standard ID: GB/Z 25105.1-2010 (GB/Z25105.1-2010)
Description (Translated English): Industrial communication networks -- Fieldbus specifications -- Type 10: PROFINET IO specifications -- Part 1: Application layer service definition
Sector / Industry: National Standard
Classification of Chinese Standard: N10
Classification of International Standard: 25.040
Word Count Estimation: 500,528
Date of Issue: 2010-09-02
Date of Implementation: 2010-12-01
Quoted Standard: IEC 61158-2; IEC 61158-3-11; IEC 61158-3-1; IEC 61158-3-12; IEC 61158-3-13; IEC 61158-3-14; IEC 61158-3-16; IEC 61158 - 3-17; IEC 61158-3-18; IEC 61158-3-19; IEC 61158-3-21; IEC 61158-3-2; IEC 61158-3-22; IEC 61158-3-3; IEC 61158-3 -4; IEC 61158-3-7; IEC 61158-3-8; IEC 61158-4-11; IEC 61158-4-1; IEC 61158-4-12; IEC 61158-4-13; IEC 61158-4 - 14; IEC 61158-4-16; IEC 61158-4-17; IEC 61158-4-18; IEC 61158-4-19; IEC 61158-4-21; IEC 61158-4-2; IEC 61158-4-22; IEC 61158-4-3; IEC 61158-4-4; IEC 61158-4-7; IEC 61158-4-8; IEC 61158-5-10; IEC 61158-5-11; IEC 61158-5-1; IEC 61158-5-12; IEC 61158-5-13; IEC 61158-5-14; IEC 61158-5-15; IEC 61158-5-16; IEC 61158-5-17; IEC 61158-5-18; IEC 61158-5-19; IEC 61158-5-20; IEC 61158-5-21; IEC 61158-5-2; IEC 61158-5-22; IEC 61158-5-3; IEC 61158-5-4; IEC 61158 -5-5;
Adopted Standard: IEC 61158-5-10-2007, MOD
Regulation (derived from): ?National Standard Approval Announcement 2010 No.4 (Total No.159); PRC National Standard Approval Announcement 2014 No.22
Issuing agency(ies): Ministry of Health of the People's Republic of China
Summary: This standard applies to the fieldbus Application Layer (FAL), program provides a means for users to access the fieldbus communication environment. In this regard, can be considered FAL "window between the corresponding application. " This section provides a common element in the application of automation and fieldbus. The term "time-critical" is used to indicate the presence of a time window. At this point in the window, a clear requirement to complete certainty level of one or more specified actions. At this time the window is not completed within the required action, the application will result in the risk of failure to request these actions, even accompanied by causing equipment, equipment and possible physical danger.

GBZ25105.1-2010: Industrial communication networks -- Fieldbus specifications -- Type 10: PROFINET IO specifications -- Part 1: 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 conmunication networks. Fieldbus specifications.Type 10. PROFINET IO specifications. Part 1. Application layer service definition ICS 25.040 N10 People's Republic of China national standardization of technical guidance documents Industrial Communication Network Fieldbus Specification Type 10.PROFINETIO specification Part 1. Application layer service definition Part 1.Applicationlayerservicedefinition (IEC 61158-5-10.2007, Industrial communication networkss- Fieldbusspecifications-Part 5-10.Applicationlayerservicedefinition- Type10elements, MOD) 2010-09-02.2010-12-01 implementation General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China China National Standardization Administration released Directory Foreword XI Introduction Ⅻ 1 Scope 1 1.1 Overview 1 1.2 Service Specification 1 2 Normative references 2 3 Terms, definitions, abbreviations, symbols and conventions 3 3.1 Terms and definitions cited 3 3.2 Additional Terms and Definitions for AL Services 4 3.3 Additional Terms and Definitions for Media Redundancy 5 3.4 Abbreviations and symbols 6 3.5 agreed 8 3.6 Application Layer Service Description Concept 13 Concept 4 5 Data Type ASE 26 5.1 General 26 5.2 Data Type The formal definition of the object 28 5.3 FAL defined data type 30 5.4 Data Types ASE Service Specification 77 6 General Service Communication Model 77 6.1 Concept 77 6.2 ASE data types 77 6.3 ASE 77 Communication Models for Distributed Automation

8 Communication Model for Decentralized Peripherals

8.1 Concept 176 8.2 ASE data type 188 8.3 ASE 189 8.4 IO Device Behavior 425 8.5 IO Controller Behavior 476 8.6 Application Features 480 Appendix A (informative) device instance 482 Appendix B (informative) Ethernet interface components 484 Appendix C (informative) MAC address allocation program 487 Appendix D (Informative) Collection of Objects 488 Appendix E (Informative) Quick Start Time Measurement 489 Figure 1 and the OSI basic reference model of the relationship 13 Figure 2 fieldbus application layer architecture location 14 Figure 3 Client/Server Interaction 16 Figure 4 pull mode interaction 16 Figure 5 Push mode interaction 17 Figure 6 APO service transmitted by FAL 18 Figure 7 Application Entity Structure 19 Figure 8 FALASE example 20 Figure 9 FAL Object Management 20 Figure 10 ASE service delivery 21 Figure 11 defines and establishes AREP 23 Figure 12 FAL Architecture Components 24 Figure 13 data type class hierarchy 27 Figure 14 NetworkTime Date Relationship 51 Figure 15 PTCP Application 90 Figure 16 Clock Drift Measurement 102 Figure 17 Multiple Synchronization 102 Figure 18 MRP Communication Stack 104 Figure 19 has a ring topology 114 with one manager and multiple clients Figure 20 MRM 114 in open loop Figure 21 More than one MRM in ring 115 Figure 22 Media Redundancy Diagnostic Dependency 116 Figure 23 Positioning Destination of Redundant RT Frame 156 Figure 24 Example of Time Period on Local Ports 163 Figure 25 Example of Communication Between Control Equipment and Field Devices Figure 26 Example of Communication Between Engineering Station and Several Control and Field Devices Figure 27 Field Device and Server Station Communication Example 178 Figure 28 Example of communication between field devices 178 Figure 29 Architecture Unit (Generic) of an arbitrary API for an IO device 180 Figure 30 Architecture Unit Example for Interfaces and Ports in API0 1 181 Figure 31 Ports and Ports in API0 Structure Unit Example 2 181 Figure 32 Application Process Overview 183 Figure 33 IO device 183 with APs, slots and sub-slots Figure 34 Application Process with Application Objects (APO) 185 Figure 35 Access to Remote APO 186 Figure 36 Remote APO Access 187 for Provider/Consumer Associations Figure 37 Example of an AR with two AREPs 187 Figure 38 A record data object with a real object relationship 189 Figure 39 a record data object and the relationship between two actual objects 190 Figure 40 IOASE Service Interaction Overview.200 Figure 41 Alarm Source Resource Model Example 276 Figure 42 Universal Isochronous Application Model (Example) Figure 43 ASE Relationship in IO Devices Running in Isochronous Mode 318 Figure 44 State Machine Relationship 318 in IO Devices Operating in Isochronous Mode Figure 45 SyncCtl State Diagram 321 Figure 46 Output Status Diagram 323 Figure 47 Input Status Diagram 327 Figure 48 Communication Relationship Assignment to Application Relationships 405 Figure 49 implicit application relationship 408 Figure 50 Example IO application relationship (one to one) 409 Figure 51 Example IO Application Relationship (One to Many) 410 Figure 52 IO Device ASE State Machine Overview 426 Figure 53 Application Startup IO Device Status Figure 427 Figure 54 Adjacent Port Check Status Figure 436 Figure 55 IO Device PD Parameters Check Status Figure 445 Figure 56 Status of submodules 457 Figure 57 IO Controller Status During Startup Figure 477 Figure 58 Network Topology Example with Low Speed Wireless Segment 481 Figure 59 Example of a Media Redundancy Topology with Wireless Segment 481 Figure A.1 Example Model 482 Figure B.1 Ethernet interface scheme 484 Figure B.2 Bridge-capable Ethernet interface scheme Figure B.3 Schematic of an Ethernet Interface with Optical Ports 485 Figure B.4 Schematic of an Ethernet Interface with Bridge Capability Using Wireless Communication 486 Figure B.5 Schematic of an Ethernet Interface Using Wireless Communication 486 Figure C.1 Scheme of MAC Address Allocation 487 Figure D.1 Example of Intersection of IO Devices, Slot and AR 488 Figure E.1 Rapid start-up time measurement 489 Table 1 line (sub) bar selection table design 8 Table 2 (sub) bar selection table content 8 Table 3 Service Selection Table Design 9 Table 4 Service Selection Table Contents 9 Table 5 Parameter Selection Table Design 9 Table 6 Parameter Selection Table Contents 9 Table 7 class attribute selection table design 10 Table 8 Class Attribute Selection Table Contents 10 Table 9 PERSISTDEF 33 Table 10 VARTYPE 33 Table 11 ITEMQUALITYDEF 34 Table 12 STATEDEF 39 Table 13 GROUPERRORDEF 39 Table 14 ACCESSRIGHTSDEF 39 Table 15 HRESULT 40 Table 16 N2 value range 45 Table 17 N2 octet 45 Table 18 N4 Value Range 45 Table 19 N4 octet 45 Table 20 X2 value range 46 Table 21 X2 octet 46 Table 22 X4 value range 46 Table 23 X4 octets 46 Table 24 Unipolar 2.16 Value range 47 Table 25 Unipolar2.16 octet 47 Table 26 E2 value range 47 Table 27 E2 octet 48 Table 28 C4 value range 48 Table 29 V2 octet 48 Table 30 L2 octet 49 Table 31 UUIDs for Distributed Peripherals 49 Table 32 UUID 50 for distributed automation Table 33 NetworkTime values 52 Table 34 NetworkTime octets 52 Table 35 T2 value 53 Table 36 T4 value 53 Table 37 D2 value 53 Table 38 R2 value 54 Table 39 UNICODEString value 55 Table 40 UTF-8 character encoding scheme Table 41 OctetString2 Unsigned8 octets 67 Table 42 Float32 Unsigned8 octet 68 Table 43 Unsigned8 Unsigned8 octet 69 Table 44 Datatypes in VARIANT Median 71 Table 45 Unsigned16_S octet 73 Table 46 Unsigned16_S Meaning 73 Table 47 Integer16_S octet 73 Table 48 Integer16_S Meaning 73 Table 49 Unsigned8_S octet 74 Table 50 Unsigned8_S Meaning 74 OctetString_S octet 74 OctetString_S status bit 75 Table 53 Fmessagetrailerwith4octets 75 Table 54 Fmessagetrailerwith5octets76 Table 55 Get 82 Table 56 Set 84 Table 57 Identify 87 Table 58 Helo 89 Table 59 Startbridge 96 Table 60 Startslave 96 Table 61 Startmaster 98 Table 62 Stopbridge 99 Table 63 Stopslave 99 Table 64 Stopmaster 100 Table 65 Syncstatechange 101 Table 66 StartMRM 108 Table 67 StopMRM 110 Table 68 Redundancystatechange 111 Table 69 StartMRC 111 Table 70 StopMRC 112 Table 71 Neighborhoodchanged 113 Table 72 MRP Network/Connection Parameters 117 Table 73 MRM parameters 117 Table 74 MRC parameters 117 Table 75 SetProvData 118 Table 76 SetProvStatus 119 Table 77 PPMActivate 120 Table 78 Close 121 Table 79 Start 121 Table 80 Error 122 Table 81 GetConsData 122 Table 82 Getconsstatus 123 Table 83 SetRedRole 123 Table 84 CPMactivate 124 Table 85 APMSActivate 128 Table 86 APMRActivate 129 Table 87 APMSAData 131 Table 88 APMRAData 131 Table 89 APMRAck 132 Table 90 APMSError 133 Table 91 APMSErrorERRCLS/ERRCODE 133 Table 92 APMRError 133 Table 93 APMRErrorERRCLS/ERRCODE 134 Table 94 APMS_Close 134 Table 95 APMR_Close 134 Table 96 Connect 135 Table 97 Release 136 Table 98 Read 137 Table 99 Write 138 Table 100 Control 139 Table 101 System Capabilities 144 Table 102 Autonegotiationsupportandstatus 146 Table 103 MDIPowerSupport 146 Table 104 Linkaggregationstatus 147 Table 105 Remotesystemsdatachange 150 Table 106 ReductionRatio Allowed values 153 Table 107 FrameID 154 for RT_CLASS_3 Table 108 SyncFrame 154 Table 109 FrameSendOffset 154 Table 110 TxPortEntry 155 Table 111 Portstatechange 158 Table 112 Setportstate 158 Table 113 Flushfilteringdatabase 159 Table 114 IFWIRTScheduleAdd 159 Table 115 IFWIRTScheduleRemove 159 Table 116 IFWSchedule 160 Table 117 MAUtypechange 165 Table 118 SetMAUtype 165 Table 119 IPMulticast Address 167 Table 120 SetARPCache 167 Table 121 Enterprisenumber 170 Table 122 VendorOUI 170 Table 123 IRTScheduleAdd 171 Table 124 IRTScheduleRemove 172 Schedule 125 Table 126 NData 173 Table 127 AData 174 Table 128 CData 175 Table 129 Requirements and characteristics 176 Table 130 Persists Behavior of Data Objects 192 Table 131 Read 192 Table 132 ReadQuery 195 Table 133 Write 197 Table 134 Setinput 207 Table 135 SetInputIOCS 208 Table 136 GetInput 209 Table 137 GetInputIOCS 210 Table 138 NewInput 211 Table 139 SetinputAPDUdatastatus 211 Table 140 NewInputAPDUDataStatus 213 Table 141 ReadInputData 214 Table 142 SetOutput 216 Table 143 SetOutputIOCS 217 Table 144 GetOutput 218 Table 145 GetOutputIOCS 219 Table 146 NewOutput 220 Table 147 SetOutputAPDUDataStatus 221 Table 148 NewOutputAPDUDataStatus 222 Table 149 ReadOutputData 223 Table 150 ReadOutputSubstituteData 226 Table 151 WriteOutputSubstituteData 228 Table 152 ReadLogbook 231 Table 153 LogbookEvent 233 Table 154 Dependencies within ChannelProperties 237 Table 155 ExtChannelErrortype 239 Table 156 ExtChannelAddValue 241 for AccumulativeInfo Table 157 Dependencies within ChannelProperties for Manufacturer Specific Diagnostics 242 Table 158 ReadDeviceDiagnosis 243 Table 159 DiagnosisItem 246 Table 160 DiagnosisEvent 251 Table 161 Diagnostics Login Status Table 254 Table 162 Features Used in the Status Table Table 163 Required Maintenance Login Status Table 256 Table 164 Required Maintenance Login Status Table 257 Table 165 Qualified Login Status Table 258 Table 166 Alarmtype 263 Table 167 ChannelDiagnosis 264 Table 168 ManufacturerSpecificDiagnosis 264 Table 169 SubmoduleDiagnosisState 265 ARDiagnosisState 265 Table 171 UserStructureIdentifier 265 Table 172 Specifier semantics 267 Table 173 AlarmNotification 271 Table 174 AlarmAck 275 Table 175 ModuleState 279 Table 176 Usage of CR Type 282 Table 177 Detail 282 Table 178 ARInfo 283 Table 179 IdentInfo 283 Table 180 Connect 284 Table 181 ConnectDeviceAccess 292 Table 182 Release 294 Table 183 Abort 295 Table 184 EndOfParameter 295 Table 185 ApplicationReady 296 Table 186 ReadyForCompanion 298 Table 187 ReadExpectedIdentification 299 Table 188 ReadRealIdentification 303 Table 189 ReadIdentificationDifference 306 Table 190 WriteIsoMData 312 Table 191 ReadIsoMData 315 Table 192 SYNCHEvent 317 Table 193 primitives issued by the AL to the SyncCtl state machine 319 Table 194 primitives sent to the user by the SyncCtl state machine 319 Table 195 primitives sent to the user by the Input state machine 319 Table 196 primitives sent to the user by the Output state machine 319 Table 197 primitives sent by the SyncCtl state machine to the Output state machine 320 Table 198 is a primitive 320 sent by the Output state machine to the SyncCtl state machine Table.199 primitives sent by the SyncCtl state machine to the Input state machine 320 The table.200 is sent by the Output state machine to the AL primitive 320 Table.201 is the primitive 320 sent by the AL to the Output state machine The table 202 is sent by the Input state machine to the primitive 321 of AL The table 203 is sent by the AL to the primitive 321 of the Input state machine Table 204 SyncCtl Status Table 321 Table 205 Output Status Table 323 Table 206 Input Status Table 328 Table 207 Sub-slot number 333 of the interface sub-module Sub-slot number 334 of the port sub-module Sub-slot number 335 of the interface sub-module Sub-slot number 336 of the table 210 Sync interface sub-module Table 211 SyncPropertiesRole 338 Table 212 SyncClass 338 Table 213 Sub-slot No. 339 for optical submodules Table 214 FiberOpticTypes 339 Table 215 FiberOpticCableTypes 340 Table 216 WriteExpectedPortData 342 Table 217 WriteAdjustedPortData 345 Table 218 Readrealportdata 348 Table 219 ReadExpectedPortData 351 Table 220 ReadAdjustedPortData 354 Table 221 WriteIRData 356 Table 222 ReadIRData 360 Table 223 WriteSyncData 364 Table 224 ReadRealSyncData 367 Table 225 ReadExpectedSyncData 370 Table 226 ReadPDevData 373 Table 227 SyncStateInfo 380 Table 228 WriteAdjustedFiberOpticData 381 Table 229 ReadRealFiberOpticData 384 Table 230 WriteMRPInterfaceData 386 Table 231 ReadMRPInterfaceData 389 Table 232 WriteMRPPortData 392 Table 233 ReadMRPPortData 394 Table 234 WriteFSUData 396 Table 235 ReadFSUData 398 Table 236 SetTime 403 Table 237 DeviceAccess 413 Table 238 CompanionAR 413 Table 239 MediaRedundancy 418 Table 240 FrameID 418 Table 241 Readardata 422 Table 242 Status of Application Start IO Devices Table 428 Table 243 Starts IO Device Status Table Function 435 Table 244 Neighbor Port Check Status Table 436 Table 245 Status Table Function 445 for Neighbor Port Inspection Table 246 IO Device PD Parameters Check Status Table 446 Table 247 Status Table Function for IO Device PD Parameter Check 452 Table 248 Maintenance Status Required for Optical Fiber Table 452 Table 249 Required Maintenance Status for Optical Fiber Table 453 Table 250 Fiber Diagnostic Status Table 455 Table 251 Status of submodules Table 457 Table 252 Insertion Behavior Status Table 471 Table 253 Status of pull-out behavior Table 473 Table 254 Status of PTCP Behavior Table 474 Table 255 Features Used by PTCP Behavior 475 Table 256 Status of the IO controller during startup Table 478

Foreword

GB /Z 25105-2010 "industrial communication network field bus specification type 10.PROFINETIO specification" is divided into the following three section. --- Part 1. Application layer service definition; --- Part 2. Application layer protocol specification; --- Part 3. PROFINETIO communication rules. This section GB /Z 25105-2010 Part 1. This part of the revision adopted IEC 61158-5-10.2007 (English version), the technical content of the original international standards there is no difference, for the convenience of me National users, in the text structure of the layout of the appropriate adjustments, and press GB/T 1.1-2000 requirements for editing. This part of the Appendix A, Appendix B, Appendix C, Appendix D, Appendix E is an informative annex. 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. China Mechatronics Technology Applications Association, Machinery Industry Instrumentation Technology Institute of Economics, China Branch Institute of Shenyang Institute of Automation, Shanghai Automation Instrumentation Co., Ltd., Southwest University, Tsinghua University, Zhengzhou Institute of Light Industry Electrical Information Engineering College, Beijing Hollysys Systems Engineering Co., Ltd., Beijing China Control Technology Co., Ltd., Beijing Machinery Industry Automation Research The China Instrument Industry Association, Siemens (China) Co., Ltd., Phoenix Contact (Nanjing) R & D Engineering Technology Center Co., Ltd. The main drafters of this section. Li Baihuang, Wang Chunxi, Liu Dan, Wang Linkun, Liu Yunan, Yang Zhijia, Bao Weihua, Liu Feng, Wang Jinbiao, Tang Jiyang, Wang Yonghua, Luo An, Chen Xiaofeng, Dong Jingchen, Ouyang Jinsong, Huadun Yan, Zhang Dandan, Guo Jianfeng, Dou Lianwang, Zhang Long.

Introduction

AL Services Interconnect for automation system components. It is in the series of standards defined by the following "three-tier" fieldbus reference model Other standards. --- Physical layer; ---data link layer; --- Application layer. Application layer protocols provide application services through the use of data link layers or other services that are available adjacent to lower layers. This section defines Application service features that can be used by fieldbus applications and/or system management. The term "service" refers to the abstraction capability provided to an adjacent upper layer by one layer of the OSI basic reference model. Therefore, as defined in this section Application layer services are conceptually structured services that are independent of the management and implementation components. Industrial Communication Network Fieldbus Specification Type 10.PROFINETIO specification Part 1. Application layer service definition

1 Scope

1.1 Overview The Fieldbus Application Layer (FAL) provides the user program with the means to access the fieldbus communication environment. In this regard, FAL can be visualized As "the window between the corresponding applications". GB /Z 25105 of this part of the application in the automation environment for the basic requirements of the strict time and non-strict time requirements Messaging Provides general purpose elements and PROFINETO fieldbus-specific information. The term "strict time requirement" is used to indicate that there is one Time windows, within this time window, require one or more specified actions to be performed at a certain definite level of certainty. At this time window did not complete the rules The act of fixing results in the risk of invalidating the application requesting these actions, even with instruments, equipment and possible personal danger. This section abstractly defines the externally visible services provided by the fieldbus application layer in the following ways. a) Abstract models for defining application resources (objects) that users can utilize by utilizing FAL services; b) Service primitive actions and events; c) the parameters associated with each primitive action and event, and the form they take; d) the interrelationship between these actions and events and their effective sequence. The purpose of this section is to define a number of services to provide. a) FAL users at the interface between the user and application layers of the fieldbus reference model; b) System management at the interface between the application layer and system management of the fieldbus reference model. This section based on OSI basic reference model (see GB/T 9387) and OSI application layer structure (GB/T 17176) provides that the field bus should Structure and service with layers. FAL services and pr......
Image     

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GBZ25105.1-2010_English be delivered?

Answer: Upon your order, we will start to translate GBZ25105.1-2010_English as soon as possible, and keep you informed of the progress. The lead time is typically 1 ~ 3 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GBZ25105.1-2010_English with my colleagues?

Answer: Yes. The purchased PDF of GBZ25105.1-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+ countries

Question 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.