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
- Status
- Replaced
- Publication Date
- 26-Jun-2005
- Technical Committee
- SC 65C - Industrial networks
- Drafting Committee
- WG 9 - TC 65/SC 65C/WG 9
- Current Stage
- DELPUB - Deleted Publication
- Start Date
- 14-Dec-2007
- Completion Date
- 14-Feb-2026
Relations
- Effective Date
- 05-Sep-2023
- Effective Date
- 05-Sep-2023
Get Certified
Connect with accredited certification bodies for this standard

BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
National Aerospace and Defense Contractors Accreditation Program (NADCAP)
Global cooperative program for special process quality in aerospace.
CARES (UK Certification Authority for Reinforcing Steels)
UK certification for reinforcing steels and construction.
Sponsored listings
Frequently Asked Questions
IEC PAS 62411:2005 is a technical specification published by the International Electrotechnical Commission (IEC). Its full title is "Real-time Ethernet PROFINET IO". This standard covers: 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).
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).
IEC PAS 62411:2005 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control; 35.100.05 - Multilayer applications; 35.240.50 - IT applications in industry. The ICS classification helps identify the subject area and facilitates finding related standards.
IEC PAS 62411:2005 has the following relationships with other standards: It is inter standard links to IEC 61158-6-10:2007, IEC 61158-5-10:2007. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
IEC PAS 62411:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
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 .560
Figure 64 — Using Medium Redundancy .561
Figure 65 — Locating the Destination for redundant RT Frames.561
Figure A.1 — Instance model of PROFINET IO.620
PAS 62411 © IEC:2005 (E) – 5 –
Tables
Table 1 — State machine description elements .40
Table 2 — Description of state machine elements.40
Table 3 — Conventions used in state machines.40
Table 4 — PROFINET IO UUID .51
Table 5 — Requirements and features of PROFINET IO .53
Table 6 — Read.71
Table 7 — Write.73
Table 8 — Set Input.82
Table 9 — Set Input IOCS.83
Table 10 — Get Input.84
Table 11 — Get Input IOCS .85
Table 12 — New Input .86
Table 13 — Set Input APDU Data Status .86
Table 14 — New Input APDU Data Status .87
Table 15 — Read Input Data .89
Table 16 — Set Output .91
Table 17 — Set Output IOCS .92
Table 18 — Get Output .93
Table 19 — Get Output IOCS.94
Table 20 — New Output.94
Table 21 — Set Output APDU Data Status .95
Table 22 — New Output APDU Data Status.96
Table 23 — Read Output Data .97
Table 24 — Write Output Substitute Data .100
Table 25 — Read Logbook.103
Table 26 — Logbook Event .105
Table 27 — Ext Channel Error Type .109
Table 28 — Read Device Diagnosis .111
Table 29 — Diagnosis Event .114
Table 30 — Alarm Type .119
Table 31 — Channel Diagnosis .120
Table 32 — Manufacturer Specific Diagnosis.120
Table 33 — Submodule Diagnosis State.121
Table 34 — AR Diagnosis State .121
Table 35 — User Structure Identifier .121
Table 36 — Alarm Notification.125
Table 37 — Alarm Ack .128
Table 38 — Module State.133
Table 39 — Usage with respect to CR Type.135
Table 40 — Detail .135
Table 41 — ARInfo .136
Table 42 — Ident Info .136
Table 43 — Connect .137
– 6 – PAS 62411 © IEC:2005 (E)
Table 44 — Release .143
Table 45 — Abort.144
Table 46 — End Of Parameter .144
Table 47 — Application Ready .145
Table 48 — Read Expected Identification .147
Table 49 — Read Real Identification .149
Table 50 — Read Identification Difference.152
Table 51 — Write IsoM Data .158
Table 52 — Read IsoM Data .160
Table 53 — SYNCH Event .162
Table 54 — Primitives issued by the AL to the SyncCtl state machine .164
Table 55 — Primitives issued by the user to the SyncCtl state machine .164
Table 56 — Primitives issued by the user to the input state machine.164
Table 57 — Primitives issued by the user to the output state machine.164
Table 58 — Primitives issued by the SyncCtl to the output state machine.165
Table 59 — Primitives issued by the output to the SyncCtl state machine.165
Table 60 — Primitives issued by the SyncCtl to the input state machine.165
Table 61 — Primitives issued by the output to the input state machine.165
Table 62 — Primitives issued by the output state machine to the AL .165
Table 63 — Primitives issued by the AL to the output state machine .165
Table 64 — Primitives issued by the input state machine to the AL .166
Table 65 — Primitives issued by the AL to the input state machine .166
Table 66 — SyncCtl state table .167
Table 67 — OUTPUT state table .169
Table 68 — INPUT state table.172
Table 69 — Subslot Number for Interface Submodules .180
Table 70 — Subslot Number for Port Submodules .180
Table 71 — System Capabilities.182
Table 72 — Auto Negotiation Support And Status .183
Table 73 — MDI Power Support .183
Table 74 — Link Aggregation Status .184
Table 75 — Multiple Peers .184
Table 76 — Subslot Number for Interface Submodules .186
Table 77 — Frame IDs for RT Class 3 .187
Table 78 — Sync Frame .187
Table 79 —FrameSendOffset .187
Table 80 — Tx Port Entry.188
Table 81 — Subslot Number for Sync Interface Submodules.189
Table 82 — Sync Properties Role.190
Table 83 — Sync Class.190
Table 84 — Write Expected Port Data .191
Table 85 — Write Adjusted Port Data .193
Table 86 — Read Real Port Data .195
Table 87 — Read Expected Port Data .198
PAS 62411 © IEC:2005 (E) – 7 –
Table 88 — Read Adjusted Port Data .200
Table 89 — Write IR Data .202
Table 90 — Read IR Data .205
Table 91 — Write Sync Data .208
Table 92 — Read Real Sync Data .210
Table 93 — Read Expected Sync Data .213
Table 94 — Read PDev Data .215
Table 95 — Sync State Info .220
Table 96 — CS status .222
Table 97 — Summertime.223
Table 98 — Synchronization Active .224
Table 99 — Announcement hour .224
Table 100 — Accuracy.224
Table 101 — Set time .225
Table 102 — Sync interval violation.226
Table 103 — MProvider Data Status.238
Table 104 — Frame ID.239
Table 105 — Read AR Data .243
Table 106 — State table application startup IO device (RT class 1 and 2) .248
Table 107 — State table for a submodule .255
Table 108 — State table client during startup .265
Table 109 — Device Conformance .266
Table 110 — Device Conformance Version 2.267
Table 111 — Timeout values for name resolution .267
Table 112 — DCP Get .271
Table 113 — Option.271
Table 114 — Suboptions for IP option .271
Table 115 — Suboptions for control option .272
Table 116 — Suboptions for DeviceProperties options.272
Table 117 — Suboption for DHCP .272
Table 118 — DCP Set.273
Table 119 — DCP Identify.274
Table 120 — DCP Identify Q .276
Table 121 — DLPDU syntax.277
Table 122 — APDU syntax.277
Table 123 — Substitutions .278
Table 124 — LT .289
Table 125 — TagControlInformation.Priority .290
Table 126 — FrameID.290
Table 127 — FrameID for PTP sync .291
Table 128 — FrameID for PTP delay request.291
Table 129 — FrameID for PTP additional delay request .291
Table 130 — FrameID for PTP additional delay response .291
Table 131 — FrameID for PTP sync for RT class 3 .291
– 8 – PAS 62411 © IEC:2005 (E)
Table 132 — FrameID for PTP follow up.292
Table 133 — FrameID for PTP delay response .292
Table 134 — FrameID for PTP additional delay followup request .292
Table 135 — PTP_RTAFlags.LocalReceiveExtensions .293
Table 136 — PTP_RTAFlags.RemoteSendExtensions .293
Table 137 — PTP_RTAFlags.DelayExtensions .293
Table 138 — PTP_RTAFlags.FollowUp .293
Table 139 — PTP_RTAFlags.DelayMeasure.293
Table 140 — PTP TypeLength.Type .294
Table 141 — PTP_SubType .294
Table 142 — IOxS.Extension .295
Table 143 — IOCS.Instance.295
Table 144 — IOxS.DataState .295
Table 145 — CycleCounter Difference.296
Table 146 — DataStatus.State .296
Table 147 — DataStatus.DataValid .296
Table 148 — DataStatus.ProviderState .296
Table 149 — DataStatus.StationProblemIndicator.296
Table 150 — The bits in the TransferStatus in a RT frame (RT class 3).297
Table 151 — AlarmType .299
Table 152 — AlarmSpecifier.ChannelDiagnosis .299
Table 153 — AlarmSpecifier.ManufacturerSpecificDiagnosis.300
Table 154 — AlarmSpecifier.SubmoduleDiagnosisState.300
Table 155 — AlarmSpecifier.ARDiagnosisState .300
Table 156 — RPCPacketType .301
Table 157 — RPCFlags .301
Table 158 — RPCFlags2.301
Table 159 — RPCDRep.Character- and IntegerEncoding.302
Table 160 — RPCDRep Octet 2 – Floating Point Representation .302
Table 161 — RPCObjectUUID.Data4.302
Table 162 — RPCObjectUUID – defined values.303
Table 163 — RPCInterfaceUUID – defined values .303
Table 164 — RPCOperationNmb (IO device, controller and supervisor).304
Table 165 — RPCOperationNmb for endpoint mapper .304
Table 166 — RPCDataRepresentationUUID – defined values .305
Table 167 — BlockType .306
Table 168 — SlotNumber .308
Table 169 — SubslotNumber.308
Table 170 — Index (user specific) .308
Table 171 — Index (subslot specific).309
Table 172 — Index (slot specific) .309
Table 173 — Index (AR specific) .310
Table 174 — Index (API specific) .310
Table 175 — Index (device specific).311
PAS 62411 © IEC:2005 (E) – 9 –
Table 176 — UDP_SrcPort.311
Table 177 — UDP_DstPort.312
Table 178 — IP_DstIPAddress .312
Table 179 — RPCInquiryType .313
Table 180 — RPCEPMapStatus .314
Table 181 — ARType.315
Table 182 — IOCRMulticastMACAdd.316
Table 183 — PTP sync multicast address.316
Table 184 — PTP follow up multicast address .316
Table 185 — PROFINET OUI .316
Table 186 — ARProperties.State.317
Table 187 — ARProperties.SupervisorTakeoverAllowed .317
Table 188 — ARProperties. ParametrizationServer.317
Table 189 — ARProperties.DataRate .317
Table 190 — ARProperties.DeviceAccess .318
Table 191 — IOCRProperties.RTClass .318
Table 192 — IOCRProperties. MProviderDataStatus.318
Table 193 — IOCRTagHeader.IOCRVLANID .319
Table 194 — IOCRTagHeader.IOUserPriority .319
Table 195 — IOCRType .319
Table 196 — CMInitiatorActivityTimeoutFactor .319
Table 197 — LengthIOCS .321
Table 198 — LengthIOPS .321
Table 199 — AlarmCRProperties.Priority.322
Table 200 — AlarmCRProperties.Transport .322
Table 201 — AlarmCRTagHeaderHigh.AlarmCRVLANID.322
Table 202 — AlarmCRTagHeaderHigh.AlarmUserPriority.322
Table 203 — AlarmCRTagHeaderLow.AlarmCRVLANID .323
Table 204 — AlarmCRTagHeaderLow.AlarmUserPriority .323
Table 205 — AlarmSequenceNumber.323
Table 206 — AlarmCRType.323
Table 207 — RTATimeoutFactor .324
Table 208 — AddressResolutionProperties.Protocol .324
Table 209 — AddressResolutionProperties.Factor .324
Table 210 — ModuleIdentNumber .325
Table 211 — SubmoduleIdentNumber .325
Table 212 — ControlCommand.PrmEnd .327
Table 213 — ControlCommand.ApplicationReady .327
Table 214 — ControlCommand.Release .327
Table 215 — ControlCommand.Done .327
Table 216 — DataDescription.Type .327
Table 217 — Values of ReductionRatio .328
Table 218 — Values of Phase .329
Table 219 — Values of Sequence .329
– 10 – PAS 62411 © IEC:2005 (E)
Table 220 — DataHoldFactor .330
Table 221 — WatchdogFactor .330
Table 222 — Values of FrameSendOffset.330
Table 223 — Values of ErrorCode for negative responses .331
Table 224 — Values of ErrorDecode .331
Table 225 — Coding of ErrorCode1 with ErrorDecode PNIORW.331
Table 226 — Values of ErrorCode1 and ErrorCode2 for ErrorDecode with the value
PNIO .332
Table 227 — Values of ErrorCode2 for ErrorCode1=RPC.334
Table 228 — ModuleState.334
Table 229 — SubmoduleState.AddInfo .335
Table 230 — SubmoduleState.DiagInfo .335
Table 231 — SubmoduleState.ARInfo .335
Table 232 — SubmoduleState.IdentInfo .335
Table 233 — SubmoduleState.FormatIndicator .335
Table 234 — SubmoduleState.Detail .336
Table 235 — SubmoduleState.FormatIndicator .336
Table 236 — SubmoduleProperties.Type.336
Table 237 — SubmoduleProperties.SharedInput.337
Table 238 — SubmoduleProperties.ReduceInputSubmoduleDataLength .337
Table 239 — SubmoduleProperties.ReduceOutputSubmoduleDataLength.337
Table 240 — SubstitutionMode.337
Table 241 — SubstituteActiveFlag.338
Table 242 — IM_Hardware_Revision.338
Table 243 — IM_SWRevision_Functional_Enhancement.338
Table 244 —
...




Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...