📖HomeBack The following alarms and events can be raised in response to IIN Status bits reported by a DNP3 outstation.
There is an abnormal condition in the outstation. Typically, this alarm is raised when there are hardware problems in the outstation.
An IIN DEVICE_TROUBLE bit set raises a Device Trouble alarm in ClearSCADA. Refer to your hardware user manual for more information.
The ClearSCADA master station attempts to communicate with the DNP3 outstation using a command that the outstation does not support.
An IIN NO_FUNC_CODE_SUPPORT bit set raises a Protocol Alarm in ClearSCADA.
If an IIN NO_FUNC_CODE_SUPPORT bit is reported, you should configure ClearSCADA to create a log file of communications to the outstation (see ClearSCADA for more information on the Logging settings). When a log file has been created, you can translate it so that it is easier to read (see Driver Log Translation). Use the translated log file to determine which command caused the Protocol alarm to be raised, then use ClearSCADA to disable the feature that caused the alarm. A common cause of this type of alarm is that the outstation does not support the disabling of unsolicited messages (or does not support unsolicited messages at all).
The ClearSCADA master station is using objects that are not recognized or supported by the DNP3 outstation. For example, if a DNP3 outstation only supports integer point types, a protocol alarm will be raised if the master station attempts to control a point using an IEEE floating point type.
An OBJECT_UNKNOWN bit set raises a Protocol Alarm in ClearSCADA.
If an IIN OBJECT_UNKNOWN bit is reported, use the log files to determine which object caused the alarm. When you have located the object, alter the configuration so that only objects (database items) that are supported by the outstation are used.
There has been a parameter error. These occur when the DNP3 outstation receives a request that is supported by the outstation, but cannot be performed due to the request being incorrectly formed or using a range that the outstation does not support. For example, if the analog input points in the outstation have index numbers in the range 0 to 31, and the master station requests a read of analog input points in the range 0 to 49, there is a parameter error. As the master station request contains point index numbers outside the outstation's supported range, a protocol alarm is raised.
A PARAMETER_ERROR bit set raises a Protocol Alarm in ClearSCADA.
If an IIN PARAMETER_ERROR bit is reported, use the log files to determine which request caused the alarm. When you have located the request, alter the configuration so that only those features and data ranges supported by the outstation are used.
A PARAMETER_ERROR alarm will be generated if you attempt to perform a Level 3 Scan on a non E-Series SCADAPack.
The DNP3 outstation has too many events stored in memory. As the DNP3's memory is full, the DNP3 outstation is discarding any new events. Typically, this type of alarm occurs when a DNP3 has been offline for an extended period of time or events are being logged too quickly (and as a result, the outstation's buffers become filled more quickly than expected).
An EVENT_BUFFER_OVERFLOW bit set raises an Event Buffer Overflow Alarm in ClearSCADA. This is a serious alarm in any SCADA system as it means that important data is being discarded. The cause of this type of problem varies according to the type of hardware and network topology.
If an EVENT_BUFFER_OVERFLOW bit is reported, you need to determine the cause of the communication problems and re-establish healthy communications as soon as possible. ClearSCADA will upload events from the outstation until all events have been successfully uploaded. As soon as an event buffer overflow alarm is raised, it means data has been (and is still being) lost, so it is vital that you rectify the cause of the event buffer overflow as soon as possible.
The DNP3 outstation is unable to perform the requested operation as:
Another operation is already in progress
The master station request is to save configuration but the outstation is already in the process of saving configuration
The master station request is to run an outstation program that the outstation is already running
The master station request is to stop an outstation program that the outstation is not running
The master station request is to activate configuration but the outstation is already using the specified configuration.
An ALREADY_EXECUTING bit set raises an Already Executing Alarm in ClearSCADA.
If an ALREADY_EXECUTING bit set is reported, you need to use the outstation's diagnostic features to determine which action caused the alarm to be raised and what prevented the outstation from completing the request. You can then take the appropriate action to ensure that the outstation is not performing another operation, saving configuration, running/not running a specific outstation program, or using configuration that is specified in the request.
This type of alarm is raised when the outstation has detected corrupt configuration. This may relate to the corruption of essential configuration that affects the outstation's ability to function reliably or may be related to non-critical configuration.
A CONFIG_CORRUPT bit set raises a Configuration Corrupt Alarm in ClearSCADA.
If a CONFIG_CORRUPT bit set is reported, you may need to re-configure the outstation. This type of alarm often occurs when:
Somebody has reset all the configuration in the outstation
A new outstation has been installed
There is a hardware fault with the outstation resulting in the configuration becoming corrupt or unavailable.
You should refer to your outstation support documentation for information on how to correct these problems.
This type of event is logged if one of the DNP3 outstation's points are in the local operation mode. Local operation mode may result in control commands not being performed.
A LOCAL_CONTROL bit set generates a Points in Local Operation Event in ClearSCADA.
For more information, please refer to the DNP3 Outstation Status Attributes in the DNP3 Guide in ClearSCADA Help.