Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Plant SCADA

GETCP Driver Specific Errors

  • Last UpdatedJun 12, 2026
  • 1 minute read

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 all 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 Plant SCADA will only display the error number.

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 all documentation, you cannot rectify an error, contact Technical Support.

0x05F4

Invalid input parameters in request.

0x05C3

Text length does not match traffic type.

0x00010031

Indicates that the PLC is "not in sending mode".

0x00010008

Indicates that the PLC has reached its "Maximum Users".

Note: Error codes in the format 0x0001xxxx indicate that the PLC returned the error. These errors are typically caused by an incorrect hardware configuration in the PLC or an issue with the PLC's operating state.

Related Links