S7-1200 TIA Portal V13 Backup: Resolving Grayed-Out Menu

Problem Statement: Grayed-Out "Download Backup" on S7-1200

Engineers using TIA Portal V13 with an S7-1200 CPU running firmware version 3 frequently encounter a non-functional "Download backup" entry in the Online menu. The option appears grayed out (inactive) even when the project is opened, the CPU is added as a device, the user is connected online (the "Go online" action completes and the status indicator turns green), and the CPU responds to STOP/RUN commands. This behavior is not a defect, an installation error, a license deficiency, or a corrupted project file—it is the expected state of the TIA Portal menu when working with the S7-1200 platform, because the "Online Backup" function does not apply to this controller family.

The Siemens TIA Portal documentation explicitly limits the Online Backup (also surfaced in the menu as "Download backup") to the following device types: S7-300, S7-400 with Flash memory card, ET 200S, and ET 200Pro. The S7-1200 is intentionally not listed because its backup mechanism is implemented through a different workflow, not because the function is hidden, locked, or licensed. Operators who interpret the gray menu as a configuration error typically waste hours searching for non-existent options, license keys, or service packs. The remainder of this reference maps the three legitimate backup paths for the S7-1200, the TIA Portal version compatibility matrix, the part numbers involved, and the field-tested step-by-step procedure for each path.

Why "Download Backup" is Grayed Out on S7-1200

The "Online Backup" feature in TIA Portal targets the legacy backup model used by S7-300/400: a complete image of the load memory is streamed to the engineering station (PG/PC) and written to a single archive file. The S7-1200 architecture differs in three respects that make this model unsuitable:

1. Load memory topology. S7-1200 stores the user program, hardware configuration, and PLC tags on internal flash memory that is permanently mounted on the CPU. There is no separate load memory image that can be streamed as a single binary block; the program is always present in flash, so an "image" backup would simply duplicate the on-line blocks with no incremental value.
2. Service concept. Service on S7-1200 is performed with a SIMATIC memory card (SD card, part number prefix 6ES7954-8). The card acts as a transfer medium, a service medium, a recipe medium, a data-log medium, and a firmware update medium. The intended field-service workflow is: pull the SD card from the CPU, duplicate its contents on a card reader, and write the duplicate back to the original card or a replacement card if a restore is needed.
3. Configuration delivery. Modern engineering practice (since the S7-1200 generation) is to maintain the canonical project on the engineering station and download it to the PLC. Recovery is performed by re-downloading the project from the engineering station, not by restoring a binary image captured at an earlier point in time.

Because of these architectural differences, the TIA Portal menu item is intentionally disabled for S7-1200 devices. Engineers should ignore the gray menu and use one of the three alternatives described in this reference.

Three Supported Backup Methods for S7-1200

Three backup paths are supported on S7-1200 CPUs running firmware V3.x with TIA Portal V13 or later. The choice of method depends on what is being backed up, what hardware is available, whether a TIA Portal project already exists, and how the file will be used for restore.

Each method captures a different subset of the PLC's persistent state. The table below maps what is captured and what is not.

The selection logic is summarized in the following decision diagram.

TIA Portal V13 and S7-1200 FW V3 Compatibility Matrix

Firmware version 3 of the S7-1200 was released by Siemens in 2014 (CPU order numbers ending in -0XB0 for compact CPUs). The version of TIA Portal in use must match the firmware on the CPU; otherwise the project will not compile, online operations will be restricted, and the "Backup from online device" menu will remain grayed out.

To check the TIA Portal version: launch TIA Portal, click Help > About. The "TIA Portal Version" field shows the version string (e.g., "V13 SP1 Update 9" or "V13 SP2"). The corresponding device description files are listed in Options > Support Packages > Installed Support Packages. If a Hardware Support Package (HSP) is missing for the CPU, install it from the Siemens Industry Online Support portal.

CPU Identification and Compatible SIMATIC Memory Cards

Before performing a backup, identify the CPU order number and the SIMATIC memory card part number. The order number is printed on the front of the CPU, on the packaging label, and in TIA Portal under Online & Diagnostics > Diagnostics > Device Information. The firmware version appears in the same dialog under the "Firmware" field.

Method 1: Upload Blocks from Device to PG/PC

This method generates a fresh, editable TIA Portal project from the online blocks. It is the correct choice when the original project file is missing or out of date, and the engineer needs to modify, document, archive, or re-download the program. The output is a complete project file that can be opened, edited, recompiled, and downloaded.

Prerequisites

• TIA Portal V13 SP1 or later installed (matching the CPU firmware)
• S7-1200 reachable on the same subnet (PROFINET, Ethernet, or routed through a network gateway)
• CPU is online (the status indicator next to the device in the project tree shows a green check mark)
• Know-how protection password if the CPU is configured with block protection (otherwise the protected blocks upload as "unreadable" placeholders)
• At least 200 MB of free disk space for the new TIA Portal project file

Step-by-Step Procedure

1. Open TIA Portal. If a project is open, close it (Project > Close). The upload creates a new, untitled project.
2. Click Online > Accessible Devices. The "Accessible Nodes" dialog opens.
3. Select the network interface that reaches the CPU. For built-in Ethernet, choose the PG/PC interface assigned to the Intel, Realtek, or Broadcom adapter connected to the plant network. For CP 1613/1623 or CP 5711, choose the corresponding Siemens interface. Click Start Search.
4. The accessible devices list populates with the CPU IP, MAC, and device name. Double-click the target CPU to open the Online & Diagnostics view.
5. From the project tree, right-click the project root (top-level entry), then select Upload from device > Software (only). The "Upload preview" dialog appears.
6. Confirm the upload. TIA Portal creates a new, untitled project, transfers the blocks from the CPU, and places them under Program blocks > System blocks / Program blocks.
7. Save the project immediately: Project > Save As, then choose a name and a folder. The file extension is .ap13 for V13 projects, .ap14 for V14, .ap15 for V15, etc.
8. Compile the project to confirm integrity: Project > Compile > Software (rebuild all). The status bar must show "Compile finished without errors".

Transfer Time Estimate

The upload time is dominated by the PROFINET/Ethernet transfer. Use the formula below to estimate the worst-case time for a known project size:

Where:

• S = total program size in KB (DB initial values + code blocks + system data)
• R = nominal link rate in Mbps (100 for PROFINET, 1000 for gigabit Ethernet)
• η = utilization factor, typically 0.4–0.6 for TCP/IP S7 communication, lower under heavy plant traffic

For example, a 500 KB program over 100 Mbps Ethernet at η = 0.5 yields t = 500 × 1024 × 8 / (100 × 10^6 × 0.5) = 4.10 / 50000 = 0.082 s. TIA Portal typically adds 10–30 s of overhead for handshake, compile, and metadata. Plan for 30–60 s of total wall-clock time for a typical 1–2 MB program.

Method 2: Backup from Online Device

This method creates a compressed archive containing the complete CPU state: blocks, hardware configuration, IP settings, time settings, and CPU properties. The file can be restored with Online > Restore from online device backup to the same CPU type, or downloaded to a new CPU of the same type as a clone. The output is a single .s7pbkp file, which is a ZIP archive with a TIA Portal–specific structure (folders Program blocks, IM, CPU, SystemData).

Prerequisites

• TIA Portal V13 SP1 Update 4 or V13 SP2 (or any V14+ version)
• Online connection to the target CPU
• CPU must be in STOP or RUN; both work for backup, and the operation does not interfere with running I/O scan
• Read-access to all blocks (no exclusive password, no read-only password protection)
• At least 50 MB of free disk space for the resulting archive

Step-by-Step Procedure

1. Open the project that contains the CPU device, or open the CPU in Online & Diagnostics from the accessible devices view.
2. Right-click the CPU in the project tree. Choose Online & Diagnostics if not already open.
3. From the Online menu, click Backup from online device. The dialog Create backup of online device opens.
4. Select the storage path and filename. The default extension is .s7pbkp. To inspect the contents, rename to .zip and extract with any standard tool such as 7-Zip, WinRAR, or the Windows 10 built-in ZIP support.
5. Click Start Backup. The progress bar shows the transfer state. A typical 50-block program completes in 30–120 seconds over PROFINET.
6. Verify the backup file size matches the expected size. A 1 MB project will produce a backup file of similar order of magnitude; the compression ratio is roughly 2:1 to 5:1 for textual SCL code and roughly 1.1:1 for compiled STL/FBD code.

Step-by-Step: Restore from Backup

1. Connect to the target CPU online.
2. Online > Restore from online device backup. Select the .s7pbkp file.
3. TIA Portal matches the file to the CPU order number. If the order number differs, the restore is refused. The CPU must be reset to factory defaults or be in a compatible state (CPU order number identical, firmware version equal or higher).
4. Confirm the transfer. The CPU goes to STOP, the program is overwritten, the CPU restarts.
5. Wait for the MAINT LED to clear and the RUN LED to return solid green (or solid yellow in STOP). The process takes 10–60 seconds depending on the program size.

Method 3: SIMATIC Memory Card Program Copy

The SD card is the only field-service path that does not require a PG/PC. The card is inserted into the CPU, and the program is copied from internal flash to the card (or vice versa) by a power-cycle operation or by a menu action in TIA Portal. This method is the standard for field service on machines shipped with a SMC in the accessory bag.

Copy from CPU to Card (Program Backup)

1. Insert a SIMATIC memory card (any size 4 MB or larger) into the CPU's card slot. The CPU must remain powered.
2. Power-cycle the CPU (turn off, wait 5 seconds, turn on) OR use the TIA Portal menu Online & Diagnostics > Functions > Program copy from internal flash to SIMATIC memory card.
3. The MAINT LED flashes during the copy. The RUN/STOP, ERROR, and MAINT LEDs indicate progress: MAINT solid + STOP solid = copy complete.
4. Remove the card once the MAINT LED returns to its previous state. The card now contains a complete copy of the CPU program in the directory structure S7_JOB\S7OS with the main file SIMATIC.S7S.

Copy from Card to CPU (Program Restore)

1. Insert the source card into the CPU. Power off.
2. Power on the CPU. The CPU detects a card with a valid program and offers to copy it. Press the selector switch (the front-panel knob) within 10 seconds to confirm, or use TIA Portal to trigger the copy remotely.
3. The CPU copies the program from card to internal flash. On completion, the CPU restarts with the new program. The RUN/STOP LED indicates the new state.

Card File System Reference

The SIMATIC memory card file system is FAT32 with a specific directory layout:

Use Cases

• Field service without a PG/PC. A technician carries a pre-loaded card, not a laptop, and updates a fleet of identical machines.
• Mass deployment. One card programs 50 identical machines during commissioning.
• Firmware update. The card can hold a firmware file (file extension .upd) that the CPU applies during power-up if a newer firmware is detected.
• Data extraction. Data logs, recipes, and user files can be copied from the CPU to the card for offline analysis.

Project Migration and Version Compatibility

If the backup must be loaded into a TIA Portal version different from the source CPU firmware supports, the project requires migration. The TIA Portal migration rules are summarized below.

To migrate: open the project in the target TIA Portal, follow the migration wizard that appears automatically. The wizard reports any unsupported features (e.g., new instructions introduced in V14 SP1 such as PEEK_BOOL variants, or new motion control blocks). Resolve or accept the warnings before saving. The migrated project should be compiled with Project > Compile > Software (rebuild all) and downloaded to a test PLC before being deployed to production.

Verification: Confirm a Successful Backup

1. Method 1 (Upload to PG/PC). Open the saved .ap13 file. Verify the program blocks, hardware configuration, and PLC tags are present. Compare the block count to the source CPU under Online & Diagnostics > Diagnostics > Device Information > Block Counters. Compile the project: Project > Compile > Software (rebuild all). The status bar must show "Compile finished without errors".
2. Method 2 (Backup from online device). Open the .s7pbkp file in TIA Portal: Project > Retrieve. The wizard extracts the archive and displays the project. Compare block count and DB initial values to the running CPU. As a final verification, restore the backup to a second CPU of the same order number and confirm the second CPU starts in the expected state.
3. Method 3 (Memory card). Insert the card into a card reader attached to the PG/PC. The card appears as a removable drive. Verify the file SIMATIC.S7S and the directory S7_JOB are present. The file size of SIMATIC.S7S reflects the program size. A 200 KB program produces a SIMATIC.S7S of approximately 200–300 KB.

Troubleshooting Matrix

Field-Proven Tips and Edge Cases

• Backing up a password-protected CPU. The CPU allows backup with the configured read access password ("Read access" protection level in Siemens terminology), but the protected blocks in the backup are encrypted. Store the password with the backup file; otherwise the restore is useless when no CPU-side copy exists.
• Backing up while the process is running. All three methods work with the CPU in RUN. The "Upload to PG/PC" captures a snapshot; the process data in the snapshot is not the current values but the values at the time of block fetch (initial values for DBs).
• Backing up a CPU with active OPC UA server. The server security certificates are not included in the backup. Re-import the certificates after a restore. The certificates live in the CPU's certificate store, which is separate from the load memory.
• Comparing two backups. Open the first .s7pbkp in TIA Portal, save the project. Open the second backup, save as a different file. Use a folder-diff tool (e.g., WinMerge) on the extracted Program blocks directory to identify which blocks changed between the two snapshots.
• Time zone in backups. The CPU stores the time in UTC internally. The backup file includes the local time zone offset. When restoring to a CPU in a different time zone, the wall-clock time displays in the local zone without conversion errors.
• Backup before firmware update. Always perform a backup before applying a firmware update. The firmware update process is destructive of the program on some CPU versions; the backup is the only recovery path.
• Backup of a CPU with active forcing. Forced I/O points are not part of the program; they are stored in the CPU's force table. The force table is not included in any backup method. Re-apply the force table manually after a restore.

Windows 10 Engineering Station Considerations

The user reports TIA Portal V13 on Windows 10. Several Windows 10 behaviors affect S7-1200 communication, backup, and project integrity:

• Network profile. Windows 10 disables network discovery by default on public networks. Set the network profile to Private in Settings > Network & Internet > Status > Network status. The CPU responds to PROFINET discovery only on private profiles.
• Windows Backup of the engineering station. Use the built-in Windows Backup to protect the engineering station itself (TIA Portal project files, license keys, custom libraries, TIA Portal Help database). See the Microsoft Windows Backup documentation for the procedure. This is a separate concern from PLC backup, but both are required for a complete recovery strategy.
• Firewall rules. Windows Defender Firewall blocks ISO-on-TCP (port 102) and PROFINET (UDP 34964) by default. Add inbound rules for Siemens.Automation.Portal.exe and S7oiehsx64.exe (the TIA Portal communication service). Without these rules, the CPU will not appear in the accessible devices list.
• Power management. USB-attached CP 5711 / PC adapters may be suspended by Windows 10 USB selective suspend. Disable in Device Manager > USB Root Hub > Power Management > Allow the computer to turn off this device to save power.
• Antivirus exclusions. Exclude the TIA Portal installation directory (%ProgramFiles%\Siemens\Automation\) and the project directory from real-time scanning. Several antivirus products quarantine .s7pbkp files as encrypted archives, breaking backup workflows.
• OneDrive / cloud sync. Do not store TIA Portal project files in OneDrive, Dropbox, or any cloud-synced folder. The sync client can write a partial file mid-save, corrupting the project. Use a local or mapped network drive.

FAQ