Retentive Memory

Retentive memory in a PLC is battery-backed or flash-based memory that preserves stored values when the PLC loses power or goes through a power cycle. When power returns, retentive variables resume with their last-known values instead of resetting to defaults. Non-retentive memory, by contrast, resets all values to zero or initial state on every power-up.

**Why Retentive Memory Matters:** Without retentive memory, a PLC would lose critical data every time power is interrupted — production counts would reset, recipe parameters would disappear, and machine positions would be unknown. Retentive memory ensures operational continuity.

**What Should Be Retentive vs Non-Retentive:**

| Make Retentive | Keep Non-Retentive | |---------------|--------------------| | Production counters & batch totals | Temporary calculation variables | | Recipe parameters & setpoints | Bit flags for one-shot logic | | Alarm acknowledgment states | Timer accumulators (usually) | | Machine calibration offsets | Outputs and output coils | | Hour meters & maintenance counters | Intermediate math results | | Last-known positions | Sequencer step flags (depends on application) |

**Retentive Memory by PLC Brand:**

- **Allen-Bradley (Logix5000):** All controller-scoped tags are retentive by default. Program-scoped tags can be set retentive or non-retentive. Use the 'Retentive' checkbox in tag properties. C-type bits (counters) and timers use the .ACC (accumulator) value retentively. - **Siemens (TIA Portal / S7-1200/1500):** Use 'Retain' keyword in Data Block variable declarations. Merker (M) memory can be configured as retentive in hardware configuration. DB variables default to non-retentive unless marked otherwise. - **CODESYS:** Add the 'RETAIN' keyword before variable declarations: `VAR RETAIN totalParts : DINT := 0; END_VAR`. For variables that must survive even a warm restart, use `VAR PERSISTENT`. - **Schneider (EcoStruxure / Unity Pro):** Configure retentive memory areas in the Memory Configuration tab. %MW variables can be assigned to retentive zones.

**Common Mistakes with Retentive Memory:** 1. Making everything retentive 'just in case' — this wastes battery-backed memory and can cause stale data bugs after maintenance. 2. Forgetting to make production counters retentive, causing data loss on power blips. 3. Not accounting for retentive memory during PLC firmware updates or program downloads — some platforms clear retentive memory on full download. 4. Confusing 'retentive timer' (RTO/TONR) with retentive memory — an RTO timer retains its accumulated time, but that is a timer function, not a memory classification.