Persistent variables retain their values after reloading the application, and after a download, warm start, or cold start.
A special non-volatile memory area on the controller, for example as NVRAM or UPS, is required to extend the lifespan. Securing the data in such a memory does not require any additional time, which is an advantage over data retention with the Persistence Manager. If the controller does not provide hardware support, then the data is usually stored in a file. Then the data will be retained if you shut down the controller correctly. In the event of a power failure or a "pulled plug", however, data will be lost.
-
Behavior
-
Mechanism when downloading an application or loading a boot application
-
Recovering data with the recipe manager
-
Changing an existing declaration in the persistent variable list
-
Double allocation of memory in the case of instance paths
-
Memory location in the case of persistent function block instances
-
Importing of CODESYS V2.3 Gateway Server projects