Owner information
The ControlLogix architecture makes it possible for more than one controller to communicate and own I/O modules. Input modules can have multiple owners; however, output modules are restricted to one owner. The output module’s firmware enforces this restriction to make sure that an output module is owned by only one controller.
There is a noted difference in controlling input modules versus controlling output modules.
Input modules | Owner Connection An input module is configured by a controller that establishes a connection as an owner. This configuring controller is the first controller to establish an owner connection. Once an input module has been configured (and owned by a controller), other controllers may establish owner connections to that module also. That way additional owners can continue to receive multicast data if the original owner controller breaks its connection to the module. All other additional owners must have the identical configuration data and identical communications format that the original owner controller used, otherwise the connection attempt is rejected.Listen-Only Connections Once an input module has been configured (and owned by a controller), other controllers may establish Listen-Only connections to that module. These controllers can then get multicast data while another controller owns the module. If all owner controllers break their connection to the input module, all controllers with Listen-Only connections no longer receive multicast data. Requested Packet Interval The module’s owner controller(s) determines the RPI. If a Listen-Only connection is established, the RPI for that connection cannot be faster than the fastest RPI configured for all owner controllers. If you configure a listen-only connection to a FLEX I/O module, the RPI should be set to the same value as the owner connection. If you do not use the same RPI value, then when scheduling the network with RSNetWorx, any running owner control system will be interrupted. Electronic keying does not work properly for Listen-only connections when the owner is configured to disable keying. |
Output modules | Owner Connections An output module is configured by a controller that establishes a connection as an owner; however, only one owner connection is allowed for output modules. If another controller attempts to establish an owner connection, the connection attempt is rejected. Listen-Only Connections Once an output module has been configured (and owned by one controller), other controllers may establish Listen-Only connections to that module. These controllers can then get 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. Requested Packet Interval The module’s owner controller determines the RPI. If a Listen-Only connection is established, the RPI for that connection cannot be faster than the fastest RPI configured for the owner controllers If you configure a listen-only connection to a FLEX I/O module, the RPI should be set to the same value as the owner connection. If you do not use the same RPI value, then when scheduling the network with RSNetWorx, any running owner control system will be interrupted. Electronic keying does not work properly for Listen-only connections when the owner is configured to disable keying. |
Provide Feedback