F36860 — Hub DRIVE-CLiQ (CU): Telegram error

F36860 reports that a cyclic telegram sent from a DRIVE-CLiQ Hub Module to the Control Unit arrived in a defective state. The defect can be a failed checksum (CRC error), a telegram that is too short or too long against the length byte or the receive list, a length or type that does not match the receive list, a power unit address that differs between telegram and receive list, a telegram that arrived too early, or the report that a component's supply voltage has failed. The code alone does not tell you which of these occurred: the drive stores the component number and the exact fault cause in the message value, so read them from r0949 (or r2124) before working on the line.

• The cause given is a DRIVE-CLiQ communication error on the connection from the Hub Module concerned to the Control Unit — a disturbance on this line corrupts the cyclic telegrams or their timing.

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

The drive codes both pieces of information into one message value, which it stores in r0949/r2124: 0000yyxx hex: yy = component number, xx = error cause

• Fault causes 1 to 6 (= 01 to 06 hex) characterise the telegram defect itself: checksum error (CRC error), a telegram shorter or longer than specified in the length byte or the receive list, a length or type that does not match the receive list, or a power unit address that does not match between telegram and receive list.
• Fault cause 9 (= 09 hex): the DRIVE-CLiQ communication from the component involved signals to the Control Unit that its supply voltage has failed.
• Fault causes 16 to 22 (= 10 to 16 hex) mean that the receive telegram arrived too early — on its own or combined with the checksum, length, type or address defects above.
• Fault cause 25 (= 19 hex): the error bit in the receive telegram is set and the telegram arrived too early.

• r0949 — fault value: read the coded message value of this fault here; one part names the affected component, the other the fault cause.
• r2124 — alarm value: the manual names this parameter alongside r0949 as a second location where the coded message value is stored.

Acknowledge the fault as soon as it appears, at the operator panel or in the commissioning tool. Since the first remedy step is a POWER ON (switch-off/switch-on), the normal route back to operation is: remove the cause on the DRIVE-CLiQ line, power the drive down and up again, then acknowledge the pending message so it is deleted from the fault memory.