TST
Assembly instructions
FUF2 / FU3F -A/-C/-F
FEIG ELECTRONIC GmbH
page 95 of 114
TST_FUxF-A-C-F_Montageanleitung_EN_15
No.
Description
Possible reason for error
F.910
No communication to expansion board possible
• The communication to the expansion board is not possible
• No expansion board plugged in
• CAN Connection interrupted (Broken cable or no supply voltage for extension
board)
F.911
ROM error on extension board
• Wrong Flash
-Code
• Defective hardware or noise
-saturated environment
F.912
RAM error on extension board
• Defective hardware or noise
-saturated environment
F.915
Communication error between main processor and
I/O processor
• Defective Hardware
• strong disturbances in surrounding
• to high temperature
F.920
Internal 2.5 V reference voltage incorrect
• Hardware defect
F.921
Internal 15 V voltage incorrect
• Hardware defect
F.922
Static and dynamic monitoring of the emergency stop
chain against defect or external power (static
monitoring is offered by each controller, dynamic
monitoring does not exist in
WU2/WUI2/FUH/FU3R/FUZ/FUZ2)
Static monitoring: Interrupted emergency stop chain means: All emergency
inputs from the interrupted one, including all subsequent emergency inputs,
must be triggered, if one of the subsequent emergency inputs is not triggered it
must be assumed that a remote supply is used.
Dynamic monitoring: During the system tests, the closed emergency stop
chain is actively opened via an internal switch, so that all emergency stop
inputs must become active, if this does not happen, an external supply or a
defect must be assumed.
F.924
24V brake output defective
• Error not acknowledgea
ble
• Hardware defect
F.925
Testing of the third shutdown method failed
• defective hardware
F.926
Bad braking current
The expected braking current that is defined by parameter P.183 can be set.
The fault is set when the actual current was exceeded by more than +-0,5 A
outside the parametrized range.
F.928
Faulty input testing
• The testing of an cyclic tested input was not successful
• The connected device is not working
• The cable connection between the connected device and the controll
er is
broken
F.92A
If the motor wiring test is activated by P.112 the
wiring will be tested during system tests.
• min. one of the motor cables is not good or nor connected.
• Motor cable damaged
• Motor damaged
F.930
External watchdog incorrect
•
Defective hardware or noise-saturated environment