What it means
F33837 reports that a fault has been detected on the DRIVE-CLiQ component concerned — the Sensor Module Encoder 3 — and that faulty hardware cannot be excluded. The message belongs to the class of internal (DRIVE-CLiQ) communication errors. Depending on how the drive is configured, the same condition can also be output as an alarm (A) or without any reaction (N). The G130/G150 and S120/S150 manuals describe this code identically for the Sensor Module Encoder 3, so the following applies to all of these families.
Why it appears
- A fault was detected on the DRIVE-CLiQ component concerned; faulty hardware cannot be excluded.
- 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) or 67 (= 43 hex): send error — the telegram buffer memory contains an error.
What to check
- Check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- Check the electrical cabinet design and the cable routing for EMC compliance.
- If required, use another DRIVE-CLiQ socket (p9904).
- Replace the component involved.
Reading the message value
- The drive codes the message value as 0000yyxx hex: yy = component number, xx = error cause.
- The value can be read in r0949 (fault value) or, when the condition is output as an alarm, in r2124 (alarm value).
Parameters the manual names
- r0949 — fault value: read the coded component number and fault cause of F33837 here.
- r2124 — alarm value: holds the same coding when F33837 is output as an alarm.
- p9904 — topology comparison acknowledge differences: applies when you move the encoder connection to another DRIVE-CLiQ socket as part of this remedy.
Acknowledging and restarting
F33837 is acknowledged immediately. Remedy the fault cause on the Encoder 3 DRIVE-CLiQ component first, then acknowledge the fault so the drive can be restarted.
What differs between the drive families
Straight from the manuals' own fields — F33837 is not described identically everywhere.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3) Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3) Hla: OFF1 (NONE, OFF2, OFF3) | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 3 | SINAMICS S120, S150 List Manual · p. 3170 |
| G130, G150 | OFF1 (IASC/DCBRK, NONE, OFF2, OFF3) | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 3 | SINAMICS G130, G150 List Manual · p. 1841 |
The drives this code lives on
F33837 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 F33837 mean on a SINAMICS drive?
It reports that a fault has been detected on the DRIVE-CLiQ component connected as Encoder 3, i.e. the Sensor Module Encoder 3. Faulty hardware cannot be excluded, so the component itself may be defective.
How do I decode the F33837 fault cause?
Read the message value in r0949 (or in r2124 when the condition is output as an alarm). It is coded 0000yyxx hex, where yy is the component number and xx the error cause — for example 32 (= 20 hex) for an error in the telegram header.
What do fault causes 66 and 67 mean in F33837?
Both are send errors: the telegram buffer memory contains an error. Cause 66 is printed as 42 hex and cause 67 as 43 hex.
How do I clear F33837?
Check the DRIVE-CLiQ wiring and the EMC-compliant cabinet design and cable routing, use another DRIVE-CLiQ socket (p9904) if required, and replace the component involved. Acknowledge the fault immediately afterwards.
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 F33xxx group · SINAMICS manuals · Siemens manuals