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

AVEVA™ Plant SCADA

Specific Errors

  • Last UpdatedAug 04, 2025
  • 1 minute read

Plant SCADA driver errors can occur when a device:

  • does not respond

  • is disconnected

  • is offline

  • returns an error.

Plant SCADA has two kinds of driver errors - generic and specific.

Generic errors are hardware errors 0-31, and are common to all protocols (for more information, see the topic Error Messages in the Reference Information section of the main Plant SCADA documentation).

Specific errors are unique to a particular driver, and may not be recognized by the hardware alarm system. The driver converts the specific errors into generic errors so they can be identified by the I/O Server. This means when a driver becomes inoperable, there is often both a specific error and a corresponding generic error.

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, verify that you have Alarm Category 255 defined with a display format that includes {ErrDesc,15} {ErrPage,10}.

KNX Specific errors

Error value

Error definition

Description

0x20000001

ERR_DEMO_EXPIRED

Unlicensed demo system has timed out

0x20000002

ERR_INIT_UNIT_IN_PROGRESS

Notification only – the unit initialization is still in progress

0x20000003

ERR_INIT_UNIT_TIMEOUT

The unit initialization process has timed out

0x20000004

ERR_INVALID_INTERNAL_STATE

Internal software error

0x20000005

ERR_ALL_TAGS_BAD_QUALITY

The unit has been taken offline because all tags on the unit are in a bad quality state

0x20000006

ERR_TAG_NOT_FOUND

The requested tag could not be found

0x20000007

ERR_TAG_QUALITY_BAD

The tag has a bad quality value

Related Links
TitleResults for “How to create a CRG?”Also Available in