
Chapter 1
CIP services
18
Rockwell Automation Publication 1756-PM020F-EN-P - January 2019
Use the CIP service format for CIP-explicit messages and to deliver
connected or unconnected messages to the controller. The mechanisms for
doing this are CIP-network specific. For example, for EtherNet/IP access, see
the
CIP Networks Library, Volume 1 unconnected, Chapter 3 and the
EtherNet/IP Adaptation of CIP, Volume 2
.
For more information about using the EtherNet/IP network to communicate
with the controller, see
http://www.rockwellautomation.com/rockwellautomation/solutions-services/
oem/design-develop-deliver/information-enabled-solutions.page
. We
recommend using connected messaging whenever possible. Be aware that the
information presented here does not replace the need to be properly
authorized by ODVA, Inc. to use the Ethernet/IP protocol.
The examples used throughout the manual show only the explicit message
protocol elements and
not
the network-specific details. The exception to this
is the information in
CIP Over the Controller Serial Port
, which shows more
details of unconnected versus connected explicit messages, and of the
PCCC and DF1 layers. All
responses
take the general form as shown in the
table.
Message Response
Field
Description
Reply Service
The request service with the MSB set to 1.
00
Reserved.
General Status
An 8-bit value indicating success or error status. The CIP Networks Library, Volume 1,
Appendix B has a list of the general status codes. The object class specified in the request
path defines any extended status codes for each service defined for that class.
Extended Status Size
An 8-bit value that indicates how many 16-bit values follow in the additional status field.
For status=0 (success) this is 0.
Extended Status
The array of 16-bit values that describe the general status code. Only present when the size
field is > 0.
Reply Data
The data returned by the service request. This field only appears in the message frame if a
service has service-specific data.
See also
CIP Over the Controller Serial Port
on
These sections describe the inherent mode of communication and addressing
of the Logix 5000 controller. The following vendor-specific services operate
on tags in the controller using symbolic addressing:
•
Read Tag Service (0x4c)
•
Read Tag Fragmented Service (0x52)
•
Write Tag Service (0x4d)
•
Write Tag Fragmented Service (0x53)
Services Supported by
Logix 5000 Controllers