SIST EN 61158-6-20:2008

SLOVENSKI STANDARD
SIST EN 61158-6-20:2008
01-julij-2008
1DGRPHãþD
SIST EN 61158-6:2004
Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 6-20. del:
Specifikacija protokola na aplikacijskem nivoju - Elementi tipa 20 (IEC 61158-6-
20:2007)
Industrial communication networks - Fieldbus specifications - Part 6-20: Application layer
protocol specification - Type 20 elements
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-20: Protokollspezifikation des
Application Layer (Anwendungsschicht) - Typ 20-Elemente
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-20:
Spécification des services des couches d'application - Eléments de type 20
Ta slovenski standard je istoveten z: EN 61158-6-20:2008
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.100.70 Uporabniški sloj Application layer
35.110 Omreževanje Networking
SIST EN 61158-6-20:2008 en,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

EUROPEAN STANDARD
EN 61158-6-20

NORME EUROPÉENNE
March 2008
EUROPÄISCHE NORM

ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-6:2004


English version


Industrial communication networks -
Fieldbus specifications -
Part 6-20: Application layer protocol specification -
Type 20 elements
(IEC 61158-6-20:2007)


Réseaux de communication industriels -  Industrielle Kommunikationsnetze -
Spécifications des bus de terrain - Feldbusse -
Partie 6-20: Spécification des services Teil 6-20: Protokollspezifikation
des couches d'application - des Application Layer
Eléments de type 20 (Anwendungsschicht) -
(CEI 61158-6-20:2007) Typ 20-Elemente
(IEC 61158-6-20: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.

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-20:2008 E

---------------------- Page: 2 ----------------------

EN 61158-6-20:2008 - 2 -
Foreword
The text of document 65C/476/FDIS, future edition 1 of IEC 61158-6-20, 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-20 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.
Annex ZA has been added by CENELEC.
__________
Endorsement notice
The text of the International Standard IEC 61158-6-20: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).
__________

---------------------- Page: 3 ----------------------

- 3 - EN 61158-6-20:2008
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

1) 2)
IEC 60559 - Binary floating-point arithmetic for HD 592 S1 1991
microprocessor systems


1) 2)
IEC 61158-5-20 - Industrial communication networks - EN 61158-5-20 2008
Fieldbus specifications -
Part 5-20: Application layer service definition -
Type 20 elements


1) 2)
ISO/IEC 7498-1 - Information technology - Open Systems EN ISO/IEC 7498-1 1995
Interconnection - Basic Reference Model:
The Basic Model


1)
ISO/IEC 8824-2 - Information technology - Abstract Syntax - -
Notation One (ASN.1): Information object
specification


1)
ISO/IEC 8859-1 - Information technology - 8-bit single-byte - -
coded graphic character sets -
Part 1: Latin alphabet No.1


1)
ISO/IEC 9545 - Information technology - Open Systems - -
Interconnection - Application Layer structure




1)
Undated reference.
2)
Valid edition at date of issue.

---------------------- Page: 4 ----------------------

IEC 61158-6-20
Edition 1.0 2007-12
INTERNATIONAL
STANDARD

Industrial communication networks – Fieldbus specifications –
Part 6-20: Application layer protocol specification – Type 20 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XA
ICS 35.100.70; 25.040.40 ISBN 2-8318-9500-6

---------------------- Page: 5 ----------------------

– 2 – 61158-6-20 © IEC:2007(E)
CONTENTS
FOREWORD.5
INTRODUCTION.7
1 Scope.8
1.1 General .8
1.2 Specifications .8
1.3 Conformance.8
2 Normative references .9
3 Terms, definitions, symbols, abbreviations and conventions .10
3.1 Terms and definitions from other ISO/IEC standards .10
3.2 IEC/TR 61158-1 terms.10
3.3 Type 20 fieldbus application-layer specific definitions.13
3.4 Abbreviations and symbols .15
3.5 Conventions .16
3.6 Conventions used in state machines.16
4 Abstract syntax.17
5 Transfer syntax.17
5.1 General .17
5.2 Common APDU structure.18
5.3 Service-specific APDU structures .20
5.4 Data coding rules .35
6 Structure of FAL protocol state machines .40
7 AP-context state machines .41
8 FAL service protocol machine (FSPM) .41
8.1 General .41
8.2 FSPM state tables .42
8.3 Functions used by FSPM.47
8.4 Parameters of FSPM/ARPM primitives.47
9 Application relationship protocol machines (ARPMs) .48
9.1 AREP mapping to data link layer .48
9.2 Application relationship protocol machines (ARPMs) .49
9.3 AREP state machine primitive definitions.51
9.4 AREP state machine functions.51
10 DLL mapping protocol machine (DMPM) .51
10.1 DMPM states.51
10.2 DMPM state machines.52
10.3 Primitives exchanged between data link layer and DMPM.52
10.4 Functions used by DMPM .53
Bibliography.54

Figure 1 – APDU format.18
Figure 2 – Normal response from slave to master .18
Figure 3 – Command error response from slave to master .19
Figure 4 – Communication error response from slave to master .20
Figure 5 – Coding without identification.35
Figure 6 – Coding of Integer type data .35

---------------------- Page: 6 ----------------------

61158-6-20 © IEC:2007(E) – 3 –
Figure 7 – Coding of Integer16 type data .36
Figure 8 – Coding of Unsigned type data .36
Figure 9 – Coding of Unsigned16 type data.36
Figure 10 – Coding of single precision Floating Point type data .36
Figure 11 – Coding of double precision Floating Point type data .37
Figure 12 – Coding of Date type data.37
Figure 13 – Relationships among protocol machines and adjacent layers .41
Figure 14 – State transition diagram of FSPM .42
Figure 15 – State transition diagram of the client ARPM .49
Figure 16 – State transition diagram of the server ARPM .50
Figure 17 – State transition diagram of DMPM .52

Table 1 – Conventions used for state machines .16
Table 2 – Response code values .19
Table 3 – Device status values .19
Table 4 – Response code values .20
Table 5 – Communication error codes.20
Table 6 – Identify request APDU .21
Table 7 – Identify response value field .22
Table 8 – Identify command specific response codes.22
Table 9 – Read primary variable response value field .23
Table 10 – Read primary variable command specific response codes .23
Table 11 – Read loop current and percent of range value field.23
Table 12 – Read loop current and percent of range command specific response codes .24
Table 13 – Read dynamic variables and loop current value field .24
Table 14 – Read dynamic variables and loop current command specific response
codes.24
Table 15 – Write polling address value field .25
Table 16 – Loop current mode codes .25
Table 17 – Write polling address command specific response codes.25
Table 18 – Read loop configuration value field.26
Table 19 – Read loop configuration command specific response codes .26
Table 20 – Read dynamic variable families classifications value field.26
Table 21 – Read dynamic variable families classifications command specific response
codes.27
Table 22 – Read device variables with status request value field .27
Table 23 – Read device variables with status command specific response codes.27
Table 24 – Read device variables with status value field.28
Table 25 – Variable status values .28
Table 26 – Read message response value field .29
Table 27 – Read message command specific response codes .29
Table 28 – Read tag, descriptor, date response value field .30
Table 29 – Read tag, descriptor, date command specific response codes .30
Table 30 – Read primary variable transducer information response value field.30

---------------------- Page: 7 ----------------------

– 4 – 61158-6-20 © IEC:2007(E)
Table 31 – Read primary variable transducer information command specific response
codes.31
Table 32 – Read device information response value field.31
Table 33 – Read device information command specific response codes.32
Table 34 – Read final assembly number response value field .32
Table 35 – Read final assembly number command specific response codes .32
Table 36 – Write message value field.32
Table 37 – Write message command specific response codes .33
Table 38 – Write tag, descriptor, date value field .33
Table 39 – Write tag, descriptor, date command specific response codes .33
Table 40 – Write final assembly number value field.34
Table 41 – Write final assembly number command specific response codes .34
Table 42 – Read long tag response value field.34
Table 43 – Read long tag command-specific response codes .34
Table 44 – Write long tag value field .35
Table 45 – Write long tag command specific Response codes .35
Table 46 – Coding for Date type .37
Table 47 – Coding for one octet Enumerated Type.38
Table 48 – One octet bit field .39
Table 49 – Packed ASCII character set.39
Table 50 – Acceptable subset of ISO Latin-1 characters .40
Table 51 – FSPM state table – client transactions.42
Table 52 – FSPM state table – server transactions .46
Table 53 – Function Command () .47
Table 54 – Function CommErr () .47
Table 55 – Function CommandErr () .47
Table 56 – Function Resp ().47
Table 57 – Function Device () .47
Table 58 – Parameters used with primitives exchanged between FSPM and ARPM .47
Table 59 – Client ARPM states .49
Table 60 – Client ARPM state table .50
Table 61 – Server ARPM states .50
Table 62 – Server ARPM state table .50
Table 63 – Primitives issued from ARPM to DMPM .51
Table 64 – Primitives issued by DMPM to ARPM.51
Table 65 – Parameters used with primitives exchanged between ARPM and DMPM .51
Table 66 – DMPM state descriptions .52
Table 67 – DMPM state table – Client transactions .52
Table 68 – DMPM state table – Server transactions .52
Table 69 – Primitives exchanged between data-link layer and DMPM .53

---------------------- Page: 8 ----------------------

61158-6-20 © IEC:2007(E) – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –

Part 6-20: Application layer protocol specification – Type 20 elements


FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
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 IEC 61784 series. Use of the various protocol types in other
combinations may require permission from their respective intellectual-property-right holders.
International Standard IEC 61158-6-20 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This first edition and its companion parts of the IEC 61158-6 subseries cancel and replace
IEC 61158-6:2003. This edition of this part constitutes a technical addition.
This edition of IEC 61158-6 includes the following significant changes from the previous
edition:
a) deletion of the former Type 6 fieldbus for lack of market relevance;
b) addition of new types of fieldbuses;
c) partition of part 6 of the third edition into multiple parts numbered -6-2, -6-3, …

---------------------- Page: 9 ----------------------

– 6 – 61158-6-20 © IEC:2007(E)
The text of this standard is based on the following documents:
FDIS Report on voting
65C/476/FDIS 65C/487/RVD

Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under http://webstore.iec.ch in the
data related to the specific publication. At this date, the publication will be:
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
NOTE  The revision of this standard will be synchronized with the other parts of the IEC 61158 series.
The list of all the parts of the IEC 61158 series, under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.

---------------------- Page: 10 ----------------------

61158-6-20 © IEC:2007(E) – 7 –
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 provides 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 time 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 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
positioned within the OSI or fieldbus reference models, otherwise incompatible systems may
work together in any combination.

---------------------- Page: 11 ----------------------

– 8 – 61158-6-20 © IEC:2007(E)
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –

Part 6-20: Application layer protocol specification – Type 20 elements


1 Scope
1.1 General
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
...