List of Fault and Alarm messages
Faults and Alarms
3-387
© Siemens AG 2007 All Rights Reserved
SINAMICS G120 Control Units CU240S, Edition 05/2007
F00061 Par Cl. MMC-PS not fitted Fault
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Cause: MMC-PS Cloning Failed.
• r0949 = 0: MMC-PS Not Connected or incorrect MMC-PS Type
• r0949 = 1: MMC-PS cannot write to MMC
• r0949 = 2: MMC-PS File not available
• r0949 = 3: MMC-PS cannot read the file
• r0949 = 4: MMC-PS problems in the clone File ( e.g CRC )
Remedy: • r0949 = 0: Use MMC-PS with FAT12 or FAT16 format or correct MMC-PS Type, or fit an MMC-PS to Drive.
• r0949 = 1: Check MMC ( e.g is MMC full ) - Format MMC again to FAT16
• r0949 = 2: Put the correct named file in the correct directory /USER/SINAMICS/DATA.
• r0949 = 3: Make sure File is accesable. Recreate File if possible
• r0949 = 4: File has been changed - Recreate File
F00062 Par Cl. MMC-PS contents invalid
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Cause: File exists but the contents are not valid Control Word Corruption.
Remedy: Recopy and ensure operation completes.
F00063 Par Cl. MMC-PS contents incompatible
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Cause: File exists but was not the correct drive type.
Remedy: Ensure clone from compatiable drive type.
F00064 Drive attempted to do an automatic clone during startup.
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Cause: No Clone00.bin File in the correct directory /USER/SINAMICS/DATA.
Remedy: If a automatic clone is required:
- Insert MMC with correct File anc power cycle.
If no automatic clone is required:
- Remove MMC if not needed and power cycle.
- Reset P8458 = 0 and power cycle.
F00070 PLC setpoint fault
Reaction: OFF 2 (OFF 3)
Acknowledge: Quit fault eg. via DI2
Cause: No setpoint values from PLC during telegram off time
Remedy: • Check and improve - if necesarry - the value in p2040
• Acknowledge fault
• if fault persists, change inverter control unit
F00071 USS setpoint fault
Reaction: OFF 2 (OFF 3)
Acknowledge: Quit fault eg. via DI2
Cause: No setpoint values from USS during telegram off time
Remedy: Check and if necessary improve the monitoring time in the STARTER SW while getting the command source.
Check USS master
To Next Page
Loading...
