Download Data types in CoDeSys

Global Variables, Variable Configuration, Document Frame
Example of a network variables list, which has been created by loading an export file *.exp and which
was named Network_Vars_UDP:
Editing Remanent Global Variables Lists
If they are supported by the runtime system, remanent variables may be processed. There are two
types of remanent global variables (see also Chapter 5.2.1, Remanent Variables !):
Retain variables remain unchanged after an uncontrolled shutdown of the runtime system (off/on) or
an 'Online' 'Reset' in CoDeSys. Persistent variables remain unchanged only after a download.
Persistent variables are not automatically also Retain variables !
Remanent variables are additionally assigned the keyword RETAIN or PERSISTENT or both.
See chapter 5.2.1, Remanent Variables, for further information.
Network variables are also defined in this syntax.
Syntax:
VAR_GLOBAL RETAIN
(* Variables declarations *)
END_VAR
VAR_GLOBAL PERSISTENT
(* Variables declarations *)
END_VAR
For the combination of retain and persistent properties both keywords are used:
VAR_GLOBAL RETAIN PERSISTENT or VAR_GLOBAL PERSISTENT RETAIN
Network variables (target specific) are also defined using this syntax.
Global Constants
Global constants additionally get the keyword CONSTANT.
Syntax:
VAR_GLOBAL CONSTANT
(* Variables declarations *)
END_VAR
6.2.2
Variable Configuration
In function blocks it is possible to specify addresses for inputs and outputs that are not completely
defined, if you put the variable definitions between the key words VAR and END_VAR. Addresses not
completely defined are identified with an asterisk.
Example:
FUNCTION_BLOCK locio
VAR
loci AT %I*: BOOL := TRUE;
6-6
CoDeSys V2.3