Anybus CompactCom 40 Modbus-TCP Installation and maintenance instructions

Anybus®CompactCom™40
PROFINET IRT Transparent Ethernet
NETWORK GUIDE
SCM-1202-021 EN 2.2 ENGLISH

Important User Information
Liability
Every care has been taken in the preparation of this document. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a
commitment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors
that may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements
including any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot
assume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product
described in this document. These intellectual property rights may include patents and pending patent applications
in the USA and other countries.
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2
Table of Contents Page
1 Preface ............................................................................................................................... 5
1.1 About this document ......................................................................................................5
1.2 Related Documents .......................................................................................................5
1.3 Document History ..........................................................................................................5
1.4 Document Conventions ..................................................................................................6
1.5 Terminology...................................................................................................................6
1.6 Trademark Information ...................................................................................................7
2 About the Anybus CompactCom 40 PROFINET IRT .............................................. 8
2.1 General.........................................................................................................................8
2.2 Features .......................................................................................................................8
2.3 Transparent Ethernet .....................................................................................................9
3 Basic Operation............................................................................................................. 10
3.1 General Information .....................................................................................................10
3.2 Network Identity...........................................................................................................13
3.3 Communication Settings...............................................................................................13
3.4 Network Data Exchange...............................................................................................14
4 PROFINET Implementation Details........................................................................... 16
4.1 General Information .....................................................................................................16
4.2 Application Process Instances (API) ..............................................................................16
4.3 Application Relationships (AR)......................................................................................17
4.4 Real Identification (RI)..................................................................................................17
4.5 Diagnostics .................................................................................................................21
4.6 Identification & Maintenance (I&M) ................................................................................22
4.7 Asset Management ......................................................................................................24
4.8 Fast Start Up ...............................................................................................................25
4.9 Address Conflict Detection (ACD) .................................................................................27
4.10 PROFIenergy Profile ....................................................................................................28
4.11 PROFIsafe ..................................................................................................................29
5 Modular Device .............................................................................................................. 30
5.1 General.......................................................................................................................30
5.2 Modular Device RI .......................................................................................................30
5.3 Remap........................................................................................................................30
5.4 Safety Module .............................................................................................................31
5.5 Record Data ................................................................................................................31
5.6 Modular Device Example..............................................................................................31
5.7 Recommendations.......................................................................................................33

Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2
Table of Contents
6 SNMP Agent.................................................................................................................... 34
6.1 General.......................................................................................................................34
6.2 Community Strings.......................................................................................................34
6.3 Management Information (MIB).....................................................................................34
6.4 MIB_II .........................................................................................................................34
7 Media Reduncancy Protocol (MRP).......................................................................... 37
7.1 General.......................................................................................................................37
7.2 GSDML Entries............................................................................................................37
8 Transparent Ethernet ................................................................................................... 38
8.1 General Information .....................................................................................................38
8.2 Enabling Transparent Ethernet......................................................................................39
8.3 MAC Address Synchronization......................................................................................39
8.4 IP Configuration Synchronization ..................................................................................39
8.5 Routing Restrictions.....................................................................................................39
9 Firmware Upgrade ....................................................................................................... 41
10 Anybus Module Objects .............................................................................................. 42
10.1 General Information .....................................................................................................42
10.2 Anybus Object (01h) ....................................................................................................43
10.3 Diagnostic Object (02h) ................................................................................................44
10.4 Network Object (03h) ...................................................................................................47
10.5 Network Configuration Object (04h)...............................................................................52
10.6 File System Interface Object (0Ah) ................................................................................60
10.7 Network Ethernet Object (0Ch) .....................................................................................61
10.8 Network PROFINET IO Object (0Eh) ............................................................................. 63
10.9 Functional Safety Module Object (11h) ..........................................................................80
11 Host Application Objects ............................................................................................ 86
11.1 General Information .....................................................................................................86
11.2 Energy Measurement Object (E4h) ...............................................................................87
11.3 Asset Management Object (E5h)...................................................................................98
11.4 Functional Safety Object (E8h)....................................................................................102
11.5 Sync Object (EEh) .....................................................................................................104
11.6 Energy Control Object (F0h) .......................................................................................108
11.7 PROFINET IO Object (F6h) ........................................................................................ 114
11.8 Ethernet Host Object (F9h) ......................................................................................... 133

Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2
Table of Contents
A Categorization of Functionality ...............................................................................137
A.1 Basic.........................................................................................................................137
A.2 Extended...................................................................................................................137
B Anybus Implementation Details ..............................................................................138
B.1 SUP-Bit Definition ......................................................................................................138
B.2 Anybus State Machine ...............................................................................................138
B.3 Application Status Register.........................................................................................138
B.4 Application Watchdog Timeout Handling ...................................................................... 139
C Flowcharts ....................................................................................................................140
C.1 Flowchart — Record Data Access ............................................................................... 140
C.2 Flowchart — I&M Record Data Handling...................................................................... 141
C.3 Flowchart —Establishment of Real Identification (RI) .................................................... 142
C.4 Flowcharts — Handling of Configuration Mismatch ....................................................... 143
D Secure HICP (Secure Host IP Configuration Protocol) .....................................145
D.1 General.....................................................................................................................145
D.2 Operation .................................................................................................................. 145
E Technical Specification .............................................................................................146
E.1 Front View.................................................................................................................146
E.2 Functional Earth (FE) Requirements............................................................................ 148
E.3 Power Supply ............................................................................................................148
E.4 Environmental Specification........................................................................................148
E.5 EMC Compliance.......................................................................................................149
E.6 Fiber Optics Compliance (MAU type Compliance) ........................................................ 149
F AIDA LED Mode ...........................................................................................................150
F.1 How to Design for AIDA LED Mode .............................................................................150
F.2 Anybus CompactCom AIDA LED Mode ....................................................................... 150

Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2
Table of Contents
G Conformance Test Guide ..........................................................................................153
G.1 General.....................................................................................................................153
G.2 Reidentifying Your Product .........................................................................................154
G.3 Factory Default Reset.................................................................................................155
G.4 IP Address.................................................................................................................155
G.5 Station Name.............................................................................................................155
G.6 Documentation Considerations ...................................................................................156
G.7 Certification in Generic Anybus Mode .......................................................................... 156
G.8 Certification in Advanced Mode...................................................................................157
G.9 Changes in GSD File for Conformance Class B............................................................ 158
G.10 SYNC Pin Measurements for Conformance Class C Test ............................................. 158
H Backward Compatibility ............................................................................................159
H.1 Initial Considerations..................................................................................................159
H.2 Hardware Compatibility ..............................................................................................160
H.3 General Software.......................................................................................................165
H.4 Network Specific — PROFINET ..................................................................................167
I Copyright Notices .......................................................................................................178

Preface 5 (188)
1 Preface
1.1 About this document
This document is intended to provide a good understanding of the functionality offered by the
Anybus CompactCom 40 PROFINET IRT. The document describes the features that are
specific to Anybus CompactCom 40 PROFINET IRT. For general information regarding Anybus
CompactCom, consult the Anybus CompactCom design guides.
The reader of this document is expected to be familiar with high level software design and
communication systems in general. The information in this network guide should normally be
sufficient to implement a design. However if advanced PROFINET specific functionality is to be
used, in-depth knowledge of PROFINET networking internals and/or information from the
official PROFINET specifications may be required. In such cases, the persons responsible for
the implementation of this product should either obtain the PROFINET specification to gain
sufficient knowledge or limit their implementation in such a way that this is not necessary.
For additional related documentation and file downloads, please visit the support website at
www.anybus.com/support.
1.2 Related Documents
Document Author Document ID
Anybus CompactCom 40 Software Design Guide HMS HMSI-216-125
Anybus CompactCom M40 Hardware Design Guide HMS HMSI-216-126
Anybus CompactCom B40 Design Guide HMS HMSI-27-230
Anybus CompactCom Host Application Implementation
Guide
HMS HMSI-27-334
Anybus CompactCom 40 PROFINET IRT Network Guide HMS SCM-1202-023
PROFINET IO specification, rev. 2.3 Profibus International
PROFIenergy Technical Specification, rev. 1.2 Profibus International
GSDML Technical Specification for PROFINET IO, rev 2.31 Profibus International
1.3 Document History
Version Date Description
1.0 2016-10-28 First public release
1.1 2016-11-23 Modular Device
Minor Corrections
1.2 2017-01-18 Minor corrections
1.3 2017-03-15 PROFIenergy profile added
Asset management and I&M5 added
1.4 2017-04-10 Updated to PROFIenergy 2
Minor corrections
1.5 2017-07-11 Added appendix on backward compatibility
Added appendix on AIDA LED mode
1.6 2017-11-28 Minor corrections
1.7 2017-12-15 Updated Copyright Appendix
1.8 2018-06-18 SYNC functionality description updated
Minor corrections
2.2 2018-10-23 Minor updates
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Preface 6 (188)
1.4 Document Conventions
Ordered lists are used for instructions that must be carried out in sequence:
1. First do this
2. Then do this
Unordered (bulleted) lists are used for:
• Itemized information
• Instructions that can be carried out in any order
...and for action-result type instructions:
► This action...
➨leads to this result
Bold typeface indicates interactive parts such as connectors and switches on the hardware, or
menus and buttons in a graphical user interface.
Monospaced text is used to indicate program code and other
kinds of data input/output such as configuration scripts.
This is a cross-reference within this document: Document Conventions, p. 6
This is an external link (URL): www.hms-networks.com
This is additional information which may facilitate installation and/or operation.
This instruction must be followed to avoid a risk of reduced functionality and/or
damage to the equipment, or to avoid a network security risk.
Caution
This instruction must be followed to avoid a risk of personal injury.
WARNING
This instruction must be followed to avoid a risk of death or serious injury.
1.5 Terminology
• The terms “Anybus” or “module” refers to the Anybus CompactCom module.
• The terms “host” or “host application” refer to the device that hosts the Anybus.
• Hexadecimal values are written in the format NNNNh or 0xNNNN, where NNNN is the
hexadecimal value.
• A byte always consists of 8 bits.
• The terms “basic” and “extended” are used to classify objects, instances and attributes.
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Preface 7 (188)
1.6 Trademark Information
Anybus®is a registered trademark of HMS Industrial Networks AB.
All other trademarks are the property of their respective holders.
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

About the Anybus CompactCom 40 PROFINET IRT 8 (188)
2 About the Anybus CompactCom 40 PROFINET
IRT
2.1 General
The Anybus CompactCom 40 PROFINET IRT communication module provides instant
PROFINET Real Time connectivity via the patented Anybus CompactCom host interface. Any
device that supports this standard can take advantage of the features provided by the module,
allowing seamless network integration regardless of network type.
This network guide covers the Transparent Ethernet version of the product.
Transparent Ethernet has to be enabled during setup, or the device will appear as
an Anybus CompactCom 40 with full IT functionality. The IT functionality is
described in the network guide for the standard Anybus CompactCom 40.
IT functionality is not available when Transparent Ethernet is enabled.
This product conforms to all aspects of the host interface for Active modules defined in the
Anybus CompactCom Hardware- and Software Design Guides, making it fully interchangeable
with any other device following that specification. Generally, no additional network related
software support is needed, however in order to take advantage of advanced network specific
functionality, a certain degree of dedicated software support may be necessary.
2.2 Features
• Transparent Ethernet
• Ethernet or fibre optics connectors
• Up to 128 submodules in total
• Up to 32767 ADIs
• Max. read process data: 1308 bytes
• Max. write process data: 1308 bytes
• Max. process data (read + write, in bytes): 2616 bytes
• Generic and PROFINET specific diagnostic support
• Complies with PROFINET IO Conformance class C
• Supports up to 1440 bytes I/O data in each direction, status bytes included.
• Supports 250 μs cycle time
• SNMP agent
• Device identity customization
• Modular Device Functionality
• PROFIenergy profile supported
• GSD file template provided by HMS
• Supports PROFINET Fast Start Up
• Supports Media Redundancy Protocol (MRP)
• Supports PROFIsafe
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

About the Anybus CompactCom 40 PROFINET IRT 9 (188)
2.3 Transparent Ethernet
Transparent Ethernet offers the possibility for a host application, that includes an IT
implementation (web pages, file system, a proprietary protocol etc.), to let the Anybus
CompactCom handle an industrial Ethernet protocol (in this case PROFINET), without the need
for extra Ethernet ports.
Ethernet communication is routed straight to the host application system using an RMII
interface. The host application must include an Ethernet controller and a TCP/IP stack.
PROFINET protocol messages will be routed to the Anybus CompactCom internal software.
Please note that the Transparent Ethernet functionality has to be enabled during startup by
setting attribute #16 (instance #1) in the Anybus Object.
16–bit parallell mode can not be used, as specific host application connector pins are reserved
for transparent Ethernet. Also TCP/UDP ports may be reserved, and can, in that case, not be
used for the transparent Ethernet communication.
See also ...
•Transparent Ethernet, p. 38
• Anybus CompactCom 40 Hardware Design Guide
•Anybus Object (01h), p. 43
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Basic Operation 10 (188)
3 Basic Operation
3.1 General Information
3.1.1 Software Requirements
Generally, no additional network support code needs to be written to support the Anybus
CompactCom 40 PROFINET IRT, however due to the nature of the PROFINET networking
system certain things must be taken into account:
• Up to 32767 ADIs can be represented on PROFINET.
• ADI names, types and similar attributes cannot be accessed via PROFINET. They are
however represented on the network through the built in web server.
• Up to 5 diagnostic instances can be created by the host application. An additional 6th
instance may be created in event of a major fault.
• For conformance reasons, the host application must implement support for network reset
types 00h (Power-on) and 02h (Power-on + Factory Default) in the Application Object
(FFh).
• PROFINET in itself does not impose any particular timing demands when it comes to
acyclic requests (i.e. requests towards instances in the Application Data Object), however
it is generally recommended to process and respond to such requests within a reasonable
time period (exactly what this means in practice depends on the implementation and the
actual installation).
• The order in which ADIs are mapped to Process Data is significant and must be replicated
in the IO Controller when setting up the network communication (i.e. modules must be set
up in the same order, size and direction, as the mapped ADIs). In case of a configuration
mismatch, see Configuration Mismatch, p. 19 for more information.
See also ...
•Application Data Instances (ADIs), p. 14
• Diagnostic Object Anybus Module Objects, p. 42
• Anybus CompactCom 40 Software Design Guide, Application Data Object (FEh)
3.1.2 Electronic Data Sheet (GSD)
On PROFINET, the characteristics of a device is stored in an XML data file. This file, referred to
as the “GSD” file, is used by PROFINET engineering tools when setting up the network
configuration. HMS Industrial Networks AB provides an example GSD file, which must be
adapted by the user to suit the application.
Setting Identity and Function Information
The GSD file must be adapted to your implementation. First thing is the device identity.
In the GSD file there is a section called “DeviceIdentity”. It looks like this.
<DeviceIdentity VendorID="0x010C" DeviceID="0x0010">
<InfoText TextId="T_ID_DEV_DESCRIPTION"/>
<VendorName Value="HMS Industrial Networks"/>
</DeviceIdentity>
The identity in the example represents HMS values.
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Basic Operation 11 (188)
• Replace VendorID value 0x010C with the value which corresponds to your vendor name.
If you do not have a Vendor ID you can obtain this by contacting PI.
Set with PROFINET IO Object (0xF6) attribute #2 (Vendor ID).
• Replace the DeviceID value 0x0010 with the value you have selected for this device.
Set with PROFINET IO Object (0xF6) attribute #1 (Device ID). Please note that if you
change the Device ID you MUST also change the Vendor ID, as the Device ID is unique for
the Vendor ID.
• Replace the VendorName value “HMS Industrial Networks” with name of your vendor.
Please note that the keyword VendorName is found not only here, but also at other places
in the GSD file. Use “Search”to find all instances and replace them with the name of your
vendor.
Specify the function of the device.
<DeviceFunction>
<Family MainFamily="General" ProductFamily="Anybus CompactCom 40 PIR"/>
</DeviceFunction>
The example GSD specifies a kind of “General”device as the usage of it is unclear.
• Replace the MainFamily with the class that best describe the device. The following are the
allowed values:
– General
– Drives
– Switching Devices
– I/O
– Valves
– Controllers
– HMI
– Encoders
– NC/RC
– Gateway
– PLCs
– Ident Systems
– PA Profiles
– Network Components
– Sensors
• Replace the ProductFamily value “Anybus CompactCom 40 PIR” with a string which
describes your device.
In addition to the above, there are a few more places where identity related information is
present in the GSD file.
DNS_CompatibleName="ABCC40-PIR"
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Basic Operation 12 (188)
For the Device access point (DeviceAccessPointItem) there is a keyword which is called DNS_
CompatibleName. Locate this by using the search function.
• Replace DNS_CompatibleName value “ABCC40-PIR” with the set Station Type. Set with
PROFINET IO Object (0xF6) attribute #3 (Station Type).
The order number of the device is set with the keyword “OrderNumber”.
<OrderNumber Value="ABCC40-PIR"/>
In many cases the value of the OrderNumber equals the Station Type string, but it does not
necessary need to be that way.
• Replace the OrderNumber value “ABCC40-PIR”with the order number used for the device.
Set with PROFINET IO Object (0xF6) attribute #8 (IM Order ID).
It is recommended to change the name of the DAP (keyword Name in the “ModuleInfo” section
of the DAP) to something more descriptive. The DAP name is often visible in the PROFINET
configuration tool.
• Replace the name “DAP” of the T_ID_DAP text ID with e.g. the name of the product type.
How to Enable Initial Record Data
During the establishment of an IO connection between the IO device and the IO controller it is
possible for the IO controller to send initial record data. This initial record data is sent using the
PROFINET IO service record write. This service can be used at any time and will write data to a
defined ADI. The initial record data is defined in the GSD file, and is specified for a submodule
of a module. By default, the Anybus CompactCom 40 module will not make use of any initial
record data, but that can be enabled if needed.
To enable this functionality, the GSD file needs to be modified as specified below. In this
example, 2 bytes are written to ADI 67 (ADI 67 corresponds to index 67) during startup of a
PROFINET IO connection (the value can be configured by the end user):
<RecordDataList>
<ParameterRecordDataItem Index="67" Length="2" TransferSequence="0">
<Name TextId="T_ID_EXAMPLE2"/>
<Ref DataType="Unsigned16" ByteOffset="0" DefaultValue=”0”
AllowedValues="0..65535" TextId="T_ID_EXAMPLE2_PRM_1"/>
</ParameterRecordDataItem>
</RecordDataList>
It is recommended that the above GSD information is placed directly after the “</IOData>”
keyword for the module for which the data is associated.
If more than one ADI needs to be set, the keyword “ParameterRecordDataItem”is duplicated.
Please note that TextId’s (“T_ID_xxx” above) need to be added to the “<ExternalTextList>”
section of the GSD file (once for each language defined).
<Text TextId="T_ID_EXAMPLE2" Value="Config parameter 1"/>
<Text TextId="T_ID_EXAMPLE2_PRM_1" Value="Parameter value description"/>
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Basic Operation 13 (188)
3.2 Network Identity
By default, the module identifies itself as a generic Anybus implementation as follows:
Device ID 0010h (Anybus CompactCom 40 PROFINET)
Vendor ID 010Ch (HMS Industrial Networks)
Station Type The Station Type will be assigned a value according to this priority:
If the PROFINET IO Object (F6h) is implemented, the value equals that of attribute
#3 in instance #1.
If the PROFINET IO Object is not implemented, the value of attribute #9 (Product
name) in the Application Object (FFh), instance #1, will be used (if implemented).
If none of these attributes are implemented, the value equals Anybus
CompactCom default value (“ABCC-PIR”).
It is recommended to customize the identity information so that the Anybus module appears as
a vendor specific implementation rather than a generic Anybus product.
See also...
•Identification & Maintenance (I&M), p. 22
•PROFINET IO Object (F6h), p. 114
• Application Object (FFh) in Anybus CompactCom Software Design Guide
3.3 Communication Settings
Network related communication settings are grouped in the Network Configuration Object
(04h), and includes:
Ethernet Interface
Settings
The module is locked to 100 Mbit full duplex operation as required by PROFINET.
IP Settings These settings must be set in order for the module to be able to participate on the
network.
Normally set by the IO Controller.
IP settings must be synchronized between the Anybus CompactCom 40 and the
host application.
PROFINET Station Name The module needs to be assigned a Station Name in order to participate on
PROFINET.
Normally set from the network.
See also...
•Identification & Maintenance (I&M), p. 22
•Network Configuration Object (04h), p. 52
•Secure HICP (Secure Host IP Configuration Protocol), p. 145
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Basic Operation 14 (188)
3.4 Network Data Exchange
3.4.1 Application Data Instances (ADIs)
ADIs can be accessed acyclically from the network by means of Record Data read/write
services. If addressed through a given API and Index range, the module translates the service
into standard object requests towards the Application Data Object. If the host application
responds with an error to such a request, that error will be translated to PROFINET standard.
The following parameters affect the addressing of ADIs onPROFINET:
Application Process
Instance (API)
API 0 (zero) provides access to data in the Application Data Object, i.e. the ADIs.
Acyclic requests towards other APIs will be forwarded to the PROFINET IO Object
(F6h), p. 114 by means of the ‘Get_Record’ and ‘Set_Record’-commands.
The remainder of this section assumes API 0 (zero).
Slot & subslot The Slot and subslot values have no impact on the actual addressing of ADIs,
except that the actual Slot and subslot needs to be populated with a module/
submodule. This is always true for the DAP (Device Access Point), which occupies
Slot #0/subslot #1. Other Slot/subslot values can also be used provided that the
implementation populates it with a module/submodule.
Index There is a 1:1 correlation between ADI and index as long as the index number is
less than - or equal to - 7FFFh. Index 0 (zero) is not associated with an ADI and
cannot be used.
API Slot Subslot Index ADI Comments
0 0 1 0000h -(not associated with ADIs)
0001h 1 Device Access Point (DAP)
0002h 2
... ...
7FFFh 32767
8000h...FFFFh -(not associated with ADIs)
X (>0) Y 0000h
0001h 1 Conditional; X and Y must be
populated
0002h 2
... ...
7FFFh 32767
8000h...FFFFh -(not associated with ADIs)
>0 - - - - See Application Process Instances
(API), p. 16
See also...
•Caveats, p. 15
•Application Process Instances (API), p. 16
•PROFINET IO Object (F6h), p. 114
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

Basic Operation 15 (188)
3.4.2 Process Data
Mapping an ADI to Write Process Data results in PROFINET input data, and mapping an ADI to
Read Process Data results in PROFINET output data. Consistency over all I/O data mapped on
PROFINET is guaranteed.
See also...
•Real Identification (RI), p. 17
The order in which ADIs are mapped to Process Data is significant and must be
replicated in the IO Controller when setting up the network communication (i.e.
modules must be set up in the same order, size and direction, as the mapped ADIs).
3.4.3 Caveats
The length parameter in the Record Data request specifies the number of bytes to read/write.
• When reading more data than the actual size of the ADI, the response will only contain the
actual ADI data, i.e. no padding on the data is performed by the module.
• When writing to an ADI, the length parameter is not checked by the module, i.e. the host
application must respond with an error if the length differs from the actual size of the
requested ADI.
See also..
•Application Process Instances (API), p. 16
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

PROFINET Implementation Details 16 (188)
4 PROFINET Implementation Details
4.1 General Information
This chapter covers PROFINET specific details in the Anybus implementation. Note that the
use of such functionality may require in-depth knowledge in PROFINET networking internals
and/or information from the official PROFINET specification. In such cases, the people
responsible for the implementation of this product are expected either to obtain these
specifications to gain sufficient knowledge or limit their implementation in such a way that this is
not necessary. The GSD file must be changed to reflect all changes.
Implementation overview:
Conformance Class The Anybus module complies to conformance class C.
Performance
Characteristics
• 100 Mbps, full duplex with autonegotiation enabled as default
• Real Time (RT) communication, 250 μs cycle time
• Isochronous Real Time (IRT) communication, 250 μs cycle time
Device Model • One IO Device instance
• The IO Device instance includes an Application Process referenced by its
identifier (API). API 0 (zero) is implemented by default.
• The API implements one or more slots
• Each Slot implements one or more subslots
• Each subslot may implement one or more Channels
Slots & Subslots Up to 128 subslots in total.
IO Data 1440 bytes of IO data in each direction, including status bytes (4 bytes for DAP
submodules + 1 byte per additional submodule)
See also...
•Electronic Data Sheet (GSD), p. 10
4.2 Application Process Instances (API)
As mentioned previously, acyclic requests towards API 0 are forwarded to the Application Data
Object.
Cyclic data exchange is by default carried out through API 0 (i.e. the Anybus associates
modules and submodules with API 0).
See also...
•Application Data Instances (ADIs), p. 14
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

PROFINET Implementation Details 17 (188)
4.3 Application Relationships (AR)
On PROFINET, a connection between an IO Controller/Supervisor and an I/O device (in this
case the Anybus) is called Application Relationship (AR). The Anybus module supports multiple
simultaneous Application Relationships, allowing multiple IO Supervisors to access its data and
functions.
The host implementation can either ignore this functionality altogether, in which case the
Anybus module will handle it automatically, or integrate the establishment and handling of
Application Relationships into the host firmware.
Application Relationships are managed through the following functions:
• AR_Check_Ind (for command details see PROFINET IO Object (F6h), p. 114)
• Expected_Ident_Ind(for command details see PROFINET IO Object (F6h), p. 114)
• AR_Abort_Ind(for command details see PROFINET IO Object (F6h), p. 114)
• AR_Abort (for command details see Network PROFINET IO Object (0Eh), p. 63)
4.4 Real Identification (RI)
4.4.1 General Information
During the establishment of an IO Connection towards the Anybus CompactCom 40
PROFINET IRT, the configuration derived from the IO Controller (i.e. the Expected
Identification) and the actual configuration in the Anybus CompactCom 40 PROFINET IRT (i.e.
the Real Identification or RI) are compared.
The RI configuration is either handled by the module (default), or by the host application. In
either case the GSD file has to be customized to correspond to the configuration.
ADI Based Configuration (Default)
By default (i.e. if the application does not issue API_Add, Plug_Module, Plug_Submodule), the
Anybus CompactCom 40 PROFINET IRT handles the plugging of modules and submodules
automatically in accordance with the mapped Process Data as follows:
• A DAP is plugged into Slot 0 (zero)
• Modules are added in consecutive order (based on the order of the mapping commands)
• All modules belong to API 0 (zero)
The Anybus CompactCom 40 PROFINET IRT internally creates module/submodule identifiers
as described in the picture and the example below. The GSD file has to be customized to define
the same modules/submodules with the same identifiers as the Anybus CompactCom 40
PROFINET IRT has created internally.
Submodule ID:Module ID:
0: Mapped to write PD area
1: Mapped to read PD area
Number of
elements to map
0x00000301
ADI start
element number
ADI number
0x00000004
Fig. 1
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2

PROFINET Implementation Details 18 (188)
Example (100BASE-TX DAP):
ADI # Type Resulting Real Identification
Module/Submodule ID Slot/Subslot IO Data Size (bytes)
- - 0x80010000/
0x00000001
0x80010000/
0x00000002
0x80010000/
0x00000003
0x80010000/
0x00000003
0/1 (Device Access
Point)
0/0x8000 (Interface)
0/0x8001 (Port1)
0/0x8002 (Port2)
-
6 1 SINT16 Wr 0x00000006/
0x00000100
1/1 2
3 2 UINT8 Rd 0x00000003/
0x10000200
2/1 2
3 1 UINT8 Rd 0x00000003/
0x10000104
2/2 1
9 1 SINT32 Rd 0x00000009/
0x10000100
3/1 4
10 1 SINT16 Wr 0x0000000A/
0x00000100
4/1 2
See also...
•Application Process Instances (API), p. 16
•Flowchart —Establishment of Real Identification (RI), p. 142
Modular Device Configuration
The RI, when implementing a modular device, is generated from the Module IDs and process
data mappings as defined in the Modular Device Object (ECh). For more information see
Modular Device, p. 30.
Custom Configuration (Advanced Users)
Optionally it is possible to override the default configuration during the SETUP state by means
of the PROFINET specific commands API_add, Plug_Module, Plug_Submodule, and Plug_
Submodule_Ext. This way, the host application can define exactly how ADIs are represented on
PROFINET by defining custom modules and submodules. These commands need to be sent
after the process data is mapped, and before sending setup complete to the Anybus
CompactCom 40 PROFINET IRT.
See also...
•Network PROFINET IO Object (0Eh), p. 63
•Flowchart —Establishment of Real Identification (RI), p. 142
Anybus®CompactCom™40 PROFINET IRT Transparent Ethernet Network Guide SCM-1202-021 EN 2.2