dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorObjects dl-breadcrumb-item__separatorObject: Persistent Variable List
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Object: Persistent Variable List dl-permalink__symbolPermalink

Symbol: _cds_icon_gvl_persistence.png

The object contains the declaration of global persistent variables in the declaration section ‎VAR_GLOBAL PERSISTENT RETAIN .. END_VAR‎. The variables are stored in special non-volatile memory.

The persistence editor shows the variables as a list in the usual way. The displayed list does not influence the persistence behavior of the variables, but only the list stored internally in the process image. The list there contains all variables ever declared in chronological order. Variables that you have removed are marked with a placeholder and continue to exist as a gap.

The declaration section can also contain instance paths, which refer to locally declared persistent variables and were created with the “Declarations  Add All Instance Paths” command.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

Before you decide how to set up persistence for an application, it would be helpful for you to be familiar with the use cases described in the ⮫ “Data Persistence ”, ⮫ Further information, ⮫ “Mechanisms in Comparison ”, ⮫ “Lifespan of variables when calling online commands ”, ⮫ “Lifespan of variables when loading a boot application ” chapter. Moreover, it is helpful if you can differentiate between the mechanisms of persistent variables, retain variables, variables of the Persistence Manager, and recipe variables.

  • Commands