Glossary · PLC and control programming
Retentive memory
Also known as: Retain memory, Non-volatile data memory
German: Remanenter Speicher
In PLC technology, retentive memory is a memory area whose contents are preserved when the controller loses power or is restarted, implemented for example with battery-backed RAM, capacitors or non-volatile memory.
- PLC programming
In one sentence
Retentive memory keeps PLC data through power loss and restarts, using battery-backed RAM, capacitors or non-volatile memory.
Example
The controller writes its retentive data to non-volatile memory during power-down, so batch counters are still correct after the power returns.
How it applies
- Engineering: The size of the retentive memory is limited and differs between controllers. Engineers decide which data is retentive and check that the reserve is sufficient.
- Maintenance: Battery-backed designs need battery replacement at defined intervals; a dead battery can lose retentive data at the next power failure. Other designs use supercapacitors or flash memory without batteries.
- Operation: Retentive data must be consistent after an unexpected power loss. Programs sometimes verify retained data with checksums or plausibility checks after startup.
- Documentation: The maintenance manual should list battery type and replacement interval where applicable, and the procedure to back up and restore retentive data. Describe the effect of losing retentive data for operators.
Retentive vs. nonretentive memory
Retentive memory keeps values; Nonretentive memory returns to initial values at restart. A Retain variable is how a program places data into retentive memory.
In risk assessment, PL analysis and security analysis
- Risk assessment (CE): Retentive values survive a power loss or restart – setpoints, counters, step positions, operating modes. The risk assessment checks what the machine does with them when power returns: under the Machinery Regulation (Annex III, 1.2.6) restoring the power must not lead to an unexpected start-up.
- PL analysis: A stored step or a stored "drive on" must never be enough to restart a hazardous movement; restart needs a deliberate action (restart prevention). State in the software documentation which variables are retentive and how they are checked after a restart.
- Security analysis: Retentive data persists – manipulated setpoints or recipes survive a reboot. Treat them as data to protect under IEC 62443 (FR 3 system integrity): who may write them, how changes are logged, how plausibility is checked at start-up.
Naming this term in a document never shows conformity; the risk assessment, the validation of the safety functions and the security risk assessment do. EN 50742 is a CENELEC draft as of the review date: it is neither law nor a source of presumption of conformity.