ST_Exception - General Information

Overview

Type:

Data structure

Available as of:

V1.0.4.0

Inherits from:

-

Description

With this structure, an exception is defined and can be entered into a list.

Structure Elements

Variable

Data type

Description

dateDate

DATE

Date where the exception was triggered.

todTimeStamp

TOD

Point of time where the exception was triggered.

udiModuleId

UDINT

ID of the module that triggered the exception.

sModuleName

STRING[80]

Name of the module that issued the exception.

etDiag

GD.ET_Diag

General, library-independent statement on the diagnostic.

A value not equal to ET_Diag.Ok corresponds to an error message.

udiDiagExt

UDINT

Value of the POU-specific statement on the diagnostic.

q_etDiag = GD.ET_Diag.Ok -> status message

q_etDiag <> GD.ET_Diag.Ok -> diagnostic message

sDiagExt

STRING[80]

Name of the POU-specific statement on the diagnostic.

q_etDiag = GD.ET_Diag.Ok -> status message

q_etDiag <> GD.ET_Diag.Ok -> diagnostic message

sMsg

STRING[Gc_udiMaxStringSizeOfExceptionMsg]

Event-triggered message which gives more detailed information on the diagnostic state.

udiExceptionNumber

UDINT

Unique exception number in the structure XXXYYYY where XXX is the value of etSource and YYYY is the value of udiDiagExt.

stReaction

ST_Reaction

Reactions that are triggered by exceptions.

etSource

ET_ExceptionSource

Origin/source of the exception

xAutoQuit

BOOL

TRUE: The exception acknowledges itself.

wHmiAttributes

WORD

Can serve for communication with an HMI.

Can be freely defined by the user.

timeDelayTime

TIME

Delay after which the reactions of the exception shall become active.

todElapsedTime

TOD

Time elapsed since the exception is active.

todReactionTimeStamp

TOD

Point in time at which the reactions of the exception became active.

NOTE: Error states difficult to diagnose now.

If you are using the xAutoQuit function with exceptions that have set a reaction in stReaction, the behavior of your application may be difficult to diagnose. If such an exception is triggered and then becomes inactive again, its reaction disappears again too. It is then only possible to understand why the system stopped by using the log data list (the effect depends on the influences of the chosen reaction).

Action recommendations:

Do not use the xAutoQuit function for exceptions where you have set a reaction.