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

Set Up a PCS 7 Operator Station Without Mixing WinCC Versions

Set Up a PCS 7 Operator Station Without Mixing WinCC Versions

Set up a PCS 7 operator station as part of the matching PCS 7 engineering environment, then generate and compile its OS data before editing process pictures. First resolve the requested WinCC V7.0 version: a PCS 7 V9.0 tutorial is not proof that a V7.0 installation supports that workflow. The procedure below is the documented V9.0-with-APL starting point, with the unresolved V7.0 applicability kept explicit.

Table of Contents

Version and Project Prerequisites

The request identifies WinCC V7.0 but not the PCS 7 release, service pack, engineering package or project state. It also references a discussion involving PCS 7 V9.0 and WinCC V7.4. These are different version contexts and cannot be silently combined.

The opened reference is Getting Started - Part 1 V9.0 with APL, A5E39543015-AA, chapter 9. Its example presupposes a prepared PCS 7 project, hardware/network configuration and suitable engineering software. Use an engineering copy and determine whether the objective is a new learning project, recovery of an existing OS, or a production deployment.

Documented V9.0 OS Preparation

For the manufacturer's V9.0 learning project:

  1. In SIMATIC Manager's Plant View, open the picture's Edit > Object Properties dialog. Give the picture its intended name.
  2. On Block icons, enable Derive the block icons from the plant hierarchy.
  3. Select the appropriate hierarchy folder and run Options > Plant Hierarchy > Create/Update Block Icons.... Confirm the required picture and hierarchy depth for the project.
  4. Compile the associated OS and examine the compilation log before continuing. The example's hierarchy depth and compilation selections are specific to its layout, not universal defaults.
  5. In Component View, select the OS under the PC station's WinCC Appl and use Edit > Open Object to open WinCC Explorer.

Chapter 9 then continues with process-picture configuration in Graphics Designer. See the V9.0 example and prerequisites.

Verification

Check that the generated icons appear in the intended process picture, that the OS compilation log reports the intended successful compilation, and that WinCC Explorer opens the correct OS project.

For an actual installation, verify each icon's measurement-point identity and communication in the approved runtime environment. These checks are separate from confirming that the editor opens. Do not describe a completed compilation as a downloaded or commissioned OS.

Limitations and Operational Precautions

The exact PCS 7/WinCC V7.0 combination remains unidentified, and the opened V9.0 tutorial does not establish it. No V7.0 installation, upgrade or migration procedure is asserted.

Do not delete pictures from a production project merely because the learning example removes unused pictures. Retain existing configurations, licenses and recovery media before planning software changes. Follow the version-specific deployment process and protect operating availability.

The outlined steps establish a documented preparation sequence for the example. A full production OS also needs its own supported hardware, communications, permissions and acceptance criteria.

Engineer FAQ

Can the V9.0 tutorial be followed unchanged on WinCC V7.0? Its applicability is not established.

Does OS compilation equal OS downloading? No. Treat compilation, deployment and runtime validation separately.

Where does process-picture editing begin? Open the intended OS project in WinCC Explorer after its engineering preparation.

Technical References

Related Articles

Related Tags

20 respuestas