How-to
How to Add an XY Plot to a WinCC Application
Short answer
No. Classic WinCC's base graphics objects stop at the bar graph and the time trend, so a value-against-value plot comes from a third-party ActiveX/OCX control, verified against your WinCC edition and licensed for engineering and runtime separately. Map the 20-element array first: 20 Y values, 10 X/Y pairs and 20 points need different point and series capacities.
On this page
Classic WinCC's base graphics objects stop at the bar graph and the time trend, so an XY plot, one process value against another, is not in the base package: you add a third-party ActiveX (OCX) control, verify it against your exact WinCC edition and Windows platform, and license it for the engineering workstation and the runtime PC separately. Before any of that, decide what your 20-element array means. Twenty Y values on a position axis, 10 X/Y pairs and 20 points from separate X and Y arrays each need a different point and series count, and that count, not the tag count, sets what the control must support.
What the base package plots #
The two objects you found are what classic WinCC gives you for charting: a bar graph, bound to one variable, and a trend that plots a tag against time. An XY plot is a different object: every point carries an explicit numeric X and a numeric Y, and time is on neither axis. Classic WinCC has no such object in its standard toolbox, so the answer to the base-package-or-extra question is the extra: an add-on control, with one scripted stopgap in between.
Two routes cost nothing to check first. WinCC OA, the other product line, has its own XY trend element, so if the project is OA rather than classic WinCC, start there. And for a small, fixed set of points you can draw a polyline object and write tag values to its vertex positions from script, so each vertex becomes one (X, Y) point. That holds up for a dozen points; it gives you no axis scaling, cursors or legend, and at twenty vertices it is a maintenance burden. It is the stopgap, not the production answer.
Map the array before you pick a control #
An array of 20 variables does not yet say what a point is, and the capacity the control needs follows from that mapping, not from the number of tags.
| What the 20 values are | X of each point | Y of each point | What the control needs |
|---|---|---|---|
| One profile, position-indexed | Array index or position | The stored value | 1 series, 20 points |
| Coordinate pairs | First entry of a pair | Second entry of a pair | 1 series, 10 points |
| Separate X and Y arrays | X entry i | Y entry i | 1 series, 20 points from 40 stored values |
| 20 independent relationships | Defined per series | Defined per series | 20 series, 1 point each |
Count points and series separately from this table before you talk to any vendor. Series count is usually the tighter limit: a control that happily draws 20 points in one series may cap series well below 20, so a mapping that needs 20 one-point series can rule out a control that meets your total point count with room to spare. Ask for both numbers, points per series and series count, and get them in writing.
Worked example: a 20-point dryer profile #
Take illustrative numbers for the posted case. The controller holds an array of 20 REAL values, one dryer-zone temperature per 0.5 m of a 10 m drum, refreshed as a complete set every 10 s. The mapping: X = (i − 1) × 0.5 m for i = 1 to 20, Y = the array value in °C over a process range of 40 °C to 260 °C.
The arithmetic: X runs from (1 − 1) × 0.5 m = 0.0 m to (20 − 1) × 0.5 m = 9.5 m, and the display needs 20 values ÷ 1 value per point = 20 points in one series. The same 20 storage slots under other mappings need different capacity: as coordinate pairs, 20 ÷ 2 = 10 points; as 20 points from separate X and Y arrays, 20 + 20 = 40 stored values.
Fix the axes from the process range: X 0 to 10 m, Y 0 to 300 °C. Both ends of the profile sit inside the limits, 0.0 m and 9.5 m on X, 40 °C and 260 °C on Y, while a fixed X limit of 9.0 m would silently hide point 20. The requirement statement for the control is now concrete: numeric-X XY mode, a script or array interface, at least 20 points in one series, one series, full-set updates every 10 s. A control that cannot document that is out; one that can is in.
Pick and verify the XY control #
Named leads from the field: TrendViewer from ICS, an OCX identified with XY-diagram capability on Siemens' WinCC add-on list, and ICONICS TrendWorx+, a trending package that also does circular charts; independent XY-chart ActiveX components exist as well. Treat the names as leads, not as compatibility results: current availability, supported WinCC versions, platform support and licensing come from the manufacturer or its distributors, and you verify each item below before anything is bought.
- Record the environment exactly: WinCC edition and version, runtime version, Windows version and 32/64-bit architecture, for the engineering workstation and for the runtime PC.
- From the control's documentation, confirm it is an ActiveX control hosted by classic WinCC, with a numeric-X and numeric-Y mode, not only time on the horizontal axis.
- Confirm the data interface against your mapping, whether arrays, per-point writes or a script API, together with both capacity numbers.
- Confirm deployment on both computers: installer, dependencies and the documented registration step. A copied component file is not an installation.
- Confirm the license terms for engineering use and for runtime use, per seat.
The gap is not Siemens-specific: plotting X/Y cam data in FactoryTalk View SE comes down to three methods on the Rockwell side, with the same control-versus-script decision.
License engineering and runtime separately #
The engineering workstation and the runtime PC are two deployment targets, and a control can open perfectly in the graphics editor yet fail on the runtime with a missing-component or license message. Install through the manufacturer's documented procedure on both machines. An evaluation version, where one is offered, is for proving the data interface on the bench; its terms do not carry production runtime rights. Settle the WinCC side in the same pass: the runtime's own license class has to cover what the new screen does, which is the question taken up in WinCC RT and RC license differences.
Bind the array and keep coordinates coherent #
Binding is where XY plots go wrong, because a tag list is not a dataset.
- Write the point map first: for every coordinate, the source array element or tag, its quantity and its unit. In the example, X in metres and Y in °C.
- Read the control's actual data interface and map the coordinates onto it. Do not feed it a time-trend tag list and hope.
- Check numeric handling: REAL versus integer representation, scaling into engineering units, and invalid-value behavior. A failed sensor must show as invalid, never as a plotted zero.
- Push the complete dataset in one script pass and trigger one redraw. With X from one acquisition and Y from another, points can pair coordinates that never existed together in the process; for a position-indexed array, keep each position married to its value end to end.
One safety note, once: the plot is visualization. Profile limits and envelopes are drawn on the screen but enforced in the PLC, never the other way round.
Prove it on the bench #
- Build a test screen with internal tags and plot known coordinates at the corners and the middle: (0.0 m, 45 °C), (4.5 m, 150 °C) and (9.5 m, 260 °C). Each must land at its numeric position with no clipping.
- Break the data source. The display holds last values or flags invalid; plotted zeros are a fail.
- Restart the runtime PC and reopen the screen. The control must load and rebind with no component or license message.
- Connect the real array and count what appears: 20 points, one series.
- Transfer the project. The runtime PC sees none of this until the edited application is downloaded, which is why an HMI edit needs a new runtime download.
The decision by mapping #
Decide, then buy:
- One profile, 20 position-indexed values: one series of 20 points, X from index or position. A documented 20-points-per-series XY control with a script interface, licensed for workstation and runtime. This is the posted case, and it is the straightforward one.
- 20 values as coordinate pairs: 10 points, same control class, half the capacity requirement.
- Separate X and Y arrays: 20 points from 40 stored values; the control must take matched arrays or per-point writes.
- 20 separate relationships: 20 one-point series, so the series cap decides. If point order carries no meaning, use markers without connecting lines.
For the posted case the production answer is the add-on XY control; the polyline is what runs on the bench while the paperwork clears.
Questions asked
Is an XY plot included in the base WinCC graphics objects?
No. The base charting objects are the bar graph, bound to one variable, and the time trend, which plots a tag against time. A value-against-value display comes from a third-party ActiveX control, or from a scripted polyline for small fixed datasets. Budget the control's engineering and runtime licenses as part of the project.
Can the standard time trend display my 20-element array?
Only as 20 curves against time, which answers when each value changed, not how values relate. If the array is one profile, map index or position to X and the requirement collapses to a single 20-point series, which is exactly the job of an XY control and far easier to read.
Does the polyline workaround replace an add-on control?
For a small, fixed point count it works: draw a polyline object and write each vertex position from tags in script, so every vertex becomes one X/Y point. Past a few dozen vertices it gets hard to maintain, and you lose axis scaling, cursors and a legend. Use it as a stopgap, not as the production screen.
Do the engineering station and the runtime PC need separate licenses?
Plan for both. They are separate deployment targets, and a control that opens in the editor can still refuse to run on an unlicensed runtime. Install through the vendor's documented procedure on each machine, and treat an evaluation version as bench testing only; its terms do not grant production runtime rights.
Will the same ActiveX control work in WinCC Flexible or WinCC Unified?
Do not assume it. The ActiveX route is a capability of classic WinCC on a PC runtime. Panel-based WinCC Flexible targets and the WinCC Unified object model are not ActiveX hosts, so each needs its own documented XY option checked before anything is bought.