F35887 — TM DRIVE-CLiQ (CU): Component fault

F35887 is generated by the CU when a fault is detected on a connected DRIVE-CLiQ component — in this case a Terminal Module (TM). The G130/G150 and S120/S150 manuals describe the message identically and state: Faulty hardware cannot be excluded. Which Terminal Module is affected, and why, is coded in the message value (see the decoding below).

• A fault has been detected on the DRIVE-CLiQ component involved — the Terminal Module; the drive cannot exclude that the hardware itself is the origin.
• The coded fault cause identifies the trigger: an error in the telegram header, a receive or send error in which the telegram buffer memory contains an error, a response that arrived too late during runtime measurement, or a characteristic-data exchange that took too long — the numbers are listed in the decoding below.

1. Check the DRIVE-CLiQ wiring to the Terminal Module — interrupted cable, contacts and the like.
2. Check the electrical cabinet design and the cable routing for EMC compliance.
3. If required, use another DRIVE-CLiQ socket for the Terminal Module (p9904).
4. Replace the component involved.

The drive codes both placeholders of the message value (component number, fault cause) into a single word, stored as fault value in r0949 and as alarm value in r2124:

0000yyxx hex — yy = component number, xx = error cause.

• 32 (20 hex): error in the telegram header.
• 35 (23 hex): receive error — the telegram buffer memory contains an error.
• 66 (42 hex): send error — the telegram buffer memory contains an error.
• 67 (43 hex): send error — the telegram buffer memory contains an error.
• 96 (60 hex): response received too late during runtime measurement.
• 97 (61 hex): time taken to exchange characteristic data too long.

• r0949 (fault value) — read the coded message value of F35887 here: component number (yy) and fault cause (xx).
• r2124 (alarm value) — named by the manual alongside r0949 as the place where the same coded message value is stored.
• p9904 (topology comparison acknowledge differences) — applies when, per the remedy, the Terminal Module is moved to another DRIVE-CLiQ socket.

The drive is brought to a standstill by the reaction (a ramp-down stop; in the alternative configuration the motor coasts down) and this fault must be acknowledged immediately before a restart is possible. Remedy the cause first, then acknowledge the fault; the remedy lists no further reset steps beyond acknowledgement and the possible socket change via p9904.