Details
Minor
Description
Today, CIP objects that are built-in in the EtherNet/IP core (e.g. the Identity Object, TCP/Interface Object, etc.) cannot be extended by the host application in terms of adding additional attributes to the object's attribute list.
The host application shall be enabled to "register" vendor-specific instance attributes in the discrete vendor-specific attribute range 0x64 - 0xC7.
- Design
- Key Features and Limitations
- Attribute Capacity: Up to 32 attributes per object class can be registered at both, class and instance level.
- Reserved Range: Registration is strictly limited to the reserved range of attribute IDs [0x64 - 0x83].
- Registration Levels: Attributes can be registered at either the object class level or at instance level (all existing instances).
- Scope of Registration: Attributes can only be registered for existing built-in object classes
- Lifetime of Registration: After a power cycle or stack reset as per HIL_CHANNEL_INIT_REQ, all vendor attribute registrations are removed.
- Behavior: When a CIP service request is received on the network, the host will be notified with an EIP_OBJECT_CL3_SERVICE_IND indication under the following conditions:
- The request targets an existing built-in object, either at the class level or any existing instance.
- The request references an attribute identifier that has been previously registered using the EIP_OBJECT_REGISTER_VENDOR_ATTRIBUTE_REQ service (this service).
- In case an object instance is addressed (instance ID > 0), the addressed instance does exist.
- The forwarding is independent of the CIP service code received with the request, all CIP services will be forwarded
- Key Features and Limitations
- Implement for all products
- Document in API manual
- New section "Registering a Vendor-Specific Attribute for a Built-In Object"
- Define & Implement new testcase
- /svn/Testframework/Tests/EthernetIP/branch/EIP_V3/EipApi/Adapter/EIP_Slave_SoftMaster_RegisterUserVendorAttribute.py