Rockwell Automation 160-DN2 160-DN2 DeviceNet Communication Module FRN 3.xx - Manual (Page 63)

Publication 0160-5.18 - June 2003
Using 160-DN2 with DeviceNet Scanner 6-25
Using Explicit Messaging
(Continued) The following table identifies the number of Explicit Messages that
can be executed at a time.
ControlLogix Message Requests and Responses
Scanner
Messages at
One Time
Refer To
1756-DNB 5 Figure 6.17
Box Description
➊
Message Type
The message type must be CIP Generic.
➋
Service Type
This box contains the type of function that the message will perform. The default
function is Custom.
➌
Service Code
The service code is the requested DeviceNet service, entered as a hex value.
Available services depend on the class and instance that you are using. Refer to
Appendix B .
➍
Class
The object class is a DeviceNet class, entered as a hex value. Refer to
Appendix B
for available classes.
➎
Instance
The object instance is determined by the selected DeviceNet class. Refer to
Appendix B for available instances.
➏
Attribute
The object attribute is a class or instance attribute, entered as a hex value. Refer to
Appendix B for available classes.
➐
Source Element
This box contains the name of the tag for any service data to be sent from the
scanner to the module and drive.
➑
Source Length
This box contains the length (in bytes) of the tag used for the Source Element.
➒
Destination
This box contains the name of the tag that will receive service response data from
the module and drive.
➓
Path
The path includes the following:
• Name of the DeviceNet scanner.
• Communication port on the front of the 1756-DNB scanner. Always 2.
• Node address of the 160-DN2 module. This is set with switches or parameters in
the module.
Tip: Click Browse to find the path or type in the name of a module that you
previously mapped. For proper set up, refer to ControlLogix online Help.