.svg){kind=logo}
If you receive a status code of 1030, it means the SCADAPack E event buffer has reached 80% of the Max Event Storage as per the configuration. If events are not collected in a timely manner, the event buffer will overflow and you will receive the Event Data Lost status code of 1031.
When situations like this arise, it usually means the DNP3 system (SCADAPack and DNP3 Master) as a whole needs to be tuned.
Challenge
The below example configuration has the Max Event Storage set to “10 events”. The SCADA host is not scheduled to poll for RTU for any class data, nor is it scheduled to perform an integrity poll. With 9 events (it has exceeded the 80% of Max Event Storage), the status code of 1030 is shown on the SCADAPack E Configurator status page. To view the events in a SCADAPack E, use the Virtual Terminal and type “status events” at the command prompt.
If events continue to be generated in the SCADAPack E, and the class data is still not retrieved, then you will see an error code of 1031 when the Max Storage buffer size has been reached. When the Max Event Storage buffer has been reached, new events will be generated and the oldest events will be discarded by the SCADAPack E.
Solution
When the RTU event buffer is filled (status code 1031), the DNP3 internal indicator (IIN) 2.4 will also be set. Only the configured DNP3 Master station can clear this IIN bit. Only the “Clear Errors” button in SCADAPack E Configurator can clear the status code messages displayed.
When a user receives these types of status code messages, the remedy is NOT to use SCADAPack E Configurator to constantly clear the errors. The challenge lies in tuning the DNP3 system. This can be a combination (but not limited) to the following:
- Reduce the amount of events being generated in the RTU configuration. As an example Binary points can be set to Class 0 (current data) only. Analog points can be configured to have a larger event deviation.
- Increase the frequency of class polls form the SCADA host. This will ensure you are getting the event data more frequently, but could yield more bandwidth on the SCADA system.
- Increase the buffer size in the SCADAPack E configuration.
- Use priority class configurations in the SCADAPack E and SCADA host. Priority data (and most frequent event change) in Class 1, Secondary data in Class 2 with less frequent polling and tertiary data in Class 3.
- Advanced users can consider enabling unsolicited messaging for classes and/or individual points.
Additional information can be found in the technical help manuals installed with SCADAPack E Utilities.
