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

Upgrade a PCS 7 V7.1 SP4 Project Directly to V9.1 SP1

Upgrade a PCS 7 V7.1 SP4 Project Directly to V9.1 SP1

Yes. A project configured with SIMATIC PCS 7 V7.1 SP4 or later can use Siemens' documented V9.1 SP1 software-update procedure with utilization of new functions; that project route does not require an intermediate V8.2 SP1 project. First bring a V7.1 SP3 project to SP4 and verify it. The migration is a controlled, multistage engineering operation: Siemens requires CPUs in STOP for this route and specifies backups, hardware and library checks, project conversion, compilation, downloads and station activation.

Table of Contents

Applicability and upgrade path

Siemens' PCS 7 V9.1 SP1 “with utilization of new functions” manual lists PCS 7 V7.1 SP4 or higher as the source project level. Thus, a project genuinely converted and checked at V7.1 SP4 does not require an intermediate V8.2 SP1 project for this route. By contrast, the separate “without utilization of new functions” manual starts at V8.2 SP1 or higher and recommends older projects be updated to that level by following the corresponding manuals.

This project migration path is distinct from updating the PCS 7 software installed on PC stations. Siemens states that PCS 7 software older than V9.1 cannot be directly updated in place to V9.1 SP1; the documented PC software procedure requires a clean installation on a supported operating system. Check the V9.1 SP1 Readme for the exact current platform requirements.

Select the update method

Use the V9.1 SP1 with-new-functions service manual when the project has reached V7.1 SP4 or higher and will follow that workflow. Siemens requires the CPU to be switched to STOP for this route; applicability and detailed tasks depend on the CPU type and libraries.

The without-new-functions route is separate. Its V9.1 SP1 manual specifies a starting project level of V8.2 SP1 or higher. Do not apply that baseline to the with-new-functions route or infer from it that every V7.1 project must be migrated through V8.2.

Prepare for the migration

  1. Confirm the actual PCS 7 project level. If the project is still at V7.1 SP3, first complete the applicable V7.1 SP4 update and verify the resulting project before proceeding.
  2. Check the V9.1 SP1 Readme and documentation for supported PC operating systems, hardware, modules, libraries, add-ons and licenses. Siemens notes that CPU type and libraries affect the update and advises obtaining product-specific guidance for PCS 7 add-ons.
  3. Back up PCS 7 project data, user-created libraries, operator/display texts and license keys or authorizations. Establish and verify a recovery plan.
  4. Plan a controlled outage. The with-new-functions update requires AS CPUs in STOP. Confirm operational authorization, system state and rollback responsibilities before starting.

The Siemens procedure overview also includes network-adapter checks, hardware preparation, installation of PCS 7 and additional libraries, project migration, Plant Hierarchy consistency, hardware and NetPro adaptations, CFC/SFC conversion, block/library updates, OS work, compilation, downloads and station activation.

Follow the documented V9.1 SP1 sequence

Use the applicable Siemens service manual for the complete, version-specific steps. Its with-new-functions task sequence includes:

  1. Back up the project and related engineering data, and prepare hardware and PC stations.
  2. Install PCS 7 V9.1 SP1 and the additional or non-standard libraries required by the project, following the relevant installation manuals.
  3. Update the project on the engineering station. Migrate OS projects, check Plant Hierarchy consistency, and adapt hardware configuration, CPU properties and NetPro connections as applicable.
  4. Convert CFC and SFC charts and perform the block and library update sequence. Siemens specifically notes removal of obsolete standard-library blocks such as OB_DIAG, OR_M_16 and OR_M_32 before adding new library blocks when those blocks are present.
  5. Complete OS and Maintenance Station adaptations, compile charts and OS, and review the compilation logs.
  6. Download changes to target systems in the order and conditions prescribed for the actual system. Siemens specifies activation order of master OS server, redundant standby server, then OS clients.
  7. Apply the separate update documentation for SIMATIC BATCH, SIMATIC Route Control or other installed add-ons where relevant.

This is a staged engineering project update, not a one-click conversion. Follow all detailed steps and branch conditions in the manuals rather than treating the summary here as a substitute.

Verify library and license requirements

The discussion reports PCS 7 Library V7.1 SP3 Update 4, PCS 7 Industry Library V9.0 SP1, PCS 7 Faceplates V7.1 SP3 Update 1 and PCS 7 Basis Library V8.2 Update 12. Treat these as reported details of that project, not a universal V9.1 SP1 prerequisite list: the cited upgrade manual does not establish that exact combination for all projects. Check actual block usage and the release documentation for every library before migration.

Siemens states that corresponding upgrade license keys are needed when updating from V7.1 SP4 through V9.1.x. Project-level eligibility alone does not confirm compatibility of specific CPUs, modules, libraries, add-ons, licenses or operating systems.

Verification

Keep evidence of each stage. Confirm backups are usable and establish the starting project and AS state before making changes. During migration, resolve project-migrator, hardware, connection, chart-conversion and compilation errors; opening the project alone does not demonstrate a successful update. Review compilation logs and verify that generated target configurations match the approved design.

After downloads and activation under the site's approved outage plan, verify required AS/OS communications and process behavior against project-specific acceptance criteria. For redundant OS configurations, verify the server and client behavior after following Siemens' documented activation order. No installation or laboratory test is claimed here.

Limitations and Operational Precautions

The direct project path applies only when the project fully corresponds to PCS 7 V7.1 SP4 or higher and the with-new-functions workflow is used. A project starting at V7.1 SP3 must first be updated to SP4. The separate V9.1 SP1 without-new-functions manual has a V8.2 SP1 baseline.

The manuals do not guarantee compatibility for every plant configuration. Confirm the target PC operating system, hardware, firmware, CPU, libraries, add-on products and licenses against applicable Siemens documentation. The with-new-functions route requires CPUs in STOP, so treat the work as a controlled outage. Back up the project and related data and use the site's approved rollback and process-safety plan before downloads or activation.

Engineer FAQ

Can a V7.1 SP4 project go to V9.1 SP1 without an intermediate V8.2 project? Yes, under Siemens' documented with-new-functions route; its stated source project level is V7.1 SP4 or higher.

Does the same answer apply to the without-new-functions route? No. Its V9.1 SP1 manual specifies a V8.2 SP1 or higher project baseline.

Can I start the V9.1 SP1 project update from V7.1 SP3? First update and validate the project at V7.1 SP4, the baseline specified by the with-new-functions manual.

Must the AS remain in RUN? No. Siemens requires the CPU to be switched to STOP for the with-new-functions update.

Are the listed library versions mandatory for every system? No. The discussion's list is project-specific; validate each library against its own applicable release documentation and the project's block usage.

Technical References

Related Articles

Search IndustrialAutomation.net for PCS 7 migration articles

Related Tags

PCS 7 V9.1 SP1 · PCS 7 project upgrade · CFC and SFC migration

20 respuestas