Breaking

Friday, March 12, 2021

SIEMENS VFD FAULTS CODE LIST PART-2

In this article we are going to discuss about siemens v20 vfd drive fault Cause and Remedy for this fault codes ( F41, F51 , F52 , F60 , F61 , F62 , F63 , F64 , F71 , F72 )




Fault Vfd Drive



F41 FAULT:

Motor data identification failure

Motor

CAUSE :
  • Motor data identification failed.
  • r0949 = 0: No load applied
  • r0949 = 1: Current limit level
  • reached during identification.
  • r0949 = 2: Identified stator resistance less than 0.1% or greaterthan 100%.
  • r0949 = 30: Current controller at voltage limit
  • r0949 = 40: Inconsistency of identified dataset, at least one identificationfailed
  • Percentage values based on the impedance Zb = Vmot,nom / sqrt(3) / Imot,nom

REMEDY :

Check the following:
  • r0949 = 0: is the motor connected to the inverter?
  • r0949 = 1 - 49: are the motor data in P0304 - P0311 correct?
  • Check what type of motor wiring is required (star, delta).

F51FAULT:

 Parameter EEPROM fault

EEPROM

CAUSE :
  • Read or write failure while access to EEPROM. 
  • The EEPROM being full, too many parameters have been changed.
  • This can also be caused by

REMEDY :

  • Must be power-cycled to cancel this bug as some parameters may not be read correct.
  • Factory reset and new parameterization, if power- cycle does not remove fault.
  • Change some parameters back to default values if the EEPROM is full, then power-cycle.
  • Change inverter.

Note:

  • r0949 = 1: EEPROM full r0949 = 1000 + block No: reading data block failed
  • r0949 = 2000 + block No: reading data block timeout
  • r0949 = 3000 + block No: reading data block CRC failed
  • r0949 = 4000 + block No: writing data block failed
  • r0949 = 5000 + block No: writing data block timeout
  • r0949 = 6000 + block No: writing data block verify failed
  • r0949 = 7000 + block No: reading data block at wrong time
  • r0949 = 8000 + block No: writing data block at wrong time
  • r0949 = 9000 + block No: factory reset did not work because restart or power failure

F52FAULT:

 Inverter software fault

Inverter software fault

CAUSE :

Read failure for inverter information or invalid data.

REMEDY :

Note:

  • r0949 = 1: Failed reading inverter identity
  • r0949 = 2: Inverter identity wrong
  • r0949 = 3: Failed reading inverter version
  • r0949 = 4: Inverter version wrong
  • r0949 = 5: Start of Part 1 inverter data wrong
  • r0949 = 6: Inverter number of temperature sensor wrong
  • r0949 = 7: Inverter number of application wrong
  • r0949 = 8: Start of Part 3 inverter data wrong
  • r0949 = 9: Reading inverter data string wrong
  • r0949 = 10: Inverter CRC failed
  • r0949 = 11: Inverter is blank
  • r0949 = 15: Failed CRC of inverter block 0
  • r0949 = 16: Failed CRC of inverter block 1
  • r0949 = 17: Failed CRC of inverter block 2
  • r0949 = 20: Inverter invalid
  • r0949 = 30: Directory size wrong
  • r0949 = 31: Directory ID wrong
  • r0949 = 32: Invalid block
  • r0949 = 33: File size wrong
  • r0949 = 34: Data section size wrong
  • r0949 = 35: Block section size wrong
Note:
  • r0949 = 36: RAM size exceeded
  • r0949 = 37: Parameter size wrong
  • r0949 = 38: Device header wrong
  • r0949 = 39: Invalid file pointer
  • r0949 = 40: Scaling block version wrong
  • r0949 = 41: Calibration block version wrong
  • r0949 = 50: Wrong serial number format
  • r0949 = 51: Wrong serial number format start
  • r0949 = 52: Wrong serial number format end
  • r0949 = 53: Wrong serial number format month
  • r0949 = 54: Wrong serial number format day
  • r0949 = 1000 + addr: Inverter read data failed
  • r0949 = 2000 + addr: Inverter write data failed
  • r0949 = 3000 + addr: Inverter read data wrong time
  • r0949 = 4000 + addr: Inverter write data wrong time
  • r0949 = 5000 + addr: Inverter read data invalid
  • r0949 = 6000 + addr: Inverter write data invalid
  • Power-cycle inverter
  • Contact service department or change inverter

F60FAULT:

Asic timeout

CAUSE :

Internal communications failure.

REMEDY :

  • Check inverter.
  • Fault appears sporadically:
Note:
  • r0949 = 0: Hardware reported link fail
  • r0949 = 1: Software reported link fail
  • r0949 = 6: Feedback is not disabled for reading inverter data
  • r0949 = 7: During inverter download, message didn't transmit to disable feedback
  • Communication failure due to EMC problems
  • Check - and if necessary - improve EMC
  • Use EMC filter

F61 FAULT:

MMC/SD card parameter cloning failed


MMC/SD card 

CAUSE :

Parameter cloning failed.

  • r0949 = 0: MMC/SD card not connected or incorrect card type or the card failed to initialize for automatic cloning
  • r0949 = 1: Inverter data cannot write to the card.
  • r0949 = 2: Parameter cloning file not available
  • r0949 = 3: The MMC/SD card cannot read the file
  • r0949 = 4: Reading data from the clone file failed (e.g., reading failed, data or checksum wrong) 

REMEDY :

  • r0949 = 0: Use an MMC/SD card with FAT16 or FAT32 format , or fit an MMC/SD card to the inverter.
  • r0949 = 1: Check the MMC/SD card (e.g., is the card memory full?) - format the card again to FAT16 or FAT32.
  • r0949 = 2: Put the correct named file in the correct directory /USER/SINAMICS/DATA.
  • r0949 = 3: Make sure file is accessible - recreate file if possible.
  • r0949 = 4: File has been changed -recreate file. 


F62 FAULT:

Parameter cloning contents invalid
Parameter cloning contents invalid
CAUSE :

File exists but the contents are not valid control word corruption.

REMEDY :

Recopy and ensure operation completes.


F63 FAULT:

Parameter cloning contents incompatible.

CAUSE :

File exists but was not the correct inverter type.

REMEDY :

Ensure clone from compatible inverter type.


F64 FAULT:

Inverter attempted to do an automatic clone during startup


CAUSE :

No Clone00.bin file in the correct directory /USER/SINAMICS/DATA.

REMEDY :

If an automatic clone is required:
  • Insert the MMC/SD card with correct file and power-cycle.
If no automatic clone is required:
  • Remove the card if not needed and power cycle.
  • Reset P-8458 = 0 and power-cycle.
Note:
  • Fault can only be cleared by a power-cycle.


F71 FAULT:

USS setpoint fault


CAUSE :

No setpoint values from USS during telegram off time.

REMEDY :

Check USS master


F72 FAULT:

USS/MODBUS setpoint fault


CAUSE :

No setpoint values from USS/MODBUS during telegram off time.


REMEDY :

Check USS/MODBUS master

No comments:

Post a Comment