Basic Operation 15
Doc.Id. HMSI-27-212
Anybus CompactCom 40 EtherNet/IP
Doc.Rev. 1.5
2.2.6 Modular Device Functionality
Modular devices consist of a backplane with a certain number of “slots”. The first slot is occupied by
the “coupler” which contains the Anybus CompactCom module. All other slots may be empty or occu-
pied by modules.
When mapping ADIs to process data the application shall map the process data of each module in slot
order.
A list of modules in a Modular Device is available to the EtherNet/IP network master by a request to
the CIP Identity object.
See also ...
• “Modular Device Object (ECh)” (see Anybus CompactCom 40 Software Design Guide)
• “Identity Object (01h)” on page 63
2.2.7 QuickConnect
The module supports the QuickConnect functionality. It is enabled in the EtherNet/IP Host Object.
The module fulfills Class A with a startup time of less than 180 ms, with 16 bytes of I/O data mapped
with parallel, SPI or shift register application interface.
See also ...
• “EtherNet/IP Host Object (F8h)” on page 161
• “TCP/IP Interface Object (F5h)” on page 87 (CIP object)
2.2.8 CIP Safety
The Anybus CompactCom 40 EtherNet/IP device supports the CIP safety profile. This profile makes
it possible for a user to send data on a black channel interface, i.e. a safe channel over EtherNet/IP using
an add-on safety module, e.g. the IXXAT Safe T100. For an application to support CIP safety, the Func-
tional Safety Object (E8h) has to be implemented.
The Anybus CompactCom serial channel is used for the functional safety communication. When this
channel is used for the host application, a second separate serial channel is implemented for the func-
tional safety communication. See the Anybus CompactCom Hardware Design Guide for more informa-
tion.
See “Functional Safety Host Object (E8h)” on page 156.
To Next Page
Loading...
Need help?
General
