IEC 61158-3-12:2010

IEC 61158-3-12 ®
Edition 2.0 2010-07
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 3-12: Data-link layer service definition – Type 12 elements

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-3-12 ®
Edition 2.0 2010-07
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 3-12: Data-link layer service definition – Type 12 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
X
ICS 25.04.40; 35.100.20; 35.110 ISBN 978-2-88912-077-2
– 2 – 61158-3-12 © IEC:2010(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 Scope.7
1.1 Overview .7
1.2 Specifications .7
1.3 Conformance.7
2 Normative references.8
3 Terms, definitions, symbols, abbreviations and conventions .8
3.1 Reference model terms and definitions .8
3.2 Service convention terms and definitions .9
3.3 Data-link service terms and definitions.10
3.4 Symbols and abbreviations .13
3.5 Common conventions .14
4 Data-link layer services and concepts .15
4.1 Operating principle .15
4.2 Topology .16
4.3 Data-link layer overview.16
4.4 Error detection overview .17
4.5 Parameter and process data handling introduction .17
4.6 Node reference model .17
4.7 Operation overview.18
4.8 Addressing .20
4.9 Slave classification .22
4.10 Structure of the communication layer in the slave.22
5 Communication services .23
5.1 Overview .23
5.2 Read services.24
5.3 Write services .27
5.4 Combined read/write services .29
5.5 Network services .33
5.6 Mailbox.34
6 Local interactions.39
6.1 Read local .39
6.2 Write local .39
6.3 Event local.40

Figure 1 – Mapping of logical data in an Ethernet frame consisting of a single Type 12
DLPDU .16
Figure 2 – Type 12 data-link reference model .18
Figure 3 – Type 12 segments in open mode .19
Figure 4 – Type 12 segment in direct mode .19
Figure 5 – Addressing mode overview .20
Figure 6 – Fieldbus memory management unit overview .21
Figure 7 – Layering of communication .23
Figure 8 – Flow of Type 12 service primitives .24

61158-3-12 © IEC:2010(E) – 3 –
Figure 9 – Successful mailbox write sequence.35
Figure 10 – Successful mailbox read sequence .35

Table 1 – Auto-increment physical read (APRD) .24
Table 2 – Configured-addresse physical read (FPRD).25
Table 3 – Broadcast read (BRD).26
Table 4 – Logical read (LRD).26
Table 5 – Auto-increment physical write (APWR) .27
Table 6 – Configured-address physical write (FPWR) .27
Table 7 – Broadcast write (BWR) .28
Table 8 – Logical write (LWR) .29
Table 9 – Auto-increment physical read/write (APRW) .29
Table 10 – Configured-address physical read/write (FPRW).30
Table 11 – Broadcast read/write (BRW).31
Table 12 – Logical read/write (LRW).31
Table 13 – Auto-increment physical read / multiple write (ARMW).32
Table 14 – Configured-address physical read / multiple write (FRMW) .32
Table 15 – Provide network variable (PNV).33
Table 16 – Mailbox write.36
Table 17 – Mailbox read update.37
Table 18 – Mailbox read .38
Table 19 – Read local .39
Table 20 – Write local .39
Table 21 – Event local.40

– 4 – 61158-3-12 © IEC:2010(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-12: Data-link layer service definition –
Type 12 elements
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.
NOTE 1 Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all
cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits
a particular data-link layer protocol type to be used with physical layer and application layer protocols in type
combinations as specified explicitly in the profile parts. Use of the various protocol types in other combinations may
require permission of their respective intellectual-property-right holders.
International Standard IEC 61158-3-12 has been prepared by subcommittee 65C: Industrial
networks of IEC technical committee 65: Industrial-process measurement, control and
automation.
This second edition cancels and replaces the first edition published in 2007. This edition
constitutes a technical revision.
The main changes with respect to the previous edition are listed below:
• editorial improvements.
61158-3-12 © IEC:2010(E) – 5 –
The text of this standard is based on the following documents:
FDIS Report on voting
65C/604/FDIS 65C/618/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 ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.
The committee has decided that the contents of this publication will remain unchanged until the
stability 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.
NOTE 2 The revision of this standard will be synchronized with the other parts of the IEC 61158 series.

– 6 – 61158-3-12 © IEC:2010(E)
INTRODUCTION
This part of IEC 61158 is one of a series produced to facilitate the interconnection of
automation system components. It is related to other standards in the set as defined by the
“three-layer” fieldbus reference model described in IEC/TR 61158-1.
Throughout the set of fieldbus standards, the term “service” refers to the abstract capability
provided by one layer of the OSI Basic Reference Model to the layer immediately above. Thus,
the data-link layer service defined in this standard is a conceptual architectural service,
independent of administrative and implementation divisions.

61158-3-12 © IEC:2010(E) – 7 –
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-12: Data-link layer service definition –
Type 12 elements
1 Scope
1.1 Overview
This part of IEC 61158 provides common elements for basic time-critical messaging
communications between devices in an automation environment. The term “time-critical” is
used to represent the presence of a time-window, within which one or more specified actions
are required to be completed with some defined level of certainty. Failure to complete specified
actions within the time window risks failure of the applications requesting the actions, with
attendant risk to equipment, plant and possibly human life.
This standard defines in an abstract way the externally visible service provided by the Type 12
fieldbus data-link layer in terms of
a) the primitive actions and events of the service;
b) the parameters associated with each primitive action and event, and the form which they
take;
c) the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
• the Type 12 fieldbus application layer at the boundary between the application and data-link
layers of the fieldbus reference model;
• systems management at the boundary between the data-link layer and systems
management of the fieldbus reference model.
1.2 Specifications
The principal objective of this standard is to specify the characteristics of conceptual data-link
layer services suitable for time-critical communications, and thus supplement the OSI Basic
Reference Model in guiding the development of data-link protocols for time-critical
communications. A secondary objective is to provide migration paths from previously-existing
industrial communications protocols.
This specification may be used as the basis for formal DL-Programming-Interfaces.
Nevertheless, it is not a formal programming interface, and any such interface will need to
address implementation issues not covered by this specification, including
a) the sizes and octet ordering of various multi-octet service parameters, and
b) the correlation of paired request and confirm, or indication and response, primitives.
1.3 Conformance
This standard does not specify individual implementations or products, nor does it constrain the
implementations of data-link entities within industrial automation systems.
There is no conformance of equipment to this data-link layer service definition standard.
Instead, conformance is achieved through implementation of the corresponding data-link
protocol that fulfills the Type 12 data-link layer services defined in this standard.

– 8 – 61158-3-12 © IEC:2010(E)
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.
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 7498-3, Information technology – Open Systems Interconnection – Basic Reference
Model: Naming and addressing
ISO/IEC 8802-3, Information technology – Telecommunications and information exchange
between systems – Local and metropolitan area networks – Specific requirements – Part 3:
Carrier sense multiple access with collision detection (CSMA/CD) access method and physical
layer specifications
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
IEEE 802.1D, IEEE Standard for Local and metropolitan area networks – Media Access Control (MAC)
Bridges; available at
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations and
conventions apply.
3.1 Reference model terms and definitions
This standard is based in part on the concepts developed in ISO/IEC 7498-1 and
ISO/IEC 7498-3 and makes use of the following terms defined therein.
[7498-3]
3.1.1 DL-address
3.1.2 DL-connectionless-mode transmission [7498-1]
3.1.3 correspondent (N)-entities [7498-1]
correspondent DL-entities  (N=2)
correspondent Ph-entities  (N=1)
3.1.4 DL-duplex-transmission [7498-1]
[7498-1]
3.1.5 (N)-entity
DL-entity  (N=2)
Ph-entity  (N=1)
3.1.6 (N)-layer [7498-1]
DL-layer  (N=2)
Ph-layer  (N=1)
3.1.7 layer-management [7498-1]
3.1.8 peer-entities [7498-1]
3.1.9 primitive name [7498-3]
3.1.10 DL-protocol [7498-1]
3.1.11 DL-protocol-data-unit [7498-1]

61158-3-12 © IEC:2010(E) – 9 –
3.1.12 DL-relay [7498-1]
[7498-1]
3.1.13 reset
3.1.14 responding-DL-address [7498-3]
[7498-1]
3.1.15 routing
3.1.16 segmenting [7498-1]
[7498-1]
3.1.17 (N)-service
DL-service  (N=2)
Ph-service  (N=1)
3.1.18 (N)-service-access-point [7498-1]
DL-service-access-point  (N=2)
Ph-service-access-point  (N=1)
3.1.19 DL-service-data-unit [7498-1]
3.1.20 DL-simplex-transmission [7498-1]
3.1.21 DL-subsystem [7498-1]
3.1.22 systems-management [7498-1]
3.1.23 DLS-user [7498-1]
3.1.24 DLS-user-data [7498-1]
3.2 Service convention terms and definitions
This standard also makes use of the following terms defined in ISO/IEC 10731 as they apply to
the data-link layer:
3.2.1 acceptor
3.2.2 asymmetrical service
3.2.3 confirm (primitive);
requestor.deliver (primitive)
3.2.4 deliver (primitive)
3.2.5 DL-service-primitive;
primitive
3.2.6 DL-service-provider
3.2.7 DL-service-user
3.2.8 DL-user-optional-facility
3.2.9 indication (primitive);
acceptor.deliver (primitive)
3.2.10 request (primitive);
requestor.submit (primitive)
3.2.11 requestor
3.2.12 response (primitive);
acceptor.submit (primitive)
3.2.13 submit (primitive)
3.2.14 symmetrical service
– 10 – 61158-3-12 © IEC:2010(E)
3.3 Data-link service terms and definitions
3.3.1
application
function or data structure for which data is consumed or produced
3.3.2
application objects
multiple object classes that manage and provide a run time exchange of messages across the
network and within the network device
3.3.3
basic slave
slave device that supports only physical addressing of data
3.3.4
bit
unit of information consisting of a 1 or a 0. This is the smallest data unit that can be
transmitted
3.3.5
client
1) object which uses the services of another (server) object to perform a task
2) initiator of a message to which a server reacts
3.3.6
connection
logical binding between two application objects within the same or different devices
3.3.7
cyclic
events which repeat in a regular and repetitive manner
3.3.8
cyclic redundancy check (CRC)
residual value computed from an array of data and used as a representative signature for the
array
3.3.9
data
generic term used to refer to any information carried over a fieldbus
3.3.10
data consistency
means for coherent transmission and access of the input- or output-data object between and
within client and server
3.3.11
device
physical entity connected to the fieldbus composed of at least one communication element (the
network element) and which may have a control element and/or a final element (transducer,
actuator, etc.)
3.3.12
distributed clocks
method to synchronize slaves and maintain a global time base

61158-3-12 © IEC:2010(E) – 11 –
3.3.13
DL-segment, link, local link
single DL-subnetwork in which any of the connected DLEs may communicate directly, without
any intervening DL-relaying, whenever all of those DLEs that are participating in an instance of
communication are simultaneously attentive to the DL-subnetwork during the period(s) of
attempted communication
3.3.14
error
discrepancy between a computed, observed or measured value or condition and the specified
or theoretically correct value or condition
3.3.15
event
instance of a change of conditions
3.3.16
fieldbus memory management unit
function that establishes one or several correspondences between logical addresses and
physical memory
3.3.17
fieldbus memory management unit entity
single element of the fieldbus memory management unit: one correspondence between a
coherent logical address space and a coherent physical memory location
3.3.18
frame
denigrated synonym for DLPDU
3.3.19
full slave
slave device that supports both physical and logical addressing of data
3.3.20
interface
shared boundary between two functional units, defined by functional characteristics, signal
characteristics, or other characteristics as appropriate
3.3.21
master
device that controls the data transfer on the network and initiates the media access of the
slaves by sending messages and that constitutes the interface to the control system
3.3.22
mapping
correspondence between two objects in that way that one object is part of the other object
3.3.23
medium
cable, optical fibre, or other means by which communication signals are transmitted between
two or more points
NOTE "media" is used as the plural of medium.
3.3.24
message
ordered series of octets intended to convey information

– 12 – 61158-3-12 © IEC:2010(E)
NOTE Normally used to convey information between peers at the application layer.
3.3.25
network
set of nodes connected by some type of communication medium, including any intervening
repeaters, bridges, routers and lower-layer gateways
3.3.26
node
a) single DL-entity as it appears on one local link
b) end-point of a link in a network or a point at which two or more links meet [derived from
IEC 61158-2]
3.3.27
object
abstract representation of a particular component within a device
NOTE An object can be
a) an abstract representation of the capabilities of a device, composed of any or all of the following components:
1) data (information which changes with time);
2) configuration (parameters for behavior);
3) methods (things that can be done using data and configuration); or
b) a collection of related data (in the form of variables) and methods (procedures) for operating on that data that
have a clearly defined interface and behavior.
3.3.28
process data
data object containing application objects designated to be transferred cyclically or acyclically
for the purpose of processing
3.3.29
receiving DLS-user
DL-service user that acts as a recipient of DL-user-data
NOTE A DL-service user can be concurrently both a sending and receiving DLS-user.
3.3.30
sending DLS-user
DL-service user that acts as a source of DL-user-data
3.3.31
server
object which provides services to another (client) object
3.3.32
service
operation or function than an object and/or object class performs upon request from another
object and/or object class
3.3.33
slave
DL-entity accessing the medium only after being initiated by the preceding slave or the master
3.3.34
Sync manager
collection of control elements to coordinate access to concurrently used objects.

61158-3-12 © IEC:2010(E) – 13 –
3.3.35
Sync manager channel
single control elements to coordinate access to concurrently used objects.
3.3.36
switch
MAC bridge as defined in IEEE 802.1D
3.4 Symbols and abbreviations
APRD Auto-increment physical read
APRW Auto-increment physical read/write
Auto-increment physical write
APWR
ARMW Auto-increment physical read / multiple write
BRD Broadcast read
BRW Broadcast read/write
BWR Broadcast write
Controller area network
CAN
CoE CAN application protocol over Type 12 services
CSMA/CD Carrier sense multiple access with collision detection
DC Distributed clocks
DL- Data-link layer (as a prefix)
DL-connection
DLC
DLCEP DL-connection-end-point
DLE DL-entity (the local active instance of the data-link layer)
DLL DL-layer
DLPCI DL-protocol-control-information
DL-protocol-data-unit
DLPDU
DLM DL-management
DLME DL-management entity (the local active instance of DL-management)
DLMS DL-management service
DLS DL-service
DL-service-access-point
DLSAP
DLSDU DL-service-data-unit
E²PROM Electrically erasable programmable read only memory
EoE Ethernet tunneled over Type 12 services
ESC Type 12 slave controller
Frame check sequence
FCS
FIFO First-in first-out (queuing method)
FMMU Fieldbus memory management unit
FoE File access with Type 12 services
FPRD Configured address physical read
Configured address physical read/write
FPRW
FPWR Configured address physical write
FRMW Configured address physical read/multiple write
HDR Header
ID Identifier
– 14 – 61158-3-12 © IEC:2010(E)
IP Internet protocol
LAN Local area network
LRD Logical memory read
LRW Logical memory read/write
Logical memory write
LWR
MAC Medium access control
MDI Media-dependent interface (specified in ISO/IEC 8802-3)
MDX Mailbox data exchange
MII Media-independent interface (specified in ISO/IEC 8802-3)
Physical device interface (a set of elements that allows access to DL-services from the
PDI
PDO Process data object
Ph- Physical layer (as a prefix)
PhE Ph-entity (the local active instance of the physical layer)
PhL Ph-layer
Physical layer device (specified in ISO/IEC 8802-3)
PHY
PNV Publish network variable
OSI Open systems interconnection
QoS Quality of service
RAM Random access memory
Receive
Rx
SDO Service data object
SII Slave information interface
SyncM Synchronization manager
TCP Transmission control protocol
Transmit
Tx
UDP User datagram protocol
WKC Working counter
3.5 Common conventions
This standard uses the descriptive conventions given in ISO/IEC 10731.
The service model, service primitives, and time-sequence diagrams used are entirely abstract
descriptions; they do not represent a specification for implementation.
Service primitives, used to represent service user/service provider interactions (see
ISO/IEC 10731), convey parameters that indicate information available in the user/provider
interaction.
This standard uses a tabular format to describe the component parameters of the DLS
primitives. The parameters that apply to each group of DLS primitives are set out in tables
throughout the remainder of this standard. Each table consists of up to six columns, containing
the name of the service parameter, and a column each for those primitives and parameter-
transfer directions used by the DLS:
– the request primitive’s input parameters;
– the indication primitive’s output parameters;
– the response primitive’s input parameters; and
– the confirm primitive’s output parameters.

61158-3-12 © IEC:2010(E) – 15 –
NOTE The request, indication, response and confirm primitives are also known as requestor.submit,
acceptor.deliver, acceptor.submit, and requestor.deliver primitives, respectively (see ISO/IEC 10731).
One parameter (or part of it) is listed in each row of each table. Under the appropriate service
primitive columns, a code is used to specify the type of usage of the parameter on the primitive
and parameter direction specified in the column:
M parameter is mandatory for the primitive.
U parameter is a User option, and may or may not be provided depending on
the dynamic usage of the DLS-user. When not provided, a default value for
the parameter is assumed.
C parameter is conditional upon other parameters or upon the environment of
the DLS-user.
(blank) parameter is never present.
Some entries are further qualified by items in brackets. These may be a parameter-specific
constraint:
(=) indicates that the parameter is semantically equivalent to the parameter in the
service primitive to its immediate left in the table.
In any particular interface, not all parameters need be explicitly stated. Some may be implicitly
associated with the primitive.
In the diagrams which illustrate these interfaces, dashed lines indicate cause-and-effect or
time-sequence relationships, and wavy lines indicate that events are roughly
contemporaneous.
4 Data-link layer services and concepts
4.1 Operating principle
This standard describes a real-time Ethernet technology that aims to maximize the utilization of
the full duplex Ethernet bandwidth. Medium access control employs the master/slave principle,
where the master node (typically the control system) sends the Ethernet frames to the slave
nodes, which extract data from and insert data into these frames.
From an Ethernet point of view, a Type 12 segment is a single Ethernet device which receives
and sends standard ISO/IEC 8802-3 Ethernet frames. However, this Ethernet device is not
limited to a single Ethernet controller with downstream microprocessor, but may consist of a
large number of Type 12 slave devices. These process the incoming Ethernet frames while
they are in transit within the device, reading data from the Ethernet frame and/or inserting their
own data into the frame before transferring the frame to the next slave device. The last slave
device within the segment sends the fully processed Ethernet frame back in the reverse
direction through the chain of devices, returning the collected information through the first
slave device to the master, which receives it as an Ethernet response frame.
This procedure utilizes the full duplex capability of Ethernet: both communication directions are
operated independently with reading and writing by the slaves on the outbound path and only
transmission-to-reception timing measurements on the inbound path as the Ethernet frame
retraverses each intermediate slave device.
Full-duplex communication between a master device and a Type 12 segment consisting of one
or several slave devices may be established without using a switch.

– 16 – 61158-3-12 © IEC:2010(E)
4.2 Topology
The topology of a communication system is one of the crucial factors for the successful
application in automation. The topology has significant influence on the cabling effort,
diagnostic features, redundancy options and hot-plug-and-play features.
The star topology commonly used for Ethernet can lead to increased cabling effort and
infrastructure cost. Particularly for automation applications, a line or tree topology often is
preferable.
The slave node arrangement represents an open-loop bus. At the open end, the master device
sends frames, either directly or via Ethernet switches; it receives them at the other end after
they have been processed by each intervening device. Each Ethernet frame is relayed from the
first node to the next one, and thence to each other node in series. The last node returns the
Ethernet frame back to the master using the full duplex capabilities of Ethernet. The resulting
topology is a physical line.
Branches, which in principle are possible anywhere, can be used to enhance the line structure
into a tree structure form. A tree structure supports very simple wiring; individual branches, for
example, can branch into control cabinets or machine modules, while the main line runs from
one module to the next. Branches are possible if a device has more than two ports. This
standard allows up to two branching links in addition to the basic set of two series interfaces.
An Ethernet frame received on port n (n not zero) is forwarded to port n+1. If there is no port
n+1 the Ethernet frame is forwarded to port 0. If no device is connected or the port is closed by
the master, a request to send to that port will be processed as if the same data are received by
this port (i.e. loop is closed).
4.3 Data-link layer overview
A single Ethernet frame can carry several Type 12 DLPDUs, which are blocked into the
Ethernet frame without gaps. Several nodes can be addressed individually by these DLPDUs.
The Ethernet frame is terminated with the last Type 12 DLPDU, except when the frame size is
less than 64 octets, in which case the Ethernet frame is padded to 64 octets.
This blocking leads to better utilization of the Ethernet bandwidth than would separate Ethernet
frames to and from each slave node. However, for e.g. a 2-channel digital input node with just
two bits of user data, the overhead of a single Type 12 DLPDU can still be excessive.
Therefore slave nodes may also support logical address mapping. The process data can be
inserted anywhere within a logical address space. If a Type 12 DLPDU is sent that contains
read or write services for a certain process image area located at the corresponding logical
address, instead of addressing a particular node, the nodes insert the data at or extract the
data from their appropriate place(s) within the process data, as noted in Figure 1.
Frame Type12
WKC
Ethernet HDR Process data FCS
HDR HDR
Figure 1 – Mapping of logical data in an Ethernet frame
consisting of a single Type 12 DLPDU

61158-3-12 © IEC:2010(E) – 17 –
Each node that detects an address match with the process image inserts its data, so that many
nodes can be addressed simultaneously with a single Type 12 DLPDU. The master can
assemble a completely sorted logical process image via a single Type 12 DLPDU, independent
of the physical wiring order of the slave devices.
Additional mapping is no longer required in the master, so that the process data can be
transferred directly to one or more different control tasks. Each task can create its own process
image and exchange it within its own timeframe. The physical order of the nodes is completely
arbitrary and is only relevant during the first initialization phase.
The logical address space is 2 octets (= 4 GB). Thus a Type 12 fieldbus can be considered to
be a serial backplane for automation systems that enables connection to distributed process
data for both large and very small automation devices. Using a standard Ethernet controller
and standard Ethernet cables, a very large number of I/O channels can be connected to
automation devices so that they can be accessed with high bandwidth, minimum delay and a
near-optimum effective usable data rate. At the same time, devices such as fieldbus scanners
can be connected as well, thus preserving existing technologies and standards.
4.4 Error detection overview
Type 12 master and slave nodes (DLEs) check the Ethernet frame check sequence (FCS) to
determine whether a frame is received correctly. Since one or several slaves may modify the
frame during the transfer, the FCS is checked by each node on reception and recalculated
during retransmission. If a slave detects a checksum error, the slave does not repair the FCS
but flags the master by incrementing an error counter, so that the source of a single fault can
be located precisely within the open-loop topology.
When reading data from or writing data to a Type 12 DLPDU, the addressed slave increments
a working counter (WKC) positioned at the end of the DLPDU. Slaves which are merely
forwarding the DLPDU, but not extracting information from it or inserting information within it,
do not modify the counter. By comparing the working counter with the expected number of
accessing slave nodes, a master can check whether the expected number of nodes have
processed the corresponding DLPDU.
4.5 Parameter and process data handling introduction
Industrial communication systems need to meet different requirements in terms of their data
transmission characteristics. Parameter data can be transferred acyclically and in large
quantities, usually in situations where the timing requirements are relatively non-critical and the
transmission is triggered by the control system. Diagnostic data is also transferred acyclically
in an event-driven mode, but the timing requirements are more demanding and the
transmission is usually triggered by a peripheral device.
Process data, on the other hand, is typically transferred cyclically with different cycle times.
The timing requirements are most stringent for process data communication. This international
standard supports a variety of services and protocols to meet these differing requirements.
4.6 Node reference model
4.6.1 Mapping onto OSI Basic Reference Model
Type 12 services are described using the principles, methodology and model of
ISO/IEC 7498-1 (OSI). The OSI model provides a layered approach to communications
standards, whereby the layers can be developed and modified independently. The Type 12
specification defines functionality from top to bottom of a full OSI communications stack.
Functions of the intermediate OSI layers, layers 3–6, are consolidated into either the Type 12
data-link layer or the DL-user of the Type 12 data-link layer. The Type 12 data-link reference
Figure 2.
model is shown in
– 18 – 61158-3-12 © IEC:2010(E)
HTTP,
Files
FTP, …
Application
DLS-user
CANopen over EtherCAT
TCP UDP
File
Object Dictionary
Access
IP
over
EtherCAT
Ethernet
SDO PDO Mapping
over EtherCAT
control/ Sync
Mailbox Process data
status settings
FMMU
SyncM FMMU
DLL
FMMU
FMMU n
SyncM SyncM
DLL Slave Layer
SyncM
info address Management
DL control/
DL status
Data-link layer
Physical layer
Figure 2 – Type 12 data-link reference model
4.6.2 Data-link layer features
The data-link layer provides basic time-critical support for data communications among devices
connected. The term “time-critical” is used to describe applications having a time window,
within which one or more specified actions are required to be completed with some defined
level of certainty. Failure to complete specified actions within the time window risks failure of
the applications requesting the actions, with attendant risk to equipment, plant and possibly
human life.
The data-link layer has the task to compute, compare and generate the frame-check sequence
and provide communications by extracting data from and/or including data into the Ethernet
frame. This is done depending on the data-link layer parameters which are stored at pre-
defined memory locations. The data is made available to the DL-user in physical memory,
either in a mailbox configuration or within the process data section.
4.7 Operation overview
4.7.1 Relation to ISO/IEC 8802-3
This part specifies data-link layer services in addition to those specified in ISO/IEC 8802-3.
4.7.2 Type 12 modes
4.7.2.1 Open mode
In the open mode, one or several Type 12 segments may be connected to a standard switching
device as shown in Figure 3. The first slave device within a Type 12 segment then has an
ISO/IEC 8802-3 MAC address representing the entire segment. This segment address slave
device replace destination address field with the source address field and source address field
with its own MAC address within the Ethernet frame if t
...