THE CIP NETWORKS LIBRARY
Volume 1
Common Industrial Protocol (CIP™)
Edition 3.3
November, 2007
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
The CIP Networks Library
Volume 1: Common Industrial Protocol (CIP™)
Publication Number: PUB00001
Copyright © 2001 through 2007 Open DeviceNet Vendor Association, Inc. (ODVA). All rights
reserved. For permissions to reproduce excerpts of this material, with appropriate attribution to
the author(s), please contact ODVA at:
Open DeviceNet Vendor Association, Inc.
4220 Varsity Drive, Suite A, Ann Arbor, MI 48108-5006 USA
TEL
FAX
EMAIL
WEB
1-734-975-8840
1-734-922-0027
odva@odva.org
www.odva.org
The right to make, use or sell product or system implementations described herein is granted
only under separate license pursuant to a Terms of Usage Agreement or other agreement.
Terms of Usage Agreements for individual CIP Networks are available, at standard charges,
over the Internet at the following web sites:
www.odva.org - Terms of Usage Agreements for CompoNet, DeviceNet, EtherNet/IP
and CompoNet along with general information on CIP Networks and the association of
ODVA
www.controlnet.org - Terms of Usage Agreement for ControlNet along with general
information on ControlNet and ControlNet International.
Warranty Disclaimer Statement
Because CIP Networks my be applied in many diverse situations and in conjunction with
products and systems from multiple vendors, the user and those responsible for specifying CIP
Networks must determine for themselves its suitability for the intended use. The Specifications
are provided to you on an AS IS basis without warranty. NO WARRANTIES, EXPRESSED
OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE ARE BEING
PROVIDED BY THE PUBLISHER, ODVA AND/OR CONTROLNET
INTERNATIONAL. In no event shall the Publisher, ODVA and/or ControlNet International,
their officers, directors, members, agents, licensors or affiliates be liable to you or any
customer for lost profits, development expenses or any other direct, indirect incidental, special
or consequential damages.
ControlNet and ControlNet CONFORMANCE TESTED are trademarks of ControlNet
International, Ltd.
CIP, DeviceNet, DeviceNet CONFORMANCE TESTED, DeviceNet Safety, DeviceNet Safety
CONFORMANCE TESTED, CompoNet and CompoNet CONFORMANCE TESTED,
EtherNet/IP CONFORMANCE TESTED, EtherNet/IP Safety CONFORMANCE TESTED,
and CIP Safety are trademarks of Open DeviceNet Vendor Association, Inc.
EtherNet/IP is a trademark of ControlNet International under license by Open DeviceNet
Vendor Association, Inc.
All other trademarks referenced herein are property of their respective owners.
– ii –
Edition 3.3
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
The CIP Networks Library: Volume 1
Common Industrial Protocol (CIP™)
Revisions
Preface
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
Appendix A
Appendix B
Appendix C
Appendix D
Table of Contents
- Summary of Changes in this Edition
- Organization of CIP Networks Specifications
- The Specification Enhancement Process
- Introduction to the Common Industrial Protocol
- Messaging Protocol
- Communications Objects
- CIP Object Model
- Object Library
- Device Profiles
- Electronic Data Sheets
- Physical Layer
- Indicators and Middle Layers
- Bridging and Routing
- Explicit Messaging Services
- Status Codes
- Data Management
- Engineering Units
– iii –
Edition 3.3
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
This page is intentionally left blank
– iv –
Edition 3.3
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
Revisions
The CIP Networks Library Volume 1: The Common Industrial Protocol Edition 3.3 contains
the following changes from Edition 3.2. Please see the change bars on the pages noted here for
specific modifications. Note: Some of the pages within the ranges noted may not contain any
changes.
Chapter
1-7.47
3-5.6.1
3-5.5.1.10
C-1.5
7-3.6.7.2
7-3.6.7.2.3
C-1.4.2
5-5
5-42
5-5.3
6-7
6-33
6-33.1
6-33.2
6-7
6-42
C-2.1.2
5-48.4
5-48.4.1
5-48.4.2
5-48.4.3
5-48.4.4
5-48.4.5
5-48.4.7
5-48.4.8
5-48.4.9
5-48.4.10
5-48.4.11
5-48.4.12
5-48.4.13
5-48.4.14
Pages
1-19
3-80
3-63
C-14
7-49
7-50
C-8
5-43
5-351
5-45
6-21
6-180
6-180
6-18
6-21
6-292
C-18
5-567
5-567
5-569
5-571, 572
5-572
5-572
5-573
5-573
5-573
5-574
5-574
5-574
5-575, 576
5-576
Reason for Change
Add new extended status code and definition of scheduled network
• Add new definition to table
• Add new extended error code to Table 3-5.29
Connection Path Enhancement
• Modify three cells in Table 3-5.13
• Add new hierarchy example
AssemN Optional Size Field
• Change Size from Required to Optional in Table 7-3.24
• Add new paragraphs to describe when the size field is not present
Allow 32-bit Logical Instances and Connection Points
• Modify 32-bit logical address to indicate when allowed for use
• Change Assembly Instance ID ranges in Table 5-5.2
• Change reserved instance ID range in Table 5-42.1
Assembly Object Member Service Support
• Update Description of Service field for Get_Member & Set_Member services and
make Set_Member service optional at the instance level.
Drop ControlNet from the ControlNet Programmable Controller Profile
• Remove ControlNet from the name in Table 6-7.1
• Remove ControlNet from the name of the profile
• Remove ControlNet and remove reference to scheduled originator from first paragraph
• Modify caption of Table 6-33.1, remove Scheduling Object and remove ControlNet
• Remove ControlNet from first paragraph and remove Scheduling Object from Table 6-
from last paragraph
33.2
Add Enhanced Mass Flow Controller Device Profile
• Add new device to Device Type list
• Add new section.
Add UCD-4 Unicode Encoding Support to STRINGI
• Add last line to Table C-2.3
Connection Configuration Object Get_Attributes_All class level response data
• Change Set_Attributes_All to N/A for class level
• Add new text and table for Get All response – Class level
• Add new text to first paragraph and changes to Table 5-48.12
• Add new text to first paragraph and changes to Table 5-48.15
• Add new text to first paragraph and changes to Table 5-48.16
• Add new text to first paragraph and changes to Table 5-48.17
• Remove Error Table
• Remove Error Table
• Remove Error Table
• Remove Error Table
• Add new text to first paragraph and changes to Table 5-48.23
• Add new text to first paragraph and changes to Table 5-48.26
• Add new text to first paragraph and changes to Table 5-48.28
• Add new text to first paragraph and changes to Table 5-48.30
– v –
Edition 3.3
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
3-7.3
5-1
5-46.1
5-47.9
5-47.13.1.10.1
5-47.13.1.10.2
6-2.1
6-7
7-3.6.4
7-3.6.10
8-1
9-1
B-1
4-4
4-4.1
4-5.1
4-5.2
4-9.2
4-9.2.1.1
4-9.2.1.2
A-4.1
A-4.1.1
A-4.2.1
5-48-2
5-48.4.1
5-48.4.2
3-7.3
5-1
5-2.2
5-14.2.1.1
6-7
7-3.6.4
7-3.6.5
7-3.6.10
B-1
3-5.5.1.10.1
3-6.1.4
5-12.5.1.2
5-48.2.2.1
5-48.2.2.4
C-all
3-89
5-22
5-403
5-547
5-552
5-552
6-13
6-20
7-44
7-70
8-3
9-3
B-4
4-4
4-5
4-9
4-9, 10
4-19
4-21
4-22
A-7
A-7, 8
A-9
5-562
5-569
5-571
3-89, 90
5-22
5-24
5-99
6-21
7-44
7-45
7-69
B-4
3-65
3-83
5-88
5-563
5-564
-
CompoNet Hooks
• Change Port Type attribute access from Set to Get
• Add value 200 = CompoNet
• Add 2 CompoNet objects to Table 5-5.1
• Revise wording to allow use with any CIP network
• Add CompoNet to Table 5-47.1
• Add CompoNet to Table 5-47.5
• Add CompoNet to Table 5-47.6
• Numerous changes to Table 6-2.2
• Add CompoNet Repeater to the Device Profile list in Table 6-7.1
• Add CompoNet to the classification list
• Add CompoNet to the Port Type list
• Remove examples of CIP networks (last sentence)
• Remove examples of CIP networks (last sentence)
• Define status codes 23 and 24 (previously reserved)
Get_All/Set_All Service Data Size Rules and Related Issues
• Move definition of the term “default” from this section to 4-4.1
• Add clarification for default value
• Numerous changes
• Remove words in first paragraph and replace last paragraph
• Numerous changes
• Numerous changes to items 1 and 2
• Removed subsections 4-9.2.1.2.2 (entirely) and 4-9.2.1.2.3 (partially)
• Clarified wording of what is returned in the service reply
• Numerous changes
• Numerous changes
EF Protocol Safety Hooks
• Add three new instance attributes (20-22) to Table 5-48.3
• Removed names of Safety Parameters, corrected capitalization and added additional
safety parameters to end of Get_Attributes_All Response Data
• Removed names of Safety Parameters, corrected capitalization and added additional
safety parameters to end of Set_Attributes_All Response Data
Modbus Integration Hooks
• Add new protocols to Attribute 1 and change TCP/IP to EtherNet/IP, change
Description & Semantics of attribute 4 in Table 3-7.3
• Add Modbus Object to list of defined objects
• Add attribute 18 to Identity Object instance attribute list
• Modify Bits 4 & 5 description, add bit 14 definition in Table 5-14.9
• Add CIP Modbus device type to list of defined devices
• Add ModbusSL & ModbusTCP to Device Classifications list
• Changed Data Type of Scaling Offset and added footnote, both in Table 7-3.22
• Changed Port name to Conditional and added footnote, both in Table 7-3.38
• Added ModbusSL & ModbusTCP to port types list
• Modified description of Port Name field
• Define General Status Code 2B
Typographical errors/corrections
• Remove extra “the” from the first sentence
• Corrected caption of Table 3-6.1 to say “32-bit…”
• Changed “Discrete” to “Analog”
• Corrected reference to a table in Chapter 3. Table was no longer at that reference due to
revisions to the chapter. Changed reference to something more distinct and less likely
to change over time.
• Removed extra word (“a”) from the second sentence of the second paragraph
• Replaced all figure/table captions and references
– vi –
Edition 3.3
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
Preface
Organization of the CIP Networks Specifications
Today, four networks - DeviceNet™, ControlNet™, EtherNet/IP™ and CompoNet™ - use the
Common Industrial Protocol (CIP) for the upper layers of their network protocol. For this
reason, the associations that manage these networks - ODVA and ControlNet International -
have mutually agreed to manage and distribute the specifications for CIP Networks in a
common structure to help ensure consistency and accuracy in the management of these
specifications.
The following diagram illustrates the organization of the library of CIP Network specifications.
In addition to CIP Networks, CIP Safety™ consists of the extensions to CIP for functional
safety.
– vii –
Edition 3.3
ODVA & ControlNet International Ltd.
The CIP Networks Library Volume 1: Common Industrial Protocol
This common structure presents CIP in one volume with a separate volume for each network
adaptation of CIP. The specifications for the CIP Networks are two-volume sets, paired as
shown below.
The EtherNet/IP specification consists of:
Volume 1: Common Industrial Protocol (CIP™)
Volume 2: EtherNet/IP Adaptation of CIP
The DeviceNet specification consists of:
Volume 1: Common Industrial Protocol (CIP™)
Volume 3: DeviceNet Adaptation of CIP
The ControlNet specification consists of:
Volume 1: Common Industrial Protocol (CIP™)
Volume 4: ControlNet Adaptation of CIP
The CompoNet specification consists of:
Volume 1: Common Industrial Protocol (CIP™)
Volume 6: CompoNet Adaptation of CIP
The specification for CIP Safety™ is distributed in a single volume:
Volume 5: CIP Safety
The specification for integrating Modbus Devices is distributed in a single volume:
Volume 7: Integration of Modbus Devices into the CIP Architecture
Specification Enhancement Process
The specifications for CIP Networks are continually being enhanced to meet the increasing
needs of users for features and functionality. ODVA and ControlNet International have also
agreed to operate using a common Specification Enhancement Process in order to ensure open
and stable specifications for all CIP Networks. This process is on going throughout the year for
each CIP Network Specification as shown in the figure below. New editions of each CIP
Network specification are published on a periodic basis.
New Specification
Edition Published
Members Develop Specification
Enhancements in Special Interest
Groups (SIGs)
Conformance Tests
Updated
Member Review and
Comment Period
Technical Review Board
Reviews and Approves
Specification Enhancements
Specification Enhancements
Integrated in New Revisions
of Publications
– viii –
Edition 3.3
ODVA & ControlNet International Ltd.