What it means
F40836 signals a send error on the internal DRIVE-CLiQ communication of the CX32: a DRIVE-CLiQ communications error occurred on the path from the Control Unit to the controller extension involved, so the data were not able to be sent. The fault is assigned to the DRIVE-CLiQ Hub Module (Hub). While this fault is active the drive coasts down and must be acknowledged before it will start again.
Why it appears
- A DRIVE-CLiQ communications error occurred from the Control Unit to the controller extension 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: it is coded 0000yyxx hex, where yy gives the component number and xx the error cause. An error cause of 41 hex (= 65) means that the telegram type does not match the send list.
- Carry out a POWER ON — switch the power supply off and then switch it on again.
Reading the message value
- The message value holds two items: the component number and the fault cause.
- The manual documents the coding in r0949/r2124 as 0000yyxx hex: yy = component number, xx = error cause.
- For this fault the error cause is 65 (= 41 hex): telegram type does not match send list.
Parameters the manual names
- r0949 — fault value: read the coded message value of F40836 here; the pattern 0000yyxx hex gives the component number (yy) and the error cause (xx).
- r2124 — alarm value: the manual names this parameter alongside r0949 as the place where the same coded message value (0000yyxx hex) is stored.
Acknowledging and restarting
The drive coasts down with this fault and must be acknowledged immediately before it will restart. The manual's remedy is: Carry out a POWER ON (switch-off/switch-on).
If the fault returns after switching on again, the message value in r0949 again names the component number and the fault cause.
The same on every family
Every manual that describes F40836 gives it the same reaction, acknowledgement and message class.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | OFF2 | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | DRIVE-CLiQ Hub Module (Hub) | SINAMICS S120, S150 List Manual · p. 3283 |
| G130, G150 | OFF2 | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | DRIVE-CLiQ Hub Module (Hub) | SINAMICS G130, G150 List Manual · p. 1926 |
The drives this code lives on
F40836 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 F40836 mean on a SINAMICS G130, G150, S120 or S150?
It is a CX32 DRIVE-CLiQ send error: a DRIVE-CLiQ communications error occurred from the Control Unit to the controller extension involved and the data were not able to be sent. The fault is assigned to the DRIVE-CLiQ Hub Module (Hub).
How do I reset fault F40836?
The manual's remedy is a POWER ON: switch the power supply off and switch it on again. The drive coasts down with this fault and must be acknowledged before it will start again.
What is fault cause 65 in F40836?
Fault cause 65 (= 41 hex) means that the telegram type does not match the send list. The coded message value 0000yyxx hex shows the component number (yy) and the error cause (xx).
Where can I read the component number and error cause of F40836?
In the message value, which you read in r0949 (fault value); the manual gives the same coding for r2124 (alarm value). It is coded 0000yyxx hex: yy = component number, xx = error cause.
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 F40xxx group · SINAMICS manuals · Siemens manuals