Troubleshooting Missing Runtime Data in SIMATIC PCS 7 Advanced Process Graphics (APG)

Troubleshooting Missing Runtime Data in SIMATIC PCS 7 Advanced Process Graphics (APG)

In SIMATIC PCS 7 Advanced Process Graphics (APG), an APG bargraph or spider diagram displaying no live runtime data—despite connecting via the Dynamic Wizard—is caused by incomplete AS-OS compilation, uninitialized OpScale normalization bounds, or missing APG global C-script actions. APG relies on HMI connector blocks in CFC (such as HMI_MonAnL or HMI_PIDConL) linked via pointer PntIn to technological blocks. If OpScale.High and OpScale.Low on the technological block are left at default 0.0 values, the bargraph cannot calculate percentage deflection. Furthermore, an OS compilation must be executed to export the APG structure tags, and the APG OS setup must be run to install required WinCC C-scripts.

Table of Contents

Architecture of Advanced Process Graphics (APG) in PCS 7

SIMATIC PCS 7 Advanced Process Graphics (APG) is an optional software package designed to implement modern High-Performance HMI visualization conforming to ISA-101 and Abnormal Situation Management (ASM) guidelines. Rather than cluttering operator screens with dense numerical displays, APG provides intuitive visual summaries: Level 1 overview displays, polar spider charts, and normalized bargraphs.

APG utilizes a two-tier connector architecture:

  1. AS Automation Layer (CFC): The technological block (MonAnL, PIDConL) is paired with an APG connector block (HMI_MonAnL, HMI_PIDConL). The connector block evaluates limit violations, process trends, and normal working ranges.
  2. OS Visualization Layer (WinCC): The APG bargraph object is linked to the connector block using the APG Dynamic Wizard. Internal WinCC C-scripts (APG_*.fct) cyclically normalize process values into graphical bar heights.

Diagnostic Root Causes for Empty APG Graphic Objects

When an APG bargraph renders in WinCC Runtime as a blank, unpopulated shape with zero dynamic bar movement, investigation reveals four primary failure modes:

Failure ModeAffected Parameter / ComponentUnderlying Technical FaultCorrective Engineering ActionZero Operating Scale SpanOpScale.High / OpScale.LowRange span equals zero ($0.0 - 0.0$); division-by-zero blocks scalingSet valid engineering limits (e.g. 0.0 to 100.0)Missing Structure TagsWinCC Tag ManagementOS compile not executed after inserting HMI_* connector blocksRun Compile OS -> Changes OnlyUnassigned Pointer (PntIn)HMI_MonAnL.PntInConnector block pointer disconnected from technological blockInterconnect PntIn to MonAnL structureMissing APG Script ActionsWinCC Global ScriptsAPG setup not installed on OS Server; APG_BarGraph.fct missingRun official APG OS setup installer

Because APG bargraphs normalize values using percentage deflection, valid high and low operating scale boundaries are mandatory.

Step-by-Step Configuration and Validation Workflow

To restore dynamic data visualization on APG bargraphs and spider charts, execute the following technical procedure:

  1. Configure Operating Scale on Technological Block: Open the CFC chart containing the monitored block (MonAnL or PIDConL). Verify that parameters PV_OpScale.High (e.g. 100.0) and PV_OpScale.Low (e.g. 0.0) are parameterized with a valid physical span.

  2. Verify Connector Pointer Interconnection: Ensure the APG connector block (HMI_MonAnL) has its input pin PntIn interconnected to the technological block. Verify that the BlockType parameter matches the target block type (e.g. 1 for MonAnL).

  3. Execute Full AS-OS Compilation: Save CFC. In SIMATIC Manager, right-click the OS Server object and select Compile. Execute an OS compilation (Compile OS -> Changes Only). Verify in WinCC Tag Management that the @APG tags and structure variables are generated.

  4. Run APG Dynamic Wizard in WinCC Graphics Designer:
    - Open the target process picture (.pdl) in Graphics Designer.
    - Highlight the APG bargraph object.
    - In the Dynamic Wizard pane, double-click 'Connect APG Block to Process Tag'.
    - Browse and select the compiled HMI_MonAnL tag name.
    - Complete the wizard and save the picture.

  5. Verify WinCC Script Triggers: In Graphics Designer, inspect the dynamic trigger of the bargraph. Confirm that the cyclic trigger is set to a reasonable update rate (e.g., 2 seconds or Upon Change).

Verification

Confirm that the APG graphic object updates dynamically through these operational tests:

  1. Graphics Designer Tag Link Inspection: In Graphics Designer, check the object properties of the bargraph. Confirm that the TagPrefix or tag connection points to a valid WinCC tag without red broken-link indicators.
  2. CFC Test Mode Value Injection: Switch CFC to Test Mode. Change the simulated process value PV_In on MonAnL to 50% of scale.
  3. WinCC Runtime Dynamic Display: In WinCC OS Runtime, observe the APG bargraph. Confirm that the vertical bar deflects to exactly 50% height and that normal operating range markers display in crisp green/grey contrast.

Limitations and Operational Precautions

When implementing Advanced Process Graphics across a facility, observe these operational guardrails:

  • Version Compatibility: APG versions are tightly coupled with PCS 7 releases (e.g., APG V8.2 for PCS 7 V8.2, APG V9.0 for PCS 7 V9.0). Never install mismatched APG versions.
  • Licensing Requirements: APG requires dedicated runtime licenses (SIMATIC PCS 7 Advanced Process Graphics) installed on both the Engineering Station and OS Servers in ALM.
  • Color Standards Compliance (ISA-101): APG uses muted grey/blue tones for normal operation and reserves bright colors (yellow, red) strictly for abnormal alarm conditions. Avoid overriding APG standard palettes with custom vibrant colors.

Engineer FAQ

Why does the APG bargraph show a grey dashed outline in runtime?

A dashed grey outline indicates that the WinCC tag connection is invalid, tag logging is offline, or the connected tag quality is Bad (16#00).

Can I connect an APG bargraph directly to an analog input driver (Pcs7AnIn)?

No. APG objects must connect to technological blocks (MonAnL, PIDConL) via their dedicated HMI connector blocks (HMI_MonAnL).

Does APG consume additional Process Objects (PO)?

No. The HMI connector blocks in CFC do not contain Alarm_8P message instances and do not consume additional AS or OS Process Objects.

Technical References

Related Articles

Related Tags

  • Advanced Process Graphics
  • APG
  • HMI_MonAnL
  • ISA-101
  • High-Performance HMI
  • Bargraph
6 respuestas