![Festo CMMP-AS-***-M0 Series Manual Download Page 72](http://html1.mh-extra.com/html/festo/cmmp-as-m0-series/cmmp-as-m0-series_manual_2283119072.webp)
4
EtherCAT interface
72
Festo – GDCP-CMMP-M3/-M0-C-CO-EN – 1510b – English
As the example above shows, the entire mapping of the Receive PDO is described in detail in such
entries. The first large block specifies the object number of the PDO and its type. This is followed by a
list of all CANopen objects which are to be mapped to the PDO.
The table below describes the individual entries in greater detail:
Node name
Significance
Adaptable
RxPDO
Fixed=“1”
Sm=“2”
This node describes the properties of the Receive PDO directly and
its assignment to the Sync Manager. The Fixed=“1” entry indicates
that the object mapping cannot be revised. The Sm=“2” entry
indicates that the PDO is to be allocated to Sync channel 2 of the
Sync Manager.
No
Index
This entry contains the object number of the PDO. The first Receive
PDO under object number 0x1600 is configured here.
Yes
Name
The name indicates that this PDO is a Receive PDO (outputs) or a
Transmit PDO (inputs).
This value must always be set to “Output” for a Receive PDO.
No
Entry
Each Entry node contains a CANopen object to be mapped to the
PDO. An Entry node contains the index and sub-index of the
CANopen object to be mapped, as well as their name and data type.
Yes
Tab. 4.18 Elements of the node “RxPDO”
The sequence and mapping of the individual CANopen objects for the PDO correspond to the sequence
in which they are specified via the “Entry” entries in the device description file. The individual sub-items
of an “Entry” node are specified in the following table:
Node name
Significance
Adaptable
Index
This entry specifies the index of the CANopen object to be mapped
to the PDO.
Yes
Sub-index
This entry specifies the sub-index of the CANopen object to be
mapped.
Yes
BitLen
This entry specifies the size of the object to be mapped in bits.
This entry must always correspond to the type of the object to be
mapped.
Allowed: 8 Bit / 16 Bit / 32 Bit.
Yes
Name
This entry specifies the name of the object to be mapped as a string.
Yes
Data Type
This entry specifies the data type of the object to be mapped.
This can be taken from the respective description for the individual
CANopen objects.
Yes
Tab. 4.19 Elements of the node “Entry”