Siemens controls technical resource
Siemens-Controlled Machine Down or Not Starting?
A stopped Siemens-controlled machine has no single diagnostic layer. First distinguish a controller in STOP from one still in RUN, an offline field station from one bad channel, and a drive fault from an HMI communication symptom. The first verified event matters more than the last alarm left on screen.
Use the scope of the first verified event
Siemens system diagnostics distinguishes device failure, module fault, channel fault and I/O access error. Those categories describe different evidence: a lost station is not proof that its individual modules failed, and a channel fault does not prove the CPU entered STOP. Compare displayed times, actual CPU mode and the affected part of the process before choosing which subsystem record to inspect.
An operator can report the visible message, machine behavior and whether a normal restart was attempted, without entering the cabinet or changing the program. Authorized controls personnel can correlate the diagnostic buffer, configured I/O and drive events using the applicable model manuals; site safety procedures govern any physical work.
A verified CPU STOP leads to the S7-1500 STOP resource; a CPU in RUN with no start leads to the sequence/permissive resource.
Siemens official technical reference — use the edition and hardware scope stated by Siemens; this is background for interpreting evidence, not a diagnosis of a particular machine.
First locate the layer of the reported fault
A machine that will not move does not tell you whether the controller stopped, its running program is holding a sequence, a field station is unavailable, or one signal is in fault. These are different investigations. Use only status already visible from normal operation; an HMI alarm is not proof of the current CPU mode or the cause of the stop.
CPU indicates STOP
If a safely visible CPU indication confirms STOP, the diagnostic buffer and the RUN-to-STOP event history become the starting evidence. Do not assume the last alarm caused the transition. See the S7-1500 CPU STOP path.
CPU remains in RUN; machine will not start
RUN means the controller is executing, not that a start request was accepted. The selected mode, first unmet permissive, commanded action and feedback are different questions; use the PLC-in-RUN sequence path.
Whole PROFINET station reported offline
A named device not reachable is a station-communication question: note which station and whether other stations report the same symptom. The CPU may still be in RUN. See the device-offline path.
Individual ET 200SP module or channel
If the station remains reachable but a specific slot or channel has a diagnostic, the question is local to that signal or module, not automatically the whole network. See the module/channel path.
If the CPU mode or station reachability is unknown, say so; these branches are not a diagnosis. The operator can share what is already visible without opening an enclosure or reproducing the failure. A qualified person can correlate timestamps and the installed project later.
Trace the stop, not just the last alarm
The useful question is what changed first: did the controller report a diagnostic event, did an operator alarm appear, or did a drive report a fault? Comparing the sequence with the machine's actual state helps narrow where to investigate. The available information depends on the installed equipment, configuration, and permitted access.
PLC and I/O evidence
If PLC status or diagnostic entries are available, compare them with the time of the stop. Ask which part of the machine sequence stopped first and whether an input, output, or communication condition changed. A diagnostic entry alone does not prove the root cause.
HMI alarms and machine state
Record the exact displayed alarm wording, number if present, and when it appeared. Was it active before the machine stopped, or did it follow another event? An HMI message may describe a consequence of a stop rather than its initiating fault.
Drive faults and warnings
Note any displayed drive fault or warning exactly as shown, along with the model if known and what the machine was commanded to do. If the drive did not start, establish whether a start command was present before assuming the drive itself failed.
What the visit is for: distinguish the observed symptom from a plausible fault location, document findings, and recommend a sensible next step. Diagnostics are not a guarantee of an immediate restart, replacement, or equipment repair.
If a SINAMICS G120 drive displays a fault or will not start, the G120 drive-start guide separates a drive fault or switching-on inhibited status from a missing command or setpoint; none is assumed to be the cause without checking the installation.
If the HMI itself reports a lost PLC connection or stops updating values, the HMI-to-PLC communication guide distinguishes a disconnected display from the controller's actual state and a separate machine-process alarm.
For an S7-1200 controller STOP event, the I/O-station diagnostic case describes recorded I/O errors, a subsequent station-failure event and a hardware-configuration event that explicitly records the STOP transition. The available buffer does not establish the machine's production outcome or identify a failed physical device; the linked case page remains under evidence review.
If a positioning axis jumps or faults as soon as it is asked to operate, read our SINAMICS S120 axis troubleshooting case. It starts with what an operator can see, then explains the A07496 and drive-configuration findings in that confirmed case.
For a different Siemens controls issue, see our S7-1200 and CM 1243-5 TIA Portal upgrade case. It documents PLC/PROFIBUS hardware compile errors during a project migration; it does not establish that the machine was down or that the errors were resolved.
If the engineering PC cannot discover or connect online to the PLC in TIA Portal, see the TIA Portal connection guide. That access problem does not alone establish the machine's controller state.
For a named G120 trip, compare the fault-specific evidence: F30001 overcurrent, F30002 DC-link overvoltage or F01910 fieldbus setpoint timeout. Do not apply one fault's interpretation to another.
If the display names S120 F07900 motor blocked / speed-controller limit, preserve axis and motion evidence. An S7-1200 SM 1231 analog wire-break alarm instead points to a channel and process signal; a Unified Comfort Panel that boots without Runtime points to an HMI startup question.
Optional details, if already known
You can call without collecting anything first. If already known or safely visible, these details may help the initial conversation:
- The site location, machine name, and what the machine was doing when it stopped.
- Exact HMI alarm text and number, drive fault or warning code, and photos of existing displays.
- PLC, HMI, and drive model numbers if already known; do not open a panel just to find them.
- When the trouble began, whether it is constant or intermittent, and any recent changes or prior attempts to restart.
- Who at the site can provide the machine documentation and authorize access for diagnostics.
More specific fault layers
A saw with a shuttle reference message belongs to the position-reference guide; a saw with an infeed-ready message belongs to the Smart Line Module guide. Neither is a universal saw diagnosis.
An S7-300 CPU 315-2 DP buffer showing OB122 and 16#2942/2943 read/write access errors has a distinct S7-300 OB122 analysis; the codes do not by themselves identify a failed module or CPU STOP. An S7-400 local-data/OB88 event belongs to the separate OB88 analysis. For separate engineering-access symptoms see TIA Portal online connection.
A flow-control loop oscillation using S7-300 CONT_C (FB41) is a separate process-control symptom, not an OB122 access event or a general CPU STOP diagnosis. See the FB41 pump-flow guide.