GeN2
GeN2
T r o u b l e S
T r o u b l e Sh o o
h o o t i n g G u i d e
t i n g G u i d e
Copyright 2002, OTIS GmbH & Co. OHG Berlin. Copyright 2002, OTIS GmbH & Co. OHG Berlin.
No part of this document may be copied or reproduced in any form or by any means without the prior written No part of this document may be copied or reproduced in any form or by any means without the prior written consent of OTIS GmbH & Co. OHG.
consent of OTIS GmbH & Co. OHG.
Authorization Date D1:
Authorization Date D1:
Draft
Draft
R
Ru
un
nn
niin
ng
g o
on
n P
PC
CB
B::
M
MC
CB
BIIIIII:: G
GA
AA
A2
26
68
80
00
0K
KF
F1
1
S
SP
PB
BC
C:
: G
GA
AA
A2
26
68
80
00
0K
KB
B
TC
TCBC
BC::
GA
GAA2
A268
680
00
0KA
KA1,
1,2
2,3
,3 D
DC
CSS
SS5:
5: GA
GAA
A2
243
435
50B
0BD1
D11
1
S
So
offttw
wa
arre V
e Ve
errs
siio
on
n:: M
MC
CB
BIIIIII:: G
GA
AA
A3
30
07
76
62
2B
BA
AA
A
S
SP
PB
BC
C:
: G
GA
AA
A3
30
07
76
60
0A
AA
AB
B
T
TC
CB
BC
C::
G
GA
AA
A2
23
30
00
08
81
1A
AA
AB
B
D
DC
CS
SS
S5
5:
: G
GA
AA
A3
30
03
32
28
8A
AA
AE
E
Document Revision :
Document Revision :
D
Da
atte
e
A
Au
utth
ho
orr
P
Pa
ag
ge
es
s
C
Co
om
mm
me
en
ntt
N
CONTENTS
CONTENTS
1
1
Ele
Elevat
vator
or sta
status
tus and
and fai
failure
lure cla
classif
ssificat
ication
ion ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 5
5
2
2
Tro
Troubl
uble
e sho
shootin
oting
g flo
flow
w char
chartt ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 6
6
3
3
Vis
Visual
ual che
check
ck on
on E &
E & I p
I pane
anell ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 7
7
4
4
Man
Manual
ual Res
Rescue
cue Ope
Operati
ration
on (MR
(MRO)
O) ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
.. 11
11
4.1
4.1 Con
Condit
dition
ions for
s for not lift
not lifting the bra
ing the brake via MRO
ke via MRO ....
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 11
11
4.2
4.2 Brake
Brake relea
release
se chec
checks
ks ...
...
...
...
...
...
...
...
...
... 11
11
5
5
Fai
Failur
lure
e han
handli
dling
ng on
on the
the SPB
SPBC
C ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 12
12
5.1
5.1 Serv
Service
ice Tool
Tool com
communic
munication
ation failure
failures
s ...
...
...
...
...
...
...
... 12
12
5.2
5.2 Failu
Failures
res displa
displayed
yed on
on SDI...
SDI...
...
...
...
...
...
...
... 12
12
6
6
Fai
Failur
lure han
e handli
dling on T
ng on TCB
CBC....
C...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 15
15
6.1
6.1 Blinki
Blinking
ng even
event
t messa
messages...
ges...
...
...
...
...
...
...
.... 15
15
6.2
6.2 Opera
Operating
ting syste
system
m relate
related
d failur
failures
es ...
...
...
...
...
...
...
... 17
17
6.3
6.3 Opera
Operationa
tional
l contr
control
ol subs
subsyste
ystem
m relat
related
ed failur
failures...
es...
...
...
...
... 17
17
6.4
6.4 Motio
Motion
n contr
control
ol subs
subsyste
ystem
m relate
related
d failure
failures...
s...
...
...
...
...
... 19
19
6.5
6.5 Doo
Door
r con
contro
trol
l sub
subsy
syste
stem
m rela
related
ted fai
failur
lures
es ....
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 20
20
6.6
6.6 Signa
Signaling
ling subsy
subsystem
stem relat
related
ed failures
failures ...
...
...
...
...
...
...
... 21
21
6.7
6.7 Group
Group functi
function
on relat
related
ed failur
failures...
es...
...
...
...
...
...
...
... 21
21
6.8
6.8 Syst
System
em relat
related
ed failure
failures
s ...
...
...
...
...
...
...
...
...
.... 22
22
7
7
Fai
Failur
lure
e han
handli
dling
ng on
on MCB
MCBIII
III ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 23
23
7.1
7.1 Syst
System
em (SYS)
(SYS) relate
related
d messa
messages...
ges...
...
...
...
...
...
... 23
23
7.2
7.2 Inve
Inverter
rter (INV)
(INV) relate
related
d messa
messages...
ges...
...
...
...
...
...
... 25
25
7.3
7.3 CAN
CAN bus
bus relate
related
d mess
messages...
ages...
...
...
...
...
...
... 26
26
7.4
7.4 Motio
Motion
n com
commands
mands (MC)
(MC) relate
related
d mess
messages
ages ...
...
...
...
...
...
... 27
27
7.5
7.5 Analo
Analog
g load
load weig
weighing
hing (ALW)
(ALW) relate
related
d messa
messages
ges ...
...
...
...
...
... 29
29
7.6
7.6 Motio
Motion
n logic
logic state
state (MLS)
(MLS) relate
related
d mess
messages...
ages...
...
...
...
...
... 29
29
7.7
7.7 Driv
Drive
e contr
control
ol (DRV)
(DRV) relate
related
d mess
messages
ages ...
...
...
...
...
...
...
... 31
31
7.8
7.8 Learn
Learn run
run (LRN)
(LRN) and
and enco
encoder
der adjus
adjustmen
tment (A
t (ADJ)
DJ) relat
related
ed mess
messages
ages...
...
... 33
33
8
CONTENTS
CONTENTS
1
1
Ele
Elevat
vator
or sta
status
tus and
and fai
failure
lure cla
classif
ssificat
ication
ion ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 5
5
2
2
Tro
Troubl
uble
e sho
shootin
oting
g flo
flow
w char
chartt ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 6
6
3
3
Vis
Visual
ual che
check
ck on
on E &
E & I p
I pane
anell ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 7
7
4
4
Man
Manual
ual Res
Rescue
cue Ope
Operati
ration
on (MR
(MRO)
O) ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
.. 11
11
4.1
4.1 Con
Condit
dition
ions for
s for not lift
not lifting the bra
ing the brake via MRO
ke via MRO ....
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 11
11
4.2
4.2 Brake
Brake relea
release
se chec
checks
ks ...
...
...
...
...
...
...
...
...
... 11
11
5
5
Fai
Failur
lure
e han
handli
dling
ng on
on the
the SPB
SPBC
C ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 12
12
5.1
5.1 Serv
Service
ice Tool
Tool com
communic
munication
ation failure
failures
s ...
...
...
...
...
...
...
... 12
12
5.2
5.2 Failu
Failures
res displa
displayed
yed on
on SDI...
SDI...
...
...
...
...
...
...
... 12
12
6
6
Fai
Failur
lure han
e handli
dling on T
ng on TCB
CBC....
C...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 15
15
6.1
6.1 Blinki
Blinking
ng even
event
t messa
messages...
ges...
...
...
...
...
...
...
.... 15
15
6.2
6.2 Opera
Operating
ting syste
system
m relate
related
d failur
failures
es ...
...
...
...
...
...
...
... 17
17
6.3
6.3 Opera
Operationa
tional
l contr
control
ol subs
subsyste
ystem
m relat
related
ed failur
failures...
es...
...
...
...
... 17
17
6.4
6.4 Motio
Motion
n contr
control
ol subs
subsyste
ystem
m relate
related
d failure
failures...
s...
...
...
...
...
... 19
19
6.5
6.5 Doo
Door
r con
contro
trol
l sub
subsy
syste
stem
m rela
related
ted fai
failur
lures
es ....
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 20
20
6.6
6.6 Signa
Signaling
ling subsy
subsystem
stem relat
related
ed failures
failures ...
...
...
...
...
...
...
... 21
21
6.7
6.7 Group
Group functi
function
on relat
related
ed failur
failures...
es...
...
...
...
...
...
...
... 21
21
6.8
6.8 Syst
System
em relat
related
ed failure
failures
s ...
...
...
...
...
...
...
...
...
.... 22
22
7
7
Fai
Failur
lure
e han
handli
dling
ng on
on MCB
MCBIII
III ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 23
23
7.1
7.1 Syst
System
em (SYS)
(SYS) relate
related
d messa
messages...
ges...
...
...
...
...
...
... 23
23
7.2
7.2 Inve
Inverter
rter (INV)
(INV) relate
related
d messa
messages...
ges...
...
...
...
...
...
... 25
25
7.3
7.3 CAN
CAN bus
bus relate
related
d mess
messages...
ages...
...
...
...
...
...
... 26
26
7.4
7.4 Motio
Motion
n com
commands
mands (MC)
(MC) relate
related
d mess
messages
ages ...
...
...
...
...
...
... 27
27
7.5
7.5 Analo
Analog
g load
load weig
weighing
hing (ALW)
(ALW) relate
related
d messa
messages
ges ...
...
...
...
...
... 29
29
7.6
7.6 Motio
Motion
n logic
logic state
state (MLS)
(MLS) relate
related
d mess
messages...
ages...
...
...
...
...
... 29
29
7.7
7.7 Driv
Drive
e contr
control
ol (DRV)
(DRV) relate
related
d mess
messages
ages ...
...
...
...
...
...
...
... 31
31
7.8
7.8 Learn
Learn run
run (LRN)
(LRN) and
and enco
encoder
der adjus
adjustmen
tment (A
t (ADJ)
DJ) relat
related
ed mess
messages
ages...
...
... 33
33
8
9
9
GLO
GLOSSA
SSARY
RY ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
... 36
36
10
10 Repor
Reports
ts for
for feedbac
feedback...
k...
...
...
...
...
...
...
...
...
...
...
...
... 39
39
10.1
10.1 Elev
Elevator
ator statu
status
s...
...
...
...
...
...
...
...
...
...
... 39
39
10.2
10.2 Even
Event loggi
t logging list to be
ng list to be filled ou
filled outt ...
...
...
...
...
...
...
...
... 40
40
10.3
10.3 Param
Parameters re
eters relate
lated to MCBI
d to MCBIII
II ...
...
...
...
...
...
...
...
... 41
41
10.4
10.4 Param
Parameters
eters relat
related to
ed to TCBC
TCBC ...
...
...
...
...
...
...
...
... 42
42
10.5
INTRODUCTION
INTRODUCTION
The trouble shooting guide helps to analyze the failure
The trouble shooting guide helps to analyze the failure when disturbances are occurring and
when disturbances are occurring and
describe the way how to proceed to
describe the way how to proceed to repair the failure. The guide includes several parts con-
repair the failure. The guide includes several parts
con-cerning the different sub-components being part of the GeN2 system.
cerning the different sub-components being part of the GeN2 system.
The different parts of t
The different parts of the trouble shooting guide are listed below.
he trouble shooting guide are listed below.
P
Pa
arrtt
T
Tiittlle
e
1
1
Elevator status and failure classification
Elevator status and failure classification
2
2
Trouble shooting flow chart
Trouble shooting flow chart
3
3
Visual check on the E & I – Panel
Visual check on the E & I – Panel
••
LED’s
LED’s
••
SDI
SDI
••
Service buttons
Service buttons
4
4
Manual Rescue Operation (MRO)
Manual Rescue Operation (MRO)
5
5
Failures handling on the
Failures handling on the service operation (SPBC)
service operation (SPBC)
6
6
Failures handling on the
Failures handling on the operating system (TCBC)
operating system (TCBC)
7
7
Failures handling on the drive system (MCBIII)
Failures handling on the drive system (MCBIII)
8
8
Failures handling on the door system (DCSS5)
Failures handling on the door system (DCSS5)
9
9
Glossary
Glossary
10
10
Feedback reports for root cause
Feedback reports for root cause analysis including:
analysis including:
••
Elevator status
Elevator status
••
Error logging list
Error logging list
••
Parameter list (MCBIII, TCBC, DCSS5)
Parameter list (MCBIII, TCBC, DCSS5)
In case of failures which are not handled in this document and if the trouble is not located, then: In case of failures which are not handled in this document and if the trouble is not located, then:
Fill out the event logging report for: TCBC and/or MCBIII and/or Fill out the event logging report for: TCBC and/or MCBIII and/or SPBC and/or DCSS5SPBC and/or DCSS5
Note all remarks concerning the disturbanceNote all remarks concerning the disturbance
1 Elevator status and failure classification
Status Observation
❏ elevator is running with failure _________________________________________________
❏ elevator is blocked _________________________________________________
❏ 1) Floor: _________________________________________________ a) Hoistway and car door opened _________________________________________________ b) Hoistway door closed _________________________________________________
❏ 2) Between the floors and _________________________________________________
The list given below shows the possible failures related to the GeN2 electrical system. The
failures are classified according to the corresponding root cause.
Failure occurring due to ...
Class
Safety chain (broken)
SAFDefective parts:
PCB, speed encoder, EPROM, EEPROM
Switch, Sensor
DEF
Wrong wiring
WIRMissing voltage (power supply)
POWInput not available or missing signal
SIGWrong operation
OPEWrong parameter setup
PARDefective battery function
BATWrong communication (CAN-bus)
COMWrong measurement
MEASticky brake lining (speed encoder)
BRANo failure, for information only
Please mark with a cross the right status
For your own documentation only
3 Visual check on E & I panel
SPBC
SERVICE PANEL BOARD with CAN
This part includes:
• Contract speed information
• Battery charge status
• SPBC functionality and communication check
Signal LED Status What does the status mean
off low / no speed; speed is lower than contract speed (v<85%vnom)
on contract speed (vnom) on
CON-SPEED
blinking Over speed as v>115%vnom during Normal run OPE
off Battery absent or over voltage fault BAT
on Fast charging BAT-CHARGE
blinking Pre-charge qualification
off Pre-charge qualification / Fast charging
MAINTENANCE
on Maintenance charging
off Pre-charge qualification/ Fast charging/ Maintenance charging
on Battery absent or over voltage fault / charging fault BAT
FAULT
blinking Charge pending (temperature out of range) BAT
off • No power Check the battery and power supply POW
on • Self test failed Replace the SPBC DEF
SPB_OK
blinking SPBC local software is properly running, self test passed off SPBC supplied from controller
on Not defined BAT
• 'Battery mode' Check the power supply wiring from
TCBC POW
BAT-MODE
blinking
• main switch is off Operate main switch (OCB) DEF
off CAN Bus not available (e.g. CAN wire is broken) COM
on Not defined COM
CAN_OK
blinking CAN Bus available
Please mark with a cross the right status
For your own documentation only
VISUAL CHECK on E & I panel (continued)
SPBC
SERVICE PANEL BOARD with CAN
This part includes:
• Information related to the MCB functionality
• The elevator status for a normal or inspection run
• Information related to the door function
• Information related to the safety chain
Signal LED Status What does the status mean off No Group function
GRP
on Group function okay
on Normal Mode
off NAV, DTO, DTC, ATT, CHC, EFO, EFS, ISC, drive-fault OPE
NOR
blinking The Hoistway access detection (ACC)is active.Release through ERO or power off OPE
on Inspection Mode (TCI or ERO operated)
INS
blinking TCI-Lock function active (Top of car procedure not correctly
fol-lowed) OPE
ES off No emergency stop
DW on Door Wiring (Hoistway door contacts closed) DFC on Door Fully Closed (Safety chain closed) DOL on Door Open Limit ( front or rear ) reached
DOB on Door Open Button operated
Please mark with a cross the right status
For your own documentation only
VISUAL CHECK on E & I panel (continued)
SPBC
SERVICE PANEL BOARD with CAN
This part includes the service buttons used for different needs, like
- Car call to top/bottom landing
- Cancel hall call
- Disable door operation - Remote tripping/resetting
• Brake release buttons
• REM service button
Signal LED Status What does the status mean
CCTL on Car Call to Top Landing (button is operated)
CHCS on Cancel Hall Call Switch (button is operated)
TEST Test button to display the errors at SDI, when car position is blinking
CCBL on Car call to Bottom Landing (button is operated)
DDO on Disable Door Operation (button is operated)
NURF on Emergency Power Test (button is operated)
RTB on Remote Tripping Button (button is operated)
REB - Common Button for RTB & RRB
RRB on Remote Resetting Button is operated Note: RRB or RTB are only accepted if REB is pressed simultaneously
on Brake supply apparent, Automatic Manual Brake Release and BRB2 ON
BRB1
off No voltage on brake supply connection (Pn: Brake)
on Voltage supplied for Automatic Manual Brake Release Also on at acti-vated brake during normal run (voltage feedback)
BRB2
off No voltage supplied for Automatic Manual Brake Release
REM off Out of Service Button (not active)
VISUAL CHECK on E & I panel (continued)
SPBC
SERVICE PANEL BOARD with CAN
This part shows the errors displayed on the SDI, when the car position is blinking:
• The errors displayed on the SDI by pushing the TEST button (LED's are on)
- 8 green LED's for upwards
- 8 green LED's for downwards
• The elevator car status at the door zone
Signal LED Status What does the status mean 15
14
13 Received out of range parameters PAR
12 Three encoder A faults, stored in E2PROM DEF
11
10 HTS failure DEF
9 DZI failure SIG
8 Over speed was reached MEA
7 No communication with master COM
6
5 Battery failure BAT
4 E2PROM failure DEF
3 Measured direction does not match dictated direction MEA
2 Encoder B failure DEF
1 Encoder A failure DEF
U P 1 5 1 3 1 2 1 4 1 1 1 0 9 1 0 5 3 2 4 7 6 8 D Z
0 Task timing error MEA
Signal LED Status What does the status mean off Outside Door Zone (No DZ Signal)
DZ on Inside Door Zone (Interruption of Automatic Manual Brake Release,
Buzzer)
Please mark with a cross the displayed error
For your own documentation only
4 Manual Rescue Operation (MRO)
4.1 Conditions for not lifting the brake via MRO
Possible state or message Reason
SPBC is not in Battery mode Controller is not switched off Error # 4 on SDI is detected E2PROM failed
Error # 7 on SDI is not detected Communication with master is established Error # 8 on SDI is detected Over speed is detected (governor not tripped) Error # 12 on SDI is detected Encoder A error
Error # 13 on SDI is detected Parameters are out of range
4.2 Brake release checks
Button LED status Function
BRB1 BRB2 BRB1 BRB2 Possible reason What to do
If the car does not move, then:
• empty battery due to a too long rescue operation
charge battery
• Parameters are not OK set default values on TCBC:
M-1-3-1-7 Activation
of BRE pressed Key locked blinking blinking
• Car in balance bring weights on the top of the car
5 Failure handling on the SPBC
5.1 Service Tool communication failures
SVT: System Menu is not available (only SPBC)
Possible reason What to do
• TCBC has no CAN connection check CAN wire between TCBC and SPBC WIR • TCBC is powered down search cause for missing power POW
• TCBC is defect replace TCBC DEF
SVT: MCBIII is not available (only SPBC)
Possible reason What to do
• MCBIII has no CAN connection check CAN wire between TCBC and MCBIII WIR • MCBIII is powered down search cause for missing power POW
• MCBIII is defect replace MCBIII DEF
5.2 Failures displayed on SDI
When the car position is blinking, then an error has occurred. Press TEST button to display the errors at SDI. TEST shows event ‘00’
Possible reason What to do
• hardware/software failure replace SPBC DEF
SDI blinking in both directions while stopping. TEST shows event ‘01’
Possible reason What to do
check rescue encoder wiring WIR
• no signals from encoder-track A
replace rescue encoder DEF
SDI shows speed in both directions. TEST shows event ‘02’
Possible reason What to do
check rescue encoder wiring WIR
• no signals from encoder-track B
replace rescue encoder DEF
SDI shows speed in both directions. TEST shows event ‘03’
Possible reason What to do
• rescue encoder-track A and B are exchanged
change SDI-DIR parameter (0->1 or 1->0) or exchange
pin4 and pin 5 at SPBC OPE
SDI mostly shows correct direction. TEST shows event ‘03’
Possible reason What to do
• rescue encoder-track A and B are exchanged
change SDI-DIR parameter (0->1 or 1->0) or exchange
pin4 and pin 5 at SPBC PAR
• invalid phase shift between encoder–
track A and B replace rescue encoder DEF
• Rollbacks adjust the drive to prevent rollbacks OPE
SDI blinking in both directions while running
Possible reason What to do
check rescue encoder wiring SIG
• no signals from rescue encoder
replace rescue encoder DEF
TEST shows event ‘04’
Possible reason What to do
• E2Prom of SPBC is defective. After loss of power the direction and scale of SDI is not reliable any more.
Replace SPBC
DEF
TEST shows event ‘05’ (only SPBC)
Possible reason What to do
Replace battery BAT
• Battery is defect. The SPBC will have no power supply if the controller is
switched off. check battery wiring WIR
TEST shows event ‘07’
Possible reason What to do
check power supply of TCBC POW
check CAN_OK led at TCBC COM
check CAN wiring between TCBC and SPBC WIR • no CAN communication with master
check ground connection between SPBC and TCBC WIR
TEST shows event ‘08’
Possible reason What to do
• car has reached over speed check encoder parameter EncoderWidth DEF
• OS safety contact has opened reset contact OPE
• parameter NomSpeed is too small for this unit
check parameter NomSpeed
PAR
TEST shows event ‘09’
Possible reason What to do
TEST shows event ‘10’
Possible reason What to do
• The HTS temperature is higher than the parameter HtsMax.
Shut down the complete System. Wait until the environ-ment temperature is cooling down at the floor with the
E&I panel.
OPE
TEST shows event ‘12’
Possible reason What to do
• Encoder A fails 3 times erase events (at TCBC with SVT); check encoder A
wire; start a controlled run DEF
TEST shows event ‘13’
Possible reason What to do
• one or more parameters (received from TCBC) is out of range
check all parameters (see chapter ‘Communication /
6 Failure handling on TCBC
6.1 Blinking event messages
wrongBoard
Possible reason What to do
• The software cannot identify the
board. replace the TCBC. DEF
Learn Run
Possible reason What to do
• The drive package is performing its Learn Run
• The drive package is adjusting the encoder.
wait until the learn run is completed.
DoorBridge DW or DFC input has not been low while the door was opened.
Possible reason What to do
check safety chain
• bridged door lock.
This event is stored into EEPROM so that the ONLY way to bring the elevator into operation again is by using INS.
SIG
Switch INS Elevator is taken out of service.
Possible reason What to do
• Landing door was opened for longer than 2 seconds.
This event is stored into EEPROM so that the ONLY way to bring the elevator into operation again is by using INS.
OPE
TCI-lock
Possible reason What to do
• The sequence to leave TCI-mode was not correctly followed
Correct steps are: 1. open door 2. switch TCI off 3. close door
OPE
1LS+2LS on
Possible reason What to do
• Limit switches 1LS and 2LS are active at the same time.
Check power supply of the position reference system.
POW
Adr-Check
Possible reason What to do
• Some RSL I/Os have to be pro-grammed to a valid address and are not allowed to be set to 00-0 or 01-0. Currently only one I/O is checked: 691 – TCI
Set I/O 691 to a valid address
SE-Fault
Possible reason What to do
• The car cannot start due to missing SE-signal
Check the door bypass
SIG
1TH-Fault
Possible reason What to do
• The DBR-contact which is connected to the input 1TH is opened.
The drive is powered down to allow cooling. SIG
2TH-Fault
Possible reason What to do
• One of the contacts which is con-nected to the 2TH is opened.
The drive is powered down to allow cooling.
SIG
PowerSave
The drive package is currently switched off to save energy. start DCS!
Possible reason What to do
• Normal operation is not allowed until the Door Check Sequence has been completed successfully.
• The DCS is required again if one of the parameters TOP or BOTTOM is changed.
Enter M-1-3-5 to start the DCS!
OPE
Shutdown
Possible reason What to do
• The drive reports a Shutdown See event logging of MCBIII. OPE
check CAN-wiring
• CAN-Communication not working
check CAN-LEDs COM
MCLS/SKL-3
Possible reason What to do
• Car Light Switch in Machine Room has been switched off
Switch on the car light switch/related setup: MCLS (697)
OPE • Car Light Relay on top of car is
dropped.
Check the car light relay/related setup: CLR (1000) PAR
LBG/CSP-2
Possible reason What to do
SPB: HTS
Possible reason What to do
• Hall Temperature Sensor from Serv-ice Panel Board is activated. Car is shutdown at next commitable floor and taken out of service
Wait until the temperature is lower than parameter SPB-temperature
SPB-Comm.
Possible reason What to do
check CAN-wiring • CAN-Communication to SPBC is not working. check CAN-LEDs COM
6.2 Operating system related failures
Task Timing
software entered endless loop W_Dog Reset
watchdog circuit on LCBII was triggered Illegal Int
illegal interupt was executed CanTxFull
CAN messages cannot be sent CanBusOff
CAN communication has been restarted MCB-Comm.
No CAN connection to the drive SPB-Comm.
No CAN connection to the SPBC
Note: the above information (wrong software run and communication) is for engineering only
6.3 Operational control subsystem related failures
OpMode NAV
OCSS is not available due to drive fault (e.g. drive-fault (NR). This mode is also active after INS before the COR starts
EPO shutd.
Possible reason What to do
• car is not able to run during EPO; the next car is allowed to recover
related setup: NU (017) NUSD (018) NUSG (019) OPE
OpMode DTC
Possible reason What to do
• door was not able to close (missing DCL, DFC or DW) within timeout related setup DCL (694) RDCL (695) DOOR, REAR DTC-T SIG OpMode DTO
Possible reason What to do
• door was not able to open (missing DOL) within timeout
related setup DOL (000) RDOL (544) DOOR, REAR DTO-T PAR OpMode DCP
Possible reason What to do
• car was not able to answer a call within timeout (e.g. door was held open manually) related setup DCP-T PAR PDS active
Possible reason What to do
• partition door switch is opened related setup
PDD (784) PAR
DS bypass
Possible reason What to do
• Malfunction of Disable Door Switch Relays (DDSR) for Generic Firemen Service. related setup DDSRC (970) PAR EEC bypass
Possible reason What to do
• Malfunction of Disable Emergency Exit Contact Relay (DEMERC) for Generic Firemen Service.
related setup
6.4 Motion control subsystem related failures
Correct.Run A correction run was performed (e.g. after INS, NAV)
/ES in FR ES-input was activated during Fast Run
/ES in SR ES-input was activated during Slow Run
TCI/ERO on TCI or ERO has been switched on
SE-Fault SE signal is missing
Possible reason What to do
• The car cannot start due to missing SE-signal
Check the door bypass
SIG
/DZ in NST DZ-signal was lost or not detected at all after having stopped
Possible reason What to do
• The inputs signals 1LV, 2LV on MCBIII are missing
Check the input signals on MCBIII
SIG
check CAN-wiring
• CAN-Communication not working
check CAN-LEDs COM
/DFC in FR car door has been opened during Fast Run
Possible reason What to do
• DFC input signal is missing check the signal SIG
/DFC in SR car door has been opened during Slow Run
Possible reason What to do
• DFC input signal is missing check the signal SIG
DrvShutdown
Possible reason What to do
• The drive reports a Shutdown See event logging of MCBIII. OPE
check CAN-wiring
• CAN-Communication not working
check CAN-LEDs COM
1TH-Fault
Possible reason What to do
• The DBR-contact which is connected to the input 1TH is opened.
2TH-Fault
Possible reason What to do
• One of the contacts which is con-nected to the 2TH is opened.
The drive is powered down to allow cooling.
SIG
RSL Adr Chk
Possible reason What to do
• Some RSL I/Os have to be pro-grammed to a valid address and are not allowed to be set to 00-0 or 01-0. Currently only one I/O is checked: 691 – TCI
Set I/O 691 to a valid address related setup: TCI(691)
PAR
PowerSave
Possible reason What to do
• The drive package has been powered on related setup: PDR-D PAR
/DW in FR landing door has been opened during Fast Run
Possible reason What to do
• DW input signal is missing check the signal SIG
/DW in SR landing door has been opened during Slow Run
Possible reason What to do
• DW input signal is missing check the signal SIG
6.5 Door control subsystem related failures
DBP: dfc_SE
Possible reason What to do
• While the door was opening or fully opened, the door bypass was found to be inactive (DFC low or SE high)
related setup: EN-RLV , EN-ADO PAR DCL in [ ]
Possible reason What to do
• (R)DCL was active while the door was fully opened related setup DCL (694) RDCL (695 PAR
DoorBridge DW or DFC was not low during the last door cycle
Possible reason What to do
• the safety chain is bridged • remove the bridge SAF
DOL:alw. on
Possible reason What to do
• (R)DOL was active while the door was fully closed. This event is also logged when the fuses of the door system are burned.
This event is not logged within the first 40 seconds after system startup.
related setup DOL (000) RDOL (544) PAR Hwy Access
Possible reason What to do
• Landing Door was opened. see description for blinking message 'Switch INS' OPE
6.6 Signaling subsystem related failures
RSL parity Two remote stations with the same address are connected to the same link
Possible reason What to do
• Wrong connection Check the RS connections WIR
RSL sync Synchronization lost on remote serial link
Possible reason What to do
• Line terminator is defective Change the line terminator DEF
6.7 Group function related failures
RNG1 msg
data error on Duplex/Triplex ring RNG1 time
no ring messages received from other car for a specific time RNG1 sio
framing error on Duplex/Triplex ring RNG1 tx
6.8 System related failures
SPB-Alert The Service Panel Board detected a malfunction which hinders a manual rescue operation with SPBC and SDI.
Possible reason What to do
• defective speed encoders for SDI DEF
• defective E2PROM on SPBC DEF
• Missing battery for SPBC
Press the SPBC-buttons REB + DDO simultaneously to locate the error.
BAT
SPB:TempHTS
Possible reason What to do
• The Service Panel Board detected an over temperature. related setup SPB-Temp PAR
7 Failure handling on MCBIII
Actual errors: <M> <2> <2> <1> ;saved errors: <M> <2> <2> <2>
7.1 System (SYS) related messages
SYS : Warmstart Software reset without power reset
Possible reason What to do
• defective EPROM start self test: M-2-3
- 0 = Self test was not yet executed
- ? = Executing the self test - + = Self test O.K.
- - = Self test not O.K.
if negative, then change EPROM
DEF
• time was not sufficient to store all occurred events into the saved event logging
the error can be neglected if it occurs in the saved event
logging MEA
• hardware problem change MCBIII DEF
SYS : Shut down A run was interrupted because of a shut down error.
Possible reason What to do
• the error which caused the shut down is displayed with <shift> <down>
Message allows a quick overview over the last shut downs, for further information refer to the concerned event.
OPE
SYS : DDP The elevator is blocked (DDP time error)
Possible reason What to do
• DDP time exceeded (default: 20 sec) LV magnet is missing SIG • The time between two positive edges
of LV-magnets was shorter than the DDP time adjusted by SVT.
The DDP time error is often caused by other events.
MEA
SYS : E2P failure EEPROM writing or reading problems
Possible reason What to do
• no EEPROM on the MCBIII plug EEPROM correctly DEF
• defective EEPROM start self test: M-2-3
- 0 = Self test was not yet executed
- ? = Executing the self test
- + = Self test O.K. - - = Self test not O.K.
if negative, then change EEPROM
DEF
• defective MCBIII change MCBIII DEF
SYS : E2P Default All parameters are set to their default values.
Possible reason What to do
• The unit is not able to run with default values.
If the parameters were stored by SVT (M-3-7) the setup can be reload by SVT (M-3-8). Otherwise the unit has to be readjusted again.
SYS : E2P InvPara Any parameters stored in the EEPROM are outside the range of their minimal or maximal values.
Possible reason What to do
• error occurs when the EEPROM is removed and replaced with new one
Note all parameters, set DEFAULT parameters, readjust
the parameters again. PAR
• EEPROM self test (M-2-3) failed Change EEPROM. DEF
Sub-code for further information: Press <Down> or <Shift-3>
p • number of parameter which is out of range (EEPROM(p): information for Engineering only SYS : ParaConflkt The parameter ConNmot is inconsistent with other parameters.
Possible reason What to do
• The maximum INS SPE is at syn-chronous speed of the motor, the maximum NOM SPE is at 110 % of the synchronous speed of the motor.
Check the parameters:
CON SPE , ConNmot , Motor Type (M-3-1-GOON), MotFnom, MotNom (M-3-5-1-GOON),
INS SPE , NOM SPE (M-3-2-GOON).
PAR
SYS : Power fail The line voltage was outside its specified range for a short time (e.g. one phase is lost).
Possible reason What to do
• voltage loss (line) check line connections L1 to L3 POW • short voltage drop or voltage variation verification of line voltages with recorder necessary POW
SYS : < 24V Supply 24V power supply is missing on MCBIII
Possible reason What to do
• external short circuit in the 24VDC power supply
switch off the unit, remove all plugs, out of P1, then switch on the inverter and check if an error message will indicate, if not then the wiring is faulty
POW
• defective MCBIII change MCBIII DEF
• defective PDB change inverter section DEF
SYS : < 15V Supply Inverter relay dropped.
Possible reason What to do
• see error 'SYS: <24V Supply' POW
SYS : Inv-Relay Inverter relay dropped, will logged at switch off of the inverter each time
Possible reason What to do
• Power save mode is active: The error is logged every time when the inverter is switched off by removing HL1 or 110V. information only OPE
• The drive blocks if one inverter or safety error occurs several times in series.
refer to error 1 ”SYS: Shut Down”
SYS : not all err Not all events have been stored during last power-OFF Possible reason What to do
• Too much errors have been logged before power has been switched off. Some events and/or maintenance in-formation may be lost.
Notify all saved error events and clear error logging.
MEA
SYS : 1LS + 2LS 1LS and 2LS are activated at the same time.
The input display (M-1-2-goon) can be compared to the TCBC input display
Possible reason What to do
• faulty wiring check wiring WIR
• defective sensor change sensor DEF
• voltage of LS sensors is missing check voltage supply POW
• defective MCBIII change MCBIII DEF
SYS : ADC Offset Zero reference for A/D converter invalid
Possible reason What to do
• line voltage variation verification of line voltages with recorder necessary POW • defective MCBIII change MCBIII (if occurs permanently) DEF • defective inverter change inverter (if occurs permanently) DEF
7.2 Inverter (INV) related messages
INV : > Volt DC DC link voltage too high
Possible reason What to do
• wrong or defective brake resistor (DBR)
Switch off, wait until DC link capacitor is discharged,
measure DBR; change if necessary. DEF
• faulty wiring to the DBR check wiring WIR
• defective inverter change inverter DEF
INV : > Heat Packg IGBT heat sink temperature exceeded, fault message occurs 10°C before shut down (err. = 80°C, fatal e. = 90°C).
Possible reason What to do
• defective fan
test fan: M-2-7
- The fan should run with fast speed for one minute after activating this test.
change the fan if necessary
DEF
• dusty / clogged air filters clean / exchange air filters DEF
• defective temperature sensor change inverter DEF
INV : < Volt DC Low DC link voltage (<350 V at 480 V package).
The message is displayed (not stored) after switch off of the inverter
Possible reason What to do
• loss of line voltage check wiring of line voltage supply POW • line voltage is too low verification of line voltages with recorder necessary SIG
INV : > Curr IGBT Short circuit in transistor modules.
Possible reason What to do
• short circuit in the motor cable or earth leakage
check motor cable
WIR
• defective PDB change inverter DEF
• defective inverter (error occurs permanently) change inverter DEF
INV : > Curr Motor Motor current exceeds 240% of the inverter current.
Possible reason What to do
• power of inverter is too low check inverter power: reduction of acceleration rate may
help (<M> <3> <2> <GOON> ACC) PAR
• short circuit in the motor or earth leakage
check motor and motor cable
WIR • faulty encoder signals check encoder, encoder cable WIR
INV : Temp meas Temperature measurement at the heat sink does not work correctly
Possible reason What to do
• ambient temperature is very low (< 5°C)
Check monitored IGBT heat sink temperature: M-2-1
verify temperature in machine room MEA
• defective Temp. sensor (error occurs permanently)
change inverter, danger of overheating for MCBIII or
inverter DEF
INV : brake chopp Brake IGBT has a short circuit or is not connected
Possible reason What to do
• DBR not properly connected check connection of DBR WIR
• defective Brake IGBT change Inverter DEF
7.3 CAN bus related messages
CAN: BusOff generated by CAN bus software
Possible reason What to do
• CAN Bus disconnected check the connection: P6 Pin1: VRS 30VDC P6 Pin2: CAN_H P6 Pin3: CAN_L P6 Pin4: HL2
COM
• defective MCB_III change MCB_III DEF
CAN: CAN error Generated by CAN bus software CAN: OPB_Init Initialization after power on failed CAN: TxQueueFull Generated by CAN bus software
CAN:1/2LSUndefnd No message received from TCBC concerning the state of the 1LS/2LS limit switches over the last 4 seconds.
7.4 Motion commands (MC) related messages
MC: EMERGNCY ST A normal run was interrupted by the safety chain.
Possible reason What to do
• safety chain was disconnected Check UIB, DIB: for detailed information refer to OCSS
(INS / ES / DW / DFC) SAF
M C: Command Lst Invalid motion command from TCBC
Possible reason What to do
• defective MCBIII or TCBC change MCBIII or TCBC DEF
Sub-code for further information: Press <Down> or <Shift-3> e = 1 Motion command lost during normal run
e = 2 Motion command lost during reduced run
e = 3 Motion command lost during emergency creep run e = 4 Motion command lost during relevelling run
e = 5 Motion command lost during inspection run
e = 6 rescue run or emergency run requested but car is in door zone e = 9 Motion command lost during rescue run
MC: FR w/o Learn Normal run is not possible without pr evious successfully learn run.
Possible reason What to do
• learn run not performed learn run has to be performed OPE
MC: MC + Safety Ch Motion Command of TCBC does not fit to feedback UIB, DIB
Possible reason What to do
• faulty wiring correct wiring WIR
• defective MCBIII input change MCBIII DEF
• The input signal change was to fast at inspection mode ignore MEA
MC: Encodr adj? no initial encoder adjustment has been done
Possible reason What to do
• after manual rescue operation
• when the brake replacement is done without manual rotation of the machine
perform encoder adjustment routine (M-4-2)
OPE
MC: OCSS disabld Inspection runs are allowed w/o TCBC support, normal runs are prohibited. Fatal error because UIB/DIB signals available but no commands from TCBC for normal run
Possible reason What to do
MC: Chk SW Sig incorrect state of SW signal, SW-signal indicates switching state of main contacts
Possible reason What to do
• faulty SW contactor check inputs SW SIG
• faulty wiring check wiring WIR
• defective MCBIII change MCBIII DEF
MC: Chk DBD Sig incorrect state of DBD signal (1 = Stop , 0 = run)
Possible reason What to do
• faulty SW1, BR or BY check inputs, SW, BR or BY SIG
• faulty wiring check wiring WIR
• defective MCBIII change MCBIII DEF
MC: Chk RDY Sig incorrect state of RDY signal
Possible reason What to do
• defective MCBIII change MCBIII DEF
MC: Chk BS1/BS2 incorrect state of Brake Switch signal
Possible reason What to do
• faulty BS sensors or wiring check BS sensors / wiring DEF • Brake does not lift check brake circuit / mechanic DEF
Sub-code for further information: Press <Down> or <Shift-3> (description is valid only for "BrakeSwType = 3") e = 11 Scenario 1 BS1 expected ON detected OFF
e = 12 Scenario 1 BS2 expected ON detected OFF
e = 13 Scenario 1 both BS1 and BS2 expected ON detected OFF e = 21 Scenario 2 & 3 BS1 expected OFF detected ON
e = 22 Scenario 2 & 3 BS2 expected OFF detected ON
7.5 Analog load weighing (ALW) related messages
ALW:No LoadW Cal Load weighing calibration not performed at start of a run. Run is started with pre-torque for balanced load.
Possible reason What to do
• LW calibration not performed perform load weighing calibration OPE
ALW:LoadW Sensor Invalid load weighing input values.
Possible reason What to do
• missing connection check connection P6 Pin1: VRS 30Vdc
P3 Pin1: 24 VDC (derived from VRS) (load sensors may use another 24V source) P3 Pin2: sensor signal
P3 Pin3: sensor signal P3 Pin4: HL2
SIG
• defective LWB change LWB DEF
• defective load sensor change sensor DEF
• defective MCB_III change MCB_III DEF
MLS : < ACC Dist The car did not reach the nominal speed.
Possible reason What to do
• secondary effect of Emergency Stop, Shut Downs, Correction runs
check other occurred errors
OPE
7.6 Motion logic state (MLS) related messages
MLS : < Dec Dist The distance for the deceleration is too short. The car stops without creep speed.
Possible reason What to do
• secondary effect of Emergency Stop, Shut Downs, Correction runs
check other occurred errors OPE
• it is possible that the MCBIII has miscount
check other occurred errors
MEA • The actual floor distance does not
correspond to the learned floor distance.
start learn run again
OPE
• Parameter 'T_creep' too small increase parameter 'T_creep' (M-3-3- goon) PAR
MLS : Stop in LS Limit switch 1LS / 2LS versus run direction.
Possible reason What to do
• faulty 1/2LS sensors or wiring check LS wiring WIR
• TCBC or CAN bus error check LS inputs on TCBC COM
MLS : TCB Inp Error TCBC command GOTO floor: Target < Bottom floor or Target > TOP floor
Possible reason What to do
• parameter mismatch check TOP FLOOR , BOTTOM FLOOR on MCB_III and
MLS : 1LS Ini Dec Deceleration in the bottom landing initiated by 1LS.
Possible reason What to do
• correction run ignore
• Parameter '1LS DLY' is too small. Increase parameter '1LS DLY' (M-3-3-goon). After that the deceleration distance for a correction run is to be checked, if it is still sufficient. A corr ection run is released after an inspection run.
PAR
MLS : 2LS Ini Dec Deceleration in the top landing initiated by 2LS.
Possible reason What to do
• correction run ignore
• Parameter '2LS DLY' is too small. Increase parameter '2LS DLY' (M-3-3- goon). After that the deceleration distance for a correction run is to be checked, if it is still sufficient. A corr ection run is released after an inspection run.
PAR
MLS: RLV-Count Too much consecutive relevelling runs (more than 4)
Possible reason What to do
• relevelling speed too high check parameter REL SPE PAR • defective hoistway switch check magnets and hoistway switches DEF
MLS:UIS/DIS miss UIS or DIS missed passing a door zone. The message is generated in the moment when the relevelling conditions are fulfilled. Relevelling run is not performed.
Possible reason What to do
• missing UIS or DIS sensor or wiring check sensors and wiring SIG
MLS : LV Missed LV signal was not detected during creeping, although the creep time reached 67% of DDP time. The message is displayed when the error is occurring eight times
Possible reason What to do
• secondary effect of Emergency Stop, Shut Downs, Correction runs
check other occurred errors
OPE • it is possible that the MCBIII has
mis-count
check other occurred errors
MEA • missing LV magnet or defective
sen-sors
check magnets and sensors by an INS RUN DEF
• only one LV signal was detected at units with 1LV and 2LV
check LV1, LV2 relays and LVCT time using a slow INS
RUN (CREEP SPE has to be reduced too). SIG
• defective MCBIII change MCBIII DEF
MLS : LV Lost Levelling zone lost, deceleration distance too short, see error 'MLS <Dec Dist'. The message is displayed when the error is occurring eight times
Possible reason What to do
• secondary effect of Emergency Stop, Shut Downs, Correction runs
check other occurred errors OPE
• it is possible that the MCBIII has miscount
check other occurred errors
MEA
MLS : LV Count Err MCBIII has miscount.
Possible reason What to do
• miscounting of door zones at INS operation ignore MEA • parameter TOP FLOOR is not correct check this parameter PAR • missing LV magnet or defective
sensors
check magnets and sensors by an INS RUN
DEF • only one LV signal was detected at
units with 1LV and 2LV
check LV1, LV2 relays and LVCT –time using a slow
INS RUN (Creep SPE has to be reduced for this test ). SIG MLS : LV Trig Err LV-signals rebound longer then 20 ms
Possible reason What to do
• distance between sensor and magnet
is not correct check distance between sensor and magnet COM
• defective LV sensors change sensors DEF
7.7 Drive control (DRV) related messages
DRV: EncoderWarn Encoder warning
Possible reason What to do
• possible electrical noises caused by bad shielding or ground /earth wiring
check shielding / earth connections WIR
• temporary bad contacts check wiring / connectors to encoder WIR
DRV: Encoder Err Encoder error
Possible reason What to do
• spikes on the index pulse wires caused by bad shielding or ground /earth wiring
check shielding / earth connections WIR • temporary bad contacts check wiring / connectors to encoder WIR
DRV : > Speed Over speed: the motor turns 10% faster than the dictated speed profile. The message is displayed when the error is occurring four times
Possible reason What to do
• parameter is incorrect Check the parameter 'Sys Inert' (M-3-1-goon) PAR
DRV : < Speed Low speed : the motor turns 45% slower than the dictated speed profile .
Possible reason What to do
• defective encoder Check encoder, use SVT-Menu ”PVT” (M-2-6). DEF
• defective MCBIII Change MCBIII DEF
• Inertia of the whole system is too big. Check the guide and distance between guides, check
the inertia of motor and gear. MEA
DRV : Rollb Start Rollback at start
Possible reason What to do
• Start-Stop-parameters are set incor-rectly
check start-related parameters
PAR • Load-weighing device does not work
correctly or is not correctly adjusted
check / adjust load-weighing device
OPE
Sub-code for further information (Press <Down> or <Shift-3>) s • measured max. rollback distance in [mm]
DRV : Rollb Stop Rollback at stop
Possible reason What to do
• Start-Stop-parameters are set incorrectly
check stop-related parameters
PAR
Sub-code for further information (Press <Down> or <Shift-3>) s • measured max. rollback distance in [mm]
DRV : Encoder Dir the sequence of the encoder signals is reversed
Possible reason What to do
• Encoder wrong direction Change the parameter 'Encoder Dir' PAR
DRV : OverLd >Time Motor current exceeds 200% of nominal current for more then 3 seconds. The message is displayed when the error is occurring four times
Possible reason What to do
• acceleration rate is too high decrease acceleration rate ”DEC ” (M-3-3-goon) PAR • power of inverter is too small check power of inverter and motor OPE
• fly wheel inertia is too big reduce fly wheel COM
Sub-code for further information (Press <Down> or <Shift-3>) t = 3 • 3 sec general overload
DRV: Overload Overload (warning): see error 'DRV: OverLd >Time
Possible reason What to do
• acceleration rate is too high decrease acceleration rate ”DEC” (M-3-3-goon) PAR • power of inverter is too small check power of inverter and motor OPE
DRV: Phase Down The current of one motor phase is zero. The message is displayed when the error is occurring four times
Possible reason What to do
• the motor wiring is disconnected (between inverter and motor)
check motor wiring, connectors and SW contacts
WIR • power of inverter is too high
(current <10%)
check power of inverter and motor
OPE
Sub-code for further information: Press <Down> or <Shift-3> p = 1 Phase-check failed: no current in motor phase 1 p = 2 Phase-check failed: no current in motor phase 2 p = 3 Phase-check failed: no current in motor phase 3 p = 10 Phase-check failed: no current in all motor phases
p = 20 invalid combination during current phase-check: current in single-phase only (possible leakage current)
DRV: I Overload Speed controller output (motor torque & current) has reached the internal limit see error "INV: >CURR MOTOR"
Possible reason What to do
• power of inverter is too low check inverter power reduction of acceleration rate may
help (<M> <3> <2> <GOON> ACC) OPE
• short circuit in the motor or earth leakage
check motor and motor cable WIR
• faulty encoder signals check encoder, encoder cable WIR
7.8 Learn run (LRN) and encoder adjustment (ADJ) related messages
LRN : Learn abort Learn run was aborted because of an error
Possible reason What to do
• Learn run was aborted see Error Logging (<M> <2> <1>) OPE
LRN : < Mag Len Length of magnet is too short (minimum 170 mm)
Possible reason What to do
• faulty floor will displayed in Error Logging
use magnet with the right length
DEF
LRN : > Mag Len Length of magnet is too long (maximum 450 mm)
Possible reason What to do
• faulty floor will displayed in Error Logging
use magnet with the right length
DEF
LRN : Mag Len Var Length of used magnets is varied.
Possible reason What to do
• faulty floor will displayed in Error Logging
use magnets with the same length
