IEC 62026-3:2008

Low-voltage switchgear and controlgear - Controller-device interfaces (CDIs) - Part 3: DeviceNet

IEC 62026-3:2008 specifies an interface system between single or multiple controllers, and control circuit devices or switching elements. The interface system uses two twisted shielded conductor pairs within one cable - one of these pairs provides a differential communication medium and the other pair provides power to the devices. This part establishes requirements for the interchangeability of components with such interfaces. This second edition of IEC 62026-3 cancels and replaces the first edition published in 2000. This second edition constitutes a technical revision. The main changes with respect to the previous edition are listed below:
- addition of new services to the base messaging protocol in 5.2;
- replacement of detailed application layer requirements in former annexes by references in 5.3 to corresponding specifications in the new edition of IEC 61158 (2007);
- addition of requirements for a corresponding safety protocol in 5.6 (by reference to IEC 61784-3);
- modified presentation of cable and connector specifications in 8.2 and 8.4, and addition of a new type;
- addition of references for safety tests for both EMC and logical tests in 8.10 and 9.3.

Appareillage à basse tension - Interfaces appareil de commande-appareil (CDI) - Partie 3: DeviceNet

La CEI 62026-3:2008 spécifie un système d'interfaces entre un ou plusieurs appareils de commande d'une part, et des appareils ou éléments de commutation pour circuits de commande, d'autre part. Le système d'interfaces utilise deux paires conductrices torsadées blindées, réunies dans un câble - l'une des paires fournit un support de communication différentiel et l'autre alimente les appareils. Cette partie définit des exigences permettant l'interchangeabilité des composants incluant de telles interfaces. Cette deuxième édition de la CEI 62026-3 annule et remplace la première édition parue en 2000. Cette deuxième édition constitue une révision technique. La version française de cette norme n'a pas été soumise au vote. Les principales modifications effectuées par rapport à l'édition antérieure sont indiquées ci-dessous:
- ajout de nouveaux services au protocole de messagerie de base de 5.2;
- remplacement des exigences détaillées relatives à la couche d'application dans les annexes antérieures par des références en 5.3 aux spécifications correspondantes dans la nouvelle édition de la CEI 61158 (2007);
- ajout d'exigences pour un protocole de sécurité correspondant en 5.6 (par référence à la CEI 61784-3);
- présentation modifiée des spécifications de câbles et de connecteurs en 8.2 et 8.4, et ajout d'un nouveau type;
- ajout de références pour les essais de sécurité à la fois pour les essais de CEM et les essais logiques de 8.10 et 9.3.

General Information

• Status: Published
• Publication Date: 28-Jan-2008
• ICS: 29.130.20 - Low voltage switchgear and controlgear
• Technical Committee: SC 121A - Low-voltage switchgear and controlgear
• Drafting Committee: WG 3 - TC 121/SC 121A/WG 3
• Current Stage: DELPUB - Deleted Publication
• Start Date: 22-Aug-2014
• Completion Date: 26-Oct-2025

Relations

• Revises: IEC 62026-3:2000 - Low-voltage switchgear and controlgear - Controller-device interfaces (CDIs) - Part 3: DeviceNet
• Effective Date: 05-Sep-2023
• Revised: IEC 62026-3:2014 - Low-voltage switchgear and controlgear - Controller-device interfaces (CDIs) - Part 3: DeviceNet
• Effective Date: 05-Sep-2023

Overview

IEC 62026-3:2008 - "Low-voltage switchgear and controlgear - Controller‑device interfaces (CDIs) - Part 3: DeviceNet" defines an interface system for connecting single or multiple controllers to control circuit devices and switching elements using DeviceNet. The standard specifies a two-pair twisted‑shielded cable (one differential pair for communications and one pair for device power) and establishes requirements to ensure component interchangeability, interoperability and safe operation in low‑voltage switchgear and controlgear environments. Edition 2.0 (2008) replaces the 2000 edition and includes technical revisions such as new messaging services, references to IEC 61158 application layer specifications, and DeviceNet Safety requirements.

Key Topics

• DeviceNet protocol and messaging: Requirements for DeviceNet messaging protocol, I/O and explicit messaging, fragmentation and acknowledgement mechanisms (see clause 5.2 and related figures/tables).
• Communication model: Use of CAN and CIP within DeviceNet, DeviceNet communication object classes and link access state machine.
• Physical layer & cabling: Two twisted shielded conductor pairs in one cable (data pair + power pair), cable profiles (thick, thin, flat), connector types and pinouts, and a new cable/connector type added in this edition (clauses 7–8, figures/tables in clause 8).
• Interchangeability & connection sets: Predefined master/slave I/O and explicit messaging connection sets and allocation/release procedures.
• Safety and EMC: Addition of DeviceNet Safety™ requirements (by reference to IEC 61784-3), EMC and logical safety test references (clauses 8.10, 9.3).
• Testing and compliance: Electrical, EMC and logical tests for CDI devices; power supply, timing and transmit/receive characteristic test setups (clause 9).

Applications

IEC 62026-3:2008 is applicable to professionals and organizations involved in industrial automation and low‑voltage control systems who need standardized, interoperable controller‑to‑device interfaces:

• Control and automation engineers designing DeviceNet-based control cabinets and networks
• OEMs and device manufacturers developing DeviceNet-compatible sensors, actuators, I/O modules and drives
• Panel builders and system integrators specifying cabling, connectors and power distribution for DeviceNet trunks and taps
• Test labs and certification bodies performing EMC, logical and safety testing for CDI compliance
• Procurement and quality teams creating interoperability and compliance requirements for low‑voltage switchgear

Related Standards

• IEC 61158 (2007) - referenced for application layer specifications (CIP)
• IEC 61784-3 - referenced for DeviceNet Safety™ protocol requirements
• Standards on CAN and CIP technologies, and EMC/safety test guidance referenced within IEC 62026-3

Keywords: IEC 62026-3:2008, DeviceNet, Controller-device interfaces, CDI, low-voltage switchgear, CAN, CIP, IEC 61158, IEC 61784-3, DeviceNet Safety, cable specifications, EMC testing, interoperability.

Standards Content (Sample)

IEC 62026-3
Edition 2.0 2008-01
INTERNATIONAL
STANDARD
Low-voltage switchgear and controlgear – Controller-device interfaces (CDIs) –
Part 3: DeviceNet
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: [e-mail]
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: [e-mail]
Tel.: [phone]
Fax: [phone]
IEC 62026-3
Edition 2.0 2008-01
INTERNATIONAL
STANDARD
Low-voltage switchgear and controlgear – Controller-device interfaces (CDIs) –
Part 3: DeviceNet
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XE
ICS 29.130.20 ISBN 2-8318-9513-8

– 2 – 62026-3 © IEC:2008(E)
CONTENTS
FOREWORD.7
INTRODUCTION.9

1 Scope.10
2 Normative references .10
3 Terms, definitions, symbols and abbreviated terms.11
4 Classification.16
4.1 General .16
4.2 DeviceNet communication model.18
4.3 DeviceNet, CAN and CIP.18
5 Characteristics .19
5.1 DeviceNet connections .19
5.2 DeviceNet messaging protocol .20
5.3 DeviceNet communication object classes .50
5.4 Link access state machine.52
5.5 Predefined master/slave connection set .55
5.6 DeviceNet Safety™ .73
5.7 Physical layer.73
6 Product information .79
7 Normal service, mounting and transport conditions.79
7.1 Normal service conditions .79
7.2 Conditions during transport and storage .80
7.3 Mounting .80
8 Constructional and performance requirements.80
8.1 Indicators and configuration switches .80
8.2 DeviceNet cable .81
8.3 Terminating resistors.92
8.4 Connectors.92
8.5 Device taps and power taps .101
8.6 Link powered devices .103
8.7 Miswiring protection .103
8.8 Power supplies.103
8.9 Electromagnetic compatibility (EMC) .104
8.10 Additional functional safety requirements related to EMC . 106
9 Tests .106
9.1 General .106
9.2 Electrical and EMC testing .106
9.3 Logical testing .114

Bibliography.118

62026-3 © IEC:2008(E) – 3 –
Figure 1 – Typical DeviceNet controller-device interfaces .17
Figure 2 – DeviceNet protocol architecture compared with the OSI reference model .18
Figure 3 – DeviceNet’s use of the CAN identifier field .19
Figure 4 – Explicit message CAN data field use .21
Figure 5 – Explicit message data field format.21
Figure 6 – Explicit message header format .21
Figure 7 – Service field format .22
Figure 8 – Open explicit messaging connection request format .23
Figure 9 – Open explicit messaging connection response format .26
Figure 10 – Close connection request format .27
Figure 11 – Close connection response format .28
Figure 12 – Non-fragmented explicit request message format, values 0 – 3 .29
Figure 13 – Non-fragmented explicit request message format, value 4.30
Figure 14 – Non-fragmented success response message format.30
Figure 15 – Error response message .31
Figure 16 – Data field of an I/O message .31
Figure 17 – Format of DeviceNet fragmentation protocol.32
Figure 18 – I/O message fragment format .33
Figure 19 – Explicit message fragment format .33
Figure 20 – Acknowledgement message format .35
Figure 21 – Establishing the offline ownership .37
Figure 22 – Multicast nature of the offline ownership .38
Figure 23 – Offline ownership request message.39
Figure 24 – Offline ownership response message protocol.39
Figure 25 – Communication faulted request message – Multicast protocol .40
Figure 26 – Communication faulted request message – Point-to-point protocol.41
Figure 27 – Identify communication faulted request message – Multicast protocol .42
Figure 28 – Communication faulted identify response message .43
Figure 29 – Identify communication faulted request message – Point-to-point protocol .43
Figure 30 – Who communication faulted request message .44
Figure 31 – Who response message .45
Figure 32 – Change MAC ID communication faulted request message.45
Figure 33 – Device heartbeat message .46
Figure 34 – Device shutdown message .48
Figure 35 – Duplicate MAC ID check CAN identifier field .49
Figure 36 – Duplicate MAC ID check message data field format.49
Figure 37 – Link access state transition diagram.53
Figure 38 – Allocation choice byte contents .58
Figure 39 – Allocate_master/slave_connection_set request message .58
Figure 40 – Success response to allocate_master/slave_connection_set request .59
Figure 41 – Parent explicit messaging connection logic .61

– 4 – 62026-3 © IEC:2008(E)
Figure 42 – Release choice byte contents.62
Figure 43 – Release_master/slave_connection set request message .62
Figure 44 – Success response to release_master/slave_connection_set request .63
Figure 45 – Predefined master/slave I/O connection state transition diagram.65
Figure 46 – Predefined master/slave explicit messaging connection state transition
diagram .67
Figure 47 – Physical layer block diagram .74
Figure 48 – Device containing a non-isolated physical layer.76
Figure 49 – Device containing an isolated physical layer.77
Figure 50 – DeviceNet medium topology.78
Figure 51 – Thick cable: physical configuration.85
Figure 52 – Thick cable: current available on the DeviceNet power bus .85
Figure 53 – Thin cable: physical configuration .88
Figure 54 – Thin cable: current available on the DeviceNet power bus.88
Figure 55 – Flat cable: physical configuration .91
Figure 56 – Flat cable: current available on the DeviceNet power bus.91
Figure 57 – Open connector pinout .95
Figure 58 – Open connector geometry .95
Figure 59 – Mini connector pinout .97
Figure 60 – Micro connector pinout .98
Figure 61 – Flat trunk connector layout – Pin out .100
Figure 62 – Flat trunk connector layout – Geometry.101
Figure 63 – Power supply rise time test circuit .106
Figure 64 – Current consumption test circuit .107
Figure 65 – Power ON test circuit .108
Figure 66 – Test circuit for reversal of V+ and V-, and also V- interruption. 108
Figure 67 – Differential impedance test circuit .109
Figure 68 – Transmit level test setup .110
Figure 69 – Transmit levels.110
Figure 70 – Timing test setup.111
Figure 71 – Timing.111
Figure 72 – CDI test configuration .112
Figure 73 – Test circuit for logical tests.114

62026-3 © IEC:2008(E) – 5 –
Table 1 – Message body format values .24
Table 2 – Group select values .25
Table 3 – Source message ID in open explicit messaging connection request.25
Table 4 – Destination message ID in open explicit messaging connection response .26
Table 5 – UCMM error conditions/codes .28
Table 6 – Fragment type bit values .32
Table 7 – Ack status bit values .35
Table 8 – Offline connection set.37
Table 9 – Addresses reporting based upon mask .41
Table 10 – Device shutdown message shutdown code ranges .48
Table 11 – Device shutdown message “Open” shutdown codes .49
Table 12 – Link access state event matrix.53
Table 13 – Predefined master/slave connection set identifier fields.56
Table 14 – Allocate_master/slave_connection_set request service data field
parameters .57
Table 15 – Allocate_master/slave_connection set response parameters .59
Table 16 – Release_master/slave_connection_set request service data field
parameters .62
Table 17 – DeviceNet object specific additional error codes.64
Table 18 – Connection instance IDs for predefined master/slave connections.65
Table 19 – Predefined master/slave I/O connection state event matrix.66
Table 20 – Predefined master/slave explicit messaging connection state event matrix .68
Table 21 – Predefined master/slave I/O connection object attribute access .69
Table 22 – General physical layer characteristics .73
Table 23 – Transmitter characteristics .75
Table 24 – Receiver characteristics .75
Table 25 – Load limits.79
Table 26 – Cable profile: data pair specifications .81
Table 27 – Cable profile: DC power pair specifications .81
Table 28 – Cable profile: general specifications .82
Table 29 – Cable profile: topology .82
Table 30 – Thick cable: data pair specifications .83
Table 31 – Thick cable: DC power pair specifications .83
Table 32 – Thick cable: general specifications .84
Table 33 – Thick cable: topology.84
Table 34 – Thick cable: maximum current available (A) based on network length.85
Table 35 – Thin cable: data pair specifications.86
Table 36 – Thin cable: DC power pair specifications .87
Table 37 – Thin cable: general specifications.87
Table 38 – Thin cable: topology .87
Table 39 – Thin cable: maximum current available (A) based on network length .88
Table 40 – Flat cable: data pair specifications .89

– 6 – 62026-3 © IEC:2008(E)
Table 41 – Flat cable: DC power pair specifications .90
Table 42 – Flat cable: general specifications .90
Table 43 – Flat cable: topology .90
Table 44 – Flat cable: maximum current available (A) based on network length .91
Table 45 – Connector profile template .93
Table 46 – Open connector.94
Table 47 – Sealed mini connector .96
Table 48 – Sealed micro connector.97
Table 49 – Flat trunk connector .99
Table 50 – Internal pass-through conductor specifications . 102
Table 51 – Internal drop conductor specifications .102
Table 52 – Internal pass-through conductor specifications . 102
Table 53 – Internal power drop conductor specifications .103
Table 54 – Voltage regulator specifications.103
Table 55 – DeviceNet power supply specifications .104
Table 56 – Immunity performance criteria .105

62026-3 © IEC:2008(E) – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
LOW-VOLTAGE SWITCHGEAR AND CONTROLGEAR –
CONTROLLER-DEVICE INTERFACES (CDIs) –

Part 3: DeviceNet
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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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 62026-3 has been prepared by subcommittee 17B: Low-voltage
switchgear and controlgear, of IEC technical committee 17: Switchgear and controlgear.
This second edition of IEC 62026-3 cancels and replaces the first edition published in 2000.
This second edition constitutes a technical revision.

– 8 – 62026-3 © IEC:2008(E)
The main changes with respect to the previous edition are listed below:
• addition of new services to the base messaging protocol in 5.2;
• replacement of detailed application layer requirements in former annexes by references in
5.3 to corresponding specifications in the new edition of IEC 61158 (2007);
• addition of requirements for a corresponding safety protocol in 5.6 (by reference to
IEC 61784-3);
• modified presentation of cable and connector specifications in 8.2 and 8.4, and addition of
a new type;
• addition of references for safety tests for both EMC and logical tests in 8.10 and 9.3)
The text of this standard is based on the first edition and the following documents:
FDIS Report on voting
17B/1580/FDIS 17B/1585/RVD
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 62026, under the general title Low-voltage switchgear and
controlgear – Controller-device interfaces (CDIs), 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.
A bilingual version of this publication may be issued at a later date.

62026-3 © IEC:2008(E) – 9 –
INTRODUCTION
)
DeviceNet™ is intended for use in, but is not limited to, industrial automation applications.
These applications may include devices such as limit switches, proximity sensors, electro-
pneumatic valves, relays, motor starters, operator interface panels, analogue inputs, analogue
outputs and controllers.
—————————
)
DeviceNet™ is a trade name of Open DeviceNet Vendor Association, Inc. This information is given for the
convenience of users of this International Standard and does not constitute an endorsement by IEC of the
trademark holder or any of its products. Compliance to this standard does not require use of the trade name
DeviceNet™. Use of the trade name DeviceNet™ requires permission of Open DeviceNet Vendor Association,
Inc.
– 10 – 62026-3 © IEC:2008(E)
LOW-VOLTAGE SWITCHGEAR AND CONTROLGEAR –
CONTROLLER-DEVICE INTERFACES (CDIs) –

Part 3: DeviceNet
1 Scope
This part of IEC 62026 specifies an interface system between single or multiple controllers,
and control circuit devices or switching elements. The interface system uses two twisted
shielded conductor pairs within one cable – one of these pairs provides a differential
communication medium and the other pair provides power to the devices. This part
establishes requirements for the interchangeability of components with such interfaces.
This part of IEC 62026 specifies the following particular requirements for DeviceNet:
− requirements for interfaces between controllers and switching elements;
− normal service conditions for devices;
− constructional and performance requirements;
tests to verify conformance to requirements.
These particular requirements apply in addition to the general requirements of IEC 62026-1.
2 Normative references
The following referenced documents are indispensable for the application 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.
IEC 60529:1989, Degrees of protection provided by enclosures (IP Code)
Amendment 1 (1999)
IEC 60947-5-2:1997, Low-voltage switchgear and controlgear – Part 5-2: Control circuit
devices and switching elements – Proximity switches
Amendment 1 (1999)
Amendment 2 (2003)
IEC 61000-4-2:1995, Electromagnetic compatibility (EMC) – Part 4-2: Testing and
measurement techniques – Electrostatic discharge immunity test
Amendment 1 (1998)
Amendment 2 (2000)
IEC 61000-4-3:2006, Electromagnetic compatibility (EMC) – Part 4-3: Testing and
measurement techniques – Radiated, radio-frequency, electromagnetic field immunity test
IEC 61000-4-4:2004, Electromagnetic compatibility (EMC) – Part 4-4: Testing and
measurement techniques – Electrical fast transient/burst immunity test
IEC 61000-4-5:2005, Electromagnetic compatibility (EMC) – Part 4-5: Testing and
measurement techniques – Surge immunity test

62026-3 © IEC:2008(E) – 11 –
IEC 61000-4-6:2003, Electromagnetic compatibility (EMC) – Part 4-6: Testing and
measurement techniques – Immunity to conducted disturbances, induced by radio-frequency
fields
Amendment 1 (2004)
Amendment 2 (2006)
IEC 61158 (all parts), Digital data communications for measurement and control – Fieldbus for
use in industrial control systems
IEC 61158-4-2, Industrial communication networks – Fieldbus specifications –Part 4-2: Data-
link layer protocol specification – Type 2 elements
IEC 61158-5-2, Industrial communication networks – Fieldbus specifications – Part 5-2:
Application layer service definition – Type 2 elements
IEC 61158-6-2, Industrial communication networks – Fieldbus specifications –Part 6-2:
Application layer protocol specification – Type 2 elements
IEC 61508 (all parts), Functional safety of electrical/electronic/programmable electronic
safety-related systems
IEC 61784-3-2, Industrial communication networks – Profiles – Part 3-2: Functional safety
fieldbuses – Additional specifications for CPF 2
IEC 62026-1:2007, Low-voltage switchgear and controlgear – Controller-device interfaces
(CDIs) – Part 1: General rules
ISO/IEC 7498-1:1994, Information technology – Open Systems Interconnection – Basic
Reference Model: The Basic Model
ISO 11898-1:2003, Road vehicles – Controller area network (CAN) – Part 1: Data link layer
and physical signalling
ISO 11898-2:2003, Road vehicles – Controller area network (CAN) – Part 2: High-speed
medium access unit
CISPR 11:2003, Industrial, scientific and medical (ISM) radio-frequency equipment –
Electromagnetic disturbance characteristics – Limits and methods of measurement
Amendment 1 (2004)
Amendment 2 (2006)
3 Terms, definitions, symbols and abbreviated terms
For the purposes of this part of IEC 62026, the following terms, definitions, symbols and
abbreviations, in addition to those given in IEC 62026-1, apply.
3.1 Terms and definitions
3.1.1
acknowledged fragmentation
fragmentation performed on an explicit message, in which the transmission of a fragment from
the transmitting object is followed by the transmission of an acknowledgement by the
receiving object
NOTE The reception of each fragment is acknowledged by the receiving object.

– 12 – 62026-3 © IEC:2008(E)
3.1.2
ack status
field within an acknowledgement/response message format that indicates whether or not an
error has been encountered by the receiver of a fragmented message
NOTE This applies specifically to the DeviceNet fragmentation protocol.
3.1.3
application objects
set of object classes and their object instances that are available within the node
NOTE These objects manage and provide the exchange of data and messages across DeviceNet controller-device
interfaces (CDIs) and within the DeviceNet compliant node.
3.1.4
attribute
description of an externally accessible characteristic or feature of an object
NOTE Attributes typically provide status information or govern the operation of an object.
3.1.5
bit-strobe
communication using strobing
3.1.6
broadcast
communication from one node to all other nodes
3.1.7
CAN (Controller Area Network)
ISO specification that defines a generic physical layer and data link medium access
procedure based on non-destructive bit-wise arbitration, see ISO 11898-1 and ISO 11898-2
3.1.8
CAN_H
positive half of the differential physical CAN signal
3.1.9
CAN_L
negative half of the differential physical CAN signal
3.1.10
client
(1) object which uses the services of another (server) object to perform a task, see server
(3.1.43)
(2) initiator of a message to which a server reacts
3.1.11
common service
CIP service used by DeviceNet objects (see IEC 61158-5-2, 6.2.1.3 and IEC 61158-6-2, 4.1.8)
3.1.12
communication objects
objects that manage and provide run-time exchange of messages across DeviceNet
3.1.13
connection
logical binding between two or more application objects

62026-3 © IEC:2008(E) – 13 –
NOTE These application objects may be located at the same node or at different nodes.
3.1.14
connection ID (CID)
connection identifier assigned to all transmissions that are associated with a particular
connection between multiple nodes
3.1.15
connection object
manages the communication-specific aspects associated with connections between nodes
3.1.16
consumer
end point of a connection that is responsible for receiving data
3.1.17
destination MAC ID
MAC ID of a node that is to receive a message
3.1.18
device tap
physical point of attachment from a DeviceNet device to a trunk cable or a drop cable
3.1.19
device type
identification of a collection of device-dependent information describing a viable combination
of options selected for all layers in the communication stack
3.1.20
dominant
one of two complementary logic levels on the physical signal
NOTE The dominant level is a logical "0".
3.1.21
duplicate MAC ID detection
DeviceNet-defined protocol that ensures no two nodes on the same link are assigned the
same MAC ID
3.1.22
explicit messaging
each explicit message commands the performance of a particular task and the return of the
results of the task performance to the requester
3.1.23
fragmentation
DeviceNet protocol provided by the connection object that defines a method by which data
greater than eight (8) bytes in length may be transmitted
3.1.24
group 2 client
unconnected message manager (UCMM)capable device that has gained ownership of the
predefined master/slave connection set within a server such that it may act as the client on
those connections
3.1.25
group 2 only client
device that is acting as a group 2 client to a group 2 only server

– 14 – 62026-3 © IEC:2008(E)
NOTE The group 2 only client provides the UCMM functionality for group 2 only servers that it has allocated.
3.1.26
group 2 server
unconnected message manager (UCMM) capable device that has been configured to act as
the server for the predefined master/slave identifier connections
3.1.27
group 2 only server
slave device that is UCMM incapable and uses the predefined master/slave connection set to
establish communications
NOTE A group 2 only device can transmit and receive only those identifiers defined by the predefined
master/slave connection set.
3.1.28
I/O connection
connection between a producer and one or more consumers for the purpose of exchanging
application-specific, time-critical I/O data
3.1.29
I/O data
information which is transferred between I/O points and the controllers which use and set the
values
3.1.30
I/O messaging
exchange of data in a previously defined format
3.1.31
isolated device
device in which some of its components are not referenced to the V- of the physical layer, see
non-isolated device (3.1.36)
3.1.32
master
node which gathers and distributes I/O using the predefined master/slave connection set
3.1.33
Medium Access Control (MAC) ID
link address of a DeviceNet node
3.1.34
multicast connection
logical connection from one object to multiple other objects
NOTE A multicast connection allows data to be transferred in a single transaction from a producer to multiple
consumers sharing the same connection.
3.1.35
node
DeviceNet entity which is identified at the data link level by a unique MAC ID
NOTE Multiple DeviceNet nodes may be implemented in one device but they appear as logically distinct nodes on
the DeviceNet link.
3.1.36
non-isolated device
device in which all components are referenced to the V- of the physical layer, see isolated
device (3.1.31)
62026-3 © IEC:2008(E) – 15 –
3.1.37
object
1) abstract representation of a device’s capabilities
NOTE Objects may be composed of any or all of the following components:
a) Data (information which changes with time);
b) Configuration (parameters for behaviour);
c) Procedures(actions that may be performed using data and configuration).
2) collection of related data (in the form of variables) and procedures for operating on that
data
3.1.38
point-to-point connection
connection that exists between two objects only
NOTE Explicit messaging connections are always point-to-point. I/O connections may be either point-to-point or
multicast, see multicast connection (3.1.34).
3.1.39
predefined master/slave connection set
utilization of an explicit messaging connection to create and configure connection objects
within each connection end-point
NOTE Uses the general rules as a basis for the definition of a set of connections which facilitate communications
typically seen in a master/slave relationship.
3.1.40
producer
end point of a connection that is responsible for sending data
3.1.41
recessive
one of two complementary logic levels on the physical signal
NOTE The recessive level is a logical "1".
3.1.42
serial number
unique 32-bit integer assigned by each manufacturer to every DeviceNet device
NOTE The number is stored within the device as an attribute of the identity object and is unique with respect to
the manufacturer.
3.1.43
server
object which provides services to another (client) object, see client (3.1.10)
3.1.44
service
operation or function that an object performs upon request from another object
3.1.45
slave
node that returns data to its master using the predefined master/slave connection set and a
communication method set by the master
3.1.46
source MAC ID
MAC ID of a node that is transmitting a message

– 16 – 62026-3 © IEC:2008(E)
3.1.47
trigger
service used by an application to initiate the production of data
3.1.48
UCMM capable device
device that supports the UCMM (see 3.1.51)
3.1.49
UCMM incapable device
device that does not support the UCMM (see 3.1.51)
3.1.50
unconnected explicit message
explicit message between nodes that have not yet established a connection between each
other
3.1.51
Unconnected Message Manager (UCMM)
function within a node that receives and processes unconnected explicit messages
3.1.52
Unsigned Short Integer (USINT)
8-bit integer
3.1.53
Unsigned Integer (UINT)
16-bit integer
3.2 Symbols and abbreviated terms
CAN Controller Area Network
CDI Controller-Device Interface
CID Connection Identifier
CIP™ Common Industrial Protocol
CRC Cyclic Redundancy Check
DCR DC Resistance
EUT Equipment Under Test
MAC ID Medium ACcess layer IDentifier
UCMM Unconnected Message Manager
4 Classification
4.1 General
DeviceNet interfaces controlling devices to control circuit devices or switching elements.
DeviceNet uses two twisted shielded conductor pairs within one cable - one of these pairs
provides a differential communication medium, and the other pair provides power to the
devices. The maximum current supported is 8 A at 24 V d.c. Data is transmitted at bit rates of
125 kbit/s, 250 kbit/s or 500 kbit/s with maximum cable lengths of 500 m, 250 m and 100 m
respectively. A maximum of 8 bytes of data may be transmitted without fragmentation. A
maximum of 64 nodes may be connected using a linear topology with a trunk line and drop
lines (see Figure 1). DeviceNet supports the transmission of I/O data, diagnostics, messaging
and programming/configuration. Data exchange may be event driven (change of state), cyclic,
polled, or multicast.
62026-3 © IEC:2008(E) – 17 –
Controller
Limit
Proximity
Pushbutton
Motor
switch
sensor
station
starter
Circuit-
Other
breaker
Photo
devices
Indicator
Solenoid
sensor
Relay
valve lamps
IEC  1204/2000
Figure 1 – Typical DeviceNet controller-device interfaces
This part of IEC 62026 defines a connection based scheme to facilitate all application
communications. A DeviceNet connection provides a communication path between multiple
end-points. The end-points of a connection are applications that need to share data.
Transmissions associated with a particular connection are assigned an identification value
when a connection is established. This identification value is called the connection ID (CID).
Connection objects model the communication characteristics of a particular application-to-
application(s) relationship.
DeviceNet’s connection based scheme defines a dynamic means by which the following two
types of connections may be established:
− I/O connections: Provide dedicated, special purpose communication paths between a
producing application and one or more consuming applications. Application specific I/O
data moves through these paths.
I/O messages are exchanged across I/O connections. An I/O message consists of a CID
and associated I/O data. The connection end-points shall have knowledge of the intended
use or meaning of the I/O message.
This part of IEC 62026 does not define any particular use for I/O messaging. There are a
wide variety of functions that may be accomplished using I/O messaging. The meaning
and/or intended use of all I/O messages shall be made known
...

IEC 62026-3 ®
Edition 2.0 2008-01
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Low-voltage switchgear and controlgear – Controller-device interfaces (CDIs) –
Part 3: DeviceNet
Appareillage à basse tension – Interfaces appareil de commande-appareil (CDI) –
Partie 3: DeviceNet
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.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI ou si vous désirez obtenir des droits supplémentaires sur cette
publication, utilisez les coordonnées ci-après ou contactez le Comité national de la CEI de votre pays de résidence.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: [e-mail]
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: [e-mail]
Tel.: [phone]
Fax: [phone]
A propos de la CEI
La Commission Electrotechnique Internationale (CEI) est la première organisation mondiale qui élabore et publie des
normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications CEI
Le contenu technique des publications de la CEI est constamment revu. Veuillez vous assurer que vous possédez
l’édition la plus récente, un corrigendum ou amendement peut avoir été publié.
ƒ Catalogue des publications de la CEI: www.iec.ch/searchpub/cur_fut-f.htm
Le Catalogue en-ligne de la CEI vous permet d’effectuer des recherches en utilisant différents critères (numéro de référence,
texte, comité d’études,…). Il donne aussi des informations sur les projets et les publications retirées ou remplacées.
ƒ Just Published CEI: www.iec.ch/online_news/justpub
Restez informé sur les nouvelles publications de la CEI. Just Published détaille deux fois par mois les nouvelles
publications parues. Disponible en-ligne et aussi par email.
ƒ Electropedia: www.electropedia.org
Le premier dictionnaire en ligne au monde de termes électroniques et électriques. Il contient plus de 20 000 termes et
définitions en anglais et en français, ainsi que les termes équivalents dans les langues additionnelles. Egalement appelé
Vocabulaire Electrotechnique International en ligne.
ƒ Service Clients: www.iec.ch/webstore/custserv/custserv_entry-f.htm
Si vous désirez nous donner des commentaires sur cette publication ou si vous avez des questions, visitez le FAQ du
Service clients ou contactez-nous:
Email: [e-mail]
Tél.: [phone]
Fax: [phone]
IEC 62026-3 ®
Edition 2.0 2008-01
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Low-voltage switchgear and controlgear – Controller-device interfaces (CDIs) –
Part 3: DeviceNet
Appareillage à basse tension – Interfaces appareil de commande-appareil (CDI) –
Partie 3: DeviceNet
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
XE
CODE PRIX
ICS 29.130.20 ISBN 978-2-88910-610-3
– 2 – 62026-3 © IEC:2008
CONTENTS
FOREWORD.7
INTRODUCTION.9
1 Scope.10
2 Normative references .10
3 Terms, definitions, symbols and abbreviated terms.11
4 Classification.16
4.1 General .16
4.2 DeviceNet communication model.18
4.3 DeviceNet, CAN and CIP.18
5 Characteristics .19
5.1 DeviceNet connections .19
5.2 DeviceNet messaging protocol .20
5.3 DeviceNet communication object classes .50
5.4 Link access state machine.52
5.5 Predefined master/slave connection set .55
5.6 DeviceNet Safety™ .73
5.7 Physical layer.73
6 Product information .79
7 Normal service, mounting and transport conditions.79
7.1 Normal service conditions .79
7.2 Conditions during transport and storage .80
7.3 Mounting .80
8 Constructional and performance requirements.80
8.1 Indicators and configuration switches .80
8.2 DeviceNet cable .81
8.3 Terminating resistors.92
8.4 Connectors.92
8.5 Device taps and power taps .101
8.6 Link powered devices .103
8.7 Miswiring protection .103
8.8 Power supplies.103
8.9 Electromagnetic compatibility (EMC) .104
8.10 Additional functional safety requirements related to EMC . 106
9 Tests .106
9.1 General .106
9.2 Electrical and EMC testing .106
9.3 Logical testing .114
Bibliography.117

62026-3 © IEC:2008 – 3 –
Figure 1 – Typical DeviceNet controller-device interfaces .17
Figure 2 – DeviceNet protocol architecture compared with the OSI reference model .18
Figure 3 – DeviceNet’s use of the CAN identifier field .19
Figure 4 – Explicit message CAN data field use .21
Figure 5 – Explicit message data field format.21
Figure 6 – Explicit message header format .21
Figure 7 – Service field format .22
Figure 8 – Open explicit messaging connection request format .23
Figure 9 – Open explicit messaging connection response format .26
Figure 10 – Close connection request format .27
Figure 11 – Close connection response format .28
Figure 12 – Non-fragmented explicit request message format, values 0 - 3.29
Figure 13 – Non-fragmented explicit request message format, value 4.30
Figure 14 – Non-fragmented success response message format.30
Figure 15 – Error response message .31
Figure 16 – Data field of an I/O message .31
Figure 17 – Format of DeviceNet fragmentation protocol.32
Figure 18 – I/O message fragment format .33
Figure 19 – Explicit message fragment format .33
Figure 20 – Acknowledgement message format .35
Figure 21 – Establishing the offline ownership .37
Figure 22 – Multicast nature of the offline ownership .38
Figure 23 – Offline ownership request message.39
Figure 24 – Offline ownership response message protocol.39
Figure 25 – Communication faulted request message – Multicast protocol .40
Figure 26 – Communication faulted request message – Point-to-point protocol.41
Figure 27 – Identify communication faulted request message – Multicast protocol .42
Figure 28 – Communication faulted identify response message .43
Figure 29 – Identify communication faulted request message – Point-to-point protocol .43
Figure 30 – Who communication faulted request message .44
Figure 31 – Who response message .45
Figure 32 – Change MAC ID communication faulted request message.45
Figure 33 – Device heartbeat message .46
Figure 34 – Device shutdown message .48
Figure 35 – Duplicate MAC ID check CAN identifier field .49
Figure 36 – Duplicate MAC ID check message data field format.49
Figure 37 – Link access state transition diagram.53
Figure 38 – Allocation choice byte contents .58
Figure 39 – Allocate_master/slave_connection_set request message .58
Figure 40 – Success response to allocate_master/slave_connection_set request .59
Figure 41 – Parent explicit messaging connection logic .61
Figure 42 – Release choice byte contents.62

– 4 – 62026-3 © IEC:2008
Figure 43 – Release_master/slave_connection set request message .62
Figure 44 – Success response to release_master/slave_connection_set request .63
Figure 45 – Predefined master/slave I/O connection state transition diagram.65
Figure 46 – Predefined master/slave explicit messaging connection state transition
diagram .67
Figure 47 – Physical layer block diagram .74
Figure 48 – Device containing a non-isolated physical layer.76
Figure 49 – Device containing an isolated physical layer.77
Figure 50 – DeviceNet medium topology.78
Figure 51 – Thick cable: physical configuration.85
Figure 52 – Thick cable: current available on the DeviceNet power bus .85
Figure 53 – Thin cable: physical configuration .88
Figure 54 – Thin cable: current available on the DeviceNet power bus.88
Figure 55 – Flat cable: physical configuration .91
Figure 56 – Flat cable: current available on the DeviceNet power bus.91
Figure 57 – Open connector pinout .95
Figure 58 – Open connector geometry .95
Figure 59 – Mini connector pinout .97
Figure 60 – Micro connector pinout .98
Figure 61 – Flat trunk connector layout – Pin out .100
Figure 62 – Flat trunk connector layout – Geometry.101
Figure 63 – Power supply rise time test circuit .106
Figure 64 – Current consumption test circuit .107
Figure 65 – Power ON test circuit .108
Figure 66 – Test circuit for reversal of V+ and V−, and also V− interruption .108
Figure 67 – Differential impedance test circuit .109
Figure 68 – Transmit level test setup .110
Figure 69 – Transmit levels.110
Figure 70 – Timing test setup.111
Figure 71 – Timing.111
Figure 72 – CDI test configuration .112
Figure 73 – Test circuit for logical tests.114

62026-3 © IEC:2008 – 5 –
Table 1 – Message body format values .24
Table 2 – Group select values .25
Table 3 – Source message ID in open explicit messaging connection request.25
Table 4 – Destination message ID in open explicit messaging connection response .26
Table 5 – UCMM error conditions/codes .28
Table 6 – Fragment type bit values .32
Table 7 – Ack status bit values .35
Table 8 – Offline connection set.37
Table 9 – Addresses reporting based upon mask .41
Table 10 – Device shutdown message shutdown code ranges .48
Table 11 – Device shutdown message “Open” shutdown codes .49
Table 12 – Link access state event matrix.53
Table 13 – Predefined master/slave connection set identifier fields.56
Table 14 – Allocate_master/slave_connection_set request service data field
parameters .57
Table 15 – Allocate_master/slave_connection set response parameters .59
Table 16 – Release_master/slave_connection_set request service data field
parameters .62
Table 17 – DeviceNet object specific additional error codes.64
Table 18 – Connection instance IDs for predefined master/slave connections.65
Table 19 – Predefined master/slave I/O connection state event matrix.66
Table 20 – Predefined master/slave explicit messaging connection state event matrix .68
Table 21 – Predefined master/slave I/O connection object attribute access .69
Table 22 – General physical layer characteristics .73
Table 23 – Transmitter characteristics .75
Table 24 – Receiver characteristics .75
Table 25 – Load limits.79
Table 26 – Cable profile: data pair specifications .81
Table 27 – Cable profile: DC power pair specifications .81
Table 28 – Cable profile: general specifications .82
Table 29 – Cable profile: topology .82
Table 30 – Thick cable: data pair specifications .83
Table 31 – Thick cable: DC power pair specifications .83
Table 32 – Thick cable: general specifications .84
Table 33 – Thick cable: topology.84
Table 34 – Thick cable: maximum current available (A) based on network length.85
Table 35 – Thin cable: data pair specifications.86
Table 36 – Thin cable: DC power pair specifications .87
Table 37 – Thin cable: general specifications.87
Table 38 – Thin cable: topology .87
Table 39 – Thin cable: maximum current available (A) based on network length .88
Table 40 – Flat cable: data pair specifications .89
Table 41 – Flat cable: DC power pair specifications .90

– 6 – 62026-3 © IEC:2008
Table 42 – Flat cable: general specifications .90
Table 43 – Flat cable: topology .90
Table 44 – Flat cable: maximum current available (A) based on network length .91
Table 45 – Connector profile template .93
Table 46 – Open connector.94
Table 47 – Sealed mini connector .96
Table 48 – Sealed micro connector.97
Table 49 – Flat trunk connector .99
Table 50 – Internal pass-through conductor specifications . 102
Table 51 – Internal drop conductor specifications .102
Table 52 – Internal pass-through conductor specifications . 102
Table 53 – Internal power drop conductor specifications .103
Table 54 – Voltage regulator specifications.103
Table 55 – DeviceNet power supply specifications .104
Table 56 – Immunity performance criteria .105

62026-3 © IEC:2008 – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
LOW-VOLTAGE SWITCHGEAR AND CONTROLGEAR –
CONTROLLER-DEVICE INTERFACES (CDIs) –

Part 3: DeviceNet
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 62026-3 has been prepared by subcommittee 17B: Low-voltage
switchgear and controlgear, of IEC technical committee 17: Switchgear and controlgear.
This second edition of IEC 62026-3 cancels and replaces the first edition published in 2000.
This second edition constitutes a technical revision.

– 8 – 62026-3 © IEC:2008
The main changes with respect to the previous edition are listed below:
• addition of new services to the base messaging protocol in 5.2;
• replacement of detailed application layer requirements in former annexes by references in
5.3 to corresponding specifications in the new edition of IEC 61158 (2007);
• addition of requirements for a corresponding safety protocol in 5.6 (by reference to
IEC 61784-3);
• modified presentation of cable and connector specifications in 8.2 and 8.4, and addition of
a new type;
• addition of references for safety tests for both EMC and logical tests in 8.10 and 9.3.
This bilingual version, published in 2009-11, corresponds to the English version.
The text of this standard is based on the first edition and the following documents:
FDIS Report on voting
17B/1580/FDIS 17B/1585/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
The French version of this standard has not been voted upon.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 62026, under the general title Low-voltage switchgear and
controlgear – Controller-device interfaces (CDIs), 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.
62026-3 © IEC:2008 – 9 –
INTRODUCTION
)
DeviceNet™ is intended for use in, but is not limited to, industrial automation applications.
These applications may include devices such as limit switches, proximity sensors, electro-
pneumatic valves, relays, motor starters, operator interface panels, analogue inputs, analogue
outputs and controllers.
—————————
)
DeviceNet™ is a trade name of Open DeviceNet Vendor Association, Inc. This information is given for the
convenience of users of this International Standard and does not constitute an endorsement by IEC of the
trademark holder or any of its products. Compliance to this standard does not require use of the trade name
DeviceNet™. Use of the trade name DeviceNet™ requires permission of Open DeviceNet Vendor Association,
Inc.
– 10 – 62026-3 © IEC:2008
LOW-VOLTAGE SWITCHGEAR AND CONTROLGEAR –
CONTROLLER-DEVICE INTERFACES (CDIs) –

Part 3: DeviceNet
1 Scope
This part of IEC 62026 specifies an interface system between single or multiple controllers,
and control circuit devices or switching elements. The interface system uses two twisted
shielded conductor pairs within one cable – one of these pairs provides a differential
communication medium and the other pair provides power to the devices. This part
establishes requirements for the interchangeability of components with such interfaces.
This part of IEC 62026 specifies the following particular requirements for DeviceNet:
− requirements for interfaces between controllers and switching elements;
− normal service conditions for devices;
− constructional and performance requirements;
tests to verify conformance to requirements.
These particular requirements apply in addition to the general requirements of IEC 62026-1.
2 Normative references
The following referenced documents are indispensable for the application 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.
IEC 60529:1989, Degrees of protection provided by enclosures (IP Code)
Amendment 1 (1999)
IEC 60947-5-2:1997, Low-voltage switchgear and controlgear – Part 5-2: Control circuit
devices and switching elements – Proximity switches
Amendment 1 (1999)
Amendment 2 (2003)
IEC 61000-4-2:1995, Electromagnetic compatibility (EMC) – Part 4-2: Testing and
measurement techniques – Electrostatic discharge immunity test
Amendment 1 (1998)
Amendment 2 (2000)
IEC 61000-4-3:2006, Electromagnetic compatibility (EMC) – Part 4-3: Testing and
measurement techniques – Radiated, radio-frequency, electromagnetic field immunity test
IEC 61000-4-4:2004, Electromagnetic compatibility (EMC) – Part 4-4: Testing and
measurement techniques – Electrical fast transient/burst immunity test
IEC 61000-4-5:2005, Electromagnetic compatibility (EMC) – Part 4-5: Testing and
measurement techniques – Surge immunity test

62026-3 © IEC:2008 – 11 –
IEC 61000-4-6:2003, Electromagnetic compatibility (EMC) – Part 4-6: Testing and
measurement techniques – Immunity to conducted disturbances, induced by radio-frequency
fields
Amendment 1 (2004)
Amendment 2 (2006)
IEC 61158 (all parts), Digital data communications for measurement and control – Fieldbus for
use in industrial control systems
IEC 61158-4-2, Industrial communication networks – Fieldbus specifications – Part 4-2: Data-
link layer protocol specification – Type 2 elements
IEC 61158-5-2, Industrial communication networks – Fieldbus specifications – Part 5-2:
Application layer service definition – Type 2 elements
IEC 61158-6-2, Industrial communication networks – Fieldbus specifications – Part 6-2:
Application layer protocol specification – Type 2 elements
IEC 61508 (all parts), Functional safety of electrical/electronic/programmable electronic
safety-related systems
IEC 61784-3-2, Industrial communication networks – Profiles – Part 3-2: Functional safety
fieldbuses – Additional specifications for CPF 2
IEC 62026-1:2007, Low-voltage switchgear and controlgear – Controller-device interfaces
(CDIs) – Part 1: General rules
ISO/IEC 7498-1:1994, Information technology – Open Systems Interconnection – Basic
Reference Model: The Basic Model
ISO 11898-1:2003, Road vehicles – Controller area network (CAN) – Part 1: Data link layer
and physical signalling
ISO 11898-2:2003, Road vehicles – Controller area network (CAN) – Part 2: High-speed
medium access unit
CISPR 11:2003, Industrial, scientific and medical (ISM) radio-frequency equipment –
Electromagnetic disturbance characteristics – Limits and methods of measurement
Amendment 1 (2004)
Amendment 2 (2006)
3 Terms, definitions, symbols and abbreviated terms
For the purposes of this part of IEC 62026, the following terms, definitions, symbols and
abbreviations, in addition to those given in IEC 62026-1, apply.
3.1 Terms and definitions
3.1.1
acknowledged fragmentation
fragmentation performed on an explicit message, in which the transmission of a fragment from
the transmitting object is followed by the transmission of an acknowledgement by the
receiving object
NOTE The reception of each fragment is acknowledged by the receiving object.

– 12 – 62026-3 © IEC:2008
3.1.2
ack status
field within an acknowledgement/response message format that indicates whether or not an
error has been encountered by the receiver of a fragmented message
NOTE This applies specifically to the DeviceNet fragmentation protocol.
3.1.3
application objects
set of object classes and their object instances that are available within the node
NOTE These objects manage and provide the exchange of data and messages across DeviceNet controller-
device interfaces (CDIs) and within the DeviceNet compliant node.
3.1.4
attribute
description of an externally accessible characteristic or feature of an object
NOTE Attributes typically provide status information or govern the operation of an object.
3.1.5
bit-strobe
communication using strobing
3.1.6
broadcast
communication from one node to all other nodes
3.1.7
CAN (Controller Area Network)
ISO specification that defines a generic physical layer and data link medium access
procedure based on non-destructive bit-wise arbitration, see ISO 11898-1 and ISO 11898-2
3.1.8
CAN_H
positive half of the differential physical CAN signal
3.1.9
CAN_L
negative half of the differential physical CAN signal
3.1.10
client
(1) object which uses the services of another (server) object to perform a task, see server
( 3. 1. 43 )
(2) initiator of a message to which a server reacts
3.1.11
common service
CIP service used by DeviceNet objects (see IEC 61158-5-2, 6.2.1.3 and IEC 61158-6-2, 4.1.8)
3.1.12
communication objects
objects that manage and provide run-time exchange of messages across DeviceNet
3.1.13
connection
logical binding between two or more application objects

62026-3 © IEC:2008 – 13 –
NOTE These application objects may be located at the same node or at different nodes.
3.1.14
connection ID (CID)
connection identifier assigned to all transmissions that are associated with a particular
connection between multiple nodes
3.1.15
connection object
manages the communication-specific aspects associated with connections between nodes
3.1.16
consumer
end point of a connection that is responsible for receiving data
3.1.17
destination MAC ID
MAC ID of a node that is to receive a message
3.1.18
device tap
physical point of attachment from a DeviceNet device to a trunk cable or a drop cable
3.1.19
device type
identification of a collection of device-dependent information describing a viable combination
of options selected for all layers in the communication stack
3.1.20
dominant
one of two complementary logic levels on the physical signal
NOTE The dominant level is a logical "0".
3.1.21
duplicate MAC ID detection
DeviceNet-defined protocol that ensures no two nodes on the same link are assigned the
same MAC ID
3.1.22
explicit messaging
each explicit message commands the performance of a particular task and the return of the
results of the task performance to the requester
3.1.23
fragmentation
DeviceNet protocol provided by the connection object that defines a method by which data
greater than eight (8) bytes in length may be transmitted
3.1.24
group 2 client
unconnected message manager (UCMM)capable device that has gained ownership of the
predefined master/slave connection set within a server such that it may act as the client on
those connections
3.1.25
group 2 only client
device that is acting as a group 2 client to a group 2 only server

– 14 – 62026-3 © IEC:2008
NOTE The group 2 only client provides the UCMM functionality for group 2 only servers that it has allocated.
3.1.26
group 2 server
unconnected message manager (UCMM) capable device that has been configured to act as
the server for the predefined master/slave identifier connections
3.1.27
group 2 only server
slave device that is UCMM incapable and uses the predefined master/slave connection set to
establish communications
NOTE A group 2 only device can transmit and receive only those identifiers defined by the predefined
master/slave connection set.
3.1.28
I/O connection
connection between a producer and one or more consumers for the purpose of exchanging
application-specific, time-critical I/O data
3.1.29
I/O data
information which is transferred between I/O points and the controllers which use and set the
values
3.1.30
I/O messaging
exchange of data in a previously defined format
3.1.31
isolated device
device in which some of its components are not referenced to the V- of the physical layer, see
non-isolated device ( 3. 1.3 6 )
3.1.32
master
node which gathers and distributes I/O using the predefined master/slave connection set
3.1.33
Medium Access Control (MAC) ID
link address of a DeviceNet node
3.1.34
multicast connection
logical connection from one object to multiple other objects
NOTE A multicast connection allows data to be transferred in a single transaction from a producer to multiple
consumers sharing the same connection.
3.1.35
node
DeviceNet entity which is identified at the data link level by a unique MAC ID
NOTE Multiple DeviceNet nodes may be implemented in one device but they appear as logically distinct nodes on
the DeviceNet link.
3.1.36
non-isolated device
device in which all components are referenced to the V- of the physical layer, see isolated
device ( 3. 1. 3 1)
62026-3 © IEC:2008 – 15 –
3.1.37
object
1) abstract representation of a device’s capabilities
NOTE Objects may be composed of any or all of the following components:
a) Data (information which changes with time);
b) Configuration (parameters for behaviour);
c) Procedures(actions that may be performed using data and configuration).
2) collection of related data (in the form of variables) and procedures for operating on that
data
3.1.38
point-to-point connection
connection that exists between two objects only
NOTE Explicit messaging connections are always point-to-point. I/O connections may be either point-to-point or
multicast, see multicast connection ( 3. 1. 3 4).
3.1.39
predefined master/slave connection set
utilization of an explicit messaging connection to create and configure connection objects
within each connection end-point
NOTE Uses the general rules as a basis for the definition of a set of connections which facilitate communications
typically seen in a master/slave relationship.
3.1.40
producer
end point of a connection that is responsible for sending data
3.1.41
recessive
one of two complementary logic levels on the physical signal
NOTE The recessive level is a logical "1".
3.1.42
serial number
unique 32-bit integer assigned by each manufacturer to every DeviceNet device
NOTE The number is stored within the device as an attribute of the identity object and is unique with respect to
the manufacturer.
3.1.43
server
object which provides services to another (client) object, see client ( 3. 1. 1 0)
3.1.44
service
operation or function that an object performs upon request from another object
3.1.45
slave
node that returns data to its master using the predefined master/slave connection set and a
communication method set by the master
3.1.46
source MAC ID
MAC ID of a node that is transmitting a message

– 16 – 62026-3 © IEC:2008
3.1.47
trigger
service used by an application to initiate the production of data
3.1.48
UCMM capable device
device that supports the UCMM (see 3 . 1. 51 )
3.1.49
UCMM incapable device
device that does not support the UCMM (see 3. 1. 51)
3.1.50
unconnected explicit message
explicit message between nodes that have not yet established a connection between each
other
3.1.51
Unconnected Message Manager (UCMM)
function within a node that receives and processes unconnected explicit messages
3.1.52
Unsigned Short Integer (USINT)
8-bit integer
3.1.53
Unsigned Integer (UINT)
16-bit integer
3.2 Symbols and abbreviated terms
CAN Co
...