Reduce Controller Communication

To reduce the communication burden on the controller, consider the following:
  • Controller applications can experience higher communication utilization when large portions of the I/O tree are not physically present, such as multiple I/O chassis. The increased communication utilization can result in an increase in the total time that is needed to qualify the redundant system. The communication utilization can be partially reduced by inhibiting the missing I/O in the configuration tree, but it will still be higher than if the I/O were physically present and operational.
  • Frequent and sustained incoming data table writes (>10/s for minutes) to controller tag values of a redundant controller can impact the communications performance of the redundant controller.
    Examples of incoming data table writes include the following:
    • Executing a message (MSG) instruction with CIP Data Table Write message type from another controller targeted to the redundant controller
    • Writing a tag value from an HMI
    • Modifying a tag value while online with the
      Studio 5000 Logix Designer®
       application
    Impacts on communications performance can include the following:
    • Reduced responsiveness while online with programming software
    • Error (16#000c) reported when a controller with many consuming tags (>15) attempts to establish connections to the redundant controller's produced tags
IMPORTANT:
FactoryTalk® Linx
 and
FactoryTalk® Linx
 Gateway are optimized to reduce the communications burden on the controller.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal