Siemens OP7 Stuck in "Ready for Transfer" Mode: Field Recovery Guide

The SIMATIC OP7 (operator panel, 6AV3 607 series) is a legacy text/graphic HMI widely deployed on S7-200, S7-300, and S7-400 machines. When the OP7 boots and the display reports "Ready for Transfer" and nothing else, the panel is signaling that the internal project image is missing, invalid, or has been deliberately erased. Operators see a device that no longer drives tags, faults, or recipes, and the PLC is left running without operator visibility. The state is recoverable, but the correct fix depends on the root cause: an accidental boot-key combination, a flash/memory fault, a transfer interruption, or SRAM/backup-battery loss. This guide walks an automation engineer through the diagnostics, the ProTool/ProSave reload, and the verification steps required to bring an OP7 back into service.

1. Problem Statement: What "Ready for Transfer" Actually Means

"Ready for Transfer" is the OP7's native bootstrap state. It indicates that the panel firmware is operational, the runtime loader is present, but the panel is not holding a valid compiled ProTool project (or the project has been flagged as invalid by the loader). The status line is intentionally minimal so the device can accept a fresh download from ProTool, ProSave, or an external programming tool.

Symptoms an operator typically reports:

• The OP7 display is stuck on a single line, "Ready for Transfer," with no process screens.
• Key presses appear to be ignored or only navigate a hidden transfer menu.
• No communication faults are raised to the PLC, but no tag updates occur.
• After a power cycle the same line returns, often within 2–3 seconds of the Siemens logo fade.

2. OP7 Hardware, Firmware, and Communication Background

The OP7 family comprises the OP7 (text, 4 lines × 20 characters), OP7/PP, and OP7/DP variants. Relevant technical constants for the troubleshooting procedure:

For the full SIMATIC HMI documentation set, see the Siemens Industry Online Support – SIMATIC HMI manuals portal. ProTool/Pro legacy download and notes are listed under ProTool/Pro V6.2 Service Pack 3.

3. Root Cause Analysis Matrix

Four primary failure modes leave the OP7 at "Ready for Transfer." The matrix below maps each cause to the diagnostic signature and the appropriate recovery path.

4. Cause 1: Accidental Boot Shortcut (ESC + Right + Down)

The OP7 boot loader recognizes a hidden key combination used by service technicians: holding ESC + Right-arrow + Down-arrow during power-up erases the project area in flash and forces the loader into transfer mode. This is a legacy field-service feature inherited from the OP3/OP5 line. When a maintenance technician props a keyboard orleans on the keypad, or when the panel is bench-tested with the membrane keys depressed, the same combination can fire unintentionally.

Diagnostic signature:

• Previous shift ran normally; a stoppage coincides with a maintenance event.
• The display returns to "Ready for Transfer" after a power cycle without any transfer activity.
• No error code is shown — the loader simply reports an empty project slot.

Workaround while a backup is fetched: the panel can be coerced out of the empty state for diagnostic purposes by pressing ESC. If the flash holds a residual project, the OP7 will boot to the runtime. If the flash is genuinely empty, ESC will simply clear the line and "Ready for Transfer" will reappear after a brief pause. A persistent return to the message is the strongest indicator that the project was deliberately cleared.

5. Cause 2: Flash Memory or Project File Fault

OP7 flash cells age with write cycles. The typical endurance is 100,000 program/erase cycles per sector. On panels that have seen dozens of project revisions over a decade, the project sector can degrade. Other contributors:

• Operating temperature above 55 °C accelerates retention loss.
• Frequent transfer-mode toggles cause repeated re-flashes of the same sector.
• ESD events during panel swaps can corrupt the loader's project pointer.

Symptoms distinct from a clean erase:

• Panel takes 30+ seconds to settle on "Ready for Transfer" instead of the normal 2–3 seconds.
• LED behavior: the "Fault" or "Transfer" LED may blink in an irregular pattern.
• ProSave returns error 0x07 / "Write error" when attempting to re-flash.

For a degraded flash, the panel must be either replaced or re-initialized by re-flashing the operating system (OS) with ProSave and then transferring the project. If OS reload fails, retire the unit.

6. Cause 3: Corrupted Transfer or Power-Loss Event

If a project transfer was in progress when the cable was pulled, the PC crashed, or the panel was de-energized, the OP7 flash can hold a partial project image. The runtime loader validates the project CRC; a mismatch forces the loader into transfer mode to await a clean copy.

Best-practice verification before another transfer attempt:

1. Inspect the ProTool transfer log for "Transfer incomplete" or "Checksum mismatch."
2. Check the OP7 firmware version against the source project (ProTool adds a build-stamp).
3. Confirm the transfer cable pinout (RS-232 PT/PC: 2-3 swap, 4-5, 6-20; do not use a null-modem crossover intended for PC-to-PC).

7. Cause 4: SRAM and Backup-Battery Failure

Recipes, passwords, and retentive tag values live in battery-backed SRAM, separate from the project flash. A dead or missing battery does not by itself cause "Ready for Transfer," but it can mask a deeper issue. If the panel is rebooted after extended storage and the loader is unable to read a flag byte in SRAM, it can drop into the safe state.

Battery replacement procedure:

1. Power down the OP7 and the PLC.
2. Open the rear cover; the battery is a 3.6 V ½-AA lithium cell in a clip.
3. Replace with a fresh unit (Siemens 6AV3 671-1CL00-0AA0 or equivalent).
4. Power up; if "Ready for Transfer" persists, the cause is not the battery.

8. Pre-Reload Diagnostics

Before connecting a PC and initiating a transfer, perform the following checks. They save hours when the panel sits in a hard-to-reach cabinet:

If the panel is accessible, attempt the ESC key diagnostic described in §4. A successful exit to the project is a free piece of evidence; a return to "Ready for Transfer" confirms an empty flash.

9. Project Reload Procedure Using ProTool / ProSave

9.1 Required Tools and Cables

• PC running ProTool V6.0 or ProTool/Pro V6.2 SP3, or ProSave ≥ V6.2 for a project-only transfer.
• The original *.pdb / *.pdz / *.arj source project, or the last *.psb backup taken with ProSave.
• RS-232 PC/PPI cable, 6ES7 901-3CB30 (for serial transfer).
• Or MPI PC adapter, 6ES7 972-0CA23-0XA0 (USB) / 6GK1 557-2AA00 (PCMCIA) for MPI transfer.

9.2 Serial Transfer (RS-232 PT/PC)

1. Connect the PC/PPI cable between the PC COM port and the OP7's PT/PC socket.
2. Power-cycle the OP7; the loader settles on "Ready for Transfer."
3. On the PC, launch ProSave. Choose OP7 as the device type, Serial as the connection, and the COM port number.
4. Set transfer parameters: Baud 19.2 kbps (or 38.4 kbps on later units), Data 8, Parity None, Stop 1.
5. Click File > Transfer > Project (Restore); point to the backup *.psb.
6. Monitor the progress bar; a successful transfer reports "Transfer complete" and a CRC match.
7. Power-cycle the OP7; the project should boot within 3 seconds.

9.3 MPI Transfer

1. Connect the USB-MPI adapter between the PC and the OP7's MPI socket. The MPI network must remain terminated (terminator at both ends, 220 Ω).
2. Set the OP7 MPI address to a value that does not collide with the PLC (default 1 is safe on most S7 networks if the PLC is address 2).
3. In ProSave, select MPI and set the PC's MPI address to 0 (auto).
4. Click Transfer > Project (Restore); point to the source file.
5. Watch the panel: it will display "Receiving" with a percentage counter.
6. After "Transfer complete," cycle the panel's 24 V supply.

9.4 ProTool Workflow (Live Source Project)

1. Open the source *.pdb in ProTool/Pro.
2. Choose File > Compile > Generate; confirm "0 errors, 0 warnings."
3. From the Online menu, click Transfer to OP.
4. Select the connection (Serial or MPI) and click Start.
5. Wait for the green "OK" status; this typically takes 30–90 seconds for a 256 KB project.

10. Verification and Commissioning Checks

A successful recovery is verified by walking the panel through its full I/O scan, not merely by checking the splash screen. The following sequence covers the typical commissioning checklist:

1. Confirm the panel boots to the configured start screen within 3 seconds of power-up.
2. Toggle each input that the panel reads; verify the tag value updates on the screen.
3. Force each output that the panel can write; verify the PLC receives the value.
4. Test the alarm acknowledgment path: trigger a configured alarm, acknowledge on the panel, confirm the alarm is logged.
5. Verify retentive recipes: change a recipe value, power-cycle, confirm the value is preserved.
6. Confirm time/date synchronization with the PLC (S7-200/300 date/time tag updates within 1 second of clock change).
7. Inspect ProTool's online diagnostics for "0 active connections" in the connection list; an unconnected tag is a common post-recovery oversight.

Document the firmware version, project CRC, and transfer date in the machine logbook so that future technicians can confirm the panel is the intended revision.

11. Preventive Measures and Best Practices

• Maintain a backup file. Export a *.psb via ProSave after every project change and store it in a versioned location tied to the machine's serial number.
• Label the keypad. Add a maintenance placard near the OP7 listing the boot-key sequence and warning that ESC + Right + Down during power-up erases the project.
• Replace the battery on schedule. A 5-year preventive replacement avoids the SRAM loss path. The OP7's lithium cell is field-replaceable in under 5 minutes.
• Use controlled transfers. Connect the PC to a UPS during transfers; do not interrupt a transfer in progress.
• Log transfer events. Capture ProSave's log into a project archive folder. This provides a paper trail for any flash degradation investigations.
• Plan for migration. The OP7 is end-of-life. For new machines, plan a migration path to a SIMATIC Comfort Panel or, for tight retrofits, a KTP700 Basic. The legacy ProTool project can be migrated using ProSave's converter or imported into WinCC Flexible / TIA Portal with the legacy importer.

12. FAQ