F36885 — Hub DRIVE-CLiQ (CU): Cyclic data transfer error

F36885 is raised when the cyclic data transfer over DRIVE-CLiQ between a DRIVE-CLiQ Hub Module and the Control Unit (CU) fails: the two nodes no longer send and receive in synchronism. The message value names the hub concerned (component number, %1) and the reason for the breakdown (fault cause, %2); the drive stores this coded as 0000yyxx hex in r0949 and r2124. The neighbouring hub codes F36851, F36860, F36875, F36886, F36887, F36895, F36896 and F36899 are described on their own pages.

• DRIVE-CLiQ communication error from the DRIVE-CLiQ Hub Module in question to the Control Unit — the nodes do not send and receive in synchronism.
• The manual distinguishes several fault causes for this breakdown: a sign-of-life bit that is not set in the receive telegram, a cyclic telegram that never arrives, a timeout in the telegram receive list, a timeout in the telegram send list, and an error at the transition to cyclic operation. The codes and exact wording are decoded in the fault value section below.

1. Read the message value in r0949 (or in r2124) and decode it as 0000yyxx hex — yy identifies the hub (component number) whose transfer to the CU failed, xx gives the fault cause.
2. Check the supply voltage of the component involved.
3. Carry out a POWER ON.
4. Replace the component involved.

• The drive enters the component number into %1 and the fault cause into %2; in the message value (r0949/r2124) the information is coded as 0000yyxx hex, where yy is the component number and xx the error cause.
• Fault cause 26 (= 1A hex): Sign-of-life bit in the receive telegram not set and the receive telegram is too early.
• Fault cause 33 (= 21 hex): The cyclic telegram has not been received.
• Fault cause 34 (= 22 hex): Timeout in the telegram receive list.
• Fault cause 64 (= 40 hex): Timeout in the telegram send list.
• Fault cause 98 (= 62 hex): Error at the transition to cyclic operation.

• r0949 (fault value) — holds the coded message value of this fault; decode it as 0000yyxx hex to identify the hub involved and the fault cause.
• r2124 (alarm value) — the manual names this alarm value alongside r0949 as the location of the same coded value for this message.

The drive takes no automatic action in response to this fault, and the message can be acknowledged immediately. It only stays cleared once the hub and the CU again exchange cyclic telegrams in synchronism — if the fault returns, work through the checks above in order.