Explainer
Does SCADA need a master and slave PLC to run
Short answer
No. A single S7-300 with one WinCC station is a complete SCADA system for one boiler: the PLC runs control and interlocks, WinCC supervises, and web clients only display. A master and slave PLC pair is needed only when two controllers must exchange data or share one polled serial network.
On this page
No. One PLC plus one WinCC station is a complete SCADA system for one plant. The S7-300 scans the boiler instruments and runs the control logic, the WinCC runtime on a PC supervises it, and the web server and clients are PC roles layered on top of the runtime. Master and slave describe a relationship between two controllers, and a single-boiler project has only one controller. WinCC is documented as scalable from a single-user system up to distributed applications, so multiple PLC stations are something the platform supports, not something it requires.
The hierarchy SCADA actually needs #
SCADA is the supervisory layer above real-time control, and its chain runs in one direction: instruments wired into the S7-300, values in PLC memory, tags in the WinCC runtime, objects on screens, screens served to web clients. Every layer above the PLC reads values and requests actions; the control decisions stay in the controller. A master/slave pairing would be a link between two PLCs, one level below WinCC, and nothing in this chain ever reaches it.
The claim that WinCC is dedicated to multiple-PLC installations gets the software backwards: the vendor documents the runtime as a PC-based operator control and monitoring system for visualizing processes and production flows, with no station count attached. For how the software divides the work between screens, tags and drivers, read what WinCC does in an HMI and SCADA system.
Who does what in a one-PLC cell #
| Role | What it owns | If it goes down |
|---|---|---|
| S7-300 | Input scan, control logic, interlocks, output writes | Nothing above it can take over this job |
| WinCC runtime | Screens, alarms, trends, the tag connection, validated writes | Plant runs unsupervised from the PC |
| Web service | Publishes the runtime screens to clients | Remote viewing lost; local runtime unaffected |
| Web client | One operator session, viewing and permitted commands | One session lost; everything else unaffected |
None of the three PC rows adds a controller; they are software on the station or a browser somewhere else. The last column is also the commissioning test: close a web client under controlled conditions and confirm the S7-300 keeps controlling, because that is the designed behavior, not a fault.
Where master and slave PLC roles do belong #
Two configurations actually create a master PLC and slave PLCs. The first is a shared polled serial network, where the link allows only one station to initiate and that station, configured as master, polls the others as slaves; vendors document exactly this arrangement for their serial PLC networks, DirectNET being one published example. The second is direct data exchange between two controllers, such as a line PLC and a utilities PLC, where one is configured to read and write the other's data; the initiating controller is the master by configuration.
The words also appear at protocol level without any second PLC: on a Modbus RTU link the polling SCADA PC is the master and the single PLC answers as slave, which is a device role on a wire, not an architecture. It matters the moment a second master appears on the same slave — an HMI Modbus timeout caused by a PLC master-slave conflict is the standard result. One floor further down in controls, master/slave also names the arrangement in e-stop circuits where one relay supervises another, a subject with its own safety relay hierarchy design guidelines and no relation to PLC data exchange. None of these cases exists in a one-boiler, one-PLC project.
The count for one boiler, one S7-300 and one WinCC station #
Inputs, each with its source:
- Controllers on the job: 1, the S7-300 already in the project.
- Measured variables: 5 — boiler temperature, boiler pressure, cold-water inlet flow, outlet flow and water level, from the process scope.
- Operator-adjusted setpoints: 2 — temperature and pressure, the two values the project adjusts.
- WinCC stations: 1, per the plan.
Rule in words: a PLC master/slave configuration is needed only when two or more controllers must exchange data with each other, or when controllers share one polled network where only one station may initiate. Count the controller pairs that must exchange data: pairs = N × (N − 1) / 2 for N controllers.
Arithmetic:
- Inter-controller pairs: 1 × (1 − 1) / 2 = 1 × 0 / 2 = 0 pairs.
- Read tags: 5 variables × 1 tag each = 5 tags.
- Write tags: 2 setpoints × 1 tag each = 2 tags.
- Process tags on the single WinCC connection: 5 + 2 = 7 tags.
Result: 0 controller pairs, so 0 master roles and 0 slave roles anywhere in the system, with 7 process tags carried on one connection to the single S7-300.
Decision: at 0 pairs, skip the master/slave question entirely and spend the commissioning time on scaling, units and alarms. The number that changes this answer is the controller count: at N = 2 the pair count is 2 × 1 / 2 = 1, and only then must one controller take the initiating role, because the pair exchanges data or shares a polled port. Until a second controller physically exists, one PLC plus one WinCC station is not a reduced SCADA system; it is the whole one for this plant.
Setting up the one-PLC station #
Build from the bottom of the chain upward:
- Program and run the S7-300 first, and confirm each process value moves in controller memory with the programming tool before WinCC enters the picture.
- Configure the PC station to match the interface. One documented configuration pairs a CPU314C-2DP at the controller with a PC station holding a cp5512 Profibus card and the WinCC application object; over Ethernet the equivalent is an Ethernet-capable S7-300 and the matching channel.
- In WinCC, select the communication channel for that interface, create one connection to the PLC station, and map the tags into the PLC data areas.
- Prove reads before enabling writes, one write at a time; a working read proves the read path only, never write addressing or permissions.
- Add a life-bit: one bit the PLC inverts on a timer and WinCC flags as stale when it stops changing, so a dead link is visible before values freeze into plausible numbers.
Diagnose a bad or static display in this order: instrument, live PLC value, PLC communication diagnostics, tag quality in WinCC, screen binding. That order separates an instrument problem from a SCADA problem in one pass.
The web layer comes last and depends on the installed WinCC edition and its licenses; read the exact web capabilities from the installed documentation and license manager rather than from the product name. The station itself can be any Windows PC the software supports — and when the runtime or a client session has to live at the machine instead of on a desk, industrial panel PCs are the touchscreen-computer fit for that spot.
Commands and the one safety rule #
A supervisory command is a request to PLC logic, never a direct write to a physical output from a screen. Start, stop, mode and setpoint requests pass through the PLC's permissives, interlocks and range checks; the controller accepts or rejects and reports the result back to WinCC. Keep indication separate from authority — an operator allowed to view pressure is not thereby allowed to change its setpoint — and enforce user levels in WinCC while the PLC re-validates every write, because a second write path such as a service tool can always exist.
Boiler pressure and temperature protection executes in the PLC or its dedicated protection hardware, so it stays in force with the SCADA PC and every web client switched off.
Growing past one PLC without a master #
Adding a second controller later adds a second WinCC connection, not a master PLC: over Ethernet each S7-300 keeps its own address and the station talks to both, the multi-station case worked through in connecting multiple S7-300 PLCs to WinCC stations. A master PLC enters only when those two controllers must exchange data with each other directly or share one polled serial port. And if the client side grows to browsers across a plant network, that growth is choosing web-based HMI and SCADA architecture, still without changing who is master of anything.
Questions asked
Does WinCC require multiple PLC stations to be worth using?
No. The platform is documented as scalable from a single-user system to distributed applications, and the runtime is a PC-based operator control and monitoring system. In the single-user form the runtime, screens and tag acquisition all run on one PC with no separate server tier, and one PLC station is a fully supported configuration. Multiple stations are something you grow into, not a precondition.
Is the WinCC PC the master and the S7-300 the slave?
Only in the protocol sense, and only on protocols that use those words. On a Modbus RTU link the polling PC is the master and the answering PLC is the slave, with no second PLC involved. On the Profibus or Ethernet channels for S7 controllers the relationship is a tag connection between station and controller. Neither case adds a controller to the plant.
How do I prove a web client shows live data rather than a cached screen?
Change one verified process input and watch the same engineering value and unit move on the local runtime and on the client. Configure the displays to show tag quality or a stale-data indicator, and toggle a life-bit in the PLC that WinCC marks invalid when it stops changing. A convincing screen with frozen values is exactly what a dead link produces.
Where should the temperature and pressure setpoints be limited?
In the PLC. Entry limits on the screen improve usability, but the controller must clamp or reject every write against its own permissive and interlock logic, because another write path such as a service tool can exist. Protective trips for pressure belong in the PLC or dedicated protection hardware and must function with the SCADA PC switched off.
When would this project actually need a master PLC?
Only when a second controller appears and the two must exchange data with each other, or when two controllers must share one polled serial network where only one station may initiate. With the pair-count formula, two controllers give 2 × 1 / 2 = 1 pair to manage. A second WinCC connection to a second PLC does not create that pair.