F31860 — Encoder 1 DRIVE-CLiQ (CU): Telegram error

This fault reports a DRIVE-CLiQ communication error on the connection from the Sensor Module involved for encoder 1 to the Control Unit. It concerns the telegram traffic between the encoder's Sensor Module and the Control Unit. Depending on how the drive is configured, the same condition can also be output as an alarm (A) or with no reaction (N) instead of as a fault.

• A DRIVE-CLiQ communication error has occurred on the connection from the Sensor Module (encoder 1) involved to the Control Unit.
• What exactly went wrong is reported as the fault cause in the message value — a checksum (CRC) error, a telegram whose length or type does not match the receive list, a mismatching power unit address, a supply voltage failure signalled by the component, or a receive telegram that arrived too early, the latter also in combination with the other causes.

1. Carry out a POWER ON — switch the drive off and on again.
2. Check the electrical cabinet design and the cable routing for EMC compliance.
3. Check the DRIVE-CLiQ wiring, for example for an interrupted cable or faulty contacts.

The drive stores the message value in r0949 (fault value) or r2124 (alarm value), coded as 0000yyxx hex: yy = component number, xx = error cause. The fault cause (xx) can take the following values:

• 1 (01 hex): checksum error (CRC error).
• 2 (02 hex): the telegram is shorter than specified in the length byte or in the receive list.
• 3 (03 hex): the 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 power unit in the telegram and in the receive list do not match.
• 9 (09 hex): the DRIVE-CLiQ communication from the component involved to the Control Unit signals that the supply voltage has failed.
• 16 (10 hex): the receive telegram is too early.
• 17 (11 hex): CRC error and the receive telegram is too early.
• 18 (12 hex): the telegram is shorter than specified in the length byte or in the receive list, and the receive telegram is too early.
• 19 (13 hex): the telegram is longer than specified in the length byte or in the receive list, and the receive telegram is too early.
• 20 (14 hex): the length of the receive telegram does not match the receive list and the receive telegram is too early.
• 21 (15 hex): the type of the receive telegram does not match the receive list and the receive telegram is too early.
• 22 (16 hex): the address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
• 25 (19 hex): the error bit in the receive telegram is set and the receive telegram is too early.

• r0949 (fault value) — read the coded message value of this fault here: component number and fault cause in 0000yyxx hex format.
• r2124 (alarm value) — carries the same coded value when the condition is output as an alarm.
• p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) — the remedy in one of the manuals additionally cross-refers to this threshold parameter for this telegram error.

Once the cause has been remedied, the fault is acknowledged immediately. The remedy itself begins with a POWER ON, i.e. switching the drive off and on again. Where the drive is configured to output the same condition only as an alarm or with no reaction, no acknowledgment is required.