Ovf20cro Adt

OTIS - OEC OVF20-CR with LCB_II Dwg : GAA21342B_ADT
Date : 2004-09-24
ENGINEERING CENTER
BERLIN Otis Variable Frequency Drive Page : 1/49
FSM Advanced diagnostics and trouble shooting

Application without encoder
OVF20-CR with LCB_II

Advanced diagnostics and trouble shooting
Authorization Date: 2004-09-24

Drive Package Number: GAA21342B1
Running on MCBIIIx: GAA26800KV6
Running on LCB_II: GCA 21240 D1 - D3 or higher
Software Version: MCBIIIx: GAA30763BAA

LCB_II: GAA30082CAC
Document Revision :
Date Author Page Comment

2004-09-24 M. TOUTAOUI 49 Original document
Unpublished Work Copyright © OTIS Elevator Company

Date : 2004-09-24
ENGINEERING CENTER

CONTENTS
1 TROUBLE SHOOTING FLOW CHART .......................................................................................................... 4
1.1 STEP 1: ELEVATOR STATUS CHECK .................................................................................................................. 5
1.2 STEP 2: FAILURE GROUP SELECTION ............................................................................................................... 6
1.3 STEP 3: FAILURE HANDLING USING SERVICE TOOL ............................................................................................ 7
1.3.1 Operational control system (LCB_II) ................................................................................................... 7
1.3.2 Drive control system (MCB_III) ........................................................................................................... 8
1.3.3 Service tool connection via drive OVF20-CR...................................................................................... 9
2 FAILURE HANDLING USING SERVICE TOOL ........................................................................................... 10
2.1 ELEVATOR IS BLOCKED ................................................................................................................................. 10
2.1.1 Failures related to the CAR AND HOISTWAY DOOR ...................................................................... 10
2.1.2 Failures related to the SAFETY CHAIN ............................................................................................ 13
2.1.3 Failures related to the VF DRIVE...................................................................................................... 14
2.1.4 Failures related to the CAR LIGHT ................................................................................................... 14
2.1.5 Failures related to the BRAKE .......................................................................................................... 15
2.2 ELEVATOR MALFUNCTION: CAR IS RUNNING WITH FAILURE .............................................................................. 16
2.2.1 Failures related to the COMMUNICATION ....................................................................................... 16
2.2.2 Failures related to the HOISTWAY SIGNALS................................................................................... 16
2.2.3 Failures related to REMOTE SERIAL LINK ...................................................................................... 21
2.2.4 Failures related to VF DRIVE ............................................................................................................ 21
2.2.5 Failures related to PERFORMANCES .............................................................................................. 28
2.2.6 Failures related to CONTACTORS AND WIRING ............................................................................ 30
2.2.7 Failures related to emergency power operation (EPO)..................................................................... 31
2.2.8 Failures related to the BRAKE .......................................................................................................... 32
2.2.9 For information only........................................................................................................................... 32
2.3 ELEVATOR FAILURES DURING INSTALLATION OR MAINTENANCE ........................................................................ 33
2.3.1 Failures related to CALIBRATION .................................................................................................... 33
2.3.2 Failures related to MANUAL RUN..................................................................................................... 34
2.3.3 Failures related to NORMAL RUN .................................................................................................... 34
2.3.4 Failures related to PARAMETER SETUP ......................................................................................... 34
2.3.5 Parameter setup: general error handling .......................................................................................... 36
3 EN81 CODE INSPECTION PROCEDURE.................................................................................................... 38
4 APPENDIX ..................................................................................................................................................... 39
4.1 5 KW PACKAGE ........................................................................................................................................... 39
4.2 CONFIGURATION ........................................................................................................................................... 40
4.3 DRIVE INTERFACE ......................................................................................................................................... 41
4.3.1 Interface to controller with LCB II ...................................................................................................... 41
4.3.2 Interface to the motor ........................................................................................................................ 41
4.4 PARAMETER SETUP ...................................................................................................................................... 42
4.4.1 Contract parameter: <M> <3> <1>.................................................................................................... 42
4.4.2 Speed Profile: <M> <3> <2> ............................................................................................................. 42
4.4.3 Vane parameters: <M> <3> <3> ....................................................................................................... 43
4.4.3.1 Vane-LV: <M> <3> <3> <1> ......................................................................................................... 43
4.4.3.2 Vane-TDEC ftf: <M> <3> <3> <2>................................................................................................ 43
4.4.3.3 Vane-TDEC mul: <M> <3> <3> <3>............................................................................................. 44
4.4.4 Start / Stop: <M> <3> <4>................................................................................................................. 44

Date : 2004-09-24
ENGINEERING CENTER

4.4.5 Engineering: <M> <3> <5> ............................................................................................................... 44

4.4.5.1 Motor parameter: <M> <3> <5> <1> ............................................................................................ 44
4.4.5.2 Control parameter: <M> <3> <5> <2> .......................................................................................... 45
4.4.6 V/f Parameter: <M> <3> <5> <3> ..................................................................................................... 45
4.4.7 TDECspec: <M> <3> <5> <4> .......................................................................................................... 45
4.5 DECELERATION DISTANCE ............................................................................................................................. 45
4.6 PARAMETER DESCRIPTION ............................................................................................................................ 46
4.6.1 Contract parameter: <M> <3> <1>.................................................................................................... 46
4.6.1.1 Table of motor types ..................................................................................................................... 46
4.6.2 Profile parameter: <M> <3> <2> ....................................................................................................... 47
4.6.3 Vane / LV Parameter: <M> <3> <3> <1>.......................................................................................... 47
4.6.4 Vane / TDECftf Parameter: <M> <3> <3> <2> ................................................................................. 47
4.6.5 Vane-TDECmul parameters: <M> <3> <3> <3> ............................................................................... 48
4.6.6 Start / Stop parameter: <M> <3> <4> ............................................................................................... 48
4.6.7 Engineering parameter: :<M> <3> <5> ............................................................................................. 49
4.6.7.1 Motor parameter:<M> <3> <5> <1> ............................................................................................. 49
4.6.7.2 Control parameter:<M> <3> <5> <2> ........................................................................................... 49
4.6.7.3 V/f parameter: <M> <3> <5> <3> ................................................................................................. 49
4.6.7.4 TDECspec <M> <3> <5> <4>....................................................................................................... 49

Date : 2004-09-24
ENGINEERING CENTER

1 Trouble shooting flow chart

Date : 2004-09-24
ENGINEERING CENTER

1.1 Step 1: elevator status check

Date : 2004-09-24
ENGINEERING CENTER

1.2 Step 2: failure group selection

Date : 2004-09-24
ENGINEERING CENTER

1.3 Step 3: failure handling using service tool
1.3.1 Operational control system (LCB_II)

Date : 2004-09-24
ENGINEERING CENTER

1.3.2 Drive control system (MCB_III)

Date : 2004-09-24
ENGINEERING CENTER

1.3.3 Service tool connection via drive OVF20-CR

Date : 2004-09-24
ENGINEERING CENTER

2 Failure handling using service tool
2.1 Elevator is blocked

2.1.1 Failures related to the CAR AND HOISTWAY DOOR
LCB_II: <M> <1> <2> <1> <GO ON> switch INS “blinking message”
Landing door has been opened for longer than 2 seconds or GS is bridged and the system has a door
bypass. The elevator is taken out of service. àThis event is stored into EEPROM
Possible reason What to do
• Landing door was opened for longer Ø Switch TCI/ERO, PES, MD/AES
than 2 sec.
• GS contact is bridged (door bypass)
LCB_II: <M> <1> <2> <1> <GO ON> SE-Fault “blinking message”
The start enable signal is missing
• The car cannot start due to missing Ø Check the door bypass
SE-signal
LCB_II: <M> <1> <2> <1> <GO ON> OpMode DTC OCSS
The door time protection for closing is exceeded.
• door was not able to close (missing Ø check the related setup DCL (694)
DCL, DFC or DW) within timeout RDCL (695)
DOOR, REAR
DTC-T
LCB_II: <M> <1> <2> <1> <GO ON> OpMode DTO OCSS
The door time protection for opening is exceeded.
• door was not able to open (missing Ø check the related setup DOL (000)
DOL) within timeout RDOL (544)
DOOR, REAR
DTO-T
LCB_II: <M> <1> <2> <1> <GO ON> OpMode DCP OCSS
The delayed car protection (DCP) time is exceeded.
• car was not able to answer a call within Ø check the related setup: DCP-T
timeout (e.g. door was held open
manually)

Date : 2004-09-24
ENGINEERING CENTER

Failures related to the CAR AND HOISTWAY DOOR (continued)
LCB_II: <M> <1> <2> <1> <GO ON> PDS active OCSS
The partition door switch is opened
• PDS is opened Ø check the related setup: PDD (784)
LCB_II: <M> <1> <2> <1> <GO ON> DS Bypass OCSS

Failure related to door switch bypass
• Malfunction of Disable Door Switch ü Check the related setup: DDSRC (970)
Relays (DDSR) for Generic Firemen
Service.
LCB_II: <M> <1> <2> <1> <GO ON> /DFC in FR MCSS

The car door has been opened during Fast Run (safety chain was opened)
• DFC (door fully closed) input signal is Ø check the signal DFC
missing
LCB_II: <M> <1> <2> <1> <GO ON> /DFC in SR MCSS

The car door has been opened during Slow Run (safety chain was opened)
• DFC (door fully closed) input signal is Ø check the signal DFC
missing
LCB_II: <M> <1> <2> <1> <GO ON> /DW in FR MCSS

The landing door has been opened during Fast Run
• DW input signal is missing Ø check the signal DW
LCB_II: <M> <1> <2> <1> <GO ON> /DW in SR MCSS

The landing door has been opened during Slow Run
• DW input signal is missing Ø check the signal DW
LCB_II: <M> <1> <2> <1> <GO ON> DCL in [ ] DCSS

Door close limit is activated.
• (R)DCL was active while the door was ü check the related setup: DCL (694)
fully opened RDCL (695)

Date : 2004-09-24
ENGINEERING CENTER

Failures related to the CAR AND HOISTWAY DOOR (continued)
LCB_II: <M> <1> <2> <1> <GO ON> DCS:DW err DCSS
During normal operation the DW-signal was active though the door was open
• DW signal activated during a normal run Ø Check the DW signal
LCB_II: <M> <1> <2> <1> <GO ON> DOL:alw. on DCSS

The door open limit is detected.
• (R)DOL was active while the door was Ø Check the related setup: DOL (000)
fully closed. This event is also logged RDOL (544)
when the fuses of the door system are
burned.
LCB_II: <M> <1> <2> <1> <GO ON> Hwy-Access DCSS

Elevator is taken out of service.
• Landing door was opened for longer Ø This event is stored into EEPROM so that the ONLY
than 2 seconds. way to bring the elevator into operation again is by using
INS.
LCB_II: <M> <1> <2> <1> <GO ON> Door Stall “blinking message”
Only for FCO 9550 door operator. The door is stalled because the closing or opening time is exceeded
• When the door is not fully opened or Ø Check the door mechanic
fully closed within 4 minutes after
starting the door movement, the door
relays are switched off to protect the
door motor.

Date : 2004-09-24
ENGINEERING CENTER

2.1.2 Failures related to the SAFETY CHAIN

LCB_II: <M> <1> <2> <1> <GO ON> /ES in FR MCSS
The emergency stop signal is detected.
• ES-input was activated during Fast Run Ø Check the switches and contacts leading to ES-input
LCB_II: <M> <1> <2> <1> <GO ON> /ES in SR MCSS

The emergency stop signal is detected during slow run
• ES-input was activated during Slow Run Ø Check the switches and contacts leading to ES-input
LCB_II: <M> <1> <2> <1> <GO ON> DBP: dfc_SE DCSS
Failure related to door bypass
• While the door was opening or fully Ø Check the related setup: EN-RLV,
opened, the door bypass was found to EN-ADO
be inactive (DFC low or SE high)
LCB_II: <M> <1> <2> <1> <GO ON> EEC bypass OCSS
Failure related to emergency exit contact bypass
• Malfunction of Disable Emergency Exit ü Check the related setup: DEMERC (971)
Contact Relay (DEMERC) for Generic
Firemen Service.
LCB_II: <M> <1> <2> <1> <GO ON> LBG/CSP-2 “blinking message”
Light beam gate /car sill protection is active
• Light Beam Gate has been active. ü check the related setup: LBG (967)
MCB_III: <M> <2> <2> <2> <GO ON> M C: EMERGNCY ST

Emergency stop, the safety chain was interrupted before the regular end of a normal run
• safety chain was disconnected Ø check safety chain, SW relay supply (VFOPL
Note: for more detailed information configurations w/o. encoder) or UIB / DIB signals
refer to signals INS / ES / DW / DFC (VFCLL configurations w. encoder)

Date : 2004-09-24
ENGINEERING CENTER

2.1.3 Failures related to the VF DRIVE

MCB_III: <M> <2> <2> <2> <GO ON> SYS: Inv-Relay
Inverter relay dropped (DC-link disconnected from mains supply)
• Power save mode is active Ø information only
• Drive blockage (too much consecutive Ø additional information only. Check other logged events
fatal errors at a time) and refer to the concerning event.
2.1.4 Failures related to the CAR LIGHT

LCB_II: <M> <1> <2> <1> <GO ON> MCLS/SKL-3 “blinking message”
Failure related to car light switch
• Car Light Relay on top of car is Ø Check the car light relay/related setup: CLR (1000)
dropped.

Date : 2004-09-24
ENGINEERING CENTER

2.1.5 Failures related to the BRAKE

LCB_II: <M> <1> <2> <1> <GO ON> RBU-Selftst SYSTEM
Self test of Rope Brake has failed (i.e. lasted longer than 5 seconds). Car is blocked.
• Self test time longer than expected Ø Switch TCI/ERO
Ø Check the related setup: RBTC (1029) ; RBTE (1028)
LCB_II: <M> <1> <2> <1> <GO ON> RBU-Fault “blinking message”/SYSTEM
Rope Brake has detected overspeed. Car is blocked.
• Over speed detection Ø Switch TCI/ERO
Ø Check the parameters: RBTC (1029) RBTE (1028)
MCB_III: <M> <2> <2> <2> <GO ON> M C: Chk BSW Sig
incorrect state of BSW signal.
Note: a "critical check" leads to an immediate drive blockage after first occurrence
• Faulty wiring or brake switches Ø Check parameter BrakeSW type; Check brake switches
and wiring
Sub-code for further information: Press <Down> or <Shift-3>
Parameter "BrakeSwType" = 1:
E= 1 Scenario 1: BSW expected ON detected OFF (critical check; see note)
E= 2 Scenario 2: BSW expected OFF detected ON at start of run (critical check; see note)
Scenario 3: BSW expected OFF detected ON during run
Parameter "BrakeSwType" = 2:
E=1 Scenario 1: BSW expected ON detected OFF before SW is activated (critical check; see note)
E= 2 Scenario 2: BSW expected OFF detected ON after SW is activated
E= 3 Scenario 2 & 3: BSW expected ON detected OFF after BY is activated
Parameter "BrakeSwType" = 3: (not used for this SW BAB version)
E= 11 Scenario 1: BS1 expected ON detected OFF (critical check; see note)
E = 12 Scenario 1: BS2 expected ON detected OFF (critical check; see note)
E= 13 Scenario 1: both BS1 and BS2 expected ON detected OFF (critical check; see note)
E= 21 Scenario 2 & 3: BS1 expected OFF detected ON
E= 22 Scenario 2 & 3: BS2 expected OFF detected ON
E= 23 Scenario 2 & 3: both BS1 and BS2 expected OFF detected ON
Note: a "critical check" leads to an immediate drive blockage after first occurrence.

Date : 2004-09-24
ENGINEERING CENTER

2.2 Elevator malfunction: car is running with failure

2.2.1 Failures related to the COMMUNICATION
MCB_III: <M> <2> <2> <2> <GO ON> M C: Command Lst
Invalid motion command received from LCB_II
• for discrete coded interface: possible Ø check wiring/connections; check HL2
faulty wiring of V1-V4, DS1-DS3 or HL2. (e.g. connection to HL1)
Note: use two SVT's to compare these
signal groups on MCB vs. LCB_II.
• defective MCB Ø change MCB
• defective LCB_II Ø change LCB_II
E= 1 Motion command lost during normal run (FR,SD)
E= 2 Motion command lost during reduced run (RR,SD)
E= 3 Motion command lost during emergeny creep run (ER)
E= 4 Motion command lost during relevel run (RL,ST)
E= 5 Motion command lost during inspection run (IN,WT)
E= 6 rescue run or emergency run requested but car is in door zone
E= 7 Stop-Wait-check: Stop (ST) expected
E= 8 Stop-Wait-check: Wait (WT) expected
E= 9 Motion command lost during rescue run (RS)
2.2.2 Failures related to the HOISTWAY SIGNALS

LCB_II: <M> <1> <2> <1> <GO ON> OP lost MCSS
OVF10 announced a drive problem by switching off the OP signal.
• OVF10 OP signal is lost Ø Check the event logging on OVF10
LCB_II: <M> <1> <2> <1> <GO ON> OP/T fault MCSS
The interface check between LCBII and OVF10 (OP and T signals) has failed.
• Disturbances coming from the discrete Ø Check the event logging on OVF10
interface (LCB_II and OVF10 Ø Check the wiring of the interface signals

Date : 2004-09-24
ENGINEERING CENTER

Failures related to the HOISTWAY SIGNALS (continued)
LCB_II: <M> <1> <2> <1> <GO ON> LS-Fault “blinking message”
Wrong information coming from 1LS or 2LS signal
• In a door zone where 1LS or 2LS is Ø Check the wiring
required, the corresponding signal is not Ø Check the sensors
detected.
• 1LS or 2LS is detected in a door zone
where the corresponding signal is not
allowed.
Note: In case of a short landing in bottom or top two door zones are present in 1LS/2LS - zone!
LCB_II: <M> <1> <2> <1> <GO ON> /DZ in NST MCSS
DZ-signal was lost or not detected at all after having stopped
• The inputs signals 1LV, 2LV are missing Ø Check the input signals
• Check the setup Ø Check the related setup: LV-MOD, DZ-TYP
LCB_II: <M> <1> <2> <1> <GO ON> DZ missed MCSS

UIS & DIS have been detected without DZ.
• Defective LV relays Ø Check the LV relay
• Wrong setup Ø Check the related setup: EN-RLV, DRIVE
LCB_II: <M> <1> <2> <1> <GO ON> DBP-Fault “blinking message”
Two correction runs have been performed in sequence. This can occur if no door zone is detected after
having stopped.
• The reason for that can be a defective Ø To bring the elevator into operation again use INS.
LVC-relais.This event is stored into
EEPROM
LCB_II: <M> <1> <2> <1> <GO ON> 1LS+2LS on “blinking message”
The normal terminal slowdown limit switches for top (2LS) and bottom (1LS) floor are on.
• Limit switches 1LS and 2LS are active Ø Check power supply of the position reference system.
at the same time.

Date : 2004-09-24
ENGINEERING CENTER

LCB_II: <M> <1> <2> <1> <GO ON> Pos. Count. MCSS
An unmatching number of DZ-signals has been counted during a run. This check is made after completion
of the run.
• The DZ signals might be too short to be Ø Check the parameters: LV-MOD, DZ-TYP
detected Ø Check the DZ signals
LCB_II: <M> <1> <2> <1> <GO ON> DDP in FR MCSS

Duration of the Fast Run is too long. The delayed drive protection time is exceeded
• No stop signals (DZ) have been Ø Check the hoistway signals
detected during Fast Run
LCB_II: <M> <1> <2> <1> <GO ON> DDP in SR MCSS

Duration of the Slow Run is too long. The delayed drive protection time is exceeded
LCB_II: <M> <1> <2> <1> <GO ON> DDP in RS MCSS

Duration of the Rescue Run is too long. The delayed drive protection time is exceeded
LCB_II: <M> <1> <2> <1> <GO ON> SpeedCheck “blinking message”
The SC signal from OVF20 was always high during a normal run. ADO and RLV are disabled until the
controller is switched off.
• The SC signal is not reliable. Ø Check the speed check signal
MCB_III: <M> <2> <2> <2> <GO ON> SYS: 1LS + 2LS
1LS and 2LS are active at the same time
• faulty wiring Ø check wiring
• defective sensor(s) Ø check sensor(s) and replace if necessary
• voltage supply of LS sensors is missing Ø check voltage supply

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> MLS: Stop in LS

Limit switch 1LS / 2LS versus run direction mismatch.
• Limit switch 1LS / 2LS versus run Ø check LS wiring
direction mismatch.
MCB_III: <M> <2> <2> <2> <GO ON> MLS: No 2nd LV

One of the LV signals was activated but the second was not activated in the following 1.2 seconds.
Problems can concern both LV inputs.
• defective sensor(s) Ø check sensor(s)
• wrong alignment of LV magnet Ø check position & alignment of LV magnet
MCB_III: <M> <2> <2> <2> <GO ON> MLS: LV Sequence

The wrong LV sequence was detected, i.e. 2LV occurred before 1LV in UP direction or 1LV occurred
before 2LV in DOWN direction.
• LV signals are noisy Ø check LV input signals
• PRS does not fulfill requirements. Ø use correct PRS.
Note: PRS2 system recommened.
MCB_III: <M> <2> <2> <2> <GO ON> MLS: LV Missed

The creep time was longer than (0.64 * DDP time) sec. w/o. any valid LV signals detected.
• missing LV magnet or defective sensors Ø check magnets and sensors
• TDEC times were adjusted wrong at Ø Adjust stop time parameters (TDEC times) according
calibration startup routine
• secondary effect of Emergency Stop, Ø check other occurred errors
Shut Downs, Correction runs; floor
count mismatch
• only one LV signal was detected at units Ø if applicable (e.g. LCB_II): check LV1, LV2 relays and
with both 1LV and 2LV specified LVCT -time by a slow INS RUN. Check that creep speed
is not too low.

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> MLS: LV lost

LV signals detected but lost again during Creep or Halt phase.
• Secondary effect of Emergency Stop, Ø check other occurred errors
Shut Downs, Correction runs;
floor count mismatch
• Secondary effect of event 52: Ø see description there
"MLS: <Dec Dist"
• LV DLY too large Ø check and decrease LV DLY (M-3-3-goon)
• other possible reasons see event 60: Ø see description there
"MLS: LV Missed"
MCB_III: <M> <2> <2> <2> <GO ON> MLS:LV Count Err
When reaching 1LS or 2LS: Actual floor count does not match expected floor (LV) count.
• miscounting of door zones at e.g. INS Ø ignore
operation or manual car movement
during power-OFF
• parameter TOP FLOOR or BOTTOM Ø check these parameters
FLOOR is not correct
• other possible reasons see event 60: Ø see description there
"MLS: LV Missed"
MCB_III: <M> <2> <2> <2> <GO ON> MLS: LV Trig Err
LV signal chattering longer then 20 ms (i.e. signal(s) are not stable).
Note: a deviation of stopping accuracy is possible (bad creep speed measurement).
• LV signals are noisy Ø check wiring (HL2), and (24V-) power supply.
• wrong distance or alignment of LV Ø check distance and alignment
sensors & magnets
• defective LV sensors; bad contacts etc. Ø check sensors, contacts etc.
• PRS does not fulfill requirements Ø use correct PRS
Note: PRS2 system recommended
LV edge (rising or falling) is not followed by a debounced signal state (i.e. spikes on LV
E= 0
signals)
E= 1 Debounced LV=OFF state w/o. previous falling LV edge
E= 2 Debounced LV=ON state w/o. previous rising LV edge

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> MLS: LV failures

Too many LV failures. Indicated only when drive is blocked for this reason.
• generic LV error message only. Ø See error logging for event which caused the blockage.
2.2.3 Failures related to REMOTE SERIAL LINK

LCB_II: <M> <1> <2> <1> <GO ON> RSL sync SSS
Synchronization lost on remote serial link
• Line terminator is defective Ø Change the line terminator
LCB_II: <M> <1> <2> <1> <GO ON> RSL parity SSS
Two remote stations with the same address are connected to the same link
• Wrong connection Ø Check the RS connections
LCB_II: <M> <1> <2> <1> <GO ON> Adr-Check “blinking message”/MCSS
Check the programmed RSL address
• Some RSL I/Os have to be programmed Ø Set I/O 691 to a valid address
to a valid address and are not allowed related setup: TCI(691)
to be set to 00-0 or 01-0. Currently only
one I/O is checked: 691 – TCI
2.2.4 Failures related to VF DRIVE

LCB_II: <M> <1> <2> <1> <GO ON> LSVF-W:/DR MCSS
LSVF-W reported an error (Drive Not Ready)
• Drive not ready on MCBIIIx is missing Ø Check the error logging on MCBIIIx
• wrong setup Ø Check the related setup: DRIVE C-TYPE
LCB_II: <M> <1> <2> <1> <GO ON> OpMode NAV OCSS
OCSS is not available due to drive fault This mode is also active after INS before the COR starts
• Operational mode not available due to Ø Check the error logging:
drive fault 8LS-fault (8L), brake-fault (BR), drive-fault (NR).

Date : 2004-09-24
ENGINEERING CENTER

Failures related to VF DRIVE (continued)
LCB_II: <M> <1> <2> <1> <GO ON> LSVF-W:/SC MCSS

During deceleration the speed of the car was too high to perform ADO or Releveling. Therefore ADO and
RLV are not allowed any more
• Speed is too high Ø Check the profile setup:
LCB_II: <M> <1> <2> <1> <GO ON> LSVF-W:P-ON MCSS

This is the minimum time for which the drive will be powered down. The package will not be switched on
again until this time has expired
• The drive has been powered on Ø Wait until the time has expired (parameter P-ON-D)
LCB_II: <M> <1> <2> <1> <GO ON> DBSS-Fault “blinking message”
Due to a fault the elevator had been shut down in a landing. The reason can be:
• Drive OVF10, OVF20 reported an error Ø Check the errors of the drive
• One of the following faults occurred Ø Check the status of the corresponding component
during DCS: OTS, PLS, MCLS, SKL,
MPD, J, LS-Fault, OVF10-Fault
LCB_II: <M> <1> <2> <1> <GO ON> P_OFF activ “blinking message”
LSVF-W has been switched off to save energy. The drive package can only be switched on again after a
delay of at least 8 seconds.
• Drive is switched off to save energy Ø Wait until the time has expired
Ø Check the parameter setup: P-OFF-D ; P-ON-D
MCB_III: <M> <2> <2> <2> <GO ON> SYS: Shut Down
Shut down of the inverter after occurrence of an error
Ø Message allows a quick overview about the shutdown
• The error causing the shut down can be
reason. For further information refer to the concerned
displayed using <SHIFT> <DOWN>
event.
MCB_III: <M> <2> <2> <2> <GO ON> SYS: DDP

Drive has entered the DDP mode
• The time between two positive edges of Ø Check car movement and LV signals
LV-magnets was longer than the DDP Ø The DDP error is often caused by other events.
time adjusted by SVT

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> SYS: WARMSTART

Software reset without power reset
• defective EPROM Ø start self test , if negative, then change EPROM
• MCB hardware problem Ø change MCB
• bad internal voltage supply Ø
change package
E= 1 Class B trap: Illegal external bus access
E= 2 Class B trap: Illegal instruction access
E= 3 Class B trap: Illegal word operand access
E= 4 Class B trap: Protection Fault
E= 5 Class B trap: Undefined Opcode
E= 6 Class A trap: Stack underflow
E= 7 Class A trap: Stack overflow
E= 9 Reset caused by watchdog hardware
MCB_III: <M> <2> <2> <2> <GO ON> SYS: ParaConflkt

The parameter “ConNmot” is inconsistent with other parameters.
• The maximum INS SPE is at Ø Check the parameters
synchronous speed of the motor, CON SPE, ConNmot, Motor Type, MotFnom,
• the maximum NOM SPE is >= 110 % of MotNom, INS SPE, NOM SPE.
the synchronous speed of the motor.
MCB_III: <M> <2> <2> <2> <GO ON> SYS: <15V Supply
15V power supply is missing on MCB
• external short circuit in 15VDC power Ø check voltage supply and wiring
supply
• defective board with 15VDC power Ø change respective board or complete drive
supply

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> SYS: Int FormErr
Internal MCB error occurred (value format error)
secondary effect if power code is invalid refer to other logged events
E= 24 Invalid or unknown inverter power code
E= 25 Package test error: invalid or unknown package test mode
E= 26 Inverter power code w/o. stored E2P parameter capability (normally covered by e = 24).
Note: "Internal" errors can be solved by ENG only.
MCB_III: <M> <2> <2> <2> <GO ON> INV: ADC Offset
Measured zero offset for one A/D converter is too large.
defective package change package (if occurs permanently)
O= 4 A/D channel: Idc (DC-link current) channel: measured offset too large
O= 5 A/D channel: Ibr (brake coil current) channel: measured offset too large
Note: O = 0, 1, 2 are reserved for motor phase current Iu,Iv,Iw
MCB_III: <M> <2> <2> <2> <GO ON> INV: ADC calibr
Bad calibration (trimming) values stored in power board EEPROM.
Note: in this case the Udcl & Temperature measurement uses fixed ROM values.
defective or no calibrated power boards change package
E= 0 manufacturing test not passed or any E2P problem (no or defect E2P)
E= 1 parameters which were determined during the manufacturing test are not in range
E= 2 K_temp not in range, use limit values for k_temp
E= 3 K_udcl not in range, use limit value for k_udcl

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> INV: PowerCode ?

Bad power code stored in power board (DCB_II or PBX).
Note: power-code is factory-preconfigured and stored in EEPROM
• faulty wiring to power boards (50-poles
Ø check wiring
flat cable)
• defective parts (e.g. EEPROM) on
Ø change power board (DCB_II or PBX)
power board
MCB_III: <M> <2> <2> <2> <GO ON> INV: >Volt DC

DC link voltage too high
• wrong or defective brake resistor (DBR) Ø Check and/or measure DBR; change if necessary.
• faulty wiring to the DBR Ø check wiring
• defective inverter Ø change inverter
MCB_III: <M> <2> <2> <2> <GO ON> INV: >Heat Packg
IGBT module temperature exceeded. Warning but allow finishing of current run for >= 90°C, immediate
shutdown for >= 100°C.
• defective fan Ø test fan (M-2-7) and wiring, change if necessary
• dusty / clogged air filters (if applicable) Ø clean / exchange air filters if necessary
• defective temperature sensor Ø change inverter
MCB_III: <M> <2> <2> <2> <GO ON> INV: IGBT Pfail
Power supply failure of IGBT gate drivers
• defective power boards / inverter Ø check power boards / inverter
MCB_III: <M> <2> <2> <2> <GO ON> INV: Temp meas.
Temperature measurement in IGBT module does not work correctly.
• defective temperature sensor or circuit Ø check power boards / inverter
Note: danger of undetected overheating !
t=0 IGBT module temperature
Note: Further numbers are reserved for other temperature channels.

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> INV: brake chopp
DBR nominal / actual current mismatch:unexpected current when DBT is OFF / no current when DBT is
ON
• DBR defective or not properly Ø check DBR & connection
connected
• defective DBT (brake IGBT) Ø change inverter
MCB_III: <M> <2> <2> <2> <GO ON> INV: PFAIL sig.
Signal "PFAIL" is active.
Note: Signal is not yet used but disables PWM drivers if active.
• defective 50-pole flat cable on MCB Ø check cable
• defective MCB Ø check MCB
MCB_III: <M> <2> <2> <2> <GO ON> INV: <Volt DC

DC-link voltage is too low
• Loss of line voltage; one phase missing Ø check line voltage supply & wiring
• line voltage is too low Ø check line voltage, check CHF (impedance).
if this occurs frequently: verification of line voltages with
recorder is necessary
• defective recifier Ø change inverter
MCB_III: <M> <2> <2> <2> <GO ON> INV: >Curr IGBT
IGBT over current detected.
Note: done by peak detection in DC-link current measurement.
• motor current too high (in conjunction
Ø refer to description of "DRV: Overload"
with "DRV: Overload")
• short circuit in motor / motor cable or
Ø check motor / motor cable / connectors
earth leakage
• defective power board (DCB_II or PBX) Ø change power board
• defective inverter (error occurs
Ø change inverter
permanently)

Date : 2004-09-24
ENGINEERING CENTER

MCB_III: <M> <2> <2> <2> <GO ON> INV: >Heat DBR
DBR overheat detected.
Note: Temperature switch has opened; status / Input displays "tdbr"
• defective temperature switch / wiring Ø check temperature switch / wiring / connector P6 on
PDB_II or DCB_II
• DBR is too hot because of bad air Ø ensure proper air circulation (check vent holes)
circulation
• DBR is overloaded because of too much Ø ensure that overload situations do not occur or ensure
generatoric runs of elevator better DBR ventilation
MCB_III: <M> <2> <2> <2> <GO ON> DRV: > Reduction
Reduction of frequency demand in case of overload (high motor current) exceeds permissible maximum
• wrong motor type Ø check motor type
• power if inverter is too low Ø check power of inverter and motor
• acceleration rate is too high Ø reduce acceleration
MCB_III: <M> <2> <2> <2> <GO ON> DRV: JerkIn OvL
HW overload signal is active during jerkin of acceleration
• acceleration rate is too high Ø decrease acceleration rate
• power of inverter is too low Ø check power of inverter and motor

Date : 2004-09-24
ENGINEERING CENTER

2.2.5 Failures related to PERFORMANCES

MCB_III: <M> <2> <2> <2> <GO ON> SYS: not all err
Not all events have been stored during last power-OFF
• Too much errors have been logged Ø Notify all (remaining) saved error events and clear error
before power has been switched off. logging.
Some events and/or maintenance
information may be lost.
MCB_III: <M> <2> <2> <2> <GO ON> MLS: invld. CrSp
Invalid creeping speed. The measured creeping speed is out of range (+ 40 mm/s).
• LV signals are noisy Ø check wiring (e.g. HL2)
• wrong frequency compensation Ø check motor type; perform new calibration.
MCB_III: <M> <2> <2> <2> <GO ON> MLS: Tdec expird
deceleration command comes after Tdec time has run out
• deceleration command comes after Ø information only
Tdec time has run out
MCB_III: <M> <2> <2> <2> <GO ON> MLS: <Creep Time
The creep time was shorter than 0.5 seconds. If the creeping time was very short (10-30ms) there may
also be “MLS: LV Trig Err” error.
• very short creeping time Ø check Motor type.
Note: New Calibration necessary after change!
Ø new adjustment of the TDEC times according startup
routine (calibration)
MCB_III: <M> <2> <2> <2> <GO ON> DRV: Overld>Time

HW overload signal is active for longer than a pre-defined time (0.5 sec.)
• V/F parameters are not adjusted Ø check adjustment of V/F parameters (Vstart, Vacc,
correctly depend on Motortype); see also startup routine
• flywheel inertia is too big Ø reduce flywheel inertia
• gear efficiency is too low Ø check gear unit

Date : 2004-09-24
ENGINEERING CENTER

Failures related to PERFORMANCES (continued)
MCB_III: <M> <2> <2> <2> <GO ON> DRV: Overload

HW overload signal from DC-link current measurement. is active.
Note: The drive will decrease the profile and allow for safe completion of the run.
• flywheel inertia is too big Ø reduce flywheel inertia
• gear efficiency is too low Ø check gear unit
MCB_III: <M> <2> <2> <2> <GO ON> DRV: Volt Boost
When the creep phase is too large, the voltage boost is activated in order to prevent a standstill.
• wrong TDEC times; wrong V/f Ø Adjustment of TDEC times according startup routine
parameters with increased Vend (repeat the calibration)
MCB_III: <M> <2> <2> <2> <GO ON> MLS: LS Ini Dec
Deceleration in the top or bottom landing initiated by 2LS or 1LS
• Deceleration in the top or bottom Ø ignore
landing initiated by 2LS or 1LS. Ø Increase parameter "1LS DLY' / "2LS DLY" (M-3-3-
goon). Check that deceleration distance for a correction
run is still sufficient.
Note: A correction run can be forced by an INS run
outside a door zone.
Ø check "FDIST" parameter(s).
L= 1 1LS initiates deceleration
L= 2 2LS initiates deceleration
MCB_III: <M> <2> <2> <2> <GO ON> MLS: <Acc Dist
Deceleration was initiated before acceleration has finished (i.e. no CONST phase or CONST phase too
short)
• Deceleration was initiated before Ø check parameter(s) FDIST
acceleration has finished Ø check Motor type.
Ø check other occurred errors
t=0 no CONST phase at all (DEC follows ACC phase)
t>0 CONST phase reached but is too short for a correct Idc measurement (VFOPL only)

Date : 2004-09-24
ENGINEERING CENTER

Failures related to PERFORMANCES (continued)
MCB_III: <M> <2> <2> <2> <GO ON> MLS: <Dec Dist
Final ramp down was initiated before deceleration has finished (i.e. no CREEP phase)
• Final ramp down was initiated before Ø check other occurred errors
deceleration has finished Ø check Motor type (perhaps Motor type 5).
Ø check parameter(s) FDIST
Ø check floor distance; start learn run again
Ø increase parameter ”T_creep” (M-3-3-GOON)
2.2.6 Failures related to CONTACTORS AND WIRING

LCB_II: <M> <1> <2> <1> <GO ON> J-Relay MCSS
The LCBII detected a fault at the 3-line-power-supply (i.e. phases missing or turned)
Note: This event is always logged when ‘EN-EVT’=1 and the power is switched off. The reason is that
the 3-line-power supply breaks down earlier than the LCBII power supply.EN-J, J-T
• Fault in the 3-lines power supply Ø Check the phases of the power supply
MCB_III: <M> <2> <2> <2> <GO ON> SYS: Power Fail
The line voltage has dropped for a short time (e.g. one phase lost).
• voltage loss (line) Ø check line connections L1 to L3
Ø if this occurs frequently: verification of line voltages with
• short voltage drop or voltage variation
recorder is necessary
MCB_III: <M> <2> <2> <2> <GO ON> M C: U/D lost

Up or down signal lost during a run
• faulty wiring between LCB_II and MCB Ø check wiring and connections
(U or D) (only VFOPL configurations;
w/o encoder)
MCB_III: <M> <2> <2> <2> <GO ON> M C: MC+SafetyCh

Motion Command from LCB_II does not fit to UIB, DIB state
• faulty wiring Ø check V1 - V4 and UIB, DIB wiring
• defective MCB input Ø change MCB
• change of input signal was too fast in Ø ignore
INS mode

Date : 2004-09-24
ENGINEERING CENTER

Failures related to CONTACTORS AND WIRING (continued)
MCB_III: <M> <2> <2> <2> <GO ON> M C: UD not drop

After the end of a run (rising edge of DZ) U or D signals are still active
• U or D relay do not drop Ø check wiring or relay
• OP signal is not recognized by OCSS Ø check Drive type (at LCB_II), otherwise check OP wiring
MCB_III: <M> <2> <2> <2> <GO ON> M C: Chk SW Sig

incorrect state of SW signal, SW-signal indicates switching state of main contacts
• loose or missing connection from MCB Ø check cables and connections
P11 to power boards
• faulty wiring for external SW feed-in Ø check respective wiring
MCB_III: <M> <2> <2> <2> <GO ON> M C: Chk DBD Sig
Incorrect state of DBD signal (active = Stop , inactive = Run)
• DBD test plug on power board Ø connect DBD test plug correctly
disconnected
• bad contact of the NC-switches in DBD Ø check contact; replace switch if necessary
chain (e.g. "SW"; see wiring diagram
MCB P3.1)
• faulty wiring on external DBD plug (MCB Ø check wiring
P3.1)
• defective power board containing SW Ø change power board (DCB_II or PDB_II)
relays
2.2.7 Failures related to emergency power operation (EPO)

LCB_II: <M> <1> <2> <1> <GO ON> EPO shutd. OCSS
Car is shut down due to emergency power operation (EPO). The car is not able to run during EPO; the
next car is allowed to recover
• car is not able to run during EPO; the Ø check the related setup: NU (017)
next car is allowed to recover NUSD (018)
NUSG (019)

Date : 2004-09-24
ENGINEERING CENTER

2.2.8 Failures related to the BRAKE

MCB_III: <M> <2> <2> <2> <GO ON> M C: Chk I_brake
Measured current in brake coil does not match expected state.
• Measured current in brake coil does not Ø check wiring and connections within brake coil current.
match expected state Ø Replace package if no other reason found.
E= 1 Brake is actuated, but measured current does not reach threshold value.
E= 2 Brake is not actuated, but measured current does not fall below threshold value.
2.2.9 For information only

LCB_II: <M> <1> <2> <1> <GO ON>
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 ring messages couldn’t be sent in an appropriate time
LCB_II: <M> <1> <2> <1> <GO ON> OPSYS
Task Timing software entered endless loop

W_Dog Reset watchdog circuit on LCBII was triggered
Illegal Int illegal interrupt was executed
MCB_III: <M> <2> <2> <2> <GO ON> SYS: PckgTst Err
Information for factory testing only
• Failure message during factory test Ø Information for factory
LCB_II: <M> <1> <2> <1> <GO ON> correct.run MCSS

A correction run was performed (e.g. after INS, NAV)
• A correction run was performed Ø For information only

Date : 2004-09-24
ENGINEERING CENTER

2.3 Elevator failures during installation or maintenance

2.3.1 Failures related to CALIBRATION
MCB_III: <M> <2> <2> <2> <GO ON> DRV: Cal invers
Info message that calibration has been done with 'inversed' load condition (full load in car).
• calibration has been done with Ø information only
'inversed' load condition
MCB_III: <M> <2> <2> <2> <GO ON> DRV: Failed Cal
Calibration routine has not been performed or or was made invalid by change of parameters (Control
parameters, V/F parameters, profile parameters, Motor type, Mot Fnom, Con Spe)
• warning that current calibration data are Ø perform new calibration
invalid
MCB_III: <M> <2> <2> <2> <GO ON> DRV: No Cal Init
Calibration routine has not been performed or or was made invalid by change of parameters (Control
parameters, V/F parameters, profile parameters, Motor type, Mot Fnom, Con Spe)
• warning that current calibration data are Ø perform new calibration
invalid
MCB_III: <M> <2> <2> <2> <GO ON> DRV: Cal TDEC<0
The calculated TDEC times were too small.
• wrong floor distances Ø check floor distances
MCB_III: <M> <2> <2> <2> <GO ON> DRV: out of Cal
Limit of load compensation reached, refer to start up routine
• wrong system balance Ø check the balance and repeat the calibration with empty
car

Date : 2004-09-24
ENGINEERING CENTER

2.3.2 Failures related to MANUAL RUN

LCB_II: <M> <1> <2> <1> <GO ON> TCI-lock “blinking message”
TCI sequence not correctly followed
• The sequence to leave TCI-mode was Ø Correct steps are: 1. open door
not correctly followed 2. switch TCI off
3. close door
LCB_II: <M> <1> <2> <1> <GO ON> TCI/ERO on MCSS

TCI or ERO has been switched on
• TCI/ERO is switched on For information only
2.3.3 Failures related to NORMAL RUN

LCB_II: <M> <1> <2> <1> <GO ON> start DCS! “blinking message”
The door check sequence is to be performed.
• Normal operation is not allowed until Ø Enter M-1-3-5 to start the DCS!
DCS hasn't been completed
successfully.
• The DCS is required again if one of the
parameters TOP or BOTTOM is
changed.
• During normal operation the DW-signal Ø Check the wiring of the hoistway doors
was active while the door was fully
opened in a door zone.
2.3.4 Failures related to PARAMETER SETUP

MCB_III: <M> <2> <2> <2> <GO ON> SYS: E2P failure
EEPROM writing or reading problems
no EEPROM on the MCB plug in EEPROM correctly
defective EEPROM change EEPROM after verification by self test (M-2-3)
defective MCB change MCB
E= 1 timeout: write during write (of other task)
E= 2 EEPROM write failure (defective or missing device)
E= 3 illegal EEPROM address ("general protection fault")
E= 4 "I2C bus" or device failure (e.g. defective EEPROM device)
Note: subcodes 1 and 3 are software problems and can be solved by ENG only

Date : 2004-09-24
ENGINEERING CENTER

Failures related to PARAMETER SETUP (Continued)
LCB_II: <M> <1> <2> <1> <GO ON> Ill. Setup “blinking message”
Illegal Setup, An invalid configuration has been programmed. The following situations are not accepted by
the software:4-car-group with more than 11 openings per car
• 4-car-group with more than 11 openings Check the parameter setting: TOP>11 GROUP=4
per car has been programmed
MCB_III: <M> <2> <2> <2> <GO ON> SYS: ParaChanged

Parameter(s) have been (manually) changed after power-on
• Parameter(s) have been (manually) Ø Information only
changed after power-on
MCB_III: <M> <2> <2> <2> <GO ON> SYS: ParaDefault

All parameters have been (manually) set to their default values.
• The unit is not able to run correctly with Ø If a backup parameter set has been stored by SVT (M-3-
default values 7) this set can be reloaded (M-3-8).
Otherwise the drive has to be completely readjusted.
MCB_III: <M> <2> <2> <2> <GO ON> SYS: E2P InvPara
One or more parameters stored in the EEPROM are outside the range of their minimal or maximal values.
• if error occurs after software change or Ø Note all parameters, perform DEFAULT setting and
after adjustment: readjust the drive again.
• EEPROM selftest (M-2-3) failed Ø Change EEPROM
p number of (1st) parameter which is out of range

Date : 2004-09-24
ENGINEERING CENTER

2.3.5 Parameter setup: general error handling

When setting a parameter < M > < 3 > ... the following error messages are possible:
D out of fixed default range

S out of variable range (caused by ” Speed ” - relations; for speed encoder)
C out of variable range (caused by ” Control ” - relations; for control algorithms)
R out of variable range (caused by ” Run Car ” - relations; for signal operations)
L out of variable range (caused by Load-compensation relations; for calibration algorithms)
D out of fixed default range

S out of variable range (caused by ” Speed ” - relations; for speed encoder)
C out of variable range (caused by ” Control ” - relations; for control algorithms)
R out of variable range (caused by ” Run Car ” - relations; for signal operations)
L out of variable range (caused by Load-compensation relations; for calibration algorithms)
Possible reasons for both "Below Min" and "Above Max" errors:
R attempt to set "TOP FLOOR" <= "BOTTOM FLOOR" or vice versa.

R attempt to set "INS SPE" < "CRE SPE" or vice versa.
R attempt to set "INS SPE" > synchronous speed
R attempt to set a speed parameter above 110% of calculated synchronous speed.
R attempt to set a r.p.m. parameter above 110% of calculated synchronous r.p.m.
R2 Floor-to-floor run: calculated start of IP-pulse must be before acceleration jerk-out.

Check all floor-, LV- and profile related parameters.
R3 Multi-floor run: start of IP-pulse must be before deceleration point.
Check all floor-, LV- and profile related parameters.

Date : 2004-09-24
ENGINEERING CENTER

Parameter setup: general error handling (continued)
internal error: "BOTTOM FLOOR" >= "TOP FLOOR" but parameters are not manually changed.
1
Can be solved by ENG only.
2 internal error: shared 1LS&2LS is only allowed for VFOPL. Can be solved by ENG only.
internal calculated pretorque freq too high. Check "PRET FREQ", "PRET SLOPE",
C1
"ACC PRECTR", "CON SPE", "NOM SPE", "INS SPE"
C2 "Vend" must be >= "Vstart". Check these parameters.
Floor-to-floor run: calculated constant speed is less than creep speed. Check all floor-, LV- and
R1
profile related parameters.
R3 Calculated creep time too low. Check all floor-, LV- and profile related parameters.
L1 "Ic U" and "Ic D" have same value. Check these parameters; perform calibration routine.

Date : 2004-09-24
ENGINEERING CENTER

3 EN81 code inspection procedure
Name Terminal Switched safety chain

24V P4:3 +24V supply (referenced to HL2)
DBD_PCB P4:4 DBD chain (series connection of safety relays NC contacts)

Date : 2004-09-24
ENGINEERING CENTER

4 Appendix
4.1 5 kW Package

Date : 2004-09-24
ENGINEERING CENTER

4.2 configuration

Date : 2004-09-24
ENGINEERING CENTER

4.3 Drive interface

4.3.1 Interface to controller with LCB II
P7.1 24 VDC Output Supply for external features (max. 1A)
P7.2 HL2 Ground connection for 24 VDC
P7.3 U Input Up command
Connector P7
P7.4 D Input Down command

P7.5 T Input Normal run (fast run) command
P7.6 LS Input Limit switch
P7.7 1LV Input Door zone signal
P7.8 2LV Input Door zone signal
P7.9 OP Output Operating signal (no error)
P7.10 DZ Output Drive in door zone
P7.11 IP Output Counting impulse signal
P7.12 BY Output Brake lift signal
P10.1 SW1-14 NO contact dry contact with terminal 2

P10.2 SW1-13 NO contact dry contact with terminal 1
Connector P10
P10.3 SW1-A1 Coil input from safety chain

P10.4 SW1-A2 Coil ground connection
P10.5 SW1-21 NC contact dry contact with terminal 6
P10.9 110 VAC 110VAC supply
P10.10 HL1 Ground of 110VAC
L1
Maine
lines
L2 Power supply AC line input

L3
PE Protection earth
4.3.2 Interface to the motor

P2:4 U
P2:3 V Motor phase output
terminal
P2:2 W
Motor
P2:1 BR DBR in (connecting point for DBR)

P2:5 P0 DBR out (connecting point for DBR)
P2:6 DC+ Positive DC-Link voltage
P2:7 DC- Negative DC-Link voltage

Date : 2004-09-24
ENGINEERING CENTER

4.4 Parameter setup

4.4.1 Contract parameter: <M> <3> <1>
Parameter min. Default max. actual
CON SPE [0.01 m/s] 10 100 135
MOTOR TYPE 0 0 6
MOT FNOM [0,1 Hz] 250 500 600
DDP [s] 1 15 45
RELAY CONTROLLER 0 0 0
LV DISTANCE [mm] 25 30 45
LV MAGNET [mm] 130 150 300
TOP FLOOR 1 1 31
BOTTOM FLOOR 0 0 0
FDIST 00-01 [cm] 220 240 700 *)
FDIST 01-02 [cm] 220 240 700 *)
FDIST 02-03 [cm] 220 240 700 *)
FDIST 03-04 [cm] 220 240 700 *)
FDIST 04-05 [cm] 220 240 700 *)
FDIST 05-06 [cm] 220 240 700 *)
FDIST 06-07 [cm] 220 240 700 *)
FDIST 07-08 [cm] 220 240 700 *)
Motor Dir [0/1] 0 0 1
*) visible depending on parameters TOP FLOOR / BOTTOM FLOOR (example: 8 / 0)
4.4.2 Speed Profile: <M> <3> <2>

INS SPE [0.01 m/s] 5 20 60
NOM SPE [0.01 m/s] 10 100 120
CRE SPE [0.01 m/s] 5 10 30
[0.01 m/s ]
2
ACC 5 50 80
[0.01 m/s ]
2
DEC 5 50 100

Date : 2004-09-24
ENGINEERING CENTER

4.4.3 Vane parameters: <M> <3> <3>
4.4.3.1 Vane-LV: <M> <3> <3> <1>

LV DLY 00 D [mm] 0 60 200 *)
LV DLY 01 U [mm] 0 60 200 *)
LV DLY 01 D [mm] 0 60 200 *)
LV DLY 02 U [mm] 0 60 200 *)
LV DLY 02 D [mm] 0 60 200 *)
LV DLY 03 U [mm] 0 60 200 *)
LV DLY 03 D [mm] 0 60 200 *)
LV DLY 04 U [mm] 0 60 200 *)
LV DLY 04 D [mm] 0 60 200 *)
LV DLY 05 U [mm] 0 60 200 *)
LV DLY 05 D [mm] 0 60 200 *)
LV DLY 06 U [mm] 0 60 200 *)
LV DLY 06 D [mm] 0 60 200 *)
LV DLY 07 U [mm] 0 60 200 *)
LV DLY 07 D [mm] 0 60 200 *)
LV DLY 08 U [mm] 0 60 200 *)
4.4.3.2 Vane-TDEC ftf: <M> <3> <3> <2>

TDEC ftf 01 U 0 0 1000 *)
TDEC ftf 02 U 0 0 1000 *)
TDEC ftf 03 U 0 0 1000 *)
TDEC ftf 04 U 0 0 1000 *)
TDEC ftf 05 U 0 0 1000 *)
TDEC ftf 06 U 0 0 1000 *)
TDEC ftf 07 U 0 0 1000 *)
TDEC ftf 08 U 0 0 1000 *)
TDEC ftf 07 D 0 0 1000 *)
TDEC ftf 06 D 0 0 1000 *)
TDEC ftf 05 D 0 0 1000 *)
TDEC ftf 04 D 0 0 1000 *)
TDEC ftf 03 D 0 0 1000 *)
TDEC ftf 02 D 0 0 1000 *)
TDEC ftf 01 D 0 0 1000 *)
TDEC ftf 00 D 0 0 1000 *)

Date : 2004-09-24
ENGINEERING CENTER

4.4.3.3 Vane-TDEC mul: <M> <3> <3> <3>

TDEC mul 02 U 0 0 1000 *)
TDEC mul 03 U 0 0 1000 *)
TDEC mul 04 U 0 0 1000 *)
TDEC mul 05 U 0 0 1000 *)
TDEC mul 06 U 0 0 1000 *)
TDEC mul 07 U 0 0 1000 *)
TDEC mul 08 U 0 0 1000 *)
TDEC mul 07 D 0 0 1000 *)
TDEC mul 06 D 0 0 1000 *)
TDEC mul 05 D 0 0 1000 *)
TDEC mul 04 D 0 0 1000 *)
TDEC mul 03 D 0 0 1000 *)
TDEC mul 02 D 0 0 1000 *)
TDEC mul 01 D 0 0 1000 *)
TDEC mul 00 D 0 0 1000 *)
4.4.4 Start / Stop: <M> <3> <4>

LFT BK DLY [10 ms] 0 20 999
PROF DLY [10 ms] 0 5 999
PRET FREQ [0,1 Hz] 0 2 100
RMP DWN T2 [10 ms] 10 50 50
DRP BK DLY [10 ms] 0 45 500
EL HLT PER [10 ms] 0 20 500
DEMAG PER [10 ms] 2 5 500
4.4.5 Engineering: <M> <3> <5>
4.4.5.1 Motor parameter: <M> <3> <5> <1>

Mot Fnom [0.1Hz] 250 500 600
Mot Vnom [V] 200 400 500
Mot Nnom [rpm] **** **** **** *)
*) Value is invisible after default setting.

Date : 2004-09-24
ENGINEERING CENTER

4.4.5.2 Control parameter: <M> <3> <5> <2>

Ic U [%In] -100 0 100
Ic D [%In] -100 40 100
Fc U [0.01%fn] -2000 -80 2000
Fc D [0.01%fn] -2000 500 2000
4.4.6 V/f Parameter: <M> <3> <5> <3>

Vstart [0.1% Un] 0 60 200
Vacc [0.1% Un] 500 1100 1600
Vend [0.1% Un] 0 80 200
Vload [0.1% Un] 0 100 250
4.4.7 TDECspec: <M> <3> <5> <4>

1
TDECmulBOT FL 0 0 1000 )
2
TDECmulTOP FL 0 0 1000 )
1
) for manual calibration: set to average value of "TDEC mul U" values
2
) for manual calibration: set to average value of "TDEC mul D" values
4.5 Deceleration distance

Rate of acc / dec Nominal speed Distance of deceleration
2
[m/s ] [m/s] [mm]
0,2 0,25 550
0,2 0,4 800
0,3 0,5 1000
0,3 0,63 1200
0,5 0,8 1400
0,5 1,0 1800
0,5 1,2 2200

Date : 2004-09-24
ENGINEERING CENTER

4.6 Parameter description

4.6.1 Contract parameter: <M> <3> <1>
Parameter Description
Defined contract speed of the unit
Con Spe[0.01m/s]
Example: for contract speed = 1,0m/s Þ set Con Spe = 100
Motor type; depended on slip (see table below).
MOTOR TYPE
If the slip is unknown, set this parameter to 5
DDP[[s]] DDP time
Controller type
RELAY CONTROLLER
0 = MS300, MCS310, MCS220(M)
LV DISTANCE [mm] Distance between LV1 and LV2 switch, should be 30mm
LV MAGNET [mm] Length of LV magnet (usually 150mm)
TOP FLOOR Number of top floor
FDIST 00-01 [cm] Floor distance between bottom floor and floor 1
FDIST 01-02 [cm] Floor distance between floor 1 and floor 2
Motor Dir [0/1] Change motor direction using the parameter value 0 or 1
4.6.1.1 Table of motor types

The parameters are set automatically when the motor type has been changed:
Motor
Description Vstart Vacc Vend Vload Cre Spe Fc D
type
0 standard elevator motor (4% - 8% slip) 60 1100 80 100 10 500
1 13VTR NE (Reivaj VF, 9kW) 25 1100 60 80 15 400
2 predefined; not authorized 40 1100 80 80 10 400
3 140VAT NE (5kW, TBA422J) 40 1100 60 80 10 400
4 11VTR (Reivaj VF,5kW, TBA422J) 40 1100 60 80 10 400
5 high slippage motor (> 8% slip) 60 1100 80 100 10 700
6 very high slip (>14%); not authorized 60 1100 80 100 10 700

Date : 2004-09-24
ENGINEERING CENTER

4.6.2 Profile parameter: <M> <3> <2>

Speed at inspection run.
INS SPE [0,01 m/s]]
Example: for inspection run with 0,5m/s Þ set INS SPE = 50
Nominal speed at constant run (normally set to "Con Spe").
NOM SPE [0,01 m/s]] Can be used to reduce nominal speed for test purposes.
Example: to run a 1,2m/s -unit at half speed Þ set NOM SPE = 60
CRE SPE [0,01 m/s]] Creep speed. Is set automatically depending on motor type.
Acceleration rate. Can be decreased indepently from nominal speed or
ACC [0,01 m/s ]
2
deceleration.
2
Example: for an acceleration rate of 0,5m/s Þ set ACC = 50 [0.01m/s²]
Deceleration rate. Can be decreased indepently from nominal speed or
DEC [0,01 m/s ]
2
acceleration.
2
Example: for a deceleration rate of 0,5m/s Þ set DEC = 50 [0.01m/s²]
4.6.3 Vane / LV Parameter: <M> <3> <3> <1>

Distance between LV signal and the beginning of the profile rampdown-to-stop
LV DLY 00 D [mm]
phase (for floor 0 in DOWN direction). *)
LV DLY 01 U [mm]
phase (for floor 1 in UP direction). *)
LV DLY 01 D [mm]
phase (for floor 1 in DOWN direction). *)

LV DLY 08 D [mm]
phase (for floor 8 in UP direction). *)
4.6.4 Vane / TDECftf Parameter: <M> <3> <3> <2>

TDEC ftf 01 U Correction of deceleration time for a floor to floor run up to floor 1 *)
TDEC ftf 02 U Correction of deceleration time for a floor to floor run up to floor 2 *)
TDEC ftf 08 U Correction of deceleration time for a floor-to-floor run UP to floor 8 *)

TDEC ftf 07 D Correction of deceleration time for a floor-to-floor run DOWN to floor 7 *)
TDEC ftf 01 D Correction of deceleration time for a multiple floor run down to floor 1 *)
TDEC ftf 00 D Correction of deceleration time for a multiple floor run down to floor 0 *)

Date : 2004-09-24
ENGINEERING CENTER

4.6.5 Vane-TDECmul parameters: <M> <3> <3> <3>

Are used to adjust the decelaration times for multi-floor runs (distance is 2 or more floors) to
each individual floor.
SVT-Display Description
TDEC mul 02 U Correction of deceleration time for a multi-floor run UP to floor 2 *)
ß ß
TDEC mul 06 D Correction of deceleration time for a multi-floor run DOWN to floor 6 *)
ß ß
TDEC mul 01 D Correction of deceleration time for a multi-floor run DOWN to floor 1
TDEC mul 00 D Correction of deceleration time for a multi-floor run DOWN to floor 0
*) numbers of parameters depend on TOP FLOOR / BOTTOM FLOOR (example: 8 / 0)
4.6.6 Start / Stop parameter: <M> <3> <4>

LFT BK DLY [10 ms] Lift brake delay
delay from activation of BY (brake relay) to start of speed profile.
Adjust so that the speed profile starts after the brake has completely lifted.
PROF DLY [10 ms]
For testing of start jerk behavior this parameter can be set temporarily to a high
value.
PRET FREQ [0,1 Hz] Specifies the frequency during the profile delay (pre-magnetization) period
Ramp down period during halt.
RMP DWN T2 [10ms] During this time (HALT) the speed profile is reduced by a constant slope from
creep speed to zero
Drop brake delay.
DRP BK DLY [10 ms] The brake should become effective after the drive has stopped electrically. An
experienced value is about 100 ms less than the ramp down period.
Electrical halt period.
After the ramp down period the drive comes to final stop still powered by the
EL HLT PER [10 ms]
inverter.
The brake should become effective during this period
Demagnetization period.
DEMAG PER [10 ms] The inverter output is zero and the current is decreased before the inverter relay
is dropped.

Date : 2004-09-24
ENGINEERING CENTER

4.6.7 Engineering parameter: :<M> <3> <5>
4.6.7.1 Motor parameter:<M> <3> <5> <1>

Nominal motor frequency specified by motor name plate.
Mot Fnom [0.1Hz]
Note: Parameter appears also in Contract menu.
Mot Vnom [V] Nominal phase-to-phase voltage specified by motor name plate *)
Mot Nnom [rpm] --- not used in standard configuration (debugging only) ---
4.6.7.2 Control parameter:<M> <3> <5> <2>

The following values are part of the frequency (load) compensation during creep speed.
They are set automatically by the calibration routine and should not be changed unless the
load compensation does not work properly.
DC link current during the constant phase of the speed profile in up direction
Ic U [%In] (empty car). The current value is part of the correct frequency (load)
compensation during creep speed.
DC link current during the constant phase of the speed profile in down direction
Ic D [%In] (empty car). The current value is part of the correct frequency (load)
compensation during creep speed.
Frequency compensation value during the creep phase of the speed profile in
Fc U .005Hz up direction (empty car). The compensation value is part of the correct
frequency (load) compensation during creep speed.
Frequency compensation value during the creep phase of the speed profile in
Fc D .005Hz down direction (empty car). The compensation value is part of the correct
frequency (load) compensation during creep speed.
Some fields require negative values. Press <OFF> key to toggle between positive and negative value input.
4.6.7.3 V/f parameter: <M> <3> <5> <3>

Vstart [0,1% Un] Lowest voltage value of the U/f-characteristic (at frequency = 0)
Specifies the voltage at nominal frequency (fn)
Vacc [0,1% Un]
Upper value of the U/f-characteristic
Vend [0,1% Un] Lowest voltage value of the U/f-characteristic while stopping
Vload [0,1% Un] Voltage increase during acceleration
4.6.7.4 TDECspec <M> <3> <5> <4>

Special calibration parameter; usable for creep time problems at bottom floor
TDECmulBOT FL
Note: for manual calibration set to average value of "TDEC mul U" values
Special calibration parameter; usable for creep time problems at top floor
TDECmulTOP FL
Note: for manual calibration set to average value of "TDEC mul D" values

Ovf20cro Adt

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Ovf20cro Adt

Transféré par

Droits d'auteur :

Formats disponibles

OTIS - OEC OVF20-CR with LCB_II Dwg : GAA21342B_ADT

FSM Advanced diagnostics and trouble shooting

OVF20-CR with LCB_II

Authorization Date: 2004-09-24

Software Version: MCBIIIx: GAA30763BAA

Date Author Page Comment

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

4.4.5 Engineering: <M> <3> <5> ............................................................................................................... 44

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

1 Trouble shooting flow chart

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

1.1 Step 1: elevator status check

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

1.2 Step 2: failure group selection

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

1.3 Step 3: failure handling using service tool

1.3.1 Operational control system (LCB_II)

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

1.3.2 Drive control system (MCB_III)

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

1.3.3 Service tool connection via drive OVF20-CR

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

2 Failure handling using service tool

2.1 Elevator is blocked

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

Failures related to the CAR AND HOISTWAY DOOR (continued)

LCB_II: <M> <1> <2> <1> <GO ON> DS Bypass OCSS

LCB_II: <M> <1> <2> <1> <GO ON> /DFC in FR MCSS

LCB_II: <M> <1> <2> <1> <GO ON> /DFC in SR MCSS

LCB_II: <M> <1> <2> <1> <GO ON> /DW in FR MCSS

LCB_II: <M> <1> <2> <1> <GO ON> /DW in SR MCSS

LCB_II: <M> <1> <2> <1> <GO ON> DCL in [ ] DCSS

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

Failures related to the CAR AND HOISTWAY DOOR (continued)

LCB_II: <M> <1> <2> <1> <GO ON> DOL:alw. on DCSS

LCB_II: <M> <1> <2> <1> <GO ON> Hwy-Access DCSS

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

2.1.2 Failures related to the SAFETY CHAIN

LCB_II: <M> <1> <2> <1> <GO ON> /ES in SR MCSS

MCB_III: <M> <2> <2> <2> <GO ON> M C: EMERGNCY ST

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

2.1.3 Failures related to the VF DRIVE

2.1.4 Failures related to the CAR LIGHT

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

2.1.5 Failures related to the BRAKE

Unpublished Work Copyright © OTIS Elevator Company

FSM Advanced diagnostics and trouble shooting

2.2 Elevator malfunction: car is running with failure