Technical data

List of Faults and Alarms
Faults and Alarms
3-661
© Siemens AG 2011 All Rights Reserved
SINAMICS G120 Control Units CU230P-2 Parameter Manual (LH9), 01/2011
F01018 Booting has been interrupted several times
Reaction: NONE
Acknowledge: POWER ON
Cause: Module booting was interrupted several times.
Possible reasons for booting being interrupted:
- POWER OFF of the module.
- CPU crash.
- USER data invalid.
After this fault is output, then the module is booted with the factory settings.
Remedy: Power down the module and power it up again.
Note:
After switching on, the module reboots from the USER data (if available).
If the fault situation is repeated, then this fault is again output after several interrupted boots.
A01019 Writing to the removable data medium unsuccessful
Reaction: NONE
Acknowledge: NONE
Cause: The write access to the removable data medium was unsuccessful.
Remedy: Remove and check the removable data medium. Then run the data backup again.
A01020 Write to RAM disk unsuccessful
Reaction: NONE
Acknowledge: NONE
Cause: The write access to the internal RAM disk was unsuccessful.
Remedy: Adapt the size of the system logbook (p9930) to the internal RAM disk.
F01023 Software timeout (internal)
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: An internal software timeout has occurred.
Fault value (r0949, decimal interpretation):
Only for internal Siemens troubleshooting.
Remedy: - carry out a POWER ON (power off/on) for all components.
- upgrade firmware to later version.
- contact the Hotline.
A01028 Configuration error
Reaction: NONE
Acknowledge: NONE
Cause: The parameterization that was downloaded was generated with a different module type (Order No., MLFB).
Remedy: Save parameters in a non-volatile fashion (p0971 = 1).
F01030 Sign-of-life failure for master control
Reaction: OFF3 (IASC/DCBRAKE, NONE, OFF1, OFF2, STOP2)
Acknowledge: IMMEDIATELY
Cause: For active PC master control, no sign-of-life was received within the monitoring time.
The master control was returned to the active BICO interconnection.
Remedy: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function.
For the commissioning software, the monitoring time is set as follows:
<Drive> -> Commissioning -> Control panel -> Button "Fetch master control" -> A window is displayed to set the
monitoring time in milliseconds.
Notice:
The monitoring time should be set as short as possible. A long monitoring time means a late response when the
communication fails!