Feig Electronic TST FU3F-A - Page 83

TST Assembly instructions FUF2 / FU3F -A/-C/-F
FEIG ELECTRONIC GmbH page 83 of 114 TST_FUxF-A-C-F_Montageanleitung_EN_15
No.
Description
Possible reason for error
F.102
Faulty CAN bus due to faulty telegrams.
• Poor CAN wiring
• Missing ferrites on the motor cable
• Missing terminating resistors for CAN bus termination
• CAN lines too long (180m)
• Faults on the CAN line when the door operator is moving
F.103
CAN BUS is faulty. The error acknowledges itself
automatically if the CAN BUS is not faulty.
•Short circuit of The CAN Low and CAN High lines
•A device on The CAN bus interferes with The bus due to faulty telegrams.
•non terminated CAN bus
F.104
The maximum number of permitted devices (16) on
the CAN bus has been exceeded.
There are too many devices on the CAN bus
F.105
A CAN bus or RS485 bus participant is in bootloader
mode when the controller is switched on
•Power failure during the update
•After a failed update, a controller reset is performed.
F.108
Protocol version of a sensor/actuator is higher than
the highest known version of the door controller.
Software version of the door control system is too old for the sensor/actuator
used
F.110
Defective hardware VEK MNST
The VEK MNST detector is defective and must be replaced.
F.111
Disturbed detector VEK MNST
The VEK MNST detector is faulty. The system must be restarted.
F.112
Detector VEK MNST not plugged in
The VEK MNST detector slot was activated with parameter P.802 or P.803 =
0400, but no detector is plugged in.
F.113
Detector VEK MNST Slot not activated
The VEK MNST detector is plugged in but the slot was not activated with
parameter P.802 or P.803 = 0400.
F.114
Detector VEK MNST incompatible with control unit
The VEK MNST detector is not compatible with the controller software version
used --> Update of the controller software
F.116
Pairing VEK MNST not possible
The pairing, with the customer coding from the controller for the VEK MNST
failed --> Replace Detecor with not yet paired version.
F.117
The VEK MNST has restarted unexpectedly
The processor of the VEK MNST has hung up, crashed or the internal
watchdog has triggered, causing the processor to perform a warm start. --> If
this occurs repeatedly, the device must be replaced.
F.118
The VEK MNST has received an invalid customer
code from the door controller.
The already paired VEK MNST has detected that its customer code does not
match the one in the controller and is therefore incompatible --> use not yet
paired detector.
F.160
Motion detector 1
MWD BPC is defective
An exchange of the device is necessary
F.162
Motion detector 1
Communication of the control unit with the MWD BPC
motion detector was interrupted.
•Check the wiring of motion detector 1.
•Restart the control unit or the motion detector