F40837 — CX32 DRIVE-CLiQ: Component fault

Fault F40837 is reported by the CX32 DRIVE-CLiQ Hub Module when a fault is detected on the DRIVE-CLiQ component concerned. The manual states plainly: Faulty hardware cannot be excluded. The component number and the fault cause are entered into the message value, so reading that value tells you which hub component is affected and which of the four known conditions triggered the message.

• A fault has been detected on the DRIVE-CLiQ component concerned; faulty hardware cannot be excluded.
• The manual distinguishes four fault causes for this component. Which one applies is recorded as the error cause in the message value — the decoding is listed below.

1. Check the DRIVE-CLiQ wiring — interrupted cable, contacts and the like.
2. Check the electrical cabinet design and the cable routing for EMC compliance.
3. If required, use another DRIVE-CLiQ socket — the manual points to p9904 here.
4. Replace the component involved.

The drive puts the component number and the fault cause into the message value. The manual codes the message value (read in r0949 or r2124) as 0000yyxx hex, where yy is the component number and xx is the error cause:

• xx = 32 (= 20 hex): error in the telegram header.
• xx = 35 (= 23 hex): receive error — the telegram buffer memory contains an error.
• xx = 66 (= 42 hex): send error — the telegram buffer memory contains an error.
• xx = 67 (= 43 hex): send error — the telegram buffer memory contains an error.

• r0949 (fault value): read the coded message value 0000yyxx hex here to identify the component number and the fault cause of F40837.
• r2124 (alarm value): named by the manual alongside r0949 as the location of the coded message value.
• p9904 (topology comparison acknowledge differences): named by the remedy when it proposes using another DRIVE-CLiQ socket.

The OFF2 reaction means the drive coasts down as soon as the fault occurs. Acknowledge the fault immediately; the drive must be acknowledged before it will start again.