
Publication 1769-UM001B-EN-P - October 2002
Explicit Messaging Application Examples B-7
The following correlates the CIP Generic message terminology with
DeviceNet command terminology and illustrates the values needed
specifically for the Get 1769 I/O Configuration Size message:
The following ladder logic program is an example of the MSG logic
needed to initiate an explicit message to the scanner/adapter. This
MSG instruction logic is specifically for the Get 1769 I/O Module
Configuration Size message. Assume the 1756-DNB scanner is in slot 1
and the Logix5550 controller is in slot 0.
Values (Hexadecimal) DeviceNet Terminology CIP Generic Terminology
e Service
1
Service Code
30c Class
2
Object Type
10 (decimal) Instance
3
Object ID
17 Attribute
4
Object Attribute
1 Service specifies the type of request being delivered. “e” hexadecimal is a “Single Parameter Read”.
2 Class specifies the desired DeviceNet class. “30c” hexadecimal is the class code for the object representing
1769 I/O.
3 Instance represents the slot number of the I/O module from which we want the configuration size.
“10” decimal in this example is the analog output module in slot 10.
4 Attribute identifies the specific characteristics of the object towards which the transaction is directed.
“17” hexadecimal means Module Configuration Size.
Comentarios a estos manuales