SiemensETIJohnson ControlsIFMSICKWIKABosch RexrothELKO EPHYUNDAIABBVEGAKSR KUEBLERAlfa Laval

Fault · SINAMICS G130, G150, S120, S150

F31837Encoder 1 DRIVE-CLiQ: Component fault

What it means

F31837 reports that a fault has been detected on the DRIVE-CLiQ component concerned — on Encoder 1 this is the Sensor Module Encoder 1 — and Faulty hardware cannot be excluded. The message value tells you which component reported the fault and why, so read it before replacing anything. Depending on how the drive is configured, the same condition can also be output as an alarm or with no reaction at all. Faults with neighbouring numbers that also concern Encoder 1 on DRIVE-CLiQ — F31813, F31820, F31835, F31836, F31845, F31850, F31851, F31860 — are described on their own pages.

Why it appears

  • Fault cause 32 (= 20 hex): error in the telegram header.
  • Fault cause 35 (= 23 hex): receive error — the telegram buffer memory contains an error.
  • Fault cause 66 (= 42 hex): send error — the telegram buffer memory contains an error.
  • Fault cause 67 (= 43 hex): send error — the telegram buffer memory contains an error.

What to check

  1. Check the DRIVE-CLiQ wiring for an interrupted cable and for faulty contacts.
  2. Check the electrical cabinet design and the cable routing for EMC compliance.
  3. If required, use another DRIVE-CLiQ socket (p9904).
  4. Replace the component involved.

Reading the message value

  • The drive puts two pieces of information into the message value: the component number and the fault cause.
  • Coded in the message value (r0949 for the fault, r2124 when it appears as an alarm) as 0000yyxx hex: yy = component number, xx = error cause.

Parameters the manual names

  • r0949 (fault value): read the coded message value of F31837 here — component number and fault cause in 0000yyxx hex.
  • r2124 (alarm value): holds the same coded value when the condition is output as an alarm instead of a fault.
  • p0491 (motor encoder fault response ENCODER): the manual's cross-reference for this fault — it sets the response the drive applies when Encoder 1 reports a component fault.
  • p9904 (topology comparison acknowledge differences): named in the remedy for the changeover to another DRIVE-CLiQ socket; topology differences are acknowledged with it.

Acknowledging and restarting

Remedy the cause first, then acknowledge the fault immediately — only after acknowledgement can the drive resume operation. In the alarm and no-reaction variants, reaction and acknowledgement are both omitted; the message then signals the component fault without the drive tripping, and the value can be read in r2124.

What differs between the drive families

Straight from the manuals' own fields — F31837 is not described identically everywhere.

Drive familyReactionAcknowledgeMessage classComponentManual
S120, S150Infeed: OFF2 Servo: ENCODER (IASC/DCBRK, NONE) Vector: ENCODER (IASC/DCBRK, NONE) Hla: ENCODER (NONE)IMMEDIATELYInternal (DRIVE-CLiQ) communication error (12)Sensor Module Encoder 1SINAMICS S120, S150 List Manual · p. 3068
G130, G150Vector: ENCODER (IASC/DCBRK, NONE) Infeed: OFF2IMMEDIATELYInternal (DRIVE-CLiQ) communication error (12)Sensor Module Encoder 1SINAMICS G130, G150 List Manual · p. 1752

The drives this code lives on

F31837 is described for G130, G150, S120, S150. These are the converters of those families in our catalogue — price on request.

Questions technicians ask

What does fault F31837 Encoder 1 DRIVE-CLiQ component fault mean?

The drive has detected a fault on the DRIVE-CLiQ component of Encoder 1, the Sensor Module Encoder 1, and faulty hardware cannot be excluded. The message value names the component number and the fault cause.

How do I decode the F31837 message value?

Read r0949 (or r2124 if the message came as an alarm): the value is coded 0000yyxx hex, where yy is the component number and xx the error cause, e.g. 20 hex for an error in the telegram header.

How do I fix fault F31837?

Check the DRIVE-CLiQ wiring (interrupted cable, contacts), review the cabinet design and cable routing for EMC compliance, and if required use another DRIVE-CLiQ socket (p9904). If the fault persists, replace the component involved.

Does F31837 always trip the drive?

No. Depending on the drive configuration, the same condition can also be issued as an alarm or with no reaction at all; in those variants there is no drive reaction and nothing to acknowledge.

Codes next to this one

Source

Written from Siemens' own List Manuals and operating instructions; every number, designation and parameter on this page is checked against them before publication.

All SINAMICS codes: fault and alarm codes · the F31xxx group · SINAMICS manuals · Siemens manuals