Siemens SINUMERIK 808D ADVANCED Diagnostic Manual page 442

SINAMICS V70 alarms
5.2 Common faults and alarms
Fault
F1018: Booting has been
interrupted several times
Reaction: NONE
Acknowledgement: POWER
ON
F1030: Sign-of-life failure for
master control
Reaction: OFF3
Acknowledgement:
IMMEDIATELY
F1611: SI CU: Defect
detected
Reaction: OFF2
Acknowledgement:
IMMEDIATELY
F1910: Drive Bus: setpoint
timeout
Reaction: OFF3
Acknowledgement:
IMMEDIATELY
F1911: Drive Bus clock cycle
synchronous operation clock
cycle failure
Reaction: OFF1
Acknowledgement:
IMMEDIATELY
F1912: Clock cycle
synchronous operation sign-
of-life failure
Reaction: OFF1
Acknowledgement:
IMMEDIATELY
442
Cause
Module booting was interrupted several
times. As a consequence, the module
boots with the factory setting.
Possible reasons for booting being
interrupted:
•
Power supply interrupted.
•
CPU crashed.
•
Parameterization invalid.
After this fault is output, then the module is
booted with the factory settings.
For active PC master control, no sign-of-
life was received within the monitoring
time.
The drive-integrated "Safety Integrated"
(SI) function on the Control Unit (CU) has
detected an error and initiated an STO
The reception of setpoints from the Drive
Bus interface has been interrupted.
•
Bus connection interrupted.
•
Controller switched off.
•
Controller set into the STOP state.
The global control telegram to synchronize
the clock cycles has failed - in cyclic
operation - for several Drive Bus clock
cycles or has violated the time grid
specified in the parameterizing telegram
over several consecutive Drive Bus clock
cycles.
The maximum permissible number of
errors in the controller sign-of-life (clock
synchronous operation) has been
exceeded in cyclic operation.
Remedy
•
Carry out a POWER ON (power off/on).
After switching on, the module reboots from
the valid parameterization (if available).
•
Rrestore the valid parameterization
Examples:
•
Carry out a first commissioning, save, carry
out a POWER ON (switchoff/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.
Contact the Hotline.
•
Carry out a POWER ON (power off/on) for
all components.
•
Upgrade software.
•
Replace the Control Unit.
Restore the bus connection and set the
controller to RUN.
•
Check the physical bus configuration
(cable,connector, 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).
•
Physically check the bus (cables,
connectors, terminating resistor, shielding,
etc.).
•
Correct the interconnection of the controller
sign-of-life.
•
Check whether the controller correctly
sends the sign-of-life.
•
Check the permissible telegram failure rate.
•
Check the bus and controller for utilization
level (e.g. bus cycle time was set too short).
Diagnostics Manual, 08/2013, 6FC5398-6DP10-0BA1
Diagnostics Manual