
10 (136)
3.1.2
EtherCAT Slave Interface (ESI) File
Each device on EtherCAT is associated with a EtherCAT Slave Interface (ESI) file in XML for-
mat, which holds a description of the device and its functions.
HMS Industrial Networks AB supplies a generic ESI file which can serve as a basis for new im-
plementations. However, due to the flexible nature of the Anybus CompactCom concept, it is
possible to alter the functionality of the module in ways which contradicts the information in this
file. This may cause trouble if the master expects the configuration stated in the file. In some
cases, these problems can be rectified by the end user by manually changing I/O parameters
etc. To ensure interoperability and to reduce the complexity for the end user, it is strongly rec-
ommended to create a custom ESI file to match the final implementation of the product.
The EtherCAT Technology Group (ETG) requires that the Vendor ID is changed to reflect the
vendor of the end product. The following scenarios, among others, may require additional
changes to the EtherCAT Slave Interface file.
•
The use of a custom Product Code.
•
The use of an own Vendor ID.
•
Change of the product revision.
•
The host application supports the Remap_ADI commands.
•
The use of Ethernet over EtherCAT (EoE).
•
Slow application response times. Explicit requests should be handled within 1 ms in or-
der to comply with the generic ESI file supplied by HMS. This may not be sufficient for a
slow serial link with a substantial amount of I/O (in such case, the mailbox timeout value
in the file needs to be increased accordingly).
Note that deviations from the generic ESI file requires the use of custom Product Codes apart
from the required custom Vendor ID.
3.1.3
Device Identity
In a generic implementation (i.e. no network specific support is implemented) the module will
appear as a generic HMS device with the following identity information:
Object Entry
Value
Vendor ID
E000 001Bh (HMS Industrial Networks Secondary Vendor ID, has to
be replaced by the Vendor ID of the end product vendor.)
Product Code
0000 0036h (Anybus CompactCom 40 EtherCAT)
Device Name
Anybus CompactCom 40 EtherCAT
Serial Number
(Assigned during manufacturing)
By implementing support for the EtherCAT Object (F5h), the module can be customized to ap-
pear as a vendor specific implementation rather than a generic Anybus device. For the end
product to pass the ETG conformance tests and be certified, a separate Vendor ID has to be re-
quested from ETG.
See also...
•
Anybus
®
CompactCom
™
40 EtherCAT
®
Network Guide
SCM-1202-034 1.1
Содержание CompactCom 40 EtherCAT
Страница 1: ...Anybus CompactCom 40 EtherCAT NETWORK GUIDE SCM 1202 034 1 1 ENGLISH...
Страница 6: ...This page intentionally left blank...
Страница 118: ...This page intentionally left blank...