Onsite Siemens S7-1500 PLC diagnostics

Siemens S7-1500 CPU in STOP and the machine will not run?

A controller that has changed from RUN to STOP needs a different investigation from a PLC that remains in RUN while a machine sequence is held. The displayed STOP state is a starting fact—not a diagnosis of a failed CPU, I/O device, program or network. West Engineering Systems provides onsite troubleshooting, diagnostics and fault identification to help determine the next action. We are based in Appleton, Wisconsin, and provide field service across the United States.

Discuss Your Stopped S7-1500

Prefer to describe the indication by phone? Call (920) 851-6363.

Confirm the controller state before interpreting the machine stop

What an operator sees may be a stopped machine, an HMI alarm, an unavailable automatic mode or a visible STOP indication at the controller. Note the exact indications already available. If the HMI has lost its own PLC connection, it cannot alone confirm the current CPU state.

CPU indicates STOP after running

Record when the transition was first noticed, what the machine was doing and whether the STOP followed a power event, a download or another observed alarm. Sequence matters; timing alone does not prove a particular cause.

STOP after a recent change

If the problem began after a maintenance or configuration event, preserve what changed and who has the original project backup. Do not assume the most recent action explains the transition without diagnostic evidence.

HMI says machine stopped, CPU state unknown

A machine alarm or an HMI connection problem is not the same as a verified S7-1500 STOP state. Confirm the controller's actual indication through safe, authorized observation before selecting a diagnostic path.

Important distinction: The S7-1200 CPU STOP / PROFIBUS case documents one machine and one station-failure event. It does not establish the cause or corrective action for an S7-1500 in STOP.

Which evidence can narrow the STOP event?

Siemens' S7-1500 system diagnostics example documents CPU display, TIA Portal, configured HMI and web-server diagnostic views. It explains that a CPU diagnostic buffer records events in order, including operating-mode transitions, program errors and module events. Those are possible event categories to compare—not claims that any one caused this machine to stop.

  • Controller indication and recent events: If already safely visible, note the CPU display or LED state and any diagnostic text. The installed S7-1500 model, firmware, display configuration and site access determine which views are available.
  • Diagnostic-buffer sequence: With authorized access, compare the RUN to STOP transition with earlier and later entries, event IDs, timestamps and associated module or program detail. An event that appears near STOP may be an initiating condition or a consequence; the full sequence and actual project matter.
  • Device and application context: Compare any identified module or communication event with the affected I/O and the machine's behavior. A diagnostic message naming a device does not prove the physical device has failed; an unrelated HMI alarm should not replace the CPU record as evidence.
  • Available diagnostic access: If TIA Portal access is unavailable, that is an additional connection question. Siemens documents that diagnostics may also be visible on an S7-1500 display or a configured web server; neither should be assumed to be enabled or accessible at this site. See the S7-1500 diagnostics function manual for the described options.

Diagnostic goal: preserve the evidence surrounding the actual STOP and identify a justified next action. This is not a generic instruction to clear the buffer, download a program, change error-handling logic or put the CPU back into RUN.

If the engineering computer also cannot connect to this PLC, the TIA Portal online-connection guide covers the separate PG/PC path and access questions without treating a failed online session as the cause of STOP.

If the diagnostic buffer instead names a particular ET 200SP slot or channel, the ET 200SP module/channel guide explains which I/O evidence to preserve; a named event is not by itself proof that it initiated the CPU's STOP.

What to gather before calling

Share existing observations and records, without accessing energized controls merely to collect more:

  • Facility and machine location, machine name and what stopped or became unavailable.
  • Visible CPU RUN/STOP and error indications, exact HMI messages, and photos of screens or displays already safely accessible.
  • Time first observed, last successful operation, whether STOP followed a power event or change, and what happened immediately beforehand.
  • S7-1500 CPU order/model number, installed project/TIA Portal version and available unmodified project backup, if the site has them.
  • Any diagnostic-buffer export already collected by authorized personnel and a site contact who can approve safe access.

Related Siemens troubleshooting paths

If the CPU actually remains in RUN but the machine will not start, see the PLC-in-RUN machine-start guide for sequence and permissive evidence. If controller state is still unknown, the Siemens machine-down guide covers the broader initial observations.

For an S7-1200 that entered STOP with a documented PROFIBUS device failure, the S7-1200 case illustrates case-specific buffer findings only. A machine with an HMI-to-PLC connection fault may require verification of actual CPU state before anyone concludes it is in STOP.

Service scope: We provide onsite troubleshooting, diagnostics and fault identification to help determine the next action. We do not promise equipment repair, a part replacement or an immediate machine restart.

Request onsite S7-1500 CPU STOP diagnostics

Tell us what the controller and operator display show, where the machine is located and when the stop occurred. We can discuss whether an onsite PLC investigation is a fit.

Request Service

Or call (920) 851-6363 or email info@westengineeringsystems.com.