Allen-Bradley ControlNet Compact GuardLogix 1769, User Manual, Page: 62 / 100

Chapter 4 Control I/O
Choose the Type of Ownership for a Module
Table 13 - Module Ownership
Module Type Controller Desired Function Required Connection Type
Input module Does not own the module Owner, such as not listen-only
Owns the module Maintain communication with the module if
it loses communication with the other
controller.
Owner, such as not listen-only
Use the same configuration as the other
owner controller.
Stop communication with the module if it
loses communication with the other
controller.
Listen-only
Output module Does not own the module Owner, such as not listen-only
Owns the module Listen-only
Controlling input modules differs from controlling output modules.
Table 14 - Module Ownership Control
Module Type Ownership Description
Input modules Owner The controller that establishes an owner connection to an input module configures that module. This configuring
controller is the first controller to establish an owner connection.
Once a controller owns and configures an input module, other controllers can establish owner connections to that
module. This lets additional owners continue to receive multicasted data if the original owner-controller’s
connection to the module breaks. All other additional owners must have the identical configuration data and
communication format as the original owner controller, or the connection attempt is rejected.
Listen-only Once a controller owns and configures an input module, other controllers can establish a listen-only connection
to that module. These controllers can receive multicast data while another controller owns the module. If all
owner controllers break their connections to the input module, controllers with listen-only connections no longer
receive multicast data.
Output modules Owner The controller that establishes an owner connection to an output module configures that module. Only one owner
connection is allowed for an output module. If another controller attempts to establish an owner connection, the
connection attempt is rejected.
Listen-only Once a controller owns and configures an output module, other controllers can establish listen-only connections
to that module. These controllers can receive multicast data while another controller owns the module. If the
owner controller breaks its connection to the output module, all controllers with listen-only connections no longer
receive multicast data.
62 Rockwell Automation Publication CNET- UM001E-EN-P - June 2016