®
™
Anybus
CompactCom
40 - PROFINET IRT Transparent
Ethernet
5. Modular Device
5.1. General
The modular device concept is useful when creating a configuration based on reusable modules, for example
when modelling a backplane device with pluggable modules.
The first slot (slot 0) is always occupied by the Device Access Point (DAP) module, which represents the head
node where the Anybus CompactCom is located. It is not allowed to add a process data mapping for any ADI
within the range of slot 0. The remaining slots are assigned fixed ranges of ADIs, set up using the Modular Device
Object. A GSD module can represent different ADIs, depending on which slot it occupies, making it possible to
create a configuration based on reusable modules. This is not possible in ADI based RI mode.
See also ...
• " Modular Device Object (ECh)" (see Anybus CompactCom 40 Software Design Guide)
5.2. Modular Device RI
The RI, when implementing a modular device, is generated from the Module IDs as defined in the Modular
Device Object (ECh) (see the Anybus CompactCom 40 Software Design Guide) and from the process data
mappings as shown in the example below.
Module ID:
0x0000004
Submodule ID:
0x00010203
0x0
A set of conditions must be fulfilled for the Anybus CompactCom to use the Modular Device RI:
• The Modular Device object implemented must be of revision 1.
• Modular device object attributes #11 and #12 must be readable and valid
– Number of slots must be: 0 < NumSlots <= 256
– ADIs per slot must be: 0 < AdisPerSlot <= 4096
• The list with Module Type IDs must contain "NumSlots" items.
5.3. Remap
For a host application not supporting remap, the modules must contain a fixed set of submodules (GSD attribute
FixedInSubslots), where the process data mapping of each slot is performed in accordance with the GSD
definition of each particular module type. See
the same module ID and also matching process data mapping commands.
If remap is supported by the application the GSD modules may be designed in a flexible manner with pluggable
submodules (GSD attributes AllowedInSubslots / UsedInSubslots). If the configuration results in an expected
identification that differs from the real identification the Anybus CompactCom will attempt to resolve the
mismatch according to
Configuration Mismatch (page
Page 28 of 177
001
02
03
Modular Device Example (page
17).
0: Mapped to Write PD area
1: Mapped to Read PD area
ADI index
Number of elements to map
ADI start element #
29), where slot 1 and slot 3 have
SCM-1202-021 Version 2.6
Modular Device
Need help?
Do you have a question about the Anybus CompactCom 40 and is the answer not in the manual?
Questions and answers