What it means
F33886 reports a DRIVE-CLiQ communication error between the Sensor Module (encoder 3) involved and the Control Unit: the data could not be sent. The drive stores the fault cause in the message value, and for this code it is always 65 (= 41 hex) — the telegram type does not match the send list. Depending on how the drive is configured, the same condition can also be issued as an alarm (A) or as an event with no reaction (N) instead of a fault.
Why it appears
- A DRIVE-CLiQ communication error occurred from the Sensor Module (encoder 3) involved to the Control Unit; the data were not able to be sent.
- The fault cause recorded with this event is 65 (= 41 hex): the telegram type does not match the send list.
What to check
- Carry out a POWER ON — the manual gives no further remedy for this fault.
Reading the message value
- The drive writes 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: yy is the component number, xx is the error cause.
- With F33886 the error cause is 65 (= 41 hex), i.e. the telegram type does not match the send list.
Parameters the manual names
- r0949 — fault value: read the coded message value (component number and fault cause) here while F33886 is present as a fault.
- r2124 — alarm value: shows the same coded value when the drive raises this condition as an alarm.
Acknowledging and restarting
Acknowledge the fault immediately. The remedy is to carry out a POWER ON, after which the drive can be restarted. When the drive raises this condition only as an alarm or with no reaction, the manual specifies no reaction and no acknowledgement for those variants.
What differs between the drive families
Straight from the manuals' own fields — F33886 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. 3174 |
| 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. 1845 |
The drives this code lives on
F33886 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 SINAMICS fault F33886 mean?
It reports a DRIVE-CLiQ communication error between the Sensor Module (encoder 3) and the Control Unit: the data could not be sent. The recorded fault cause is 65 (= 41 hex) — the telegram type does not match the send list.
How do I clear fault F33886?
Acknowledge the fault immediately and carry out a POWER ON. The manual gives no further remedy for this code.
How is the message value of F33886 decoded in r0949?
The value is coded 0000yyxx hex: yy is the component number and xx is the error cause. For this fault the error cause is 65 (= 41 hex), meaning the telegram type does not match the send list.
Why does F33886 appear as an alarm instead of a fault?
The drive configuration decides whether the condition is raised as a fault, as an alarm (A) or with no reaction (N). For the alarm and no-reaction variants the manual specifies no reaction and no acknowledgement.
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