FUZ2 -A/-B/-C/-CX/-G/-L
Assembly instructions
TST
FEIG ELECTRONIC GmbH
Page 76 of 96
TST_FUZ2-A-B-C-CX-G-L_Montageanleitung_EN_22.docx
No.
Description
Possible reason for error
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.106
The parameterization of
sensors regarding the mounting
position or the operating mode
is implausible
The parameterization of
sensors regarding the mounting
position or the operating mode
is implausible
• At least more than 1 light curtain in the encoder mode.
• One light curtain as comfort light curtain, but no light curtain in encoder or autark mode
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.109
There is a new safety device
connected to the CAN bus that
could not be assigned to an SAI
slot.
Another light curtain was connected to the CAN bus, but there is no free SAI slot available.
Or the SAI slot was preset incorrectly.
Remedy: Set corresponding application profile A.480.
F.10A
A sensor/actuator component
was not detected or is not
present
It was detected that only one component of a sensor/actuator is present on the CAN bus (e.g. for a light curtain only
the transmitter)
Remedy:
- Connect missing component to the CAN bus
- Check CAN cabling to see if there is a broken wire.
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.