Message pragmas

Message pragmas force the output of messages in the message window during the compilation process.

Insertion location: Separate or already existing line in the text editor of a POU.

Four types of message pragmas

Pragma	Message type
`{text <'text string'>}`	Text Output of the text `<text string>`
`{info <'info string'>}`	Information Output of the information `<info string>`
`{warning <'warning string'>}`	Warning Output of the warning `<warning string>` In contrast to the attribute pragma `'obsolete'`, you define the warning locally for the current position. The message pragma `{warning <'warning string'>}` is only permitted for objects such as POUs, for instructions and for variables. Sample: Use with variables: POGRAM MAIN VAR {warning <'warning message'>}; nVar1 : INT; END_VAR
`{error <'error string'>}`	Error Output of the error `<error string>`

	In the TwinCAT message window, you can access the source position of a message of category Information, Warning and Error by using the commands Next Message or Previous Message. This means you get to the position where the pragma is added in the source code.

Sample:

VAR 
    nVar : INT; {info 'TODO: should get another name'} 
    bVar : BOOL; 
    aTest : ARRAY [0..10] OF INT; 
    nIdx : INT; 
END_VAR 

aTest[nIdx] := aTest[nIdx]+1; 
nVar := nVar+1; 

{warning 'This is a warning'} 
{text 'Part xy has been compiled completely'}

Output in the message window:

See also:

Conditional pragmas