IEC PAS 62411:2005
(Main)Real-time Ethernet PROFINET IO
Real-time Ethernet PROFINET IO
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."with the structure and services of the IEC fieldbus Application Layer. It is specified in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545).
General Information
Relations
Standards Content (Sample)
PUBLICLY
IEC
AVAILABLE
PAS 62411
SPECIFICATION
First edition
2005-06
Real-time Ethernet PROFINET IO
Reference number
IEC/PAS 62411:2005(E)
Publication numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series. For example, IEC 34-1 is now referred to as IEC 60034-1.
Consolidated editions
The IEC is now publishing consolidated versions of its publications. For example,
edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the
base publication incorporating amendment 1 and the base publication incorporating
amendments 1 and 2.
Further information on IEC publications
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology. Information relating to
this publication, including its validity, is available in the IEC Catalogue of
publications (see below) in addition to new editions, amendments and corrigenda.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is also available from the following:
• IEC Web Site (www.iec.ch)
• Catalogue of IEC publications
The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to
search by a variety of criteria including text searches, technical committees
and date of publication. On-line information is also available on recently issued
publications, withdrawn and replaced publications, as well as corrigenda.
• IEC Just Published
This summary of recently issued publications (www.iec.ch/online_news/ justpub)
is also available by email. Please contact the Customer Service Centre (see
below) for further information.
• Customer Service Centre
If you have any questions regarding this publication or need further assistance,
please contact the Customer Service Centre:
Email: custserv@iec.ch
Tel: +41 22 919 02 11
Fax: +41 22 919 03 00
PUBLICLY
IEC
AVAILABLE
PAS 62411
SPECIFICATION
First edition
2005-06
Real-time Ethernet PROFINET IO
© IEC 2005 – Copyright - all rights reserved
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 the publisher.
International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland
Telephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale
XH
International Electrotechnical Commission
Международная Электротехническая Комиссия
For price, see current catalogue
– 2 – PAS 62411 © IEC:2005 (E)
CONTENTS
FOREWORD.16
INTRODUCTION.18
1 Scope .19
2 Normative references .20
3 Terms and definitions.21
3.1 Summary.21
3.2 Terms and definitions from other ISO/IEC standards .21
3.3 Terms and definitions from IEC 61158-5.22
3.4 ISO/IEC 8802-3 and IEEE 802.1Q terms .22
3.5 IEC 61588 terms.22
3.6 ISO/IEC 7498-1 terms.23
3.7 ISO/IEC 8822 terms.23
3.8 ISO/IEC 9545 terms.23
3.9 ISO/IEC 8824 terms.23
3.10 ISO/IEC 8802-3 and IEEE 802.1Q terms .23
3.11 Fieldbus Application Layer specific definitions .23
3.12 Abbreviations and symbols .31
3.13 Conventions for Part 5 of IEC 61158 .33
3.14 Conventions for Part 6 of IEC 61158 .36
3.15 Conventions used in state machines .39
4 Part 5: Application Layer Service definition of Type 10 for decentralized periphery .42
4.1 Concepts.42
4.2 Data type ASE.42
4.3 Communication model specification .52
4.4 DCP service specification .269
5 Part 6: Application Layer protocol specification of Type 10 for decentralized
periphery .277
5.1 FAL syntax description.277
5.2 Transfer syntax.286
5.3 FAL protocol state machines.353
5.4 AP-Context state machine.359
5.5 FAL Service Protocol Machines (FSPMs) .359
5.6 Application Relationship Protocol Machines (ARPMs) .409
5.7 RPC .510
5.8 DLL Mapping Protocol Machines (DMPMs) .511
5.9 Parameters for an IO Device.593
5.10 DCP protocol .593
Annex A (informative) Device Instances .620
BIBLIOGRAPHY .622
PAS 62411 © IEC:2005 (E) – 3 –
Figures
Figure 1 — Common structure of specific fields .37
Figure 2 — Common structure of specific fields for Octet 1 (High).38
Figure 3 — Common structure of specific fields for Octet 2 (Low) .38
Figure 4 — Common structure of specific fields for Octet 1 (High).38
Figure 5 — Common structure of specific fields for Octet 2 .39
Figure 6 — Common structure of specific fields for Octet 3 .39
Figure 7 — Common structure of specific fields for Octet 4 (Low) .39
Figure 8 — Data type class hierarchy .42
Figure 9 — Example of communication between controlling devices and field devices .54
Figure 10 — Example of communication between an engineering station and several
controlling and field devices.54
Figure 11 — Example of communication between field devices and a server station .55
Figure 12 — Example of communication between field devices .55
Figure 13 — Structural units of one arbitrary API of an IO device (General) .57
Figure 14 — Example 1 structural units for interfaces and ports within API 0.58
Figure 15 — Example 2 structural units for interfaces and ports within API 0.59
Figure 16 — Overview of application processes.61
Figure 17 — IO device with APs, slots and subslots.61
Figure 18 — Application Process with application objects (APOs) .64
Figure 19 — Access to a remote APO .65
Figure 20 — Access to a remote APO for provider/consumer association .66
Figure 21 — Example of one AR with two AREPs .67
Figure 22 — Relation of a record data object to one real object .69
Figure 23 — Relation of a record data object to two real objects .69
Figure 24 — Overview IO ASE service interactions.75
Figure 25 — Example of a resource model at the alarm source .130
Figure 26 — General isochronous application model (example) .157
Figure 27 — ASE relations in an IO device operating in isochronous mode .162
Figure 28 — State machine relations in an IO device operating in isochronous mode .163
Figure 29 — SyncCtl state diagram .166
Figure 30 — OUTPUT state diagram .168
Figure 31 — INPUT state diagram.172
Figure 32 — Assignment of communication relationship to application relationship.227
Figure 33 — Implicit application relationship.230
Figure 34 — Example IO application relationship (one-to-one) .232
Figure 35 — Example IO application relationship one-to-many.233
Figure 36 — Overview ASE state machines for IO device .246
Figure 37 — State diagram application startup IO device .247
Figure 38 — State diagram for a submodule.254
Figure 39 — State diagram client during startup .264
Figure 40 — Example of RT Class 1 behavior at the local interface.268
Figure 41 — Example of RT Class 1 behavior at the local interface.268
Figure 42 — Example of dropping RT Class 1 frames because of local overload .269
– 4 – PAS 62411 © IEC:2005 (E)
Figure 43 — Example of network topology including slower wireless segments .269
Figure 44 — Sequence diagram for DCP (example) .270
Figure 45 — Coding of the data type BinaryDate .287
Figure 46 — Encoding of Time Of Day value .288
Figure 47 — Encoding of Time Difference value .288
Figure 48 — Encoding of Network Time value .288
Figure 49 — Encoding of Network Time Difference value.289
Figure 50 — Relationship among Protocol Machines .353
Figure 51 — Structuring of the protocol machines and adjacent layers in a IO
controller .356
Figure 52 — Structuring of the protocol machines and adjacent layers in a IO device .357
Figure 53 — Structuring of the protocol machines within the DMPM (single port).511
Figure 54 — Structuring of the protocol machines within the DMPM (bridge) .512
Figure 55 — Line delay measurement .513
Figure 56 — Synchronization and line delay measurement.514
Figure 57 — Delay accumulation.517
Figure 58 — Worst case Time deviation of Synchronization .517
Figure 59 — Structure of a Time Frame.518
Figure 60 — Hardware Arrangement for Processing Sync PDU .519
Figure 61 — Start up sequence.520
Figure 62 — Green and Red intervals and interval transitions .557
Figure 63 — Possible Time Inaccuracies .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.