SINAMICS G120D
List Manual (LH14), 01/2016, A5E33842313
821
4 Faults and alarms
4.2 List of faults and alarms
Remedy:
- check the parameters displayed in r9406 up to r9408, and correct these if required.
- Restore the factory setting using (p0970 = 1) and re-load the project into the drive unit.
Then save the parameterization in STARTER using the function "Copy RAM to ROM" or with p0971 = 1. This
overwrites the incorrect parameter files in the non-volatile memory – and the alarm is withdrawn.
See also: r9406 (PS file parameter number parameter not transferred), r9407 (PS file parameter index parameter not
transferred), r9408 (PS file fault code parameter not transferred)
A01049
It is not possible to write to file
Message class:
Hardware/software error (1)
Reaction:
NONE
Acknowledge:
NONE
Cause:
It is not possible to write into a write-protected file (PSxxxxxx.acx). The write request was interrupted.
Alarm value (r2124, interpret decimal):
Drive object number.
Remedy:
Check whether the "write protected" attribute has been set for the files in the non-volatile memory under
.../USER/SINAMICS/DATA/... When required, remove write protection and save again (e.g. set p0971 to 1).
F01054
CU: System limit exceeded
Message class:
Error in the parameterization / configuration / commissioning procedure (18)
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
At least one system overload has been identified.
Fault value (r0949, interpret decimal):
1: Computing time load too high (r9976[1]).
5: Peak load too high (r9976[5]).
Note:
As long as this fault is present, it is not possible to save the parameters (p0971).
See also: r9976 (System utilization)
Remedy:
For fault value = 1, 5:
- reduce the computing time load of the drive unit (r9976[1] and r9976[5]) to under 100 %.
- check the sampling times and adjust if necessary (p0115, p0799, p4099).
- de-activate function modules.
- de-activate drive objects.
- remove drive objects from the target topology.
- note the DRIVE-CLiQ topology rules and if required, change the DRIVE-CLiQ topology.
When using the Drive Control Chart (DCC) or free function blocks (FBLOCKS), the following applies:
- the computing time load of the individual run-time groups on a drive object can be read out in r21005 (DCC) or
r20005 (FBLOCKS).
- if necessary, the assignment of the run-time group (p21000, p20000) can be changed in order to increase the
sampling time (r21001, r20001).
- if necessary, reduce the number of cyclically calculated blocks (DCC) and/or function blocks (FBLOCKS).
A01064 (F)
CU: Internal error (CRC)
Message class:
Hardware/software error (1)
Reaction:
NONE
Acknowledge:
NONE
Cause:
A checksum error (CRC error) has occurred in the Control Unit program memory
Remedy:
- carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.