Anybus CompactCom 40 Network Manual page 127

Appendix F: Conformance Test Guide
F.3.2 Implementation of Anybus Module Objects
Only the Anybus module objects relevant to EtherNet/IP will be discussed.
Network Object (03h)
Network Object (03h) - Attribute #5 - Write Process Data Size
The Write Process Data Size represents the current amount of data mapped for the T-> O con-
nection. In most cases, but not always, this value will correspond to the T->O connection size in
the connection manager. Please note that it is possible to support multiple assemblies for con-
nection points by supporting process data remapping.
Network Object (03h) - Attribute #6 - Read Process Data Size
The Read Process Data Size represents the current amount of data mapped for the O->T con-
nection. In most cases, but not always, this value will correspond with the O->T connection size
in the connection manager. Please note that it is possible to support multiple assemblies for
connection points by supporting process data remapping.
Network Object (03h) - CIP Port Configuration Object (0Dh)
CIP routing can be enabled by instance attribute #17 of the Host EtherNet/IP object. Each in-
stance of this object corresponds to an instance of the CIP Port object (F4h).
Please note that a CIP port does not necessarily correspond to a Physical port. The two network
connectors on the two-port Anybus CompactCom correspond to a single CIP routable port. De-
vices with a single CIP port are not required to support the Port Object, but the Communication
Adapter device profile does require support for this object.
Anybus CompactCom 40 EtherNet/IP Transparent Ethernet Network Guide
125 (144)
SCM-1202-019-EN 1.6