CIP identity structure

The CIP identity structure provides information about an application in the format of an CIP identity object. RSLinx Classic maintains an identity object for each registered application (see DTL_CIP_APPLICATION_REGISTER) so that other devices in a CIP system can recognize the presence of the application and gain some information about it. This structure is defined in DTL.H:

The DTL_CIP_IDENTITY structure:

Parameters

vendor

specifies the CIP Vendor ID for the application provider. If no vendor ID was assigned by Allen-Bradley or by the Open DeviceNet Vendor Association (ODVA), the value zero should be used.

prod_type

specifies the CIP Product Type for the application. Typically, either zero (

Generic Device

) or 11 (

Software

) should be used.

prod_code

specifies the Product Code for the application. It should either be zero, or it should map to the product's catalog (bulletin) number.

major_rev

specifies the major revision or version number of the product, and must fall in the range of 1-127. Alternatively, zero can be used to indicate an

Unknown

revision number.

minor_rev

specifies the minor revision or version number of the product, and must fall in the range of 1-255. Alternatively, zero can be used to indicate an Unknown revision number.

status

is described in the

Logix 5000

Data Access Programming Manual (publication 1756-PM020). It should almost always be given a value of zero.

serial_num

specifies the serial number of this particular instance of the application. It can be assigned as desired, although along with the Vendor ID it is intended to be a unique number (for a particular vendor) in a CIP system.

name_len

specifies the number of characters in the name.

name

must be up to 32 ASCII characters in the range 0x20 to 0x7E specifying the name of the product or application. There is no trailing NULL.