Resolving WinCC Unified VoT Download Failed Error on S7-1500

Problem Overview

When loading a WinCC Unified View of Things (VoT) application to a Siemens SIMATIC S7-1500 CPU, the engineering tool TIA Portal V17 returns the dialog "Download failed for selected web application" and aborts the transfer. The dialog appears even though the web server is enabled in the CPU properties, the project translation is complete, and a CPU1516TF-3 PN/DP with firmware V2.9 is connected and online.

The failure originates during the load step that copies the generated HTML/JS/CSS pages plus the runtime binary into the /web folder of the CPU file system. The download manager for the web application cannot allocate a valid container on the SIMATIC Memory Card (SMC). This symptom is typically caused by an undersized or corrupted SMC and is independent of the application logic. Resolving the error requires replacing the card with one that meets the published capacity requirement, then completing a clean compile and load sequence inside TIA Portal.

The reported root cause in field deployments is that the SIMATIC Memory Card inserted in the CPU is too small to host the generated web application bundle. Minimum thresholds established by Siemens for VoT deployment are 8 MB of usable SMC capacity; smaller cards (e.g., legacy 2 MB or 4 MB units) trigger the error message and leave no diagnostic-buffer entry that points to the card. In one installation a 2 GB consumer SD card was used in place of an SMC and produced the same error until the card was formatted. In another installation, replacing a 4 MB card with a 12 MB card resolved the issue.

Affected Versions and Hardware

The error is reproducible with any S7-1500 CPU that supports web-server-based VoT pages (CPU1510/1511/1512/1513/1515/1516/1517, including F and T variants) when the SMC does not satisfy the capacity requirement. CPU1516TF-3 PN/DP is a Safety/Fail-safe variant; presence of safety functions does not affect VoT loading once the card size is correct.

Root Cause: SIMATIC Memory Card (SMC) Capacity

A WinCC Unified VoT project compiles to a multi-megabyte file set. The web application bundle contains:

• The generated HTML5 pages with CSS and JavaScript
• Graphics, fonts, and user-defined controls
• Project language database (one set per configured language)
• Runtime configuration XML files
• Certificates and security descriptors
• Process tag mapping and image database
• An internal manifest describing screen hierarchy

Field deployments report sizes of 2-6 MB for a small VoT application; larger projects (many graphic screens, several languages) easily reach 15-25 MB. The published minimum usable installation requires an SMC with at least 8 MB of usable capacity. Anything below that threshold blocks the web-application load step with the generic dialog without producing a corresponding entry in the CPU diagnostic buffer.

Three observed sub-causes surface in field installations:

1. Legacy SMC below minimum — 2 MB or 4 MB SIMATIC Memory Cards are still in distribution channels and are sometimes shipped inserted in stock CPUs.
2. Consumer SD card used in place of SMC — Although the card is large at the file-system level, fragmented state and an incompatible allocation-unit geometry on certain consumer SD cards trigger the same load failure. Formatting the card through TIA Portal restores the correct file layout and resolves the issue.
3. Worn or corrupted SMC — Valid SMC with a corrupted boot sector after hot removal or a power loss during a prior download. Re-formatting or replacement of the card is required.

In every case the load step cannot write the web application manifest under /web on the CPU. Once the underlying card surface is recreated (formatted) or replaced with a card of suitable capacity, the load completes and the Web server delivers the VoT start page.

Symptom Checklist Before Touching the Card

Perform these checks in order before swapping memory cards. Each check produces an actionable result that may eliminate the need for hardware replacement.

1. Open the project in TIA Portal V17 and select the CPU in the project tree.
2. Confirm the firmware and TIA Portal versions: Project tree → CPU → Properties → "General" → "Identification & Maintenance" lists the firmware. TIA Portal: "Project" menu → "About" lists the build (e.g., V17.0 + Update 2).
3. Open CPU Properties → "Web server". Verify "Activate web server on this module" is selected.
4. Confirm user rights. CPU Properties → "Web server" → "User administration": a user with the role "Administrator" or a dedicated "web-access" role with all web-server permissions must exist.
5. Verify the SIMATIC Memory Card capacity. With TIA Portal closed, eject the card and read the label. Cards smaller than 8 MB will not load any VoT project. Note the article number and capacity.
6. Ensure the project translation is complete. Right-click the project → "Languages & Resources" → "Compile" must finish without errors. A missing translation occasionally surfaces as a "translation not found" log message, but in some failure paths it is masked as the web-application error.
7. Run a quick "Online → Accessibility" check to confirm the TCP connection to the PLC's PROFINET interface and verify the active connection rates match on both sides.

Solution 1: Replace the SIMATIC Memory Card

Use a Siemens SIMATIC Memory Card (SMC, type 6ES7954 series) with a capacity of 8 MB or larger. For projects with multiple language databases or large graphics, plan to use at least 24 MB so future expansions do not require another replacement. Keep the card article number and slot orientation in mind; the card inserts label-side outward on the front of the CPU.

1. Place the CPU in STOP mode.
2. Press the SMC ejector and remove the current card.
3. Insert the replacement SMC. The CPU performs a one-time automatic format and creates the /active and /backup partitions on first power-up.
4. Power on the CPU. Wait until the RUN/STOP and MAINT LEDs indicate the card is recognized — MAINT briefly flashes during the recognition phase, then transitions to RUN.
5. Reconnect TIA Portal and trigger "Download to device". Re-enter the password if prompted.
6. Confirm in the load log that the Web folder has been successfully created and the application manifest transferred.

Solution 2: Format the Existing Memory Card

If the card is a Siemens SMC that meets the 8 MB minimum, the load error can be resolved by formatting the card through TIA Portal rather than replacing it. Formatting recreates the required directory structure and reinitializes the file system that WinCC Unified VoT uses. This is the procedure that corrected the 2 GB consumer-SD occurrence in the field reports.

1. Close all runtime applications and disconnect TIA Portal from any active online session.
2. Place the CPU in STOP mode.
3. Remove the SMC from the CPU slot.
4. Insert the SMC into a card reader connected to the engineering PC.
5. From TIA Portal menu "Project" → "Card Reader/USB memory" → right-click the card reader entry → "Format" → select "SIMATIC Memory Card File System" (recommended) or FAT16b.
6. Alternatively, use a SIMATIC Field PG or any Windows PC to format the card with cluster size 32 KB and partition type "Primary". Avoid quick-format; full format is preferred so that the card's bad-sector list is refreshed.
7. Reinsert the card into the CPU. The CPU re-formats the card internally on first power-up and recreates the system folders.
8. Reload the VoT project.

Solution 3: Verify the Compile Settings

The VoT project must compile cleanly before it can be loaded. Use a standalone compile of the WinCC Unified application to bypass partial-compile inconsistencies that can leave the web bundle in an inconsistent state. This is the specific recommendation in the original Siemens-supported resolution path.

1. Right-click the WinCC Unified device in the project tree → "Compile" → "Software (rebuild all)" or "Compile completely".
2. Select the VoT project entry under the same device → right-click → "Compile" → "Compile standalone".
3. Watch the "Compile preview" dialog for warnings. Common warnings to address before retrying the download:

• "Unused tag" — remove or bind the tag in the screen that flags it.
• "Missing localization for screen X" — open the screen, set every text field's language table.
• "Property not supported" — adjust the property to a runtime-supported type.

4. After a clean compile, the project should download without errors.

Step-by-Step Recovery Procedure

The end-to-end sequence recommended for the reported configuration (TIA Portal V17, CPU1516TF-3 PN/DP, firmware V2.9):

1. Save and close the project in TIA Portal.
2. Back up the project to the engineering drive using "Project" → "Archive".
3. Place the CPU in STOP mode using the physical selector or via TIA Portal "Online" → "Stop".
4. Remove the SMC from the CPU.
5. Inspect the card label. Replace with an SMC ≥8 MB if currently smaller. If the card is ≥8 MB but the file system is suspect, proceed to the formatting step.
6. Format the card through TIA Portal or directly with a card reader.
7. Insert the card and power up the CPU.
8. Open the project. Confirm CPU Properties → "Web server" → "Activate web server on this module" is selected.
9. Confirm user rights under "User administration" — ensure the Administrator role has full access including "Read/write" for the web folder.
10. Right-click the WinCC Unified device → "Compile" → "Compile standalone".
11. Wait for the compile to complete. Resolve every error and warning in the "Info" window.
12. Connect to the CPU → "Online" → "Download to device".
13. In the "Load preview" dialog, tick "Replace all objects" and "Consistent download to target device".
14. Confirm. The transfer should now complete without the "Download failed" dialog.
15. Test the VoT pages from a browser pointing at https://<plc-ip>/vot.

Verification

A successful load is verified by several independent indicators:

1. The TIA Portal "Info" window reports no errors at the end of the download.
2. The CPU diagnostic buffer shows no WEBAPP or VOA_LOAD error entries. Acceptable events include "Load of user web pages" or "Web server state changed".
3. The CPU web interface is reachable at https://<cpu-ip>. Log in with the configured user and password.
4. The VoT entry point displays the configured start screen without layout errors.
5. Browse the "Files" view in TIA Portal ("Online & Diagnostics" → "Files") to confirm that the /web folder contains the loaded HTML and asset files.
6. Toggle the simulator or HMI tags bound to the VoT pages and confirm updates propagate to the browser.

Diagnostic Buffer and Log Markers

When the load fails, the CPU may generate diagnostic buffer entries under the source WEBAPP / Web Server. Reading the buffer enables quick fault classification even before exchanging the card. TIA Portal path: "Online" → "Diagnostics" → "Diagnostic buffer" → filter by "Web" or sort descending.

The exact event IDs vary by firmware version; treat the buffer entries as clues rather than exact codes. If no WEBAPP entry is recorded but the load still fails, the SMC capacity check (Solution 1) is still the most likely remedy.

Prevention and Best Practices

• Use Siemens SMC — adopt SIMATIC Memory Card (6ES7954 series) supplied by Siemens. Cards from the S7-1500 catalog guarantee the file-system layout and reduce the chance of subtle geometry mismatches.
• Size up front — maintain a card size of at least 24 MB per CPU used for VoT. Larger cards cost little extra and avoid capacity shortages after panel expansions.
• Always STOP before removal — do not remove or insert the SMC while the CPU is in RUN.
• Full project compile — always use a full project compile ("Compile → Software (rebuild all)" plus "Compile standalone" for VoT) before downloading VoT projects. Partial compiles can leave the generated web bundle in an inconsistent state.
• Archive the project — TIA Portal's "Project archive" keeps a full backup of the project, including generated web folders, so recovery is fast and complete.
• Firmware alignment — keep the CPU firmware at the level matching the TIA Portal version. TIA Portal V17 expects firmware ≥V2.9. Mixing firmware levels and TIA Portal versions can produce silent web-application incompatibilities.
• Document languages and certificates — record the project languages and certificate handling at the project level so future maintenance engineers know what to compile when adding fields or screens.
• Role-based web access — consider activating the web server with a separate user role dedicated to VoT, distinct from any maintenance user, and limit the role rights to minimize exposure.

Related Issues and Edge Cases

Compatibility Matrix

Use this table to audit multi-version fleets before updating the engineering toolchain. Each step up in TIA Portal usually also raises the recommended SMC size; keep the card at ≥24 MB to remain forward compatible.

Field-Proven Checklist

When all entries above read "OK", the original error is considered resolved and the project is production-ready. Re-check the page after any panel update that adds a new language, screen, or graphic asset; these edits increase the compiled size and may push a previously adequate SMC back below the threshold if the card was exactly at the minimum.

References and Additional Information

For full firmware-update procedures and CPU web-server option ranges, consult the official TIA Portal V17 help and the S7-1500 system manual on the Siemens Industry Online Support portal. Search the portal for entry ID "VoT load SIMATIC Memory Card" and the firmware entry for CPU1516TF-3 PN/DP V2.9 to retrieve the latest KB articles and example projects.

FAQ