EtherNet/IP Implementation Details
4
EtherNet/IP Implementation Details
4.1
General Information
This chapter covers EtherNet/IP specific details in the Anybus implementation. Note that the use
of such functionality may require in-depth knowledge in EtherNet/IP networking internals and/or
information from the official EtherNet/IP and CIP specifications. 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 EDS file must be changed to reflect all changes.
4.2
EtherNet/IP & CIP Implementation
By default, the module supports the generic CIP profile. Optionally, it is possible to re-route
requests to unimplemented CIP objects to the host application, thus enabling support for other
profiles etc.
To support a specific profile, perform the following steps:
1.
Set up the identity settings in the EtherNet/IP Host Object according to profile requirements.
2.
Implement the Assembly Mapping Object in the host application.
3.
Set up the Assembly Instance Numbers according to profile requirements.
4.
Enable routing of CIP messages to the host application in the EtherNet/IP Host Object.
5.
Implement the required CIP objects in the host application.
See also...
•
Using the Assembly Mapping Object (EBh), p. 18
•
EtherNet/IP Host Object (F8h), p. 200
Process_CIP_Object_Request.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide
(Host Application Object), details for the command
17 (244)
SCM-1202–069 1.9 en-US
Need help?
Do you have a question about the CompactCom 40 and is the answer not in the manual?
Questions and answers