What it means
F32887 is raised when a fault is detected on the DRIVE-CLiQ component involved for encoder 2 — the Sensor Module for encoder 2. Faulty hardware cannot be excluded. The message value identifies the component involved and the specific fault cause. Depending on the drive configuration, the same condition can also be output as an alarm (A) or without any reaction (N). The drive responds with a stop of the affected drive object; the exact stop response depends on the drive object.
Why it appears
- A fault has been detected on the DRIVE-CLiQ component involved for encoder 2, the Sensor Module for encoder 2.
- Faulty hardware cannot be excluded.
- The specific fault cause is coded in the message value — see the fault value decoding below.
What to check
- Check the DRIVE-CLiQ wiring, e.g. for an interrupted cable or a problem with the 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 enters the component number and the fault cause into the message value.
- In r0949 (fault value) or r2124 (alarm value) the information is coded as 0000yyxx hex, where yy = component number and xx = error cause.
- 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.
- Fault cause 96 (= 60 hex): Response received too late during runtime measurement.
- Fault cause 97 (= 61 hex): Time taken to exchange characteristic data too long.
Parameters the manual names
- r0949 — fault value: read the coded component number and fault cause of F32887 here (see the decoding above).
- r2124 — alarm value: holds the same coding when the message is output as an alarm.
- p9904 — topology comparison acknowledge differences: needed if you switch the connection to another DRIVE-CLiQ socket, so the changed topology is acknowledged.
Acknowledging and restarting
Once the cause has been remedied, acknowledge the fault immediately; the drive can then be restarted. When the same condition is configured as an alarm (A) or without a reaction (N), it triggers neither a stop response nor an acknowledgement (NONE).
What differs between the drive families
Straight from the manuals' own fields — F32887 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) | — | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 2 | SINAMICS S120, S150 List Manual · p. 3124 |
| G130, G150 | OFF1 (IASC/DCBRK, NONE, OFF2, OFF3) | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 2 | SINAMICS G130, G150 List Manual · p. 1801 |
The drives this code lives on
F32887 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 F32887 on a SINAMICS drive mean?
It reports a fault on the DRIVE-CLiQ component involved for encoder 2, the Sensor Module for encoder 2, and faulty hardware cannot be excluded. The message value tells you which component is affected and the specific fault cause.
How do I clear fault F32887?
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.
How is the fault cause coded in the F32887 message value?
In r0949 or r2124 the value is coded as 0000yyxx hex: yy is the component number and xx the fault cause. For example, 32 (= 20 hex) means an error in the telegram header, and 96 (= 60 hex) means the response was received too late during runtime measurement.
Can F32887 also appear as an alarm?
Yes. Depending on the drive configuration, the same condition can also be output as an alarm (A) or without any reaction (N); in those cases neither a stop response nor an acknowledgement is triggered.
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 F32xxx group · SINAMICS manuals · Siemens manuals