DNPR Driver-specific Errors

When a hardware error occurs, Plant SCADA generates an alarm, and displays the alarm on the hardware alarm page (in the alarm description of the hardware alarm). To see the error number, make sure you have Alarm Category 255 defined with a display format that includes {ErrDesc,15} {ErrPage,10}.

There are a number of generic errors that are common to protocols. In some cases only the generic error is available, though often both the generic error and a specific error are given.

The following errors, listed in (hexadecimal) sequence, are specific to this protocol. Plant SCADA displays the error number and description for common protocol-specific errors. Uncommon errors are not contained in the Plant SCADA error database, in which case only the error number will be displayed.

You may require additional information to enable you to rectify an error. This information should be detailed in the documentation that accompanied the I/O Device (or network). If, after reviewing the documentation, you cannot rectify an error, contact Technical Support for this product. Due to the complex nature of this protocol, technical support is only available at hourly rates. Please contact Technical Support for further details.

0x00050GENERIC_SOFTWARE_ERROR

Software driver error

0x00051GENERIC_SOFTWARE_ERROR

Memory could not be allocated for cache

0x00052GENERIC_TOO_MANY_COMMANDS

Could not insert request to lower API layer because of existing duplicate request

0x00053GENERIC_ADDRESS_RANGE_ERROR

A point used in a write request is invalid

0x00054GENERIC_INVALID_DATA

Point(s) in a read request are not yet valid because they are older than polltime

0x00055GENERIC_BAD_PARAMETER

User has set polltime to zero

0x00056GENERIC_INVALID_COMMAND

This type is write only

0x00057GENERIC_ADDRESS_RANGE_ERROR

More points were requested than defined by the user

0x00058GENERIC_SOFTWARE_ERROR

Invalid Object read tag object sub field. Check for the correct DNPR.dbf file

0x00059GENERIC_SOFTWARE_ERROR

No matching entry in tag object table can be found. Check for the correct DNPR.dbf file

0x0005AGENERIC_INVALID_DATA

A point or points in read request not valid

0x0005BGENERIC_SOFTWARE_ERROR

Cannot find a matching dcb for a write response

0X0005CGENERIC_ADDRESS_RANGE_ERROR

Data does not exist in cache

0x0005DGENERIC_GENERAL_ERROR

Unable to complete write command

0x0005EGENERIC_UNIT_WARNING

IIN Error detected that will generate an alarm. The ability of the driver to detect any individual member of this group of alarm conditions can be turned on and off using the Citect.ini parameter MinorIINSelectFilter. The default for the driver is to turn each of these alarms ON.

This Plant SCADA error will only be returned under the following circumstances:

On Plant SCADA write requests for Analog Outputs, CROBs, Counter Freeze and Restart requests. The error will only be returned when there are no other errors considered more serious for that request (e.g. Analog Output/CROB status errors described above).

On a front-end read request (e.g. a tag is displayed) following a back-end periodic poll where the error was detected. This error will only be returned when there are no other errors considered more serious resulting from the back-end poll (low level API application errors have precedence).

If this occurs, it indicates one or more of the selected minor IIN errors have occurred under the circumstances described above. The error code cannot differentiate which of the enabled IIN flag(s) has caused the IIN error. To accomplish this, a "Debug * ALL" command should be issued in the kernel, and the individual IIN flags will be reported in the syslog through the protocol diagnostic reporting.

IIN flags that can be detected are:

LOCAL_IIN:Bit 5 in byte 1 of IIN - Outstation Digital Output(s) are in Local mode (driver cannot control)

TROUBLE_IIN:Bit 6 in byte 1 of IIN - Abnormal condition flagged in Outstation (refer to device profile).

BUFFER_OVFL:Bit 3 in byte 2 of IIN - Outstation lost data from overflow of event buffers

EXECUTING_IIN: Bit 4 in byte 2 of IIN - Request understood but operation already executing

CONFIG_IIN: Bit 5 in byte 2 of IIN - Current configuration in Outstation is corrupt.

0x0005FGENERIC_GENERAL_ERROR

Cannot open database - Plant SCADA form may be open

0x00060GENERIC_GENERAL_ERROR

Error detected in queue

0x00061GENERIC_GENERAL_ERROR

Cache refresh late due to poll delays

0x00062GENERIC_INVALID_DATA_TYPE

Requested raw type invalid for native type

0x00063GENERIC_UNIT_WARNING

An error has occurred in a device using a virtual unit tag

0x00064GENERIC_UNIT_WARNING

General null pointer issue, e.g. a request has occurred internally for a device no longer installed

0x00065GENERIC_UNIT_OFFLINE

A unit's Startup mode has not been configured (for example, "Primary" or "Standby") for the I/O Device, and peer redundancy is in use.

0x00068GENERIC_UNIT_OFFLINE

IIN error detected that will generate an error alarm. The ability of the driver to detect any individual member of this group of alarm conditions can be turned on and off using the Citect INI parameter MinorIINSelectErrorFilter. Note: the default for the driver is to turn each of these alarms OFF. See error 0.x0005E for the conditions that trigger this error.

0x00069GENERIC_UNIT_REMOTE

We have done another SELECT while one is in progress.

0x0006AGENERIC_UNIT_REMOTE

Waiting for an RTU response before coming online

0x0006B GENERIC_GENERAL_ERROR

Port level indication that transport is unavailable

0x0006C GENERIC_UNIT_WARNING

Unit is offline for valid reasons, for example, its pair unit is active

0x0006D GENERIC_CHANNEL_OFFLINE

Still trying to connect to a port and have been prompted to do it again

0x10002GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 2 - Function code in response not supported

0x10003GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 3 - Response sequence number does not match the latest request

0x10004GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 4 - Response fragment received with no active request

0x10005GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 5 - Object/Variation not supported

0x10006GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 6 - Object/Qualifier combination not supported

0x10007GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 7 - Response qualifier code not supported

0x10008GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 8 - Timeout waiting for application layer response fragment or restart

0x10009GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 9 - Object/Variation not supported in read response

0x1000AGENERIC_GENERAL_ERROR

Low Level API Application Layer error code 10 - Object/Variation not supported in operate response

0x1000BGENERIC_GENERAL_ERROR

Low Level API Application Layer error code 11 - Error considered serious by low level API. Internal indications bits relating to remote device parsing of last request indicate either:

Device does not recognize requested objects (Bit 1 in byte 2 of IIN).

Outstation rejected application request as invalid or out of range due to formatting errors (Bit 2 in byte 2 of IIN).

Function code not implemented (Bit 0 in byte 2 of IIN).

0x1000CGENERIC_GENERAL_ERROR

Low Level API Application Layer error code 12 - Response does not match request for 'Select before Operate'

0x1000DGENERIC_GENERAL_ERROR

Low Level API Application Layer error code 13 - Response to Restart message does not include time object

0x1000EGENERIC_GENERAL_ERROR

Low Level API Application Layer error code 14 - Object/Variation not supported in write response

0x1000FGENERIC_GENERAL_ERROR

Low Level API Application Layer error code 15 - Invalid device number (index) in application layer transmit queue

0x10010GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 16 - Response to Delay measurement does not include time object

0x10011GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 17 - Message not processed as unsolicited responses disabled

0x10012 GENERIC_GENERAL_ERROR

Low Level API Application Layer error code 18 - Invalid application layer frame received

0x20001GENERIC_GENERAL_ERROR

Analog Output/CROB Status Value 1 - Bad control request - OPERATE received after SELECT timeout (This Plant SCADA error will only be returned on Plant SCADA Write requests)

0x20002GENERIC_GENERAL_ERROR

Analog Output/CROB Status Value 2 - Bad control request - OPERATE received without prior SELECT (This Plant SCADA error will only be returned on Plant SCADA Write requests)

0x20003GENERIC_GENERAL_ERROR

Analog Output/CROB Status Value 3 - Bad control request - formatting errors in control request (This Plant SCADA error will only be returned on Plant SCADA Write requests)

0x20004GENERIC_GENERAL_ERROR

Analog Output/CROB Status Value 4 - Bad control request - control request not supported for point (This Plant SCADA error will only be returned on Plant SCADA Write requests)

0x20005GENERIC_GENERAL_ERROR

Analog Output/CROB Status Value 5 - Bad control request - control queue full or point already active (This Plant SCADA error will only be returned on Plant SCADA Write requests)

0x20006GENERIC_HARDWARE_ERROR

Analog Output/CROB Status Value 6 - Bad control request - not accepted due to hardware problems (This Plant SCADA error will only be returned on Plant SCADA Write requests)