Anybus CompactCom 40 Network Manual page 117

Appendix F: Conformance Test Guide
This means that all requests to CIP objects and instances not listed in the CIP objects section
need to be handled by responses to the Process_CIP_Request command if CIP Forwarding is
enabled.
Enabling CIP Forwarding can be necessary when users support device profiles defined by Vol-
ume 1 of the CIP Network Libraries. Additionally, vendors may define and support objects and
Assembly Object Instances that are not specified in the CIP network specification as long as
those objects and Assembly Object Instances are in the vendor specific range.
CIP defined device profiles define which object(s) instance(s) attributes(s), and Instances of the
Assembly Object need be supported by a device. Additionally, mandatory services and behav-
iors are defined. Chapter 6 of Volume 1 CIP Network Libraries details device profiles. The de-
fault profile supported by the Anybus CompactCom is Generic Device, Keyable. This device
profile, and some other profiles do not require any additional objects or assembly instances to
be supported making it not necessary to enable CIP forwarding.
Responding properly can mean different things for different requests at different times. The fol-
lowing list gives advice how to reduce the complexity.
• Decide which Object/Instance/attributes combinations will be implemented. Consult specifi-
cations to ensure that mandatory/optional/vendor specific combinations are correct.
• Decide which services are supported for the implemented combinations. Consult specifica-
tion to ensure that mandatory/optional/vendor specific services are implemented properly.
• Verify that proper application behavior is provided for the correct interaction of the imple-
mented services and paths.
• Provide the correct error response for all paths not supported by application.
CIP status code 0x05 (path destination unknown) will be reported, when the application re-
turns any of the following Anybus CompactCom error codes: Unsupported Object (3), Un-
supported Instance (4). Consult the CIP network libraries Vol1 appendix B for status codes,
and the section on CIP Objects in the Anybus CompactCom EtherNet/IP Network Guide
for a translation of CIP error codes to Anybus CompactCom error codes.
• Provide the correct error response for all unsupported commands.
CIP status code 0x08 service not supported will be reported when the application returns
the Anybus CompactCom error code Unsupported Command (5). Consult the CIP network
libraries Vol1 appendix B for status codes, and the CIP objects chapter in the Anybus Com-
pactCom EtherNet/IP Network Guide for a translation of CIP error codes to Anybus Com-
pactCom error codes.
• Provide error checking for all commands that modify variables, and respond with the cor-
rect CIP defined error code. Consult the CIP network libraries Vol1 appendix B for status
codes, and the CIP Objects chapter in the Anybus CompactCom EtherNet/IP Network
Guide for a translation of CIP error codes to Anybus CompactCom error codes.
Please consult the profile requirements, services, and behaviors as well as the object definitions
specified in the CIP Network Libraries.
EtherNet/IP Host Object (F8h) - Attribute #12 - Enable Parameter Object
The purpose of the CIP Parameter Object is to provide a uniform interface for device configura-
tion. EtherNet/IP requires one instance of the parameter object per configurable parameter. A
request to the CIP parameter object is converted into a request to the Host Application Data ob-
ject. It is possible to disable access to the Parameter Object by responding FALSE to this re-
quest. The required and optional instance attributes are listed in table 5A-14.7 of The CIP
Network Libraries Volume 1. If the object is disabled the parameter object must be removed
from the list of supported objects in the STC file.
Anybus CompactCom 40 EtherNet/IP Transparent Ethernet Network Guide
115 (144)
SCM-1202-019-EN 1.6