F40887 — CX32 DRIVE-CLiQ (CU): Component fault

F40887 is raised by the Control Unit (CU) when it detects a fault on the DRIVE-CLiQ component concerned — for this code that component is the CX32 DRIVE-CLiQ Hub Module (Hub). The manual adds Faulty hardware cannot be excluded, so a defective module is a real possibility. The exact fault cause is coded in the message value. The description is identical for G130/G150 and for S120/S150. The drive coasts down when the fault trips and must be acknowledged before it will start again.

• The Control Unit detected a fault on the DRIVE-CLiQ component concerned, the CX32 DRIVE-CLiQ Hub Module; faulty hardware cannot be excluded.
• Which condition actually tripped the fault is coded in the message value as the fault cause — the manual lists six possible values, from an error in the telegram header (32) to a time taken to exchange characteristic data that was too long (97). The decoding is given in the fault value section below.

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

The message value carries two items: the component number (%1) and the fault cause (%2). The drive codes both in r0949 or r2124 as 0000yyxx hex, where yy = component number and xx = error cause. The fault cause values the manual lists are:

• 32 (= 20 hex): error in the telegram header.
• 35 (= 23 hex): receive error — the telegram buffer memory contains an error.
• 66 (= 42 hex): send error — the telegram buffer memory contains an error.
• 67 (= 43 hex): send error — the telegram buffer memory contains an error.
• 96 (= 60 hex): response received too late during runtime measurement.
• 97 (= 61 hex): time taken to exchange characteristic data too long.

• r0949 (fault value) — read the coded message value 0000yyxx hex here to see which CX32 hub component reported the fault and which of the six fault causes tripped it.
• r2124 (alarm value) — the manual names this parameter alongside r0949 as a place where the same coded message value is stored.
• p9904 (topology comparison acknowledge differences) — the parameter the manual references in the remedy when it says to use another DRIVE-CLiQ socket.

The drive coasts down when this fault trips and must be acknowledged before it will start again. Work through the checks above first — because faulty hardware cannot be excluded, the manual's last remedy step is to replace the component involved. Once the cause has been eliminated, acknowledge the fault on the operator panel or in the commissioning tool and restart the drive.