F35860 — TM DRIVE-CLiQ (CU): Telegram error

F35860 — TM DRIVE-CLiQ (CU): Telegram error is raised when a DRIVE-CLiQ communication error occurs on the path from the Terminal Module (TM) involved to the Control Unit. The message value tells you which Terminal Module is affected and why the telegram failed: it contains a component number and a fault cause, so two drives showing F35860 have not necessarily failed for the same reason. The G130, G150, S120 and S150 manuals describe this fault identically. While the fault is active the reaction stops the drive (OFF1, alternatively OFF2).

• A DRIVE-CLiQ communication error has occurred from the Terminal Module (TM) involved to the Control Unit.
• Which telegram problem triggered the fault is not fixed — it is coded as the fault cause in the message value. The possible causes are the ones decoded below (checksum/CRC error, telegram too short or too long, length or type mismatch against the receive list, power-unit address mismatch, failed supply voltage, receive telegram too early — several also in combination).

1. Read the component number and the fault cause from the message value (fault value r0949 or alarm value r2124, coded 0000yyxx hex) so you know which component and which telegram problem are involved.
2. Carry out a POWER ON (switch-off/switch-on).
3. Check the electrical cabinet design and the cable routing for EMC compliance.
4. Check the DRIVE-CLiQ wiring — interrupted cable, contacts, ... .

• The drive puts the component number in %1 and the fault cause in %2. It is coded in the message value (r0949/r2124): 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 power unit in the telegram and in the receive list do not match.
• 9 (= 09 hex): the DRIVE-CLiQ communication from the DRIVE-CLiQ 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 — 0000yyxx hex gives the component number (yy) and the fault cause (xx).
• r2124 (alarm value): the manual names this parameter alongside r0949 as the location of the same coded message value (0000yyxx hex) for this message.
• p9915 (DRIVE-CLiQ data transfer error shutdown threshold master): the G130/G150 remedy cross-refers to this parameter ('See also'); its printed function is the DRIVE-CLiQ data transfer error shutdown threshold master.

The fault is one that is acknowledged immediately (IMMEDIATELY): once the cause has been corrected, the message can be cleared directly. Because the first remedy step is a POWER ON, the practical sequence is to correct or exclude the cause, switch the supply off and on again, and then restart the drive.