Overview: The S7-1200 Upload Question
Uploading a program from a Siemens S7-1200 CPU to a programming device is one of the most common service operations on installed machinery, yet it is also one of the most common sources of frustration. Unlike the S7-300/400 families where the offline project file typically sits on a memory card or PG, the S7-1200 stores only compiled blocks (OB, FB, FC, DB, SDB, SFB, SFC) in its internal load memory. The full TIA Portal project - including comments, symbolic names, HMI screens, libraries, watch tables, and trace recordings - is not retained on the CPU.
The frequently asked question - "Can I upload the program to S7-1200 with any version?" - has a short and a long answer. The short answer is no. The long answer, documented in this reference, explains why version selection matters, which TIA Portal versions can read which firmware revisions, what to do when the upload fails, and how to recover the maximum possible information from a CPU whose offline project has been lost.
Why Version Selection Matters for S7-1200 Upload
TIA Portal is forward-compatible for upload but not backward-compatible. Concretely:
- A newer TIA Portal can upload a project created in an older TIA Portal (subject to firmware support limits below).
- An older TIA Portal cannot upload a project that was created with a newer TIA Portal or that targets a newer firmware version.
- If the firmware version on the CPU is newer than the TIA Portal's supported range, the upload fails with a version-mismatch dialog and no blocks are transferred.
The practical implication for a service technician who does not know what is installed: always start with the latest TIA Portal version that the laptop or company license server permits. If that fails, walk down one major release at a time. If the project was built in V13 SP1, attempting the upload with V13 SP1 (or any later release) is the correct starting point.
Compatibility Matrix: TIA Portal vs S7-1200 Firmware
The table below lists every publicly released S7-1200 firmware major version and the TIA Portal versions that can establish a working online connection and upload blocks. The mapping is verified against the Siemens Online Support delivery releases; firmware sub-versions (e.g. V4.4.2) inherit compatibility from the major version.
| S7-1200 Firmware | Earliest TIA Portal | Latest TIA Portal | Notes |
|---|---|---|---|
| V1.0 | STEP 7 Basic V10.5 | V13 SP2 (read-only) | Initial S7-1200 release; legacy CPU 1212C/1214C only |
| V2.0 | V11 | V13 SP2 | Adds PID, basic motion |
| V2.1 | V11 SP1 | V14 SP1 (read-only) | CPU 1211C introduced |
| V2.2 | V11 SP2 | V15.1 (read-only) | Released alongside S7-1500 |
| V3.0 | V12 SP1 | V16 (read-only) | High-speed counters, basic trace |
| V4.0 | V13 SP1 | V17 (read-only) | New OPC UA server, secure PG/PC communication |
| V4.1 | V14 | V18 (read-only) | S7-1200 G2 preview compatibility layer |
| V4.2 | V14 SP1 | V19 (read-only) | Expanded web server API |
| V4.3 | V15 | V19 (read-only) | OPC UA pub/sub method set |
| V4.4 | V15.1 | Current TIA Portal | Recommended for new installations |
| V4.5 | V16 | Current TIA Portal | Adds user-defined web pages |
| V4.6 | V17 | Current TIA Portal | Current production firmware |
Refer to the canonical Siemens support entry for live updates: Which versions of STEP 7 (TIA Portal) support which firmware versions of the S7-1200 CPU?
Prerequisites Before the Upload
- Network path: PROFINET cable (direct or via switch) or MPI/PROFIBUS for legacy CPUs. The S7-1200 has no MPI port; only PROFINET.
- CPU IP address: Must be known or reachable. If unknown, use the Online → Accessible nodes function (broadcast discovery). For unconfigured CPUs, the default IP is 192.168.0.1 with subnet mask 255.255.255.0.
- PG/PC interface assignment: In the TIA Portal, set the network adapter that is physically connected to the CPU under Online → Accessible nodes → PG/PC interface.
- TSAP / Rack / Slot: S7-1200 is always rack 0, slot 1; the TSAP is fixed at 01.01.
- Protection level: The CPU's access protection (full access, read-only access, or HMI access) determines what can be retrieved. Know-how-protected blocks cannot be read regardless of version.
- Password: If the project is password-protected, obtain the password from the machine builder or operator before attempting upload.
- CPU mode: The CPU may be in RUN, STOP, or start-up. Uploading from a CPU in RUN mode is permitted but increases the chance of inconsistent DB values being captured.
Step-by-Step: Upload Procedure in TIA Portal
The recommended procedure assumes the offline project is not available. If an offline project already exists, skip steps 4-7 and use Online → Compile and download → Upload to PG/PC instead.
- Open TIA Portal and select Open existing project → Empty project. Create a temporary workspace.
- From the project tree, click Online → Accessible nodes. The portal broadcasts a discovery packet on the configured network adapter. After approximately 5-15 seconds, every reachable S7-1200 CPU appears with its MAC address, IP, and (if accessible) firmware version.
- Right-click the target CPU and select Online → Upload from device (software). The wizard opens.
- In the Upload preview dialog, the wizard lists the device type and the firmware version detected on the CPU. Confirm the device configuration.
- Select Upload as new station if no matching offline device exists in the project tree. The CPU's complete block folder (OB, FB, FC, DB, SDB, system blocks) is transferred.
- Accept the destination folder. TIA Portal creates a new device object under Devices & networks.
- After the upload, open Program blocks to verify that all expected blocks are present. Compare counts against the machine documentation or I/O list as a sanity check.
- Use Online → Compare offline/online to verify the local project now matches the CPU one-to-one.
Upload Methods Compared
| Method | Menu Path | Result | Use Case |
|---|---|---|---|
| Upload from device (software) | Online → Upload from device | Complete block folder to a new station | No offline project available (most common field scenario) |
| Upload to PG/PC | Right-click device → Upload to PG/PC | Updates an existing offline device to match the CPU | Offline project exists but is stale |
| Snapshot (read-only) | Online → Snapshot of online data | Captures current tag values without modifying the project | Diagnostics; value trending |
| Drag-and-drop from Accessible nodes | Drag CPU to project tree | Same as Upload from device | Quick capture during commissioning |
| S7-SIMATIC Manager Upload | STEP 7 (classic) → PLC → Upload Station | Only works for S7-200/300/400, not S7-1200 | Do not use for S7-1200 |
Decision Flowchart: Which TIA Portal Version Should You Use?
The diagram below codifies the version-selection heuristic for a technician who is about to walk up to an unknown S7-1200.
Common Errors and Root Causes
| Error / Symptom | Root Cause | Resolution |
|---|---|---|
| "The online interface is not accessible" | PG/PC interface not assigned or wrong subnet | Configure Online → Accessible nodes → PG/PC interface; verify IP and subnet match |
| "The device is configured for a different firmware version" | TIA Portal older than the firmware on the CPU | Upgrade TIA Portal to a version supporting the firmware (see matrix above) |
| "The connection has been interrupted" | Cable fault, firewall, or PROFINET topology loop | Replace cable; disable Windows firewall on the PG/PC adapter profile |
| "You do not have sufficient access rights for this operation" | CPU protection level set to "No access" or "HMI access" | Connect as the configured user, or reset CPU to factory defaults (loses program) |
| "The block is know-how protected" | Block compiled with know-how protection enabled | Obtain original SCL source from the machine builder; upload alone cannot decrypt |
| Upload completes but DB values are zeroed | CPU in STOP during upload, or DBs defined as non-retentive | Repeat upload with CPU in RUN; verify retentivity settings of the original DBs |
| "The online data of the device cannot be read" (TIA V11/V12) | CPU firmware newer than V2.2, requiring TIA V13 SP1 or later | Install at least TIA V13 SP1; V11 SP2 only supports firmware up to V2.2 |
Special Cases and Field-Proven Caveats
Know-How Protected Blocks
Blocks compiled with the Know-how protection attribute in SCL or FBD are uploaded as black-box placeholders. The interface (IN, OUT, IN_OUT, STAT, TEMP declarations) is preserved; the algorithm body is replaced with a stub. Only the original SCL source or the unprotected block file from the offline project can restore the body.
Password-Protected CPUs
When the CPU has a configured access password and the project on the PG has none, TIA Portal prompts for the password at the start of the upload. Without the password, the CPU rejects the connection with W#16#8082 ("Resource is not available") at the S7 communication layer.
CPU in Factory-Fresh State
A never-configured CPU (default IP 192.168.0.1) responds to accessible-node broadcast but has no blocks to upload. TIA Portal reports "The device does not contain any online data." This is not an error; it means the CPU has never been downloaded to. Confirm with the operator whether the machine has ever run before troubleshooting further.
Migrating an Uploaded Project Forward
An uploaded project in TIA V13 SP1 can be migrated upward to a newer TIA Portal via Project → Migrate project. Migration preserves blocks and tags but recompiles the project. After migration, download to the CPU only after verifying with Online → Compare that the migrated offline project matches the live online state block-for-block.
Lost Symbolic Names and Comments
The S7-1200 stores symbolic names in the CPU's symbol table only if the project was downloaded with Download with symbolic names enabled. If the original download skipped this option, uploaded blocks show only absolute addresses. Comments are never transferred to the CPU; they exist only in the offline project. Recovering them requires the machine builder's source.
Verification After Upload
- Block count match: Compare the number of OBs, FBs, FCs, DBs, SDBs against the documentation. A missing system block (SDB 1000-1999) usually indicates a hardware configuration mismatch.
- Offline/online compare: Use Right-click Program blocks → Compare offline/online. All blocks should display the green check icon.
- Watch table functional test: Create a watch table, go online, and force a known I/O point. The output should react, confirming that the tag references resolved correctly.
- Compile: Run Project → Compile all. If the upload came from a newer TIA Portal than your local one, compilation may produce warnings about unused tags or syntax deprecations. These warnings are informational, not errors.
Best Practices for Long-Term Project Preservation
- Always archive the TIA Portal project (Project → Archive) and store the .zap* file in version control (Git LFS, SVN, or a managed PLM).
- Export the PLC tag table and I/O assignment to CSV at every major revision; CSV survives TIA Portal version changes.
- Maintain a machine log file that records TIA Portal version, firmware version, and project SHA hash per device. The hash allows a future upload to be compared byte-for-byte.
- Enable Download with symbolic names on every download operation. This ensures that even if the offline project is lost, symbolic information can be reconstructed from the CPU.
- Apply firmware updates through a controlled process; never update the firmware without an offline backup of the project, because some major firmware revisions (e.g. V3 to V4) require project recompilation.
Related Siemens Documentation
- Which versions of STEP 7 (TIA Portal) support which firmware versions of the S7-1200 CPU? - The canonical compatibility reference.
- S7-1200 programmable controller system manual - Hardware, addressing, and protection-level details.
- STEP 7 (TIA Portal) upload options - Wizard procedures and behavior on version mismatch.
- S7-1200 firmware update procedure - Required when forcing a CPU to a compatible firmware.
- How do you reset an S7-1200 to factory defaults? - Last-resort procedure when the password is unknown.
FAQ
Can I upload an S7-1200 program with any TIA Portal version?
No. TIA Portal is forward-compatible only. The TIA Portal version used for the upload must be equal to or newer than the version that originally created the project, and it must support the firmware version on the CPU. Start with the latest TIA Portal you have and step down only if the upload fails with a version-mismatch error.
Which TIA Portal version supports the S7-1200 firmware installed on my CPU?
Use the compatibility matrix above or the live Siemens support entry at support.industry.siemens.com. As a rule, TIA V13 SP1 covers firmware V4.0, V14 covers V4.1, V15 covers V4.3, V15.1 covers V4.4, V16 covers V4.5, and V17 covers V4.6.
The upload says "The device is configured for a different firmware version." What now?
The TIA Portal you are using is older than the firmware on the CPU. Install the newest TIA Portal your license permits, or apply a CPU firmware update to a version supported by the TIA Portal you have. Mixing a newer CPU with an older TIA Portal will not work.
Why are symbolic names and comments missing after upload?
The S7-1200 only stores symbolic names if the project was downloaded with the "Download with symbolic names" option. Comments are never stored on the CPU. To recover full project fidelity you need the offline .zap* archive from the original programming laptop.
Can I upload an S7-1200 over the MPI/PROFIBUS port of an S7-300?
No. The S7-1200 has no MPI or PROFIBAS interface; PROFINET (or the legacy RS-232 service interface on firmware V1/V2 CPUs only) is required. Use a PROFINET-capable network adapter on the PG/PC and configure the correct PG/PC interface in TIA Portal.