14 Rockwell Automation Publication 5000-UM005B-EN-P - November 2015
Chapter 1 Analog I/O Module Operation in a Logix5000 Control System
Because part of module configuration includes a slot in the 5069 Compact I/O
system, the owner-controller checks for the presence of a module there. If a
module is detected, the owner-controller sends the configuration. One of the
following occurs:
• If the configuration is appropriate to the module detected, a connection is
made and operation begins.
• If the configuration is not appropriate to the module detected, the data is
rejected and the Logix Designer application indicates that an error
occurred.
The configuration can be inappropriate for many reasons. For example, a
mismatch in electronic keying that prevents normal operation.
The owner-controller monitors its connection with a module. Any break in the
connection, for example, the loss of power to the 5069 Compact I/O system,
causes a fault. The Logix Designer application monitors the fault status tags to
indicate when a fault occurs on a module.
Connection Types Available with 5069 Compact I/O Analog I/O Modules
When configuring a 5069 Compact I/O analog I/O module, you must define the
module. Connection is a required parameter in the Module Definition. The
choice determines what data is exchanged between the controller and the
module.
Table 2 describes the connection types that you can use with 5069 Compact I/O
analog I/O modules.
Table 2 - Connections - 5069 Compact I/O Analog I/O Modules
Connection Type
Description
5069 Compact I/O Analog Input
Modules
5069 Compact I/O Analog Output
Modules
Data with Calibration The module returns the following to the
owner-controller:
• General fault data
• Input data
• Calibration data
The module returns the following to the
owner-controller:
• General fault data
• Output data
• Calibration data
Data The module returns the following to the
owner-controller:
• General fault data
• Input data
The module returns the following to the
owner-controller:
• General fault data
• Output data
Listen Only When a Listen Only connection is used, another controller owns the module.
A controller that makes a Listen Only connection to the module does not write
configuration for the module. It merely listens to the data exchanged with the owner-
controller.
IMPORTANT: If a controller uses a Listen Only connection, the connection must use the
Multicast option. For more information on Listen Only connections, see
Listen Only
Mode on page 20. In this case, all other connections to the module, for example, the
connection to the owner-controller must also use the Multicast option.
To Next Page
Loading...
Need help?
General
