Slow or unreliable communications

Possible cause and solution:
  • The
    FactoryTalk Linx Gateway
     host computer is out of memory or out of disk space
    Ensure the
    FactoryTalk Linx Gateway
     host computer meets the System requirements in
    FactoryTalk Linx Gateway
     Release Notes.
  • The
    FactoryTalk Linx Gateway
     host computer is at maximum CPU load.
    Ensure the
    FactoryTalk Linx Gateway
     host computer meets the System requirements in
    FactoryTalk Linx Gateway
     Release Notes.
    Change anti-virus scan settings to only run during off-peak
    FactoryTalk Linx Gateway
     communication periods.
    Move other services on the
    FactoryTalk Linx Gateway
     machine to a new host computer until the runtime load is reduced.
    Rockwell Automation
     recommends a 40% maximum steady state CPU load. This balances utilization of the hardware and provides enough bandwidth for peak loads.
  • A firewall or switch is blocking some or all
    FactoryTalk Linx Gateway
     communications.
    Verify firewall and switch rules allow
    FactoryTalk Linx Gateway
     communications. For a list of ports used by
    FactoryTalk Linx Gateway
    , see Application notes in
    FactoryTalk Linx Gateway
     Release Notes.
  • The
    FactoryTalk Linx Gateway
     CPU usage is high
    Reduce the number of clients packaging data to OPC standards.
    Limit the number of clients requesting data from a single OPC data server.
    Restrict the action of changing groups by clients.
  • The network is not configured correctly.
    Check your network configuration and
    FactoryTalk Linx Gateway
     installation.
  • The controller CPU usage is too high.
    Use Logix Designer Task Monitor to monitor task utilization and take proper actions.
  • The communication efficiency linked to Ethernet Module is low.
    ENET, ENBT, EN2T, or EWEB modules could be a bottleneck to communications depending on the number of data requests and the number of requesting clients.
  • The communication efficiency is affected by tag structure.
    See
    Studio 5000 Logix Designer
     online help.
  • The communication efficiency is affected by the time slice setting.
    Increase the time slice value in Logix Designer application.
  • The ControlLogix Optimized Packets process is hindered.
    Refer to your ControlLogix controller documentation.
  • OPC
     UA or DA service is stopped.
    Check the Server Configuration tab, make sure the UA and DA Server is not disabled. Or go to windows Services tool to restart the
    OPC
     UA or DA service.
  • A hard-coded 6-minute time-out notification received.
    Verify the server and client connection, both physical and software level.
  • A reboot is required for
    OPC
     servers and client.
    Verify the
    OPC
     server and client are successfully reconnected to the original objects after disconnection.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal