Attribute no_check, Attribute no_copy, L-force | plc designer – Lenze PLC Designer PLC Designer (R3-1) User Manual

Page 1003

Advertising
background image

L-force | PLC Designer

Programming Reference

DMS 4.1 EN 03/2011 TD29

1001

2. Pragma '{attribute 'monitoring':='call'}'
This attribute can only be used for properties returning simple data types or pointers,
not for structured types:
The value to be monitored is retrieved directly by calling the property, i.e. the
monitoring service of the runtime system calls the Get method. Regard that if any
operations on the variables are implemented within the property, the value might still
change!
Syntax:
{attribute 'monitoring':='call'}

Attribute No_check
The pragma {attribute 'no_check'} is added to a POU in purpose to suppress the call of
any check functions within this POU. As check functions may influence the
performance, it is reasonable to apply this attribute to POUs that are frequently called
or already approved.

Syntax:
{attribute 'no_check’}

Attribute No_Copy
Generally an online change will require a reallocation of instances e.g. of POUs.
Thereby the value of the variables within this instance will get copied.
If the pragma {attribute 'no_copy'} is added to a variable, an online change copy of this
variable will not be performed; instead this variable will be initialised. This might be
reasonable in case of local pointer variables being assigned to the address of a variable
actually shifted by the online change.
Syntax:
{attribute 'no_copy’}

Advertising