MicroSCADA Status Codes is a technical reference manual that lists all MicroSCADA status codes. It provides explanations of the codes and their possible causes, and divides them into groups based on their relation to the base system or communication and NET units.
advertisement
1MRS751251-MEN
2
2.1
2.2
ABB Automation
Status Codes
Technical Reference Manual
MicroSCADA
2 Handling Errors
Handling Errors
The status codes are positive integers with descriptive names. The purpose of the status codes is:
•
To show the reliability of calculated data and process data.
•
To inform about errors that occur during the execution of SCIL programs and evaluation of SCIL expressions.
•
To inform an application of certain events taking place in the process communication system or in the communication units.
Reliability of Data
In SCIL each evaluated expression gets a status code, which indicates the reliability of the value. As a rule, the status code is determined by the most unreliable operand included in the expression. Data written by the programmer or entered by the user always has the status code 0. An unreliable status code may be caused by a process object or data object value with a bad status (OS attribute). It may also be caused by some operators when the operands do not match and by some SCIL functions.
The status code of an application object value is the value of the OS attribute of the object. For process and data objects the code indicates the reliability of the OV attribute. For command procedures it indicates the success of the latest program execution.
The OS attribute of a process object is updated at each updating of the OV value in the process database. Process objects can be assigned the status codes 0, 1, 2, 3 and 10.
OS is updated by the base system, which determines the status code based on the system messages sent by NET.
The status code of a process object affects the status codes of the data objects that use the process object value in their expressions. If the logging function (LF attribute) is
DIRECT, the status code for the process object is copied to the status code of the data object.
The status code of an expression can be read with the SCIL function GET_STATUS and written with the function SET_STATUS.
SCIL Errors
A SCIL error is usually caused by a syntax error in the program, but it may also be caused for example by a database error or a communication error during the execution of a SCIL program.
Depending on the error handling policy defined by using the #ERROR command, the error may cause:
•
An error message or activation of an error handling program (CONTINUE,
STOP).
3
advertisement
Key Features
- Lists all MicroSCADA status codes
- Provides explanations of the codes
- Divides codes into groups
- Covers base system and NET units
- Technical reference manual