How-to
How to Address S7 PLC Outputs in a WinCC Flexible Tag
Short answer
A WinCC flexible tag must carry the address of the real PLC operand: Bool tags on Q0.1, Q0.2 and Q0.3 for the line, delta and star outputs. DB1.DBX0.0 is bit 0 of byte 0 in data block 1 and follows an output only if the PLC program copies it there — and the S7-200 CPU family has no data blocks at all.
On this page
- Is a PC Runtime tag configured differently than a panel tag?
- What does DB 1 DBX 0.0 mean in the Address column?
- How do I point the tag at output Q0.1?
- Which connection decides what addresses the tag accepts?
- How do I bind the blue LED to the tag?
- Should the lamp show the contactor output or the start command?
- How do I prove the tag is reading the right bit?
- Questions asked
A WinCC flexible tag reads and writes the PLC operand written in its Address column — nothing else. For the star-delta starter that means three Bool tags addressed Q0.1, Q0.2 and Q0.3 on the connection configured for the actual CPU. DB1.DBX0.0 is not another spelling of an output: it is bit 0 of byte 0 in data block 1, and it follows an output only when the PLC program copies that output into it. The steps below take the tag table from that dead DB entry to three working lamps.
Is a PC Runtime tag configured differently than a panel tag? #
No. PC Runtime fills the same tag table as an operator panel — Name, Connection, Data type, Address — with the same communication drivers, so the tag you create for a panel project is the tag you create for the PC. The difference is where the runtime executes, not how a tag is defined.
On its own, a tag only proves that its address was syntactically accepted. The Connection column carries the driver and the path to one specific CPU; the Address column decides which operand inside that CPU the tag follows. Both have to point at the real installation before any screen object means anything.
What does DB 1 DBX 0.0 mean in the Address column? #
DB1.DBX0.0 is data block 1, byte 0, bit 0: the number after DB names the block, the number before the dot is the byte offset, and the number after the dot is the bit position within that byte. Every byte in S7 memory holds 8 bits, numbered 7 down to 0, and the notation is always byte.bit.
That convention gives you the arithmetic for any bit number: divide by 8 — the quotient is the byte, the remainder is the bit. Bit 11 of DB1 lands at 11 ÷ 8 = 1 remainder 3, so its address is DB1.DBX1.3. The three starter outputs all sit in output byte 0: Q0.1 is byte 0 bit 1, Q0.2 is byte 0 bit 2, Q0.3 is byte 0 bit 3.
A DB bit is memory inside a data block: no terminal, no channel, no wiring. Q0.0 is the process image of a physical output terminal. A Bool tag on DB1.DBX0.0 is a perfectly valid tag that reads the state of that one DB bit, nothing more. It mirrors an output only if the program copies the output there — and if the program copies output byte 0 into DB1, the line contactor Q0.1 appears at DB1.DBX0.1, bit 1, not bit 0. DB1.DBX0.0 would mirror Q0.0.
How do I point the tag at output Q0.1? #
Create a Bool tag on the S7 connection and type Q0.1 into the Address column; the tag then tracks that output bit live, and you repeat the same steps for Q0.2 and Q0.3. The full sequence, in order:
- Identify the actual CPU family and its communication path before touching the tag table. A project started for an S7-300 and a cabinet holding an S7-200 are two different targets, and every later step depends on this one.
- Configure the PLC connection to match: on Ethernet, give the PC's network card an unused address in the controller's subnet with the matching subnet mask; on PROFIBUS, set the node the driver will poll.
- In the tag table, set Name to the function (Line, Delta, Star), Connection to your PLC connection, Data type to Bool, and Address to Q0.1, Q0.2 and Q0.3 respectively.
- Transfer the project. A changed address reaches the running system only after a new build is downloaded, which is why an HMI edit needs a new runtime download.
Which connection decides what addresses the tag accepts? #
The connection's driver does: it fixes the operand areas the Address column accepts, so a project whose connection is configured for a different CPU family than the one in the cabinet will reject or silently misaddress the tag. Set the connection for the CPU that is actually wired, then rebuild the tag table against it.
DB operands belong to the S7-300/400 area list; the S7-200 CPU family has no data blocks, so DB1.DBX0.0 names nothing in such a controller. Delete the DB entry and address the outputs directly. If the configured driver does not offer the Q area at all, do not force a DB address as a substitute: add one rung in the PLC program that copies the output area into a memory area the driver does expose, every scan, and address the copy — keeping the arithmetic above, so the copy of Q0.1 lands on bit 1 of the copied byte.
How do I bind the blue LED to the tag? #
Give the LED an Appearance animation on the Bool tag: in the object's Animations > Appearance settings, enable the animation, assign the tag, and set which appearance belongs to value 0 and which to value 1. The graphic drawn in the image editor is presentation only; it carries no address and creates no connection. The lamp changes exactly when the tag value changes, so the blue LED becomes a line-contactor indicator the moment its Appearance is driven by the Q0.1 tag. Use one lamp per tag so line, delta and star are each visible on their own.
Should the lamp show the contactor output or the start command? #
The lamp shows the output — Q0.1, Q0.2 or Q0.3 — or a contactor auxiliary contact wired back to an input; it must never show the operator's start command, because a command proves a key press, not a closed contactor. Put start and stop on a memory bit or DB bit that the program reads as a request, and let the program switch the outputs with its own timing and interlocks.
The operand behind a physical channel stays under the PLC's control, for the same reason an HMI toggle switch cannot write a physical PLC input. The split between what a client may read and what it may write sits in the driver too — why Ignition reads Siemens tags but cannot write them shows the same wall from a different package.
One safety note: the exclusion between the star and delta contactors and the star-delta transition timing belong in the PLC program and in the contactors' hardware interlock. Screen logic is not a safety function, and an HMI write may not substitute for either.
How do I prove the tag is reading the right bit? #
Toggle the bit from the PLC side and watch it in two places at once — the CPU's online status view and the runtime screen — and call the tag correct only when both show the same 0, then 1, then 0 on the exact operand you typed. Work through the checks in this order:
- With the machine in a safe state, switch Q0.1 from the program side — jog the logic or force the bit in the programming tool — and confirm the online view shows 0, then 1, then 0.
- Watch the runtime lamp. It must follow the same two transitions with the appearances you configured.
- If the lamp does not move, check in order: the connection is active with no communication fault in runtime diagnostics; the Address column holds the operand you intended; the data type is Bool; the Appearance animation references this tag.
- For any tag on a DB address, open the program and find the instruction that writes that DB. A tag on DB1.DBX0.0 is honest only if the program puts the copy of Q0.0 there — and your line contactor would be DB1.DBX0.1.
The decision for the star-delta station: three Bool tags — Q0.1, Q0.2, Q0.3 — on the connection configured for the actual CPU; three Appearance-animated lamps on those tags; start and stop on a separate request bit; and no DB address in the tag table unless the program writes it.
Questions asked
Can I write to Q0.1 from the screen to start the motor?
Do not. Commands from the operator belong on a memory bit or a DB bit that the PLC program reads as a start request; the program then sets Q0.1 with its own interlocks and timing. A screen object that writes an output directly bypasses the star-delta sequencing, and when two systems touch the same output bit, the last write wins.
What do DBB, DBW and DBD stand for next to DBX?
They are the sizes of data-block operands: DBX is a single bit, DBB a byte of 8 bits, DBW a word of 2 bytes, DBD a double word of 4 bytes. The marker area repeats the same ladder as MB, MW and MD. A Bool tag uses DBX with byte.bit addressing; a Word tag on DBW10, for example, covers bytes 10 and 11.
Why does the tag read a steady 0 even though the CPU output LED is on?
Three usual causes: the connection points at the wrong CPU or node, the connection type does not match the actual CPU family, or the tag address names an area the program never writes — for example a DB bit on a controller that has no data blocks. Check the connection first, then the address as typed, then the program side of the operand.
Do I need three tags, or can one tag show all three contactors?
Three Bool tags, one per output: Q0.1 for the line contactor, Q0.2 for delta, Q0.3 for star. One lamp animates on one tag at a time, and each contactor needs its own indicator, because star and delta must never be energized together — a single combined tag would hide exactly that fault.