Siemens S7-200PLC program data power-off preservation method - Database & Sql Blog Articles

Photocoupler

Siemens S7-200 PLCs offer several methods for preserving program data during power outages. These techniques are essential for ensuring that critical data remains intact even when the system is turned off. Here’s a detailed breakdown of the available options:

1. Power-down Data Retention via System Block Settings: The S7-200 includes a built-in function in the system block that allows users to define which memory areas should retain their values when power is lost. This typically involves V memory, M memory, and timers/counters (only the current value can be preserved). When the main power is cut, the internal super capacitor powers the PLC for a short period, keeping the selected data intact. However, this method is limited by the capacitor’s capacity, usually lasting only a few days. For the first 14 bytes of the M memory (MB0–MB13), the PLC automatically transfers the data to EEPROM upon power loss, enabling long-term storage. To extend this retention time further, Siemens offers an optional battery card that keeps the data alive for up to 200 days after the supercapacitor is drained.

2. Using Data Blocks for Persistent Storage: Another approach is to create a data block within the programming environment and assign initial values to specific variables. Once the program is compiled and downloaded to the PLC, the CPU stores these values in EEPROM. This ensures that the data remains intact even after a power cycle. If the corresponding V memory area is not set for power-down retention, the PLC will load the EEPROM data back into RAM at startup. However, if the area is configured for retention, the CPU checks whether the saved data was successfully stored. If so, it retains the RAM values; otherwise, it loads from EEPROM. This method is especially useful for static data that needs to persist across restarts.

3. Utilizing SMB31 and SMW32 for Programmatic Data Saving: By writing the address of the V memory to be saved into SMW32 and specifying the data length in SMB31, you can trigger an EEPROM write operation. Setting bit SM31.7 to 1 initiates the save process, which occurs automatically at the end of each scan cycle. After saving, the bit is reset to 0. This method is ideal for dynamically changing data that needs to be preserved over time. However, note that EEPROM writes take around 15–20 milliseconds per operation and have a limited lifespan (typically 1 million cycles). Therefore, it's important to minimize unnecessary writes to avoid premature failure.

Combining these methods in real-world applications often yields the best results. For instance, calibration parameters that need to be set once and adjusted occasionally can be stored in data blocks with initial values, while frequently updated data can be retained using the M memory area or EEPROM via SMB31/SMW32. In practice, engineers often use a mix of these strategies to ensure reliability and flexibility. A typical example is setting M0.0 to 1 when configuring parameters, then triggering an EEPROM save of VD100. This ensures that the latest settings are always preserved, even after a power interruption.