《BS-EN-61158-6-9-2008.pdf》由会员分享，可在线阅读，更多相关《BS-EN-61158-6-9-2008.pdf（102页珍藏版）》请在三一文库上搜索。
1、BRITISH STANDARD BS EN 61158-6-9:2008 Industrial communication networks Fieldbus specifications Part 6-9: Application layer protocol specification Type 9 elements ICS 25.040.40; 35.100.70 ? Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Bo
2、eing Co/5910770001 Not for Resale, 08/14/2008 21:26:14 MDTNo reproduction or networking permitted without license from IHS -,-,- BS EN 61158-6-9:2008 This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2008 BSI 2008 ISBN 978 0 580 61629 7
3、 National foreword A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard cannot
4、confer immunity from legal obligations. Amendments/corrigenda issued since publication DateComments This British Standard is the UK implementation of EN 61158-6-9:2008. It is identical with IEC 61158-6-9:2007. Together with all of the other sections of BS EN 61158-6, it supersedes BS EN 61158-6:2004
5、 which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and control, including Fieldbus. Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Boeing C
6、o/5910770001 Not for Resale, 08/14/2008 21:26:14 MDTNo reproduction or networking permitted without license from IHS -,-,- EUROPEAN STANDARD EN 61158-6-9 NORME EUROPENNE EUROPISCHE NORM March 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrot
7、echnique 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 means reserved worldwide for CENELEC members. Ref. No. EN 61158-6-9:2008 E ICS 35.100.70; 25.040.40 Partially supersed
8、es EN 61158-6:2004 English version Industrial communication networks - Fieldbus specifications - Part 6-9: Application layer protocol specification - Type 9 elements (IEC 61158-6-9:2007) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 6-9: Spcification des services de
9、s couches dapplication - Elments de type 9 (CEI 61158-6-9:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-9: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 9-Elemente (IEC 61158-6-9:2007) This European Standard was approved by CENELEC on 2008-02-01. CENELEC member
10、s 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-date lists and bibliographical references concerning such national standards may be obtained on application
11、 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 the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has
12、 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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlan
13、ds, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Boeing Co/5910770001 Not for Resale, 08/14/2008 21:26:14 MDTNo reproduction or net
14、working permitted without license from IHS -,-,- Foreword The text of document 65C/476/FDIS, future edition 1 of IEC 61158-6-9, prepared 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 approv
15、ed by CENELEC as EN 61158-6-9 on 2008-02-01. This and the other parts of the EN 61158-6 series supersede EN 61158-6:2004. With respect to EN 61158-6:2004 the following changes were made: deletion of Type 6 fieldbus for lack of market relevance; addition of new fieldbus types; partition into multiple
16、 parts numbered 6-2, 6-3, 6-20. The following dates were fixed: latest date by which the EN has 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 withd
17、rawn (dow) 2011-02-01 NOTE Use of some of the associated protocol types is restricted by their 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 t
18、o be used with physical layer and application layer protocols in type combinations as specified 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 CENE
19、LEC. _ Endorsement notice The text of the International Standard IEC 61158-6-9:2007 was approved by CENELEC as a European Standard without any modification. _ BS EN 61158-6-9:2008 2 Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Boeing Co/
20、5910770001 Not for Resale, 08/14/2008 21:26:14 MDTNo reproduction or networking permitted without license from IHS -,-,- CONTENTS INTRODUCTION.6 1 Scope.7 1.1 General .7 1.2 Specifications7 1.3 Conformance.7 2 Normative references .8 3 Terms, definitions, symbols, abbreviations and conventions .8 3.
21、1 Terms and definitions from other ISO/IEC standards .8 3.2 IEC/TR 61158-1 terms.9 3.3 Abbreviations and symbols13 3.4 Conventions 14 3.5 Conventions used in state machines14 4 Abstract syntax.15 4.1 FAL-AR PDU abstract syntax.15 4.2 Abstract syntax of PDUBody18 4.3 Type definitions for ASEs 21 4.4
22、Abstract syntax of data types.26 5 Transfer syntax.27 5.1.1 General .27 5.1.2 Coding rules27 5.1.3 Structure of the identification information.28 6 Structure of FAL protocol state machines .37 7 AP-Context state machines.39 7.1 VCR PM structure39 7.2 VCR PM state machine39 8 FAL service protocol mac
23、hine (FSPM)52 8.1 General .52 8.2 FSPM state tables .52 8.3 Functions used by FSPM.55 8.4 Parameters of FSPM/ARPM primitives.55 9 Application relationship protocol machines (ARPMs) 55 9.1 AREP mapping to data-link layer .55 9.2 Application relationship protocol machines (ARPMs) .65 9.3 AREP state ma
24、chine primitive definitions.81 9.4 AREP state machine functions.84 10 DLL mapping protocol machine (DMPM).85 10.1 DMPM States 85 10.2 DMPM state table85 10.3 Primitives exchanged between data-link layer and DMPM .93 10.4 Functions used by DMPM96 Bibliography98 Figure 1 Insertion of identification in
25、formation in the FMS PDU27 Figure 2 Identification 28 Annex ZA (normative) Normative references to international publications with their corresponding European publications 99 BS EN 61158-6-9:2008 3 Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Li
26、censee=Boeing Co/5910770001 Not for Resale, 08/14/2008 21:26:14 MDTNo reproduction or networking permitted without license from IHS -,-,- Figure 3 Coding with identification .29 Figure 4 Coding without identification.29 Figure 5 Representation of the value true 29 Figure 6 Representation of the valu
27、e false .30 Figure 7 Coding of data of data type Integer16.30 Figure 8 Coding of data of data type Unsigned16.31 Figure 9 Coding of data of data type Floating Point31 Figure 10 Coding of data of data type Visible String.32 Figure 11 Coding of data of data type Octet String.32 Figure 12 Coding of dat
28、a of type Date33 Figure 13 Coding of data of data type Time-of-day.34 Figure 14 Coding of data of data type Time-difference .34 Figure 15 Coding of data of data type Bit String .35 Figure 16 Coding of data of data type Time-value 35 Figure 17 Coding of data of user data definitions with identifier36
29、 Figure 18 Coding of data of user data definitions without identifier.36 Figure 19 Coding of ID info for a SEQUENCE 36 Figure 20 Relationships among protocol machines and adjacent layers .38 Figure 21 Relationships among protocol machines and adjacent layers .39 Figure 22 VCR state machine 40 Figure
30、 23 State transition diagram of FSPM.52 Figure 24 State transition diagram of the QUU ARPM 66 Figure 25 State transition diagram of QUB ARPM 68 Figure 26 State transition diagram of the BNU ARPM.77 Figure 27 State transition diagram of DMPM 85 Table 1 Conventions used for state machines 14 Table 2 C
31、oding for Date type .33 Table 3 AP-VCR state machine transactions 41 Table 4 Primitives issued by FAL-User to VCR PM.50 Table 5 Primitives issued by VCR PM to FAL-User.50 Table 6 Primitives issued by VCR PM to FSPM51 Table 7 Primitives issued by FSPM to VCR PM52 Table 8 FSPM state table sender trans
32、actions 53 Table 9 FSPM state table receiver transactions.54 Table 10 Function SelectArep()55 Table 11 Parameters used with primitives exchanged between FSPM and ARPM 55 Table 12 QUU ARPM states.65 Table 13 QUU ARPM state table sender transactions66 Table 14 QUU ARPM state table receiver transaction
33、s67 Table 15 QUB ARPM states.68 Table 16 QUB ARPM state table sender transactions69 Table 17 QUB ARPM state table receiver transactions70 BS EN 61158-6-9:2008 4 Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Boeing Co/5910770001 Not for Re
34、sale, 08/14/2008 21:26:14 MDTNo reproduction or networking permitted without license from IHS -,-,- Table 18 BNU ARPM states .76 Table 19 BNU ARPM state table sender transactions77 Table 20 BNU ARPM state table receiver transactions 79 Table 21 Primitives issued from ARPM to DMPM .82 Table 22 Primit
35、ives issued by DMPM to ARPM.82 Table 23 Parameters used with primitives exchanged between ARPM and DMPM .83 Table 24 Function GetArepId().84 Table 25 Function BuildFAS-PDU 84 Table 26 Function FAS_Pdu_Type.84 Table 27 Function AbortIdentifier .84 Table 28 Function AbortReason.84 Table 29 Function Ab
36、ortDetail85 Table 30 DMPM state descriptions.85 Table 31 DMPM state table sender transactions86 Table 32 DMPM state table receiver transactions88 Table 33 Primitives exchanged between data-link layer and DMPM .94 Table 34 Function PickArep .96 Table 35 Function FindAREP .97 Table 36 Function LocateQ
37、ubArep .97 Table 37 Function SetIdentifier()97 BS EN 61158-6-9:2008 5 Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Boeing Co/5910770001 Not for Resale, 08/14/2008 21:26:14 MDTNo reproduction or networking permitted without license from I
38、HS -,-,- INTRODUCTION This part of IEC 61158 is one of a series produced to facilitate 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 protocol provi
39、des the application service by making use of the services available from the data-link or other immediately lower layer. The primary aim of this standard is to provide a set of rules for communication expressed in terms of the procedures to be carried out by peer application entities (AEs) at the ti
40、me of communication. These rules for communication are intended to provide a sound basis for development in order to serve a variety of purposes: as a guide for implementors and designers; for use in the testing and procurement of equipment; as part of an agreement for the admittance of systems into
41、 the open systems environment; as a refinement to the understanding of time-critical communications within OSI. This standard is concerned, in particular, with the communication and interworking of sensors, effectors and other automation devices. By using this standard together with other standards
42、positioned within the OSI or fieldbus reference models, otherwise incompatible systems may work together in any combination. BS EN 61158-6-9:2008 6 Copyright British Standards Institution Provided by IHS under license with BSI - Uncontrolled Copy Licensee=Boeing Co/5910770001 Not for Resale, 08/14/2
43、008 21:26:14 MDTNo reproduction or networking permitted without license from IHS -,-,- INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 6-9: Application layer protocol specification Type 9 elements 1 Scope 1.1 General The fieldbus Application Layer (FAL) provides user programs with a m
44、eans to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.” This standard provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an aut
45、omation 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 or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the ti
46、me window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This standard defines in an abstract way the externally visible behavior provided by the Type 9 fieldbus Application Layer in terms of a) the abstract syntax defining
47、the application layer protocol data units conveyed between communicating application entities, b) the transfer syntax defining the application layer protocol data units conveyed between communicating application entities, c) the application context state machine defining the application service behavior visible between communicating application entities; and d) the application relationship state machines defining the communication behavior visible between communicating application entities; and. The purpose of this