Siemens OP15 Program Backup and Transfer Between HMI Panels

Overview

The Siemens SIMATIC OP15 is a compact text-based operator panel from the early-generation OP3 / OP5 / OP7 / OP15 / OP17 family, designed primarily for direct connection to SIMATIC S5 and early SIMATIC S7 PLCs over MPI or serial point-to-point links. The OP15 is differentiated from later panels by its lack of ProSave backup/restore support and by the requirement to use the legacy Siemens COMTEXT configuration environment for full upload and download operations. Modern engineers servicing an OP15 in production frequently hit a hard wall when a unit fails and a replacement panel needs to be programmed, or when a backup copy is required for audit and disaster-recovery purposes.

This reference consolidates the hardware-level memory model of the OP15, the supported software toolchain, the upload constraints imposed by ProSave and ProTool, and the documented procedure for transferring a working project from a known-good OP15 to a replacement panel or to a PC archive. Where Siemens documentation is silent, the practical path is identified explicitly rather than inferred.

OP15 Hardware and Memory Architecture

The OP15 contains two distinct non-volatile storage regions and one volatile region. Understanding which subsystem holds which data is the foundation of every backup decision on this platform.

The OP15 is designed so that the program/project is retained in flash memory and is not dependent on the buffer battery. The battery's job on the OP15 is limited to keeping the real-time clock running and preserving retentive process data while mains power is off. A common field misconception is that removing the battery erases the HMI application. On the OP15 this is not the case: with main power removed and the lithium cell pulled, the project remains in flash and will reload on the next power-up.

Supported Configuration Software

OP15 projects were authored using one of two Siemens toolchains:

1. Siemens COMTEXT — the original OP-series configuration software for S5-coupled OP3/OP5/OP7/OP15/OP17 panels. COMTEXT produces a binary that can be uploaded from a working panel back to a PC.
2. Siemens ProTool / ProTool/Lite — the successor environment that targets OP and TD family panels. ProTool was used for some OP15 projects and is the entry point for newer operators trained on the ProTool/ProSave workflow.

The choice of authoring tool is the determining factor for whether a reverse (panel-to-PC) operation is technically possible. The COMTEXT path is the only documented upload route on OP15. ProTool on OP15 generally supports only download (PC-to-panel) and does not provide a panel-to-PC upload.

Why ProSave Upload Fails on OP15

ProSave is the Siemens service tool bundled with later WinCC flexible, TIA Portal, and ProTool/ProTool/Lite installations. It exposes a "Backup" / "Restore" interface over MPI, PROFIBUS, USB, or Ethernet depending on the target panel. The OP15 is not in the ProSave device catalog. When ProSave is pointed at an OP15, the operation fails before the file-transfer handshake because the panel firmware does not implement the ProSave backup protocol that newer SIMATIC Panels use.

Practical consequences:

• No "Backup" button in ProSave will ever read an OP15.
• No "Restore" operation will ever write an OP15 from a ProSave archive.
• ProSave cannot be coerced into OP15 mode by selecting a sibling device (OP7, OP17, OP270) — the firmware IDs are unique and the protocol handshake will reject the session.

This is the root cause of the most common engineer question on this platform: "How can I back up from OP15 to PC?" The honest answer is that ProSave is the wrong tool, and the operator must instead use COMTEXT or recover the original ProTool source files from a project archive.

COMTEXT-Based Upload Procedure

If the OP15 was originally programmed with COMTEXT, the upload workflow is the only reverse path that exists at firmware level. The procedure below is the standard COMTEXT transfer sequence applied to a single OP15 connected to a PC running COMTEXT over an MPI or serial PC adapter.

Prerequisites

• PC with Siemens COMTEXT installed and licensed for OP15 device type.
• Siemens PC adapter (MPI/PC or USB/MPI) compatible with COMTEXT, or a serial COMTEXT cable for older builds.
• OP15 powered, with the suspect project still resident in flash.
• Original project source files (.CTX or vendor-specific COMTEXT archive) if they exist — useful for diff validation after upload.

Upload sequence

1. Connect the PC adapter to the OP15's MPI/serial port and to the PC.
2. Launch COMTEXT and open the OP15 device driver.
3. Set the OP15 to Transfer mode via the OP15 key sequence (see panel keymap below) so the panel accepts host commands.
4. From the COMTEXT menu select Transfer > Upload from OP (menu wording varies by COMTEXT service pack).
5. Accept the destination path on the PC. COMTEXT writes a binary that is the inverse of the download image.

OP15 keymap for transfer mode

ProTool-Based Projects: Upload is Not Supported

If the OP15 was programmed with ProTool/ProTool/Lite, the firmware in the panel does not expose a panel-to-PC reverse channel that any current Siemens host tool can drive. This is not a configuration oversight; the ProTool runtime for OP15 is write-only over the fieldbus. The practical paths when only a ProTool-programmed OP15 is available are:

1. Locate the original ProTool source (.pdb / archived project). Search the EWS that originally generated the project, the plant's engineering archive (typically a version-controlled directory or a PVCS / SVN / Git repo), and any backup tapes or DVDs from the original commissioning.
2. Read the project out of flash with a programmer. This requires desoldering the flash IC, which is not a supported service procedure. It is mentioned only to confirm that the firmware does not implement a soft upload — the flash image is the source of truth.
3. Rebuild the project from documentation. If neither the source nor a service contract exists, the engineer must rebuild the OP15 project from the screen captures, message lists, and PLC tag mapping that survive in plant documentation. This is the most common path on panels that have been in service for 20+ years.

Transfer Workflow: From a Working OP15 to a Replacement OP15

The most common field scenario is a hardware failure on a single OP15 in a multi-panel line, where sister panels of the same type are running identical projects. The supported transfer workflow depends entirely on how the surviving project was originally authored.

Scenario A — Project was built with COMTEXT (uploadable)

1. Upload the project from the working OP15 to the PC using the COMTEXT procedure above. Save with a versioned filename.
2. Place the replacement OP15 into transfer mode (key sequence, power on).
3. From COMTEXT, select Transfer > Download to OP and select the saved binary.
4. Wait for the OP15 to confirm "Transfer OK" and reboot automatically.
5. Power-cycle the OP15 and verify that the project boots to the operator screen rather than the transfer prompt.

Scenario B — Project was built with ProTool (not uploadable)

1. Locate the original ProTool source archive. Without this source the transfer cannot be done.
2. Open the project in ProTool/ProTool/Lite on a PC with the OP15 device add-in installed.
3. Set the PLC connection parameters to match the live PLC (MPI address, baud rate).
4. Connect the PC adapter to the replacement OP15.
5. Place the OP15 into transfer mode using the boot key sequence.
6. From ProTool select File > Transfer > to OP and complete the download.
7. Verify on the live screen.

Scenario C — No source available (worst case)

1. Document every screen, message, and key action on the surviving OP15. Photograph each menu.
2. Capture the PLC tag list from the connected PLC using STEP 5 / STEP 7 cross-reference.
3. Rebuild the OP15 project from scratch in ProTool/ProTool/Lite using COMTEXT if no ProTool license is available.
4. Validate against the surviving OP15 panel by panel.

RAM-Only Transfer (Short-Term Testing)

COMTEXT supports a download mode that loads the project into OP15 working RAM only, bypassing the flash programming step. This is used for short-term bench testing and has two operational consequences that engineers must understand:

• The project is lost on the next power cycle.
• The flash programming cycle count is not incremented, which is useful for panels near end-of-life flash endurance.

The RAM-only transfer is selected with a specific COMTEXT menu option (typically Transfer > Download (RAM only)) and is unsuitable for production transfer between OP15 panels.

Battery Replacement Without Losing the Project

A frequent maintenance trigger is the OP15 clock stopping or the panel reporting a low-battery warning on screen. The battery is a lithium primary cell, single-use, and must be replaced with main power applied to preserve the RTC and any retentive data:

1. Power the OP15 from mains; do not power it down.
2. Open the rear battery compartment.
3. Note the polarity and the exact cell type (commonly a CR2032 holder or a 1/2 AA lithium, panel-revision dependent).
4. Replace the cell within the rated buffer window (typically 1-5 minutes; check the silk screen on the battery PCB for the capacitor hold-up if fitted).
5. Close the compartment and verify the RTC on the OP15 status screen.

Identification: Was My OP15 Built with COMTEXT or ProTool?

Determining the authoring tool is required before choosing an upload path. Use the following decision sequence:

1. Power the OP15 and navigate to the system / version screen (typically accessed via the ESC + softkey sequence shown in the COMTEXT manual).
2. Record the firmware version, project CRC, and any project-build string visible on the splash screen.
3. Compare the visible splash text and the firmware version with the COMTEXT and ProTool device lists in the respective configuration tools.
4. If the splash shows a ProTool-style build identifier (typically a project name and date stamp in ProTool format), the project is ProTool-built and not uploadable.
5. If the splash shows a COMTEXT-style identifier or no recognizable ProTool marker, attempt a COMTEXT upload as a non-destructive test — a failed upload leaves the flash image untouched.

Verification Steps After Any Transfer

Troubleshooting Matrix

Official Documentation and Where to Find It

The OP15 belongs to a discontinued Siemens product line. Authoritative documentation lives in:

• Siemens Industry Online Support (SiePortal) — legacy OP/TD product tree. Search for "OP15" and the EWA manual numbers EWA 4NEB 710 5090-01a and successor indices. Use the SiePortal knowledge base and the legacy OP/TD forum area for additional engineering notes. The SiePortal entry point is the canonical navigation root for current Siemens support resources.
• COMTEXT printed manual and help files — bundled with the COMTEXT installation media or archived on the customer's EWS.
• ProTool device add-in help — describes the OP15 device variant, supported object types, and download constraints.

Field engineers working on OP15 hardware should escalate hardware-fault cases through official Siemens support channels rather than relying on informal community knowledge, given the platform's age and the limited remaining stock of spare panels.

FAQ