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

Customizing APL MotSpdCL Faceplates and Block Icons with Additional Setpoint Fields in SIMATIC PCS 7

Customizing APL MotSpdCL Faceplates and Block Icons with Additional Setpoint Fields in SIMATIC PCS 7

To add two custom setpoint fields (such as High Speed and Low Speed setpoints) to an Advanced Process Library (APL) MotSpdCL block icon and faceplate for specific motors without altering global library files, use either the multi-instance chart extension method or create a customized block icon and faceplate variant. In the multi-instance approach, place auxiliary monitoring blocks (such as MonAnL) in the same CFC chart using a shared chart prefix (e.g., Motor_HiSpd), allowing the standard faceplate to bind the parameters dynamically. Alternatively, create custom copies of @PG_MotSpdCL_Standard.pdl and assign a unique block icon type index (e.g., @MotSpdCL/10).

Table of Contents

Architectural Strategies for APL Faceplate Customization

The SIMATIC PCS 7 Advanced Process Library (APL) uses a strictly standardized, script-driven visualization framework. In standard operation, the MotSpdCL (Speed Controlled Motor) block provides a single process variable and setpoint interface (SP_Int, SP_Ext).

When plant requirements demand displaying and adjusting two distinct speed setpoints (e.g., High Speed Setpoint and Low Speed Setpoint) directly within the motor faceplate for specific equipment, modifying the global @PG_MotSpdCL_Standard.pdl directly in the project directory is dangerous because it alters every MotSpdCL faceplate across the entire plant.

Siemens provides two compliant engineering approaches within the APL framework:
1. Multi-Instance Faceplate Integration: Retaining standard faceplates while augmenting the faceplate with child blocks placed in the same CFC chart using tag prefix inheritance.
2. Custom Faceplate Variant and Block Icon Type: Creating a uniquely named faceplate set (@PG_MotSpdCL_SP.pdl) and associating it with a dedicated block icon index (e.g., @MotSpdCL/10).

Strategy 1 - Multi-Instance Faceplate Architecture (APL Style Guide)

Documented in the SIMATIC PCS 7 APL Style Guide, the multi-instance architecture allows a primary technological block (such as MotSpdCL) to aggregate auxiliary variables from secondary blocks within the same CFC chart without modifying the master APL library code:

How Multi-Instance Prefixing Works

  • In the target CFC chart, name the main motor block with a clear root prefix, for example M101.
  • In the same CFC chart, insert two analog setpoint/monitoring blocks, such as OpAnL or MonAnL, and name them with matching prefixes:
  • M101_HiSpd
  • M101_LoSpd
  • When an operator clicks the motor block icon, the standard APL faceplate opens. WinCC automatically populates the @Faceplate.TagPrefix property with the CFC chart hierarchy path and block root (Plant/Area/M101).
  • Inside the customized faceplate view, additional I/O fields can bind to _HiSpd.SP_Int and _LoSpd.SP_Int. Because the tag prefix supplies Plant/Area/M101, the resolved WinCC tag names become Plant/Area/M101_HiSpd.SP_Int and Plant/Area/M101_LoSpd.SP_Int dynamically.

Strategy 2 - Creating a Dedicated Block Icon and Faceplate Variant

When the user interface requires a unique layout, custom buttons, or specialized setpoint authorization that must only apply to specific motors, engineering a distinct block icon variant is the industry best practice:

Variant Naming and Routing Conventions

  • Block Icon Type Number: In @Template_APL.pdl, copy the standard MotSpdCL block icon and assign a new type string in the object properties:
    Type: @MotSpdCL/10
  • Custom Server Name Binding: In the block icon, alter the internal server call property server_name from PCS7 MotSpdCL Control to PCS7 MotSpdCL_SP Control. This informs the WinCC APL script engine (APL_OpenFaceplate) to load a specialized top-level picture container.
  • Specialized Faceplate Set: Copy the standard faceplate family and rename them:
  • Base Faceplate: @PG_MotSpdCL_SP.pdl
  • Standard View: @PG_MotSpdCL_SP_Standard.pdl
  • View Toolbar: @PG_MotSpdCL_SP_ViewToolbar.pdl
  • Assigning to Target Block: In CFC, select the specific MotSpdCL block, open its block properties, and set the Block Icon Number attribute to 10. During OS Compile, WinCC automatically instantiates the custom @MotSpdCL/10 icon for this motor only.

Comparison Table - Customization Strategies

The following table compares the two methods for extending APL faceplates with additional setpoint fields.

Parameter / MetricMulti-Instance ExtensionCustom Faceplate Variant (@MotSpdCL/10)CFC Chart StructureRequires auxiliary blocks (MonAnL / OpAnL)Can use existing block pins or auxiliary blocksAS Memory ImpactAdditional instance DBs for auxiliary blocksMinimal (no extra blocks if mapping existing pins)Faceplate Global ImpactCan affect other blocks if global PDL is modifiedIsolated exclusively to designated icon type (/10)OS Compile BehaviorAutomatically compiles standard tagsGenerates customized icon based on block attributeAPL Library Upgrade SafetyFully upgrade-safe (no system PDL modified)Requires re-verifying custom PDLs upon APL upgradeImplementation ComplexityLow to moderate (chart naming rules)Moderate to high (PDL script adjustments)

Step-by-Step Implementation Workflow

To implement a dedicated @MotSpdCL/10 faceplate variant with High and Low Speed setpoint controls, follow this procedure:

  1. Copy and Rename WinCC Faceplate Files:
    * In WinCC Explorer on the OS Server or ES, open the GraCS directory.
    * Make copies of:

    • @PG_MotSpdCL.pdl -> @PG_MotSpdCL_SP.pdl
    • @PG_MotSpdCL_Standard.pdl -> @PG_MotSpdCL_SP_Standard.pdl
    • @PG_MotSpdCL_ViewToolbar.pdl -> @PG_MotSpdCL_SP_ViewToolbar.pdl

  2. Configure Top-Level Faceplate Routing:
    * Open @PG_MotSpdCL_SP.pdl in Graphics Designer.
    * Select the @Faceplate root object, locate the property Firstview, and set its string value to @PG_MotSpdCL_SP_Standard.pdl.
    * Select the ToolbarWindow object and set PictureName to @PG_MotSpdCL_SP_ViewToolbar.pdl.
    * Save and close the file.

  3. Embed Custom Setpoint Controls in Standard View:
    * Open @PG_MotSpdCL_SP_Standard.pdl.
    * Duplicate the existing Setpoint APL control object (@APL_AnalogOutput).
    * Bind the first new control to the High Speed setpoint tag (or auxiliary block pin) and the second to the Low Speed setpoint tag.
    * Configure operator authorization levels (e.g., Higher Process Controlling) and unit labels.
    * Save and close the file.

  4. Create Custom Block Icon in Template Picture:
    * Open @Template_APL.pdl (or @PCS7Typicals_APL.pdl).
    * Copy the standard MotSpdCL icon.
    * In Object Properties:

    • Set Type to @MotSpdCL/10.
    • Set ServerName to PCS7 MotSpdCL_SP Control.
    • Save the template picture.

  5. Configure CFC Block and Compile OS:
    * In SIMATIC Manager, open the CFC chart containing the motor.
    * Open properties of the MotSpdCL block and set Block icon = 10.
    * Perform an OS Compile with Create/update block icons selected.
    * WinCC generates the custom icon in the process graphic.

Verification

Verify that the customized motor block icon and faceplate function correctly:

  1. Verify Block Icon Generation:
    * Open the target process graphic in Graphics Designer.
    * Confirm that the generated block icon displays the /10 variant structure and reflects the correct block tag name.
  2. Test Faceplate Invocation in Runtime:
    * Launch WinCC Runtime.
    * Click the newly generated motor block icon.
    * Confirm that @PG_MotSpdCL_SP.pdl opens, loading @PG_MotSpdCL_SP_Standard.pdl as the default view.
  3. Verify Setpoint Operation and Interlocks:
    * In the faceplate, click the High Speed setpoint field. Confirm that the APL analog input dialog opens.
    * Enter a new setpoint value within allowable high/low limits. Confirm that the value writes successfully to the target controller parameter.
    * Click a standard motor block icon elsewhere in the plant to ensure its faceplate remains completely unmodified.

Limitations and Operational Precautions

  • Preserving Original @ Template Pictures: Never modify @Template_APL.pdl directly. Instead, copy custom block icons into @PCS7Typicals_APL.pdl or a custom typicals file (e.g., @PCS7Typicals_Custom.pdl) to prevent PCS 7 updates from overwriting custom icons.
  • Attribute s7_m_c Requirement: If linking custom setpoint variables directly from a modified S7 block, ensure the variables possess the system attribute s7_m_c = 'true'; otherwise, WinCC will not create OS tags during compilation.
  • APL Library Upgrades: Custom faceplate PDLs will not be automatically updated when migrating to newer PCS 7 versions (e.g., V8.1 to V9.0). Document all custom PDLs and re-validate scripts during system upgrades.

Engineer FAQ

Can I add new pins directly to the MotSpdCL block in SCL?

While possible, modifying standard Siemens APL system blocks (FB 1856) is strongly discouraged. It invalidates manufacturer support, complicates future library updates, and may cause compilation mismatches. Using auxiliary blocks or unused block pins is the recommended approach.

What happens during an OS Compile if the custom block icon number is missing?

If the CFC block specifies Block Icon = 10, but @PCS7Typicals_APL.pdl does not contain an icon with Type @MotSpdCL/10, the OS compilation wizard falls back to generating the default Type @MotSpdCL/1 icon.

How do I prevent operators from changing setpoints without authorization?

Assign the standard APL operator authorization attribute (Password Level) on the custom I/O field (e.g., Authorization Level 5 'Process Controlling' or Level 6 'Higher Process Controlling').

Does the multi-instance approach work with Web Navigator?

Yes. Multi-instance faceplates and custom PDLs function seamlessly in WinCC Web Navigator, provided all referenced PDLs and APL ActiveX/OCX controls are published via the Web View Publisher wizard.

Technical References

Related Articles

Related Tags

  • APL
  • MotSpdCL
  • Faceplates
  • Block-Icons
  • WinCC-Graphics
  • CFC
6 respuestas