F34820 — VSM DRIVE-CLiQ: Telegram error

F34820 reports a DRIVE-CLiQ telegram error on the connection from the Control Unit to the Voltage Sensing Module (VSM) involved. The manuals for the G130/G150 and the S120/S150 describe this fault identically; in every case the affected component is the VSM. The fault itself does not name the telegram problem directly — the message value stored with it tells you the component number and the exact telegram fault cause, which you decode as shown below.

• A DRIVE-CLiQ communications error has occurred on the path from the Control Unit to the Voltage Sensing Module (VSM) involved.
• Both manual families print the same cause for this fault; the nature of the telegram problem — a checksum (CRC) error, a telegram that is too short or too long against the length byte or the receive list, a mismatch with the receive list, a missing or unexpected SYNC telegram, a set error bit, or a receive telegram that arrived too early — is read from the fault cause in the message value.

1. Read the fault cause before clearing anything: in the message value (r0949) the pair 0000yyxx hex gives yy as the component number and xx as the fault cause, so you know which telegram problem the drive registered and on which component.
2. Carry out a POWER ON (switch-off/switch-on).
3. Check the electrical cabinet design and cable routing for EMC compliance.
4. Check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).

• The drive raises the fault with the message value "Component number: %1, fault cause: %2". The individual information is coded in the message value (r0949/r2124) as 0000yyxx hex: yy = component number, xx = error 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 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) — here the drive stores the message value of this fault as 0000yyxx hex; read yy as the component number and xx as the fault cause for F34820.
• r2124 (alarm value) — the manual names it alongside r0949 as the register in which the same 0000yyxx hex coding of component number and fault cause is read.
• p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave / DQ fault slave) — the manual for the G130/G150 lists this parameter as a cross-reference under this fault's remedy.

The manuals require this fault to be acknowledged immediately before the drive will run again. The stated remedy starts with a POWER ON (switch-off/switch-on); after the DRIVE-CLiQ wiring and the EMC environment have been checked and the cause removed, acknowledge the fault and restart the drive.