F35837 — PTM DRIVE-CLiQ: Component fault

F35837 is titled PTM DRIVE-CLiQ: Component fault. The drive raises it when a fault has been detected on the DRIVE-CLiQ component concerned — a Terminal Module (TM) — adding that faulty hardware cannot be excluded. The G130/G150 and S120/S150 List Manuals describe the fault identically for the TM; the message reports the component number and the fault cause in its message value, which the drive stores as fault value (r0949) or alarm value (r2124).

• A fault has been detected on the DRIVE-CLiQ component concerned.
• The manuals state explicitly that faulty hardware cannot be excluded.
• Which fault cause applies — a telegram header error or a receive/send error in the telegram buffer memory — is read from the message value (see the decoding below).

1. Check the DRIVE-CLiQ wiring, e.g. for an interrupted cable or poor contacts.
2. Check the electrical cabinet design and the cable routing for EMC compliance.
3. If required, use another DRIVE-CLiQ socket (p9904).
4. Replace the component involved.

• The drive writes two pieces of information into the message value: the component number and the fault cause.
• The information is coded as 0000yyxx hex and is stored in r0949 as fault value or in r2124 as alarm value: yy = component number, xx = error cause.
• Fault cause 32 (= 20 hex): error in the telegram header.
• Fault cause 35 (= 23 hex): receive error — the telegram buffer memory contains an error.
• Fault cause 66 (= 42 hex): send error — the telegram buffer memory contains an error.
• Fault cause 67 (= 43 hex): send error — the telegram buffer memory contains an error.

• r0949 — read the coded message value of this fault here (fault value); it contains the component number and the fault cause.
• r2124 — the same coded message value is also stored here (alarm value).
• p9904 — the remedy for this fault points to this parameter when the DRIVE-CLiQ connection is to be moved to another socket; it covers acknowledging the topology comparison differences.

Rectify the cause first, then acknowledge the fault — the manuals specify immediate acknowledgement — and restart the drive. The fault response is an OFF1, so the drive is ready for the next start as soon as the fault has been acknowledged and the cause removed.