Restore Missing Industry Library Faceplates in an Existing PCS 7 OS Project

Restore Missing Industry Library Faceplates in an Existing PCS 7 OS Project

Update the affected existing OS project's Industry Library faceplates using OS project editor and its base-data tab. Siemens documents this operation for both Industry Library V8.0 SP1 and V9.1. Installing the library and seeing its blocks in CFC does not prove that an older OS project has received the graphics. Back up customized pictures before processing, then verify the required faceplates and preserve project-specific graphics.

Table of Contents

Why Blocks Can Be Available While Faceplates Are Missing

Industry Library setup supplies AS blocks and OS visualization components. Siemens separately requires updating faceplates within the project using OS project editor. Thus, finding a block in CFC does not establish that an existing OS contains its visualization files. A reported existing-project case was resolved by running that editor; a newly created project already had the faceplates.

This explanation addresses missing project graphics after installation. It does not identify every possible cause of a faceplate that fails at runtime.

Update the Existing OS Project

  1. Back up the OS project, including its graphics and any customized system pictures, before processing.
  2. Identify the installed PCS 7 and Industry Library versions. Use their applicable readme rather than upgrading libraries to solve a graphics-only symptom.
  3. Open the affected existing OS project and its OS project editor.
  4. Select the base-data tab used for the library-faceplate update. The V9.1 readme calls it "Basis data"; the V8.0 SP1 readme uses "Basic Data".
  5. Review the processing selection against the customized pictures you need to retain. In the reported case, customized pictures such as @Screen required protection from replacement or restoration afterward. Do not assume every project uses identical selection defaults.
  6. Process the base-data update, then inspect the affected project's graphics and check the required Industry Library faceplates.

The manufacturer-documented operation is the project-editor faceplate update. Backup and comparison of customized graphics are practical safeguards. V9.1 readme, section 6.1; V8.0 SP1 readme, section 3.

Verification

Verify the affected existing project rather than relying on a new-project comparison:

  1. Confirm that the required faceplate graphics are now present in that project's graphics collection.
  2. Open a representative Industry Library faceplate in an approved test environment and verify that it corresponds to the intended block instance.
  3. Inspect relevant status and display values; an editor run completing does not prove correct runtime association.
  4. Compare customized system pictures with the backup, especially any changed @Screen picture.

These checks are proposed verification activities. The reported resolution supports the project update, but no laboratory test is claimed.

Limitations and Operational Precautions

The reported installation versions are unspecified. The faceplate-update operation is independently documented for Industry Library V8.0 SP1 and V9.1; exact labels and available processing selections must be confirmed in the installed edition.

Do not confuse an OS faceplate update with AS block-type replacement or a controller download. If the actual library upgrade also changes AS blocks, assess that work under its own release instructions. Preserve customized graphics and keep a restorable OS backup until verification is complete.

Engineer FAQ

Is reinstalling the entire library the first necessary action? The documented project faceplate update addresses this symptom without assuming setup failed.

Does a new project containing the files prove the old project is updated? No; inspect and update the existing OS.

Does this require an AS download? The graphics-update operation does not itself establish a need for controller changes.

Technical References

Related Articles

Related Tags

20 respuestas