Ethernet POWERLINK
Modular Device
EPSG DS 302-F V1.0.1

EPSG Draft Standard 302-F

Ethernet POWERLINKPart F: Modular Device

Version 1.0.1©

B&R(B&R Automation Industrial Automation GmbH)
2023

EPSG DS 302-F V1.0.1-2-

B&R Industrial Automation GmbH

POWERLINK-Office
B&R Straße 15142 Eggelsberg
Austria

powerlink.office@br-automation.com
www.br-automation.com/en/technologies/powerlink/

The EPSG Draft Standard 302-F “Ethernet Powerlink, Part F: Modular Device” has been provided by
Ethernet POWERLINK Standardisation Group (hereinafter referred to as “EPSG”). As a consequenceof the EPSG being dissolved from March 31st, 2023, B&R Industrial Automation GmbH will – as theformal successor of EPSG regarding the rights and content – make the Ethernet Powerlink Part F:
Modular Device available as open source on it’s own website subject to the conditions mentioned in
the disclaimer under clause Pre. 1 of this document. B&R Industrial Automation GmbH especiallydisclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether
special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication,use of, or reliance upon this, or any other EPSG Standard document.

EPSG DS 302-F V1.0.1

Pre. 1-3-Disclaimer

Use of this EPSG Standard is wholly voluntary. The EPSG disclaims liability for any personal injury,
property or other damage, of any nature whatsoever, whether special, indirect, consequential, orcompensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any
other EPSG Standard document.
The EPSG does not warrant or represent the accuracy or content of the material contained herein,and expressly disclaims any express or implied warranty, including any implied warranty ofmerchantability or fitness for a specific purpose, or that the use of the material contained herein is freefrom patent infringement. EPSG Standards documents are supplied “AS IS”.
The existence of an EPSG Standard does not imply that there are no other ways to produce, test,measure, purchase, market, or provide other goods and services related to the scope of the EPSG
Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued issubject to change brought about through developments in the state of the art and comments received
from users of the standard. Users are cautioned to check to determine that they have the latest editionof any EPSG Standard.
In publishing and making this document available, the EPSG is not suggesting or rendering
professional or other services for, or on behalf of, any person or entity. Nor is the EPSG undertaking toperform any duty owed by any other person or entity to another. Any person utilizing this, and anyother EPSG Standards document, should rely upon the advice of a competent professional indetermining the exercise of reasonable care in any given circumstances.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as
they relate to specific applications. When the need for interpretations is brought to the attention of theEPSG, the group will initiate action to prepare appropriate responses. Since EPSG Standards
represent a consensus of concerned interests, it is important to ensure that any interpretation has also
received the concurrence of a balance of interests. For this reason, the EPSG and its members are
not able to provide an instant response to interpretation requests except in those cases where thematter has previously received formal consideration.
Comments for revision of EPSG Standards are welcome from any interested party, regardless ofmembership affiliation with the EPSG. Suggestions for changes in documents should be in the form ofa proposed change of text, together with appropriate supporting comments. Comments on standards
and requests for interpretations should be sent to the address given on the page before.

Pre. 1.1

Patent noticeAttention is called to the possibility that implementation of this standard may require use of subject
matter covered by patent rights. By publication of this standard, no position is taken with respect to theexistence or validity of any patent rights in connection therewith. B&R shall not be responsible for
identifying patents for which a license may be required by an EPSG standard or for conducting
inquiries into the legal validity or scope of those patents that are brought to its attention.

EPSG DS 302-F V1.0.1-4-Pre. 2

HistoryVers.
0.0.1
0.0.2

Date2016-06-27
2016-07-12

Author
KirchmayerKirchmayer

B&R
B&R

1.0.0
1.0.1

2016-09-15
2023-05-31

Kirchmayer
Kirchmayer

B&R
B&R

short description
createdDocument status changed to DSP
Value range of ChildIdentList and DownloadChildProgList
restricted
Document status changed to DS© B&R due to dissolution of EPSGEPSG DS 302-F V1.0.1

Pre. 3Pre. 1Pre. 1.1
Pre. 2Pre. 3Pre. 4Pre. 5Pre. 6Pre. 6.1
Pre. 6.2
Pre. 7
12
2.1
2.2
2.3
3
3.1
3.2
3.2.1
3.2.2
3.3
3.3.1
3.3.2
4-5-ContentDisclaimer
Patent noticeHistory
ContentTables
FiguresDefinitions and Abbreviations
Definitions
Abbreviations
References
Introduction
GeneralDefinitions
What is not part of this specification?
Device Description
Additional Object Description
Object 1F82h: NMT_FeatureFlags_U32
Child identification
Object 1027h: NMT_ChildIdentList_AU16
Object ChildIdentListIdx: NMT_ChildIdentData_ADOM
Child program download
Object 1F55h: PDL_DownloadChildProgList_AU16
Object ChildProgListIdx: PDL_DownloadChildProgData_ADOM
Additional Device Description Entries

33456788891011111111121212121213131415EPSG DS 302-F V1.0.1

Pre. 4
Tab. 1
Tab. 2-6-

Tables
NMT_FeatureFlags_U32 additional bit interpretation
ChildIdent value interpretation

1213

EPSG DS 302-F V1.0.1

Pre. 5Figures

There are no figures in the document.

-7-

EPSG DS 302-F V1.0.1-8-Pre. 6

Definitions and Abbreviations

Pre. 6.1

Definitions

Pre. 6.2

AbbreviationsEPSG DS 302-F V1.0.1

Pre. 7[1][2]-9-

References

EPSG Draft Standard 301 (EPSG DS 301), Ethernet POWERLINK, Communication Profile
Specification
EPSG Draft Standard 311 (EPSG DSP 311), Ethernet POWERLINK, XML Device DescriptionEPSG DS 302-F V1.0.1

1-10-Introduction

So far from POWERLINK specifications point of view a POWERLINK device is a device with aPOWERLINK network interface and objects in the object dictionary to be accessed via PDO or SDO.
The device behind the interface was no target of the specification at all.
With the introduction of modular devices the way how the device is composed becomes a focus.
A POWERLINK device may be a single device or it may be composed of two or more modules, i.e. it
is a modular device.
This specification extends the POWERLINK specification DS 301 to be able to describe and configure
modular devices in the POWERLINK network. Therefore also the device description specification (DS311) is extended to be able to describe modular devices.

EPSG DS 302-F V1.0.1

2General

2.1

Definitions-11-

A modular device consists of a so called head device and one or more attached devices called childdevices.
The POWERLINK interface shall allways be included in the head device. Furthermore the head device
shall have one or more interfaces for attaching child devices.
These child devices may be connected to the head device and also to each other by any bus.

2.2

What is not part of this specification?

The physical and logical connection of the child devices between each other and also to the headdevice is not part of this specification.

2.3

Device Description

All matters concerning device description are specified in the corresponding device description
specification. See EPSG 311 for more details.
The mapping of child objects into the object dictionary of the head device is described in thespecification of the device description.

EPSG DS 302-F V1.0.1-12-3

Additional Object Description

3.1

Object 1F82h: NMT_FeatureFlags_U32

The Feature Flags indicate communication profile specific properties of the device given by its design.
The object shall be setup by the device firmware during system initialisation.
Additional bit used:
Octet Bit
2
21

Name
Modular Device

TRUE
device is a
modular device

FALSE
device is not aTab. 1

NMT_FeatureFlags_U32 additional bit interpretation

3.2

Child identification

3.2.1

Object 1027h: NMT_ChildIdentList_AU16

NMT_ChildIdentList_AU16 holds the indices of objects in the user specific area holding identification
data for child devices. For definition of these objects named NMT_ChildIdentData_ADOM.
One NMT_ChildIdentData_ADOM object is able to hold information of up to 254 child devices. If thedevice supports more, the identification data will continue with sub-index 1 of the object given by thenext index of this array.
Index
Name
Data Type•

1027h
NMT_ChildIdentList_AU16
UNSIGNED16

Object CodeARRAY

Category

MN:
CN: M

AccessPDO MappingroNoCategory
AccessPDO Mapping

MroNo-Sub-Index 00h: NumberOfEntries
Sub-IndexNameValue Range
Default Value

00h
NumberOfEntries
1 .. 254-

NumberOfEntries is implementation specific.
•Sub-Index 01h .. FEh: ChildIdentList
Sub-Index
Name-Value Range
Default Value

01h .. FEh
ChildIdentList-2000h ... 5FFFh-ChildIdentList holds the index of the object NMT_ChildIdentData_ADOM.

3.2.2

ObjectChildIdentListIdx1:
NMT_ChildIdentData_ADOM

NMT_ChildIdentData_ADOM holds identification data for child devices. It allows the access toidentification data of up to 254 child devices.

1 ChildIdentListIdx represents the value given by the object 1027h.

EPSG DS 302-F V1.0.1

Index
Name
Data Type•-13-

ChildIdentListIdx
NMT_ChildIdentData_ADOM
DOMAIN

Object Type

ARRAY

Category

MN:
CN: MAccess
PDO MappingroNoCategory
AccessPDO Mapping

M
ro
No

-Sub-Index 00h: NumberOfEntries
Sub-Index
Name
Value Range
Default Value

00h
NumberOfEntries
01h .. FEh-

Number of child devices addressed by this object.
Sub-Index 01h .. FEh: ChildIdent
Sub-Index
Name-Value Range
Default Value

01h .. FEh
ChildIdent-DOMAIN-ChildIdent sub-indices provide access to the identification data of child devices.
Each sub-index in the array corresponds to the child device with the module number equal tothe sub-index (plus all the number of entries of the objects listed in NMT_ChildIdentList_AU16(1027h) before).
•Value Interpretation
VendorId_U32

ProductCode_U32

RevisionNo_U32

SerialNo_U32

ApplSwDate_U32

ApplSwTime_U32…

Tab. 2ChildIdent value interpretation
ChildIdent is composed of at least 24 octets. The vendor may define more (vendor specific)
data after this. However the size of the domain shall not exceed 128 bytes.
NOTE: This is to avoid problems with clients which cannot handle very large domains.
VendorId_U32, ProductCode_U32_RevisionNo_U32 and SerialNo_U32 are equivalent to thesub-indicesofobject1018h(NMT_IdentityObject_REC).
ApplSwDate_U32
andApplSwTime_U32
areequivalent
tothe
sub-indicesofobject
1F52h(PDL_LocVerApplSw_REC).
In case of a not plugged child device the values shall be all 0.

3.3Child program download

3.3.1

Object
PDL_DownloadChildProgList_AU16

1F55h:

PDL_DownloadChildProgList_AU16 holds the indices of objects in the user specific area holding thefirmwareofchilddevices.
For
definitionoftheseobjects
named
PDL_DownloadChildProgData_ADOM.
One PDL_DownloadChildProgData_ADOM object is able to hold the firmware of up to 254 childdevices. If the device supports more, the firmware will continue with sub-index 1 of the object given by
the next index of this array.

EPSG DS 302-F V1.0.1

Index
Name
Data Type
•

-14-

1F55h
PDL_DownloadChildProgList_AU16
UNSIGNED16

Object CodeARRAY

Category

MN: CN: MAccess
PDO Mappingro
No

Category
AccessPDO Mapping

M
ro
No

Sub-Index 00h: NumberOfEntries
Sub-Index
Name
Value Range
Default Value

00h
NumberOfEntries
1 .. 254-NumberOfEntries is implementation specific.
•Sub-Index 01h .. FEh: DownloadChildProgList
Sub-Index
Name-Value Range
Default Value

01h .. FEh
DownloadChildProgList-2000h ... 5FFFh-

DownloadChildProgList holds the index of the object PDL_DownloadChildProgData_ADOM.

ObjectChildProgListIdx2:
PDL_DownloadChildProgData_ADOM

3.3.2

PDL_DownloadChildProgData_ADOM holds programs for child devices. It allows the access to up to254 programs.
Index
Name
Data Type•ChildProgListIdx
Object TypePDL_DownloadChildProgData_ADOM
DOMAIN
Category

ARRAY
MN:
CN: M

-Sub-Index 00h: NumberOfEntries
Sub-Index
Name
Value Range
Default Value

00h
NumberOfEntries
01h .. FEh-Access
PDO MappingroNo

Category
AccessPDO MappingM
condNoNumber of child devices addressed by this object.
Sub-Index 01h .. FEh: ChildProgram
Sub-Index
Name-Value Range
Default Value

02h .. FEh
ChildProgram-DOMAIN-ChildProgram sub-indices provide access to the firmware of child devices.
If the device supports reading of the program the access shall be rw otherwise wo.
Each sub-index in the array corresponds to the child device with the module number equal to
the sub-index (plus all the number of entries of the objects listed in
PDL_DownloadChildProgList_AU16 (1F55h) before).
2 ChildProgListIdx represents the value given by the object 1F55 .
h

EPSG DS 302-F V1.0.1

4-15-

Additional Device Description Entries

There are no additional device description entries necessary.