WinCC SCADA · Lab Manual

WinCC Sequence Overview Screen: Step Text, Blocking Condition and Step History Lab Manual (V8.1)

On a line with several machines, the first question is always which one stopped and why. This lab manual builds a WinCC Explorer V8.1 sequence overview through all six stages – mapped sensors, the sequence in SCL with a ladder watchdog, structured tags, text lists and a step-history archive – and tests it with two machines live.

2,500+ engineers trained 4.9/5 Google rating 21+ years, Chinchwad, Pune Next batch: contact for dates
Quick answer

Write each machine's sequence with a step number and a wait code (SCL CASE), add a step watchdog and a transition pulse (ladder), load the sequence DBs as a WinCC structure type, show step and wait code through text lists on one overview screen, and archive the step tag on change so step durations can be analysed.

  • Step and wait code come from the PLC; WinCC turns them into text.
  • One structure type, one row per machine.
  • Archive transitions to find where time is lost.

Designing the Overview Screen

One row per machine: name, step text, blocking condition, step time against its limit, cycle count. Colour only for abnormal (a timeout), as in HMI screen design best practices. A click on a row opens the detail screen of that machine.

Lab Flow: From Station Sensors to a Line Overview

Every lesson in the Softwell PLC lab manual series follows the same six stages and the same address rule, so the code you write here plugs straight into the HMI lessons.

Lab manual flow: field input to tested HMI screenSix stages: field device and PLC tag, input mapping to DB_IO, PLC logic, HMI tags, graphics linking, and perform and test.1Field + tags%I9.0 .. %I9.5station sensors2Input mappingFC_InputMapping→ DB_IO3LogicFB_SeqSCL + LAD4WinCC tagsstructure typeM1, M25Graphicstext listsoverview, archive6Perform + testSimulatorjam a stationAddress rule for every lesson: %I only in FC_InputMapping, %Q only in FC_OutputMapping, symbolic DB members everywhere else – including the HMI.
Figure 1 – Six-stage lab flow for this lesson.

Stage 1Field Wiring and PLC Tags

PLC tagAddressTypeDevice / comment
M1_PartPresent%I9.0BoolStation 1 part sensor
M1_Clamped%I9.1BoolStation 1 clamp closed
M1_Done%I9.2BoolStation 1 process complete
M2_* (same three)%I9.3 .. %I9.5BoolStation 2

Stage 2Input Mapping into DB_IO

// FC_InputMapping
"DB_IO".M1_PartPresent   := "M1_PartPresent";
"DB_IO".M1_Clamped       := "M1_Clamped";
"DB_IO".M1_Done          := "M1_Done";

Station 2 is mapped the same way.

Stage 3PLC Logic in Ladder and SCL

Step watchdog and transition log trigger for station M1Ladder diagram: Network 1 — Step changed: pulse for the WinCC step-history archive; Network 2 — Step watchdog: machine step longer than its maximum timeNetwork 1 — Step changed: pulse for the WinCC step-history archiveStepChanged"DB_SeqM1" (Step <> StepOld)LogPulse"DB_SeqM1"Network 2 — Step watchdog: machine step longer than its maximum timeMachineStep"DB_SeqM1"T_Step.Q"IDB_SeqM1" TONTimeout"DB_SeqM1"Timeoutseal-inCmd_Reset"DB_SeqM1"
Figure 2 – Transition pulse and step watchdog in ladder.

The same logic in SCL – use whichever your plant standard prefers; both write the same DB members that WinCC reads:

// FB_SeqM1 – CASE sequence with wait codes (see the TIA lessons for the full pattern)
#T_Step(IN := #Step = #StepOld, PT := #StepMax);
"DB_SeqM1".StepChanged := #Step <> #StepOld;      // ladder network 1 uses this
#StepOld := #Step;
CASE #Step OF
    10: IF NOT "DB_IO".M1_PartPresent THEN "DB_SeqM1".Wait := 1; ELSE #Step := 20; END_IF;
    20: IF NOT "DB_IO".M1_Clamped     THEN "DB_SeqM1".Wait := 2; ELSE #Step := 30; END_IF;
    30: IF NOT "DB_IO".M1_Done        THEN "DB_SeqM1".Wait := 3; ELSE #Step := 10; END_IF;
END_CASE;
"DB_SeqM1".Step := #Step;
"DB_SeqM1".MachineStep := #Step = 20 OR #Step = 30;
"DB_SeqM1".Timeout := (#T_Step.Q AND "DB_SeqM1".MachineStep) OR ("DB_SeqM1".Timeout AND NOT "DB_SeqM1".Cmd_Reset);

The complete pattern with hold, abort and recovery is in PLC step sequences.

Stage 4Link PLC Tags to WinCC: Structure Type

In Tag Management add the SIMATIC S7-1200, S7-1500 Channel, create a connection with the CPU IP address, then use AS Symbols to load the PLC symbols and drag the DB members you need into a tag group. The DB members must have Accessible from HMI ticked in TIA Portal. Names and menus can differ slightly between WinCC versions.

Create a structure type Seq with elements Step, Wait, StepTime, Timeout and Cycles, then instances M1 and M2 addressed to DB_SeqM1 and DB_SeqM2. A new machine is one more instance.

Stage 5Text Lists, Overview Screen and Step Archive

#ObjectPropertiesTag / event
①Text list objects (per row)Step: 10 Load part, 20 Clamp, 30 Process; Wait: 1 part present, 2 clamped, 3 process doneM1.Step, M1.Wait
②I/O field step timeOutput, 99.9 s; background red via dynamic on TimeoutM1.StepTime, M1.Timeout
③Row repeated per machineFaceplate or copied group with instance tagsM2.*
④Tag LoggingStep tags archived on changeArchive PVA_Steps
⑤OnlineTableControlStep history with timestampsPVA_Steps

The panel version is in HMI sequence status screen.

Stage 6Perform and Test: Two-Machine Sequence Overview

Two stations run their sequences. The overview screen shows step text, blocking condition, step time and cycles; the history table is what the step-transition archive keeps. Jam a station and read the cause from the screen.

Stations and PLC
WinCC Runtime · Sequence overview
SeqOverview.pdlLine 2
MachineStepBlocking conditionStep timeCycles
Step transitions (from the archive)
TimeMachineTransitionNew step

Troubleshooting

SymptomLikely causeFirst check
Step shows a number, not textText list missing that valueText list assignments
Wrong machine shownInstance tag mix-upStructure instance addressing
History emptyStep not archived on changeTag Logging settings

Hands-On Lab: Build a Two-Machine Sequence Overview

Hands-on
Before you start
  • TIA Portal and WinCC Explorer V8.1
  • Estimated time: 90 minutes
1

Wire and declare the station sensors

Declare part present, clamped and done for each station.

Station signals declared.
2

Map into DB_IO

Copy the sensors per station.

DB_IO follows each station.
3

Write the sequence and watchdog

FB_Seq in SCL with wait codes; watchdog and log pulse in ladder.

Sequences run; watchdog and pulse behave identically in LAD and SCL.
4

Create the WinCC structure type and tags

Structure type Seq with Step, Wait, StepTime, Timeout, Cycles; instances M1, M2.

Structure type and two instances exist.
5

Build the overview screen and archive

Text lists for step and wait, one row per instance; Tag Logging on change for Step.

Overview and history show both machines.
6

Test with a jam

Jam one station and read the cause and the history.

A jam is identified by machine, step and condition.
Checkpoint—how to know you did it right

From one screen you can say which machine stopped, in which step, waiting for what, and since when.

Frequently asked questions

How do I show a step number as text in WinCC?

Use the Text list smart object (or an I/O field with a text list) connected to the step tag, with one assignment per step number. Number steps in tens so the list can grow without renumbering.

How do I show what a step is waiting for?

Let the PLC write a wait code per step and display it through a second text list. The condition is evaluated where it is known – in the PLC.

How can I analyse where a machine loses time?

Archive the step tag on change in Tag Logging, or log each transition with a timestamp, then evaluate step durations in a table control or an SQL report.

Why a step watchdog in the PLC rather than in WinCC?

The PLC knows exactly when a step starts and runs every scan; WinCC would only see what it reads at its acquisition cycle. WinCC displays and archives the result.

Should the sequence be written in SCL or ladder?

The CASE sequence is clearer in SCL; the watchdog and the logging pulse are clear in ladder. Both are shown, and both write the same DB members.

Can one screen show many machines?

Yes. Use a structured tag type for the sequence interface and one row or faceplate per instance, so adding a machine is adding an instance.

Reviewed by Bhawesh Kumar SinghIndustrial Automation Trainer and Industry 4.0 Consultant · Softwell Automation · 21+ years industry experience

Get the full syllabus + free demo class

Share your details—a Softwell training advisor will contact you with batch dates, fees and hardware-practice options.

No spam. Used only to share course details for this enquiry.

Learn with practical industrial examples

Join live online, Pune classroom or corporate in-plant automation training.

Request Course Details
Verified learning pathway

Discuss WinCC Sequence Overview Screen

Explore practical curriculum, software, hardware and batch options for this technology.

Content reviewed: 16 October 2026

Siemens PLC & TIA Portal Learning Path

Continue with the related Siemens PLC tutorials in this practical learning series.

  1. SCL vs Ladder Logic
  2. Upload PLC Program
  3. TIA Selection Tool
  4. Analog Input Scaling
  5. PLC Counters
  6. PLC Timers
  7. Addressing & Data Types
  8. Hardware & PLC Tags
  9. OB, FB, FC & DB
☎ Call WhatsApp ✉ Email Enquire Now