Fault
Cause
Remedy
F1015: Internal software er‐
ror
Reaction: OFF2
Acknowledgement: POWER
ON
An internal software error has occurred.
● Carry out a POWER ON (power off/on) for
all components.
● Upgrade firmware to the latest version.
● Contact the Hotline.
F1018: Booting has been in‐
terrupted several times
Reaction: NONE
Acknowledgement: POWER
ON
Module booting was interrupted several
times. As a consequence, the module
boots with the factory setting.
Possible reasons for booting being interrup‐
ted:
● Power supply interrupted.
● CPU crashed.
● Parameterization invalid.
After this fault is output, then the module is
booted with the factory settings.
● Carry out a POWER ON (power off/on).
After switching on, the module reboots from
the valid parameterization (if available).
● Restore the valid parameterization.
Examples:
● Carry out a first commissioning, save, carry
out a POWER ON (switch-off/switch-on).
● Load another valid parameter backup (e.g.
from the memory card), save, carry out a
POWER ON (switch-off/switch-on).
Note:
If the fault situation is repeated, then this fault
is again output after several interrupted boots.
F1030: Sign-of-life failure for
master control
Reaction: OFF3
Acknowledgement: IMMEDI‐
ATELY
For active PC master control, no sign-of-life
was received within the monitoring time.
Contact the Hotline.
F1611: SI CU: Defect detec‐
ted
Reaction: OFF2
Acknowledgement: IMMEDI‐
ATELY
The drive-integrated "Safety Integrated"
(SI) function on the Control Unit (CU) has
detected an error and initiated an STO
● Carry out a POWER ON (power off/on) for
all components.
● Upgrade software.
● Replace the Control Unit.
F1910: Drive Bus: Setpoint
timeout
Reaction: OFF3
Acknowledgement: IMMEDI‐
ATELY
The reception of setpoints from the Drive
Bus interface has been interrupted.
● Bus connection interrupted.
● Controller switched off.
● Controller set into the STOP state.
Restore the bus connection and set the control‐
ler to RUN.
F1911: Drive Bus clock cycle
synchronous operation clock
cycle failure
Reaction: OFF1
Acknowledgement: IMMEDI‐
ATELY
The global control telegram to synchronize
the clock cycles has failed - in cyclic oper‐
ation - for several Drive Bus clock cycles or
has violated the time grid specified in the
parameterizing telegram over several con‐
secutive Drive Bus clock cycles.
● Check the physical bus configuration (cable,
connector, Drive Bus terminator, shielding,
etc.).
● Check whether communication was briefly
or permanently interrupted.
● Check the bus and controller for utilization
level (e.g. bus cycle time was set too short).
SINAMICS V70 faults and alarms
7.2 Common faults and alarms
Diagnostics Manual
538
Diagnostics Manual, 06/2015, 6FC5398-6DP10-0BA2
