C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Why a PCS 7 V9.0 UpdateCollection Will Not Upgrade an SP1 Installation

Why a PCS 7 V9.0 UpdateCollection Will Not Upgrade an SP1 Installation

A PCS 7 UpdateCollection requires the matching complete PCS 7 base release; it is not the Service Pack installer that upgrades an SP1 system to SP2 or SP3. Siemens explicitly lists an SP2 base for V9.0 SP2 UC03 and an SP3 base for V9.0 SP3 UC03. Check the installed system release rather than a component's SP label, establish the authorized target base installation, then apply its collection. Treat a move to V9.1 and its license upgrade as a separate decision.

Table of Contents

Distinguish the Product Release from a Component Update

Installing an SP2 package for one component, such as a library, does not establish that the complete engineering station has become PCS 7 V9.0 SP2. Record the installed PCS 7 system release and the component versions separately.

The decisive installer prerequisite is version-specific. Siemens' V9.0 SP2 UC03 readme accepts PCS 7 V9.0 SP2, with or without UC01/UC02. Its V9.0 SP3 UC03 notes instead require PCS 7 V9.0 SP3, with or without UC01/UC02. Neither list identifies a V9.0 SP1 system as the qualifying base. SP2 readme, section 4.23; SP3 readme, section 5.23

Establish the Correct Base Before Applying UC03

For a test PC, use this version-selection workflow before installation:

  1. Record the current system and component inventory. Retain the actual name and version of the previously installed package rather than inferring its scope from SP2 in its title.
  2. Choose the required target: V9.0 SP2 UC03, V9.0 SP3 UC03, or a separately planned V9.1 upgrade.
  3. Obtain the complete, authorized PCS 7 installation media for that target base and confirm the supported operating-system and installation path.
  4. Preserve project data, licenses and a recoverable PC state before changing the installation.
  5. Establish the target base installation using its applicable system setup procedure. A component patch or UC is not a replacement for that base.
  6. Only after confirming the base release, apply the UC belonging to that same release and regional edition.

This is a release-selection and prerequisite procedure. It does not assert that every existing SP1 computer supports an in-place upgrade; the PC operating system, installed options and approved target path determine that choice.

UC03 Does Not Require Installing Every Earlier UC

For V9.0 SP2 UC03, Siemens explicitly says the collection replaces the previous collections for that PCS 7 version. Its prerequisite list includes the unpatched SP2 base. For V9.0 SP3 UC03, the documented list likewise includes the SP3 base and earlier UC levels.

Therefore, once the correct base and other requirements are met, installing UC01 and UC02 merely as stepping stones is not required by these UC03 prerequisites. This is evidence for those named collections, not a universal rule for every Siemens update product.

The SP3 notes identify PCS7_V903_UC03.exe as that collection's setup. Confirm the package identity and read the included component readmes before using it; do not bypass a failed base-version check.

Treat V9.1 Licensing as a Separate Upgrade Decision

Siemens' 2021 ST PCS 7 catalog, section 16/2, documents a SIMATIC PCS 7 Engineering Upgrade Package AS/OS V9.0 to V9.1. That establishes an upgrade route; it does not support assuming that an existing V9.0 engineering license automatically entitles the holder to V9.1.

Identify the actual engineering, OS and option licenses and the relevant Certificate of License before ordering or upgrading. The broad statement that every license behaves identically across all Service Packs or every V9.1 component requires the same purchase is not established here. Siemens catalog, section 16/2

Verification

After the base installation, confirm the PCS 7 release before applying the chosen UC. After the UC, compare installed component versions and setup results with the applicable UC component table.

Open a backed-up test project and validate the required engineering tools in the approved test environment. Successful setup does not prove project compatibility, licensing of every option or readiness for a production AS download.

Limitations and Operational Precautions

The exact package previously mistaken for a PCS 7 SP2 installer and the PC's operating system were not supplied. No exact in-place upgrade sequence or customer-specific license entitlement is inferred.

Keep recoverable installation and project backups and use approved license-transfer procedures. Do not transfer projects to production or download to the H system merely to validate that the installer now accepts the UC. Software installation, project conversion, compilation and controller downloading are separate changes.

Engineer FAQ

Why does UC03 reject a computer where I installed something labeled SP2?
Verify whether that package updated only a component. The UC requires the matching complete PCS 7 base release.

Must I install UC01 and UC02 before these UC03 packages?
The cited SP2 and SP3 UC03 prerequisite lists include their respective base releases, so those earlier UCs are not required stepping stones.

Technical References

Related Articles

Related Tags

20 respuestas