What it means
F36886 reports a DRIVE-CLiQ communication error from the DRIVE-CLiQ Hub Module in question to the Control Unit (CU): the data were not able to be sent. The manuals give exactly one fault cause for this code: 65 (= 41 hex) — the telegram type does not match the send list. The condition is signalled at the Terminal Board (TB). The G130/G150 and S120/S150 descriptions are worded identically and name the same single remedy, so everything below applies to both families.
Why it appears
- A DRIVE-CLiQ communication error has occurred from the DRIVE-CLiQ Hub Module in question to the Control Unit — 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 and note its coding: in r0949 or r2124 it appears as 0000yyxx hex, where yy is the component number of the DRIVE-CLiQ Hub Module that could not send and xx the error cause (65 = 41 hex, telegram type does not match send list).
- Carry out a POWER ON — switching the drive off and back on is the remedy the manuals give for this code.
Reading the message value
- The message value carries two placeholders: %1 = component number, %2 = fault cause.
- The manuals code the value as 0000yyxx hex and store it in the fault value r0949 and in the alarm value r2124.
- yy = component number.
- xx = error cause; the only error cause the manuals decode for this code is 65 (= 41 hex): telegram type does not match send list.
Parameters the manual names
- r0949 — fault value: read here the coded message of F36886 (0000yyxx hex) to identify the Hub Module component number and the error cause.
- r2124 — alarm value: holds the same 0000yyxx hex coding; the manuals name it directly next to the fault value as a place where the message value of this code is stored.
Acknowledging and restarting
The fault is acknowledged immediately. The manuals describe exactly one remedy: carry out a POWER ON, i.e. switch the drive off and back on again. No further repair steps are given for this code.
The same on every family
Every manual that describes F36886 gives it the same reaction, acknowledgement and message class.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | NONE | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Terminal Board (TB) | SINAMICS S120, S150 List Manual · p. 3257 |
| G130, G150 | NONE | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | Terminal Board (TB) | SINAMICS G130, G150 List Manual · p. 1919 |
The drives this code lives on
F36886 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 F36886 mean on a SINAMICS drive?
It reports a DRIVE-CLiQ communication error from the DRIVE-CLiQ Hub Module to the Control Unit: the data were not able to be sent. The only stated fault cause is 65 (= 41 hex), a telegram type that does not match the send list.
How do I clear F36886?
The manuals give a single remedy: carry out a POWER ON, switching the drive off and back on. The fault is acknowledged immediately, and no other repair steps are described.
Which component is reporting F36886?
Read the fault value r0949 (or the alarm value r2124): coded as 0000yyxx hex, the yy byte gives the component number and the xx byte the error cause. The condition is signalled at the Terminal Board (TB).
What is fault cause 65 in F36886?
It means the telegram type does not match the send list, printed as 65 (= 41 hex). It is the only fault cause the manuals list for this code.
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 F36xxx group · SINAMICS manuals · Siemens manuals