Problem Description
After installing SIMATIC WinCC flexible 2008 (Advanced) with the ProAgent option selected during setup, the Diagnostics folder does not appear in the WinCC flexible project tree, and the diagnostic elements (Motion Monitor, Sequence Monitor, status/condition blocks, and the "ProAgent" toolbox folder) are absent from the WinCC flexible Toolbox window. The user observes that:
- ProAgent is listed as an installed component in the WinCC flexible "Software Versions" dialog.
- S7-PDIAG is correctly installed in the STEP 7 / SIMATIC Manager PG.
- The HMI-PLC tag communication between the S7 PLC and WinCC flexible Runtime is verified as functional.
- Despite all of the above, ProAgent remains invisible inside the project editor and no diagnostic screens are created during HMI compilation.
Affected Software and Components
| Component | Product Designation | Behavior |
|---|---|---|
| Configuration software | SIMATIC WinCC flexible 2008 (Advanced), SP1–SP5 | ProAgent not exposed after install |
| Runtime component | WinCC flexible Runtime | Diagnostic screens not generated |
| PLC diagnostics add-on | S7-PDIAG (STEP 7 V5.x add-on) | Correctly installed on PG |
| HMI panel series | 170-series (TP 170, OP 170, OP 73, OP 77, TP 177 micro, OP 77B) | ProAgent not supported |
| HMI panel series | 270-series and higher (TP 270, OP 270, MP 270, MP 277, TP 277, OP 277, MP 370, MP 377, Mobile Panel 277) | ProAgent supported |
Root Cause Analysis
ProAgent for WinCC flexible is a panel-class-restricted option. The software package is correctly installed and registered when it shows up in Help → Software Versions inside the WinCC flexible configuration, but the configuration project itself will only render ProAgent elements when the target panel resolves to one of the supported families. Panels in the older 170 micro class (OP 73, OP 77, TP 170 mono, TP 170 color, OP 170, OP 77B, TP 177 micro and TP 177A) lack the screen real-estate, color depth, and Runtime diagnostic stack required to host ProAgent. When the project is opened against any of these panels, ProAgent features are automatically deselected at editor startup and will not be visible in the Toolbox even when the ProAgent setup option is enabled.
The Siemens answer in the underlying discussion thread confirms exactly this: "You can use ProAgent only with panels of the 270 series and higher." Once the project is migrated to (or created against) a TP 270, OP 270, MP 270, MP 277, MP 370, MP 377 or equivalent panel, the standard diagnostic screens, the Diagnostics folder in the project tree, and the ProAgent Toolbox category appear automatically. No additional post-install step is required beyond selecting the supported panel and rebuilding the project.
Prerequisites
Before applying the fix, confirm the following on the engineering PG (Windows XP SP3 / Windows 7 / Windows 10 in compatibility mode depending on the era of the installation):
- STEP 7 V5.4 SP3 or higher, including S7-PDIAG as a separately licensed add-on (license key on the USB hardware dongle or in the Automation License Manager).
- WinCC flexible 2008 SPx (same SP level or higher than the Runtime that will be loaded onto the panel).
- WinCC flexible Runtime license that matches the panel model (e.g., 6AV6 617-… for 270-series panels).
- S7 MPI/Profibus or Industrial Ethernet routing between the PG, the S7-300/400 PLC, and the HMI panel.
- STEP 7 project containing a configured SIMATIC S7-300 or S7-400 station with S7-PDIAG unit definitions generated for the relevant program blocks (FB/FC/OB with monitoring configured in HW Config or directly in the LAD/FBD/STL editor).
- An HMI panel from the supported 270-series family (or later) selected in the WinCC flexible project.
Solution: Step-by-Step Procedure
Step 1 — Confirm Panel Compatibility
Open the WinCC flexible project and inspect the panel resolution by selecting Project → Device Selection (or "Target Device"). Acceptable panel classes for ProAgent are:
| Panel Family | Typical Article Numbers | Display | ProAgent? |
|---|---|---|---|
| OP 73 / OP 77 | 6AV3 501-… (mono, 3-inch) | Mono | No |
| TP 170 / OP 170 | 6AV6 620-… (mono/color, 5.7") | Mono or STN Color | No |
| OP 77B / TP 177 | 6AV6 640-…, 6AV6 642-… | STN Color, 4"-5.7" | No |
| TP 270 / OP 270 | 6AV6 627-1... (10.4") | TFT Color | Yes |
| MP 270 | 6AV6 625-1... (10.4") | TFT Color | Yes |
| MP 277 / MP 277 Touch | 6AV6 644-… (7"–10.4") | TFT Color | Yes |
| TP 277 / OP 277 | 6AV6 644-… (6"–10.4") | TFT Color | Yes |
| Mobile Panel 277 | 6AV6 645-… | TFT Color, WLAN | Yes |
| MP 370 / MP 377 | 6AV6 575-…, 6AV6 674-… (12"–15") | TFT Color | Yes |
If the active panel is below the 270 family, ProAgent elements will be hidden. To migrate the project, choose Project → Device Selection → Migrate Project (WinCC flexible 2008 SP2 and later supports cross-panel migration between compatible device families). For example, migrating a TP 177 micro project to a TP 277 or MP 277 will rewrite the screen layout and rescale the objects, retaining alarms, tag connections, and S7-PDIAG diagnostic configurations.
Step 2 — Reinstall ProAgent via Custom Installation
If the panel is already 270-class but ProAgent is still missing, perform a custom reinstall:
- Insert the WinCC flexible 2008 installation DVD or mounted ISO.
- Author the setup with elevated rights: Start → Programs → SIMATIC → WinCC flexible → Setup → Customer Installation.
- On the Select Components dialog, tick the ProAgent option (this component is independent of WinCC flexible Runtime).
- Select Continue. Do not uninstall the base package; allow side-by-side upgrade.
- When setup finishes, restart the engineering PG and reopen the WinCC flexible project.
Verify the install outcome via Help → About WinCC flexible → Software Versions. The entry "WinCC flexible ProAgent" must report a version consistent with the WinCC flexible 2008 service pack (for example, ProAgent V1.2 SPx for WinCC flexible 2008 SP5).
Step 3 — Check the Toolbox Profile
Even with ProAgent installed and a 270-class panel selected, the Toolbox may be filtered to a different view. In the WinCC flexible editing environment:
- Open the View → Toolbox dialog. The default icon palette below the menu bar should list categories including Simple Objects, Enhanced Objects, Graphics, Libraries, and — for 270-class projects — Diagnostics containing ProAgent objects.
- If the Diagnostics subfolder is missing, click the Reset Toolbox button (palette context menu → "Reset to default").
- Confirm that the project tree (right-side navigator) shows a Diagnostics folder beneath the screen node. If it is not present even with the correct panel, the project was previously saved against an unsupported panel — relink the panel as described in Step 1.
Step 4 — Confirm S7-PDIAG Integration
ProAgent on the HMI side depends on S7-PDIAG data being generated at the STEP 7 side. Confirm the integration is end-to-end:
- In SIMATIC Manager, open the S7 program and switch to the LAD/FBD/STL editor.
- Select the FB/FC block that should be diagnosed, right-click → Object Properties → Diagnostics, and confirm that monitoring is enabled.
- From the menu, run Options → S7-PDIAG → Generate Diagnostics Data. This writes a DBA (Diagnostics-Data) source into the S7 program that WinCC flexible picks up at compile time.
- In the WinCC flexible project, open Options → ProAgent → Configure. The wizard must enumerate every S7-PDIAG unit from the STEP 7 program. If the unit list is empty, re-import the STEP 7 integration or rebuild the project graph via Options → STEP 7 Integration → Re-Integrate.
Verification Procedure
- Reopen the WinCC flexible project after confirming Step 1 (panel class) and Step 2 (ProAgent installed). The Diagnostics folder must appear in the project tree.
- Switch the Toolbox view to All. The entries Motion Monitor, Sequence Monitor, and the unit diagnostic swatch should appear with the ProAgent icon.
- Insert a Motion Monitor object onto a screen, configure a tag binding, and run a partial compilation (Project → Compiler → Compile (Incremental)). The compiler must accept the ProAgent object without raising warning 130021 "ProAgent not licensed" or similar.
- Transfer the compiled project to the panel and trigger a fault condition in the PLC. The ProAgent Runtime on the panel must navigate to the diagnostic screen and display the failing block's call environment.
ProAgent Toolbox Element Reference
| Element | Icon Position | Function |
|---|---|---|
| Motion Monitor | Diagnostics → first object | Graphical display of the monitored FB state vector versus time; flags out-of-tolerance transitions. |
| Sequence Monitor | Diagnostics → second object | Step/status grid visualizing the active and historical step sequences of an S7-PDIAG unit. |
| Status/Condition Block | Diagnostics → third object | Live visualization of boolean operand states and interlocks within a monitored FB. |
| Standard Screen (Diagnostics Overview) | Auto-generated | Entry point for the operator to drill from a triggered alarm into the related diagnostic unit. |
| Alarm Unit Object | Diagnostics → fifth object | Filters messages with a diagnostic context and renders ProAgent-specific status colors. |
S7-PDIAG and ProAgent Coupling
The ProAgent engine on the HMI does not generate diagnostic data on its own — it consumes the S7-PDIAG output that the STEP 7 toolchain produces at compile time. The data pipeline is:
- STEP 7 programmer enables monitoring on FB/FC blocks (motion, sequence, or status type).
- S7-PDIAG add-on extends the LAD/FBD/STL editors with diagnostic attributes and writes a unit description into the S7 program container.
- WinCC flexible 2008 imports the STEP 7 program; Options → STEP 7 Integration → Re-Integrate refreshes the DBA source.
- At WinCC flexible compile time, ProAgent objects are instantiated on the target screen and the diagnostic DB is referenced as a tag.
- At Runtime on the 270-class panel, the ProAgent Runtime reads the S7-PDIAG DB, decodes states, and renders the chosen diagnostic view.
Common Fault Scenarios and Remedies
| Observed Behavior | Root Cause | Remedy |
|---|---|---|
| ProAgent installed (visible in Software Versions) but no Diagnostics folder in project tree. | Project panel is 170-class (TP 170, OP 170, OP 73, OP 77, TP 177). | Migrate project to TP 270/OP 270/MP 270/MP 277/MP 370/MP 377. |
| Toolbox does not show the Diagnostics objects even after panel migration. | Toolbox profile was customized and the filter excluded Diagnostics. | Toolbox → Reset to default, then View → All Objects. |
| Diagnostics folder appears empty after STEP 7 integration. | S7-PDIAG Generate Diagnostics Data was never run. | In SIMATIC Manager: Options → S7-PDIAG → Generate Diagnostics Data, then re-integrate. |
| ProAgent Runtime shows "Unit not configured" when an alarm triggers. | S7-PDIAG licensing missing on PG or Runtime panel. | Verify license in Automation License Manager; confirm the panel's Runtime license includes ProAgent. |
| Compiler warning 130021 "ProAgent not licensed". | Engineering license missing or expired. | Repair the WinCC flexible installation and re-import the ProAgent authorization. |
| Project compiles but the panel refuses to load ProAgent screens. | Mismatch between WinCC flexible engineering SP and Runtime SP. | Match SP levels; rebuild and retransfer. |
Migration Considerations
When upgrading a project from a 170-class panel to a 270-class device, the migration tool may rescale screens but does not automatically generate S7-PDIAG units. The diagnostic configuration must be present in the original STEP 7 program before the migration begins. Recommended migration order:
- Refresh the STEP 7 program and confirm S7-PDIAG is installed and licensed.
- Run Generate Diagnostics Data on every monitored FB.
- Backup the WinCC flexible project.
- Run Project → Device Selection → Migrate Project.
- Re-integrate STEP 7 to refresh the DBA source.
- Rebuild and transfer.
FAQ
Which Siemens HMI panels support ProAgent in WinCC flexible 2008?
ProAgent is supported on panels of the 270 series and higher: TP 270, OP 270, MP 270, MP 277 (Touch/Key), TP 277, OP 277, Mobile Panel 277, MP 370, and MP 377. The 170-series panels (TP 170, OP 170, OP 73, OP 77, TP 177 micro, OP 77B) are not supported and will hide the ProAgent elements from the Toolbox even when the option is installed.
Does ProAgent need to be installed as a separate package?
No. ProAgent is a sub-component of WinCC flexible 2008 and is selected on the setup's Select Components dialog. If the option was not ticked during the initial install, run Setup → Customer Installation and enable ProAgent; the running installation can be modified without uninstalling the WinCC flexible base package.
How can I verify that ProAgent has installed successfully on the PG?
Open WinCC flexible and select Help → About → Software Versions. A "WinCC flexible ProAgent" entry matching the WinCC flexible 2008 SP level confirms the binaries are present. Editor visibility, however, additionally requires a 270-class target panel: the Diagnostics folder only appears once the active project resolves to a supported device.
Why does the ProAgent Runtime show no diagnostic data even though communication works?
If S7-PDIAG has not generated the diagnostic data block, the ProAgent Runtime has nothing to render. In SIMATIC Manager, select Options → S7-PDIAG → Generate Diagnostics Data on the S7 program after every program edit, then re-integrate STEP 7 in WinCC flexible (Options → STEP 7 Integration → Re-Integrate) and recompile before transferring to the panel.
Will a TP 277 project migrated from a TP 177 lose its S7-PDIAG alarms?
No. The WinCC flexible migration preserves alarms, area pointers, and S7-PDIAG units. After migration, re-run Generate Diagnostics Data on the STEP 7 side, then re-integrate STEP 7 in WinCC flexible to confirm the DBA source is rebuilt; the migrated panel project will automatically populate the Diagnostics folder with one entry per S7-PDIAG unit.