F40860 — CX32 DRIVE-CLiQ (CU): Telegram error

F40860 reports a DRIVE-CLiQ communications error on the path from the CX32 controller extension involved to the Control Unit: a telegram received on this path was corrupted or did not match what the receive list specifies. The fault is assigned to the DRIVE-CLiQ Hub Module (Hub) component. Because the reaction is a coast down (OFF2), the drive stops and will not restart until the fault has been acknowledged. Which defect the telegram actually had is coded as the fault cause inside the message value, so reading the value out is the first diagnostic step. Other CX32 DRIVE-CLiQ codes such as F40851, F40845, F40837 or F40885 are separate entries on this site and are not covered here.

• A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit — the telegram arriving from the CX32 was defective.
• The manual names no component-level root causes beyond this communication error itself; the kind of telegram defect (checksum, length, type, address, error bit set, or a telegram that arrived too early) is told by the fault cause number in the message value.
• For the hardware side, the remedy points to EMC aspects of the electrical cabinet design and cable routing and to the DRIVE-CLiQ wiring (interrupted cable, contacts, ...) — see the checks below.

1. Carry out a POWER ON (switch-off/switch-on) of the drive.
2. Check the electrical cabinet design and cable routing for EMC compliance.
3. Check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).

The remedy additionally refers to p9915 (DRIVE-CLiQ data transfer error shutdown threshold master); see the parameter notes below.

The drive outputs the message value as Component number: %1, fault cause: %2. It is coded in r0949 (fault value) or r2124 (alarm value) as 0000yyxx hex, where yy is the component number and xx the fault cause. The fault causes printed in the manual:

• 1 (= 01 hex): Checksum error (CRC error).
• 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list.
• 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list.
• 4 (= 04 hex): The length of the receive telegram does not match the receive list.
• 5 (= 05 hex): The type of the receive telegram does not match the receive list.
• 6 (= 06 hex): The address of the power unit in the telegram and in the receive list do not match.
• 9 (= 09 hex): The error bit in the receive telegram is set.
• 16 (= 10 hex): The receive telegram is too early.
• 17 (= 11 hex): CRC error and the receive telegram is too early.
• 18 (= 12 hex): The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
• 19 (= 13 hex): The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
• 20 (= 14 hex): The length of the receive telegram does not match the receive list and the receive telegram is too early.
• 21 (= 15 hex): The type of the receive telegram does not match the receive list and the receive telegram is too early.
• 22 (= 16 hex): The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
• 25 (= 19 hex): The error bit in the receive telegram is set and the receive telegram is too early.

The manual for the G130/G150 groups the conditions of causes 20, 21 and 22 into one line under 20 (= 14 hex); the individual conditions are the same.

• r0949 (fault value) — read the coded message value of this fault here: 0000yyxx hex, with the component number (yy) and the fault cause (xx) of the defective CX32 telegram.
• r2124 (alarm value) — named by the manual next to r0949 as the location where the same coded message value is stored.
• p9915 (DRIVE-CLiQ data transfer error shutdown threshold master / DQ fault master) — the remedy for this fault refers to this parameter; the entry itself gives no further step for it.

The fault must be acknowledged immediately: the drive has coasted down and only accepts a new start after acknowledgement. The prescribed first remedy is a POWER ON — switch the drive off and on again. If F40860 comes back, work through the EMC and DRIVE-CLiQ wiring checks above before attempting another start.