SIST EN 61158-6-3:2008
Industrial communication networks - Fieldbus specifications - Part 6-3: Application layer protocol specification - Type 3 elements
Industrial communication networks - Fieldbus specifications - Part 6-3: Application layer protocol specification - Type 3 elements
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." This 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 3 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 time 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 3 fieldbus application layer in terms of a) the abstract syntax defining 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 standard is to define the protocol provided to 1) define the wire-representation of the service primitives specified in IEC 61158-5-3, and 2) define the externally visible behavior associated with their transfer. This standard specifies the protocol of the Type 3 fieldbus application layer, in conformance 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 Service 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 instances 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 applications 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 such object behavior. In addition to these services, some supporting services are also defined in this standard to pr ovide access to the FAL to control certain aspects of its operation.
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-3: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 3-Elemente
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-3: Spécification des services des couches d'application - Eléments de type 3
Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 6-3. del: Specifikacija protokola na aplikacijskem nivoju - Elementi tipa 3 (IEC 61158-6-3:2007)
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 6-3. del: Specifikacija protokola na aplikacijskem nivoju - Elementi tipa 3 (IEC 61158-6-3:2007)Industrielle Kommunikationsnetze - Feldbusse - Teil 6-3: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 3-ElementeRéseaux de communication industriels - Spécifications des bus de terrain - Partie 6-3: Spécification des services des couches d'application - Eléments de type 3Industrial communication networks - Fieldbus specifications - Part 6-3: Application layer protocol specification - Type 3 elements35.110OmreževanjeNetworking35.100.70Uporabniški slojApplication layer25.040.40Merjenje in krmiljenje industrijskih postopkovIndustrial process measurement and controlICS:Ta slovenski standard je istoveten z:EN 61158-6-3:2008SIST EN 61158-6-3:2008en,de01-julij-2008SIST EN 61158-6-3:2008SLOVENSKI
STANDARDSIST EN 61158-6:20041DGRPHãþD
EUROPEAN STANDARD EN 61158-6-3 NORME EUROPÉENNE
EUROPÄISCHE NORM March 2008
CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für 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-3:2008 E
ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-6:2004
English version
Industrial communication networks -
Fieldbus specifications -
Part 6-3: Application layer protocol specification -
Type 3 elements (IEC 61158-6-3:2007)
Réseaux de communication industriels -
Spécifications des bus de terrain -
Partie 6-3: Spécification des services
des couches d'application -
Eléments de type 3 (CEI 61158-6-3:2007)
Industrielle Kommunikationsnetze -
Feldbusse -
Teil 6-3: Protokollspezifikation
des Application Layer (Anwendungsschicht) -
Typ 3-Elemente (IEC 61158-6-3: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-date 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 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, France, 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.
EN 61158-6-3:2008
- 2 -
Foreword The text of document 65C/476/FDIS, future edition 1 of IEC 61158-6-3, 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 approved by CENELEC as EN 61158-6-3 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 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 withdrawn
(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 to 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. IEC and CENELEC draw attention to the fact that it is claimed that compliance with this standard may involve the use of patents as follows, where the [xx] notation indicates the holder of the patent right:
The following patent rights for Type 3 have been announced:
DE 36 43 979 C2 [SI] Deterministisches Zugriffsverfahren nach dem Tokenprinzip für eine Datenübertragung
DE 36 43 979 A1 [SI]
Deterministisches Zugriffsverfahren nach dem Tokenprinzip für eine Datenübertragung IEC and CENELEC take no position concerning the evidence, validity and scope of these patent rights. The holders of these patent rights have assured IEC that they are willing to negotiate licences under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holders of these patent rights are registered with IEC. Information may be obtained from:
[SI]: SIEMENS AG
Ludwig Winkel
Siemensallee 73
D-76181 Karlsruhe
Germany Attention is drawn to the possibility that some of the elements of this standard may be the subject of patent rights other than those identified above. IEC and CENELEC shall not be held responsible for identifying any or all such patent rights. Annex ZA has been added by CENELEC. __________
- 3 - EN 61158-6-3:2008
Endorsement notice The text of the International Standard IEC 61158-6-3:2007 was approved 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: IEC 61784-1 NOTE
Harmonized as EN 61784-1:2008 (not modified). IEC 61784-2 NOTE
Harmonized as EN 61784-2:2008 (not modified). __________
EN 61158-6-3:2008
- 4 -
Annex ZA
(normative)
Normative references to international publications with their corresponding European publications
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
NOTE
When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies.
Publication Year Title EN/HD Year IEC 60559 - 1) Binary floating-point arithmetic for
microprocessor systems HD 592 S1 1991 2)
IEC 61158-3-3 - 1) Industrial communication networks -
Fieldbus specifications -
Part 3-3: Data-link layer service definition - Type 3 elementsEN 61158-3-3 2008 2)
IEC 61158-4-3 - 1) Industrial communication networks -
Fieldbus specifications -
Part 4-3: Data-link layer protocol
specification - Type 3 elements
EN 61158-4-3 2008 2)
IEC 61158-5-3 - 1) Industrial communication networks -
Fieldbus specifications -
Part 5-3: Application layer service definition - Type 3 elements EN 61158-5-3 2008 2)
ISO/IEC 7498-1 - 1) Information technology - Open Systems Interconnection - Basic Reference Model:
The Basic ModelEN ISO/IEC 7498-1 1995 2)
ISO/IEC 8822 - 1) Information technology - Open Systems Interconnection - Presentation service definition - -
ISO/IEC 8824-2 - 1) Information technology - Abstract Syntax Notation One (ASN.1): Information object specification - -
ISO/IEC 9545 - 1) Information technology - Open Systems Interconnection - Application Layer structure - -
ISO/IEC 10731 - 1) Information technology - Open Systems Interconnection - Basic reference model - Conventions for the definition of OSI services - -
1) Undated reference.
2) Valid edition at date of issue.
IEC 61158-6-3Edition 1.0 2007-12INTERNATIONAL STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-3: Application layer protocol specification – Type 3 elements
INTERNATIONAL ELECTROTECHNICAL COMMISSION XNICS 35.100.70; 25.040.40 PRICE CODEISBN 2-8318-9475-1
– 2 – 61158-6-3 © IEC:2007(E) CONTENTS FOREWORD.8 INTRODUCTION.10 1 Scope.11 1.1 General.11 1.2 Specifications.12 1.3 Conformance.12 2 Normative references.12 3 Terms, definitions, abbreviations, symbols and conventions.13 3.1 Referenced terms and definitions.13 3.2 Additional definitions.14 3.3 Abbreviations and symbols.17 3.4 Conventions.19 3.5 Conventions used in state machines.21 4 FAL syntax description.24 4.1 APDU abstract syntax.24 4.2 Data types.28 5 Transfer syntax.30 5.1 Coding of basic data types.30 5.2 Coding section related to data exchange PDUs.33 5.3 Coding section related to slave diagnosis PDUs.33 5.4 Coding section related to parameterisation PDU.44 5.5 Coding section related to configurationPDUs.50 5.6 Coding section related to global control PDUs.54 5.7 Coding section related to clock-value-PDUs.55 5.8 Coding section related to function identification and errors.56 5.9 Coding section related to master diagnosis PDU.60 5.10 Coding section related to upload/download/act para PDUs.62 5.11 Coding section related to the bus parameter set.64 5.12 Coding section related to the slave parameter set.66 5.13 Coding section related to statistic counters.70 5.14 Coding section related to set slave address PDU.70 5.15 Coding section related to initiate/abort PDUs.70 5.16 Coding section related to read/write/data transport PDUs.74 5.17 Coding section related to load region and function invocation PDUs.74 5.18 Examples of diagnosis-RES-PDUs.77 5.19 Example of Chk_Cfg-REQ-PDU.79 5.20 Examples of Chk_Cfg-REQ-PDUs with DPV1 data types.80 5.21 Example structure of the Data_Unit for Data_Exchange.81 6 FAL protocol state machines.83 6.1 Overall structure.83 6.2 Assignment of state machines to devices.84 6.3 Overview DP-slave.85 6.4 Overview DP-master (class 1).87 6.5 Overview DP-master (class 2).88 6.6 Cyclic communication between DP-master (class 1) and DP-slave.89 6.7 Acyclic communication between DP-master (class 2) and DP-master (class 1).90 6.8 Acyclic communication between DP-master (class 1) and DP-slave.92
61158-6-3 © IEC:2007(E) – 3 –
6.9 Application relationship monitoring.94 7 AP-context state machine.99 8 FAL service protocol machines (FSPMs).99 8.1 FSPMS.99 8.2 FSPMM1.134 8.3 FSPMM2.170 9 Application relationship protocol machines (ARPMs).189 9.1 MSCY1S.189 9.2 MSAC1S.221 9.3 SSCY1S.234 9.4 MSRM2S.238 9.5 MSAC2S.243 9.6 MSCS1S.260 9.7 MSCY1M.262 9.8 MSAL1M.282 9.9 MSAC1M.291 9.10 MMAC1.304 9.11 MSCS1M.311 9.12 MSAC2M.316 9.13 MMAC2.332 10 DLL mapping protocol machines (DMPMs).339 10.1 DMPMS.339 10.2 DMPMM1.353 10.3 DMPMM2.370 11 Parameters for a DP-slave.379 Bibliography.380
Figure 1 – Common structure of specific fields.20 Figure 2 – Coding of the data type BinaryDate.31 Figure 3 – Encoding of TimeOfDay value.31 Figure 4 – Encoding of Time Difference value.32 Figure 5 – Encoding of Network Time value.32 Figure 6 – Encoding of Network Time Difference value.33 Figure 7 – Example Modul_Status_Array.38 Figure 8 – Example of Ext_Diag_Data in case of DPV1 diagnosis format
with alarm and status PDU.78 Figure 9 – Example of Ext_Diag_Data in case of the basic diagnosis format.79 Figure 10 – Example of a special identifier format.79 Figure 11 – Example of a special identifier format with data types.80 Figure 12 – Example of a special identifier format with data types.80 Figure 13 – Example of a empty slot with data types.81 Figure 14 – Example for multi-variable device with AI and DO function blocks.81 Figure 15 – Identifiers (ID).82 Figure 16 – Identifier list.82 Figure 17 – Structure of the Data_Unit for the request- and response-DLPDU.82 Figure 18 – Structuring of the protocol machines and adjacent layers in a DP-slave.86
– 4 – 61158-6-3 © IEC:2007(E) Figure 19 – Structuring of the protocol machines and adjacent layers in a DP-master (class 1).87 Figure 20 – Structuring of the protocol machines and adjacent layers in a DP-master (class 2).88 Figure 21 – Sequence of the communication between DP-master and DP-slave.90 Figure 22 – Sequence of communication between DP-master (class 2) and DP-master (class 1).92 Figure 23 – Sequence of acyclic communication between DP-master (class 1) and DP-slave.94 Figure 24 – Example for connection establishment on MS2.96 Figure 25 – Idle at master-side on MS2.97 Figure 26 – Idle at slave-side on MS2.98 Figure 27 – Example for connection establishment on MS2(server-side).239 Figure 28 – Structure of RM entries in the RM_Registry.240
Table 1 – State machine description elements.21 Table 2 – Description of state machine elements.21 Table 3 – Conventions used in state machines.22 Table 4 – APDU syntax.24 Table 5 – Substitutions.27 Table 6 – Alarm_Type range.36 Table 7 – Status_Type value range.36 Table 8 – Alarm_Specifier.37 Table 9 – Range of Modul_Status_Entry (1-4).39 Table 10 – Error type.41 Table 11 – Specification of the bits Lock_Req and Unlock_Req.44 Table 12 – Range of Length_of_Manufacturer_Specific_Data if used in Chk_Cfg-REQ-PDU.51 Table 13 – Range of Length_of_Manufacturer_Specific_Data if used in Get_Cfg-RES-PDU.51 Table 14 – Values (codes) for data types.53 Table 15 – Specification of the bits for Un-/Sync and Un-/Freeze.54 Table 16 – Coding of the Function_Code/ Function_Num.57 Table 17 – Coding of the Error_Code / Function_Num.58 Table 18 – Values of Error_Decode.58 Table 19 – Coding of Error_Code_1 at DPV1.59 Table 20 – Values of MDiag_Identifier.60 Table 21 – Values for Area_Code_UpDownload.62 Table 22 – Values for Area_CodeActBrct.63 Table 23 – Values for Area_CodeAct.63 Table 24 – Values for Data_rate.64 Table 25 – Values for Slave_Type.67 Table 26 – Values for Alarm_Mode.68 Table 27 – Values for Subnet.73 Table 28 – Values of reason code if instance is DLL.73
61158-6-3 © IEC:2007(E) – 5 –
Table 29 – Values of reason code if instance is MS2.73 Table 30 – Values of Extended_Function_Num.74 Table 31 – Values of FI_State.76 Table 32 – Assignment of state machines.85 Table 33 – Primitives issued by AP-Context to FSPMS.99 Table 34 – Primitives issued by FSPMS to AP-Context.101 Table 35 – FSPMS state table.108 Table 36 – Functions used by the FSPMS.133 Table 37 – Primitives issued by AP-Context to FSPMM1.135 Table 38 – Primitives issued by FSPMM1 to AP-Context.137 Table 39 – FSPMM1 state table.144 Table 40 – Functions used by the FSPMM1.170 Table 41 – Primitives issued by AP-Context to FSPMM2.171 Table 42 – Primitives issued by FSPMM2 to AP-Context.173 Table 43 – FSPMM2 state table.176 Table 44 – Functions used by the FSPMM2.188 Table 45 – Primitives issued by FSPMS to MSCY1S.189 Table 46 – Primitives issued by MSCY1S to FSPMS.190 Table 47 – Rules for DPV1_Status_1, DPV1_Status_2 and DPV1_Status_3 check.192 Table 48 – MSCY1S state table.197 Table 49 – Functions used by the MSCY1S.219 Table 50 – Primitives issued by FSPMS to MSAC1S.221 Table 51 – Primitives issued by MSAC1S to FSPMS.222 Table 52 – Primitives issued by MSCY1S to MSAC1S.222 Table 53 – Primitives issued by MSAC1S to MSCY1S.222 Table 54 – Parameter used with primitives exchanged between MSAC1S and MSCY1S.222 Table 55 – MSAC1S state table.224 Table 56 – Functions used by the MSAC1S.234 Table 57 – Primitives issued by FSPMS to SSCY1S.234 Table 58 – Primitives issued by SSCY1S to FSPMS.235 Table 59 – SSCY1S state table.236 Table 60 – Functions used by the SSCY1S.237 Table 61 – Primitives issued by FSPMS to MSRM2S.238 Table 62 – Primitives issued by MSRM2S to FSPMS.238 Table 63 – MSRM2S state table.241 Table 64 – Primitives issued by FSPMS to MSAC2S.244 Table 65 – Primitives issued by MSAC2S to FSPMS.245 Table 66 – Primitives issued by MSRM2S to MSAC2S.245 Table 67 – Primitives issued by MSAC2S to MSRM2S.246 Table 68 – Parameter used with primitives exchanged with MSAC2S.246 Table 69 – MSAC2S state table.249 Table 70 – Primitives issued by MSCS1S to FSPMS.261 Table 71 – MSCS1S state table.262
– 6 – 61158-6-3 © IEC:2007(E) Table 72 – Primitives issued by FSPMM1 to MSCY1M.263 Table 73 – Primitives issued by MSCY1M to FSPMM1.264 Table 74 – Parameters used with primitives exchanged between FSPMM1 and MSCY1M.264 Table 75 – MSCY1M state table.267 Table 76 – Primitives issued by FSPMM1 to MSAL1M.282 Table 77 – Primitives issued by MSAL1M to FSPMM1.283 Table 78 – Primitives issued by MSCY1M to MSAL1M.283 Table 79 – Primitives issued by MSAL1M to MSCY1M.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.