2.3 System Messages. ABB MicroSCADA

MicroSCADA

2 Handling Errors

2.3

4

Status Codes

Technical Reference Manual

1MRS751251-MEN

•

An immediate stop of the program execution (STOP, EVENT).

•

No action (IGNORE).

For more information on error handling policies see the #ERROR command in the

Programming Language SCIL manual.

An error handling program allows you to build procedures handling error messages. If the error handling policy is CONTINUE or STOP, a SCIL error generates a standard error message unless defined otherwise in an error handling program.

Errors in Visual SCIL dialogs are shown in the Error Viewer by default. The Error

Viewer shows the status code, the line in the program where the error occurred and the error state.

When the pictures are shown on the screen, the status codes are part of standard error messages written on the top line of the application window. This is done unless no other ways to handle error messages are defined in the named program called

ERROR_HANDLER. These error messages have the following format: code1 code2 SCIL STATEMENT OR EXPRESSION

The ’code1’ states roughly in which circumstances the error occurred. This code is always a picture handling code (801 . . 999). The ’code2’ specifies the error more accurately. The SCIL statement or expression that caused the error message is usually, but not always, shown and the error is marked to help to correct it.

A status code may also appear in a message shown in the MicroSCADA Notification

Windows. Usually the message refers to errors in command procedures or in system configuration. In some cases it is the result of errors in the report database, the process database, the file handling or the operating system interface.

Normally, the message in the Notification Window has the following format: time module: object name or message

SCIL STATEMENT OR EXPRESSION

STATUS = code

The message is displayed in all active MicroSCADA Notification Windows connected to the base system that generates the message. The message is also stored in a file in the base system computer. The file is located in the \SC\SYS\ACTIVE\SYS_ directory and has the name SYS_ERROR.LOG.

System Messages

System messages are internal MicroSCADA messages sent to one or several applications. Most system messages are status codes generated by NET. Some station types (STY objects) may also generate codes sent as system messages.

By means of certain communication system object attributes (SE, MS, MI, CA), the system messages can be directed to the chosen applications and process objects. By defining process objects for receiving the system messages, the programmer can define various consequential actions to be activated at certain system message codes.

This kind of action could be for example a request for a line switch when the status sent by the main communication line indicates a communication disturbance.

ABB Automation