Anybus CompactCom 40 EtherNet/IP
Doc.Rev. 1.5
Chapter 8
8. CIP Objects
8.1 General Information
This chapter specifies the CIP-object implementation in the module. These objects can be accessed
from the network, but not directly by the host application.
Mandatory Objects:
• “Identity Object (01h)” on page 63
• “Message Router (02h)” on page 66
• “Assembly Object (04h)” on page 67
• “Connection Manager (06h)” on page 70
• “Parameter Object (0Fh)” on page 74
• “DLR Object (47h)” on page 77
• “QoS Object (48h)” on page 78
• “TCP/IP Interface Object (F5h)” on page 87
• “Ethernet Link Object (F6h)” on page 90
CIP Energy Objects:
• “Base Energy Object (4Eh)” on page 79
• “Power Management Object (53h)” on page 81
Optional Objects:
• “Port Object (F4h)” on page 85 (Optional)
Vendor Specific Objects:
• “ADI Object (A2h)” on page 83
It is possible to implement additional CIP-objects in the host application using the CIP forwarding func-
tionality, see “EtherNet/IP Host Object (F8h)” on page 161 and “Command Details: Process_CIP_-
Object_Request” on page 166.
Unconnected CIP routing is supported, which means that a message can be sent to a device without first
setting up a connection.
To Next Page
Loading...