What it means
F31836 means that a DRIVE-CLiQ communication error has occurred on the path from the Control Unit to the encoder involved on Encoder 1: the data were not able to be sent. The manuals for G130, G150, S120 and S150 describe this fault identically. The message value tells you which component reported the error and why (see the fault value section). Depending on how the drive is configured, the same condition can also be issued as an alarm (A) or as a message with no reaction (N).
Why it appears
- A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved — the data were not able to be sent.
- Fault cause 65 (= 41 hex): the telegram type does not match the send list.
What to check
- Read the message value in r0949 (or in r2124 if the message was issued as an alarm): it is coded 0000yyxx hex and tells you the component number (yy) and the fault cause (xx — here 65).
- Carry out a POWER ON — this is the only remedy the manuals give for this fault.
Reading the message value
- The drive enters the component number as %1 and the fault cause as %2 into the message value.
- In r0949 (fault value) or r2124 (alarm value) the information is coded as 0000yyxx hex: yy = component number, xx = error cause.
- Error cause 65 (= 41 hex): telegram type does not match send list.
Parameters the manual names
- r0949 — fault value: read out the coded message value of this fault here (0000yyxx hex: component number and error cause).
- r2124 — alarm value: holds the same coding when the message is signalled as an alarm rather than a fault.
- p0491 — motor encoder fault response ENCODER: the response configured for the motor encoder; the manuals reference it for this fault under 'See also'.
Acknowledging and restarting
The fault must be acknowledged immediately. The only remedy the manuals give is Carry out a POWER ON
, i.e. power the converter up again. If the message has been configured with no reaction (N), the drive takes no reaction and no acknowledgement is required.
What differs between the drive families
Straight from the manuals' own fields — F31836 is not described identically everywhere.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | Infeed: 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. 3067 |
| G130, G150 | Vector: ENCODER (IASC/DCBRK, NONE) Infeed: OFF2 | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Sensor Module Encoder 1 | SINAMICS G130, G150 List Manual · p. 1751 |
The drives this code lives on
F31836 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 F31836 mean on a SINAMICS drive?
A DRIVE-CLiQ communication error occurred from the Control Unit to the encoder involved on Encoder 1, and the data could not be sent. The fault cause is 65 (41 hex): the telegram type does not match the send list.
How do I clear F31836?
Carry out a POWER ON and acknowledge the fault immediately. If the message is configured with no reaction (N), neither a reaction nor an acknowledgement is required.
Where is the fault value of F31836 stored?
In r0949 as fault value or in r2124 as alarm value, coded 0000yyxx hex: yy is the component number and xx the error cause, where 65 (= 41 hex) means the telegram type does not match the send list.
Which parameter sets the drive response to F31836?
p0491, the motor encoder fault response ENCODER, which the manuals reference for this fault.
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