What it means
F40835 is raised when a DRIVE-CLiQ communications error occurs from the Control Unit to the CX32 controller extension involved: the nodes no longer send and receive in synchronism, so the cyclic data exchange breaks down. The message value tells you which component is affected and why the transfer failed. The G130/G150 and the S120/S150 manuals describe this fault with identical wording.
Why it appears
- A DRIVE-CLiQ communication error has occurred from the Control Unit to the CX32 controller extension involved.
- The nodes do not send and receive in synchronism, so the cyclic data transfer fails.
What to check
- Read the message value in r0949 (or r2124) and decode it as 0000yyxx hex: yy identifies the component, xx the fault cause (33, 34 or 64).
- Carry out a POWER ON (switch-off/switch-on).
- If the fault comes back, replace the component involved.
Reading the message value
- The drive enters the component number into %1 and the fault cause into %2 of the message value.
- Coding in r0949/r2124: 0000yyxx hex, where yy = component number and xx = error cause.
- 33 (= 21 hex): The cyclic telegram has not been received.
- 34 (= 22 hex): Timeout in the telegram receive list.
- 64 (= 40 hex): Timeout in the telegram send list.
Parameters the manual names
- r0949 (fault value) — where the drive stores the message value of this fault; decode it as 0000yyxx hex to get component number and fault cause.
- r2124 (alarm value) — named by the manual alongside r0949 as the register in which the coded message value of this fault can be read.
- p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave / DQ fault slave) — the manual points to this parameter under "See also" in the remedy for this fault.
Acknowledging and restarting
The drive coasts down when this fault trips, and it must be acknowledged immediately before it will run again. Acknowledging alone does not remove the underlying communication problem: the manual's remedy is a POWER ON (switch-off/switch-on), and if the fault persists afterwards, the component involved has to be replaced.
The same on every family
Every manual that describes F40835 gives it the same reaction, acknowledgement and message class.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| G130, G150 | OFF2 | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | DRIVE-CLiQ Hub Module (Hub) | SINAMICS G130, G150 List Manual · p. 1926 |
| S120, S150 | OFF2 | IMMEDIATELY | Internal (DRIVE-CLiQ) communication error (12) | DRIVE-CLiQ Hub Module (Hub) | SINAMICS S120, S150 List Manual · p. 3283 |
The drives this code lives on
F40835 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 F40835 in SINAMICS mean?
It reports a DRIVE-CLiQ cyclic data transfer error: communication from the Control Unit to the CX32 controller extension involved has failed because the nodes no longer send and receive in synchronism.
How can I see which component triggered F40835?
Read the message value in r0949 (or r2124): it is coded 0000yyxx hex, where yy is the component number and xx is the fault cause (33, 34 or 64).
How do I clear fault F40835?
Acknowledge the fault immediately after the drive coasts down, then carry out a POWER ON (switch-off/switch-on). If the fault returns, the manual says to replace the component involved.
What do the fault causes 33, 34 and 64 of F40835 mean?
33 (= 21 hex) means the cyclic telegram has not been received, 34 (= 22 hex) a timeout in the telegram receive list, and 64 (= 40 hex) a timeout in the telegram send list.
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