IMDTouchKnowledge BaseShop main store

Troubleshooting

Animating WinCC symbol library objects in TIA Portal

HMI and touchscreens Published 7 min read

Short answer

Symbol library objects in WinCC Comfort and Advanced are dynamic; a solid fill style hides the color your Appearance animation writes. Set Fill style to Shaded, animate the foreground color, and verify in the simulator before duplicating. For bitmaps in a graphic view there is no color to animate — drive a graphic list with the state tag, or redraw the symbol from native objects.

On this page
  1. Why the color never changes
  2. Check which object class you placed
  3. Fix a symbol library object: Fill style to Shaded
  4. Bitmaps: graphic list, not color animation
  5. Scale it: faceplates and the popup restriction
  6. Animate state, not flow
  7. The decision for each case
  8. Questions asked

A WinCC symbol library object that ignores its Appearance animation is not broken and not static — the animation is writing a color the object never paints with. Symbol library objects in WinCC Comfort and Advanced are dynamic: the engineering documentation lists appearance dynamization for them, alongside panels, RT Advanced and RT Professional. The renderer draws each symbol with a background color, a foreground color and a fill style, and a solid fill means the animated color has no pixels to land on. Set the object's fill style to Shaded, animate the foreground color, and the state change appears. If what you placed is a bitmap in a graphic view, there is no color to animate — drive a graphic list with the state tag or redraw the symbol from native objects. You do not fix it with overlays. The checks below sort every case, including the faceplate-on-popup restriction that bites once one valve finally animates.

Why the color never changes #

TIA Portal puts three different classes of drawable content on a screen, and each class takes a different fix.

Basic objects — rectangle, circle, line, I/O field — expose every fill and border property to the animation editor. If a basic object refuses to animate, the graphics are not the problem: the tag, the range rows or the connection is, and testing an HMI simulation against a live PLC settles which.

Symbol library objects — the vector valves, pumps, motors and fittings supplied in the WinCC graphics folder, organized by topic — use a two-color rendering model: a background color, a foreground color, and a fill style that decides which of the two the renderer paints. Dynamizing the appearance of these objects is a documented capability, so the object class is not what is blocking you.

Graphics — WMF, EMF or bitmap files in the project graphics pool, shown through a graphic view — carry no color properties at all. The only properties the runtime can change are which image is displayed and whether the view is visible.

What you placed Color the runtime can write Working animation
Basic object (rectangle, circle, line) fill and border color, per state Appearance animation as configured
Symbol library object background and foreground, subject to fill style Fill style to Shaded, then animate the rendered color
Graphic view with a bitmap none graphic list swaps the image; visibility only

Check which object class you placed #

Select the object, open its Properties and read what the Appearance group offers:

  • Background color and Foreground color are listed: symbol library object, take the shaded fix below.
  • No color fields, only the image and visibility: a graphic view holding a bitmap, take the graphic list route.
  • Fill color, border color and a live animation editor: a basic object, and the graphics are already fine.

The complaint that library objects are not dynamic is almost always one of the first two: a bitmap asked to change color, or a symbol animating the color its fill style never renders.

Fix a symbol library object: Fill style to Shaded #

  1. Select the symbol on the screen and open Properties. In the Appearance group, set Fill style to Shaded.
  2. Look at which color now carries the body of the symbol, because that is the one to animate. On most symbols it is the foreground color — exactly the field that starts rendering once both colors are painted.
  3. In the Animations group, under Display, add an Appearance animation.
  4. Assign the state tag, choose bit or value range, and enter one row per state with its color.
  5. Compile and run before duplicating the object across the P&ID. Where the simulator and the panel disagree, believe the panel.

The workaround to retire is an invisible basic object stacked over every elbow: it doubles the object count the panel compiles and draws, breaks alignment the moment anything is nudged, and stacked layers cause the opposite failure too, as in how overlapping graphics hide HMI symbols. Two-color rendering is not Comfort-specific either: a polygon that fills black on another HMI platform gets shaded style fix for a polygon that renders black, the same mechanism under a different name.

Bitmaps: graphic list, not color animation #

A bitmap has no semantic color for the runtime to address, so the runtime swaps whole images instead. Create a graphic list, add one entry per state in the graphics list entries table, and bind the graphic view's image property to the list plus the state tag. An entry can cover a span of values through its Range setting instead of one exact value, which keeps a numeric level tag to a handful of images. For a sequence of images rather than two states, graphic list driving a bottle fill animation shows the entry-by-entry setup.

Two limits decide when this is the right tool. The list content is fixed at engineering time — a Comfort graphic list cannot take a file path computed at runtime, so images the machine generates while running never reach this object. And artwork multiplies: 30 valve types with 3 states each is 30 × 3 = 90 images to draw and to re-draw on every artwork revision, against zero for shaded native symbols. Where the only difference between states is a fill color on ten pipe segments, the graphic list is the wrong answer and the shaded symbol is the right one.

Dynamic SVG keeps element fills addressable after import on the runtimes that support it, which makes it the cleanest bitmap replacement where your panel family has it — the system manual for that family is the authority, not the editor's behavior on the engineering PC.

Scale it: faceplates and the popup restriction #

Once one symbol animates, the cost question is copies. A faceplate is a reusable type with a defined interface: build the animation once, bind each instance to its own tag, and a color revision is one edit plus a recompile instead of an edit per copy.

WinCC Comfort does not support faceplates on popup screens, so the detail dialog opened from a valve cannot be a faceplate instance on that popup. Two patterns hold:

  • Build the dialog as a faceplate on a normal screen and open it through a screen window on the base screen; the click event writes which screen the window displays. The faceplate sits on a normal screen, which Comfort accepts.
  • Compose the popup from native objects driven by one selected-device data block: the click writes a device index, the PLC copies that device's data into the interface block, and one popup serves every valve.

Illustrative example — a header screen carries 30 identical valves, two states each; the counts are assumed screen contents, not a panel limit. Overlay approach: 30 symbols + 30 invisible rectangles = 60 screen objects, and one state-color revision edits 30 objects. Faceplate approach: 1 faceplate type + 30 instances = 31 screen objects, and the same revision edits 1 object. Object count goes 60 → 31; the edit count goes 30 → 1. At 30 instances the faceplate has already paid for itself, and nothing above that number argues for overlays.

Animate state, not flow #

ISA-101.01-2015, the process-industry HMI design standard, is why experienced engineers push back on animated pipes: its approach is a muted, mostly gray base graphic with color reserved to carry status, so every color change reads as information. A pipe drawn as flowing claims fluid is present and moving. The PLC usually knows the valve position — not whether liquid remains upstream, whether a hand valve is shut somewhere, or whether a junction feeds the line from elsewhere. An HMI that shows flow the PLC cannot prove misleads an operator working on that line; treat an unmeasured fill as wrong information, not decoration.

So: animate the valve state, leave the pipe a static line, and add a fill only where a measurement backs it — a flowmeter on the line, or a level tag on the tank, as in how to animate a tank level graphic on an HMI screen. Where the measurement exists, the shaded fix above is all the animation you need.

The decision for each case #

  • Symbol library object, state shown as color: Fill style to Shaded, Appearance animation on the foreground color, one row per state.
  • Bitmap in a graphic view: graphic list with one entry per state, Range spans for numeric tags; no color animation and no runtime file path on Comfort.
  • The same animated symbol in many places: a faceplate with the animation inside; a popup detail dialog on Comfort opens through a screen window on a normal screen, or uses a native-object popup driven by a device-index block.
  • Pipe fill: valve state only, unless a flowmeter tag backs the line.
  • WinCC Unified target: graphic objects there take a dynamic fill color directly, as in how dynamic fill color changes work on graphic objects, so the shaded workaround often disappears entirely.

The professional solution was never overlays. Two colors are already inside the symbol: set the fill style so the renderer paints both, and a library object animates like any basic object on the screen.

Questions asked

Does the Shaded fill style behave the same on RT Advanced and WinCC Unified?

RT Advanced uses the same symbol library objects and the same documented appearance dynamization, so the fill style behaves the same there. WinCC Unified is a separate runtime: its graphic objects take a dynamic fill color directly, so the shaded trick is often unnecessary. Property names and the animation editor differ between the generations, so build the first animated symbol on your actual target panel, not on whichever runtime is closest.

Can a graphic list load images from a folder path at runtime?

No. A graphic list on a Comfort panel is compiled into the project, with its entries fixed at engineering time. Pointing the list at files the machine creates while it runs is not something the object supports, so an application that truly needs runtime-chosen images has to solve the problem outside a panel graphic list.

What does the Range setting do in a graphic list entry?

An entry does not have to map one exact tag value. With Range selected in the entry's properties, a single image covers a span of values — for example a level tag from 0 to 40 percent shows the empty picture and 41 to 70 the half picture. Fewer entries, same visual behavior, and far less artwork to maintain.

Why does the animation work in the simulator but not on the panel?

The simulator runs on the engineering PC with the PC's graphics stack and full feature set; the panel draws with its own runtime. An out-of-date panel image, a property the firmware generation does not take, or a tag that only moves in simulation all look identical from the chair. Recompile, check the tag on the panel itself, and only then trust the screen.

Can the background color be animated instead of the foreground?

Yes. Once the fill style renders both colors, background and foreground both appear in the Appearance animation and either can carry the state. Which one holds the process body differs between symbol variants, so set the fill style first, see which color the shape actually paints with, and animate that field.

Keep reading

  • How-to

    How to Animate a Tank Level Graphic on an HMI Screen

    Fill a vector tank symbol through the symbol component's fill option, bound to the scaled level channel with the empty and full endpoints matched. Normalize any level with f = (L - L_empty)/(L_full - L_empty), where all three values share units. A linear gauge suits only a narrow column, and the size parameter demands channel inversion.

    HMI and touchscreens

  • How-to

    How to migrate a WinCC flexible project to TIA Portal

    One TIA Portal installation replaces both STEP 7 Classic and WinCC flexible, but the two project types move differently: the STEP 7 V5.x project is imported, and the WinCC flexible 2008 project is migrated through an intermediate release because the newest TIA Portal versions no longer offer that migration. Verify the exact S7-300 CPU and panel against the device lists and license STEP 7 and WinCC Comfort separately.

    HMI and touchscreens

  • Comparison

    TIA Portal vs STEP 7 plus WinCC hardware configuration

    Configuring the same PLC and HMI in TIA Portal instead of STEP 7 plus WinCC needs no extra PLC, panel, module or network hardware — the cabinet stays exactly as it is. The difference is where devices, networks and tags are configured: one integrated project instead of two. The one hard limit: S7-1200 and S7-1500 CPUs engineer only in TIA Portal, and CPU firmware sets the minimum release, so a V2.9 CPU needs TIA Portal V17 or higher.

    HMI and touchscreens