CODESYS Development System
Identifier Designation Rules and recommendations for the identifier designation for variables, constants, functions, function blocks, methods, and other objects :
CODESYS Development System
For Variables in CODESYS V3 Libraries Identifier designation recommendation for Description Example Variable Corresponds to the description for variable names, with the exception that global variables
CODESYS Development System
For Custom Data Types in CODESYS V3 Libraries Identifier designation recommendation for Description Example DUTs in CODESYS V3 libraries The namespace replaces the need for the library prefix. Therefo
CODESYS Development System
For POUs Identifier designation recommendation for Description Example Functions, function blocks, programs Library prefix followed by an underscore and a short, informative POU name Like for variable
CODESYS Development System
For POUs in CODESYS V3 Libraries Identifier designation recommendation for Description Example POU The library prefix is omitted because the namespace replaces the function of the library prefix. FUNC
CODESYS Development System
For visualizations Name recommendations for visualization objects Important Note that a visualization is not named the same as another block in the project because this may cause problems when changin
CODESYS Development System
Shadowing Rules In CODESYS , you are generally allowed to use the same identifier for different elements. For example, a POU and a variable can be named the same. However, you should avoid this practi
CODESYS Development System
Attribute: call_on_type_change The effect of this pragma is that a method decorated with is called if the data type of the function blocks referenced there changes in the superordinate function block.
CODESYS Development System
Attribute: conditionalshow The pragma has the effect that the identifiers of an integrated compiled library <library name>.compiled-library , which are decorated with the pragma, are hidden before pro