12BAppendix D: Example Messages 84BGeneral Information
111
Appendix D: Example Messages
General Information
The DeviceNet messaging protocol is based on hexadecimal (base 16) math, rather than decimal
(base 10) math. The examples in this appendix, designed to illustrate how DeviceNet messages
are generated and interpreted, assume a basic understanding of hexadecimal math.
In the actual application of DeviceNet communications, the messaging process is typically
automated using an interface software program; therefore, manual calculation or interpretation of
the messages is not required. Typical interface programs require only the input of specific class
codes, instance IDs, attribute IDs, and any required data variable(s).
Explicit Messaging
Explicit messaging connections utilize a direct request/response format that enables you to access
any attribute data. Explicit messaging typically is used for the setup, configuration, and
calibration of your device. Refer to Explicit Messaging Connections, page 46, for more
inform
ation.
Three examples of explicit m
essages are described on pages 112 to 117. These messages illustrate
how to request inform
ation on the Vendor ID and interpret the network’s response. The following
information applies for each exam
ple:
• The examples depict explicit messaging.
• The examples are all nonfragmented message strings.
• The node address of the MKS device (the Slave) is 05.
• The node address of the master device is 01.
• Spaces are shown for clarity only. Do not enter spaces in the actual message string.
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com
To Next Page
Loading...
Need help?
General
