SINAMICS S120 Fault F31100 — Encoder Zero Mark Distance Error

Overview

Siemens SINAMICS S120 fault F31100 indicates an Encoder Zero Mark Distance Error. This fault occurs when the drive control unit detects that the measured physical distance (number of pulses) between consecutive encoder zero marks (reference marks) does not match the configured value parameterized in the drive's firmware. In closed-loop systems, the zero mark serves as a critical reference point to calibrate and verify the absolute position of the motor shaft, making any discrepancy a major safety and positioning hazard.

When the S120 Control Unit (such as a CU320-2) processes encoder feedback through a Sensor Module (SMC10, SMC20, SMC30, or SME series), it counts the encoder increments between two zero-point pulses. If this count exceeds or falls short of the expected tolerance window defined in parameter p0425 (Encoder zero mark distance), the drive immediately trips on F31100 to prevent uncontrolled acceleration, positioning errors, or mechanical damage.

Symptoms

If your SINAMICS S120 system is suffering from an F31100 fault, you will typically observe one or more of the following symptoms on the shop floor:

• Immediate Drive Tripping: The drive transitions to a fault state (OFF2 or OFF3) as soon as the axis performs a homing routine or completes its first physical motor revolution.
• Intermittent Positioning Errors: The axis may drift or lose its reference point over time, leading to contouring errors or safety-related path deviations before the drive finally faults out.
• Flashing LEDs on Sensor Modules: The LED status indicator on the associated SMC20, SMC30, or SME module may change color (typically flashing red or solid red) during operation.
• Diagnostic Messages in Starter/Startdrive: Active alarms in your Commissioning Tool (STARTER or TIA Portal Startdrive) indicating "Fault F31100: Encoder 1: Zero mark distance error."
• Jerkiness or Motor Vibration: Just before tripping, the motor may exhibit unusual vibrations or mechanical resonance due to rapid, incorrect internal corrections calculated by the position controller.

Possible Causes

Several physical, electrical, and logical issues can cause the zero mark distance evaluation to fail:

• Electromagnetic Interference (EMI): High-frequency electrical noise from the motor power cables regular-mode currents, or nearby frequency converters can couple into the encoder signal line, creating false pulses or swallowing legitimate zero marks.
• Damaged or Poorly Shielded Encoder Cables: Broken internal shielding, poor ground/shield terminations at the cabinet entry point, or fractured conductors within high-flex drag-chain cables.
• Mechanical Axis Slippage: Physical slippage of the encoder's shaft coupling relative to the actual motor shaft, or slippage in friction-wheel encoder systems.
• Contaminated Encoder Scale: Dirt, oil mist, carbon dust, or metallic particles inside an optical or magnetic encoder housing that obstruct the reading head from detecting the physical zero mark.
• Incorrect Drive Parameterization: Mismatched configuration settings in the drive parameter pool. Specifically, parameters p0400 (Encoder selection), p0408 (Encoder rotary pulse number), and p0425 (Zero mark distance) may not accurately match the physical data plate of the encoder.
• Faulty Sensor Module (SMC/SME): Hardware failure or component degradation within the Siemens Sensor Module processing the encoder signals (such as an SMC20 or SMC30).
• Faulty Encoder Electronics: Internal failure of the encoder's optical transmitter diode or magnetic sensor chip, preventing the reliable generation of the zero-track differential signal (usually marked as N or Z tracks).

Step-by-Step Troubleshooting

Follow this systematic engineering procedure to isolate and resolve the root cause of the F31100 fault code.

Step 1: Verify Drive Parameters Against the Encoder Nameplate

Before checking physical components, rule out logical configuration errors:

1. Open your project in Siemens STARTER or TIA Portal.
2. Navigate to the absolute axis configuration and inspect parameter p0400 (Encoder type) and p0408 (Encoder pulse number).
3. Compare these values directly with the label printed on the physical encoder/motor.
4. Verify parameter p0425 (Encoder zero mark distance). For a standard incremental rotary encoder, this parameter should correspond precisely to the number of increments per revolution. If using a linear encoder, verify the grid division and the exact distance between reference marks in millimeters (p0424).

Step 2: Perform an Electrical Noise and Shielding Audit

EMI is a leading contributor to intermittent F31100 faults in industrial environments:

1. Ensure the encoder cable is routed completely separate from three-phase AC power cables. Avoid running them parallel in the exact same wire tray; if they must cross, ensure they do so at a $90^\circ$ angle.
2. Check that the encoder cable shield is grounded at both ends. At the control cabinet side, the shield must be stripped back and clamped using a $360^\circ$ low-impedance grounding shield clamp directly onto the cabinet's functional ground bar.
3. Verify the motor housing itself is cleanly bonded back to the machine ground plate using high-flex grounding braids.

Step 3: Inspect the Physical and Mechanical Connections

Mechanical slip directly distorts the pulse count relative to the motor's actual movement:

1. Isolate power from the drive (verify zero voltage before proceeding).
2. Remove the protective shroud from the encoder.
3. Inspect the coupling hub connecting the encoder shaft to the motor shaft. Check for loose grub screws, radial cracks, soft polyurethane inserts, or overtightened/overstretched bellows couplings.
4. Try to gently rotate the encoder body relative to the motor shaft by hand. If there is any axial play or rotational slippage, tighten the mechanical coupling to the manufacturer's specified torque rating.

Step 4: Run a Diagnostic Signal Trace

Use the commissioning tool's trace function to pinpoint signal dropout:

1. Configure a drive trace in STARTER or Startdrive to record the variables associated with the active encoder (e.g., actual speed, position, encoder path deviation, reference mark detection flag).
2. Set the trigger condition to start recording when Fault F31100 occurs.
3. Run the axis slowly. Analyze the resulting trace graph. Look for sudden spikes or vertical drop-offs in the pulse count or speed feedback track immediately prior to the trip. Continuous, clean waveforms indicate parameters are wrong; rugged, jagged dropouts indicate hardware EMI or cable breaks.

Step 5: Isolate and Validate Hardware

To determine if the issue lies in the encoder, cable, or Sensor Module:

1. If you have a multi-axis setup, swap the encoder cable and Sensor Module (e.g., SMC30) with an adjacent, operational axis of the same type.
2. Run the system again. If the F31100 fault moves to the newly configured axis, the issue lies within that specific Sensor Module or encoder cable.
3. If the fault stays on the original axis, the mechanical encoder built into the motor is likely damaged and requires replacement.

Recommended Actions

• Clear Dirt and Contaminants: If the encoder is an open-frame optical variety (common in large linear axes), clean the glass scale using lint-free cloths and purified isopropyl alcohol.
• Replace Worn Cables: If resistance checks on the A/B or N/Z channels show intermittent open circuits when flexing the cable, replace the cable assembly.
• Reinforce Grounding Schemes: Install Siemens-approved shield connection plates (line filter and line reactor shields) to divert high-frequency noise.
• Standardize Parameterization: Update and download the correct drive topology configuration using the automatic "Detect Drive-CLiQ Topology" feature if utilizing Siemens electronic nameplate motors (DRIVE-CLiQ encoders).

Recommended Replacement Parts

When troubleshooting indicates hardware failure, keep these critical replacement parts on hand to minimize downtime:

Related Articles

• How to Replace a Siemens SINAMICS SMC20 Sensor Module
• Understanding Drive-CLiQ Cable Pinouts and Shielding Best Practices
• Siemens SINAMICS S120 Parameter Configuration Masterlist
• Resolving Contour Errors and Tracking Discrepancies on CNC Axes

FAQ

Q: Can I run my S120 drive without the zero mark check to keep the machine running temporarily?

A: Yes, for non-safety-critical axes operating in standard closed-loop speed control, you can temporarily suppress or bypass the zero mark evaluation. This can be achieved by adjusting parameter p0404 (Encoder configuration) to disable zero-mark evaluation (deselecting the zero-mark bit) or modifying p0425 to a wider tolerance range. Warning: Do not attempt this on positioning axes (such as interpolating CNC axes or vertical load lifters), as it can result in unpredictable mechanical travel and severe equipment damage.

Q: Why does F31100 only occur when the machine reaches high operating speeds?

A: At higher velocities, mechanical vibration increases, which can exacerbate shaft slippage or cause optical reading errors inside the encoder. Additionally, high-frequency EMI generated by the inverter becomes more intense at higher switching frequencies and currents, pushing a marginal cable or poorly terminated shield beyond its noise-rejection limits.

Q: What is the main physical difference between using an SMC20 and an SMC30 for zero-mark evaluation?

A: The SMC20 evaluates analog sinusoidal signals ($1\text{ V}_{\text{pp}}$), calculating intermediate positions using vector interpolation, whereas the SMC30 evaluates digital square-wave signals (TTL or HTL push-pull). Both analyze the zero mark (often called the reference index), but troubleshooting the SMC20 requires analyzing an oscilloscope pattern for degradation of the sinusoidal shape, while the SMC30 focuses on digital high/low voltage transitions.

Q: How do I know if my SINAMICS drive motor has an electronic nameplate to auto-configure these values?

A: Siemens motors with a built-in DRIVE-CLiQ interface (indicated by an RJ45-type connection socket directly on the motor housing, and often denoted in the motor model number) contain an integrated memory module. When plugged into the S120 system, the Control Unit automatically queries the electronic nameplate, auto-populating parameters p0400, p0408, and p0425 without manual engineering intervention. If F31100 occurs on a DRIVE-CLiQ motor, focus immediately on cleaning the optical scale, checking for EMI, or replacing the DRIVE-CLiQ cable rather than debugging parameters.