《BS EN 61158-5-9-2008 工业通讯网络.现场总线规范.应用层服务定义.9型元件.pdf》由会员分享，可在线阅读，更多相关《BS EN 61158-5-9-2008 工业通讯网络.现场总线规范.应用层服务定义.9型元件.pdf（124页珍藏版）》请在三一文库上搜索。
1、BRITISH STANDARD BS EN 61158-5-9:2008 Industrial communication networks Fieldbus specifications Part 5-9: Application layer service definition Type 9 elements ICS 25.040.40; 35.100.70 BS EN 61158-5-9:2008 This British Standard was published under the authority of the Standards Policy and Strategy Co
2、mmittee on 30 June 2008 BSI 2008 ISBN 978 0 580 61594 8 National foreword This British Standard is the UK implementation of EN 61158-5-9:2008. It is identical with IEC 61158-5-9:2007. Together with all of the other sections of BS EN 61158-5, it supersedes BS EN 61158-5:2004 which is withdrawn. The U
3、K participation in its preparation was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and control, including fieldbus. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to includ
4、e all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard cannot confer immunity from legal obligations. Amendments/corrigenda issued since publication DateComments EUROPEAN STANDARD EN 61158-5-9 NORME EUROPENNE EUROPISCHE NOR
5、M March 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2008 CENELEC - All rights of exploitation in any form and by any me
6、ans reserved worldwide for CENELEC members. Ref. No. EN 61158-5-9:2008 E ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-5:2004 English version Industrial communication networks - Fieldbus specifications - Part 5-9: Application layer service definition - Type 9 elements (IEC 61158-5-9:2007) R
7、seaux de communication industriels - Spcifications des bus de terrain - Partie 5-9: Dfinition des services des couches dapplication - Elments de type 9 (CEI 61158-5-9:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 5-9: Dienstfestlegungen des Application Layer (Anwendungsschicht) - Typ 9-E
8、lemente (IEC 61158-5-9:2007) This European Standard was approved by CENELEC on 2008-02-01. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-da
9、te lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under
10、 the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Franc
11、e, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Foreword The text of document 65C/475/FDIS, future edition 1 of IEC 61158-5-9, prepar
12、ed by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-5-9 on 2008-02-01. This and the other parts of the EN 61158-5 series supersede EN 61158-5:2004. With respect
13、 to EN 61158-5:2004 the following changes were made: deletion of Type 6 fieldbus and Type 1 fieldbus application layer, for lack of market relevance; addition of new fieldbus types; partition into multiple parts numbered 5-2, 5-3, , 5-20. The following dates were fixed: latest date by which the EN h
14、as to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2008-11-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2011-02-01 NOTE Use of some of the associated protocol types is restricted by thei
15、r intellectual-property-right holders. In all cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer protocol type to be used with physical layer and application layer protocols in type combinations as specifi
16、ed explicitly in the EN 61784 series. Use of the various protocol types in other combinations may require permission from their respective intellectual-property-right holders. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 61158-5-9:2007 was appro
17、ved by CENELEC as a European Standard without any modification. In the official version, for Bibliography, the following notes have to be added for the standards indicated: _ BS EN 61158-5-9:2008 2 CONTENTS INTRODUCTION. 1 Scope. 1.1 Overview . 1.2 Specifications 1.3 Conformance. 2 Normative referen
18、ces . 3 Terms, definitions, symbols, abbreviations and conventions . 3.1 ISO/IEC 7498-1 terms . 3.2 ISO/IEC 8822 terms 3.3 ISO/IEC 9545 terms 3.4 ISO/IEC 8824 terms 3.5 IEC/TR 61158-1 terms. 3.6 Type 9 fieldbus application-layer specific definitions1 3.7 Abbreviations and symbols1 3.8 Conventions 1
19、4 Concepts1 5 Data type ASE1 5.1 Overview .1 5.2 Formal definition of data type objects 5.3 FAL defined data types2 5.4 Data type ASE service specification 2 5.5 Summary of data types2 6 Communication model specification2 6.1 Concepts.2 6.2 Common parameters .2 6.3 ASEs.2 6.4 ARs .11 6.5 Summary of
20、classes 11 6.6 Permitted services by AREP role.11 Bibliography1 Figure 1 Data type class hierarchy.1 Figure 2 VFD model.2 Figure 3 Abstract model of an automation system (VFD)2 Figure 4 Source OD/remote OD .3 Figure 5 Put OD state machine 4 Figure 6 Transaction object state machine .5 Figure 7 Conte
21、xt test of two features-supported with different bitstring length Figure 8 Overview of event 7 Figure 9 Event state machine.8 Figure 10 Domain genericdownload/download state machine (server)9 Figure 11 Domain upload state machine (server) .10 BS EN 61158-5-9:2008 3 - - - - 1 Figure 12 State diagram.
22、11 Table 1 Data type summary .2 Table 2 Logical status 2 Table 3 Status2 Table 4 Unsolicited status Table 5 Identify3 Table 6 Structure of the object dictionary.3 Table 7 Structure of the static list of types .3 Table 8 Structure of the static object dictionary3 Table 9 Structure of the dynamic list
23、 of variable lists3 Table 10 Structure of the dynamic list of program invocations3 Table 11 Empty object dictionary .3 Table 12 Get OD service parameters .4 Table 13 Initiate put OD service parameters 4 Table 14 Put OD service parameters4 Table 15 Terminate put OD service parameters .4 Table 16 Put
24、OD state transitions.4 Table 17 Attribute FMS features supported Table 18 Transaction object state transitions .5 Table 19 Initiate service parameters 5 Table 20 Failure reasons .5 Table 21 Abort service parameters.5 Table 22 User abort reasons5 Table 23 APO ASE abort reasons 5 Table 24 Reject servi
25、ce parameters .5 Table 25 Reject APDU reasons5 Table 26 Compatibility of the local context to the remote context .5 Table 27 Unconfirmed send service parameters.6 Table 28 Confirmed send service parameters 6 Table 29 AR-Abort service parameters.6 Table 30 Compel service parameters .6 Table 31 Get bu
26、ffered message service parameters.6 Table 32 AR-Status service parameters .6 Table 33 Simple variable access group membership 6 Table 34 Simple variable access rights membership 6 Table 35 Array variable access group membership 6 Table 36 Array variable access rights membership. Table 37 Variable li
27、st access group membership7 Table 38 Variable list access rights membership7 Table 39 Read service parameters.7 Table 40 Write service parameters.7 Table 41 Information report service parameters .7 BS EN 61158-5-9:2008 4 Table 42 Define variable list service parameters 7 Table 43 Delete variable lis
28、t service parameters 7 Table 44 Event access group membership . Table 45 Event access rights membership .8 Table 46 Event notification service parameters 8 Table 47 Acknowledge event notification service parameters .8 Table 48 Alter event condition monitoring service parameters8 Table 49 Event state
29、 transitions .8 Table 50 Domain access group membership 8 Table 51 Domain access rights membership 8 Table 52 GenericInitiateDownloadSequence 8 Table 53 GenericDownloadSegment 8 Table 54 GenericTerminateDownloadSequence .9 Table 55 InitiateDownloadSequence 9 Table 56 DownloadSegment 9 Table 57 Termi
30、nateDownloadSequence .9 Table 58 RequestDomainDownload9 Table 59 InitiateUploadSequence.9 Table 60 UploadSegment.9 Table 61 TerminateUploadSequence .9 Table 62 RequestDomainUpload9 Table 63 Domain genericDownload/download state machine (server) 9 Table 64 Domain upload state machine (server) 10 Tabl
31、e 65 Program invocation access group membership 10 Table 66 Program invocation access group membership 10 Table 67 Create program invocation service parameters10 Table 68 Delete program invocation service parameters 10 Table 69 Start service parameters .10 Table 70 Stop service parameters10 Table 71
32、 Resume service parameters 10 Table 72 Reset service parameters1 Table 73 Kill service parameters 11 Table 74 Program invocation state machine.11 Table 75 Class summary11 Table 76 Services by AREP role 11 BS EN 61158-5-9:2008 5 INTRODUCTION This part of IEC 61158 is one of a series produced to facil
33、itate the interconnection of automation system components. It is related to other standards in the set as defined by the “three-layer” fieldbus reference model described in IEC/TR 61158-1. The application service is provided by the application protocol making use of the services available from the d
34、ata-link or other immediately lower layer. This standard defines the application service characteristics that fieldbus applications and/or system management may exploit. Throughout the set of fieldbus standards, the term “service” refers to the abstract capability provided by one layer of the OSI Ba
35、sic Reference Model to the layer immediately above. Thus, the application layer service defined in this standard is a conceptual architectural service, independent of administrative and implementation divisions. BS EN 61158-5-9:2008 6 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 5-
36、9: Application layer service definition Type 9 elements 1 Scope 1.1 Overview The fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.” Thi
37、s standard provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 9 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one
38、 or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This standard defines
39、in an abstract way the externally visible service provided by the different Types of the fieldbus Application Layer in terms of a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events
40、of the service; c) the parameters associated with each primitive action and event, and the form which they take; and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this standard is to define the services provided to 1) the FAL user at the boundar
41、y between the user and the Application Layer of the Fieldbus Reference Model, and 2) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This standard specifies the structure and services of the IEC fieldbus Application Layer, in c
42、onformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Ser
43、vice Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the in
44、stances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applic
45、ations are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing BS EN 61158-5-9:2008 7 such object behavior. In addition to these services, some supporting services are also defined in t
46、his standard to provide access to the FAL to control certain aspects of its operation. 1.2 Specifications The principal objective of this standard is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic R
47、eference Model in guiding the development of application layer protocols for time- critical communications. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various types of IEC 61158. This specification may be used as the basis for formal application programming interfaces. Nevertheless, it is not a formal programming interface, and any such interface will need to address implementation issues not covered by this specif