F35820 — TM DRIVE-CLiQ: Telegram error

F35820 is raised when a DRIVE-CLiQ telegram error occurs on the connection from the Control Unit to the Terminal Module (TM) involved. The drive stores which component is affected and which telegram check failed in the message value, so the value read out together with the fault tells you exactly where the communication broke down. The component concerned is always a Terminal Module (TM).

• A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved.
• The specific telegram defect is stored as the fault cause in the message value: it ranges from a checksum (CRC) error and telegram length, type or address mismatches against the receive list to a missing or unexpected SYNC telegram, a set error bit in the receive telegram, or a receive telegram that arrives too early.

1. Read the component number and the fault cause from the message value (r0949, coded 0000yyxx hex) — this identifies the Terminal Module concerned and the type of telegram error.
2. Carry out a POWER ON (switch off/on).
3. Check the electrical cabinet design and cable routing for EMC compliance.
4. Check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).

The message value consists of two placeholders: %1 is the component number and %2 is the fault cause. The manual codes both values in r0949/r2124 as 0000yyxx hex, where yy is the component number and xx the error cause. The fault cause (xx) decodes as follows:

• 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): holds the coded message value of this fault, 0000yyxx hex — read the component number and fault cause from here.
• r2124 (alarm value): named alongside r0949 by the manual as a location holding the same coded value 0000yyxx hex.
• p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave): the remedy for this fault points to this parameter for further information.

The fault has to be acknowledged before the drive will restart, and the acknowledgement is required immediately. Because the reaction is OFF1 (OFF2), the drive stops when the fault trips. Once the cause has been eliminated, acknowledge the fault and restart the drive; if the fault returns, begin again with a POWER ON (switch off/on).