F34837 — VSM DRIVE-CLiQ: Component fault

F34837 (manual title: VSM DRIVE-CLiQ: Component fault) is raised when a fault is detected on the DRIVE-CLiQ component concerned — the Voltage Sensing Module (VSM). The manual explicitly notes that faulty hardware cannot be excluded, so the module itself may be defective. Which of the possible errors actually occurred is coded in the message value as a component number and a fault cause (see Message value below). Other VSM messages described on their own pages include F34820, F34835, F34836, F34845, F34850, F34851, F34860 and F34806.

• A fault has been detected on the connected DRIVE-CLiQ component, the Voltage Sensing Module (VSM).
• Faulty hardware cannot be excluded — the VSM itself may be defective.
• The concrete reason is one of four telegram errors (header error, receive error or send error); the code stored in the message value identifies which one.

1. Check the DRIVE-CLiQ wiring — 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; acknowledge the changed topology with p9904.
4. Replace the component involved.

The drive reports «Component number: %1, fault cause: %2» and stores this information coded in r0949 (fault value) or r2124 (alarm value) in the form 0000yyxx hex: yy = component number, xx = error cause. The fault cause can therefore take these values:

• 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.

• r0949 (fault value) — holds the coded message value 0000yyxx hex for this fault: the component number and the fault cause.
• r2124 (alarm value) — the manual names it together with r0949 as the location of the same coded value.
• p9904 (topology comparison acknowledge differences) — belongs to the remedy step in which the connection is moved to another DRIVE-CLiQ socket: it acknowledges the resulting topology difference.

This fault is cleared with the drive's normal acknowledge function. The manual assigns immediate acknowledgement to the message, so once the cause has been remedied you can acknowledge the fault right away and then restart the drive.