15 Appendix
59-4
FSM: error
management: too many
errors
Cause:
Too many errors have occurred simultaneously.
Measure:
- Clarify: What is the status of the inserted safety
module - does it contain a valid parameter set?
- Read out and analyse the permanent event
memory of the servo drive via the
parameterisation program.
- Eliminate causes of error step by step.
- Install safety module with “delivery status” and
perform commissioning of servo drive.
- If this is not available: Set factory settings in the
safety module, then copy data from the servo
drive and perform complete validation.
- Check whether the error occurs again.
59-7
FSM: flash checksum
error
Cause:
- Voltage interruption / power off while
parameters were being saved.
- Flash memory in safety module corrupted (e.g.
by extreme malfunctions).
Measure:
Check whether the error recurs after a reset. If it
does: parameterise the module again and
validate the parameter set again. If error persists:
safety module defective, replace.
59-8
FSM: internal
monitoring, processor 1
- 2
Cause:
- Serious internal error in the safety module: Error
detected while dynamising internal signals
- Disrupted programme sequence, stack error or
OP code test failed, processor exception /
interrupt.
Measure:
Check whether the error recurs after a reset. If it
does: Safety module defective, replace.
59-9
FSM: other unexpected
error
Cause:
Triggering of internal programme sequence
monitoring.
Measure:
- Check the firmware version of the servo drive
and the version of the safety module – update
available?
- Safety module defective, replace.
Group 60: Ethernet
60-0
Ethernet user-specific
(1)
Please contact the Technical Support team.
Group 61: Ethernet
61-0
Ethernet user-specific
(2)
Please contact the Technical Support team.
Product manual BL 4000-C
Page 293 of 298
