Explainer
Can a Weintek HMI Command Siemens CPU Run and Stop
Short answer
A Weintek panel can command a Siemens CPU between run and stop only when the EasyBuilder Pro driver for that CPU family documents an operating-state operation; Siemens documents that GET/PUT data access works in either state, so working tags prove nothing. If the operation is absent from your driver, mode changes stay on TIA Portal, a Siemens operator panel or the S7-1200's built-in web server, which offers stop and run and no restart command.
On this page
- Can a Weintek HMI command a Siemens CPU to run and stop?
- What is the difference between CPU operating state and machine operating mode?
- Why does working tag access not prove the panel can stop the CPU?
- How do you check whether your EasyBuilder Pro driver supports CPU mode control?
- What can command an S7-1200 between stop and run when the panel cannot?
- Does putting a CPU in stop make the press safe?
- What should you read before cycling a stopped CPU back to run?
- Can a remote run/stop command replace a broken mode selector?
- When is a run/stop button on the Weintek panel the right answer?
- Questions asked
A Siemens panel changes an S7-1200's operating state from the operator level, so the question follows naturally: can a Weintek panel on the same CPU do the same? It can only when the EasyBuilder Pro driver for that Siemens CPU family documents an operating-state command. A working data connection proves nothing about that, and this article shows the check that decides it, the distinction behind it, and the three documented paths that do change an S7-1200's mode — closing with the press-line case where the cabinets sit in a pit and the mode selector has already failed once.
Can a Weintek HMI command a Siemens CPU to run and stop? #
Only if the EasyBuilder Pro driver for that Siemens CPU family documents an operating-state command — a driver that reads and writes tags proves nothing about run/stop; where the command is absent, mode changes stay on a Siemens path.
The rule comes from how the two connections differ. A Siemens panel and the CPU are engineered together, and the mode command travels as a controller-management service defined for that pair. A Weintek panel connects through an EasyBuilder Pro driver, and a driver is a contract: it implements exactly the operations its documentation lists for the selected CPU family. Reading and writing memory bits and data blocks is one set of operations. Changing the CPU's operating state is a different operation, and it exists in the connection only if the driver documents it for that family.
Three outcomes decide the project:
- The driver documents an operating-state operation for your CPU family: build the button exactly as documented, and prove it on the live CPU before anyone relies on it.
- The driver documents data access only: the panel cannot command CPU state, and mode changes stay on the documented Siemens paths.
- The real requirement is recovering a stuck sequence while the CPU stays in run: that is an application reset written into the machine program with explicit permissives — and it cannot recover a CPU that has actually stopped.
What is the difference between CPU operating state and machine operating mode? #
CPU operating state — run or stop — is whether the controller executes its user program; machine operating mode, such as manual or automatic, is application behavior that runs inside run, and no writable data variable can change the CPU state itself.
Run means the CPU scans and executes the user program; stop means it does not. Machine operating mode — manual, automatic, step, purge — lives inside that program, and every such change happens while the CPU stays in run.
The test that separates them: read the CPU's reported operating state before and after the action you already perform from the Siemens panel. If the CPU stays in run and only the sequence changes, your requirement is an application variable, and a plain write on the Weintek panel does the job today. If the CPU genuinely moves between run and stop, your requirement is controller management, and the driver check below decides it.
Keep the two buttons honest as well. Do not label a production stop as CPU stop unless it truly commands that state, and do not present CPU run as a normal start command: starting program execution and authorizing machine motion are separate decisions, and run belongs to the first, never the second.
Why does working tag access not prove the panel can stop the CPU? #
Because Siemens documents that remote data access through GET and PUT works with the remote CPU in either run or stop: a live connection to tags and data blocks is independent of operating-state control, so a successful read/write test cannot distinguish a data driver from a control-capable one.
Siemens' S7-1200 documentation for GET and PUT communication — the read and write instructions a remote device uses — states that the remote CPU may be in run or in stop when the access executes. Data access is deliberately independent of the operating state; that is what lets a supervisor read a stopped CPU's memory. The consequence: a connection that reads and writes tags behaves identically whether or not it can control the mode, so connection health is not evidence of control capability.
The comparison people reach for is the special control bit that some controller vendors expose for their own CPU management. Mapping management functions to user-addressable bits is one vendor's architecture; it is not a Siemens address specification, and hunting for a Siemens equivalent by trial and error is not a configuration method. No user-writable run/stop bit for an S7-1200 appears in the Siemens documentation checked for this article. If a Weintek driver implements mode control at all, it arrives as a dedicated documented operation for that CPU family — never as a bit someone happened to find.
How do you check whether your EasyBuilder Pro driver supports CPU mode control? #
Open the EasyBuilder Pro installation you commission with, open the documentation for the exact Siemens driver your project uses, and read the operations that driver documents for your CPU family: the check is binary — a documented mode-control operation for your CPU family, or none.
Run it on the installation you actually commission with, because driver capability can change between EasyBuilder Pro versions:
- Record the exact EasyBuilder Pro version, the target panel model, the Siemens CPU family and its firmware, read from the equipment and the project rather than from a description such as a Siemens Ethernet connection.
- In that installation, open the documentation for the exact Siemens driver the project selects — not documentation for a neighboring family.
- Read the operation list that driver documents for the CPU family. You are looking for operating-state control as a named operation, not variable read/write.
- If the operation exists, build the button exactly as documented and determine how the panel reports acceptance, rejection and communication failure — the three outcomes must be distinguishable at the panel before the button is trusted.
- Prove the command on the live CPU, not only offline, following the same approach as testing an HMI against a live PLC. A mode command that has never touched a powered CPU is a design assumption, not a verified function.
If the operation list contains data access and nothing else, stop there: no macro, no scripting layer and no control object can issue an operation the driver does not implement. The panel's answer is no, and the documented Siemens paths in the next section take over.
What can command an S7-1200 between stop and run when the panel cannot? #
Three documented paths remain: TIA Portal from an engineering station, a Siemens operator panel that implements the mode function, and the S7-1200 built-in web server, which changes the CPU between stop and run and offers no restart command.
TIA Portal from an engineering station is the baseline: online mode selection with the full diagnostic view around it. Access protection applies — on a protected CPU the mode command asks for the appropriate access level first, so the credentials belong in the plan rather than surfacing during a fault.
A Siemens operator panel remains the operator-level path, and it is worth being precise about why the button exists there: the panel's own software implements the mode service against the CPU. That service — not the panel's nameplate — is the thing a Weintek driver either documents or does not.
The CPU's built-in web server covers the emergency case without any engineering tool: a stop/run sequence there is a mode change rather than a restart, and the server is the only one of the three paths that lives inside the CPU itself, which matters on a line where the cabinets sit in a pit.
One absence to know: the S7-1200 has no physical mode selector to fall back on, unlike CPU families that ship one, which is exactly why these software paths matter on this controller.
Does putting a CPU in stop make the press safe? #
No — CPU operating state is a program-execution condition, not a safety function; protecting people from a press requires the machine's validated safety functions, and a run/stop command from any panel sits entirely outside them.
CPU stop ends program execution and, on an S7-1200, drives the outputs to their configured substitute values, which default to 0 — off — unless the project sets otherwise. That is programmable behavior, not a validated safety function: a stopped CPU has no place in the safety circuit of a press, and the safety-rated stop and guarding designed for the machine remain the only protection for anyone entering the pit or approaching the tool. Whatever the panel's run/stop button ends up doing, it never substitutes for those functions and it is never wired into them.
What should you read before cycling a stopped CPU back to run? #
Read the CPU diagnostic buffer and the active machine alarms before you issue run, because a stop/run cycle can clear a symptom while its cause stays in place and the evidence becomes much harder to correlate afterwards.
Capture the state while it still exists: before issuing run, read the diagnostic buffer and note the active alarms, permissives and sequence position. The buffer is circular, so newer events eventually displace the entries that explain why the CPU stopped — read first, then run.
The same discipline covers a line that stops repeatedly and receives a run command each time. Repeated stop/run cycling is diagnosis deferred: it can restart execution and temporarily clear an application condition without correcting its cause. If the reason for a stop is unknown, the run command follows the buffer read, not the other way around. And when power restoration does not produce the expected operating state, read the startup configuration and diagnostics before changing anything else.
Can a remote run/stop command replace a broken mode selector? #
No — remote control is not a repair: a broken mode selector leaves the local mode path unproven, so repair or replace it through authorized service, verify a repeatable local stop/run transition, and only then add a remote command as a supplement.
The sequence on a machine where the selector has already failed:
- Restore the selector or its card through authorized service or replacement — the local mode path is the reference, and every remote command is measured against it.
- Verify local operation after the repair: a repeatable stop/run transition with no unresolved CPU diagnostic standing in the way.
- Only then evaluate the remote command path, using the driver check above, as a supplement that saves the trip into the pit — never as a substitute for working local control.
The pit-and-press layout is a genuine argument for the remote command: the panel is at the press, the cabinets are below, and a verified mode command removes a routine walk into the pit. It becomes the wrong answer the day it is the only working means of changing mode, because a failed driver, network or panel then leaves the CPU state unreachable — exactly the situation the broken selector created.
When is a run/stop button on the Weintek panel the right answer? #
Only when the EasyBuilder Pro driver for your Siemens CPU family documents an operating-state operation in the version you run: the button then goes on the panel, built as documented and proven on the live CPU; in every other case, mode changes stay on a Siemens path.
Run the decision once per project, in this order:
- Requirement. CPU operating state, or a machine mode inside run? Machine mode means an application variable, and the panel can do it now.
- Driver. The documented operation list decides: an operating-state operation for your CPU family means build as documented and prove on the live CPU; data access only means the panel's answer is no.
- Fallback. Mode changes stay on TIA Portal, a Siemens operator panel or the built-in web server — the three documented S7-1200 paths.
- Safety. The validated safety functions cover people; the run/stop button covers the program, and neither substitutes for the other.
On those four answers the press-line project either gets its panel button with evidence behind it, or gets the Siemens path with the same certainty — and in neither case rests on tag traffic that once looked like proof.
Questions asked
Do the special control bits another PLC vendor uses also exist on a Siemens CPU?
No — a special run/stop bit is one vendor's design inside its own controllers, and it is not a Siemens address specification. Siemens documents no user-writable CPU mode bit for an S7-1200; the documented mode paths are the engineering tool, a Siemens panel implementing the mode service and the built-in web server. Treat any claimed bit address as unverified until both Siemens documentation and the Weintek driver's operation list name it for your CPU family.
Does the S7-1200 built-in web server answer while the CPU is in stop?
Yes. The web server is a CPU service that runs independently of the user program, which is exactly why it can bring a stopped CPU back to run from a standard browser session. Note the limit: the server exposes stop and run and no restart command, so a stop/run sequence is a mode change, not a restart or a power cycle, and the same project resumes.
Can the Weintek panel keep every other duty while mode changes stay on a Siemens path?
Yes, and that is the normal split. Count operator stations by the job each one needs to do: the Weintek panel runs screens, alarms, trends and data logging against the documented Siemens data driver, while run/stop, download and diagnostics stay on a Siemens panel, an engineering station or the CPU web server. The only duty that cannot move across is the one the driver does not document.
Is wiring a jumper across a broken mode selector an acceptable workaround?
No. Bypassing a damaged control component with jumper wiring is not a vendor-documented mode function, it leaves the CPU's state at power-up undefined, and it removes the one local means of taking the machine to a known condition. Replace the selector or its card through authorized service, then verify startup mode behavior and a repeatable local stop/run transition before any remote command is added.
What should be confirmed in writing before a run/stop button is designed into a panel project?
Four things: the exact EasyBuilder Pro version, the exact Siemens CPU family and firmware, the driver name selected for that family, and a documented operating-state operation in that driver's operation list covering that CPU. Ask the HMI maker or distributor to confirm those four points together, because a claim about some Siemens connection without a driver name proves nothing, and prove the button against the live CPU before relying on it.