EtherCAT interface
58
AMS 338
i
Leuze electronic GmbH + Co. KG
9.7
CANopen over EtherCAT
EtherCAT provides the communication mechanisms described below. In this context, the
SDO accesses to the online dictionary via CoE (CANopen over EtherCAT) are carried out
via mailbox services. PDO services via CoE mailboxes are not supported.
• Object index
• PDO, process data object
• SDO, service data object
• NMT, network management
Master and slave must be located in the same EtherCAT network.
9.7.1
Device profile
The device profile describes the application parameters and the functional behavior of the
AMS 338
i
. For EtherCAT, one does not specify individual device profiles for device classes.
Instead, simple interfaces for existing device profiles are provided.
The AMS 338
i
supports the "Device Profile for Encoder" DS406 known from CANopen.
9.7.2
Device description file
The object directory of the AMS 338
i
is saved for the user in a so-called ESI file (EtherCAT
Slave Information).
The ESI file contains all objects with index, sub-index, name, data type, default value,
minimum and maximum, and access privileges.
The ESI file describes the entire functionality of the AMS 338
i
.
The ESI file has the name AMS 338
i
.xml and is available for download on the Leuze home
page www.leuze.com.
Vendor ID for the AMS 338
i
The Vendor ID assigned by Leuze for the AMS 338
i
is 121
h
= 289
d
.