F30860 — Power unit DRIVE-CLiQ (CU): Telegram error

F30860 reports a DRIVE-CLiQ telegram error between a power unit and the involved Control Unit: a telegram received over DRIVE-CLiQ was unusable, so the drive coasts to a stop and must be acknowledged before it can restart. The message value tells you which component is affected and what exactly went wrong.

• A DRIVE-CLiQ communication error occurred between the power unit and the Control Unit involved — the received telegram was corrupt, had the wrong structure or address, or arrived outside its expected time window. Which of these applies is shown by the fault cause in the message value (decoding below).

1. Carry out a POWER ON — switch the drive off and then on again.
2. Check the electrical cabinet's design and how the cables are routed, for EMC compliance.
3. Check the DRIVE-CLiQ wiring — look for an interrupted cable and poor contacts.

The manual fills %1 with the component number and %2 with the fault cause. In r0949 or r2124 the information is coded as 0000yyxx hex, where yy is the component number and xx is the fault cause. The manual decodes the fault cause as follows:

• 1 (01 hex): the checksum of the received data is wrong (CRC error).
• 2 (02 hex): the received telegram is shorter than its length byte or the receive list allows.
• 3 (03 hex): the received telegram is longer than its length byte or the receive list allows.
• 4 (04 hex): the length of the received telegram deviates from the receive list.
• 5 (05 hex): the type of the received telegram deviates from the receive list.
• 6 (06 hex): the power unit's address in the received telegram does not match the receive list.
• 9 (09 hex): the DRIVE-CLiQ communication from the component involved tells the Control Unit that its supply voltage has failed.
• 16 (10 hex): the receive telegram arrived too early.
• 17 (11 hex): a CRC error (as in cause 1) combined with a receive telegram that arrived too early.
• 18 (12 hex): a telegram that is too short (cause 2) and arrived too early.
• 19 (13 hex): a telegram that is too long (cause 3) and arrived too early.
• 20 (14 hex): a length mismatch against the receive list (cause 4) and the telegram arrived too early.
• 21 (15 hex): a type mismatch against the receive list (cause 5) and the telegram arrived too early.
• 22 (16 hex): an address mismatch (cause 6) and the telegram arrived too early.
• 25 (19 hex): the error bit is set in the received telegram and it arrived too early.

• r0949 — the fault value: read the coded component number and fault cause of this fault here (0000yyxx hex).
• r2124 — the alarm value: it carries the same coding of component number and fault cause for this message.
• p9915 — the DRIVE-CLiQ data transfer error shutdown threshold (master); the manual refers to this threshold in connection with this fault.

The fault must be acknowledged before the drive will restart. The manual's own remedy is a POWER ON — switch the drive off and back on again. If the fault returns, work through the checks above (cabinet design and cable routing, DRIVE-CLiQ wiring) before restarting.