Adjust the Configuration of any DNP3 Points that Cause a High Load

Inadequate client performance can cause your ClearSCADA system to be slow (see Diagnose Client Performance Problems in the ClearSCADA Guide to the Server Status Tool). One of the causes of inadequate performance is high load on the server.

You can use the statistics that are displayed in Lists and Status displays to identify any DNP3 outstations that are causing a high loading on the ClearSCADA system.

For those outstations that have a high load, use the Points List to identify the point(s) that are causing the high load.

High load is typically caused by a point updating at too frequent a rate.

Where a point on a DNP3 outstation is causing a high load:

• If the point is on an outstation that has a direct connection to the server, check the Scan Group (Confidence Poll) that the point is using (see Configure General Point Properties). If this is causing the server to update the current point value at too frequent a rate, you might need to:
  • Specify a different Scan Group.
  • or:
  • Specify a less frequent scan rate for the Scan Group (see Define Intervals for Timed Current Data Updates in the ClearSCADA Guide to Advanced Drivers).
• If the point is an Analog point:
  1. Enable the Significant Change feature (see Significant Change Properties).
  2. If Significant Change enabled, you might need to increase the Significant Change deadband—the amount by which the point value has to change for the value to be logged by the outstation (see Significant Change Properties).
  3. If none of the above checks and configuration changes have cleared the high load caused by the point, check:
     1. The configuration at the outstation.
     2. The outstation hardware for any faults.
     3. The plant for any faults.
     4. The instrumentation for any faults.