What it means
F32836 reports a DRIVE-CLiQ communication error on the path from the Control Unit to the encoder connected as Encoder 2 (component: Sensor Module Encoder 2): the data could not be sent. The component states as fault cause that the telegram type does not match the send list. Depending on how the drive is configured, the drive can also signal the same condition as an alarm or without any reaction.
Why it appears
- A DRIVE-CLiQ communication error occurred from the Control Unit to the encoder involved — the data could not be transmitted.
- The reported fault cause is 65 (= 41 hex): the telegram type does not match the send list. Both manuals describe the identical cause, so this applies equally regardless of the drive object concerned.
What to check
- Carry out a POWER ON: switch the drive's power supply off and then back on. The manuals give no further repair steps for this message.
Reading the message value
- The drive puts the component number in the first placeholder of the message value and the fault cause in the second (%1, %2). The information is coded as 0000yyxx hex: yy = component number, xx = error cause. This coding is stored in r0949 (fault value) and r2124 (alarm value).
- Fault cause 65 (= 41 hex): telegram type does not match send list.
Parameters the manual names
- r0949 (fault value) — read here to decode the message value of this fault: 0000yyxx hex, i.e. the component number (yy) and the error cause (xx).
- r2124 (alarm value) — holds the same coding when the drive raises the condition as an alarm instead of a fault.
Acknowledging and restarting
Acknowledge the fault immediately. The remedy the manuals specify is to carry out a POWER ON — switch the drive's power supply off and back on — after which the drive can be acknowledged and restarted. When the condition appears only as an alarm, it triggers neither a reaction nor an acknowledgement.
What differs between the drive families
Straight from the manuals' own fields — F32836 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 2 | SINAMICS S120, S150 List Manual · p. 3119 |
| 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. 1796 |
The drives this code lives on
F32836 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 F32836 mean?
It reports a DRIVE-CLiQ communication error from the Control Unit to the encoder connected as Encoder 2: the data could not be sent because the telegram type does not match the send list.
How do I clear F32836?
The manuals give one remedy: carry out a POWER ON, i.e. switch the drive's power supply off and back on, and acknowledge the fault immediately.
What is fault cause 65 in F32836?
Fault cause 65 (= 41 hex) means that the telegram type does not match the send list.
Where can I read the component number and fault cause for F32836?
In the message value, coded 0000yyxx hex (yy = component number, xx = error cause); it is stored in r0949 as fault value and in r2124 as alarm value.
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