Industrial networks
A missing distributed I/O device is not the same as a fault on one module or channel. Check which station and which diagnostic layer is reporting an event before treating the network as the cause.
Siemens controls troubleshooting resources
A machine that will not start, an HMI without current values, and a drive reporting a fault need different evidence. Start with the observed symptom, locate the affected control layer, then follow a guide for that layer. These resources distinguish diagnostic possibilities from documented field outcomes.
Start with the symptomWritten by West Engineering Systems LLC, an industrial-controls field-service business in Appleton, Wisconsin. The guides are not a substitute for your site's safety procedures.
Choose the control layer to investigate
Start at the first confirmed symptom, not the component named by an alarm. Each area below links to a different diagnostic question.
PLC & I/O
A CPU in STOP needs a different investigation from a controller in RUN whose start sequence is held. A channel wire-break indication is narrower still: it does not by itself prove the CPU stopped.
HMI & operator interface
First determine whether Runtime opens. A panel that never launches its project is different from one whose screens load but report a lost PLC connection or stale values.
SINAMICS drives
Record the exact fault and drive state before choosing a path: a start command that never reaches the drive, an inhibited enable, overcurrent, and DC-link overvoltage do not point to the same condition.
Distributed I/O: ET 200 and analog channels
Separate a device-offline report from one ET 200SP slot diagnostic or an SM 1231 analog channel wire-break indication. An isolated channel message does not establish a failed PLC or an entire network outage.
TIA Portal, STEP 7 and WinCC
A programming device that cannot go online, an HMI Runtime that does not start, and a project that does not compile are different failures. Identify the software version, affected device and exact stage before changing a live project.
Motion & positioning
A positioning axis that jumps or fails to reference can involve feedback, configuration, or sequence state. A documented S120 axis case shows what was actually observed, without promising the same outcome elsewhere.
Find a guide by displayed code or diagnostic family
Verify the exact product and message in the installed firmware's documentation. A fault title narrows the question; it does not identify a failed part.
SINAMICS G120
SINAMICS S120
Controller and communication
- S7-400 16#3576 / OB88: processing-abort diagnostic, not proof that OB88 ran.
- SM 1231 wire break: a channel diagnostic rather than a whole-PLC verdict.
- PROFINET I/O device offline: distinguish station identity and reachability from a module alarm.
Start with the observed machine-down symptom
A stopped machine does not identify its failed component. Compare controller state, panel behavior, drive indication and I/O diagnostics before choosing the applicable guide; an alarm text alone is not a root-cause finding.
Four first distinctions
- Controller RUN versus STOP: If RUN is indicated, a held start sequence, missing permissive or unavailable I/O can coexist with an active CPU. If STOP is indicated, use the controller diagnostic buffer and the exact CPU family instead of attributing it to the last visible alarm.
- HMI runtime versus connection: A panel that cannot open Runtime needs a different path from a running HMI whose values are stale or whose PLC connection is lost. Note which screen appears before diagnosing the network.
- Drive command versus fault: Record whether a command and enable are present and whether the drive itself displays a specific fault. An F30001 overcurrent indication and F30002 DC-link overvoltage indication call for distinct investigations.
- I/O station versus channel: A whole PROFINET station marked offline is a different scope from a single ET 200SP slot or SM 1231 channel fault. Record the device and channel indicated before assuming a wiring or network failure.
These are routing questions, not a remote diagnosis. Equipment variants, program logic and site conditions determine the next safe check.
What to record safely
If already visible, note the controller state, exact alarm/fault code, panel screen, affected I/O address or station, and the sequence of operator-visible events. A photograph of a display can be more useful than a paraphrased alarm. Do not infer event order from a fault list alone.
Do not bypass guards or safety circuits or open energized equipment to gather this information. Follow your site's safety procedures and use qualified personnel for electrical work.
For the next distinction, compare the PLC-in-RUN start-sequence guide with the CPU STOP guide. Neither a running controller nor a stopped one identifies the cause without its diagnostic context.
Find the guide for your observed symptom
Siemens Controls Troubleshooting in Practice
Three different evidence records call for different investigations. These case notes distinguish observed diagnostic events from unverified outcomes.
S7-1200 STOP and I/O-station diagnostic events
An archived CPU 1214C buffer records I/O access errors, then an I/O-station failure for a project-specific device ID, followed by a hardware-configuration event that explicitly records the CPU transition to STOP. A later export records RUN alongside I/O errors. These controller records do not establish a physical device failure, corrective work or whether the machine resumed production. The linked case page is under evidence review.
Read the S7-1200 diagnostic case →SINAMICS S120 axis jumped or faulted immediately
A positioning-axis problem led to drive feedback and configuration findings, including A07496. The configuration issue was resolved in this case; that does not establish that the machine had resumed production.
Read the drive fault case →S7-1200 / CM 1243-5 project would not compile
A TIA Portal upgrade surfaced CPU firmware compatibility and PROFIBUS DP cycle messages. This was a project-compilation issue, not a confirmed machine-down event; the final outcome is not known.
Read the TIA upgrade case →
About this publisher
West Engineering Systems is based in Appleton, Wisconsin, and provides onsite Siemens industrial controls field service for customers across the United States.
WES publishes these guides to separate observed symptoms from conclusions. Product manuals explain what a diagnostic can mean; a machine-specific sequence, configuration and event history are needed to determine what happened on any installation. The case notes identify where the available record ends. WES is independent of Siemens and does not claim Siemens authorization or affiliation.
For site corrections or publisher questions, use the contact address below. Do not send passwords, control-system projects or private machine data in an unsolicited email.
Publisher contact
For factual corrections, publication inquiries or a legitimate business inquiry, email West Engineering Systems LLC. These resources are educational and are not an emergency response channel.