Updating Module Configuration

Configuration data is stored in the ControlLogix "owner" controller(s) and is sent to the module when the IO connection is initially established, when the module connection is re-established after Inhibit, and when the module is sent a Reset or Reconfigure message.
Important:
When a module has multiple "owners", both controllers must have the same Configuration data for the module. When changing Configuration with multiple owners, the module connection must be inhibited to prevent other owners from receiving potentially erroneous data. Refer to the "User’s Manual" and associated Rockwell Automation documentation for the detailed procedures for handling multiple owners.
Use of the AOP for generating the Configuration should ensure valid Configuration data. However, it’s also possible to change Configuration data manually or programmatically. If an invalid configuration is sent to the module, a connection error will occur. When you download a module configuration to a controller, the controller attempts to establish a connection to each module in the configuration. Because part of module configuration includes a slot number in the local or remote 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 helps prevent normal operation.
The owner-controller monitors its connection with a module. Any break in the connection, for example, the loss of power to the system, causes a fault. The Logix Designer application monitors the fault status tags to indicate when a fault occurs on a module.
For more information, see Module Data Quality Reporting in Compact 5000 I/O Digital Modules documentation, PN 5069-UM004 for a more detailed list of error codes, and for explanations of other methods for sending Configuration data to the module, including Inhibit, Module Reset Request, and Reconfigure Module MSG.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal