IEC 61158-6-14:2010
(Main)Industrial communication networks - Fieldbus specifications - Part 6-14: Application layer protocol specification - Type 14 elements
Industrial communication networks - Fieldbus specifications - Part 6-14: Application layer protocol specification - Type 14 elements
IEC 61158-6-14:2010(E) specifies the protocol of the Type 14 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). It defines the protocol provided to define the wire-representation of the service primitives defined in IEC 61158-5-14:2010, and the externally visible behavior associated with their transfer. This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main changes with respect to the previous edition are:
- update the Normative references and Bibliography;
- corrections of editorial errors;
- specification changes for CPF3;
- update of the requirements for all conformance classes;
- update of the requirements for all conformance services.
General Information
Relations
Standards Content (Sample)
IEC 61158-6-14 ®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-14: Application layer protocol specification – Type 14 elements
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.
IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: 0Hinmail@iec.ch
Web: 1Hwww.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: 2Hwww.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: 3Hwww.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: 4Hwww.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: 5Hwww.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: 6Hcsc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-6-14 ®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-14: Application layer protocol specification – Type 14 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XC
ICS 25.04.40; 35.100.70; 35.110 ISBN 978-2-88912-130-4
– 2 – 61158-6-14 © IEC:2010(E)
CONTENTS
FOREWORD.1H7
INTRODUCTION.2H9
1 Scope.3H10
1.1 General .4H10
1.2 Specifications.5H10
1.3 Conformance.6H11
2 Normative references .7H11
3 Terms, definitions, symbols, abbreviations and conventions .8H11
3.1 Referenced terms and definitions .9H11
3.2 Fieldbus application layer specific terms and definitions.10H13
3.3 Abbreviations and symbols.11H16
3.4 Conventions .12H17
4 Abstract syntax.13H18
4.1 Fixed format PDU description .14H18
4.2 Object definitions in FAL management ASE.15H26
4.3 Definition of objects used in Type 14 application access entity .16H33
5 Transfer syntax .17H36
5.1 Encodingof basic data types.18H36
5.2 Encoding of Type 14 APDU header .19H43
5.3 Encoding of FAL management entity service parameters.20H43
5.4 Encoding of AAE Services.21H49
6 Structure of FAL protocol state machines .22H55
7 AP-Context state machine .23H56
7.1 Primitives exchanged between ALU and ALE .24H56
7.2 Protocol state machine descriptions .25H56
7.3 State transitions .26H57
7.4 Function descriptions .27H63
8 FAL management state machines.28H63
8.1 Primitives .29H63
8.2 Protocol state machine descriptions .30H65
8.3 State transitions .31H65
8.4 Function descriptions .32H67
9 Application access entity protocol machine.33H71
9.1 Primitives .34H71
9.2 AAE state machine .35H73
9.3 Event ASE protocol machine .36H76
9.4 Domain ASE protocol machine .37H77
10 Application relationship state machine.38H81
10.1 Primitives .39H81
10.2 AREP state description.40H82
10.3 State transitions .41H83
10.4 Function descriptions .42H84
11 DLL mapping protocol machine .43H84
11.1 Concept .44H84
11.2 Primitives .45H84
61158-6-14 © IEC:2010(E) – 3 –
11.3 State description .46H85
11.4 State transitions .47H85
11.5 Function description .48H86
Bibliography.49H87
Figure 1 – State transition diagram .50H17
Figure 2 – Exchanged primitives of protocol state machine .51H56
Figure 3 – ACE protocol state machine .52H57
Figure 4 – FME protocol state machine.53H65
Figure 5 – AAE state transition diagrams .54H73
Figure 6 – Event ASE state transition diagrams .55H76
Figure 7 – Domain ASE state transition diagram .56H78
Figure 8 – AREP state transition diagrams.57H83
Figure 9 – ESME state transition.58H85
Table 1 – State machine description elements .59H18
Table 2 – Definition of Type 14 MOB header object .60H26
Table 3 – Definition of Type 14 device descriptor object .61H26
Table 4 – Definition of the time synchronization object.62H27
Table 5 – Definition of maximum response time object.63H28
Table 6 – Definition of the Type 14 communication scheduling management object .64H28
Table 7 – Definition of the device application information object .65H28
Table 8 – Definition of FB application information header.66H29
Table 9 – Definition of domain application information header.67H29
Table 10 – Definition of Type 14 link object header.68H30
Table 11 – Definition of Type 14 FRT link object header .69H30
Table 12 – Definition of FB application information object .70H31
Table 13 – Definition of Type 14 link object .71H31
Table 14 – Definition of Type 14 FRT link object.72H32
Table 15 – Definition of domain application information object .73H33
Table 16 – Definition of domain object .74H33
Table 17 – Definition of simple variable object .75H34
Table 18 – Definition of event object .76H34
Table 19 – Definition of Type 14 socket mapping object.77H35
Table 20 – Definition of Type 14 socket timer object .78H35
Table 21 – Definition of ErrorType object .79H36
Table 22 – Encoding of Boolean value TRUE.80H36
Table 23 – Encoding of Boolean value FALSE .81H36
Table 24 – Encoding of Unsigned8 data type .82H37
Table 25 – Encoding of Unsigned16 data type .83H37
Table 26 – Encoding of Unsigned32 data type .84H37
Table 27 – Encoding of Unsigned64 data type .85H38
Table 28 – Encoding of Int8 data type.86H38
– 4 – 61158-6-14 © IEC:2010(E)
Table 29 – Encoding of Int16 data type.87H38
Table 30 – Encoding of Int32 data type.88H39
Table 31 – Encoding of Int64 data type.89H39
Table 32 – Encoding of Real type .90H39
Table 33 – Encoding of VisibleString data type .91H40
Table 34 – Encoding of OctetString data type .92H40
Table 35 – Encoding of BitString data type .93H40
Table 36 – Encoding of TimeOfDay data type .94H41
Table 37 – Encoding of BinaryDate data type .95H42
Table 38 – Encoding of PrecisionTimeDifferen
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.