F31820 — Encoder 1 DRIVE-CLiQ: Telegram error

F31820 reports a DRIVE-CLiQ telegram error for encoder 1: a telegram exchanged between the Control Unit and the encoder concerned violated the expected format, content or timing. The exact defect is coded in the message value (r0949/r2124), which the drive fills with the component number and the fault cause. Depending on how the drive is configured, the same condition can also be output as an alarm or as a message without any reaction instead of a fault.

• A DRIVE-CLiQ communication error has occurred on the path from the Control Unit to the encoder concerned (encoder 1).
• Which specific fault cause lies behind the error — from a checksum error (CRC error) to a telegram of the wrong length, type or address, a missing or unexpected SYNC telegram, a set error bit, or a telegram that arrived too early — is read from the message value; the full decoding is given under fault value below.

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

• The message value contains the component number and the fault cause. It is stored in r0949 (fault value) or r2124 (alarm value), coded as 0000yyxx hex: yy = component number, xx = error cause.
• Fault cause 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 component in the telegram and in the receive list do not match.
• 7 (= 07 hex): a SYNC telegram is expected - but the received telegram is not a SYNC telegram.
• 8 (= 08 hex): no SYNC telegram is expected - but the received telegram is one.
• 9 (= 09 hex): the error bit in the receive telegram is set.
• 16 (= 10 hex): the receive telegram is too early.

• r0949 (fault value): read the component number and the fault cause of this fault here, coded as 0000yyxx hex.
• r2124 (alarm value): holds the same coding when the condition is signalled as an alarm.
• p0491 (motor encoder fault response ENCODER): sets the drive's response to an encoder fault; the manual cross-references it for this fault.
• p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave): on the G130 and G150, the remedy for this fault points to this threshold in connection with DRIVE-CLiQ data transfer errors.

After the cause has been corrected, acknowledge the fault immediately so the drive can be restarted. The remedy itself begins with a POWER ON (switch-off/switch-on): switch the supply off and on again before acknowledging the fault.