Anybus CompactCom 40 Network Manual page 20

EtherNet/IP Implementation Details
4.3.4 Configuring CIP Assembly Numbers
The read and write instance list attributes in the assembly mapping object are bound to two cor-
responding attributes in the EtherNet/IP host object, according to the following table.
This routes application data to CIP assembly data, by linking CIP instance numbers to assem-
bly mapping object instances.
The lists are matched index-wise, and must thus be of equal length.
Assembly Mapping Object
Attribute
11 - Write PD Instance List
12 - Read PD Instance List
4.3.5 Going Forward
During the initialization phase, in the NW_INIT state, all write assemblies (e.g. the instances of
the assembly mapping object with type"write") will be remapped to the write process data area.
For this to happen, the device will issue the Remap_ADI_Write_Area command to the applica-
tion data object in the host.
See the appendix about "Runtime Remapping of Process Data" in the Anybus CompactCom 40
Software Design Guide for more information.
When the network has been initialized, the device transitions from NW_INIT to the WAIT_
PROCESS state. When the device receives a forward open request, the producing/consuming
parameters in the request are verified and matched against the EtherNet/IP Host Object in-
stance numbers (producing/consuming)
If the verification is successful, the read process data is remapped and the device transitions to
the PROCESS_ACTIVE state. The I/O connection will then be established, and data can be ex-
changed over the network.
Anybus CompactCom 40 EtherNet/IP Transparent Ethernet Network Guide
Value
10
11
51
1
2
30
For conformity with the CIP specification, both the Write_Assembly_Data and the
Read_Assembly_Data services must be implemented.
Value EtherNet/IP Host Object Instance
Attribute
<—>
10 7 - Producing Instance Number
<—>
22
<—>
100
<—> 1 8 - Consuming Instance Number
<—>
2
<—>
150
18 (144)
SCM-1202-019-EN 1.6