List of Faults and Alarms
Faults and Alarms
3-691
© Siemens AG 2011 All Rights Reserved
SINAMICS G120 / Control Units CU240B/E-2 Parameter Manual (LH11), 01/2011
F07016 Drive: Motor temperature sensor fault
Reaction: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge: IMMEDIATELY
Cause: An error was detected when evaluating the temperature sensor set in p0601.
Possible causes:
- wire breakage or sensor not connected (KTY: R > 2120 Ohm).
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Note:
If alarm A07015 is present, the time in p0607 is started. If the fault is still present after this time has expired, then
fault F07016 is output; however, at the earliest, 50 ms after alarm A07015.
See also: p0607 (Temperature sensor fault timer)
Remedy: - make sure that the sensor is connected correctly.
- check the parameterization (p0601).
- induction motors: De-activate temperature sensor fault (p0607 = 0).
See also: r0035 (Motor temperature), p0601 (Motor temperature sensor type), p0607 (Temperature sensor fault
timer)
F07080 Drive: Incorrect control parameter
Reaction: NONE
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0).
Fault value (r0949, decimal interpretation):
The fault value includes the parameter number involved.
The following parameter numbers only occur as fault values for vector drives:
p0310, for synchronous motors: p0341, p0344, p0350, p0357
The following parameter numbers do not occur as fault values for synchronous motors:
p0354, p0358, p0360
See also: p0310, p0311, p0341, p0344, p0350, p0354, p0356, p0357, p0358, p0360, p0640, p1082, p1300
Remedy: Modify the parameter indicated in the fault value (r0949) (e.g. p0640 = current limit > 0).
See also: p0311, p0341, p0344, p0350, p0354, p0356, p0358, p0360, p0640, p1082
F07082 Macro: Execution not possible
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The macro cannot be executed.
Fault value (r0949, interpret hexadecimal):
ccccbbaa hex:
cccc = preliminary parameter number, bb = supplementary information, aa = fault cause
Fault causes for the trigger parameter itself:
19: Called file is not valid for the trigger parameter.
20: Called file is not valid for parameter 15.
21: Called file is not valid for parameter 700.
22: Called file is not valid for parameter 1000.
23: Called file is not valid for parameter 1500.
24: Data type of a TAG is incorrect (e.g. Index, number or bit is not U16).
Fault causes for the parameters to be set:
25: Error level has an undefined value.
26: Mode has an undefined value.
27: A value was entered as string in the tag value that is not "DEFAULT".
31: Entered drive object type unknown.
32: A device was not able to be found for the determined drive object number.
34: A trigger parameter was recursively called.
35: It is not permissible to write to the parameter via macro.
36: Check, writing to a parameter unsuccessful, parameter can only be read, not available, incorrect data type, value
range or assignment incorrect.
37: Source parameter for a BICO interconnection was not able to be determined.
38: An index was set for a non-indexed (or CDS-dependent) parameter.
39: No index was set for an indexed parameter.
41: A bit operation is only permissible for parameters with the parameter format DISPLAY_BIN.
42: A value not equal to 0 or 1 was set for a BitOperation.
43: Reading the parameter to be changed by the BitOperation was unsuccessful.
51: Factory setting for DEVICE may only be executed on the DEVICE.
61: The setting of a value was unsuccessful.
Remedy: - check the parameter involved.
- check the macro file and BICO interconnection.
See also: p0015, p0700, p1000, p1500
To Next Page
Loading...
