Troubleshooting
Animating Four Images With a Graphic List in WinCC RT
Short answer
SimulateTag is not missing from WinCC RT. The function is documented for Basic Panels, Panels, Comfort Panels and RT Advanced targets and simulates Integer tags from a function list, while RT Professional uses the WinCC Runtime Professional Tag Simulator. Verify the configured runtime target, then animate four images with a graphic list on a dedicated Integer tag at a short cycle.
On this page
SimulateTag is not missing from WinCC RT. The function is documented for Basic Panels, Panels, Comfort Panels and RT Advanced targets and is used in the function list of an event, while RT Professional gets the separate WinCC Runtime Professional Tag Simulator tool. So the reason you cannot find it is almost certainly the configured runtime target of the project, or the Professional tool being the documented route there. The animation itself is a dedicated Integer tag, four graphic-list entries and a short cycle: the list selects the image, the changing tag supplies the motion.
Which runtime the project is really configured for #
An event's function list offers only the functions valid for the configured HMI device. When SimulateTag does not appear, verify the target before touching the graphic list.
- WinCC RT Advanced. SimulateTag is documented in the V20 online help for Basic Panels, Panels, Comfort Panels and RT Advanced, used in the function list, with the documented purpose of demonstrating project functionality. Only Integer tags can be simulated.
- WinCC RT Professional. Use the WinCC Runtime Professional Tag Simulator, which installs with WinCC in the Siemens program group on Windows. Insert the required tags, select the function for the simulation, set the other function parameters in the Tag properties area, and change the update there.
- Still a panel target. A project authored for an HMI panel must be retargeted to the PC runtime and recompiled before its function lists reflect the PC function set; the compile-and-run sequence is the one in running a TIA Portal V14 HMI on WinCC Runtime Advanced.
Read the HMI device entry in the project tree and let that entry decide. A folder name or a quotation that says WinCC RT is not a configuration.
The frame tag and the four graphic-list entries #
Give the animation its own internal tag of data type Integer: internal keeps the effect out of the process data, and Integer is the data type the simulation accepts. The value-to-image mapping is the technique already covered in switching HMI images with an integer variable value.
| Selector value | Graphic-list entry | Displayed image |
|---|---|---|
| 0 | First entry | First animation pose |
| 1 | Second entry | Second pose |
| 2 | Third entry | Third pose |
| 3 | Fourth entry | Fourth pose, then back to 0 |
Values 0 through 3 are a mapping you define, not existing project addresses. Bind the image object to the graphic list and the list to the frame tag, then write 0, 1, 2 and 3 by hand at runtime: each value must show its own image before any timing is added. A tag that changes while the image stays fixed is a binding fault, and it is cheaper to fix it here than during commissioning.
Animating four frames at the chosen interval in WinCC RT Advanced #
Inputs, each with its source:
- Four images, from your project.
- Frame interval of 200 ms, the cadence you asked for.
- Frame tag: internal, data type Integer, per the documented restriction of the function.
- Graphic list with four entries at values 0 to 3, one image each.
- Call site: the function list of a screen event, which is where the function is used.
Rule in words: each cycle produces one image change; a complete pass over the animation equals the number of list entries times the cycle time; the image changes per second equal 1000 ms divided by the cycle time.
Arithmetic:
- 4 entries × the frame interval = 800 ms per complete pass.
- 1000 ms ÷ the frame interval = 5 image changes per second.
Result: the selector walks 0 → 1 → 2 → 3 → 0 every 800 ms, at five image changes per second.
Decision: accept when the manual write test passed and one runtime pass shows all four images inside 800 ms. If the tag advances but images skip, the update path is dropping intermediate values, so correct the binding first and only then lengthen the cycle. Treat this interval as a PC-runtime figure: Siemens support entry 109747174 documents that SimulateTag with a short cycle time can overload a Basic Panel, so on panel targets lengthen the interval if the device slows. And because the documented purpose of the function is demonstrating a project, use it to prove the effect, then hand the frame tag to a cyclic script or the controller on the machine as delivered.
When the selector moves but the image does not #
| Observation | Likely cause | Next check |
|---|---|---|
| Selector stays constant | The sequence never starts | The event that calls the function, and its enable condition |
| Selector changes, image fixed | Wrong list or wrong tag bound | Repeat the manual write test |
| Selector advances, frames skip | Display drops intermediate values | Compare tag changes with visible changes, then lengthen the cycle |
| Cadence changes after navigation | Execution tied to screen lifetime | Start and stop conditions on screen load and unload |
A graphic list supplies image selection, never timing: a fixed image with a moving tag is a binding fault, and a skipping image is an update-path fault. The same selection-versus-timing split governs animating WinCC symbol library objects in TIA Portal.
One owner for the frame tag #
Exactly one execution source may write the selector. Two conflicts account for most irregular animation:
- The simulation still running while a cyclic script also increments the tag.
- A controller-owned tag being overwritten by the simulation, or the reverse.
Read the tag's cross-references and the project's event actions, keep the intended owner, and remove the competing writes. Define the start of the sequence, entering the animation screen, and its stop, so that navigating away cannot leave a second execution path running.
What the animation may tell the operator #
A decorative animation is not evidence that the equipment is moving: if the four images communicate a real machine state, the selection must be derived from that state, including what is displayed when controller communication is lost.
Questions asked
Is SimulateTag available in WinCC RT Professional as well as RT Advanced?
Both runtimes support tag simulation, but through different entry points. The function-list call is documented for Basic Panels, Panels, Comfort Panels and RT Advanced, while RT Professional uses the WinCC Runtime Professional Tag Simulator from the Siemens program group. If one project must run unchanged on both targets, drive the frame tag from a cyclic script or the controller instead, which behaves the same on each.
Why must the frame tag be an Integer tag?
Because the documented restriction is explicit: only tags of the data type Integer can be used for simulation. Design the frame selector as an Integer and map the graphic-list entries onto consecutive whole numbers such as 0 to 3. No documented way exists to simulate a Real or Bool tag with this function, so fix the data type before building the list.
What cycle time is safe for this animation?
On a PC runtime, the interval used here gives five image changes per second and an 800 ms pass over four frames, and no documented minimum cycle applies to PC targets. The documented limit is on panels: Siemens support entry 109747174 warns that a short cycle time can overload a Basic Panel. If a Basic Panel slows or drops frames, lengthen the cycle until it keeps up.
Should the frame tag be an internal tag or a controller tag?
Internal when the sequence is purely visual, controller-owned when the displayed phase must follow the machine. The RT Professional simulator does not simulate external tags, so a controller-owned selector has to be moved by the controller or a PLC simulation, which is one more reason to keep decorative animation on an internal tag. Either way, exactly one writer sets the tag.
How do I stop the animation when the operator leaves the screen?
Attach the stop to the same lifetime that started the sequence: begin on screen load, end on screen unload, and disable the simulation call or script there too. An unstopped sequence keeps writing the tag in the background, and the next screen that binds the same tag shows an animation it never started.