F32835 — Encoder 2 DRIVE-CLiQ: Cyclic data transfer error

F32835 is raised when the cyclic data exchange over DRIVE-CLiQ between the Control Unit and encoder 2 fails: the nodes no longer send and receive in synchronism, so the telegrams of the Sensor Module Encoder 2 stop arriving correctly. Depending on how the drive is configured, the same condition can also be signalled as an alarm or without any reaction instead of a fault.

• A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned — the nodes do not send and receive in synchronism.
• Which failure pattern actually occurred is identified by the fault cause that the drive writes into the message value (see the decoding below).

1. Read the fault cause from the message value in r0949 — the decoding below shows whether the cyclic telegram was not received or a timeout occurred in the receive or send list.
2. Carry out a POWER ON and return the drive to operation.
3. If F32835 reappears, replace the component involved.

The drive writes two pieces of information into the message value: the component number (%1) and the fault cause (%2). The value is coded in r0949 or r2124 as 0000yyxx hex, where yy is the component number and xx the error cause. The manual decodes the fault cause as follows:

• 33 (= 21 hex): the cyclic telegram has not been received.
• 34 (= 22 hex): timeout in the telegram receive list.
• 64 (= 40 hex): timeout in the telegram send list.

• r0949 — fault value: read the coded message value (component number and fault cause) here when F32835 comes as a fault.
• r2124 — alarm value: holds the same coded value when the condition is signalled as an alarm.
• p9916 — DRIVE-CLiQ data transfer error shutdown threshold slave: on G130 and G150 the manual cross-references this parameter in connection with F32835.

Acknowledge F32835 immediately. The manual's remedy is a POWER ON, after which the drive is returned to operation; if the fault occurs again, the component involved must be replaced.