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

Opening a PCS 7 APL Faceplate from a Custom Screen Object

Opening a PCS 7 APL Faceplate from a Custom Screen Object

A custom PCS 7 APL launcher should start from the matching library's block-icon template, preserving its configured faceplate connection while adapting the presentation. Siemens documents that customization procedure in the 10/2012 APL Style Guide. If opening another faceplate from an existing faceplate is acceptable, APL V7.1 also documents freely assignable jump buttons. Neither procedure establishes a universal script for an independent WinCC pushbutton; that implementation still requires the installed versions and a verified call interface.

Table of Contents

Prerequisites and Version Scope

Record the actual PCS 7, WinCC and APL versions, the target block type and the measurement point. Preserve a recoverable engineering-project copy and an existing working launcher before editing. These are practical preparation measures.

Method 1 follows the APL Style Guide, 10/2012, A5E03860312-02, section 6.3.1, printed pages 72-73. Its example uses V8 templates. Method 2 follows PCS 7 Advanced Process Library V71, 03/2009, A5E02102723-01, section 1.2.1.2, printed page 43. These are separate documented contexts; confirm applicability before combining them in a project.

Method 1 - Adapt an APL Block Icon

Use this documented customization route when a project-specific block icon meets the presentation requirement. It provides a concrete alternative to creating an unrelated button and guessing its script.

  1. Copy a suitable icon from @PCS7TypicalsAPLV8.PDL into a project-specific picture.
  2. Configure type and Servername for the AS block and intended faceplate.
  3. Select User object > Edit from the shortcut menu.
  4. Add or reposition the required internal objects and give them meaningful names.
  5. If resizing, adjust PolylineIcon, the border used by HighLightBlockIcon.
  6. Select all constituent objects and finish edit mode.
  7. Expose newly dynamized objects' attributes through the icon interface; combine shared status-word connections where applicable.
  8. Give new attributes matching display and attribute names, close the configuration dialog, and connect the dynamics, adapting copied dynamics as necessary.

This sequence is based on section 6.3.1 of the Style Guide.

Expected result: an adapted user object with its additional attributes connected. Creating it does not demonstrate successful runtime faceplate opening.

Project-specific adaptation: the visual arrangement, block reference and retained dynamics depend on the chosen template and target instance. Moving a button outside the user object requires separate implementation evidence.

Method 2 - Use an Existing Faceplate Jump Button

Use this documented APL V7.1 option when navigation from another faceplate satisfies the requirement. It is not a process-picture pushbutton.

  1. In CFC, interconnect the launching block's SelFp1 input for the standard-view button, or SelFp2 for the preview button, to an output of the target block.
  2. Open the process picture in WinCC Graphics Designer and open the launching block icon's object properties.
  3. Under Configurations, set UserButtonText1 or UserButtonText2 to the required label.

Siemens documents button visibility following the interconnection and opening the target's standard view. See APL V71, section 1.2.1.2.

Apply engineering changes through the installation's version-specific compilation and deployment procedure; the interconnection steps do not replace that procedure.

Verification

Use an approved validation environment and compare the result with the original working measurement-point icon.

CheckAcceptance evidenceInstance selectionThe opened faceplate identifies the intended measurement pointDisplay bindingIts measurement agrees with the known working displayNew object dynamicsAdded displays follow their intended connected valuesJump-button navigationThe chosen standard or preview button opens the intended targetOperational accessRequired views and permissions behave as specified by the project

These are proposed engineering acceptance checks, not reported laboratory results. Record failures separately: an invisible button, the wrong instance and stale values are different observations.

Limitations and Operational Precautions

The installed versions remain unspecified. The procedures above establish historical customization and faceplate-navigation routes, but do not verify a standalone button call for this installation.

Do not replace library templates with files from a different release solely because the filenames look similar. Retain the working launcher until its replacement passes validation.

Method 2 changes CFC interconnections. Preserve the prior configuration and plan the applicable compile, download and rollback activities before changing an operating system. Completing an edit, compiling, downloading and observing runtime behavior are distinct checks.

Engineer FAQ

Which method most closely addresses a custom object in a process picture? Method 1 adapts a block icon. It does not establish an independent button script.

Can navigation start inside another faceplate? Method 2 documents that option for APL V7.1.

Is an API example provided for a bare button? No applicable standalone-button interface has been established.

Is this configuration ready for deployment? Its installed-version applicability and runtime behavior still need confirmation.

Technical References

Related Articles

Related Tags

20 respuestas