Home / Guides / Siemens S120 Fault Triage Playbook
Fault responseTroubleshooting playbook

Siemens S120 Fault Triage Playbook

Use this playbook when the Siemens S120 Error Codes queue starts filling with thermal or DC-link events such as F30005 or F30021. The goal is to collapse uncertainty fast enough that you know whether to cool, re-check supply conditions, or escalate to replacement.

Advanced9 min readUpdated Apr 9, 2026For Maintenance, Controls, Operations

Before you continue

Use this order first. It is here to remove uncertainty quickly before the page drops into deeper narrative or reference detail.

  1. Step 01Capture the exact event context
  2. Step 02Inspect the thermal path
  3. Step 03Confirm line and DC-link conditions

Fast read

Triage principles

01

02

03

04

Execution order

First-pass sequence

Stay inside a repeatable first-pass routine so every technician is checking the same signals against the Siemens S120 error system instead of improvising from memory.

1

Capture the exact event context

Record the fault code, machine state, ambient condition, and whether the event cleared after a controlled reset.

Next move: If the event is vague or undocumented, fix that gap before moving deeper.

Signals to check

  • Exact code and timestamp
  • Load state at trip
  • Whether the cabinet was already heat-soaked
2

Inspect the thermal path

Check fans, filters, airflow path, cabinet blockage, and recent ambient changes before you assume hardware failure.

Next move: If thermal margin is weak, restore cooling and observe whether the fault returns under normal load.

Signals to check

  • Blocked vents or dirty filters
  • Fan not running or reduced airflow
  • Trip pattern aligned with production heat peaks
3

Confirm line and DC-link conditions

If the code indicates DC-link instability, review incoming supply behavior, braking path assumptions, and any recent electrical changes.

Next move: Only escalate when the instability repeats after line-side checks are complete.

Signals to check

  • Line fluctuations during the event window
  • Recent braking resistor or supply changes
  • Trips during decel or regenerative behavior
4

Choose recover, observe, or replace

Move to a part decision only after the failure mode is stable enough to defend. If not, keep the case in diagnostic mode.

Next move: If the evidence supports replacement, package the failure notes with the quote request.

Signals to check

  • Repeatability after reset
  • Consistency across shifts
  • Whether the unit fails after cooling and supply checks

Decision matrix

What to do after the first pass

Use the evidence pattern, not the anxiety level, to decide the next move.

Recover after restoring cooling

Risk low

Good path when the evidence says environment first, hardware second.

Best for

Thermal events that align with obvious airflow or ambient issues and do not immediately repeat after correction.

Avoid if

The fault repeats under normal temperature and normal load shortly after restart.

Keep the case in electrical diagnosis

Risk medium

Do not jump to replacement while the supply picture is still ambiguous.

Best for

DC-link or overvoltage behavior with unresolved line-side, braking, or deceleration questions.

Avoid if

All upstream checks are clean and the unit still fails in a repeatable pattern.

Escalate to replacement sourcing

Risk high

Package code history and first-pass findings with the sourcing request.

Best for

Repeatable fault behavior that survives cooling, line checks, and controlled restart attempts.

Avoid if

The evidence set is incomplete or the event has not repeated under controlled conditions.

Warning

Do not let one reset become a false close

A successful reset after cooling does not automatically prove the hardware is healthy. It only proves the immediate trip condition disappeared. Keep watching the pattern before you declare the case closed.

Risk notes

What can distort the diagnosis

These are the failure patterns most likely to waste time or push the team toward a weak replacement decision.

Thermal symptoms masked as hardware failure

high

If filters, fans, or cabinet airflow changed recently, a thermal code can look like a dead drive when it is really an environment issue.

Incomplete event capture

high

A quote request with no exact code, no operating condition, and no reset behavior forces unnecessary guesswork.

Supply-side causes left open

medium

DC-link and overvoltage trips can be misread as internal failure if upstream conditions were never checked.

Editorial

What a good handoff looks like

A good escalation package says whether the team is seeing repeatable F30005 thermal behavior, unstable F30021 DC-link behavior, or a confirmed unit failure after cooling and supply checks. If thermal margin is questionable, run the Control Panel Heat Load & Cooling Calculator before you order parts. If the case turns into a catalog-identification question, the ET 200SP baseunit selection guide shows the structured selection template the team can reuse elsewhere on the site.

FAQ group

Questions that slow teams down

Use these answers when the team is split between observation, reset, and immediate replacement.

FAQ

Questions engineers still ask