What it means
F31886 reports a DRIVE-CLiQ communication error on the path from the Sensor Module of encoder 1 to the Control Unit: the data were not able to be sent. The message value identifies the affected component and the fault cause; for this code the manual names one fault cause, 65 (= 41 hex), Telegram type does not match send list
. Depending on how the drive is configured, the same condition can also be issued as an alarm (A) or with no reaction (N).
Why it appears
- A DRIVE-CLiQ communication error occurred from the Sensor Module (encoder 1) involved to the Control Unit — the data could not be sent.
- The fault cause stored with the message is 65 (= 41 hex): the telegram type does not match the send list.
What to check
- Carry out a POWER ON, i.e. power the drive up again.
- Check whether the firmware version of the encoder (r0148) matches the firmware version of the Control Unit (r0018).
Reading the message value
- The drive stores the component number in placeholder %1 and the fault cause in placeholder %2.
- In the fault value r0949 and the alarm value r2124 the information is coded as 0000yyxx hex: yy = component number, xx = error cause.
- For this code the error cause is 65 (= 41 hex) — the telegram type that does not match the send list.
Parameters the manual names
- r0949 — fault value: read the coded message value here while the fault is present (0000yyxx hex).
- r2124 — alarm value: holds the same coded information when the condition is signalled as an alarm.
- r0148 — Sensor Module firmware version: compare it against the Control Unit firmware version, as the remedy asks.
- r0018 — Control Unit firmware version: the reference for the firmware comparison with r0148.
Acknowledging and restarting
Acknowledge the fault immediately. The remedy begins with carry out a POWER ON
, followed by the firmware check: the encoder's firmware version (r0148) must match the Control Unit's firmware version (r0018).
What differs between the drive families
Straight from the manuals' own fields — F31886 is not described identically everywhere.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | Infeed: NONE (OFF1, OFF2) Servo: ENCODER (IASC/DCBRK, NONE) Vector: ENCODER (IASC/DCBRK, NONE) Hla: ENCODER (NONE) | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 1 | SINAMICS S120, S150 List Manual · p. 3072 |
| G130, G150 | Vector: ENCODER (IASC/DCBRK, NONE) Infeed: NONE (OFF1, OFF2) | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 1 | SINAMICS G130, G150 List Manual · p. 1756 |
The drives this code lives on
F31886 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 cause 65 in F31886 mean?
It is the value 41 hex: the telegram type does not match the send list, so the Sensor Module of encoder 1 could not send its DRIVE-CLiQ data to the Control Unit.
How is the message value of F31886 coded?
In r0949 (fault value) or r2124 (alarm value) the value reads 0000yyxx hex, where yy is the component number and xx the error cause.
Can F31886 also appear as an alarm?
Yes. Depending on the drive's configuration, the same condition can also be issued as an alarm (A) or with no reaction (N).
What do I do first about F31886?
Carry out a POWER ON, then compare the firmware version of the encoder (r0148) with the firmware version of the Control Unit (r0018) and acknowledge the fault immediately.
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