Emerson Process Management MICRO MOTION 2400S - Manual (Page 29)

Configuration and Use Manual 21
Requ
ired Co
nfi
g
u
ratio
n
O
ptio
nal
Con
fig
uration
Using the T
rans
m
itte
r
Us
ing a De
vice
Net T
o
ol
Chapter 5
Using a DeviceNet Tool
5.1 Overview
A customer-supplied DeviceNet tool can be used to communicate with the Model 2400S DN
transmitter. This chapter provides basic information on using a customer-supplied DeviceNet tool.
However, because there are a variety of DeviceNet tools available, this chapter does not provide
detailed information for using any one tool. For detailed information on your DeviceNet tool, see the
documentation supplied with the tool.
5.2 Connecting to the Model 2400S DN transmitter
To connect to the Model 2400S DN transmitter:
1. Default connection values for this transmitter are as follows:
• DeviceNet node address = 63
• Baud rate = 125 kBaud
If required, use the digital communications hardware switches on the device to set the
DeviceNet node address and baud rate for this transmitter. To do this, see Sections 8.10.1 and
8.10.2.
2. Connect to the network where the transmitter is installed.
3. Using the same methods that you use for other DeviceNet devices, establish a connection to
the Model 2400S DN transmitter, using the appropriate node address and baud rate.
5.3 Using the DeviceNet device profile
All DeviceNet devices employ a device profile with an object-instance-attribute structure.
In general, process and configuration data is stored in attributes, and operational functions are
performed by using services or setting attributes to specific values.
Two standard services are used to read or write single attributes:
• The Get Single Attribute service (0x0E) performs an explicit read and returns a single value
from the transmitter.
• The Set Single Attribute service (0x10) performs an explicit write and writes a single value to
the transmitter.
In this manual, these two services are referenced as the Get and Set services.
Other services are used to reset values to 0 , start or stop calibrations, to acknowledge alarms, etc.
These services are identified by name and by service code (a hexadecimal label).
Input assemblies are used to publish multiple values to the DeviceNet bus. A summary of the input
assemblies is provided in Table 7-2. Output assemblies can be used to read data from the DeviceNet
bus or to perform totalizer and inventory control. Summaries of the output assemblies are provided in
Tables 7-9 and 9-1.