Cicode Errors | Cicode

Cicode Programming Reference > Cicode Errors > Hardware/Cicode Errors

Hardware/Cicode Errors

Citect SCADA 'traps' system errors automatically. When Citect SCADA detects a system error, it generates a hardware alarm, and the corresponding error message is placed in the alarm description. Each error has an associated (unique) error number.

You can use the IsError() function to get the number of the last error. Alternatively, you can trap and process errors within your user functions. Use the ErrSet() function to enable or disable error trapping.Citect SCADA 'traps' system errors automatically. When a system error occurs, Citect SCADA generates a hardware alarm, and the corresponding error message is placed in the alarm description. Each error has an associated (unique) error number. Number 0 means no error, errors start from 1.

Range	Source	Cause
1 - 31	PLC or I/O Device Generic errors	The I/O device is reporting an error, or Citect SCADA is experiencing the reported error trying communicate with an I/O device. Often caused by incorrect configuration or poor cabling. For a detailed list of these errors, see the Error Messages topic in the Topology \| I/O Devices \| Troubleshooting Device Communications section of the Citect SCADA help.
256 -511	General	General errors are wide ranging, from animation to server problems. However, there are two main causes of general errors: 1. Device External devices such as printers, databases, and files can cause many different hardware errors since they are beyond the control of Citect SCADA. Often the device itself is improperly configured or non-existent. 2. Cicode Cicode errors are generated when your project configuration calls a Cicode function in an invalid way, or when a Cicode function returns an error or does illegal operations. For a detailed list of these errors see Cicode and General Errors.
382 - 383	Invalid tag data	This will indicate that the tag data validation process has identified a discrepancy with the tag index values. For more information, see the topic Validating Distributed Project Data for Tag-based Drivers in the Topology \| I/O Devices section of the Citect SCADA help.

Range

Source

Cause

1 - 31

PLC or I/O Device
Generic errors

The I/O device is reporting an error, or Citect SCADA is experiencing the reported error trying communicate with an I/O device. Often caused by incorrect configuration or poor cabling. For a detailed list of these errors, see the Error Messages topic in the Topology | I/O Devices | Troubleshooting Device Communications section of the Citect SCADA help.

256 -511

General

General errors are wide ranging, from animation to server problems. However, there are two main causes of general errors:

1. Device

External devices such as printers, databases, and files can cause many different hardware errors since they are beyond the control of Citect SCADA. Often the device itself is improperly configured or non-existent.

2. Cicode

Cicode errors are generated when your project configuration calls a Cicode function in an invalid way, or when a Cicode function returns an error or does illegal operations.

For a detailed list of these errors see Cicode and General Errors.

382 - 383

Invalid tag data

This will indicate that the tag data validation process has identified a discrepancy with the tag index values. For more information, see the topic Validating Distributed Project Data for Tag-based Drivers in the Topology | I/O Devices section of the Citect SCADA help.

You can use the IsError() function to get the number of the last error. Alternatively, you can trap and process errors within your user functions. Use the ErrSet() function to enable or disable error trapping.

Published June 2018