Table of Contents
Advertisement
Faults and Alarms
List of faults and alarms
Cause:
An internal software error has occurred when initializing the terminal functions on the CU3xx, the TB30 or the TM31.
Fault value (r0949, hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
- carry-out a POWER ON (power off/on) for all components.
- upgrade the firmware release.
- contact the Hotline.
- replace the control unit.
Reaction upon A:
NONE
Acknowledge
NONE
upon A:
F01205
CU: Time slice overflow
Reaction:
OFF2
Acknowledge:
power on
Cause:
Insufficient processing time is available for the existing topology.
Fault value (r0949, hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
- reduce the number of drives.
- increase the sampling times.
F01210
CU: Selected basic clock cycle does not match DRIVE-CLiQ clock cycle
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The parameter to select the basic clock cycle does not match the drive topology. Drives connected to the same
DRIVE-CLiQ port of the control unit have been assigned different basic clock cycles.
Fault value (r0949, decimal):
The fault value specifies the parameter involved.
See also: p0111
Remedy:
Only those drive objects may be connected to the same DRIVE-CLiQ socket of the control unit that should run with
the same basic clock cycle. For example, active line modules and motor modules should be inserted at different
DRIVE-CLiQ ports as their basic clock cycles and current controller clock cycles are generally different.
See also: p0111
F01220
CU: Bas clock cyc too low
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The parameter for the basic clock cycle is set too short for the number of connected drives.
Fault value (r0949, decimal):
The fault value specifies the parameter involved.
See also: p0110
Remedy:
- increase the basic clock cycle.
- reduce the number of connected drives and start to re-commission the unit.
See also: p0110
F01221
CU: Basic clock cycle too short (application cannot maintain its clock cycle)
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The closed-loop control / monitoring cannot maintain the intended clock cycle.
The runtime of the closed-loop control/monitoring is too longer for the particular clock cycle or the computation time
remaining in the system is not sufficient for the closed-loop control/monitoring.
Fault value (r0949, hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
Increase the basic clock cycle of DRIVE-CLiQ communications.
See also: p0112
F01250
CU: CU-EEPROM incorrect read-only data
Reaction:
NONE (OFF2)
Acknowledge:
power on
3-522
Siemens AG 2004 All Rights Reserved
SINAMICS G List Manual, Edition 12.2004
Hide quick links:
Advertisement
Table of Contents
