IEC 61158-6-3:2007
(Main)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
It 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. It includes the following significant changes from the previous edition deletion of the former Type 6 fieldbus for lack of market relevance; addition of new types of fieldbuses; partition of part 6 of the third edition into multiple parts numbered.
General Information
Relations
Standards Content (Sample)
IEC 61158-6-3
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-3: Application layer protocol specification – Type 3 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: inmail@iec.ch
Web: www.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: www.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: www.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: www.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: www.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: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-6-3
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-3: Application layer protocol specification – Type 3 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XH
ICS 35.100.70; 25.040.40 ISBN 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
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.