Fallas 5400-1

5.
3 Error Description
5.3.1 Overview
Range Section
0..149 Travel Control
20..5999 0020_5999_Others
150..199 Variodyn E
200..299 Door Control
300..399 Varidor70 Door Drive
400..599 elevator
600..699 MC PVF
700..739 MC PVEC
740..799 Magnetek
800..899 800_899_Varidor35_Door_Drive
900..999 IO
1000..1199 CPU
1200..1249 LON
1250..1299 BIO2
1300..1349 1300_11349_CAN
1400..1499 VF
1500..1999 Travel Control Ext
2000..2099 2000_2099_Load_Measurement
2100..2299 2100_2299_MOSIS
2300..2499 2300_2499_SALSIS
5000..5099 5000_5099_Remote_Monitoring
8000..8099 8000_8099_Remote_Alarm
CADI GC Help A detailed description of all errors and possible causes with recommended actions can be
found in the CADI GC Help.
5.3.2 0..149 Travel Control
Error ID: 0007

NameShort
NameLong SH_Fault
Description The auxiliary contacts of SH / SH1 (or RH / RH1) opened while the car was
moving.
Extra Info Source-ID 104 (MONITOR)
1: SH and SH1 opened together (SH1 state is faulty)
3: SH and SH1 opened together (SH state is faulty)
5: RH and RH1 opened together (RH1 state is faulty)
8: RH and RH1 opened together (RH state is faulty)
Source-ID 114 (PREPARE_TRIP)
0: RTSC closed and Safety-chain open (old TX-Safety)
1: RTSC closed and Safety-chain closed (old TX-Safety)
S7000 Call Back Handling Draft K 42520051 00-H

Diagnostics
Copyright © 2013 INVENTIO AG 69/145
Error ID: 0007
Extra Info 2: RTSC not closed (old TX-Safety)
3: Safety-Chain open (MX2, MX5, TX2_EU, TX2_NA, TX_NA, TX_NA_A17_2000
.... safety)
4: Safety-Chain closed (MX2, MX5, TX2_EU, TX2_NA, TX_NA,
TX_NA_A17_2000.... safety)
5: SH-State is faulty on trip start, initiate shaking test (MX-Safety)
Cause Action
Safety circuit open Check the safety circuit
Wrong parameter value If the error occurs when the car is approaching the target
floor it may be caused by the door pre-opening circuit.
Reduce value for parameter MAX_DOOR_ZONE.
Bad wiring Check the auxiliary contact wiring of SH, SH1 (RH, RH1)
Error ID: 0008
NameShort
NameLong SB_Fault
Description Brake control error when the car is moving or during preparation for a trip. E.g. the
SB auxiliary contact opened unexpectedly or an error on the brake module
occurred (e.g. MBBx). See extra info values for different scenarios.
New error messages (id: 15xx) were introduced in 2011 for SB and MBBx
monitoring replacing this error message.
Extra Info 00 (hex)/ 0 (dec): The brake does not open during trip start with the predefined
time (brake is expected to open within 5s after command to open)
with MBBxx brake module (pcb: MBB3, MBBG, MBBGM):
01 (hex): State message (MBB_TASK_CREATE_ERROR)
02 (hex): IO message (MBB_BUFFER_OVERFLOW_ERROR)
03 (hex): Unknown message received (MBB_INT_WRONG_MSG)
04 (hex): Zero length message sent (MBB_ZERO_MESSAGE)
05 (hex): Unknown command received (MBB_UNKNOWN_COMMAND)
06 (hex): KB fault (MBB_KB_FAULT)
07 (hex): KB1 fault (MBB_KB1_FAULT)
08 (hex): Open timeout, no current (MBB_OPEN_TIMEOUT_CURRENT)
09 (hex): Close timeout, no zero current (MBB_CLOSE_TIMEOUT_CURRENT)
0A (hex): IGBT fault or other error (MBB_IGBT3_FAULT)
0B (hex): Error on MBB HW (MBB_HW_FAULT)
0C (hex): Brake open during standstill (MBB_OPEN_STANDSTILL)
0D (hex): Brake closed during trip (MBB_CLOSED_RUNNING)
0E (hex): MBB mailbox error (MBB_MBX_ERROR)
0F (hex): MBB too long message size (MBB_MAX_MESSAGE_SIZE)
10 (hex): MBB current difference error (MBB_CURRENT_DIFF_ERROR)
11 (hex): Mains did not switch off (MBB_MAINS_NOT_OFF)
12 (hex): IGBT1 check not O.K. (MBB_IGBT1_FAULT)
13 (hex): MBB voltage difference error (MBB_VOLTAGE_DIFF_ERROR)
Brake Module MX controls:
14 (hex): RB fault (for MX-GC controls) / (MBB_KBR_FAULT)
15 (hex): Brake time relay fault (for MX-GC controls) / (MBB_ZSB_FAULT)
Cause Action
Open safety circuit Check the safety circuit

Diagnostics
Cause Action
Auxiliary contacts of SB/SB1 not working Check operation of auxiliary contacts of SB/SB1.
Wiring of auxiliary contacts on SB/SB1 faulty Check wiring of auxiliary contacts of SB/SB1
Relay RB not working (pcb ASIXxx) Check operation of relay RB
Dust in the control cabinet or other difficult Remove dust
environmental conditions causing
conductivity problems.
MBBx (extra info value x0000000A): Open Check the electrical circuit from the cabinet to the brake(s),
brake circuit or faulty brake module check wiring of the AC supply to the brake module or replace
brake module
MBBx (extra info value x00000010): Short Check the electrical circuit from the cabinet to the brake(s)
circuit at brake module output
MBBx (extra info value x00000013): Wrong Check parameter values for these parameters: opening
parameter values voltage, holding voltage, AD resolution for brake voltage
measurement (-> Parameter -> Brake)
MBBx: No AC supply voltage on brake Check AC supply voltage for the brake module while brake
module should open when starting a trip (refer to the actual wiring
diagram)
MBBx: Faulty RSK/RSK1 relay on Check and replace SKEx/SKNAx board
SKEx/SKNAx board.
Transformer TAB/TB broken Replace transformer
Error ID: 0009

NameShort
NameLong KB_Fault
Description The brake contacts KB or KB1 do not switch as expected. Travel Control
continuously monitors both KB and KB1 (including standstill). In case of only one
KB contact, check that there is a jumper on the connector to the PCB.
Comment: With gearless drives, check that the brake contacts work properly, and
that the brake power supply is ok; when the brake opens, SB is operated first (full
power supply to the brake) and after a delay the voltage reduction to the brake is
activated (e.g. SGRB or electronic brake module). MX control: The operation of the
voltage reduction is independent of the KB and KB1 status. With MBBx brake
module the voltage reduction to holding voltage is depending on active state of
KB/KB1.
The brake has a certain time within which it must open; after this time the contacts
are checked. The reliable operation of the brake contact(s) is important. Make sure
the contacts are well fixed, clean and well adjusted. Consult the corresponding
instruction to adjust the brake contacts (experience shows, that probably the best
adjustment is to allow a gap of 1 mm between the contact and the actuating
element when the brake is closed).
Refer also to error messages 1507 - 1510 (these messages replace the message
#8 - depending on SW version)
Extra Info with MBBxx brake module (pcb: MBB3, MBBG, MBBGM):
06: KB fault (MBB_KB_FAULT)
07: KB1 fault (MBB_KB1_FAULT)
Cause Action
Defective brake contact(s) Check the brake contacts.
Bad adjustment of the brake contact(s) Check the operation of the brake contact(s) and (re-)adjust if
necessary
Mechanical problem on the brake Check the brake. Observe the brake when it opens. Both
sides of the brake should open symmetrically.

Diagnostics
Cause Action
Wrong parameter value for parameter 'KB Check drive parameters 'KB Type' and 'Brake Setting' for
feedback type' correct brake type.
Faulty pcb where brake contacts are wired Check for broken input and replace pcb (Brake Module,
to. ASILOGx/ASIXx or GCIOx) if necessary. Refer also to the
actual wiring diagram.
Error ID: 0010

NameShort
NameLong FC_Fault
Description The travel control monitors the state of the motor control (frequency converter)
based on the messages sent from the motor control to the control. After a start
command to the motor control, the control sets the state 'fc state' to 'running' when
it receives the message 'start acknowledge' (from motor control). After that the
control will terminate the trip with an emergency stop and log the error 'FC Fault'
when:
a) The motor control requests an emergency stop by sending the related message
to the control.
b) The control detects a communication problem to the frequency converter
(control receives no 'return_speed' message for more than 40ms).
Comments: The Motor Control monitors the contactor SH. When the safety circuit
opens during a trip Motor Control may detect this before Travel Control. So this
event can also be caused by a safety circuit problem. Please refer also to the error
description for error 'SH_Fault'.
There is a known problem on the control (TX2, MX) which may lead to a false
'FC_Fault' error in the log of the control: If the control performs an emergency stop
with closed safety circuit the RSK relays drop and the software of the motor control
detects this before it receives the related message 'inverter stop'. The motor
control then interprets this situation as a emergency stop which in return will lead
to a FC_Fault error on the control. This scenario may be tested/verified by sending
a VCOM telegram (STCMD_DRIVE / BLOCK_DRIVE)
Extra Info R&D use only
Cause Action
Problem on frequency converter. Refer to Motor Control related diagnostics.
Communication between control Check the wiring and plugs of the connection cable between
(ASILOGx/ASIXx) and frequency converter the FC and the control.
(temporarily) interrupted.
Problem on the safety circuit. Look for safety circuit related error messages which are
logged together with 'FC-Fault'. Check the contacts in the
related section of the safety circuit.
Error ID: 0011

NameShort
NameLong FC_Block
Description 'Error State' of Motor Control (frequency converter) is 'blocked'. The frequency
converter is not available. The travel control recovers when the inverter is available
again.
Extra Info None.
Cause Action
Frequency converter is not available Refer to Motor Control related diagnostics

Diagnostics
Error ID: 0013
NameShort
NameLong OverSpeed
Description The error is logged in the following cases:
a) The software detects that the actual speed of the car exceeds the maximum
limit for the car speed. The software calculates the speed limit based on the
current speed reference value which is sent to the inverter Vlim = f(Vref). If the
difference between the actual speed of the car and the speed reference
(velocity_ref) exceeds the calculated limit the trip is interrupted with an emergency
stop. The allowed speed difference is calculated as follows: 6.25% of the actual
reference speed; the minimum for the allowed speed difference is 0.2m/s (applies
also when the car is standing). The actual speed value which is compared against
the limit is either the calculated speed from the car position encoder (s_tacho) or
the actual speed received from the inverter (v_tacho).
b) that the speed reference (velocitiy_ref) was outside the allowed limits (min/max).
If the value of the calculated speed reference (velocity reference) exceeds the
predefined limits (min/max) for the speed reference the trip is interrupted with an
emergency stop. The maximum limit for the velocity reference applies to the car
speed in the direction the car shall travel. The values for the minimum limits apply
when the car moves in the opposite direction. The predefined min/max limits are
[mm/s]:
max velocity_ref for manual_trips: 630 + 20
min velocitiy_ref for manual trips: -100
max velocity_ref for montage trips: 500 + 15
min velocitiy_ref for montage trips: -100
max velocity_ref for learn trips: v_learn + 30
min velocity_ref for learn trips: -100
max velocity_ref for synch trips: v_synch + 30
min velocity_ref for synch trips: -300
max velocity_ref for normal trips: v_max
min velocity_ref for normal trips: -300
max velocity_ref for relevel trips: 300
min velocity_ref for relevel trips: -300
max velocity_ref for ramp trips: 350
min velocity_ref for ramp trips: -100
If the limit for velocity reference is exceeded an additional SW warning (error #70)
is logged with the same time stamp and with the extra info hex35A/dec858
Extra Info 0: speed calculated from position tacho (car) too high
1: actual speed from inverter too high with IMOF
2: actual speed from inverter too high
3: speed calculated from position tacho (car) too high with IMOF
other values: value of the velocity reference when it is above or below the max. or
min. limit
Cause Action
Incorrect parameter values Check the parameters both on Travel Control and Motor
Control.
Incorrect tacho input from position tacho Check position tacho.
Incorrect load value from load measuring Check the load measurement device and the load
system causing wrong torque on machine parameters. These checks should also be made if the event
occurs just at the beginning of the trip.

Diagnostics
Cause Action
Car moves faster than the detection speed Check if machine brake applies sufficient mechanical torque.
limit while the drive/motor is switched off. Perform brake test according to acceptance test instruction.
May be caused by loss of traction at
standstill or manual opening of the brake.
Excessive rope stretch (e.g. ARAMID ropes). Adjust parameter for rope elongation.
Position control for car attempts to do
correction with a velocity reference outside
the limits.
Error ID: 0014

NameShort
NameLong UnderSpeed
Description If the difference between the actual speed of the car calculated from the position
encoder and the reference speed (velocity_ref) exceeds the calculated limit (speed
tolerance) the trip is interrupted with an emergency stop. The allowed speed
difference (tolerance) is calculated as follows: 6.25% of the reference speed with a
minimum of 0.1m/s. The allowed speed difference is 0.1m/s up until a speed of
1.6m/s.
The software detects that the actual speed of the car is below the minimum limit for
the car speed. The software calculates the speed limit based on the current speed
reference value which is sent to the inverter Vlim = f(Vref). If the difference
between the actual speed of the car and the speed reference (velocity_ref) is
below the calculated limit the trip is interrupted with an emergency stop. The
allowed speed difference is calculated as follows: -6.25% of the actual reference
speed; the minimum for the allowed speed difference is 0.2m/s. The actual speed
value which is compared against the limit is either the calculated speed from the
car position encoder (s_tacho) or the actual speed received from the inverter
(v_tacho).
Extra Info 0: speed calculated from position tacho (car) too low
1: actual speed from inverter too low with IMOF
2: actual speed from inverter too low
3: speed calculated from position tacho (car) too low with IMOF
Cause Action
Incorrect parameter values Check the parameters both on Travel Control and Motor
Control.
Incorrect tacho input from position tacho Check position tacho
Incorrect load input Check the load measurement device and the load
parameters. These checks should also be made if the event
occurs just at the beginning of the trip.
Speed reference value exceeds capabilities Check speed and acceleration parameters.
of the inverter; the inverter is not able to
follow the trip curve.
Car or counterweight mechanically blocked Make sure car and counterweight can move in guide rails.
Rope slip on traction sheave Check correct balancing of car/counterweight.
Error ID: 0020

NameShort
NameLong PositionLost

Diagnostics
Error ID: 0020
Description Error occurs when:
- the car passes a floor fin/magnet at a measured position more than 15cm off the
reference position stored during the learn trip.
- the car passes a floor position without detecting a floor fin/magnet at that floor
position stored during learn trip.
- the car approaches a target floor without finding a floor fin/magnet at that floor
position stored during learn trip.
- the car is at a floor level and detects no floor fin/magnet.
Comments:
- Travel Control initiates a synchronization trip after the error occurs. In case of
incremental position tacho (IG) the car will then make a synch trip to the KSE
position. With absolute type encoder position tacho (AGSI/ALSIS) the car will go to
the next floor level.
- If the car is standing at floor level and one of the photocells (PHS/PHNRD) gives
an incorrect message 'OUT_FIN' travel Control takes the photocell information to
be actual and assumes that the car is at the edge of the fin and not at floor level.
(This situation can occur in large buildings with significant rope stretch, if the car is
standing a long time at the floor level). Travel Control overwrites the position and a
relevel_trip is started for a distance of 15mm. Since the car was at level at the
beginning of this trip the second photocell will go out of the fin. Now both
photocells are out of the fin, but Travel Control still assumes the car is almost level,
which is detected as a POSITION_LOST.
Extra Info 0 (hex): With the car at a floor level both signals PHS and PHNR_D are inactive
('OUT_FIN'). 'OUT_FIN' transition of signal PHS occurs later than expected.
(Comment: with PHS/PHNR_D input the SW interprets the signals as 'IN_FIN'
when the related wire from the photocell is removed).
1 (hex): 'OUT_FIN' transition of signal PHNR_D occurs later than expected.
2 (hex): TX-GC2: Corrupted shaft image.> Invalid floor position / MX-GC with
AGSI/ALSIS: LUET did not switch while passing a floor.
3 (hex): MX-GC/TX-GC: Corrupted shaft image -> Invalid floor position
4 (hex): TX-GC2: Corrupted shaft image for KSE-D / Mismatch detected between
the door zone information (KUET) and the position value from the car position
feedback device (AGSI/IGS). The digital signal for the door zone from the shaft
information (LUET) is active but the car position value says the car is well outside
the door zone.
5 (hex): MX-GC/TX-GC: Corrupted shaft image -> Invalid value for KSE-D position
8 (hex): TX-GC2: Corrupted shaft image -> Invalid value for KSE-U position
9 (hex): MX-GC/TX-GC: Corrupted shaft image -> Invalid value for KSE-U position
A (hex): Position of KSE-U magnet found more than 15cm away from the position
stored during the learn trip.
B (hex): Position of KSE-D magnet found more than 15cm away from the position
stored during the learn trip.
C (hex): While doing a synch trip KSE-D magnet switched more than 15cm away
from the position stored during the learn trip.
Cause Action
Mechanical problem with the shaft Check the position of the fins or magnets. Repeat the learn
information (fins or magnets). trip.
Mechanical problem with the shaft Check the horizontal distance between fins/magnets and
information; mounting of photocall or photocell/switch. Make sure the clearance of the car is not
switch. too big when the car is at floor levels.

Diagnostics
Cause Action
Problem with components in hoistway (e.g. Check tension of safety ropes in hoistway. If vane to vane
safety rope). On installations with safety distance is > 5m, the safety rope must be removed. See also
ropes (yellow rope) one of the ropes may related TK K602777
interfere with the floor sensor giving wrong
input (e.g. inputs PHS) to the control.
The position tacho (IG type or AGSI type) is Check for mechanical slip on the position tacho. Check that
not working properly. the position tacho runs smoothly. For IGBV check the tension
of the tacho belt.
Problem with the rope of the car position Check the car position tacho rope system:
tacho (IG type). - Correct tension force / Rope pulleys (top and bottom)
- The groove of the tacho pulleys has to be clean (especially
for IGS-200).
Wrong car position values from the car Check car position value shown on the SMLCD (or UI1).
position tacho. Check for EMC problems and refer to explanations for extra
info values.
Problem with electrical interferences on the Check the power supply for the photocells.
photocells (PHS / PHNR_D or magnetic
switches)
Broken wire or bad connection on plug. Check the ground connection on top of the car and from the
machine room/control cabinet to the car.
Faulty tacho interface circuit on Replace pcb.
ASILOGx/ASIXx
Error ID: 0028

NameShort
NameLong OverTempMotor
Description The measured motor temperature exceeds the temperature limits defined by the
parameter 'Mot Temp Limit' (PCT: P_ANT_TEMP_OVERHEAT_MOTOR) and the
minimum temperature limit (-10°C). For motors with a temperature sensor type
'PT100 resistor' the error may indicate a problem with the sensor (short circuit or
open). The elevator system will normally recover by itself when the motor
temperature drops below the overtemperature level (see also description for extra
info).
Remark: Before the introduction of the parameter 'Mot Temp Limit' the
overtemperature limit was fix at 150°C (Check motor parameters 'supervision').
Extra Info 0(hex): The motor temperature is below the minimum limit of -10°C. The elevator
remains blocked until the motor temperature rises above the minimum limit (fixed
value)
1(hex): The motor temperature is above the maximum limit defined by the
parameter 'Mot Temp Limit' (PCT_ANT_TEMP_OVERHEAT_MOTOR). The
elevator remains blocked until the motor temperature drops 20°C below the
maximum limit.
A(hex): The motor temperature is above the maximum limit defined by the
parameter 'PCT_ANT_TEMP_OVERHEAT_MOTOR' for more than 30min. The
elevator remains blocked until the motor temperature drops 20°C below the
maximum limit.
Cause Action
In case of normal motor temperature:
Incorrect or missing connection of the temp. Check wiring of temperature measurement device.
sensor (PT100) on the motor.
Wrong value of parameter. Check for correct parameter values of Motor Control ('Mot
Temp Limit').
Temperature sensor on motor broken Measure resistance of sensor and use other if broken.

Diagnostics
Cause Action
Wrong selection of sensor type on ASILOGx Check position of switch/jumper on ASILOGx board
board.
When motor temperature is too high:
Faulty motor windings. Check the motor windings for short circuit on the motor
terminal box.
Overtemperature due to excessive current. Check the main supply connection to the motor and the
ground connection.
Faulty ventilation on the motor. Check the motor ventilator(s).
Excessive temperature in the machine room. Measure temperature in the machine room.
Error ID: 0040

NameShort
NameLong NoPHS_Learn
Description For IG type position tacho (incremental):
At the beginning of the learn trip (after the preparation trip) the car should be within
the fin of PHS Photocell (IN_FIN). If this is not the case the preparation for the
learn_trip is aborted. If the PHS connection to Travel Control is missing, the
internal status is PHS=IN_FIN. Therefore, without PHS connected, the learn trip
will start normally. The trip will abort when passing the first KSE magnet.
For AGSI/ALSIS type position tacho (absolute encoder):
Trip will be aborted if the learn trip is triggered outside door zone magnet (KUET).
For MOSIS / SALSIS:
At the end of the preparation trip the control expects to have crossed the lowest
floor while the car is slowing down. This because the preparation ends 2cms
beyond [below] the lowest floor. If the car undertravels this distance, then the
lowest floor will not be learnt and if the learn trip continues, then the learn trip will
learn 1 less floor [i.e. the lowest floor] and end unsuccessfully. A possible reason
for this error would be misaligned floor magnets [which the control expects at
KSE_DISTANCE below the lower KSE]. Another reason could be incorrectly
adjusted drive parameters [like interia, etc] which would affect the speed regulation
so the car is not following the speed curve.
Cause Action
With IG type (incremental) position tacho: Check the KSE signal (distance, polarity of magnet, wiring).
With IG type (incremental) position tacho: Check wiring of PHS.
With IG type (incremental) position tacho: Check ground connection of photocell PHS.
With AGSI or ALSIS (absolute encoder) type Check the KUET signal (polarity of magnet, wiring).
position tacho:
With AGSI or ALSIS (absolute encoder) type Check operation of KUET(1) inputs on car interface board
position tacho:
With MoSIS / SALSIS type position tacho: Check sensor & magnet for floor detection
Error ID: 0050

NameShort
NameLong NoDistRelv

Diagnostics
Error ID: 0050
Description The software detects that the car is outside the relevel zone defined by the
parameter 'Relevel Distance' during the preparation for a relevel trip. The software
aborts the preparation for the relevel trip. In case the error occurs too frequent the
elevator shuts down with fatal error. This situation may occur in situations where
the car moves due to a high 'load change rate' when the car is loaded or unloaded
on a floor. The same effect may be caused by high rope stretch/shrink when the
car load changes (bouncing effects).
Based on field experience the decision was made to no longer log this error
(modification in software June 2011).
Cause Action
Wrong parameter values. Check the parameter for the releveling zone 'Relevelling
Distance'. 'Minimum Distance'
Excessive car movement at standstill. Check for causes of the car movement at standstill.
Inappropriate triggering of the relevelling Check/adjust the parameter 'Re-levelling delay'.
trip.
Error ID: 0055

NameShort
NameLong NoMCR_Com
Description Communication with frequency converter (motor control) can not be established or
is lost. The communication between control and inverter is also monitored in
standstill; the control requests the commissioning and error state periodically from
the inverter.
Remark: On control software versions released before Sep. 2012 interruption of
the communication between inverter and (travel) control is logged with error
'FC_Fault'.
Extra Info Information about the circumstances when communication to the inverter is not
working:
0: Communication interrupted during a trip, e.g. bus cable physically removed
while the car is moving.
1: The travel control does not get a response from the inverter after requesting
parameters.
2: The travel control does not get a response from the inverter when expecting the
parameter checksum to be received.
3: The travel control does not get a response from the inverter when expecting the
acknowledge message after sending a parameter to the inverter.
4: The travel control could not send the STOP_EDIT message to the inverter.
5: The travel control receives a negative acknowledge from the inverter after
sending the STOP_EDIT command.
6: The travel control does not receive an acknowledge from the inverter after
sending the STOP_EDIT command.
7: The travel control does not receive an acknowledge from the inverter after
requesting the commissioning state or error state. Travel control requests
commissioning state and error state periodically from the inverter.
Cause Action
Bus cable between Travel Control and Motor Check if bus cable is connected to pcb on Motor Control
Control not connected. (inverter) and Travel Control (ASIX, ASILOG, etc).
Broken pcb on frequency converter. Check if pcb on Inverter (Motor Control) is damaged and
replace if necessary. Try to access the Motor Control with
SMLCD or CADI. This will check the hardware connection.
Interface pcb on control where bus cable is Replace pcb if necessary.
connected to broken (ASILOGx, ASIXx)

Diagnostics
Cause Action
EMC Problems Check shielding (motor cable, encoder, RS422...), separate
motor cable from all others.
Error ID: 0056

NameShort
NameLong CarNoStop
Description The trip monitoring detects that the car is still moving after the brake has closed.
This may occur when the brake capability of the machine brake is insufficient.
When finishing a trip (normal stop or emergency stop) the travel control
deactivates the brake and waits for the brake to close. After the brake contacts
indicate that the brakes have closed the software checks the car speed periodically
and expects the car to stop within the time limit defined by the internal parameter
'MOVE_SHUTDOWN' (default value: 4 sec). The condition that the car has
stopped is that the car does not move more than 10mm within 1 sec (for a tacho
factor of 3000inc/m). If the car still moves after the time defined by the parameter
'MOVE_SHUTDOWN' the error is generated and the control aborts the trip. There
is no way to set the parameter 'MOVE_SHUTDOWN' manually.
This monitoring detects an unintended movement of the car at the end of a trip if
the brake torque is insufficient or if the car keeps moving for another reason
(monitoring of the car speed in standstill is done with 'overspeed' detection). This
monitoring is also active during an emergency stop but only if mains power is
available.
See also error message #737 (motor control)
Cause Action
Incorrect brake adjustment or faulty brake. Verify brake action by performing an emergency stop at full
speed in up direction with empty car and check if the car
comes to rest. Adjust brake.
Remark: Use the brake test (acceptance test) to measure the
average car deceleration rate after emergency stop. Be
aware of possible rope slip on the traction sheave.
Insufficient traction between ropes and Check for rope slip.
traction sheave
Error ID: 0064

NameShort
NameLong PHS_Fault
Description The lower photocell (PHS) is not working properly (software name for error
message: PHS_BOUNCE). The PHS/PHNRD signals are generated by two
photocells on the car. Only used on shaft information systems with incremental
encoders (e.g. TX, TX-R5). On TX-R5 and TX controls the state of the input signal
is logically 1 and electrically 'low' (in_fin) when the input is disconnected (same as
when the car is levelled).
Monitoring Conditions:
1. The car left the fin but the PHS input is in state 'IN_FIN' or
2. the car is at floor level and PHS input is in state 'OUT_FIN' or
3. two PHS signals are received within a too short time which means that the PHS
signal is bouncing.
The error does not trigger an emergency stop. When the error is detected during a
trip the software will log it only after the trip when the car has stopped. Therefore
the trip-phase is always logged as STANDSTILL in the error log. If the error occurs
too frequently the software blocks the car with FATAL. Manual reset is required.
Extra Info 00: PHS is bouncing during a trip

Diagnostics
Cause Action
Interruption on wiring from photocell to Check the PHS connection from the photocell to the PCB.
interface pcb (traveling cable)
Photocell not working Check the function of the photocell: dirt, holes in the fins (for
attaching a rope) not sealed so that the photocell detects it,
the rope between fins, horizontal distance between fin and
photocell.
Problem with ground connection between Check the ground connection on top of the car and to the
car and machine room machine room.
Faulty input on the IO interface board
Error ID: 0065

NameShort
NameLong PHNR_D_Fault
Description The upper photocell (PHNR_D) is not working properly (software name for error
message: PHNR_D_BOUNCE). The PHS/PHNRD signals are generated by two
photocells on the car. Only used on shaft information systems with incremental
encoders (e.g. TX, TX-R5). On TX-R5 and TX controls the state of the input signal
is logically 1 and electrically 'low' (in_fin) when the input is disconnected (same as
when the car is levelled).
Monitoring Conditions:
1. The car left the fin but the PHNR_D input is in state 'IN_FIN' or
2. the car is at floor level and PHNR_D input is in state 'OUT_FIN' or
3. two PHNR_D signals (transitions) are received within a too short time which
means that the PHNR_D signal is bouncing.
The error does not trigger an emergency stop. When the error is detected during a
trip the software will log it only after the trip when the car has stopped. Therefore
the trip-phase is always logged as STANDSTILL in the error log. If the error occurs
too frequently the software blocks the car with FATAL. Manual reset is required.
Extra Info 00: PHS is bouncing during a trip
Cause Action
Interruption on wiring from photocell to Check the PHNR_D connection from the photocell to the
interface pcb (traveling cable) PCB.
Photocell not working Check the function of the photocell: dirt, holes in the fins (for
attaching a rope) not sealed so that the photocell detects it,
the rope between fins, horizontal distance between fin and
photocell.
Problem with ground connection between Check the ground connection on top of the car and to the
car and machine room machine room.
Faulty input on the IO interface board
Error ID: 0067

NameShort
NameLong KUET_Fault

Diagnostics
Error ID: 0067
Description The monitoring of the door bridging signals (feedback from relays RUET and
RUET1) indicates that they are not working properly. The relays RUET and RUET1
are not switching in parallel, or RUET and RUET1 are switching outside the door
zone fin/magnet.
Comments: Both signals are transmitted via bus communication from the car. The
error does not trigger an emergency stop. An error detected during a trip is logged
only after the car has come to rest. Therefore the trip-phase stored in the log
always appears as STANDSTILL.
This error is also generated on elevators with MOSIS system. For detailed
information about the error cause please refer to the description of the extra
information below. With MoSIS this error is also logged when there is a mismatch
between the numbers of floors learnt by MOSIS and by the control system.
Extra Info The extra information value is a 8 digit hexadecimal number (0xABCDEFGH) and
has to be converted/decoded into binary format (each bit has a specific meaning).
Meaning of value 'GH':
01(hex): Status of KUET and KUET1 are different
02(hex): Enable UET false or outside a floor but KUET or KUET1 is TRUE
03(hex): Enable UET true and at floor but KUET or KUET1 is FALSE
04(hex): Status of KUET_20 and KUET1_20 are different
05(hex): Enable UET_20 false or outside a floor but KUET_20 or KUET1_20 is
TRUE
Additional for MX only:
06(hex): Car at floor without door on side1 but IUET or IUET1 is true
07(hex): Car at floor with door on side1 but IUET or IUET1 is false
08(hex): Car outside floor but IUET or IUET1 is true
09(hex): Car at floor without door on side20 but IUET_20 or IUET1_20 is true
0A(hex): Car at floor with door on side20 but IUET_20 or IUET1_20 is false
0B(hex): Car outside floor but IUET_20 or IUET1_20 is true
Meaning of value 'F':
0(hex): 'KUET' false, 'KUET1' false, 'Enable UET' false
1(hex): 'KUET' true, 'KUET1' false, 'Enable UET' false
2(hex): 'KUET' false, 'KUET1' true, 'Enable UET' false
3(hex): 'KUET' true, 'KUET1' true, 'Enable UET' false
4(hex): 'KUET' false, 'KUET1' false, 'Enable UET' true
5(hex): 'KUET' true, 'KUET1' false, 'Enable UET' true
6(hex): 'KUET' false, 'KUET1' true, 'Enable UET' true
7(hex): 'KUET' true, 'KUET1' true, 'Enable UET' true
Meaning of value 'E': for TX only
0(hex): 'PHS' = OUT_FIN, 'PHNR_D' = OUT_FIN
1(hex): 'PHS' = IN_FIN, 'PHNR_D' = OUT_FIN
2(hex): 'PHS' = OUT_FIN, 'PHNR_D' = IN_FIN
3(hex): 'PHS' = IN_FIN, 'PHNR_D' = IN_FIN
Meaning of value 'D': for MX only
0(hex): 'IUET' false, 'IUET1' false, 'LUET' false
1(hex): 'IUET' true, 'IUET1' false, 'LUET' false
2(hex): 'IUET' false, 'IUET1' true, 'LUET' false
3(hex): 'IUET' true, 'IUET1' true, 'LUET' false
4(hex): 'IUET' false, 'IUET1' false, 'LUET' true
5(hex): 'IUET' true, 'IUET1' false, 'LUET' true

Diagnostics
Error ID: 0067
Extra Info 6(hex): 'IUET' false, 'IUET1' true, 'LUET' true
7(hex): 'IUET' true, 'IUET1' true, 'LUET' true
Meaning of value ‘AB’: for MoSIS only (with bit decoding / (value “CDEFGH”
always '000000')
01(hex): MoUET_RelaisFail is ON.
02(hex): MoUET_WrongFloors is ON.
04(hex): MoUET_reserve2 is ON.
08(hex): MoUET_inLuet is ON.
10(hex): MoUET_CmdOn is ON.
20(hex): MoUET_inDoorZone is ON.
40(hex): MoUET_v_below is ON.
80(hex): MoUET_OK is ON.
Example 1: Error 67 with extra info value 68000000(hex) on MoSIS system
68 (Hex) = 40(hex) + 20(hex) + 08(hex) meaning:
'MoUET_v_below' is ON and
'MoUET_inDoorZone' is ON and
'MoUET_inLuet' is ON
Example 2: Error 67 with extra info value 31000000(hex) on MOSIS system:
31 (Hex) = 20(hex) + 10(hex) + 01(hex) meaning:
'MoUET_inDoorZone' is ON and
'MoUET_CmdOn' is ON and
'MoUET_RelaisFail' is ON
Cause Action
Bad wiring on car Check the connection of the RUET/RUET1 enable- and
feedback-signals to the car interface board.
Check the wiring of the door zone detection devices (PHUET
/ KUET)
Bad environmental conditions (dirt, dust) in Check photocell/magnet switches on car for dirt.
the hoistway
Electrical problems Check the ground connection on the car and the power
supply for the car interface board and the door bridging
device (e.g. PHUET)
Communication problems between control Check the (LON) bus connection from the control cabinet to
cabinet and car the car. Caution: KUET error may indicate a communication
problem caused by another LON node (landings etc.)
Check for EMC problems caused by Schindler or 3rd party
equipment (MX-GC: refer to field information No.291)
Configuration Check if number of floors and shaft layout (front rear doors) in
configuration is matching the floor vanes in the hoistway.
MX-GC: Travel control checks for each access is a KUET
vane is present for front and/or rear side.
Mechanical problem with switches Check mounting of KUET switches/fins
With MoSIS: MOSIS was replaced, e.g. from Perform a learn trip.
other installation (learnt floors mismatch)
Error ID: 0081

NameShort
NameLong TripV_Tacho

Diagnostics
Error ID: 0081
Description The signal from the car position tacho failed during a trip. Travel Control continues
the trip to the nearest floor using the speed tacho feedback from the frequency
converter (motor control). Also applies with MOSIS and SALSIS. With broken CAN
bus connection between MOSIS/SALSIS and control the safety functions are still
operational.
Comments: The speed tacho information is provided by Motor Control as a
handshake to each speed reference telegram (closed loop). This information is
used by Travel Control to calculate position and speed of the car and to continue
the current trip with the speed tacho only. The car stops at the nearest floor; normal
stopping precision cannot be guaranteed. However the car will stop close enough
to the floor so that the door(s) can open normally for passengers to leave the car.
Cause Action
Problem with the signal from the position Check the position tacho as well as its connection to the
tacho interface PCB and the PCB hardware.
Bad/broken wire between position tacho and Check wiring
control cabinet
Faulty position tacho Replace position tacho
EMC problems Check for EMC interferences caused by Schindler or 3rd
party equipment. A very common cause for this error is
missing or insufficient motor cable shielding.
Error ID: 0088

NameShort
NameLong TachoFault
Description Major problem with the position tacho of the car. The position value read from the
position tacho (for incremental or absolute encoders) is inconsistent. The value
representing the car position either jumped (difference between values too big) or
no tacho impulses were detected during the trip.
Remark: always perform a learn trip after exchange of the position tacho or main
pcb. On controls with AGSI/ALSIS always disconnect the position encoder (cable)
with power off.
Extra Info 0 (hex): No signal (speed feedback) from position tacho when starting a trip while
speed reference below the limit for underspeed error. This monitoring is disabled
with active JMOF or when finishing a trip.
1 (hex): During INSPECTION or RECALL trip the car is allowed to move for a
distance of 0.5m with a faulty position tacho (S_TACHO). After a distance of 0.5m
running with V_TACHO (speed feedback from inverter) the control stops the car
with error TACHO_FAULT.
A (hex) / B(hex): The position value read from the position tacho is not in the shaft
range. (Absolute encoder was disconnected during manual trip.)
C (hex) / D(hex): The position value read from the position tacho is not in the shaft
range. (Absolute encoder was disconnected during inspection trip in up direction.)
E (hex): The position value read from the position tacho is not in the shaft range.
(Absolute encoder was disconnected during inspection trip in down direction.)
F (hex): The position value read from the position tacho is not in the shaft range.
An inspection trip in up direction was initiated with the tacho disconnected or with
the elevator out of the shaft range.
10(hex): The position value read from the position tacho is not in the shaft range.
An inspection trip in down direction was initiated with the tacho disconnected or
with the elevator out of the shaft range
10BADCAB(hex): refer to description of error 1501 'Invalid Position'
20BADCAB(hex): refer to description of error 1502 'Position Jump'

Diagnostics
Cause Action
Bad connection/wiring of the position tacho. Check the connection of the position tacho to the control
(cable).
The position tacho is damaged. Check position tacho itself.
Mechanical problems with position Check that the tacho runs smoothly.
tacho/encoder.
Position tacho disconnected. Reconnect position tacho.
Broken circuit on the interface board Replace pcb.
(ASILOGx, ASIXx) for the position tacho.
Error ID: 0092

NameShort
NameLong IVXVF_HW_Fault
Description Monitoring of I/O's in Travel Control detects abnormal status of I/O's (uncontrolled
activation of relays or bad status of inputs). Check extra info for detailed
description of possible cause.
See also error #135
Extra Info 0 (hex)/ 0 (dec): All relays controlled by Travel Control are active unintentionally
A (hex)/ 10 (dec): DRH-U button on the recall panel is pressed without active recall
control JRH; check wiring of JRH / DRH-U
B (hex)/ 11 (dec): DRH-D button on the recall panel is pressed without active recall
control JRH; check wiring of JRH / DRH-D
14( hex)/ 20 (dec): DREC-U button on the inspection panel is pressed without
active inspection control JREC; check wiring of JREC / DREC-U
15 (hex)/ 21 (dec): DREC-D button on the inspection panel is pressed without
active inspection control JREC; check wiring of JREC / DREC-D
16 (hex)/ 22 (dec) DREC-E button on the inspection panel is pressed without
active inspection control JREC; check wiring of JREC / DREC-E.
17 (hex)/ 23 (dec) DREC-U button pressed for more than 30 seconds and no trip
because DREC-E not pressed simultaneously; both buttons must be released
before a new trip is initiated.
18 (hex)/ 24 (dec) DREC-D button pressed for more than 30 seconds and no trip
because DREC-E not pressed simultaneously; both buttons must be released
before a new trip is initiated.
19 (hex)/ 25 (dec) DREC-E button pressed for more than 30 seconds and no trip
because DREC-U or DREC-D not pressed simultaneously; buttons must be
released before a new trip is initiated.
1E (hex)/ 30 (dec): DRH-E button on the recall panel is pressed without active
recall control JRH; check wiring of JRH / DRH-E
32 (hex)/ 50 (dec): The status of the input RTCCON is not same as the status of
the input RTC1CON (check) for more than 0.6 seconds.
33 (hex)/ 51 (dec): The status of the input RTSCON is not same as the status of
the input RTS1CON (check) for more than 0.6 seconds.
34 (hex)/ 52 (dec): The status of the input RTSCON_20 is not same as the status
of the input RTS1CON_20 (check) for more than 0.6 seconds.
5C (hex)/ 92 (dec): Manually bridged safety circuit detected (between taps 3 and 5)
with active inspection control REC. Activation of inspection control on car is not
allowed with bridge safety circuit across the inspection control panel (JREC / JHC)
5D (hex)/ 93 (dec): Used for NA: Manually bridged safety circuit detected (between
taps 3 and 5) with active inspection control REC. Activation of inspection control on
car is not allowed with bridge safety circuit across the inspection control panel
(JREC / JHC)

Diagnostics
Error ID: 0092
Extra Info 64 (hex)/ 100 (dec): refer to description of extra information for error 74.
(monitoring of open safety circuit before the third tap ISKT3 for more than 15
minutes is done with error 74 /changed 20.02.03)
14D (hex)/ 333 (dec): The status of the input JRH is not same as the status of the
input JRHCH (check) for more than 20 seconds.
Cause Action
Handling problem (wrong manipulation on none
recall- or inspection panel)
Grounding or EMC problem Remove all possible ground loops from the corresponding
pcb (i.e. use AC mains socket in the control cabinet to power
the service laptop).
HW fault 1) Check wiring
2) Check function of I/Os' (refer to extra info)
3) Replace the pcb (IVXVF / GCIO) if necessary
Jumper in safety circuit Remove jumper
Extra info 14D (hex)/ 333 (dec): LDBCS plug If ASIXA 33 PCB, the operation with LDBCS needs that JRH
in BYPASS position and JRH switch not is switched ON before LDBCS plug is put on BYPASS
activated (only for MX-GC) position
Error ID: 0094
NameShort
NameLong DoorLockFault
Description The control checks if the door state (open) matches with the information read from
the safety circuit (KTS and KTC). The safety circuit shows closed/locked shaft or
car door (taps ISKT4 or ISKT5 on) while the door status is 'open'. With TX-GC2 the
control can detect whether a KTS opened on the front side or the rear side
because the contacts operate the relays RTS and 2RTS.
Together with this error a SW_Warning (error #70) may be logged which provides
additional information for diagnostics. For the description of the extra information in
the SW_Warning see description here.
With newer SW (2011/12) the software will log errors #1527 - #1535 instead.
Extra Info 5(hex): Retiring cam (RCAM) activation error
6(hex): Retiring cam (RCAM) release error
28(hex): Monitor status of safety circuit (bridged contacts)
29(hex): Monitor status of safety circuit (bridged contacts)
2A(hex): Shaft Door Contact KTS bridged/bypassed
2B(hex): Car Door Contact KTC bridged/bypassed (KOREA)
2C(hex): Both contacts KTS and KTC are bridged, or a bridge is across KTS and
KTC
2D(hex): Shaft Door Contact KTS bridged
2E(hex): Car Door Contact KTC bridged (detection only at the end of a trip)
940(hex): Shaft Door Contact KTS bridged in safety circuit
941(hex): Car Door Contact KTC bridged in safety circuit
942(hex): Door side 1 open and inconsistent state of KTC/KTS (TX-GC2)
943(hex): Door side 2 open and inconsistent state of KTC2/KTS2 (TX-GC2)
944(hex): Door lock problem during trip preparation (TX-GC2)
945(hex): Door lock problem during trip preparation (MX-GC/TX-GC)
Description of the extra information value for the message SW_Warning (70) sent
together with error'Door Lock Fault' with extra info value 942(hex):
80(hex): Incorrect status of sdoor coil - coil of shaft door lock relay (NA)

Diagnostics
Error ID: 0094
Extra Info 40(hex) : Incorrect status of sdoor contact - contact of shaft door lock relay (NA)
20(hex) : Incorrect status of cdoor coil - coil of car door lock relay (NA)
10(hex) : Incorrect status of cdoor contact - contact of car door lock relay (NA)
08(hex) : Incorrect status of rtscon - shaft door safety 1 input (EUAP)
04(hex) : Incorrect status of rts1con - shaft door safety 2 input (EUAP)
02(hex) : Incorrect status of rtccon - car door safety 1 input (EUAP)
01(hex) : Incorrect status of rtc1con - car door safety 2 input (EUAP)
Description of the extra information value for the message SW_Warning (70) sent
together with error'Door Lock Fault' with extra info value 943(hex):
80(hex): Incorrect status of sdoor_coil_20 - coil of shaft door lock relay for rear
door (NA)
40(hex): Incorrect status of sdoor_contact_20 - contact of shaft door lock relay for
rear door (NA)
20(hex): Incorrect status of cdoor_coil_20 - coil of car door lock relay for rear door
(NA)
10(hex): Incorrect status of cdoor_contact_20 - contact of car door lock relay for
rear door (NA)
08(hex): Incorrect status of rtscon_20 - rear shaft door safety 1 input (EUAP)
04(hex): Incorrect status of rts1con_20 - rear shaft door safety 2 input (EUAP)
02(hex): Incorrect status of rtccon - car door safety 1 input (EUAP)
01(hex): Incorrect status of rtc1con - Incorrect status of car door safety 2 input
(EUAP)
Cause Action
Problem with the door contacts Check the door contacts and the wiring to the door interface
board.
Safety chain Check for jumpers in the safety chain.
Error in configuration (PCT) Check door parameters for automatic/manual doors (if the
parameter DOOR TYPE is set to automatic doors on a
installation with manual doors the error occurs with each door
opening)
Error ID: 0095

NameShort
NameLong ETSL_Overspeed
Description Overspeed detected by the ETSL device within the upper or lower deceleration
zones in the hoistway.
This event is generated according to the status signals (parallel inputs) from the
ETSL device (see actual wiring diagram). A separate contact from the ETSL
device is used to interrupt the safety circuit (independent from the status
information signals). See also TK of ETSL device for more information.
Extra Info None.
Cause Action
Wrong parameter values Check the values for parameters A2 (acceleration) and A6
(deceleration).
Other drive system error Check the operation of the drive system.
Installation issue Check the vertical position of the vanes in the shaft end
according to K603046.

Diagnostics
Error ID: 0096
NameShort
NameLong ETSL_VaneError
Description Unsafe operating condition detected by the ETSL device while scanning the
vanes.
ETSL. A separate contact from the ETSL device is used to interrupt the safety
circuit (independent from the status information signals).
Extra Info None.
Cause Action
Wrong alignment between PHVKSE and Check the alignment.
vanes/metal stripe.
Deformed or twisted metal stripe in the Check the tension of the metal stripe.
hoistway
A gap in the check track without a measure Cover the gap with something that interrupts IR-light. A single
vane in front of it. plastic tape is probably not enough.
There is no cutout behind a measure vane or Check the cutouts.
cutout partly covered.
Dirt on optical parts. Clean the lenses in the gap of the PHVKSE with a clean
cloth.
Error ID: 0097

NameShort
NameLong ETSL_DeviceError
Description Unsafe operating condition detected by the ETSL device (internal error).
ETSL. A separate contact from the ETSL device is used to interrupt the safety
circuit (independent from the status information signals).
Extra Info None.
Cause Action
Internal error of PHVKSE Cycle power (off/on) on the PHVKSE, repeat the last trip and
test the ETSL system. Replace the PHVKSE if the same error
message appears again.
If the same error only happens now and then, check the
electrical environment for possible EMC problems
(unpermitted strong electro-magnetic interference by some
other defective component like conductors etc.)
Error ID: 0099

NameShort
NameLong RSK_Fault
Description The software detects a problem with the operation of the relays RSK/RSK1/RFE.
During the preparation for a trip the software checks the switching of the relays
RSK/RSK1 (RFE) and interrupts the preparation in case of a problem. See
description of the extra info value for the monitoring conditions.
Location of safety circuit relays RSK/RSK1/RFE:
MX: ASIXx
TX: SKE
TX2: SKEAPx / SKNAx

Diagnostics
Error ID: 0099
Extra Info 00(hex): problem with RFE relay; relay not off in preparation phase
WAIT_FOR_RFE_OFF (for TX controls)
00(hex): problem with RSK relay; relay not off in preparation phase (for TX2
controls)
01(hex): problem with RSK1 relay; relay not off in preparation phase (for TX2
controls)
0A(hex): problem with RSK/RSK1 relay; relay not on in preparation phase
WAIT_FOR_RSK_ON after relay is enabled by the software (for TX, MX,TX2
controls)
0B(hex): problem with RSK/RSK1 relay; relay not off in preparation phase
WAIT_FOR_RSK_OFF (for TX, MX controls)
Cause Action
Faulty feedback contact of the relays RSK / Check wiring and/or functionality of relays RSK / RSK1.
RSK1
RSK/RSK1 does not drop off as expected Replace relays RSK/RSK1 or pcb which holds the relays.
RSK/RSK1 does not turn on during trip Check the safety circuit (ISKT4, ISKT5).
preparation as expected
Error ID: 0100

NameShort
NameLong RFE_Fault
Description Problem with the feedback contact of the relay RFE (malbehavior of relay). The
relay RFE is monitored during the trip preparation. Relay RFE has to drop after
relays RSK & RSK1 have picked.
Comments: This error is only generated if the trip initiation circuit is with relay RFE
(not valid for MX-GC and TX-GC2). See also actual wiring diagram.
Extra Info None.
Cause Action
RFE is turned on and does not pick up within Check the wiring and the functionality of RFE.
5 seconds (Timeout)
Check all contacts/contactors in the RFE circuit (SH, RSK,
RF, etc).
RFE does not turn off Check RSPFE.
Error ID: 0131

NameShort
NameLong SI_KNE_Fault
Description Message sent by MoSis due to a status change of the KNE relay (on MoSis).

Diagnostics
Error ID: 0131
Extra Info The extra information value is a 8 digit hexadecimal number (0xABCDEFGH)
A=0: KNE relay closed (normal)
A=1: KNE relay open (reason for opening see other digits)
B=_: RESERVED FOR FUTURE USE
C=1: KNE open because of detection of unintended car movement
D=1: MoSis internal hardware or software error relating to the KNE. Check the
error-log (MoSis) for further info.
E=1: Relay test failure (KneRelayFail)
F=1: Car travelled past the end of the known shaft range (StrangePlace). MoSis
was never at this position before (past the last floor).
G=1: Travel past last known floor (Overtravel)
H=1: Pre-commissioned state; no floors discovered (Precom)
Cause Action
Car is in KNE zone (below bottom floor or Move car out of KNE zone.
above top floor)
Unintended car movement detected Refer to description for error 139
Internal error in MOSIS Refer to description for error 1515
Error ID: 0132

NameShort
NameLong SI_ETSL_Fault
Description Message from MoSis together with status change of ETSL relay. This relay opens
under the following conditions:
- ETSL speed limit exceeded (emergency terminal speed limit)
- NTSD speed limit exceeded (normal terminal stopping device)
- Internal error in MOSIS
Extra Info The extra information value is a 8 digit hexadecimal number (0xABCDEFGH)
A=0: ETSL relay closed (normal)
A=1: ETSL relay open (reason for opening see other digits)
B=_: RESERVED FOR FUTURE USE
C=1: NTSD overspeed. (Normal Terminal Stopping Device)
D=1: MoSis internal hardware or software error relating to the ETSL. Check the
error-log (MoSis) for further info.
E=1: Relay test failure (EtslRelayFail)
F=1: Commissioned speed exceeded (MaxSpeed).
G=1: Pre-commissioned limit of 1m/s exceeded (1mps)
H=1: Exceeded ETS/ETSL curve towards terminal (Curve)
Cause Action
Car speed exceeded the limit for ETSL Check parameter for speed and acceleration. Check
monitoring; ETSL monitoring is done by configuration data of drive.
MOSIS. This error will occur during
acceptance test for ETSL.
Car speed exceeded the limit for NTSD Check parameter for speed and acceleration. Check
monitoring; NTSD monitoring is done by configuration data of drive.
MOSIS. This error will occur during
acceptance test for NTSD.
Internal error in MOSIS Refer to description for error 1515

Diagnostics
Error ID: 0138
NameShort
NameLong Brake Not Set
Description Brakes do not close at the end of a trip. After a normal (automatic) trip the machine
brakes do not close as expected (status of KB contacts show open brakes) after
the 'brake off' command timeout following the 'SB off' command. This is a critical
situation because potentially no mechanical torque is applied to the traction
sheave. In this situation the inverter remains powered and keeps the car on the
floor. The door(s) are closed immediately and remain closed (door open button is
disabled).
Version 1: With closed doors the inverter is switched off and the elevator is blocked
permanently with fatal error.
Version 2: The monitoring of the closing of the brakes was extended with a safety
parking trip. As soon as the door(s) are closed the elevator performs a slow speed
trip top the top floor where the inverter is switched off.
Before opening the doors manually to release the passengers a check must be
done to confirm that the brake applies sufficient mechanical torque to hold the car.
On elevators with only one physical switch on the brake (KB) a safety parking is
done if the KB does not indicate closed brake at the end of a trip.
Extra Info ndef
Cause Action
Brake does not close due to mechanical Check brake for correct function (sufficient mechanical torque
obstruction applied to machine)
Problem with wiring of KB contacts to Check wiring and operation of KB contacts
control
Faulty input circuit for KB contacts (both!) Check input status of KB contacts. Replace pcb if necessary
Error ID: 0139

NameShort
NameLong Unintended Car Movement
Description Unintended car movement detected. The unintended movement detection device
opens the safety circuit. The detection device depends on the control system and
the area. The control shuts down the elevator until manual reset of FATAL state.
No car movement is allowed until the unintended movement detection device is
manually reset. Unintended movement protection device is required by the
following codes: A17.1 / Hong Kong Code of Practice (Am.10) / Korean Code /
EN81-1 Am.3. (list subject to change)
The error is also logged when the acceptance test for unintended movement is
performed. The limits for the detection of unintended movement depend on the
detection device. With MoSIS the limits are: distance from floor > 100mm or speed
>0.3m/s.
For NA: a unintended movement of the traction sheave (motor encoder) on the
motor detected by the inverter is considered as an unintended movement. The
inverter logs the error #737.
The control also logs the error.
Extra Info not used
Cause Action
Problem with traction system Check machine brake and friction between traction sheave
and ropes.
Wrong car movement (direction/speed) Check load measuring system, position tacho.
during re-levelling

Diagnostics
Error ID: 0140
NameShort
NameLong Safety T4B
Description The safety circuit opened before the tap (ISKT4B) but after the previous tap
(ISKT4). This safety circuit tap is only available on specific hardware (e.g.
LONICK).
Comments: Downward safety circuit tap inputs (ISKT5 etc.) will not create
corresponding error messages. Refer to actual wiring diagram for contacts causing
the error.
Extra Info = 00000000: no information
= xxyyyyyy: First 2 digits (xx) hold information for software development only.
The remaining 6 digits (yyyyyy) show the car position (decimal value in mm) when
the error occurred.
Cause Action
Bad landing door contact(s) KTS Check switching of landing door contacts.
Bad wiring of landing door contact(s) in Check wiring to and between landing door contacts.
safety circuit
Faulty input on interface board for safety Check the interface board (LONICK) and the connections to
circuit tap inputs the safety circuit. Replace board if necessary.
Error ID: 0141

NameShort
NameLong Safety T1
Description The safety circuit opened before the first tap (ISKT1) or there was a problem with
safety circuit power supply.
Comments: This error may be logged after main power supply is disconnected.
Other safety circuit tap inputs (ISKT2 etc.) will not create corresponding error
messages when the input T1 opens.
New error messages introduced (May 10, 2011) for monitoring of safety circuit
supply (message numbers 1587, 1588, 1589, 1590).
Extra Info = 00000000: no information available
= xxyyyyyy: First 2 digits (xx) show diagnostics information for the safety circuit
supply (SKS). The SKS board monitors the safety cuircuit supply for undervoltage,
overvoltage and overcurrent.
the error occurred.
Extra information safety circuit supply (xx):
00: no power safety circuit supply
For control systems with pcb SKS the following extra information is provided:
01: Safety circuit voltage at the relays RSK/RSK1 too high (SAFVRHI). In the event
of a HW failure (e.g. malfunction of the voltage regulation) the safety circuit power
supply is switched off if the voltage at the relays is too high. The voltage limit is
27.0 to 28.0 volts.
02: Safety circuit supply voltage too low (SAFVLO). In the event of a HW failure
(malfunction of the voltage regulation) the safety circuit power supply is switched
off if the output voltage is too low. The voltage limit is 19.0 to 20.0 volts.
03: Safety circuit supply voltage too high (SAFVHI). In the event of a HW failure
(malfunction of the voltage regulation) the safety circuit power supply is switched
off if the output voltage is too high. The voltage limit is 60.1 to 60.7 volts.

Diagnostics
Error ID: 0141
Extra Info 04: Safety circuit Overcurrent (SAFOVCURR). In the event of a short circuit to
GND or leakage current to GND the safety circuit supply is switched off. The
overcurrent limit is 300 to 500mA.
When the SKS detects a fault on the safety circuit supply the LED on the SKS
board indicates on which channel (1-5) the error occurred. This information
(channel number) is not available to the software.
Cause Action
No supply on the safety circuit Check the power supply for the safety circuit.
In case of regulated voltage supply: Reset short circuit
protection for safety circuit supply.
Relais RKPH Check the phase control relay RKPH (if available).
Faulty input on interface board for safety Check the interface board and the connections to the safety
circuit tap inputs circuit. Replace board if necessary.
Error ID: 0142

NameShort
NameLong Safety T2
Description The safety circuit opened before the second tap (ISKT2) but after the first tap
(ISKT1).
the error.
the error occurred.
Cause Action
Open contact in safety circuit Check the corresponding section in the safety circuit.
Bad wiring of contact(s) in safety circuit Check wiring to and between contacts.
Error ID: 0143

NameShort
NameLong Safety T2A
Description The safety circuit opened before the tap (ISKT2A) but after the first tap (ISKT1).
the error.
the error occurred.
Cause Action

Diagnostics
Error ID: 0144
NameShort
NameLong Safety T2B
(ISKT2A).
the error.
the error occurred.
Cause Action
Error ID: 0145

NameShort
NameLong Safety T3
Description The safety circuit opened before the third tap (ISKT3) but after the second tap
(ISKT2).
the error.
= xxyyyyyy: First 2 digits (xx) show information for diagnostics (see below).
the error occurred.
Extra information (xx):
64 (hex)/100 (dec): Safety circuit is open before the third tap (ISKT3) for more than
15 minutes. The error will not occur with switches JHC or JHM on or active recall-
or inspection control.
Cause Action
Error ID: 0146

NameShort
NameLong Safety T3A
Description The safety circuit opened before the tap (ISKT3A) but after the previous tap
(ISKT2).
Comments: Downward safety circuit tap inputs (ISKT3B etc.) will not create
the error.

Diagnostics
Error ID: 0146
the error occurred.
Cause Action
Error ID: 0147

NameShort
NameLong Safety T3B
(ISKT3A).
the error.
the error occurred.
Cause Action
Error ID: 0148

NameShort
NameLong Safety T4

Diagnostics
Error ID: 0148
Description Safety circuit tab T4 is open unexpected.
Depending on the controller product safety circuit design this tab monitors the
landing door contacts KTS or the door contacts KTC.
The safety circuit is open before the fourth tap (ISKT4) but after the third tap
(ISKT3). The message is logged if:
a) the safety circuit opens during a trip due to a landing door contact (any) which
opens unexpectedly.
b) the safety circuit does not close as expected after the door has closed.
Comments: Downward safety circuit tap input (ISKT5) will not create
corresponding error message. Refer also to actual wiring diagram for contacts
causing the error.
If this error persists increase the value of the drive parameter 'DOOR_CONTACT-
DELAY' to 50 (corresponds to 0.5 s), 70 or 100. This is time the logic waits during
startup from the first time the SKD signal 5 (safety end) is received to the moment
when the door overbridging is disabled. During this time, the door contacts may
bounce. Do not increase the value for this parameter too much because it will
further increase the trip preparation timer. More care should be taken to improve
the adjustment of the door movement.
the error occurred.
Cause Action
Bad landing door contact(s) KTS Check switching of landing door contacts KTS.
Bad wiring of landing door contact(s) in Check wiring to and between landing door contacts.
safety circuit
Error ID: 0149

NameShort
NameLong Safety T5
Description The Safety circuit tab T5 is open unexpected.
Depending on the controller product safety circuit design, this tab monitors the car
door contacts KTC or the landing contacts KTS.
The safety circuit is open before the fifth tap (ISKT5) but after the fourth tap
(ISKT4). The message is logged if:
a) the safety circuit opens during a trip due to a car door contact (front or rear)
which opens unexpectedly.
Comments: Refer also to actual wiring diagram for contacts causing the error.
If the pre-opening of the door during landing is not working properly this event may
appear instead of error 'SafetyRTS'. If this error persists, change the drive
parameter 'DOOR_CONTACT_DELAY' from 50 (0.5 s) to 70 or 100. This is time
the logic waits during startup from the first time the SKD signal 5 (safety end) is
received to the moment when the door overbridging is disabled. During this time,
the door contacts may bounce. Do not increase the value for this parameter too
much because it will further increase the trip preparation timer. More care should
be taken to improve the adjustment of the door movement.

Diagnostics
Error ID: 0149
the error occurred.
Cause Action
Door contacts KTC Check switching of car door contacts
Bad wiring of car door contacts in safety Check wiring to car door contacts
circuit
Door bridging circuit Check the door bridging circuit
5.3.3 20..5999 0020_5999_Others
Error ID: 0020

NameShort
NameLong Elevator is available
Description
5.3.4 150..199 Variodyn E
5.3.5 200..299 Door Control
Error ID: 0202

NameShort
NameLong DoorOperErr
Description Door operator error. Error detected on the door drive behavior by door control.
The door can not reach its end position. After several attempts the door will be
blocked.
Extra Info 01: KET-O and KET-S are active at the same time (illegal status)
02: KET-S does not switch when expected
03: KET-O does not switch when expected
04. Output VST-S is faulty or has short circuit.
05: Output VST-O is faulty or has short circuit.
06: The door drive does not move the door, although VST-O / VST-S is active.
07: For manually-operated or semi-automatic doors the RTS contact feedback
(shaft door closed) is not active after a close command has been given. Either the
shaft door is open or the shaft door contact (RTS) is faulty.
08: Door motor moves the door in the wrong direction
For extra info 02 and 03 the maximum time is according the value of the PCT
parameter 'Max Door Travel Time' (PCT: P_KAB_MAX_DOOR_TRAVEL_TIME). If
this parameter does not exist or the value of the parameter is 0, then a default
value of 15 seconds is taken for the monitoring of the door travel time.

Diagnostics
Cause Action
Extra info 1,2,3 Check the door contacts KET-O, KET-S and the related
wiring
Check if the door can reach the end position
mechanically
Check for dirty door guides.
Extra Info 3: Mechanical unlocking does not Check if the door unlocking works
function; the door can not open
Extra info 4,5 Check the connections to the door drive
Replace the interface board
Extra info 6 Check the door drive board and connections (fuse and power
supply).
Check the physical door parts (V-belt)
Extra info 7 For manually-operated or semi-automatic doors check if the
landing door is closed.
Check the landing door contacts and wiring.
Extra info 8 Check if electrical phase sequence is correct.
Check if VST-O/VST-S or wiring is mixed up
Error ID: 0203

NameShort
NameLong ThermoDoorMot
Description Thermal protection device of the door motor indicates excessive temperature.
The thermal contact KTHMT of the door motor is active. After detection of the
overtemperature the control attempts to open the door once so passengers are not
trapped. The door control allows that the current door movement is finished and
the magnetic brake will be released; all outputs from the door drive are then
switched off and the door control blocks the door. The door can still be moved
manually.
For door drives with inverter (e.g. IDD, SEMATIC) the error is logged when the
door inverter is blocked due to a severe error detected by the inverter software. In
this situation the door is no longer able to operate.
Cause Action
Jammed door / excessive torque Check the mechanical door drive and the door for smooth
operation
Problem on door drive / inverter Check the door inverter
Error ID: 0204

NameShort
NameLong DoorRevDevErr
Description Door reversing device error. The error is generated by the door control when:
a) the same reversing device was active permanently twice during 5 complete
opening and closing cycles.
b) a reversing device is permanently active so that even after the final timer has
timed out the door can not close.

Diagnostics
Error ID: 0204
Extra Info 01: DT-O / KTL is permanently active.
02: RPHT is permanently active (Light curtain).
03: Radar is permanently active (REP).
04. Reserve Reserving Device is permanently active.
05: Closing force limiter KSKB is permanently active.
06: DT-S is permanently active.
07: KTHMT is permanently active.
08: RTS (safety circuit tap) is permanently inactive (only for manual shaft door).
Cause Action
Damaged or badly adjusted reversing device Check the function of the reversing device indicated by the
extra info value.
Bad connection or faulty input on the Check the connection from the interface board to the
interface board on car (e.g. reversing device. Replace interface board.
PIOC/ICE/TIC/LONIBV/LONIC etc.). See
actual wiring diagram for details.
Error ID: 0207

NameShort
NameLong CloseSeqErr
Description Door close sequence error. The error is generated by the door control when:
a) a reversing device is activated during x attempts to close the door repeatedly on
the same floor and if this occurred twice within five trips.
b) the same reversing device becomes active too often (8 times = warning, 12
times = error) during door closing.
Extra Info meaning of value:
01: DT-O is triggered repeatedly.
02: RPHT is triggered repeatedly.
03: Radar is triggered repeatedly.
04: Reserve reserving device is permanently active.
05: Closing force limiter KSKB is triggered repeatedly.
Cause Action
Damaged or badly adjusted reversing device Check the reversing devices.
Bad connection or faulty input on interface Check the connection from the interface board to the
board on car (e.g. reversing device. Replace interface board.
PIOC/ICE/TIC/LONIBV/LONIC etc.)
Error ID: 0208

NameShort
NameLong DoorDevErr
Description Door device error. Door control malfunction. See extra info for details.
Extra Info Identifies the causing component:
01: Input from light barrier (PROGARD L etc.).
02: I/O-Bus error.
03: JHCT pressed.
04: Door motor power failed.
05: Door node communication failed or power fail for door node.

Diagnostics
Cause Action
Faulty device Examine the device and replace it if necessary.
Extra Info = 2 Check I/O-bus cable.
Check I/O-bus drivers.
Extra Info = 3 Check JHCT switch and the related wiring.
Extra Info = 4 Check the power supply on the door driver pcb (fuse).
Extra Info = 5 Check LON bus and 24V power supply to door interface
board.
Check LON node and its rotary switch settings.
Check LON bus to other nodes. (remove for test)
Check pcb EBLON (TX/TX2) or ASIXx (MX).
Check for EMC disturbances.
5.3.6 300..399 Varidor70 Door Drive
5.3.7 400..599 elevator
Error ID: 0401

NameShort
NameLong VCOM Node Connected
Description The control software detects a new VCOM bus node (subsystem) on the bus. The
message is logged when the connection to the node/subsystem is established
after it was interrupted for some time or if the node/subsystem is reinitialising. A
manual reset of the elevator control causes this message to be logged on the other
elevators in the group.
Extra Info (8 digit hex. value xABCDEFGH).
Value of digits ABCDEF: information for R&D only
Value of digits GH: identification number of the VCOM node (pcb):
Old encoding (SUBSYS):
x07 = Controller elevator 1
x0A = Controller elevator 4
x0B = Controller elevator 5
x0C = Controller elevator 6
x0D = Controller elevator 7
x0E = Controller elevator 8
New encoding "LOGADDR"

Diagnostics
Error ID: 0401
Extra Info x81 = Controller elevator 8
xD9 = E-Vision PC
xFA = PC_1 (SID Mainstation or M10 overlay)
xF9 = PC_2 (SID Mainstation or M10 overlay)
xF8 = Gateway Interface Board (GW/GW2)
xD1 = SID embedded elevator 1 (PTG1/2)
Examples:
Extra info value = AF56E131: Controller of Elevator #3 connected to VCOM
Extra info value = 00000081: Controller of Elevator #8 connected to VCOM
Extra info value = 2901E5FA: SID PC (#1) connected to VCOM
Cause Action
Reset button pressed and released none (Normal behavior)
Power switched on none (Normal behavior)
VCOM bus cable connected none (Normal behavior)
Ethernet hub/switch powered on none (Normal behavior)
Error ID: 0402

NameShort
NameLong VCOM Node Disconnected
Description The control software detects that a VCOM bus node (subsystem) is no longer
present. The message is logged after the connection to a node/subsystem is
interrupted or when the node/subsystem is reinitialising. A manual reset of the
elevator control causes this message to be logged on the other elevators in the
group.
Extra Info (8 digit hex. value xABCDEFGH).
Value of digits ABCDEF: information for R&D only
Value of digits GH: identification number of the VCOM node (pcb):
Old encoding (SUBSYS):
x0A = Controller elevator 4
x0B = Controller elevator 5
x0C = Controller elevator 6
x0D = Controller elevator 7
x0E = Controller elevator 8
New encoding "LOGADDR"

Diagnostics
Error ID: 0402
Extra Info x31 = Controller elevator 3
xD9 = E-Vision PC
xFA = PC_1 (SID Mainstation or M10 overlay)
xF9 = PC_2 (SID Mainstation or M10 overlay)
xF8 = Gateway Interface Board (GW/GW2)
Examples:
Extra info value = AF56E131: Controller of Elevator #3 disconnected to VCOM
Extra info value = 00000081: Controller of Elevator #8 disconnected to VCOM
Extra info value = 2901E5FA: SID PC (#1) disconnected to VCOM
Cause Action
Reset button pressed none (Normal behavior)
Power switched off none (Normal behavior)
VCOM cable for group bus (Ethernet or none (Normal behavior)
RS485) manually unplugged
Bad cable connection, EMC, HW defect, If this message appears very often without an obvious
VCOM bus termination switches on EBCOM reason, check the VCOM bus connection/termination and
set wrongly; Ethernet hub/switch powered test the corresponding VCOM node to verify its operation;
off exchange pcb it if necessary. Check shielding of bus cable.
Error ID: 0407

NameShort
NameLong COM Bus Stress
Description COM_BUS_STRESSED. The communication System VCOM does not have
enough time to work through the telegram buffer on the Data Link level. External
messages, which come in through the bus, might get lost. Reliable operation is no
longer guaranteed.
Extra Info stress_id from the VCOM_upcall VCOM_BUS_STRESSED
01 = elevator bus transmit stressed
02 = elevator bus receive stressed
03 = group bus transmit stressed
04 = group bus receive stressed

Diagnostics
Cause Action
Bus is faulty Check elevator -, groupbus if all links and terminators are
functional.
Check the communication of all subsystems which are
connected with the Bus.
Too many messages are generated in a Trace the telegram traffic in order to determine the source of
certain period of time the telegram flood and test the corresponding subsystem to
verify its operation and if necessary to exchange it.
Another subsystem is not working properly The problem might be caused by faulty operation of another
subsystem. To locate the faulty subsystem, separate every
single subsystem from the bus until the problem disappears.
Error ID: 0412

NameShort
NameLong KTHM-Service
Description Overtemperature in machine room or hoistway detected.
Extra Info 8 digit hex number: 0xAABBCCDD where:
AA: not used (always 00)
BB: represents the status of input KTHS [elevator input]
CC: represents the status of input KTHBRM [elevator input]
DD: represents the status of input KTHM [elevator group]
examples:
00000001 (hex): KTHM is active
00000100 (hex): KTHBRM is active
00010000 (hex): KTHS is active
Cause Action
Overtemperature detected none related to elevator control
Temperature sensor faulty Replace sensor
Fault in wiring of sensor Check wiring
IO Interface board for sensor connection Check interface board and replace if necessary
faulty (input electronics)
Connector of cable to sensor not plugged in. Check connectors
Error ID: 0413

NameShort
NameLong TAB-Service
Description Technical out of service operation activated. The TAB service is activated when a
peripheral IO board with critical IO's is no longer alive (loss of communication).
Critical I/Os are marked in the actual wiring diagram and BMK lists (e.g. Fire
Switch JBF, Emergency Power RNO, Earthquake KEB).
Remark: TAB may also occur if a group is temporarily divided. With the SMLCD
command “Service Visit” TAB can be bypassed for trouble shooting.

Diagnostics
Error ID: 0413
Extra Info The extra information is a 8 digit hex code (Example: x020E8903). The code
identifies the peripheral LON IO board causing the activation of the TAB service.
For BIO bus nodes the extra information is 0.
Meaning per digit for LON boards: xABCDEFGH
(refer to error 1209 'Missing Node' for the description of the Board Id and the Board
Type)
AB: Board Id
CD: Board Type
EF: Subnet id
GH: Node id
Cause Action
Missing I/O board(s)/node(s) on the user bus check peripheral I/O boards (faulty or disconnected); see
(CAN / LON / BIO2) error log for error 'missing node'.
MX/TX2: A critical I/O was configured and Always execute the 'Freeze' command after configuration
then removed (reconfigured). This I/O may and verification of IOs.
be hard to find because it's not visible in
CADI.
Error ID: 0415

NameShort
NameLong SID Alive
Description ndef
Extra Info ndef
Error ID: 0416

NameShort
NameLong SID Dead
Description ndef
Extra Info ndef
Error ID: 0476

NameShort
NameLong Elevator Operation Interrupted
Description Message indicates the interruption of the elevator operation due to the temporary
or permanent activation of the Fatal service (elevator breakdown) used to block the
elevator temporary or permanent after a severe error condition in a subsystem
(drive, door etc.) is detected. With active fatal service the elevator is no longer
available for transport. When the elevator recovers from FATAL service the control
logs the message 477 Elevator Operation Resumed.
See value of extra information for further details about:
- predefined duration of temporary or permanent active fatal service
- current service before activation of fatal service
- error number which caused the activation of the fatal service (reason)

Diagnostics
Error ID: 0476
Extra Info Interpretation (decoding) of the 8 digit hex. value (0xABCDEFGH)
Value of 'ABCD' (Bit 16 to Bit 31): Value of the error number that caused the fatal
service.
For Example: For Error number 300 (dec) ‘ABCD’ will be 012C(hex). Dec300 =
Hex12C
Value of 'EF'(Bit 8 to Bit 15): Service Id. number of the Current Service when the
error occurred.
For Example:
01(dec)/01(hex): Normal Service 'N'
10(dec)/0A(hex): Inspection Service 'INS'
14(dec)/OE(hex): Unavailable Service 'UNV'
27(Dec)/1B(hex): SAB Service
Value of 'GH'(Bit 0 to Bit 7):
0000 0000(bin)/00(hex): Fatal Service with Permanent Blockage
0000 0001(bin)/01(hex): Fatal Service with Short Blockage
0000 0101(bin)/05(hex): Fatal Service with Long Blockage
0001 1110(bin)/1E(hex): Fatal Service with Blockage from Door Module
(Permanent Blockage)
Cause Action
A error occurred which sets the elevator to Please refer to the extra information of this message for the
status 'fatal'. This message itself is not an causing error.
error.
Error ID: 0477

NameShort
NameLong Elevator Operation Resumed
Description The message indicates deactivation of FATAL service; the elevator resumes
operation. See also error 476 for description of activation of FATAL service
(temporary or permanent).
See value of extra information for further details about:
- cause of fatal service reset (manual reset of permanent or temporary fatal service
or time-based reset of temporary fatal service)
- current service before activation of fatal service
- error number which caused the activation of the fatal service (reason)

Diagnostics
Error ID: 0477
Extra Info Interpretation (decoding) of the 8 digit hex. value (0xABCDEFGH)
Value of 'ABCD': Value of the error number that caused the activation of FATAL
service.
Example: if the value of ABCD is 012C(hex) it needs to be converted to decimal
value:
Hex012C => Dec300 => Error 300 caused the Fatal Error (use calculator or
smartphone app to convert).
Value of 'EF'(Bit 8 to Bit 15): Service Id. number of the active (current) service
before Fatal service ON (see error 476)
For Example:
01: Normal Service 'N'
0A: Inspection Service 'INS'
0E: Unavailable Service 'UNV'
1B: SAB Service
Value of 'GH': Fatal Reset cause
00: Fatal service OFF after Reset Timer expired
01: Fatal service Off after Manual Reset
Cause Action
not applicable (the message 'Fatal Error OFF'
is not an error)
Error ID: 0478

NameShort
NameLong OVERLAY failure
Description The message indicates a status change of the overlay Master and/or Slave PC
(M10 overlay/Schindler ID) detected by the control software. This message is
generated when the communication with the Overlay Master/Slave PC (M10 or
Schindler ID) fails.
Extra Info Interpretation of values:
0101(hex): PC1 ok, PC2 failed, Communication to overlay OK
0011(hex): PC1 failed, PC2 ok, Communication to overlay OK
0000(hex): Communication Failure
Cause Action
Failure of master or slave overlay (PC) Check overlay PC and replace if necessary
Communication link to master or slave Check connection between control and overlay PC.
overlay (PC) disconnected Reestablish communication
Overlay software (application) no longer Check operation of overlay application
responding or shut down
Problem with interface board on Replace interface board
master/slave overlay PC
Error ID: 0498

NameShort
NameLong Group 24VDC Fail

Diagnostics
Error ID: 0498
Description The Group 24V supply voltage is out of tolerance (24V20%). If the warning
'elevator24VDCFail' occurs simultaneously, the system may be running on the
backup battery power only.
Note: The battery charge level is tested every hour and after a manual reset. After
either 'elevator24VDCFail' or 'Group24VDCFail' event the battery is not tested,
since testing the battery could eventually interrupt power to the control.
Extra Info ndef
Error ID: 0499

NameShort
NameLong elevator 24VDC Fail
Description The elevator 24V supply voltage is out of tolerance (24V20%). If the warning
'Group24VDCFail' occurs simultaneously, the system may be running on the
backup battery power only.
Note: The battery charge level is tested every hour and after a manual reset. After
either 'elevator24VDCFail' or 'Group24VDCFail' event the battery is not tested,
since testing the battery could eventually interrupt power to the control.
Extra Info None
Error ID: 0501

NameShort
NameLong Battery Charging
Description The errors occurs if the control cannot perform the battery test because the battery
is being charged. After that the control attempts to check the battery every 5min.
The battery charging is done automatically by the hardware. Refer also to error
message 'Battery Charge Time Expired'.
Remark: This event is normal following a power failure. If the battery requires
increasingly charging, the battery should be checked to see if it is OK, and
replaced if necessary. Normally, the battery level is tested at every reset and once
an hour there after, however if the battery is charging then the reserve level of the
battery is not tested since the battery needs charging anyway.
Extra Info None
5.3.8 600..699 MC PVF
5.3.9 700..739 MC PVEC
Error ID: 0703

NameShort
NameLong Overcurrent Motor

Diagnostics
Error ID: 0703
Description There are two possible reasons for the error:
1. The motor current exceeds the maximum value at constant speed (Extra Info 1).
The motor current monitoring at constant speed makes it possible to detect
inadmissible operating conditions. The limit depends on the parameter "over
current fact" (Supervisor Parameters) and relates to the rated motor current "Is
nom" (Motor parameters).
The effective limits are:
- gearless induction motors: over current fact * 1.15 = 1.38
- planetary gear: over current fact * 1.2 = 1.44
- worm gear: over current fact * 1.25 = 1.5
- synchronous motors (typically underslung): over current fact * 1.25 = 1.5
2. Unexpected change of motor torque (Extra Info 2). This reason only applies to
gearless induction motor drives with load measuring device.
Extra Info 1: Current exceeded at constant speed (Over current factor exceeded)
2: Unexpected change of motor torque
For Parallel Inverter and Line inverter there is an offset in the Extra Info set in order
to assign the event to the relevant subsystem:
valid for Vecsys/Variosys 1.10
Slave 1: + 100
Slave 2: + 200
valid from Variosys 1.12
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Line inverter: + 0x10000000
Cause Action
Brake that does not open or opens only check brake
partially
Wrong parameters check parameters
Wrong dimensioning of drive system check drive calculation (speed, acceleration, car weight,
rated load, etc.)
Wrong balancing (counterweight) of the check balancing of the elevator
elevator
Too much friction check guide shoes
Trip into the buffers upwards with check why a trip into the buffers.
insufficient rope slip or trip into an obstacle. check for obstacle and remove it.
Blocked return pulley Replace the pulley
Wrong counting direction of motor encoder Check/correct parameter 'phase_dir',
and/or wrong phase direction of Motor for induction motors: perform direction test
Error ID: 0704

NameShort
NameLong Encoder Failure
Description The feedback signal from the motor encoder is missing. The encoder failure signal
is generated on the related control board (e.g. PIOVECxx) and read by the
software.

Diagnostics
Error ID: 0704
Extra Info 1: Measured speed is zero and speed reference is not zero
2: Encoder signal input on frequency converter is faulty
3: Data transaction failed (absolute encoder with serial interface)
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Encoder cable not connected or not Check the cable and its connection between the encoder and
correctly plugged in. the corresponding pcb (PIOVECxx).
Check the plug.
Motor encoder not correctly mounted Check the mounting of the encoder
Defective incremental encoder or encoder Replace encoder cable and/or encoder
cable
Error ID: 0705

NameShort
NameLong Speed Difference
Description The difference between the speed reference value from travel control and the
actual speed feedback derived from the motor encoder exceeds the value defined
by the parameter OVER_SPEED_FACT. The parameter OVER_SPEED_FACT
relates to nominal speed.
Further error cause: In spite of a high torque no actual speed can be measured
(speed control error).
Extra Info x01: underspeed
x02: overspeed
x03: speed control error
x04: wrong sense of rotation detected during test 'sense of rotation' (direction test
for asynchronous motors)
x05: emergency stop during adjust tacholess control test
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000

Diagnostics
Cause Action
Extra info 0x01 - 0x03: a) ensure the brakes do not remain closed
a) the controller can not provide enough b) check that the car is balanced at 50%
torque to follow the speed reference; c) reduce acceleration or deceleration values
possible causes are:
d) check elevator parameter impu ref
- the break does not open
e) check the encoder
- elevator not balanced
- output power of frequency converter too
small
b) the incremental encoder is defective
Extra info 0x04 with AC machine: tacho change either tacho signals or motor phases or execute
signals or motor phases inverted (error direction test
detection immediately after trip start)
Extra info 0x04 with DC machine: Current Check motor parameters: Rated Motor Current, Maximum
limited Motor Current
Extra info 0x0001nnnn: Motor brake not Check motor brake
working properly
Error ID: 0706

NameShort
NameLong Speed Ref Missing
Description The speed reference telegrams from the Travel Control (MX- / TX- / PTCM
controller) are missing for at least two consecutive periods (20ms).
Extra Info x01: Time out for speed references on CAN (trip phase EXCITING_FIELD)
x02: Speed reference not received on CAN (during trip)
x03: Time out for speed references on RS422 (trip phase EXCITING_FIELD)
x04: Speed reference not received on RS422 (during trip)
x05: Plausibility check of speed reference on CAN failed (acceleration would be
too high).
x06: Plausibility check of speed reference on RS422 failed (acceleration would be
too high).
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Interrupted transmission line from Travel Check serial communication (cable and connection to pcb's)
Control (e.g. pcb ASILOG/ASIX) to Motor
Control (e.g. pcb PIOVECxx / PVEC)
Problem with Travel Control software Check if problem persists with other version of inverter
software or control software
Interface board (pcb) defective Replace respective pcb
Error ID: 0707

NameShort

Diagnostics
Error ID: 0707
NameLong SGRW Failure
Description Control or auxiliary feedback contact of charging contactor SGRW faulty.
Extra Info Meaning of extra info value:
1: SGRW contact not ON when VSGRW is ON
2: SGRW contact not OFF when VSGRW is OFF
+4(bitmask 0x4): Event before trip (trip preparation)
+8(bitmask 0x8): DC link was discharged < 50V
Examples of extra info values:
6(4+2): SGRW switches not OFF when VSGRW is OFF during preparation for trip
1(1+0): SGRW switches not ON when VSGRW is ON at end of trip
9(1+8): SGRW contact not ON when VSGRW ON when charge of DC link after
long mains separation ('Long' means DC link is completely discharged).
2(2+0): SGRW contact not OFF when VSGRW is OFF. Mains separation in
standstill when DC link is charged.
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Wiring of control signal VSGRW or of Check related wiring acc. to actual wiring diagrams
feedback signal SGRW broken or not
connected
Contactor SGRW faulty Check contactor SGRW
PIOVEC/VARIOcon PCB faulty replace PCB
Error ID: 0708

NameShort
NameLong SGR/SH Failure
Description Control or auxiliary feedback of contactor SGR/SH faulty.

Diagnostics
Error ID: 0708
Extra Info Meaning of extra info value:
1: SGR/SH contact not ON when VSGR is ON
2: SGR/SH contact not OFF when VSGR is OFF
+4(bitmask 0x4): Event before trip (trip preparation)
+8(bitmask 0x8): DC link was discharged (<50V)
Examples of extra info values (since VARIOsys V1.05):
5(1+4): SGR/SH switches not ON when VSGR is ON during preparation for a trip
1(1+0): SGR/SH is not ON when VSGR is ON during a trip
2(2+0): SGR/ SH switches not OFF when VSGR is OFF at end of trip
2(2+0): SGR/SH contact not OFF when VSGR is OFF. Mains separation in
standstill when DC link is charged.
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Wiring of control signal VSGR or of feedback Check related wiring acc. to actual wiring diagrams
signal SGR/SH broken or not connected
Contactor SGR/SH faulty Check contactor SGR/SH
TX-GC: the safety circuit opens during a trip Check safety circuit and total error log
or a test (extra info values 1 or 5)
PIOVEC/VARIOcon PCB faulty replace PCB
Known problem in VecSys software. Update VecSys software to version 2.14 (or higher)
Error ID: 0709

NameShort
NameLong Safety Circuit

Diagnostics
Error ID: 0709
Description The frequency converter detects that the safety circuit opens (relay RSK off) during
a trip or a test. The monitoring of the safety circuit done by the control (travel
control) may also generate a message when the safety circuit opens. On Schindler
frequency converters the monitoring of the safety circuit is more sensitive than the
one done by travel control.
Caution: This error does not report a fault or an abnormal behavior of the power
assembly (frequency converter, PVEC/PIOVEC) but of the system as a whole;
refer also to safety circuit monitoring (errors) of travel control.
The error is not generated during inspection or recall trips (electrical emergency
operation).
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Extra Info None.
Cause Action
The safety circuit opened during a trip or a Check safety circuit and logs of other subsystems (total error
test. The safety circuit may have been log)
interrupted only for a very short time.
Cable of safety circuit signal broken or not Check wiring from control (ASxxx board) to frequency
connected converter.
Error ID: 0710

NameShort
NameLong FCR Not Ready
Description The FCR is not ready to run.
Extra Info 1: FCR not started correctly
2: FCR not stopped correctly
3: FCR wrong feedback
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
check FCR error log
Error ID: 0712

NameShort

Diagnostics
Error ID: 0712
NameLong Power Electronic Failure
Description The feedback of the power electronics module(s) report an error.
Extra Info Meaning of extra info value for VecSys 2.15 / VARIOsys 1.02 and higher:
x00: Any error in power module
x01(Bitmask Bit 0): Error in phase U / VF11BR: overcurrent / DC: not used
x02(Bitmask Bit 1): Error in phase V / VF11BR: supply voltage error / DC: error in
half bridge A1
x04(Bitmask Bit 2): Error in phase W / DC: error in half bridge A2
x08(Bitmask Bit 3): AC/DC: Error in brake chopper
Meaning of extra info value for VecSys 2.14 / VARIOsys 1.01 and below (older):
x01: error in phase U
x02: error in phase V
x03: error in phase W
x04: error in brake chopper
x05: any error in power module
For Parallel Inverter and line inverter there is an offset in the Extra Info set in order
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
line inverter: + 0x10000000
Cause Action
Cable from power unit broken or not check cable and connectors
connected
Power module faulty replace power unit
Fan faulty check that the fan runs during a trip, run fan test, check
cables, replace fan
Brake resistor/chopper faulty (overvoltage check brake resistor and cables
trigger)
Temperature in machine room or hoistway
too high
Wrong dimensioning (calculation) of the
drive system
For extra info value=0: thyristor not on
(VF30BR only)
Power module turned off (VF88PF1 V2 only)
For extra info value=5: overcurrent / short
circuit
Error ID: 0714

NameShort
NameLong Current Not Zero
Description Motor current not zero at standstill

Diagnostics
Error ID: 0714
Extra Info For Parallel Inverter and line inverter there is an offset in the Extra Info set in order
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Current measurement faulty Check cables, LEM
Power assembly faulty Replace power unit
Error ID: 0715

NameShort
NameLong Current Sum Failure
Description Sum of motor phase currents is not zero. The error is generated when the current
sum exceeds 30% of the inverter nominal current.
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Short circuit between phase and ground on Check wiring and motor
the motor side
Current measurement faulty (EMC) Check cables, LEM
Error ID: 0717

NameShort
NameLong Overtemp HS Limit
Description Temperature limit of the heatsink or of the brake chopper (if available) exceeded.
(See supervisor parameter INV_TEMP_LIM --> parameter description).
A trip must be terminated by the Travel Control on the next floor.

Diagnostics
Error ID: 0717
Extra Info Meaning of extra info value for Variosys 1.17 and higher:
0xSI0PTTTT
S: Subsystem: 0 MC, 1 LC
I: Inverter ID: 0 Master, 1 Slave 1, 2 Slave 2
P: Phase: 1 U/L1, 2 V/L2, 4 W/L3
TTTT: Temperature: measured temperature
special values:
over temperature = 1
no signal = 2
short cut = 3
out of range = 4
ambient = 20
For Variosys 1.13 to Variosys 1.16
0xn1 Overtemperature of power module
0xn2 No temperature signal of sensor power module
0xn3 Shortcut of sensor power module
0x0m Sensor of converter with one single power module
0x1m Sensor of power module phase 1
For VecSYS and software versions below 1.13 of Variosys software
01: overtemperature of heatsink
02: no temperature signal from heatsink
03: overtemperature of brake chopper
04: no temperature signal from brake chopper
dec11(h0B): Overtemperature phase U
dec12(h0C): Overtemperature phase V
dec13(h0D): Overtemperature phase W
dec21(h15): No temperature signal from heatsink phase U
dec22(h16): No temperature signal from heatsink phase V
dec23(h17): No temperature signal from heatsink phase W
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Fan faulty Check fan
Cable from heatsink broken or not connected Check cable
Temperature of machine room too high
Faulty dimensioning of drive system

Diagnostics
Error ID: 0719
NameShort
NameLong DCL Overvoltage
Description Overvoltage in DC link.
The DC link voltage is measured by an AD-converter. The limit is determined by
the supervisor parameter Udcl Upp Lim Idle (see parameter description). It can
only occur during standstill.
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Overvoltage in mains Check mains supply voltage
Parameter wrong Check the parameter Input voltage setting and/or Udcl Upp
Lim Idle
line inverter at the input of DC link (VF120 - Check line inverter
VF280, VF55PF1 - 3xVF288PF1 AC,
VF155PF1 - VF288PF1 DC): malfunction of
line inverter
line inverter at the input of DC link (VF120 - Check line inverter parameters
VF155PF1 - VF288PF1 DC): wrong
parameters of line inverter
Error ID: 0720

NameShort
NameLong DCL Undervoltage
Description Undervoltage in DC link.
The DC link voltage is measured by an AD-converter. The limit is determined by
the supervisor parameter Udcl Low Lim Idle (see parameter description) during
stand still and Udcl Low Lim Ride during the trip.
In addition, the dc link voltage is monitored by line control (VarioLC).
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Undervoltage in mains Check mains supply voltage

Diagnostics
Cause Action
Parameter wrong Check the parameters Input voltage setting, Udcl Low Lim
Idle and Udcl Low Lim Ride
Defective diode bridge Replace power unit
line inverter at the input of DC link (VF120 - Check line inverter
VF155PF1 - VF288PF1 DC): malfunction of
line inverter
line inverter at the input of DC link (VF120 - Check line inverter parameters
VF155PF1 - VF288PF1 DC): wrong
parameters of line inverter
Error ID: 0725

NameShort
NameLong Overtemp KTHBR
Description Overtemperature on the brake chopper resistor (detected with PT100 / KTJ84 /
KTHBR). On some PF1 inverters (with VarioLC) overtemperature of line choke.
Please check in actual wiring diagram.
0xSI0PTTTT
P: Probe: 0 unknown, 1 none, 2 PT100, 3 KTY84
special values:
no signal = 2
short cut = 3
out of range = 4
ambient = 20
Meaning of extra info value for Variosys 1.16 and older:
1: Overtemperature of BR (detected with klixon KTHBR)
2: No temperature signal from sensor BR / open
3: Shortcut of sensor BR
4: No feedback from FAN (converters with VARIOcon / VIP only)
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Fan faulty Check fan
Cable from sensor (klixon) broken or not Check cable
connected

Diagnostics
Cause Action
Wrong dimensioning of drive system Verify drive calculation
Wrong value of parameter “Brake Chopper Correct parameter according to the parameter description
Type”
Error ID: 0726

NameShort
NameLong Overtemp MH
Description Overtemperature of the hoisting motor (detected with PT100 / KTJ84).
On some PF1 inverters overtemperature of line choke. Please check actual wiring
diagram.
0xSI0PTTTT
P: Probe: 0 unknown, 1 none, 2 PT100, 3 KTY84
special values:
no signal = 2
short cut = 3
out of range = 4
ambient = 20
Meaning of extra info value for Variosys 1.16 and older:
1: Overtemperature of MH
2: No temperature signal from MH / open
3: Shortcut of sensor MH
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
MH fan faulty check fan
THMH cable MH broken or not connected check cable
Wrong dimensioning of drive system Verify drive calculation
Wrong value of parameter “Motor Temp Lim” Set parameter according to parameter description
Error ID: 0727

NameShort
NameLong HW failure

Diagnostics
Error ID: 0727
Description HW failure of converter detected.
Extra Info Yaskawa inverter:
1: for further details see Yaskawa documentation CPF04
VARIOSys parallel inverter the extra info
0x0001: no CAN communication to master
0x0002: no CAN communication to slaves (at least one slave did not answer)
0x0003: no dsmc alive
0x0004: dsmc progerr
0x8xxx: (until v1.17)
Bit 0 (0x1): no capture signal
Bit 1 (0x2): TMOD not synchronized
Bit 2-5 (0x4/0x8/0x10/0x20): Timeout ssi
Bit 6/7 (0x40/0x80): Transmission error (data/flag)
Bit 8 (0x100): mode u/v/w not synchronized
Bit 9 (0x200): task_counter not synchronized
Bit 10 (0x400): master_int_counter not synchronized
0x8xxx: (v1.18 and beyond)
Bit 0 (0x1): no capture signal
Bit 1 (0x2): TMOD not synchronized
Bit 2-5 (0x4/0x8/0x10/0x20): Timeout ssi
Bit 6/7 (0x40/0x80): Transmission error (data/flag)
Bit 8 (0x100): task_count & mast_int_count not synchronized / line angle not
synchronized
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Yaskawa: faulty inverter hardware refer to Yaskawa documentation for details
VARIOSys parallel inverter: SSI/CAN Check SSI/CAN wiring of VIP3 board
communication interrupted
VARIOSys parallel inverter: Disturbance on Check grounding connections (screws) of VIP3 board and
SSI/CAN connection shielding of SSI/CAN communication cables

Diagnostics
Cause Action
VARIOSys parallel inverter: Reset of master Check warning log of master inverter for SW warning (E1)
inverter with extra info value 140
VARIOSys inverter info 0x0003, 0x0004: Fatal Change Variocon board, download new software
program/hardware failure of dsmc
VarioLC inverter info 0x81xx Phase sequence of mains supply not the same for master
and slaves
Error ID: 0729

NameShort
NameLong Fan failure
Description Failure of the fan
Extra Info BR converters
1: no feedback of VFVE (line inverter fan)
4: no feedback of VFVE-BR (brake resistor fan)
PF1 converters
1: no feedback of VFVE-CO (line inverter fan)
4: no feedback of VFVE-FCR (line resistor fan)
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
VF288: no 48 V supply (NG48) Check power supply unit: measure supply and output voltage
all other converters: no 24 V supply
VF288: no control signal on fan Check wiring of connector VIP3.FAN OUT
VF288: no feedback signal from FAN Check wiring of connector VIP3.FAN IN
Error ID: 0736

NameShort
NameLong Mains Voltage Failure
Description Mains voltage too high or too low or mains voltage frequency too high or too low.

Diagnostics
Error ID: 0736
Extra Info 0x01: Mains voltage out of range: undervoltage
0x02: Mains voltage out of range: overvoltage
0x03: Mains frequency out of range: frequency too low
0x04: Mains frequency out of range: frequency too high
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Incorrect inverter parameters Check settings parameter of inverter (Inverter Input Voltage)
Mains supply voltage not stable Measure 3 phases of mains voltage
Error ID: 0737

NameShort
NameLong UEM detected
Description Motor encoder moved in standstill. Unintended encoder movement.
Extra Info 0x0001nnnn: Motor moves when motor control is at standstill; nnnn: distance of
car movement in [mm]
Examples for extra info values:
0x0001000A: traction sheave moved resulting in a car movement of 10
mm in up direction.
0x0001FFF6: traction sheave moved resulting in a car movement of 10
mm in down direction.
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000
Cause Action
Motor brake faulty Replace motor brake
Motor brake adjustment wrong Adjust brake (if adjustment is allowed)
Wrong measurement of encoder Check/replace encoder
5.3.10 740..799 Magnetic

Diagnostics
5.3.11 800..899 800_899_Varidor35_Door_Drive
5.3.12 900..999 IO
5.3.13 1000..1199 CPU
Error ID: 1063

NameShort
NameLong Group24vFail
Description The CPU was reset, and the Group 24V supply is below tolerance (24V20%). If
warning 1064 elevatorPowerFail also appears at the same time as this warning,
the system may be running on the backup battery power only.
TX5 Note: Normally, the battery level is tested at every reset, however if either
1064 elevatorPowerFail or 1064 elevatorPowerFail event appears, then the
reserve level of the battery is not tested, since testing the battery could possibly
interrupt power to the control in this case.
Extra Info None.
Error ID: 1064

NameShort
NameLong elevator24vFail
Description The CPU was reset, and the Group 24V supply is below tolerance (24V20%). If
warning 1063 GroupPowerFail also appears at the same time as this warning, the
system may be running on the backup battery power only.
TX5 Note: Normally, the battery level is tested at every reset, however if either
1064 elevatorPowerFail or 1064 elevatorPowerFail event appears, then the
reserve level of the battery is not tested, since testing the battery could possibly
interrupt power to the control in this case.
Extra Info None.
Error ID: 1066

NameShort
NameLong BatteryCharging
Description The CPU was reset, and the battery needs charging. The battery is automatically
charged.
TX5 Note: This event is normal following a power failure. If the battery requires
increasingly charging, the battery should be checked to see if it is OK, and
replaced if necessary.
Normally, the battery level is tested at every reset, however if the battery is
charging then the reserve level of the battery is not tested since the battery needs
charging anyway.
Extra Info None.
Error ID: 1069

NameShort
NameLong BatteryDeadOrMissing

Diagnostics
Error ID: 1069
Description The CPU was reset, and the battery was dead or missing
TX5 Note: Normally, the battery level is tested at every reset (As long as Group24V
and elevator24V to ASILOG are OK) and also once every day. The battery voltage
was tested, and found to be too low. The battery is either completely discharged,
dead, damaged, or disconnected.
Cause Action
Check the wiring and connections to the battery
Leave the controller powered on, see if the battery is
charged eventually
Measure the voltage of the battery. It should be about 12v
If the error continues, check the battery and replace if
necessary
5.3.14 1200..1249 LON
Error ID: 1209

NameShort
NameLong Missing Node
Description The error is logged when a node (pcb) is missing on the LON network for some
time (maximum 1 min.) or when an output on a missing LON can not be set
because the node is no longer responding. When a LON node is found missing the
control system will respond depending on the IO's configured on the node (e.g.
TAB for critical IOs). The message is not logged when mains power is turned off.
Comment: A node will only be considered missing if it is listed in the LON node
reference list maintained by the SW. The node list is either generated after a
'freeze LON tree' command (for p&p IO interfaces) or is part of the physical
configuration table (PCT). For details about the status of the LON nodes refer to
SMLCD or CADI 'I/O tracer'.
Change history:
Oct.25 2007 extra information value includes LON channel number

Diagnostics
Error ID: 1209
Extra Info LON channel identifier; Node type and Location ID.
LON channel identifier, LON node type and LON node location ID are encoded in a
32-bit value (8 digit hex. value)
wxxxyyyy: The first digit (w) identifies the LON channel (0,1 or 2); 0 means that the
control software does not provide this information. The next 3 digits (xxx) identify
the Node type ("p_type"). The last 4 digits (yyyy) show the Node Id. ("p_id")
The "p_type" defines which type of node is affected (see the list below).
The "p_id" defines the location-ID of the node, typically set by a local dipswitch, or
configured through the M10-keypad.
Examples:
10010002: LON channel 1, Node type=01, ID=02. (LONIO, dipswitch=02. See list
below for p-type)
10030004: LON channel 1, Node type=03, ID=04. (LFT-DPI, dipswitch=04.)
Meaning of values for "p_type":
Value / software name / board names
000(hex) / 0(dec): UNDEF should never occur
001(hex) / 1(dec): GENERIC_IO_BOARD LONIOS16, LONIOH16, ICE, (H)TIC
002(hex) / 2(dec): ARRIVAL_INDICATOR LONDAG
003(hex) / 3(dec): DIGITAL_POSITION_INDICATOR LFTSDPI8, LFTDPI50
004(hex) / 4(dec): LMS_MODUL LONLMS
005(hex) / 5(dec): MACHINE_MODUL not used
006(hex) / 6(dec): CIOHNA Cab IO for HX system
007(hex) / 7(dec): HPBHNA Hall node for HX system
008(hex) / 8(dec): M10_TERMINAL ZRTL
009(hex) / 9(dec): M10_DESTINATION_INDICATOR AZRC
00A(hex) / 10(dec): M10_SPEECH ANN
00C(hex) / 12(dec): MX_COP LONCOP, LONCPI
00D(hex) / 13(dec): MX_LOP LONCUS, LONIO(C), LOND(G)I
00E(hex) / 14(dec): MX_OPT_LIP_BIG LONCUB, LON(P/D)GIO, LONDY(H/IO),
LONPII, LONVEx
01E(hex) / 30(dec): MX_LONIC LONIC, LONGIC
Extra Info 036(hex) / 54(dec): CAR_DOOR_NODE LONIBV, LONDIM, LONV70, PLDA
037(hex) / 55(dec): SHAFT_DOOR_NODE not used
03C(hex) / 60(dec): HIOMRLPP HIOMRL plug and play for NA
064(hex) / 100(dec): LOCAL_IO_BOARD ASILOG(A), ASIX(A)
Cause Action
No power at fixture or I/O board Check power LED's and power wiring.
Communication to pcb interrupted Check bus cables and wiring (APPL LED on LON interface
board indicates if board is communicating).
Damaged or defective fixture or I/O board Replace damaged fixture or I/O interface board and repeat
(corrupted software or other defect) LON freeze command if necessary.
5.3.15 1250..1299 BIO2

Diagnostics
5.3.16 1300..1349 1300_11349_CAN
5.3.17 1400..1499 VF
5.3.18 1500..1999 Travel Control Ext
Error ID: 1501

NameShort
NameLong Invalid Car Position
Description The actual car position read from the position encoder is not in the range of the
learnt floor/stop positions (1m above the top floor / 1m below the bottom floor).
The monitoring is not active when a learn trip is needed or is being performed. It is
not reported with active montage (JMOF on). The error is surpressed during active
acceptance testing, since some of the tests require the elevator to move beyond
the normally acceptable range [extreme floors +/- 1meter]. On systems with
incremental position tachos this error is not reported.
Extra Info Actual car position (decimal value in [mm]) when the error occurred.
Cause Action
Car position encoder was moved (without Do a learn trip
car) while not connected to control or with
power down (AGSI)
Car position encoder was replaced Do a learn trip
Car position encoder faulty Replace encoder and do a learn trip
Error ID: 1502

NameShort
NameLong Position Jump
Description The software calculates a difference of the car position values for two consecutive
readings (read cycle: 10msec) which exceeds a travel distance of 240mm. After 5
consecutive wrong reading cycles the software logs the error: the elevator
performs an emergency stop and is blocked permanent.
This monitoring limits the 'change rate' of the readings from the position tacho and
prevents that the software calculates wrong a false floor position (or speed) for the
car. The limit value of 240mm is independent of the car speed (240mm is less than
the foreseen minimum floor distance). The limit distance is not adjustable.
Extra Info Value of position tacho [increments]
Cause Action
EMC problems with car position encoder Check wiring of car position encoder
(absolute encoder)
Faulty car position encoder Replace encoder
Faulty wiring of car position encoder Check wiring and connectors
Error ID: 1504

NameShort
NameLong Safety T6

Diagnostics
Error ID: 1504
Description Used for the monitoring of the landing door lock contacts KV. The safety circuit is
open before the last tap but after the previous tap. The message is logged if:
a) the safety circuit opens during a trip due to a landing door lock contact (any)
which opens unexpectedly.
Refer also to actual wiring diagram for contacts causing the error.
the error occurred.
Cause Action
Bad landing door lock contact(s) KV
Error ID: 1505

NameShort
NameLong Invalid Floor Position during Trip
Description Inconsistent floor position found during a trip. The error is logged when:
a.) the software detects no related floor signal (e.g. hardware input KUET/KUET2)
at a car position for which a floor/stop was detected during the learn trip;
b.) the software sees the input for the floor/stop detection (e.g. KUET/KUET2)
switching at a car position not related to a position found during the learn trip.
The monitoring is disabled:
- when a learn trip is needed or is being performed.
- with active montage (JMOF on).
- when the mains switch JH is off
On systems with incremental position tachos this error is not reported when the car
position is unknown and during a 'sync trip'.
Cause Action
Missing floor magnet or floor vane Check the hardware in the hoistway.
(KUET/KUET2).
Faulty input on interface board for Check/replace the interface board.
KUET/KUET2.
Mechanical problem with fixation of floor Check fixation of vane(s).
vane.
Error ID: 1506

NameShort
NameLong Invalid Floor Position in Standstill

Diagnostics
Error ID: 1506
Description Inconsistent floor position found in standstill. The error is logged when:
a.) the software detects no related floor signal (e.g. hardware input KUET/KUET2)
at a car position for which a floor/stop was detected during the learn trip;
b.) the software sees the input for the floor/stop detection (e.g. KUET/KUET2)
switching at a car position not related to a position found during the learn trip.
The monitoring is disabled:
- when a learn trip is needed or is being performed.
- with active montage (JMOF on).
- when the mains switch JH is off.
On systems with incremental position tachos this error is not reported when the car
position is unknown and during a 'sync trip'.
Cause Action
Missing floor magnet or floor vane Check the hardware in the hoistway.
(KUET/KUET2).
Faulty input on interface board for Check/replace the interface board.
KUET/KUET2.
Mechanical problem with fixation of floor Check fixation of vane(s).
vane.
Error ID: 1507

NameShort
NameLong KB ON standstill
Description The control detects that a brake is released (ON) in standstill. A brake contact KB
is logically active in standstill indicating that the respective brake (lever) is not in
the closed position.

Diagnostics
Error ID: 1507
Extra Info Shows the status of the individual KB inputs. The 8 digit hexadecimal number
(0xABCDEFGH) has the following meaning:
Value 'A': Internal state of brake control channel 1 (brake_state, ch1) in software.
The values are:
0: BRAKE_INIT
1: NO_PARAMETERS (Brake parameters missing)
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'B':Internal state of brake control channel 2 (brake_state, ch2) in software.
The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'C': Physical state (0/1) of contact KB
Value 'D': Physical state (0/1) of contact KB1
Value 'E': Physical state (0/1) of contact KB2 [only if input used, else 0]
Value 'F': Physical state (0/1) of contact KB3 [only if input used, else 0]
Value 'G': Physical state (0/1) of contact KB4 [only if input used, else 0]
Value 'H': Physical state (0/1) of contact KB5 [only if input used, else 0]
Cause Action
Faulty brake contact(s) KBx Check the function of the brake contacts.
necessary
Wrong parameter value for parameter 'KB Check drive parameters (settings) for correct brake type.
feedback type'
Faulty input on the interface board for the KB Verify faulty input and replace board
inputs (ASILOG, ASIX.. etc).
Error ID: 1508

NameShort
NameLong KB not ON start
Description The control detects that the brake does not open (open = ON) during trip start as
expected. A brake contact KB does not switch when starting a trip indicating that
the respective brake (lever) does not open after activation of the brake (SB or
MBB). The error may also indicate a faulty KB contact.

Diagnostics
Error ID: 1508
Value 'A': Internal state of brake control (brake_state) in software. The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Cause Action
necessary
feedback type'
inputs (ASILOG, ASIX . .etc).
Error ID: 1509

NameShort
NameLong KB OFF Run
Description The control detects that a brake is closed (OFF) during a trip. A brake contact KB
is inactive during a trip indicating that the respective brake (lever) is not in the open
position.

Diagnostics
Error ID: 1509
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Cause Action
necessary
feedback type'
Error ID: 1510

NameShort
NameLong KB not OFF stop
Description The control detects that the brake does not close (closed = OFF) at the end of a
trip as expected. A brake contact KB does not switch when finishing a trip as
expected indicating that the respective brake (lever) did not close after deactivation
of the brake (SB or MBB). The error may also indicate a faulty KB contact.
There is an additional monitoring done by the software in case both (all) brake
contacts do not switch at the end of a trip. In this case a so called safety parking is
performed. See error 'Brake not Set' (#138) for more details.

Diagnostics
Error ID: 1510
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Cause Action
necessary
feedback type'
Error ID: 1512

NameShort
NameLong SI Communication Lost

Diagnostics
Error ID: 1512
Description The control detects a lost CAN communication to the shaft info system (MoSIS /
SALSIS). The control constantly monitors the position messages received over the
CAN bus. It logs the error if no position message arrives for more than 50ms
during a trip or 500ms at standstill (MoSIS/SALSIS send messages every 10ms
during a trip and every 100ms in standstill). The message is logged when the CAN
bus is interrupted (e.g. plug of CAN bus cable removed) or after interrupting power
supply for MoSIS/SALSIS. If the communication fails during a trip the control
continues the trip to serve the call using the speed signal from the inverter
(V_TACHO). The control will switch back to the signal from MoSIS/SALSIS
(S_TACHO) if the communication is reestablished within 1sec. This avoids
unnecessary aborting of trips. If the communication is lost for more than 1sec the
control stops at the nearest floor [current SELECTOR] and waits for the
communication to be reestablished. The elevator is no longer available and no
trips can be performed unless the communication is established again. If the
communication to MOSIS/SALSIS remains interrupted the control will activate
FATAL service (breakdown); see also error 1595.
Error ID: 1513

NameShort
NameLong SI UET Fault
Description This error is reported if the UET relay opens for a reason other than the normal
door overbridging, if the relay test fails, or other error condition related to the UET
function of MoSIS/SALSIS. The extra info describes the message sent by
MoSis/SALSIS together with status change of UET relay.
Extra Info The extra information is a 8 digit hexadecimal code with the following meaning per
digit: STUVWXYZ
S=1: Doors are overbridged
T=1: Below max overbridging speed
U=1: In door zone
V=1: Overbridging command given
W=1: LUET A magnet detected within 25mm
X=1: Internal error. The error “1515 MOSIS_INTERNAL_LOG" may also be
reported if this bit is set.
Y=1: Error: Number of floors in MoSIS don’t fit number of floors in control
Z=1: Error: The MoUET relay failed to pick correctly
Error ID: 1526

NameShort
NameLong ZSB Fault
Description Error on brake control (MX control). The software monitors the status of the input
KZSB (feedback signal of the relay ZSB on the brake module). The ZSB timer
reduces the brake voltage/current after the brake has opened (opening
voltage/holding voltage). The error indicates that the status of the input KZSB is
not as expected during a trip.
digit (ABCDEFGH). Decoding of the value:
The extra info value indicates the status of the input
H: Status of the input of the KZSB contact
00000001: KZSB on
00000001: KZSB off

Diagnostics
Error ID: 1527
NameShort
NameLong KTS Bridged
Description The error is reported in case the software detects a bridged KTS contact in the
safety circuit.
The monitor checks the open state of the KTS contact when the door is fully
opened and when the door starts closing.
Error ID: 1528

NameShort
NameLong KTC Bridged
Description The error is reported in case the software detects a bridged KTC contact in the
safety circuit.
The monitor checks the open state of the KTC contact when the door is fully
opened and when the door starts closing.
Error ID: 1530

NameShort
NameLong RTC Fault
Description The relay RTCx or 2RTCx did not operate as expected.
On older software version the error 95 'Door Lock Fault' was logged in this
situation.
Error ID: 1531

NameShort
NameLong RTS Fault
Description The relay RTSx or 2RTSx did not operate as expected.
On older software version the error 95 'Door Lock Fault' was logged in this
situation.
Error ID: 1532

NameShort
NameLong KTS Fault
Description The error is reported in case the software detects that the KTS contact in the safety
circuit does not close as expected. The monitor checks the closed state of the KTS
contact when the door received a door lock command. In case of unsuccessful
check, the control performs a number of lock - unlock cycles to recover the contact
problem.
Error ID: 1533

NameShort
NameLong KTC Fault

Diagnostics
Error ID: 1533
Description The error is reported in case the software detects that the KTC contact in the
safety circuit does not close as expected.
The monitor checks the closed state of the KTC contact when the door received a
door lock command.
In case of unsuccessful check, the control performs a number of lock - unlock
cycles to recover the contact problem.
Extra Info none
Error ID: 1534

NameShort
NameLong Door State Fault
Description
Error ID: 1535

NameShort
NameLong KTS/KTC Bridged
Description The error is reported in case the software detects a bridged KTS or KTC contact in
the safety circuit.
The monitor checks the open state of the KTS and KTC contacts when the door is
fully opened and when the door starts closing.
Note: This error is reported in case the control system can not determine whether
KTS or KTC is bridged.
Extra Info none
Error ID: 1545

NameShort
NameLong SB ON standstill
Description The control detects that the brake contactor is active (ON) in standstill. The
feedback contact indicates open contactor while the related output to activate the
brake (SB) is inactive.
Extra Info The 8 digit hexadecimal number (0xABCDEFGH) has the following meaning:
Value 'A': not used
Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Value 'G': SB contact state
Value 'H': SB1 contact state
Error ID: 1546

NameShort
NameLong SB not ON start
Description The control detects that the brake contactor does pick (ON) during trip start as
expected. The feedback contact of SB/SB1 does not switch when starting a trip.

Diagnostics
Error ID: 1546
Value 'A': not used
Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Error ID: 1547

NameShort
NameLong SB OFF Run
Description The control detects that a brake contactor closed (OFF) during a trip. The feedback
contact is inactive during a trip indicating that the respective contactor is not on.
Value 'A': not used
Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Error ID: 1548

NameShort
NameLong SB not OFF stop
Description The control detects that the brake contactor (SB/SB1) does not close (closed =
OFF) at the end of a trip as expected. An auxiliary contact does not switch when
finishing a trip as expected indicating that the respective contactor did not drop
after deactivation of the related output. The error may also indicate a faulty output.
Value 'A': not used
Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Error ID: 1555

NameShort
NameLong MBB Open Timeout Current

Diagnostics
Error ID: 1555
Description The brake does not open after applying the set voltage to the brake circuit.
After the brake_open command is given to the brake module the brakes are not
opened within the maximum time. The maximum time is defined by the PCT
parameter 'KB_time'. Its min value is 1sec and max value is 2.3 sec.
Possible reason: Insufficient current in brake circuit when reference value for
current in brake circuit applied by control.
For MBBG2 this error is for channel 1.
Extra Info 8 digit hex number: 0xaabbccdd where
aa: internal_brake_state (state machine)
bb: brake_state
cc: current reference applied to brake module (hex value)
dd: voltage reference applied to brake module (hex value)
Values for 'internal_brake_state':
00: MBB_CLOSED / Brake is closed
01(hex01): MBB_GO_PREPARING / Start preparing brake
02(hex02): MBB_PREPARING / Brake is preparing to open
03(hex03): MBB_GO_OPENING / Start opening
04(hex04): MBB_OPENING_WITH_PROBLEM / Open with IGBT check
05(hex05): MBB_OPENING / Brake is opening
06(hex06): MBB_OPENING_AFTER_KB / Wait high voltage after KB
07(hex07): MBB_OPEN / Brake is open
08(hex08): MBB_GO_CLOSING_SLOW / Start closing slow
09(hex09): MBB_CLOSING_SLOW / Brake is closing slow
10(hex0A): MBB_GO_CLOSING_FAST / Start closing fast
11(hex0B): MBB_CLOSING_FAST / Brake is closing fast
12(hex0C): MBB_WAIT_AFTER_KB / Wait for state closed after KB
13(hex0D): MBB_WAIT_ZERO_VOLT / Wait for zero voltage on ADC
14(hex0E): MBB_GO_REFRESHING / Do IGBT3 test with a Refresh
15(hex0F): MBB_REFRESHING / Check the result of the test
16(hex10): MBB_REFRESH / Refresh is complete
Values for 'brake_state' (bb):
00: BRAKE INIT
01: NO PARAMETERS / Brake parameters missing
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Cause Action
Wrong parameter values Check parameter values of the brake parameters: opening
voltage, holding voltage, AD resolution for brake voltage
measurement (-> Parameter -> Brake)
Error ID: 1556

NameShort
NameLong MBB Close Timeout Current

Diagnostics
Error ID: 1556
Description The brake does not close after removing the voltage to the brake circuit.
After the brake_close command is given to the brake module the brakes are not
closed within the maximum time. The maximum time is defined by the PCT
parameter 'KB_time'. Its min value is 1sec and max value is 2.3 sec.
Current in brake circuit not zero when reference value for current in brake circuit is
set to zero.
bb: brake_state
cc: current reference applied to brake module
dd: voltage reference applied to brake module
10(hex0A): MBB_REFRESH / Refresh is complete
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Error ID: 1557

NameShort
NameLong MBB IGBT3 Fault
Description The test of the power electronics (IGBT3) on MBBx board failed. This IGBT3 test is
triggered by the control software with every trip preparation before opening the
brake(s).
Testing: the error can be reproduced by disconnecting the plug on the 230VAC
connector on the MBBx board.

Diagnostics
Error ID: 1557
bb: brake_state
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Cause Action
Open brake circuit or faulty brake module Check the electrical circuit from the cabinet to the brake(s)
or replace brake module
No AC supply voltage for brake module Check the AC supply voltage for the brake module and the
MBBx created circuits.
Error ID: 1558

NameShort
NameLong MBB Hardware Fault
Description Harware problem MBBx board

Diagnostics
Error ID: 1558
bb: brake_state
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Error ID: 1559

NameShort
NameLong MBB Current Difference
Description Maximum difference between the reference brake current and actual current
exceeded. The reference values for brake opening and holding currents are
defined by PCT parameters. The software checks he difference between 'current
ref' applied and the value of actual current received from brake module. The
maximum difference is: 'current_ref' / 3 where the value of current_ref is either
opening_current or holding current depending on the brake_state.

Diagnostics
Error ID: 1559
bb: brake_state
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Error ID: 1560

NameShort
NameLong MBB Mains Not Off
Description AC power to MBB not turned off after deactivation of the brake. The software
expects the mains supply voltage to be turned off after the brake has closed
(standstill). The AC mains supply for the brake module is turned off when safety
circuit relays (RSK) are off.

Diagnostics
Error ID: 1560
bb: brake_state
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Cause Action
Incorrect wiring of AC voltage from TB to Check wiring of AC supply voltage to MBBx board
MBBx
Error ID: 1561

NameShort
NameLong MBB IGBT1 Fault
Description Test of power electronics on MBBx (IGBT1) failed. The IGBT1 test is done before
opening the brake(s).

Diagnostics
Error ID: 1561
bb: brake_state
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Cause Action
Faulty PCB Replace pcb MBBx
Error ID: 1562

NameShort
NameLong MBB Voltage Difference
Description Maximum difference between the reference brake voltage and the actual voltage
exceeded. Reference values for brake opening and holding voltages are defined
by PCT parameters. For brake modules MBBx (TX/TX2).
The software checks the difference between the 'voltage ref' applied and the value
of actual voltage received from brake module. The maximum difference is:
'voltage_ref' / 3' where the value of the voltage_ref is either opening_voltage or
holding_voltage (PCT parameter) depending on the actual brake_state. For
magnetic brakes the SW regulates the brake current and monitors the output
voltage to the brake coil. For Hydraulic brakes the SW regulates/sets the brake
voltage and monitors the current to the valve.

Diagnostics
Error ID: 1562
bb: brake_state
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING
Cause Action
Wrong parameter setting of PCT parameter Check parameter values and required brake voltage. The SW
'Opening Voltage', 'Holding Voltage' or 'AD monitors the output voltage to the brake coil.
Resolution for voltage measuring'
Faulty pcb Check measured brake voltage with CADI; replace pcb if
necessary.
Error ID: 1574

NameShort
NameLong Safety Circuit Bridged
Description The safety circuit is found bridged permanently.
If the safety circuit tab T4 is off and the tabs T5 and T6 are on, a bridging of the
safety circuit is detected. The bridging can only be detected, if the bridging
contains the section of the door safety contacts.

Diagnostics
Error ID: 1614
NameShort
NameLong Overspeed Drive
Description The error is logged when the software detects that the actual speed of the car
[based on V_TACHO feedback from the inverter] exceeds the maximum limit for a
given car speed reference. The tolerance is calculated as 6.25% of the speed
reference value. The minimum speed difference that will lead to an error is based
on the trip type:
1. 0.2m/sec for Normal trips.
2. 0.1m/sec for RELEVEL or when at STANDSTILL.
3. 0.3m/sec for all other trips.
If the difference between the actual speed of the car and the speed reference
(velocity_ref) exceeds this calculated limit the trip is interrupted with an emergency
stop.
extra_info : 0xABCDEFGH
H = JMOF state. In case the Overspeed was detected in JMOF, then H=1.
Error ID: 1615

NameShort
NameLong Underspeed Drive
[based on V_TACHO feedback from the inverter] is below a minimum limit for a
on the trip type:
stop.
extra_info : 0xABCDEFGH
H = JMOF state. In case the Overspeed was detected in JMOF, then H=1.
Error ID: 1616

NameShort
NameLong Overspeed Car
[based on S_TACHO feedback from the inverter] exceeds the maximum limit for a
on the trip type:
stop.
Extra Info extra_info : 0xABCDEFGH
H = JMOF state (0: off / 1: on). In case the Overspeed was detected in JMOF, then
H=1.

Diagnostics
Error ID: 1617
NameShort
NameLong Underspeed Car
[based on V_TACHO feedback from the inverter] is below a minimum limit for a
on the trip type:
stop.
Extra Info extra_info : 0xABCDEFGH
H = JMOF state (0: off / 1:on)). In case the Overspeed was detected in JMOF, then
H=1.

Diagnostics

Fallas 5400-1

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Fallas 5400-1

Hochgeladen von

Copyright:

Verfügbare Formate

5.

5.3.2 0..149 Travel Control

Error ID: 0007

S7000 Call Back Handling Draft K 42520051 00-H

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0009

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0010

Error ID: 0011

S7000 Call Back Handling Draft K 42520051 00-H

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0014

Error ID: 0020

S7000 Call Back Handling Draft K 42520051 00-H

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0028

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0040

Error ID: 0050

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0055

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0056

Error ID: 0064

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0065

Error ID: 0067

S7000 Call Back Handling Draft K 42520051 00-H

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0081

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0088

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0092

S7000 Call Back Handling Draft K 42520051 00-H

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0095

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0097

Error ID: 0099

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0100

Error ID: 0131

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0132

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0139

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0141

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0142

Error ID: 0143

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0145

Error ID: 0146

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0147

Error ID: 0148

S7000 Call Back Handling Draft K 42520051 00-H

Error ID: 0149

S7000 Call Back Handling Draft K 42520051 00-H

5.3.3 20..5999 0020_5999_Others

Error ID: 0020

5.3.4 150..199 Variodyn E