EN 62453-302:2017
(Main)Field device tool (FDT) interface specification - Part 302: Communication profile integration - IEC 61784 CPF 2
Field device tool (FDT) interface specification - Part 302: Communication profile integration - IEC 61784 CPF 2
IEC 62453-302:2016 provides information for integrating the CIP technology into the FDT interface specification (IEC 62453-2). It specifies communication and other services. This second edition cancels and replaces the first edition published in 2009. This edition constitutes a technical revision. The main changes are provided in order to provide improved support for Ethernet IP (see Clauses 9, 10, and 12), additional implementation hints (see Annex A) and to support introduction of the technology according to IEC TR 62453-42. This publication is to be read in conjunction with IEC 62453-2:2009.
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 302: Integration von Kommunikationsprofilen - Kommunikationsprofilfamilie (CPF) 2 nach IEC 61784
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 302: Intégration des profils de communication - CPF 2 de l’IEC 61784
L'IEC 62453-302:2016 fournit des informations sur l'intégration de la technologie CIP dans la spécification des interfaces des outils des dispositifs de terrain (FDT) (IEC 62453-2). Elle spécifie les services de communication et autres services. Cette deuxième édition annule et remplace la première édition parue en 2009. Cette édition constitue une révision technique. Les principales modifications sont apportées afin de fournir une prise en charge améliorée de l'Ethernet IP (voir Articles 9, 10 et 12), des indications de mise en oeuvre supplémentaires (voir Annexe A) et venir à l'appui de l'introduction de la technologie conformément à l'IEC TR 62453-42. Cette publication doit être lue conjointement avec la IEC 62453-2:2009.
Specifikacija vmesnika orodja procesne naprave - 302. del: Integracija komunikacijskih profilov - IEC 61784 CPF 2 (IEC 62453-302:2016)
Družina komunikacijskega profila 2 (znana kot CIP™2) določa komunikacijske profile, ki temeljijo na standardih IEC 61158-2, tip 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2 in IEC 62026-3. Osnovni profili CP 2/1 (ControlNet™3), CP 2/2 (EtherNet/IP™4) in CP 2/3 (DeviceNet™2) so določeni v standardih IEC 61784-1 in IEC 61784-2. Dodatni komunikacijski profil (CompoNet™2), ki tudi temelji na CIP™, je določen v [15].
Ta del standarda IEC 62453 podaja informacije za integracijo tehnologije CIP™ v specifikacijo vmesnika orodja procesne naprave (FTD) (IEC 62453-2).
Ta del standarda IEC 62453 določa komunikacijske in druge storitve.
Ta specifikacija niti ne vsebuje specifikacije orodja procesne naprave niti je ne spreminja.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-februar-2018
1DGRPHãþD
SIST EN 62453-302:2010
Specifikacija vmesnika orodja procesne naprave - 302. del: Integracija
komunikacijskih profilov - IEC 61784 CPF 2 (IEC 62453-302:2016)
Field device tool (FDT) interface specification - Part 302: Communication profile
integration - IEC 61784 CPF 2 (IEC 62453-302:2016)
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 302: Integration von
Kommunikationsprofilen - Kommunikationsprofilfamilie (CPF) 2 nach IEC 61784 (IEC
62453-302:2016)
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 302:
Intégration des profils de communication - CPF 2 de l'IEC 61784 (IEC 62453-302:2016)
Ta slovenski standard je istoveten z: EN 62453-302:2017
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD EN 62453-302
NORME EUROPÉENNE
EUROPÄISCHE NORM
December 2017
ICS 25.040.40; 35.100.05; 35.110 Supersedes EN 62453-302:2009
English Version
Field device tool (FDT) interface specification - Part 302:
Communication profile integration - IEC 61784 CPF 2
(IEC 62453-302:2016)
Spécification des interfaces des outils des dispositifs de Field Device Tool (FDT)-Schnittstellenspezifikation - Teil
terrain (FDT) - Partie 302: Intégration des profils de 302: Integration von Kommunikationsprofilen -
communication - CPF 2 de l'IEC 61784 Kommunikationsprofilfamilie (CPF) 2 nach IEC 61784
(IEC 62453-302:2016) (IEC 62453-302:2016)
This European Standard was approved by CENELEC on 2016-07-19. 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 CEN-CENELEC
Management Centre 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 CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden,
Switzerland, Turkey and the United Kingdom.
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2017 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62453-302:2017 E
European foreword
The text of document 65E/336/CDV, future edition 1 of IEC 62453-302:2016, prepared by SC 65E
"Devices and integration in enterprise systems", of IEC/TC 65 "Industrial-process measurement,
control and automation" was submitted to the IEC-CENELEC parallel vote and approved by
CENELEC as EN 62453-302:2017.
The following dates are fixed:
• latest date by which this document has (dop) 2018-06-08
to be implemented at national level by
publication of an identical national
standard or by endorsement
• latest date by which the national (dow) 2020-12-08
standards conflicting with this
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Endorsement notice
The text of the International Standard IEC 62453-302:2016 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 61131-3:2013 NOTE Harmonized as EN 61131-3:2013
IEC 62453-1:2009 NOTE Harmonized as EN 62453-1:2009
IEC/TR 62453-41:2009 NOTE Harmonized as CLC/TR 62453-41:2009
IEC/TR 62453-502:2009 NOTE Harmonized as CLC/TR 62453-502:2009
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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 1 When an International Publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.
Publication Year Title EN/HD Year
IEC 61158-2 - Industrial communication networks - EN 61158-2 -
Fieldbus specifications - Part 2: Physical
layer specification and service definition
IEC 61158-3-2 - Industrial communication networks - EN 61158-3-2 -
Fieldbus specifications - Part 3-2: Data-link
layer service definition - Type 2 elements
IEC 61158-4-2 - Industrial communication networks - EN 61158-4-2 -
Fieldbus specifications - Part 4-2: Data-link
layer protocol specification - Type 2
elements
IEC 61158-5-2 2014 Industrial communication networks - EN 61158-5-2 2014
Fieldbus specifications -- Part 5-2:
Application layer service definition - Type 2
elements
IEC 61158-6-2 2014 Industrial communication networks - EN 61158-6-2 2014
Fieldbus specifications - Part 6-2:
Application layer protocol specification -
Type 2 elements
IEC 61784-1 - Industrial communication networks - EN 61784-1 -
Profiles -- Part 1: Fieldbus profiles
IEC 61784-2 - Industrial communication networks - EN 61784-2 -
Profiles - Part 2: Additional fieldbus profiles
for real-time networks based on ISO/IEC
8802-3
IEC 61784-3-2 2010 Industrial communication networks - EN 61784-3-2 2010
Profiles -- Part 3-2: Functional safety
fieldbuses - Additional specifications for
CPF 2
IEC 62026-3 - Low-voltage switchgear and controlgear - - -
Controller-device interfaces (CDIs) -- Part
3: DeviceNet
IEC 62453-1 - Field Device Tool (FDT) interface EN 62453-1 -
specification -- Part 1: Overwiew and
guidance
IEC 62453-2 - Field Device Tool (FDT) Interface EN 62453-2 -
Specification - Part 2: Concepts and
detailed Description
ISO 15745-2 2003 Industrial automation systems and - -
integration -- Open systems application
integration framework -- Part 2: Reference
description for ISO 11898-based control
systems
ISO 15745-3 2003 Industrial automation systems and - -
integration - Open systems application
integration framework -- Part 3: Reference
description for IEC 61158 based control
systems
IEC 62453-302 ®
Edition 2.0 2016-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field device tool (FDT) interface specification –
Part 302: Communication profile integration – IEC 61784 CPF 2
Spécification des interfaces des outils des dispositifs de terrain (FDT) –
Partie 302: Intégration des profils de communication – CPF 2 de l’IEC 61784
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-3463-1
– 2 – IEC 62453-302:2016 IEC 2016
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references. 7
3 Terms, definitions, symbols, abbreviated terms and conventions. 8
3.1 Terms and definitions . 8
3.2 Symbols and abbreviated terms . 8
3.3 Conventions . 8
3.3.1 Data type names and references to data types . 8
3.3.2 Vocabulary for requirements . 8
4 Bus category . 9
5 Access to instance and device data . 10
6 Protocol specific behavior . 10
7 Protocol specific usage of general data types . 11
8 Protocol specific common data types . 11
9 Network management data types . 15
9.1 General . 15
9.2 Node address . 15
9.3 Scanner/master – Bus parameter set (CIP) . 15
10 Communication data types . 23
11 Channel parameter data types . 25
12 Device identification . 28
12.1 Device type identification data types . 28
12.2 Topology scan data types . 29
12.3 Scan identification data types . 29
12.4 Device type identification data types . 29
Annex A (informative) Implementation hints . 32
A.1 Addressing in CompoNet DTMs . 32
A.2 Displaying addresses of CompoNet DTMs . 33
A.3 Handling of Config1 and Config2 elements in EtherNet/IP . 33
Bibliography . 34
Figure 1 – Part 302 of the IEC 62453 series . 6
Figure A.1 – Examples of DTM naming for CompoNet . 33
Table 1 – Protocol identifiers . 9
Table 2 – Physical layer identifiers for DeviceNet . 9
Table 3 – Physical layer identifiers for ControlNet . 9
Table 4 – Physical layer identifiers for Ethernet/IP . 9
Table 5 – Physical layer identifiers for CompoNet . 10
Table 6 – Data link layer identifiers . 10
Table 7 – Protocol specific usage of general data types . 11
Table 8 – Simple protocol specific common data types . 12
IEC 62453-302:2016 IEC 2016 – 3 –
Table 9 – Structured protocol specific common data types . 13
Table 10 – Simple fieldbus configuration data types . 15
Table 11 – Structured fieldbus configuration data types . 17
Table 12 – Simple communication data types . 23
Table 13 – Structured communication data types . 24
Table 14 – Simple channel parameter data types . 26
Table 15 – Structured channel parameter data types . 26
Table 16 – Identification data types with protocol specific mapping . 28
Table 17 – Simple identification data types with protocol independent semantics . 28
Table 18 – Structured identification data types with protocol independent semantics . 28
Table 19 – Simple scan identification data types . 29
Table 20 – Structured scan identification data types . 29
Table 21 – Structured device type identification data types . 30
Table A.1 – CompoNet relationship between Device Category, Node Address, MAC ID . 32
– 4 – IEC 62453-302:2016 IEC 2016
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 302: Communication profile integration –
IEC 61784 CPF 2
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 itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
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.
International Standard IEC 62453-302 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
This second edition cancels and replaces the first edition published in 2009. This edition
constitutes a technical revision. The main changes are provided in order to provide improved
support for Ethernet IP (see Clauses 9, 10, and 12), additional implementation hints (see
Annex A) and to support introduction of the technology according to IEC TR 62453-42 [5]
(see Clause 4).
Each part of the IEC 62453-3xy series is intended to be read in conjunction with IEC 62453-2.
———————
Figures in square brackets refer to the Bibliography.
IEC 62453-302:2016 IEC 2016 – 5 –
The text of this standard is based on the following documents:
CDV Report on voting
65E/336/CDV 65E/395A/RVC
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 the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 62453 series, under the general title Field Device Tool (FDT)
interface specification, can be found on the IEC website.
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.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – IEC 62453-302:2016 IEC 2016
INTRODUCTION
This part of IEC 62453 is an interface specification for developers of FDT (Field Device Tool)
components for function control and data access within a client/server architecture. The
specification is a result of an analysis and design process to develop standard interfaces to
facilitate the development of servers and clients by multiple vendors that need to interoperate
seamlessly.
With the integration of fieldbusses into control systems, there are a few other tasks which
need to be performed. In addition to fieldbus- and device-specific tools, there is a need to
integrate these tools into higher-level system-wide planning or engineering tools. In particular,
for use in extensive and heterogeneous control systems, typically in the area of the process
industry, the unambiguous definition of engineering interfaces that are easy to use for all
those involved is of great importance.
A device-specific software component, called DTM (Device Type Manager), is supplied by the
field device manufacturer with its device. The DTM is integrated into engineering tools via the
FDT interfaces defined in this specification. The approach to integration is in general open for
all kinds of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.
Figure 1 shows how IEC 62453-302 is aligned in the structure of the IEC 62453 series.
Part 302
Communication
profile integration–
IEC 61784 CPF 2
IEC
Figure 1 – Part 302 of the IEC 62453 series
IEC 62453-302:2016 IEC 2016 – 7 –
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 302: Communication profile integration –
IEC 61784 CPF 2
1 Scope
Communication Profile Family 2 (commonly known as CIP™ ) defines communication profiles
based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2,
IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNet™ ), CP 2/2
(EtherNet/IP™ ), and CP 2/3 (DeviceNet™ ) are defined in IEC 61784-1 and IEC 61784-2. An
), also based on CIP™, is defined in [15].
additional communication profile (CompoNet™
This part of IEC 62453 provides information for integrating the CIP™ technology into the FDT
interface specification (IEC 62453-2).
This part of IEC 62453 specifies communication and other services.
This specification neither contains the FDT specification nor modifies it.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 61158-2, Industrial communication networks – Fieldbus specifications – Part 2: Physical
layer specification and service definition
IEC 61158-3-2, Industrial communication networks – Fieldbus specifications – Part 3-2: Data-
link layer service definition – Type 2 elements
IEC 61158-4-2, Industrial communication networks – Fieldbus specifications – Part 4-2: Data-
link layer protocol specification – Type 2 elements
IEC 61158-5-2:2014, Industrial communication networks – Fieldbus specifications – Part 5-2:
Application layer service definition – Type 2 elements
———————
CIP™ (Common Industrial Protocol), DeviceNet™ and CompoNet™ are trade names of Open DeviceNet Vendor
Association, Inc (ODVA). This information is given for the convenience of users of this document and does not
constitute an endorsement by IEC of the trade name holder or any of its products. Compliance to this standard
does not require use of the trade names CIP™, DeviceNet™ or CompoNet™. Use of the trade names CIP™,
DeviceNet™ or CompoNet™ requires permission of Open DeviceNet Vendor Association, Inc.
ControlNet™ is a trade name of ControlNet International, Ltd. This information is given for the convenience of
users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its
products. Compliance to this profile does not require use of the trade name ControlNet™. Use of the trade
name ControlNet™ requires permission of ControlNet International, Ltd.
EtherNet/IP™ is a trade name of ControlNet International, Ltd. and Open DeviceNet Vendor Association, Inc.
This information is given for the convenience of users of this document and does not constitute an endorsement
by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the
trade name EtherNet/IP™. Use of the trade name EtherNet/IP™ requires permission of either ControlNet
International, Ltd. or Open DeviceNet Vendor Association, Inc.
– 8 – IEC 62453-302:2016 IEC 2016
IEC 61158-6-2:2014, Industrial communication networks – Fieldbus specifications – Part 6-2:
Application layer protocol specification – Type 2 elements
IEC 61784-1, Industrial communication networks – Profiles – Part 1: Fieldbus profiles
IEC 61784-2, Industrial communication networks – Profiles – Part 2: Additional fieldbus
profiles for real-time networks based on ISO/IEC 8802-3
IEC 61784-3-2:2010, Industrial communication networks – Profiles – Part 3-2: Functional
safety fieldbuses – Additional specifications for CPF 2
IEC 62026-3, Low-voltage switchgear and controlgear – Controller-device interfaces (CDIs) –
Part 3: DeviceNet
IEC 62453-1:– , Field device tool (FDT) interface specification – Part 1: Overview and
guidance
IEC 62453-2:– , Field device tool (FDT) interface specification – Part 2: Concepts and
detailed description
ISO 15745-2:2003, Industrial automation systems and integration – Open systems application
integration framework – Part 2: Reference description for ISO 11898-based control systems
ISO 15745-3:2003, Industrial automation systems and integration – Open systems application
integration framework – Part 3: Reference description for IEC 61158-based control systems
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1 and
IEC 62453-2 apply.
3.2 Symbols and abbreviated terms
For the purposes of this document, the symbols and abbreviations given in IEC 62453-1,
IEC 62453-2, as well as the following apply.
CIP™ Common Industrial Protocol
EDS Electronic Data Sheet [ISO 15745-2]
3.3 Conventions
3.3.1 Data type names and references to data types
The conventions for naming and referencing of data types are explained in IEC 62453-2:–,
Clause A.1.
3.3.2 Vocabulary for requirements
The following expressions are used when specifying requirements.
Usage of “shall” or “mandatory” No exceptions allowed.
———————
To be published concurrently with this standard.
IEC 62453-302:2016 IEC 2016 – 9 –
Usage of “should” or “recommended” Strong recommendation. It may make sense in
special exceptional cases to differ from the
described behavior.
Usage of “can’ or “optional’ Function or behavior may be provided,
depending on defined conditions.
4 Bus category
IEC 61784 CPF 2 protocol is identified in the protocolId element of the structured data type
'fdt:BusCategory' by the following unique identifiers, as specified in Table 1.
Table 1 – Protocol identifiers
Identifier value ProtocolId name Description
19B91472-EDB9-4e8c-BB61-516EEC79C1C0 ‘CIP DeviceNet’ Support for CP 2/3 (DeviceNet)
6CD80F51-019D-4e60-AEAC-B10144943B4B ‘CIP EthernetIP’ Support for CP 2/2 (EtherNet/IP)
C290CE23-62EA-478c-97F2-97EFEC602E05 ‘CIP ControlNet’ Support for CP 2/1 (ControlNet)
089BB2BC-B75A-11DB-8314-0800200C9A66 ‘CIP CompoNet’ Support for CompoNet
Table 2 shows the identifiers for physical layer that can be used for DeviceNet.
Table 2 – Physical layer identifiers for DeviceNet
Identifier value Description
23E6EFA5-B1DA-11E2-9D9C-005056C00008 Standard DeviceNet
Table 3 shows the identifiers for physical layer that can be used for ControlNet.
Table 3 – Physical layer identifiers for ControlNet
Identifier value Description
30F4EF13-B1DA-11E2-9D9C-005056C00008 ControlNet Coaxial Medium
30F4EF14-B1DA-11E2-9D9C-005056C00008 ControlNet Fiber Medium
30F4EF15-B1DA-11E2-9D9C-005056C00008 ControlNet Network Access Port (NAP)
Table 4 shows the identifiers for physical layer that can be used for Ethernet/IP.
Table 4 – Physical layer identifiers for Ethernet/IP
Identifier value Description
307dd808-c010-11db-90e7-0002b3ecdcbe 10BASET
307dd809-c010-11db-90e7-0002b3ecdcbe 10BASETXHD
307dd80a-c010-11db-90e7-0002b3ecdcbe 10BASETXFD
307dd80b-c010-11db-90e7-0002b3ecdcbe 10BASEFLHD
307dd80c-c010-11db-90e7-0002b3ecdcbe 10BASEFLFD
307dd80d-c010-11db-90e7-0002b3ecdcbe 10BASEFXHD
307dd80e-c010-11db-90e7-0002b3ecdcbe 10BASEFXFD
307dd80f-c010-11db-90e7-0002b3ecdcbe 100BASETXHD
307dd810-c010-11db-90e7-0002b3ecdcbe 100BASETXFD
– 10 – IEC 62453-302:2016 IEC 2016
Identifier value Description
307dd811-c010-11db-90e7-0002b3ecdcbe 100BASEFXHD
307dd812-c010-11db-90e7-0002b3ecdcbe 100BASEFXFD
307dd813-c010-11db-90e7-0002b3ecdcbe 100BASELX10
307dd814-c010-11db-90e7-0002b3ecdcbe 100BASEPX10
307dd815-c010-11db-90e7-0002b3ecdcbe 1000BASEXHD
307dd816-c010-11db-90e7-0002b3ecdcbe 1000BASEXFD
307dd817-c010-11db-90e7-0002b3ecdcbe 1000BASELXHD
307dd818-c010-11db-90e7-0002b3ecdcbe 1000BASELXFD
307dd819-c010-11db-90e7-0002b3ecdcbe 1000BASESXHD
307dd81a-c010-11db-90e7-0002b3ecdcbe 1000BASESXFD
307dd81b-c010-11db-90e7-0002b3ecdcbe 1000BASETHD
307dd81c-c010-11db-90e7-0002b3ecdcbe 1000BASETFD
307dd81d-c010-11db-90e7-0002b3ecdcbe 10GigBASEFX
Table 5 shows the identifiers for physical layer that can be used for CompoNet.
Table 5 – Physical layer identifiers for CompoNet
Identifier value Description
475B2CB0-B1DA-11E2-9D9C-005056C00008 Standard CompoNet
475B2CAF-B1DA-11E2-9D9C-005056C00008 CompoNet IP67 Cable
Table 6 shows the identifiers for data link layer.
Table 6 – Data link layer identifiers
Identifier value Description
5B1EDEF7-B1CC-11E2-9D9C-005056C00008 DeviceNet (CAN – CSMA/NBA)
5B1EDEF8-B1CC-11E2-9D9C-005056C00008 ControlNet (CTDMA)
5B1EDEF9-B1CC-11E2-9D9C-005056C00008 EtherNet/IP (CSMA/CD)
5B1EDEFA-B1CC-11E2-9D9C-005056C00008 CompoNet (TDMA)
5 Access to instance and device data
The services InstanceDataInformation and DeviceDataInformation shall provide access at
least to all parameters defined in the Params section of the EDS.
6 Protocol specific behavior
IEC 61784 CPF 2 protocol has specific requirements related to configuration of fieldbus
masters.
It is very important to keep both data provider and consumer synchronized. Therefore data
provider shall be informed if the provided data has been modified. For instance, in case the
provided data is modified by the scanner/master DTM, then the slave/adapter DTM shall be
provided with the new data set.
NOTE For a description of data exchange between DTMs, see IEC 62453-2:–, 6.3 (Configuration of fieldbus
master or communication scheduler).
IEC 62453-302:2016 IEC 2016 – 11 –
7 Protocol specific usage of general data types
Table 7 shows how general data types, defined in IEC 62453-2 within the namespace ‘fdt’, are
used with IEC 61784 CPF 2 devices.
According to IEC 62453-2, at least one set of semantic information (one per supported
fieldbus protocol) shall be provided for each accessible data object, using the
‘SemanticInformation’ general data type. The corresponding data type ‘applicationDomain’
shall have the value “FDT_CIP” and the data type ‘semanticId’ shall have an appropriate
value, as specified in Table 7).
Table 7 – Protocol specific usage of general data types
Data type Description for use
fdt:address The “address” data type is not mandatory for the exposed parameters in
the DTMs. But if the address will be used, the string shall be
constructed according to the rules of the semanticId. That means the
data type “semanticId” is always the same as the data type “address”
fdt:protocolId See Clause 4.
fdt:deviceTypeId As defined in Identity object (see IEC 61158-5-2:2014, 6.2.1.2.2)
fdt:deviceTypeInformation A CIP DTM shall provide the path to the device specific EDS file with
this data type. For DTM certification, the path to the certified EDS file
shall be provided here.
NOTE The EDS information is accessible via
• IDtmParameter::GetParameters()
• IDtmInformation::GetInformation()
fdt:deviceTypeInformationPath Path to the EDS file which is also provided via the attribute
‘deviceTypeInformation’
The attribute contains full path to the EDS file including the file name in
URL notation.
For CIP devices, it is mandatory to provide information for this data
type.
This attribute is specific to FDT 1.2.1 (see IEC 62453-2 and [9]),
therefore it shall not be provided if DTM is running in FDT 1.2 (see [8])
based Frame Applications
fdt:manufacturerId As defined in Identity object (see IEC 61158-5-2:2014, 6.2.1.2.2)
fdt:semanticId The applicationDomain is: FDT_CIP.
fdt:applicationDomain The data that is contained in the objects are addressable via classId,
instanceId and attributeId. This data may be variables or composed
blocks of data. The semanticID is directly based on the CIP address
information:
The semanticId is: CLASSxx.INSTANCEyy.ATTRIBUTEzz
xx classId
yy instanceId
zz attributeId
xx, yy, zz are based on decimal format without leading ‘0’.
Since ‘ATTRIBUTE’ is conditional in CIP in certain cases, it can be left
out. In this case, the semanticId is:
CLASSxx.INSTANCEyy
fdt:tag CIP assembly, parameter name or name of a I/O connection (in the
context of channel data)
8 Protocol specific common data types
Table 8 and Table 9 specify the protocol specific common data types, which are used in the
definition of other data types.
– 12 – IEC 62453-302:2016 IEC 2016
The data types described in Clause 8 are defined for following namespace:
Namespace: cip
Table 8 – Simple protocol specific common data types
Data type Definition Description
attributeId USINT CIP attribute identifier
bitOffset UDINT Bit offset of a parameter in an assembly
cipStatus UINT cipStatus represents the Status (attribute 5) of
the Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2
classId UINT CIP class identifier
constValue UDINT Represents the constant value used in the data
type Constant
dataType enumeration ( byte | float | double | int Defines the different enumerations of the CIP
| unsigned | enumerator | data types
bitEnumerator | index | ascii |
password | bitString | hexString | date
| time | dateAndTime | duration |
binary | structured | dtmSpecific )
deviceType UINT Represents the DeviceType (attribute 2) of the
Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2
ePath ARRAY OF USINT CIP EPATH, see IEC 61158-6-2:2014, 4.1.9.
extendedIdentifier STRING Represents the address of the CIP device in the
CIPNodeID if the address used on this CIP
network is a name or IP-address. The
extendedIdentifier shall be used for CompoNet
networks to cover the CompoNet MAC ID.
See also shortIdentifier
instanceId UINT CIP object instance identifier
majorRevision USINT Represents the Major Revision (attribute 4.1) of
the Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2
minorRevision USINT Represents the Minor Revision (attribute 4.2) of
the Identity object. IEC 61158-5-2:2014,
6.2.1.2.2
portNumber UINT Represents the portnumber within a CIP bridging
or routing device to route a message to another
segment
productCode UINT Represents the Product code (attribute 3) of the
Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2
productName STRING Represents the Product name (attribute 7) of the
Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2
serialNumber ARRAY OF USINT Represents the Serialnumber (attribute 6) of the
Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2. If the serialNumber is not known
because of offline configuration then a 0 should
be returned
serviceCode USINT CIP service code. This is a function, or method,
supported by a CIP object or attribute
serviceName STRING CIP service name. This is a function, or method,
supported by a CIP object or attribute. This
attribute provides additional human readable
information about the related service code
shortIdentifier USINT Represents the address of the CIP device in the
CIPNodeID if the address used on this CIP-
network is a simple address. See also
extendedIdentifier
IEC 62453-302:2016 IEC 2016 – 13 –
Data type Definition Description
symbolicAddress STRING Represents a name of a component inside the
device
vendorID UINT Represents the Vendor ID (attribute 1) of the
Identity object. See IEC 61158-5-2:2014,
6.2.1.2.2
Table 9 – Structured protocol specific common data types
Data type Definition Description
Elementary data type U Multipli
sa city
ge
CIPDevice STRUCT Specifies a CIP device.
CIPDevice contains manufacturer and device
information (the Identity Object), which is
present in every CIP node
cipStatus M [1.1]
CIPPath M [1.1]
CIPDeviceIdentity M [1.1]
CIPDeviceIdentity STRUCT Represents the static part of the Identity object
of the CIP device. See IEC 61158-5-2:2014,
6.2.1.2.2
vendorID M [1.1]
deviceType M [1.1]
productCode M [1.1]
majorRevision M [1.1]
minorRevision M [1.1]
serialNumber M [1.1]
productName M [1.1]
CIPNodeID STRUCT Identifier used to identify a particular node
(device) on a CIP network, e.g. CIP MAC
(Media Access Control) ID (1 byte) for
DeviceNet and ControlNet; IP address for
EtherNet/IP.
Since the size differs from protocol to protocol,
structure is used which contains 2 attributes:
extended identifier (n bytes string) and short
identifier (1 byte unsigned integer) and only
one of them shall be used
choice of M [1.1]
ExtendedIdentifier S [1.1]
ShortIdentifier S [1.1]
CIPObjectAddress STRUCT CIP object address as CIPObjectId,
CIPSymbolicAddress or HexAddress
choice of M [1.1]
CIPObjectId S [1.1]
CIPSymbolicAddress S [1.1]
HexAddress S [1.1]
– 14 – IEC 62453-302:2016 IEC 2016
Data type Definition Description
Elementary data type U Multipli
sa city
ge
CIPObjectId STRUCT The CIP classId, instanceId and (conditional)
attributeId ‘address’ information for a CIP
object and attribute. If used in a Process
Channel this is likely to be either an Assembly
object or a Parameter object
classId M [1.1]
instanceId M [1.1]
attributeId O [0.1]
CIPPath STRUCT The full ‘address’ of the CIP node (device). In
general this consists of the Node ID stored in
the CIPNodeID element. The RoutingPath
element is used to transfer additional routing
information that can be used by the CIP FDT
communication component
RoutingPath O [0.1]
CIPNodeID M [1.1]
CIPSymbolicAddress STRUCT classId, instanceId and attributeId does not
necessarily be known, a symbolic address
could also be used.
CIPSymbolicAddress, HexAddress or
CIPObjectId could be used for
DataExchangeRequest
symbolicAddress M [1.1]
Constant STRUCT A constant value
constValue M [1.1]
ExtendedIdentifier STRUCT See attribute extendedIdentifier
extendedIdentifier M [1.1]
HexAddress STRUCT CIP object address as ePath
ePath O [0.1]
LinkAddress STRUCT Represents the CIPNodeID within a Segment
CIPNodeID M [1.1]
ParameterReference STRUCT Reference to a description of a parameter
fdt:idref M [1.1]
bitOffset O [0.1]
ReservedBits STRUCT Used wherever reserved bits are needed
RoutingPath STRUCT Any additional CIP network routing information,
which can be understood by the
Communication Channel
Segment M [1.1]
Segment STRUCT Represents the path a message shall follow to
reach the addressed CIP device
portNumber M [1.1]
LinkAddress M [1.1]
Segment O [0.1]
Service STRUCT CIP service identified by serviceCode and
serviceName. CIP service code is a function,
or method, supported by a CIP object or
attribute
serviceCode M [1.1]
serviceName O [0.1]
IEC 62453-302:2016 IEC 2016 – 15 –
Data type Definition Description
Elementary data type U Multipli
sa city
ge
ShortIdentifier STRUCT See attribute shortIdentifier
shortIdentifier M [1.1]
9 Network management data types
9.1 General
The data types specified in Clause 9 are used at following services:
• NetworkManagementInfoRead service;
• NetworkManagementInfoWrite service.
9.2 Node address
The CIPNodeID will be stored in the busAddress element of the fdt:DeviceAddress data type.
This is not used for CompoNet because the master has a fixed address – since this is a
mandatory element, the recommendation is to use the value “0”.
9.3 Scanner/master – Bus parameter set (CIP)
Information is sent to the CIP scanner/master within the UserDefinedBus element of the
NetworkInfo data type, using the data types specified in Table 10 and Table 11. This
information shall be set to configure the scan list of scanner/master.
The data types described in this subclause are defined for following namespace:
Namespace: cippar
Table 10 – Simple fieldbus configuration data types
Data type Definition Description
async USINT See Table 7-2.3 of [14]. This is a CIP Safety exclusive field. Only
applies to producing connections. Field should be empty for
consuming connections. Used to calculate Network Reaction
Time
base UINT Scaling parameters. See ISO 15745-2:2003, A.4.1.4.6
class0 BOOL See ISO 15745-3:2003, Table A.25
class1 BOOL
class2 BOOL
class3 BOOL
class4 BOOL
class5 BOOL
class6 BOOL
compoNetDeviceCategory USINT Defines the different categories of CompoNet devices. See [15],
Chapter 7-4
compoNetIOLength UINT See [15], Chapter 7-5
compoNetIOLengthUnit USINT
connectionId STRING Uniquely identifies the connection within the DTM.
connectionNameString STRING See ISO 15745-3:2003, Table A.24
connectionTypeMulticast BOOL See ISO 15745-3:2003, Table A.26
– 16 – IEC 62453-302:2016 IEC 2016
Data type Definition Description
connectionTypeNULL BOOL
connectionTypePoint2Point BOOL
consumedConnectionSize UINT Maximum number bytes received across this connection
defaultConnection BOOL Indicates whether the CIPConnection is default or not
defaultSafetyConnections USINT See Table 7-2.2 of [14]. Instance Number
defaultValue STRING Represents the value of the attribute when in offline state
div UINT Scaling parameters. See ISO 15745-2:2003, A.4.1.4.6
expectedPacketRate UINT Scanner determines this parameter. There might be some reason
that
...
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...