
2105 Interface Module
Section 3 Modbus Protocol and 2100 Output
3-2
register locations. A list of the 2100 register addresses, and what
parameters are held where, is available in Section 3.6.
By accessing these registers you can obtain the current value of
whatever parameter you desire. The reading(s) can then be dis-
played or stored wherever you designate as a destination; for
example, a process control computer.
Note
Level, flow, velocity, and temperature data is stored in metric
units only.
Not all registers are limited to read-only data storage. You can
also use some registers for control purposes. For example, by
writing a “1” value to register 24 (“Identify Module” register), you
will tell a 2100 module to light the LED on the front of the
module. See Table 3-2 for register definitions for individual
modules, including read/write designation.
3.2.1 Establishing
Communication
There are several different communications protocols supported
in the 2100 series that require auto-baud rate detection. Because
of this, each time a modbus connection is made, the module uses
a polling mechanism to repeatedly send a command until a
response is received. It may take up to 20 command retries
before the module has identified the baud rate and a response is
received.
Modbus Protocol Setup
The communication settings for Modbus protocol are as follows:
Baud: 9600
Bits: 8
Parity: None
Stop Bits: 1
3.2.2 Module Addressing
When connecting to a site via a Modbus OPC server, you use a
dedicated line of communication to that module or stack from the
OPC server, which can be a dedicated communications cable
(direct connection) or a dedicated phone number (modem).
When you are using a direct connection, you are dedicating a
specified COM port on the computer, and that COM port deter-
mines the site to which you are connecting.
When you are using a modem, the dedicated line is defined by
the site's phone number.
If you connect more than one 2100 Series module at a site, the
Modbus OPC server, while using the shared communication line
for all of the modules within the network, must have some way to
differentiate between the modules. When sending a command to
a specific module, the command has an address field. This allows
the server software to talk to, as well as control, the specified
module, while ignoring other modules in the same stack or site.
Summary of Contents for 2105
Page 2: ......
Page 4: ......
Page 10: ...2105 Interface Module Table of Contents viii ...
Page 58: ...2105 Interface Module Section 2 Installation and Operation 2 40 ...
Page 70: ...2105 Interface Module Section 3 Modbus Protocol and 2100 Output 3 12 ...
Page 74: ...2105 Interface Module Section 4 Maintenance 4 4 ...
Page 77: ...2105 Interface Module Appendix A Replacement Parts List A 3 Drawing 602002586 ...
Page 78: ...2105 Interface Module Appendix A Replacement Parts List A 4 Drawing 602002586 ...
Page 79: ...2105 Interface Module Appendix A Replacement Parts List A 5 ...
Page 80: ...2105 Interface Module Appendix A Replacement Parts List A 6 ...
Page 82: ...2105 Interface Module Appendix A Replacement Parts List A 8 ...
Page 84: ...2105 Interface Module Appendix A Replacement Parts List A 10 ...
Page 94: ...2105 Interface Module Appendix C Material Safety Data Sheets C 8 ...
Page 98: ......