IEC 61158-3-24:2014
(Main)Industrial communication networks - Fieldbus specifications - Part 3-24: Data-link layer service definition - Type 24 elements
Industrial communication networks - Fieldbus specifications - Part 3-24: Data-link layer service definition - Type 24 elements
IEC 61158-3-24:2014 defines the services provided to the Type 24 fieldbus application layer at the boundary between the application and data-link layers of the fieldbus reference model and systems management at the boundary between the data-link layer and systems management of the fieldbus reference model.
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 3-24: Définition des services de la couche liaison de données - Eléments de type 24
L'IEC 61158-3-24:2014 définit les services fournis à la couche application de bus de terrain Type 24 au niveau de la frontière entre les couches application et liaison de données du modèle de référence de bus de terrain et à la gestion des systèmes au niveau de la frontière entre la couche liaison de données et la gestion des systèmes selon le modèle de référence de bus de terrain.
General Information
Relations
Standards Content (Sample)
IEC 61158-3-24 ®
Edition 1.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Industrial communication networks – Fieldbus specifications –
Part 3-24: Data-link layer service definition – Type-24 elements
Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 3-24: Définition des services de la couche liaison de données – Éléments
de type 24
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 l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC 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 l'IEC de votre pays de résidence.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland 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.
IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.
IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,
77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) 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 IEC
Le contenu technique des publications IEC 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 IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient plus de 30 000 termes et définitions en
Spécifications techniques, Rapports techniques et autres
anglais et en français, ainsi que les termes équivalents dans
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
14 langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.
Recherche de publications IEC - www.iec.ch/searchpub
Glossaire IEC - std.iec.ch/glossary
Plus de 55 000 entrées terminologiques électrotechniques, en
La recherche avancée permet de trouver des publications IEC
en utilisant différents critères (numéro de référence, texte, anglais et en français, extraites des articles Termes et
comité d’études,…). Elle donne aussi des informations sur les Définitions des publications IEC parues depuis 2002. Plus
projets et les publications remplacées ou retirées. certaines entrées antérieures extraites des publications des
CE 37, 77, 86 et CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished
Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just
Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur cette
Disponible en ligne et aussi une fois par mois par email. publication ou si vous avez des questions contactez-nous:
csc@iec.ch.
IEC 61158-3-24 ®
Edition 1.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Industrial communication networks – Fieldbus specifications –
Part 3-24: Data-link layer service definition – Type-24 elements
Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 3-24: Définition des services de la couche liaison de données – Éléments
de type 24
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX W
ICS 25.040.40; 35.100.20; 35.110 ISBN 978-2-8322-1710-8
– 2 – IEC 61158-3-24:2014 © IEC 2014
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
1.1 General . 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 Additional Type 24 data-link specific definitions . 9
3.4 Common symbols and abbreviations . 12
3.5 Additional type 24 symbols and abbreviations . 12
3.6 Common conventions . 13
3.7 Additional Type 24 conventions . 14
4 Data-link service and concepts . 14
4.1 Overview . 14
4.2 DLS-user services . 15
4.3 Overview of interactions . 16
4.4 Detailed specification of services and interactions . 18
5 DL-management service . 22
5.1 Overview . 22
5.2 Overview of interactions . 23
5.3 Detailed specification of services and interactions . 25
Bibliography . 37
Figure 1 – Sequence of primitive for set data and read data service . 17
Figure 2 – Sequence of primitive for send data with acknowledge service . 17
Figure 3 – Sequence of primitive for send data with no-acknowledge service . 18
Figure 4 – Sequence of primitives for event service . 18
Figure 5 – Sequence of primitives for Reset service . 24
Figure 6 – Sequence of primitives for Set/get value service . 24
Figure 7 – Sequence of primitives for Evaluate delay service . 24
Figure 8 – Sequence of primitives for Start communication service . 25
Figure 9 – Sequence of primitives for Event and Clear error status service . 25
Table 1 – The list of DLS service primitives and parameters . 16
Table 2 – Write data primitives and parameters . 18
Table 3 – Values of result for write data service . 19
Table 4 – Read data primitives and parameters . 19
Table 5 – Values of result for read data service . 19
Table 6 – SDA primitives and parameters . 20
Table 7 – Values of result for SDA service . 20
Table 8 – SDN primitives and parameters . 21
Table 9 – Values of result for SDN service . 21
Table 10 – Event primitives and parameters . 22
Table 11 – Values of Event_ID for event service . 22
Table 12 – The list of DLMS service primitives and parameters . 23
Table 13 – Set value primitive and parameters . 26
Table 14 – The list of parameter Var_ID of Set value request . 26
Table 15 – Data type and range of variables . 26
Table 16 – List of the values of variable Cyc_sel . 27
Table 17 – List of the values of variable Tunit . 28
Table 18 – Structure example of the each element of variable IO_Map . 28
Table 19 – Data type and range of the each element . 29
Table 20 – Values of result for Set value service . 29
Table 21 – Get value primitive and parameters . 29
Table 22 –The list of parameter Var_ID of Get value request . 30
Table 23 – Data type and range of variables . 30
Table 24 – Error factor assign . 31
Table 25 – Values of result for Get value service . 31
Table 26 – Evaluate delay primitive and parameters . 32
Table 27 – Values of result for Set value service . 32
Table 28 – Set communication mode primitives and parameters . 33
Table 29 – Range of Tunit . 34
Table 30 – Values of result for set communication mode service. 34
Table 31 – Start communication service primitives and parameter . 34
Table 32 – Values of result for start communication service . 34
Table 33 – Clear error primitive and parameters . 35
Table 34 – Values of result for clear error service . 35
Table 35 – DLM error event primitive and parameters . 36
Table 36 – Value and definition of Err_Event_ID . 36
– 4 – IEC 61158-3-24:2014 © IEC 2014
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-24: Data-link layer service definition –
Type-24 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.
Attention is drawn to the fact that the use of the associated protocol type is restricted by its
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 layer protocol type to
be used with other layer protocols of the same type, or in other type combinations explicitly
authorized by its intellectual-property-right holders.
NOTE Combinations of protocol types are specified in IEC 61784-1 and IEC 61784-2.
International Standard IEC 61158-3-24 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/759/FDIS 65C/769/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 the parts of the IEC 61158 series, 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.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – IEC 61158-3-24:2014 © IEC 2014
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 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.
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-24: Data-link layer service definition –
Type-24 elements
1 Scope
1.1 General
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
24 fieldbus data-link layer in terms of
a) the primitive actions and events of the service;
b) the interrelationship between these actions and events, and their valid sequences;
c) the parameters associated with each primitive action and event, and the form which they
take.
The purpose of this standard is to define the services provided to
– the Type 24 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 24 data-link layer services defined in this standard.
– 8 – IEC 61158-3-24:2014 © IEC 2014
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
NOTE All parts of the IEC 61158 series, as well as IEC 61784-1 and IEC 61784-2 are maintained simultaneously.
Cross-references to these documents within the text therefore refer to the editions as dated in this list of normative
references.
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 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
ISO/IEC 19501:2005, Information technology – Open Distributed Processing – Unified
Modeling Language (UML) Version 1.4.2
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.
3.1.1 acknowledgement [ISO/IEC 7498-1]
3.1.2 correspondent (N)-entities [ISO/IEC 7498-1]
correspondent DL-entities (N=2)
correspondent Ph-entities (N=1)
3.1.3 DL-address [ISO/IEC 7498-3]
3.1.4 DL-protocol [ISO/IEC 7498-1]
3.1.5 DL-protocol-data-unit [ISO/IEC 7498-1]
3.1.6 DL-service-data-unit [ISO/IEC 7498-1]
3.1.7 DLS-user [ISO/IEC 7498-1]
3.1.8 DLS-user-data [ISO/IEC 7498-1]
3.1.9 event [ISO/IEC 19501]
3.1.10 layer-management [ISO/IEC 7498-1]
3.1.11 rimitive name [ISO/IEC 7498-1]
3.1.12 reset [ISO/IEC 7498-1]
3.1.13 segmenting [ISO/IEC 7498-1]
3.1.14 state [ISO/IEC 19501]
3.1.15 state machine [ISO/IEC 19501]
3.1.16 systems-management [ISO/IEC 7498-1]
3.1.17 transition [ISO/IEC 19501]
3.1.18 (N)-entity [ISO/IEC 7498-1]
DL-entity(N=2)
Ph-entity (N=1)
3.1.19 (N)-layer [ISO/IEC 7498-1]
DL-layer (N=2)
Ph-layer (N=1)
3.1.20 (N)-service [ISO/IEC 7498-1]
DL-service (N=2)
Ph-service (N=1)
3.1.21 (N)-service-access-point [ISO/IEC 7498-1]
DL-service-access-point (N=2)
Ph-service-access-point (N=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 confirm (primitive)
3.2.2 DL-service-primitive;
primitive
3.2.3 DL-service-provider
3.2.4 DL-service-user
3.2.5 indication (primitive)
3.2.6 request (primitive)
3.2.7 requestor
3.2.8 response (primitive)
3.3 Additional Type 24 data-link specific definitions
For the purposes of this standard, the following terms and definitions apply.
3.3.1
acknowledge
acknowledgement
3.3.2
acyclic transmission
non-periodic exchange of telegrams
3.3.3
C1 master
one of the station type that initiates and control cyclic transmission
– 10 – IEC 61158-3-24:2014 © IEC 2014
3.3.4
C1 message
message communication that C1 master operates as initiator to exchange messages with
slave or C2 master
3.3.5
C2 master
one of the station type that has the function of monitoring all process data transmitted through
the network and may initiates message communication
3.3.6
C2 message
message communication that C2 master operates as initiator to exchange messages with
slave or C1 master
3.3.7
cyclic transmission
periodic exchange of telegrams
3.3.8
data
generic term used to refer to any information carried over a fieldbus
3.3.9
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.10
event driven mode
transmission mode for the application layer protocol of the communication type 24 in which a
transaction of command-response-exchanging arises as user’s demands
3.3.11
frame
synonym for DLPDU
3.3.12
initiator
station that initiates the exchange of process data or message
3.3.13
interface
shared boundary between two functional units, defined by functional characteristics, signal
characteristics, or other characteristics as appropriate
3.3.14
input data
process data sent by the slave and received by the C1 master
3.3.15
message
ordered series of octets intended to convey information
Note 1 to entry: Normally used to convey information between peers at the application layer.
3.3.16
monitor slave
slave that has the function of monitoring all process data transmitted through the network
3.3.17
network
set of nodes connected by some type of communication medium, including any intervening
repeaters, bridges, routers and lower-layer gateways
3.3.18
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
3.3.19
output data
process data sent by the C1 master and received by the slaves
3.3.20
protocol
convention about the data formats, time sequences, and error correction in the data exchange
of communication systems
3.3.21
real-time communication
transfer of data in real-time
3.3.22
receiving DLS-user
DL-service user that acts as a recipient of DL-user-data
Note 1 to entry: A DL-service user may be concurrently both a sending and receiving DLS-user.
3.3.23
responder
station that responds process data or message after it has been initiated by initiator
3.3.24
send data with acknowledge
data transfer service with acknowledge of reception from corresponding DLE
3.3.25
send data with no-acknowledge
data transfer service without acknowledge of reception from corresponding DLE
3.3.26
slave
one of the station type that accesses the medium only after it has been initiated by C1-Maser
or C2 Master
3.3.27
sending DLS-user
DL-service user that acts as a source of DL-user-data
3.3.28
station
node
– 12 – IEC 61158-3-24:2014 © IEC 2014
3.3.29
topology
physical network architecture with respect to the connection between the stations of the
communication system
3.3.30
transmission cycle
fixed time period of cyclic transmission
3.3.31
time slot
time period reserved so that initiator and responder may exchange one frame respectively
3.4 Common symbols and abbreviations
Destination address
DA
3.4.1
Data-link layer (as a prefix)
DL-
3.4.2
DL-entity (the local active instance of the data-link layer)
DLE
3.4.3
DL-layer
DLL
3.4.4
DL-management
DLM
3.4.5
DL-management service
DLMS
3.4.6
DL-protocol-data-unit
DLPDU
3.4.7
DL-service
DLS
3.4.8
DL-service-access-point
DLSAP
3.4.9
DL-service-data-unit
DLSDU
3.4.10
First-in first-out (queuing method)
FIFO
3.4.11
Identifier
ID
3.4.12
Open systems interconnection
OSI
3.4.13
Protocol data unit
PDU
3.4.14
Physical layer (as a prefix)
Ph-
3.4.15
Ph-entity (the local active instance of the physical layer)
PhE
3.4.16
Ph-layer
PhL
3.4.17
Physical layer device (specified in ISO/IEC 8802-3)
PHY
3.4.18
Quality of service
QoS
3.4.19
Real-time
RT
3.4.20
Service access point
SAP
3.4.21
Service data unit
SDU
3.4.22
3.5 Additional type 24 symbols and abbreviations
Acknowledge
ACK
3.5.1
C1 message
C1MSG
3.5.2
C2 message
C2MSG
3.5.3
Input and/or output
I/O
3.5.4
Message
MSG
3.5.5
Receive
Rx
3.5.6
Send data with acknowledge
SDA
3.5.7
Send data with no-acknowledge
SDN
3.5.8
State machine
SM
3.5.9
Transmission cycle
Tcycle
3.5.10
Time slot
Tslot
3.5.11
Transmit
Tx
3.5.12
3.6 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.
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.
– 14 – IEC 61158-3-24:2014 © IEC 2014
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 to 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.
3.7 Additional Type 24 conventions
The following notation, a shortened form of the primitive classes defined in 3.2, is used in the
figures.
req request primitive
ind indication primitive
cnf confirm primitive (confirmation)
4 Data-link service and concepts
4.1 Overview
The services provided by this interface are used to utilize the following functions which are
required in factory automation system, especially in motion control system.
• Exchange I/O data between the controller and the device.
• Transfer message between the controller and the device, or between the equipments
for engineering and them.
• Exactly synchronize the controller with the device.
This interface provides the data exchange service for the above usage. For the data
exchange, this service classifies the stations into three types of C1 master, C2 master and
slave. The data exchange is executed between one master station (C1 master or C2 master)
and N slave stations. There are two types of transmission modes, cyclic transmission and
acyclic transmission.
In cyclic transmission mode, transmission is executed cyclically with an accurate period. The
transmission cycle is set by the C1 master and slave and C2 master follow it. The
transmission cycle has I/O data exchange band to transmit process data and message
communication band to transmit message. In I/O data exchange band, C1 master transmits
output data to all slaves and the slaves transmit input data to C1 master. This transmission is
executed once to each slave, to provide real-time transmission service to DLS-user. In
message communication band, transmission is executed only when DLS-user requests.
The DLE in C1 master controls transmission sequence in cyclic transmission mode. The time
period for a master station to exchange with one slave station is called time slot. There are
two types of communication sequence, one is “fixed-width time slot type” whose time slot
width is same for all stations and the other is “configurable time slot type” whose time slot can
be defined for each station. All stations shall use the same-data-length frame when the DLE
adopts fixed-width time slot type. The width of the time slot is static in both type, and it is set
by DL-management during initialization. Once cyclic communication starts, it shall not be
changed.
Acyclic transmission mode is used by DLS-user that operates in event driven mode. In acyclic
transmission mode, transmissions are executed sporadically. The same transmission
sequence and message communication may be executed in acyclic transmission, as in cyclic
transmission mode without fixing the transmission cycle. Though C2 message communication
is also possible, the DLS-user shall execute the arbitration of the transmission timing. In
acyclic transmission mode, the data length is fixed at 64 octets.
In acyclic transmission mode, slaves execute processing of the output data sent by the
master and processing of the data to send the input data at its own timing. (Slaves do not
operate simultaneously.)
This interface provides the maintenance service besides the transmission of data. The
maintenance service is described in the next clause.
4.2 DLS-user services
4.2.1 General
This clause describes notional model for data transfer service between DLE and DLS user.
Information is exchanged by DLS primitives and related parameters between DLE and DLS
user. The following services are provided to DLS user.
– Write data
– Read data
– Send data with acknowledge service (SDA)
– Send data with no-acknowledge service (SDN)
– Cyclic event
– Get Status
4.2.2 Write data
This service is used to transmit process data. This service is available in cyclic transmission
mode. This service transfers DLSDU that contains process data to DLE. The DLE stores the
passed DLSDU within the DLE itself and transmits at the scheduled timing. The previous
DLSDU will be overwritten by new DLSDU when the DLS-user issues a new request to the
identical SAP before the DLE transmits the previous DLSDU.
4.2.3 Read data
This service is used to receive process data. This service is available in cyclic transmission
mode. This service retrieves the DLSDU that DLE has been received during I/O data
exchange. DLE stores the DLSDU that has been assembled from received DLPDU into the
DLE itself. DLE has an independent storage area of DLSDU of each SAP. And it holds only
the newest DLSDU. DLSDU will be overwritten by new DLSDU when the DLE assembles a
new DLSDU from a newly received DLPDU before the DLS-user issues this service request.
4.2.4 Send data with acknowledge service (SDA)
This service is used for message communication in cyclic transmission mode. This service
permits the local DLS-user to send a DLSDU to a single remote station. The DLSDU is
delivered to remote DLS-user by the remote DLE. If the size of the DLSDU is too large to
transfer with one DLPDU, local DLE divides the DLSDU before transmitting it, and then
remote DLE will assemble them into the original DLSDU.
– 16 – IEC 61158-3-24:2014 © IEC 2014
Remote DLE returns acknowledge to the local station to notify of the receipt status of the
each DLPDU. If an error occurred during the transmission, the local DLE repeats to transmit
the DLPDU. The local DLS-user receives a confirmation concerning the receipt or non-receipt
of the DLSDU by the remote DLE.
4.2.5 Send data with no-acknowledge service (SDN)
This service is used for both I/O data exchange and message communication in acyclic
transmission mode. This service permits a local DLS-user to transfer a DLSDU to a single
remote station (unicast), or to all other remote stations (broadcast) at the same time. In this
service, DLE does not operate segmentation of the DLSDU passed by DLS user. Confirmation
of this service is issued by local DLE, therefore it does not include any information indicating
whether remote DLE has received the DLSDU requested by DLS user or not.
4.2.6 Event
DLS primitive employs this service to inform the DLS-user about certain events in the DLL.
4.2.7 Get status
This service permits the local DLS-user to read current status of the local DLE.
4.3 Overview of interactions
Table 1 shows the list of service primitives and parameters for DLS-user.
Table 1 – The list of DLS service primitives and parameters
Service primitive Parameter function
Request for writing send
Set data DL-WRITE-DATA.req SAP_ID, DLSDU data
DL-WRITE-DATA.cnf Result
Request for reading
Read data DL-READ-DATA.req SAP_ID received data
DL-READ-DATA.cnf Result, DLSDU
Request for sending
DL-SDA.req SAP_ID, Node_ID, Length, DLSDU message
Send data with
acknowledge
DL-SDA.cnf Result
service
DL-SDA.ind SAP_ID, Node_ID, Length, DLSDU
Request for asynchronous
DL-SDN.req SAP_ID, Node_ID, Length, DLSDU communication
Send data with no-
acknowledge
DL-SDN.cnf Result
service
DL-SDN.ind SAP_ID, Node_ID, Length, DLSDU
Cyclic Event DL-EVENT.ind Event_ID Event notification
The sequences of primitives are shown in Figure 1 to Figure 4.
DLS-user DLE DLE DLS-user DLE DLS-user
(C1-Master) （Slave#1) （Slave#n)
DL-WRITE-DATA.req DL-WRITE-DATA.req DL-WRITE-DATA.req
（SAP_ID, DLSDU) （SAP_ID, DLSDU) （SAP_ID, DLSDU)
DL-WRITE-DATA.cnf
DL-WRITE-DATA.cnf DL-WRITE-DATA.cnf
（Result) （Result) （Result)
DL-EVENT.ind
（Event_ID)
（DLPDU #1)
（DLPDU #1)
・
・
・
（DLPDU #n)
（DLPDU #n)
DL-EVENT.ind DL-EVENT.ind
DL-EVENT.ind
（Event_ID) （Event_ID)
（Event_ID)
DL-READ-DATA.req DL-READ-DATA.req
DL-READ-DATA.req
（SAP_ID) （SAP_ID)
（SAP_ID)
DL-READ-DATA.cnf DL-READ-DATA.cnf
DL-READ-DATA.cnf
（Result, DLSDU) （Result, DLSDU)
（Result, DLSDU)
DL-WRITE-DATA.req DL-WRITE-DATA.req
DL-WRITE-DATA.req
（SAP_ID, DLSDU) （SAP_ID, DLSDU)
（SAP_ID, DLSDU)
DL-WRITE-DATA.cnf DL-WRITE-DATA.cnf
DL-WRITE-DATA.cnf
（Result) （Result)
（Result)
Figure 1 – Sequence of primitive for set data and read data service
DLS-user DLE DLE DLS-user
(Sender) (Receiver)
（DLPDU segment #1)
DL-SDA.req
（SAP_ID, Node_ID, Length, DLSDU)
・
・
・
（DLPDU segment #n)
DL-SDA.ind
（SAP_ID, Node_ID, Length, DLSDU)
DL-SDA.cnf
（Result)
Figure 2 – Sequence of primitive for send data with acknowledge service
– 18 – IEC 61158-3-24:2014 © IEC 2014
DLS-user DLE DLE DLS-user
(Sender) (Receiver)
（DLPDU)
DL-SDN.req
DL-SDN.ind
（SAP_ID, Node_ID, Length, DLSDU)
DL-SDN.cnf
（Result)
Figure 3 – Sequence of primitive for send data with no-acknowledge service
DLS-User DLE
DL-EVENT.ind
（Event_ID)
Figure 4 – Sequence of primitives for event service
4.4 Detailed specification of services and interactions
4.4.1 Write data
4.4.1.1 Function
The DLS-user uses this service to write the data directly to the internal buffer of DLE. The
service is locally processed after the DL-WRITE-DATA request primitive has arrived. The DLE
communicates the successful processing of the service to the DLS-user by means of a DL-
WRITE-DATA confirmation primitive (immediate confirmation).
4.4.1.2 Type of parameters
4.4.1.2.1 General
Table 2 indicates the primitives and parameters of write data service. Details of these
parameters are shown in the following sections.
Table 2 – Write data primitives and parameters
DL-WRITE-DATA Request Confirm
Parameter name Input Output
SAP_ID
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...