Otis Gecb LV

OTIS - SSI GECB-LV Dwg: GAA25PJ_ADT
Date : 2013-06-17
SSI – ENGINEERING Page : 1/64
BERLIN GECB
FSM Advanced diagnostics and trouble shooting
GECB-LV
Advanced diagnostics and trouble shooting
Authorization Date:
Running on PCB: GECB-LV: GAA26800NR
Software Version: GECB_II: GAA30780EAH
Document Revision:
Date Author Page Comment

2013-06-17 M. TOUTAOUI 64 Original document
Otis Elevator Company Proprietary Information

© 2013, Otis Elevator Company
Date : 2013-06-17
BERLIN GECB
CONTENTS
1. Flow chart ....................................................................................................................................................... 4
1.1 STEP 1: ELEVATOR STATUS CHECK.................................................................................................................. 5
1.2 STEP 2: VISUAL CHECK: SERVICE PANEL ......................................................................................................... 5
1.3 STEP 3: FAILURE GROUP SELECTION ............................................................................................................... 6
1.4 STEP 4: FAILURE HANDLING USING OFT .......................................................................................................... 7
2 Visual check ................................................................................................................................................... 8
2.1 SERVICE PANEL STATUS DISPLAY .................................................................................................................... 8
2.2 SERVICE PANEL KEY DESCRIPTION .................................................................................................................. 9
2.3 SERVICE PANEL: BUTTONS ........................................................................................................................... 10
3 Failures handling using OFT ...................................................................................................................... 11
3.1 ELEVATOR IS BLOCKED ................................................................................................................................. 12
3.1.1 Failures related to the CAR AND HOISTWAY DOOR ...................................................................... 12
3.1.2 Failures related to the SAFETY CHAIN ............................................................................................ 15
3.1.3 Failures related to TEMPERATURE ................................................................................................. 19
3.1.4 Failures related to the CAR LIGHT ................................................................................................... 19
3.1.5 Failures related to EMERGENCY POWER OPERATION (EPO) ..................................................... 19
3.2 ELEVATOR MALFUNCTION: CAR IS RUNNING WITH FAILURE .............................................................................. 20
3.2.1 Failures related to the CAR AND HOISTWAY DOOR ...................................................................... 20
3.2.2 Failures related to the COMMUNICATION ....................................................................................... 22
3.2.3 Failures related to the HOISTWAY SIGNALS .................................................................................. 23
3.2.4 Failures related to SHUT DOWN ...................................................................................................... 30
3.2.5 Failures related to REMOTE SERIAL LINK ...................................................................................... 30
3.2.6 Failures related to the DRIVE ........................................................................................................... 32
3.2.7 Failures related to LOAD WEIGHING ............................................................................................... 34
3.2.8 Failures related to RESCUE ............................................................................................................. 35
3.2.9 Information for ENGINEERING ONLY .............................................................................................. 40
3.3 ELEVATOR FAILURES DURING INSTALLATION OR MAINTENANCE ....................................................................... 42
3.3.1 Failures related to wrong HARDWARE ............................................................................................ 42
3.3.2 Failures related to PARAMETER SETUP ......................................................................................... 42
3.3.3 Failures related to SOFTWARE UPDATE ........................................................................................ 42
3.3.4 Failures related to LEARN RUN ....................................................................................................... 43
3.3.5 Failures related to NORMAL RUN .................................................................................................... 43
4 Appendix ....................................................................................................................................................... 45
4.1 SERVICE PANEL ........................................................................................................................................... 45
4.1.1 Key lock............................................................................................................................................. 45
4.1.2 Graphical symbol overview ............................................................................................................... 46
4.2 GECB-LV INTERFACES ................................................................................................................................ 51
4.3 GECB SETUP .............................................................................................................................................. 52
4.3.1 Setup allowed Mask .......................................................................................................................... 52
4.3.2 Enable Mask ..................................................................................................................................... 53
4.3.3 Cut call Mask..................................................................................................................................... 54
4.3.4 Card Reader Mask ............................................................................................................................ 55
4.3.5 Position Indicator setup ..................................................................................................................... 56
4.3.6 ELD setup ......................................................................................................................................... 57
4.3.7 Floor Display ..................................................................................................................................... 58
4.3.8 Edit Display ....................................................................................................................................... 59
4.3.9 Store Display ..................................................................................................................................... 60
4.3.10 Default Display.............................................................................................................................. 61
4.3.11 Rescue Menu................................................................................................................................ 62
4.4 REMOTE STATIONS ...................................................................................................................................... 63
4.4.1 RS functionality test .......................................................................................................................... 63

Date : 2013-06-17
BERLIN GECB
4.4.2 Search I/O address ........................................................................................................................... 64

Date : 2013-06-17
BERLIN GECB
1. Flow chart

Date : 2013-06-17
BERLIN GECB
1.1 Step 1: elevator status check
1.2 Step 2: visual check: Service Panel

Date : 2013-06-17
BERLIN GECB
1.3 Step 3: failure group selection

Date : 2013-06-17
BERLIN GECB
1.4 Step 4: failure handling using OFT

Date : 2013-06-17
BERLIN GECB
2 Visual check
2.1 Service Panel status display
SDI - Speed and Direction Indicator
DZI – Door zone Indicator
PI - Position Indicator
Signal Status
DZ EG es DW DFC
dob dol grp
NOR ddo chc
Service Status Symbol
MAIN Trapped Passenger Alarm
.Construction.... Battery Status Symbol
Startup Key lock Symbol
Test
...OK..
. Menu
Softkeys
SDI Shows the speed and direction of the car as measured by the encoder inputs located on
GECB_II.
The maximum value is defined by the parameter SDI-Max.
DZI DZ: The car is within the doorzone.
dz: The car is outside the doorzone
Battery Battery is charging. Rescue is possible.

Battery is fully charged. Rescue is possible.
Battery fault. Rescue is not possible. Check Battery and BCB.
Service Service notification for Gateway is ON

(blanc) Service notification for Gateway is OFF
Trapped The Trapped Passenger Alarm (TPA) button was pushed.

Passenger (blanc) No TPA active.
Alarm
PI EG: The display of the Car Position Indicator is shown in inverted style.
00: If the Position Indicator Setup is not valid, a floor counter is displayed in
non-inverted style.
Signals DW: Logically active inputs are displayed in uppercase inverted style.
es: Inactive inputs are displayed in lowercase normal style.
Menu The name of the shown menu is displayed in the first line in uppercase.
The selected menu function is highlighted in inverted style. Push the softkey OK to activate
this menu function.
Softkey In the bottom area, up to three softkeys can be shown. The name and functionality of these
softkeys are context sensitive and depend on the selected function.

Date : 2013-06-17
BERLIN GECB
2.2 Service Panel key description

Date : 2013-06-17
BERLIN GECB
2.3 Service Panel: buttons
Button Name Description

CCTL Car Call to Top Landing This button enters a car call to the top floor. Only available
in normal operation.
CCBL Car Call to Bottom Landing This button enters a car call to the bottom floor. Only
available in normal operation.
CCTL+CCBL Start a Correction Run If the buttons CCTL+CCBL are pushed for longer than 1
(> 1 sec) second, the system will perform a correction run. Outside
1LS/2LS, the direction of the COR can be defined by the
order in which CCTL/CCBL is pressed.
CHCS Cancel Hall Call Switch This button disables the hall calls. If activated, the car parks
with opened doors (except if DDO is activated).
If active, the status display shows “CHC”.
If inactive, the status display shows “chc”.
DDO Disable Door Operation This button disables door operation.

If active, the status display shows “DDO”.
If inactive, the status display shows “ddo”.
Up Within the menu, this button moves the menu selection up

by one row.
Down Within the menu, this button moves the menu selection
down by one row.
END End Only applicable for GCS222MRL, not for GCS222LVA:

When this button is pushed, the menu function is left and
the main menu is displayed.
When this button is pushed for longer than 2 seconds, a
new initialization of the SP is performed.
(softkeys) Context sensitive The meaning of the three softkeys depends on the currently
active menu function and is shown in the lowest line of the
display just above the corresponding button.
BRB1 Brake Release Button When this button is pushed, the RESCUE function is
activated.

Date : 2013-06-17
BERLIN GECB
3 Failures handling using OFT

Date : 2013-06-17
BERLIN GECB
3.1 Elevator is blocked

3.1.1 Failures related to the CAR AND HOISTWAY DOOR
<M> <1> <2> <1> <GO ON> DoorBridge “blinking message”: 0302
DW or DFC input has not been low while the door was opened.
Possible reason What to do
Bridged door lock.  check safety chain
 This event is stored into EEPROM so that the
ONLY way to bring the elevator into operation
again is by using INS.
<M> <1> <2> <1> <GO ON> Switch INS “blinking message”
Elevator is taken out of service.
Landing door was opened for longer than 4  This event is stored into EEPROM so that the
seconds or the car door is bridged ONLY way to bring the elevator into operation
<M> <1> <2> <1> <GO ON> OpMode DTC Event number:0102
The door time protection for closing is exceeded.
door was not able to close (missing DCL,  check the related DCL (694)
DFC, DW or GDS) within timeout setup RDCL (695)
DOOR, REAR
DTC-T
<M> <1> <2> <1> <GO ON> OpMode DTO Event number:0103
The door time protection for opening is exceeded.
door was not able to open (missing DOL)  check the related DOL (000)
within timeout setup RDOL (544)
DOOR, REAR
DTO-T
<M> <1> <2> <1> <GO ON> OpMode DCP Event number:0104
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 : 2013-06-17
BERLIN GECB
Failures related to the CAR AND HOISTWAY DOOR (continued)
<M> <1> <2> <1> <GO ON> PDS active Event number:0106
The partition door switch is opened
PDS is opened  check the related setup: PDD (784)
<M> <1> <2> <1> <GO ON> /DFC in FR Event number:0211

The car door has been opened during Fast Run
DFC (door fully closed) input signal is missing  check the signal DFC
<M> <1> <2> <1> <GO ON> /DFC in SR Event number:0212

The car door has been opened during Slow Run
DFC (door fully closed) input signal is missing  check the signal DFC
<M> <1> <2> <1> <GO ON> /DW in FR Event number:0237

The landing door has been opened during Fast Run
DW input signal is missing  check the signal DW
<M> <1> <2> <1> <GO ON> /DW in SR Event number:0238

The landing door has been opened during Slow Run
DW input signal is missing  check the signal DW
<M> <1> <2> <1> <GO ON> /ES with ][ Event number:0239
The TES or PES button was pushed without seeing a prior “/DW in FR” or “/DW in SR” event. If a prior
“/DW in FR” or “/DW in SR” event is seen, then that would be an indication of the normal procedure to
enter the hoistway, so is not reported.
<M> <1> <2> <1> <GO ON> /DW > 5min Event number:0240
The DW signal is missing for 5 minutes, but no HAD and no DTC was detected.
<M> <1> <2> <1> <GO ON> /DFC > 5min Event number:0241
The DFC signal is missing for 5 minutes, but no HAD and no DTC was detected.

Date : 2013-06-17
BERLIN GECB
Failures related to the car and hoistway door (continued)
<M> <1> <2> <1> <GO ON> DOL alw.on Event number:0304
The front door open limit is detected.
DOL was active (low) while the door was fully  Check the event log to find out DOL (000)
closed. This event is also logged when the whether the front or the rear door
fuses of the door system are burned. This signal is wrong
event is not logged within the first 40 seconds  Check the door fuses
after system startup.  Check 24V power supply
<M> <1> <2> <1> <GO ON> RDOL alw.on Event number:0307
The rear door open limit is detected.
RDOL was active (low) while the door was  Check the event log to find out RDOL (544)
fully closed. This event is also logged when whether the front or the rear door
the fuses of the door system are burned. This signal is wrong
event is not logged within the first 40 seconds  Check the door fuses
after system startup.  Check 24V power supply
<M> <1> <2> <1> <GO ON> DCL in [ ] Event number:0301

Door close limit is activated.
(R)DCL was active while the door was fully  check the related DCL (694)
opened setup: RDCL (695)
<M> <1> <2> <1> <GO ON> Hwy Access Event number:0306
Elevator is taken out of service.
Landing door was opened or the car door is  This event is stored into EEPROM so that the
bridged ONLY way to bring the elevator into operation
<M> <1> <2> <1> <GO ON> DS bypass Event number:0107

Failure related to door switch bypass
Malfunction of Disable Door Switch Relays  Check the related setup: DDSRC (970)
(DDSR) for Generic Firemen Service.

Date : 2013-06-17
BERLIN GECB
3.1.2 Failures related to the SAFETY CHAIN

<M> <1> <2> <1> <GO ON> SE-Fault “blinking message”:0205
The start enable signal is missing
The car cannot start due to missing SE-signal  Check the door bypass
<M> <1> <2> <1> <GO ON> 2SE-Fault “blinking message”:0244

nd
The input 2 Start Enable opened (e.g. active BID).
<M> <1> <2> <1> <GO ON> /ES in FR Event number:0202

The emergency stop signal is detected.
ES-input was activated during Fast Run  Check the switches and contacts leading to ES-
input
<M> <1> <2> <1> <GO ON> /ES in SR Event number:0203

The emergency stop signal is detected.
ES-input was activated during Slow Run  Check the switches and contacts leading to ES-
input
<M> <1> <2> <1> <GO ON> DBP: dfc_SE Event number:0300
Failure related to door bypass
While the door was opening or fully opened,  Check the related EN-RLV,
the door bypass was found to be inactive setup: EN-ADO
(DFC low or SE high)
<M> <1> <2> <1> <GO ON> DBP-Fault! “blinking message”:0303

Two correction runs have been performed in sequence
Two correction runs have been performed in  Check LVC-relay EN-RLV,
sequence. This can occur if no door zone is DRV-TYP
detected after having stopped.
The reason for that can be a defective LVC-
relay.
This event is stored into EEPROM so that the
ONLY way to bring the elevator into operation
<M> <1> <2> <1> <GO ON> SP: en.DBP! Event number:0318
ADO or /& RLV must be enabled via SP menu (installation without SVT): EN-ADO, EN-RLV

Date : 2013-06-17
BERLIN GECB
Failures related to safety chain (continued)
<M> <1> <2> <1> <GO ON> DoorBridge Event number:0302

DW or DFC was not low during the last door cycle
the safety chain is bridged  remove the bridge
the Door Bypass is defect  check the door bypass
<M> <1> <2> <1> <GO ON> FSO Rly Err “Blinking message”:0253
When the inconsistency is detected for front SO relay
When the inconsistency is detected for front  When the inconsistency is EN-SO=1
SO relay detected for front SO relay
 Check IO FDZ(1195),
FSO(1197) and CHK_SO(1196)
<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, 968)
<M> <1> <2> <1> <GO ON> 110VAC dead Event number:0225
110VAC is dead for 5 seconds
110VAC is dead for 5 seconds  check the missing voltage
<M> <1> <2> <1> <GO ON> No 110VAC “blinking message”

The power supply of the safety chain is missing.
The power supply of the safety chain is  check the connections
missing.  check the fuses
<M> <1> <2> <1> <GO ON> EEC bypass Event number:0108
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.

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> TCI-Lock “blinking message”

The sequence to leave TCI-mode was not correctly followed:
 The correct sequence is:
1. Operate TES
2. Open door
The sequence to leave TCI-mode was not
3. Leave car roof
correctly followed:
4. Switch TCI off
5. Release TES
6. Close door
<M> <1> <2> <1> <GO ON> ETSC Fault Event number:0242
Emergency Terminal Slowdown Circuit has failed. PX2.1=2 ; UP(576) ; DN(577)
<M> <1> <2> <1> <GO ON> ETSC Block Event number:0243
System is blocked after ETSD Failure to prevent further runs: PX2.1=2 ; UP(576) ; DN(577)
<M> <1> <2> <1> <GO ON> /UIB/DIB FR Event number:0245

The safety chain opened at UIB or DIB during a run while accelerating or at constant velocity.
<M> <1> <2> <1> <GO ON> /UIB/DIB SR Event number:0246

The safety chain opened at UIB or DIB during a run while decelerating.
<M> <1> <2> <1> <GO ON> /UIB/DIB>30 Event number:0247

The safety chain stayed open at UIB or DIB for longer than 5 seconds.
Low Overhead installations (OHLOW).  Check KS contact
<M> <1> <2> <1> <GO ON> ES Wiring “blinking message”:0248

ES Safety chain wiring fault
 Check the safety chain wiring.
PES not wired in series After correction of the wiring the error is cleared by
switching off/on

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> SAF Wiring “blinking message”:0249
SAF Safety chain wiring fault (DS/GS not wired in series)
 check safety chain wiring. After correction of the
wiring the error is cleared by successful door
SAF Safety chain wiring fault (DS/GS not
operation or by unlocking the landing door.
wired in series)
 For GCS222MRL, the SP function “Tools – Safety
Wiring” must be executed.
<M> <1> <2> <1> <GO ON> 6LS-TYP! “blinking message”:0250

Wrong parameter “6LS-TYP”
The parameter “6LS-TYP” at GECB has a
 Check GECB Parameter “6LS-TYP”
different value than the parameter “6LS-TYP”
 Check Drive parameter “6LS-TYP”
at the drive.
<M> <1> <2> <1> <GO ON> RBU-Selftst Event number:0617

Selftest of Rope Brake has failed (i.e. lasted longer than 5 seconds). RBTC (1029)
Car is blocked until TCI/ERO is switched. RBTE (1028)
<M> <1> <2> <1> <GO ON> RBU-Fault Event number:0618

Rope Brake has detected overspeed. RBTC (1029)
Car is blocked until TCI/ERO is switched or the controller is switched off RBTE (1028)
<M> <1> <2> <1> <GO ON> No UIB DIB blinking message
The safety chain stayed open at UIB and DIB for longer than 5 seconds
The safety chain stayed open at UIB and DIB  In Low Overhead Installations (OHLOW), check KS
for longer than 5 seconds. contact
<M> <1> <2> <1> <GO ON> SOS up Event number:0612

SOSU (1054)
Safety Operated Switch Up triggered
HWY-TYP
<M> <1> <2> <1> <GO ON> SOS down Event number:0613
SOSD (1054)
Safety Operated Switch Down triggered
HWY-TYP

Date : 2013-06-17
BERLIN GECB
3.1.3 Failures related to TEMPERATURE

<M> <1> <2> <1> <GO ON> 1TH-Fault “blinking message”:0222
Failure related to thermal contact 1
The DBR-contact connected to the input 1TH
 The drive is powered down to allow cooling.
is opened.
<M> <1> <2> <1> <GO ON> 2TH-Fault “blinking message”:0223

Failure related to thermal contact 2
One of the contacts connected to 2TH is
 The drive is powered down to allow cooling.
opened.
3.1.4 Failures related to the CAR LIGHT

<M> <1> <2> <1> <GO ON> Car Light “blinking message”
Failure related to car light switch
Car Light Relay on top of car is dropped.  Check the car light relay/related setup: CLR (1000)
<M> <1> <2> <1> <GO ON> NoCarLight Event number:0113

The light within the car has failed.
3.1.5 Failures related to EMERGENCY POWER OPERATION (EPO)

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

Date : 2013-06-17
BERLIN GECB
3.2 Elevator malfunction: car is running with failure

3.2.1 Failures related to the CAR AND HOISTWAY DOOR
<M> <1> <2> <1> <GO ON> Stuck DCB Event number:0109
Door Close Button contact permanent active
DCB contact permanent active  Check the related setup: DCB (003)
<M> <1> <2> <1> <GO ON> Stuck RDCB Event number:0110
Rear Door Close Button contact permanent active
RDCB contact permanent active  Check the related setup: DCB (547)
<M> <1> <2> <1> <GO ON> FDOOR stuck Event number:0321
Front door is stuck reversing over and over again
<M> <1> <2> <1> <GO ON> RDOOR stuck Event number:0322
Rear door is stuck reversing over and over again
<M> <1> <2> <1> <GO ON> GDS noPull Event number:0314
Gate Door Switch relay not pulled
GDS relay not pulled  Check the relay and the wiring
<M> <1> <2> <1> <GO ON> GDS noDrop Event number:0315
Gate Door Switch relay not dropped
GDS relay not dropped  Check the relay and the wiring
<M> <1> <2> <1> <GO ON> GSM Ferror Event number:0319
Gate Switch Monitoring input error front door
GSM input error front door  Check GSM signal
<M> <1> <2> <1> <GO ON> GSM Rerror Event number:0320
Gate Switch Monitoring input error rear door
GSM input error rear door  Check GSM signal

Date : 2013-06-17
BERLIN GECB
Failures related to the CAR AND HOISTWAY DOOR (continued)
<M> <1> <2> <1> <GO ON> ABL Abort Event number:0235
Advanced Brake Lift was aborted
Advanced Brake Lift was aborted because EN-ABL=1,
 Check the related setup
the door was not fully closed 10 seconds after DRV-TYP=1
the brake was lifted
<M> <1> <2> <1> <GO ON> Stuck CB Event number:0111

Car Call Button contact permanent active
<M> <1> <2> <1> <GO ON> Stuck HB Event number:0112

Hall Call Button contact permanent active
<M> <1> <2> <1> <GO ON> FDOOR /Deen Event number:0323
disable PowerSave mode after deenergized front door could not kept closed
<M> <1> <2> <1> <GO ON> RDOOR /Deen Event number:0324
disable PowerSave mode after deenergized rear door could not kept closed
<M> <1> <2> <1> <GO ON> Stuck WDCB Event number:0124
Wheel Chair Door Close Button contact permanent active: WDCB(1167)
<M> <1> <2> <1> <GO ON> Stuck RWDCB Event number:0125
Rear Wheel Chair Door Close Button contact permanent active: RWDCB(1171)
<M> <1> <2> <1> <GO ON> Ext LV Err Event number:0317
The external door zone sensor X1LV or X2LV was active outside of a door zone:
X1LV (1039) ; X2LV (1040)

Date : 2013-06-17
BERLIN GECB
3.2.2 Failures related to the COMMUNICATION

<M> <1> <2> <1> <GO ON> DOOR sync Event number:0308
Multidrop synchronization error
Multidrop synchronization error  Check the Multidrop communication
<M> <1> <2> <1> <GO ON> DOOR adr Event number:0309
Multidrop unused message origin
Multidrop unused message origin  Check the Multidrop communication
<M> <1> <2> <1> <GO ON> FDOOR chk Event number:0310
Multidrop front door checksum error
Multidrop front door checksum error  Check the Multidrop communication
<M> <1> <2> <1> <GO ON> RDOOR chk Event number:0311
Multidrop rear door checksum error
Multidrop rear door checksum error  Check the Multidrop communication
<M> <1> <2> <1> <GO ON> FDOOR Tout Event number:0312
Multidrop front door communication timeout (>200ms)
Multidrop front door communication timeout
 Check the Multidrop communication
(>200ms)
<M> <1> <2> <1> <GO ON> RDOOR Tout Event number:0313
Multidrop rear door communication timeout (>200ms)
Multidrop rear door communication timeout
 Check the Multidrop communication
(>200ms)
<M> <1> <2> <1> <GO ON> BCB-Comm. Blinking message

CAN-Communication to BCBIO is not working.
CAN-Communication to BCBIO is not  Check CAN-wiring
working.  Check CAN-LEDs

Date : 2013-06-17
BERLIN GECB
3.2.3 Failures related to the HOISTWAY SIGNALS

<M> <1> <2> <1> <GO ON> 1LS+2LS on “blinking message”: 0228
The normal terminal slowdown limit switches for top (2LS) and bottom (1LS) floor are on.
Limit switches 1LS and 2LS are active at the  Check power supply of the position reference
same time. system.
<M> <1> <2> <1> <GO ON> LS-fault “blinking message”: 0226
In a door zone where 1LS or 2LS is required, the corresponding signal is not 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!
Note: Some controller-/drive- types require the LS signals directly connected to LCBII and others to the
RSL.
<M> <1> <2> <1> <GO ON> Ext LV-Flt “blinking message”
For the Australian Code, CAUS1. The car left the door zone but the external X1LV (1039)
sensors still indicate that it is in the door zone. X2LV (1040)
<M> <1> <2> <1> <GO ON> RLV-Count “blinking message”

The car did not reach the UIS/DIS-zone after the maximum number of releveling EN-RLV
steps which is given by the parameter RLVCNT RLVCNT
RL-UIS
RL-DIS
<M> <1> <2> <1> <GO ON> DZ missed “blinking message”:0263

UIS & DIS have been detected without DZ. This happens when one of LV relays is defect (EN-RLV)
<M> <1> <2> <1> <GO ON> /DZ in NST Event number:0210
Door zone (DZ)-signal was lost or not detected at all after having stopped
The inputs signals 1LV, 2LV on the Drive are  Check the input signals on the Drive
missing
CAN-Communication not working  check CAN-wiring
 check CAN-LEDs
<M> <1> <2> <1> <GO ON> ETSC-Fault Blinking message

ETSD Self-test has failed: PX2.1=2 ; UP(576) ; DN(577)
<M> <1> <2> <1> <GO ON> ETSD-Fault Blinking message

ETSD Circuit has triggered. This is the case if DFC+uib+dib is seen
PX2.1=2 ; UP(576) ; DN(577)
during run.

Date : 2013-06-17
BERLIN GECB
Failures related to the HOISTWAY SIGNALS
<M> <1> <2> <1> <GO ON> ETSD-Comm blinking message

The ET_S1-4 expectation message from the Drive was not received for 3 seconds.
The ET_S1-4 expectation message from the  Check CAN-wiring PX2.1=4 or 5 PX2.2=1
Drive was not received for 3 seconds.  Check CAN-LEDs ET_P1(1257)
ET_P2(1258)
ET_S1(1259)
ET_S2(1260)
ET_P3(1261)
ET_P4(1262)
ET_S3(1263)
ET_S4(1264)
<M> <1> <2> <1> <GO ON> ETSD-Fault blinking message

ETSD with reed switch monitor function has detected a problem
ETSD with reed switch monitor function has  Check relays PX2.1=4 or 5
detected a problem. This is the case if the PX2.2=1
ET_P1-4 signals do not match their expected ET_P1(1257)
value in a door zone, or if the ET_S1-4 ET_P2(1258)
signals do not match their expected values ET_S1(1259)
during the run ET_S2(1260)
Inconsistent configuration of ETSD-related  disable all ETSD ET_P3(1261)
parameters or IOs. If you want to disable the parameters and IOs ET_P4(1262)
ETSD function, you must disable all ETSD ET_S3(1263)
parameter and unprogram all IOs mentioned ET_S4(1264)
under “Related setup”. Additionally, if the
factory has programmed the ETSD pattern
into the EEPROM, then the function cannot
be disabled.
<M> <1> <2> <1> <GO ON> EtsdCommErr Event number:0256

The ET_S1-4 expectation message from the Drive was not received for 3 seconds.
The ET_S1-4 expectation message from the  Check CAN-wiring PX2.1=4 or 5
Drive was not received for 3 seconds.  Check CAN-LEDs ET_P1(1257)
ET_P2(1258)
ET_S1(1259)
ET_S2(1260)
ET_P3(1261)
ET_P4(1262)
ET_S3(1263)
ET_S4(1264)

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> Etsd Block Event number:0257
ETSD with reed switch monitor function has detected a problem.
ETSD with reed switch monitor function has  Check relays PX2.1=4 or 5
detected a problem. This is the case if the  Chack configuration ET_P1(1257)
ET_P1-4 signals do not match their expected ans IOs ET_P2(1258)
value in a door zone, or if the ET_S1-4 ET_S1(1259)
signals do not match their expected values ET_S2(1260)
during the run, or if the configuration of the ET_P3(1261)
parameters and IOs is inconsistent. ET_P4(1262)
ET_S3(1263)
ET_S4(1264)
<M> <1> <2> <1> <GO ON> /UIB/DIB ET Event number:0258

The safety chain opened between DFC and UIB/DIB within the first step ETSD zone
The safety chain opened between DFC and  verify Drive ETSD PX2.1=4 or 5
UIB/DIB within the first step ETSD zone, as settings, “ETP ET_P1(1257)
indicated by ET_P1 and ET_P2 Spe %DutySpe” and ET_P2(1258)
“ETP2 Spe %Duty” ET_S1(1259)
 verify ET_P1-4 sensor ET_S2(1260)
adjustment ET_P3(1261)
ET_P4(1262)
ET_S3(1263)
ET_S4(1264)
<M> <1> <2> <1> <GO ON> LateET_S2/4 Event number:0259

The ASCB-controlled relays, ET_S2 and/or ET_S4 switch open too late during acceleration
The ASCB-controlled relays, ET_S2 and/or  readjust ASCB PX2.1=4 or 5
ET_S4 switch open too late during settings ET_P1(1257)
acceleration in comparison to the GECB- ET_P2(1258)
controlled relays, ET_S1 and/or ET_S3 ET_S1(1259)
ET_S2(1260)
ET_P3(1261)
ET_P4(1262)
ET_S3(1263)
ET_S4(1264)
<M> <1> <2> <1> <GO ON> DDP in FR Event number:0207

no hoistway signals have been detected during Fast Run (missing DZ): DDP

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> DDP in SR Event number:0208

duration of Slow Run is longer than 3P-time (i.e. no stop signal has been detected): 3P
<M> <1> <2> <1> <GO ON> DDP in RS Event number:0209

duration of Rescue Run is longer than 3P-time (i.e. no stop signal has been detected): 3P
<M> <1> <2> <1> <GO ON> KS-L fault “blinking message”:0334
Low Pit: KS-L is stuck closed (KS-L=off) although the bottom landing door is open
KS-L is stuck closed (KS-L=off) although the  Check KS-L and DS1 HWY-TYP
bottom landing door is open (DS1=off) for > 4 switches and wiring. KS-L (1251)
s while the car is not at the bottom floor or at DS1 (1252)
the bottom floor outside DZ.
<M> <1> <2> <1> <GO ON> APS fault “blinking message”:0335
Front or rear Toe Guard is “folded” above 1LS
Front or rear Toe Guard is “folded” above  Check APS and RAPS
HWY-TYP
1LS (APS=off or RAPS=off) for > 2 s or front switches and wiring.
APS (1254)
or rear Toe Guard is “unfolded” at bottom
RAPS (1256)
floor (APS=ON or RAPS=ON) for > 2 s.
<M> <1> <2> <1> <GO ON> /TUM1 Event number:0607

TUM1 missing after run at TOP or active during standstill
TUM1 missing after run at TOP or active  Check the contacts
during standstill; (reduced overhead: trigger TUM1 (1047) HWY-TYP
module contacts)
<M> <1> <2> <1> <GO ON> /TUM1 Event number:0608

TUM2 missing after run at TOP or active during standstill
TUM2 missing after run at TOP or active  Check the contacts
during standstill; (reduced overhead: trigger TUM2 (1048) HWY-TYP
module contacts)

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> /TDM Event number:0609

TDM missing after run at BOTTOM or active during standstill
TDM missing after run at BOTTOM or active  Check the contacts
during standstill; (shallow pit: trigger module TDM (1049) HWY-TYP
contacts)
<M> <1> <2> <1> <GO ON> /TUPS Event number:0610

TUPS missing during run;
TUPS missing during run; (reduced  Check the contacts
TUPS (1050) HWY-TYP
overhead: trigger module power supply)
<M> <1> <2> <1> <GO ON> /TDPS Event number:0611

TDPS missing during run;
TDPS missing during run; (shallow pit:  Check the contacts
TDPS (1051) HWY-TYP
trigger module power supply)
<M> <1> <2> <1> <GO ON> TUM/TDM Event number:0611

One of the trigger modules (up or down) RSL inputs detected a failure
One of the trigger modules (up or down) RSL  Check event log /
inputs detected a failure (needed for reduced switch to ERO to HWY-TYP, I/O’s 1047 - 1051
hoistway). reset (after solving).
<M> <1> <2> <1> <GO ON> HWY-TYP! “blinking message”:0619

The Factory-programmed EEPROM does not match the setting of HWY-TYP (LOSP)
The Factory-programmed EEPROM does not  Check the parameter setting
match the setting of HWY-TYP for Low
Overhead / Shallow Pit settings.

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> LOPIT cfg! “blinking message”
The parameter HWY-TYP is not configured for Low Pit
The parameter HWY-TYP is not configured  Set APS and RAPS according to
for Low Pit (4 for APS, 8 for RAPS, or 12 for the factory setup.
APS and RAPS) although the E²PROM has
been configured in the factory to require Low
Pit to be configured.
RSL IOs
 For a Low Pit configuration set KS-L (1251)
HWY-TYP is set to 4, 8, or 12 but the Ultra
Drive installation parameter Low Pit is set to Ultra Drive Low Pit to 1 and for a DS1 (1252)
normal pit configuration set PMSI (1253)
0.
HWY-TYP accordingly (e.g. 0). APS (1254)
RAPS (1256)
 For a Low Pit configuration set PBUZ (1255)
HWY-TYP is set to 0 but Ultra Drive Low Pit
is set to 1. HWY-TYP according to the
present APS/RAPS and for a Ultra Drive
normal pit configuration set parameter Low
HWY-TYP accordingly (e.g. 0). Pit
RSL IOs KS-L, DS1, PMSI, APS (if present),  Set RSL IOs to valid addresses.
RAPS (if present), PBUZ do not have valid
addresses.
<M> <1> <2> <1> <GO ON> UCM Detect Blinking message:0234
Unintended Car Movement (leaving the door zone with open doors under motor) was detected by the
GECB or by the Drive or both : (UCM-TYP=1, 2,3)
<M> <1> <2> <1> <GO ON> UCM Welded Blinking message:0232
The UCM relay is stuck.
The UCM relay is stuck.  Check Hardware (UCM-TYP=1)
<M> <1> <2> <1> <GO ON> UCMRWelded Blinking message

The UCM relay is stuck.
The UCM relay is stuck.  Check Hardware (UCM-TYP=1)
<M> <1> <2> <1> <GO ON> UCMCommErr Blinking message:0252

CAN communication fault between GECB and UCM board
CAN communication fault between GECB  Check CAN line between GECB and UCM board
and UCM board (UCM-TYP=2)

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> No RLV/ABL Event number:0255

An error occurred during releveling on a system with EN-required UCM. Further relevel runs will be
prevented at the floor where the problem occurred. Relevel runs will be re-enabled when the car moves to
another floor (UCM-TYP=3)
<M> <1> <2> <1> <GO ON> EEQF Active Event number:0126
Detected Earthquake Flash from external system
<M> <1> <2> <1> <GO ON> EQOR > Time Event number:0127
EQO restart condition active, but not arrived to the nearest floor within 4 minute 10 sec.
<M> <1> <2> <1> <GO ON> EQOR Hi-gal Event number:0128
EQO restart condition active with high-gal, but not run to the nearest floor within 10 sec.
<M> <1> <2> <1> <GO ON> EQAR Start Event number:0129
Started EQAR after EQO operation with just low-gal active
<M> <1> <2> <1> <GO ON> EQAR Abort Event number:0130
EQAR aborted by causes like EFO or EFS active, PFO active, other earthquake sensor active except for
low-gal, disconnected remote service under defined condition which EQAR allowed with remote service
connection (EQAR-O)
<M> <1> <2> <1> <GO ON> EQAR Fail Event number:0131
EQAR start was not permitted by drive for 60 sec after completion EQO general operation.
<M> <1> <2> <1> <GO ON> EQAR OK Event number:0132

Allowed to return to normal operation after completion of temporary serviceable check thru floor-to-floor,
top to bottom and bottom-to-floor running.
<M> <1> <2> <1> <GO ON> EQAR > Time Event number:0133
No maintenance since EQAR for defined time (EqrTrg-T)
<M> <1> <2> <1> <GO ON> OpMode EQO Event number:0134
Earthquake is occurred (EqoAlarm)

Date : 2013-06-17
BERLIN GECB
3.2.4 Failures related to SHUT DOWN

<M> <1> <2> <1> <GO ON> Shutdown “blinking message”
Error leading to a shut down
The drive reports a Shutdown  See event logging of Drive
 check CAN-wiring
CAN-Communication not working
 check CAN-LEDs
<M> <1> <2> <1> <GO ON> DrvShutdown Event number:0218

The drive is shut down
The drive reports a Shutdown  See event logging of Drive
 check CAN-LEDs
CAN-Communication not working
 check CAN-wiring
3.2.5 Failures related to REMOTE SERIAL LINK

<M> <1> <2> <1> <GO ON> Adr-Check/TCI-Check “blinking message”
The programmed address is to be checked
Some RSL I/Os have to be programmed to a  Set I/O 691 to a valid address
valid address and are not allowed to be set to TCI(691)
00-0 or 01-0. Currently only one I/O is
checked: 691 – TCI
<M> <1> <2> <1> <GO ON> RSL Adr Chk Event number:0230
Check the programmed RSL address
Some RSL I/Os have to be programmed to a  Set I/O 691 to a valid address
valid address and are not allowed to be set to related setup: TCI(691)
00-0 or 01-0. Currently only one I/O is
checked: 691 – TCI
<M> <1> <2> <1> <GO ON> RSL parity Event number:0400
Two remote stations with the same address are connected to the same link
Wrong connection  Check the RS connections

Date : 2013-06-17
BERLIN GECB
Failures related to REMOTE SERIAL LINK (continued)
<M> <1> <2> <1> <GO ON> RSL sync Event number:0401
Synchronization lost on remote serial link
Shortcut on the link  Check whether there is a shortcut on the link
Line terminator is defective  Change the line terminator
<M> <1> <2> <1> <GO ON> RSL reinit Event number:0402
RSL reinitialized
RSL driver has reported a problem  Wait RSL reinitialization
<M> <1> <2> <1> <GO ON> RSL Fail Event number:0403
RSL failed during application
RSL driver does not run anymore  Wait, software has been restarted
<M> <1> <2> <1> <GO ON> RSL Hrtbeat Event number:0404
RSL failed during application
Application does not run anymore  Wait, software has been restarted
<M> <1> <2> <1> <GO ON> RSL Board Event number:0405
RSL board mismatch
RSL board mismatch  Check the RSL board
<M> <1> <2> <1> <GO ON> Group RSL Event number:0406
Group RSL has failed
Group RSL has failed  Check the Group Link
<M> <1> <2> <1> <GO ON> CR-FSO Flt Event number:0275
Physical address of additional front PRS input for COR rescue is invalid or abnormally CR-OPT
detected at the inter-floor or the unnecessary landing. CR_FSO
<M> <1> <2> <1> <GO ON> CR-RSO Flt Event number:0276
Physical address of additional rear PRS input for COR rescue is invalid or abnormally CR-OPT
detected at the inter-floor or the unnecessary landing. CR_RSO
<M> <1> <2> <1> <GO ON> SameREM-ID Blinking message

Two OAD’s have been detected with the same address dip switch setting.

Date : 2013-06-17
BERLIN GECB
3.2.6 Failures related to the DRIVE

<M> <1> <2> <1> <GO ON> OpMode NAV Event number:0100
Operational control system is not available due to drive fault (e.g. drive-fault (NR). This mode is also active
after INS before the COR starts
The drive reports a fault  See event logging of Drive
The inputs signals 1LV, 2LV on drive are
 Check the input signals on Drive
missing
Limit switches 1LS and 2LS are active at the  Check power supply of the position reference
same time. system.
Switch from TCI/ERO to NORMAL  Switch to TCI/ERO at the door zone
<M> <1> <2> <1> <GO ON> PowerSave “Blinking message”:0233

Power save mode
The drive package has been powered on  related setup: PDR-D
<M> <1> <2> <1> <GO ON> DrvStartErr Event number:0219

Error during drive start
Error occurred during drive start  See event logging of Drive
<M> <1> <2> <1> <GO ON> DrvService Event number:0220

“Request for Service” (REM) for drive
REM info requested from drive  See event logging of the Drive
<M> <1> <2> <1> <GO ON> DrvEndRun Event number:0224

Drive did not end the run.
<M> <1> <2> <1> <GO ON> 110VacOffOn Event number:0227

110VAC died and came back before complete power down
<M> <1> <2> <1> <GO ON> DrvPrepErr Event number:0213

PrepareToRun expected from Drive
 PrepareToRun expected from Drive  Check the event logging of the drive
(e.g. missing load weighing information for
ABL)

Date : 2013-06-17
BERLIN GECB
Failures related to the DRIVE (continued)
<M> <1> <2> <1> <GO ON> Event number:0214

Drive stuck in PrepareToRun
<M> <1> <2> <1> <GO ON> DrvStuckRtr Event number:0215

Drive stuck in Ready To Run (no ABL)
 Drive stuck in Ready To Run  Check the event logging of the drive
<M> <1> <2> <1> <GO ON> DrvBrakeErr Event number:0216

Brake not lifted
 Brake not lifted  Check the brake
<M> <1> <2> <1> <GO ON> DrvCreepErr Event number:0217

Drive creep time too long
 Drive Creep time too long  Check the drive creep time setting
<M> <1> <2> <1> <GO ON> Drv SC Err Event number:0231
Drive Speed Check signal did not toggle on the run
 Indicates that ADO is enabled and the
conditions were met to begin an ADO run, but
 Check CAN bus connection (EN-ADO=1)
the DriveSpeedCheck signal did not toggle on
this run
<M> <1> <2> <1> <GO ON> DBSS Fault Blinking message
One of the following faults occurred during DCS: OTS, PLS, MCLS, SKL, MPD, J, LS-Fault, OVF10-Fault
<M> <1> <2> <1> <GO ON> EncoAdjust Blinking message

Evolux: Encoder Adjustment of Evolux drive -> Finishes automatically within 30 s, no action required

Date : 2013-06-17
BERLIN GECB
Failures related to the DRIVE (continued)
<M> <1> <2> <1> <GO ON> BTI NG 3rd Event number:0271
BTI result is no good at every 3rd trial.
<M> <1> <2> <1> <GO ON> BTI OK 3rd Event number:0272
BTI result is good at 3rd trial.
<M> <1> <2> <1> <GO ON> BTI Fault Event number:0271
BTI is not available or aborted.
3.2.7 Failures related to LOAD WEIGHING

<M> <1> <2> <1> <GO ON> LwssService Event number:0602
“Request For Service” (REM) from LWSS
RFS requested from LWSS  See LWSS event logging for reason
<M> <1> <2> <1> <GO ON> DrvOverHeat “Blinking message”:0251

Drive overheat signal is received
When the drive overheat signal is received  Check GDCB events
from Drive thru CAN bus.
<M> <1> <2> <1> <GO ON> OLD > 30s Event number:0114
The elevator is overloaded for more than 30 seconds.
<M> <1> <2> <1> <GO ON> LNS > 30s Event number:0115
The elevator is full for more than 30 seconds.

Date : 2013-06-17
BERLIN GECB
3.2.8 Failures related to RESCUE
<M> <1> <2> <1> <GO ON> 0701 SP missing F

Node Guarding does not detect the SP at the  Check CAN_OK LED at SP
CAN bus.  Check CAN wiring between GECBII & SP
<M> <1> <2> <1> <GO ON> 0702 BCB missing F

Node Guarding does not detect the BCB at  Check CAN_OK LED at BCB_II
the CAN bus.  Check CAN wiring between GECBII & BCB_II
<M> <1> <2> <1> <GO ON> 0703 BcbIoFail F

The states of inputs were not received every
second or the output commands were not  CAN bus overload? Defect BCB_II?
acknowledged.
<M> <1> <2> <1> <GO ON> 0704 BcbHwFail F

The BCB shows an EEPROM error.  Exchange BCB_II
<M> <1> <2> <1> <GO ON> 0705 BcbSwFail F

The BCB published a task timing problem.  Exchange BCB_II
<M> <1> <2> <1> <GO ON> 0706 EncoderFail F

The rescue encoder generates no signals  Check rescue encoder wiring
during a normal run.  Replace rescue encoder or GECBII_II

Date : 2013-06-17
BERLIN GECB
Failures related to Rescue (continued)
<M> <1> <2> <1> <GO ON> 0707 OCB fail F

The OCB auxiliary contacts are wired  Check wiring to OCB
incorrectly.  Check OCB; Check GECBII_II inputs
<M> <1> <2> <1> <GO ON> 0708 Overspeed W

The measured rescue encoder speed is 15%
faster than the nominal speed. The OS  Reset OS contact
contact or the safeties could be activated.  Check Encoder / Speed parameter
MRO is prevented.
<M> <1> <2> <1> <GO ON> 0710 No Battery F

The BCB misses the rescue battery  Check RPS / battery
<M> <1> <2> <1> <GO ON> 0711 BatTempErr W

The BCB indicates that the battery cannot be
charged, because the temperature is out of  Check battery temperature sensor
range
<M> <1> <2> <1> <GO ON> 0712 BatFault F

The BCB indicates a battery charge failure or
 Replace battery
a defect battery.
<M> <1> <2> <1> <GO ON> 0713 NoBatSignal F

The BCB has not charge unit signals. It could
be defect BCB or a missing charge power  Replace BCB_II
supply.

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> 0714 Low Battery I

The battery voltage is to low for ARO or MRO
 Charge battery or replace it
with drive.
<M> <1> <2> <1> <GO ON> 0715 BatCharged I

The BCB indicates a fully charged battery.
<M> <1> <2> <1> <GO ON> 0716 BatPower I

The BCB is powered by battery, caused by lost main power supply
<M> <1> <2> <1> <GO ON> 0717 NormalPower I

The BCB operates by the main power supply.
<M> <1> <2> <1> <GO ON> 0719 No3runNoAro I

The main power is lost, but there where less than 3 runs before power fail and after ERO or after operating
the OCB. These 3 runs are needed to execute ARO.
<M> <1> <2> <1> <GO ON> 0720 AroStarted I

ARO were initialized
<M> <1> <2> <1> <GO ON> 0721 AroAborted W

The OCSS ARO mode was aborted (e.g. by  If no other event was additional logged (as ARO
INS, timeout, invalid position, drive abort indicator), the failure must be found in the
shutdown). drive (shutdown).
<M> <1> <2> <1> <GO ON> 0722 AroFinished I

ARO sequence was finished.
<M> <1> <2> <1> <GO ON> 0723 AroNoDrive F

Drive does not communicate at the beginning
 Check wiring between drive / RR relays / BCB_II
of ARO.
<M> <1> <2> <1> <GO ON> 0724 AroTimeout W

ARO didn’t reach the target and opened the door during 5 minutes.

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> 0725 NoPreferDir F

 Check CAN connection to the drive
ARO or MRO: Drive did not send its preferred
 Check if drive is powered by battery
direction.
 Check drive events
<M> <1> <2> <1> <GO ON> 0726 BothDirFail F

MRO with drive: the car didn’t move / both  Check rescue encoder & drive
directions tested.  Check Drive events
<M> <1> <2> <1> <GO ON> 0727 DrvLineFail W

The drive indicates a line failure.
<M> <1> <2> <1> <GO ON> 0728 /RRI_IN F

The read back contacts of the RR relays were missed during ARO or MRO
In case of OVFR2A-406 drive without MRO-BL ignore this event because it doesn’t mean an error.
<M> <1> <2> <1> <GO ON> 0729 /ARO_IN F

The read back contacts of the ARO relays were missed during ARO or MRO.
<M> <1> <2> <1> <GO ON> 0730 MroWithDrv I

MRO with drive were started.
<M> <1> <2> <1> <GO ON> 0731 Mro w/o Drv I
MRO without drive were started.
<M> <1> <2> <1> <GO ON> 0614 PRBB BatLow W

The battery of the PRBB board is weak: During PowerOff, the battery only provides power for less than 10
seconds (EN-PRBB=1).
<M> <1> <2> <1> <GO ON> 0626 DeepBattery F

Evolux: Deep Discharge Protection switched off the OCB to protect the batteries (DRV-TYP)
<M> <1> <2> <1> <GO ON> 0627 LowBat wait F

Evolux: Enforced Battery Charging (DRV_TYP)

Date : 2013-06-17
BERLIN GECB
<M> <1> <2> <1> <GO ON> 0628 NoPowerWait F

Evolux: BatRun-T expired during blackout (DRV-TYP, BatRun-T)
<M> <1> <2> <1> <GO ON> DeepBat Blinking message

Evolux: Deep Discharge Protection is going to switch off the OCB to protect the batteries (DRV-TYP)
<M> <1> <2> <1> <GO ON> LowBatWait Blinking message

Evolux: Enforced Battery Charging  Resumes normal operation automatically after 30 min (restarted by
every blackout), no action required (DRV-TYP)
<M> <1> <2> <1> <GO ON> 0603 Aro Service W

The ARO subsystem (modified SPBC_III) requested “Request For Service” (REM). See ARO subsystem’s
event logging for reason.
<M> <1> <2> <1> <GO ON> NoPowrWait Blinking message

Evolux: BatRun-T expired during blackout:  Resumes normal operation automatically DRV-TYP
when mains returns BatRun-T

Date : 2013-06-17
BERLIN GECB
3.2.9 Information for ENGINEERING ONLY

3.2.9.1 GECB information
<M> <1> <2> <1> <GO ON>
Wrong software run and communication
Dummy task has not been called within timeout. Software has
Task Timing Event number: 0000
been restarted.
watchdog circuit on GECBII was triggered. Software has been
SW Reset Event number: 0001
restarted.
Illegal Int illegal interrupt was executed Event number: 0002
CanTxFull CAN messages cannot be sent Event number: 0003
CanBusOff CAN communication has been restarted Event number: 0004
StackCheck Stack Violation was detected. Software has been restarted. Event number: 0006
SCN Error Wrong software, order new SW with correct part number Event number: 0007
Internal software timers have not been updated correctly.
TimerSync Event number: 0008
Software has been restarted.
Application software doesn't run properly. Software has been
Task Fail Event number: 0009
restarted.
McbCommErr No CAN connection to the drive Event number: 0010
SpbCommErr No CAN connection to the SPBC_II Event number: 0011
Power On Board has been powered on Event number: 0012
Event Fail Event number: 0013
Power OffOn Short Failure of PowerSupply Event number: 0014
S/W Restart Reset with unknown reason Event number: 0016
Trace Error Bad value in the event Trace Control buffer Event number: 0017
Different addresses found for “mirrored I/Os” (e.g. IO0032 and
Bad E2P Event number: 0018
IO3000)  Check all level- and opening-related I/Os
MissedLvint lv1 and lv2 edge was missed Event number: 0019
RemoteReset System was reset by Elite Service expert Event number: 0020
Time Adjust Time was changed using SVT function Event number: 0021
Time Summer Time was adjusted for summer time Event number: 0022
Time Winter Time was adjusted for winter time Event number: 0023
Time NotSet Time has not yet been set Event number: 0024
ExternReset The external watchdog caused a reset Event number: 0025
Time NmsAdj Time was adjusted by NMS Event number: 0026
PowerReturn Power returned after ARO Event number: 0027
CcanSndFail Sending car bus CAN message failed Event number: 0028
CcanPubFail Publishing car bus CAN message failed Event number: 0029
CcanError Disturbances on the car CAN bus have been detected.
Event number: 0030
 Check termination, wiring, shielding

Date : 2013-06-17
BERLIN GECB
GECB information (continued)
<M> <1> <2> <1> <GO ON>

Wrong software run and communication
GcanTxFull Group bus CAN messages cannot be sent Event number: 0031
GcanBusOff Group bus CAN communication failure Event number: 0032
GcanSndFail Sending group bus CAN message failed Event number: 0033
GcanPubFail Publishing group bus CAN message failed Event number: 0034
GcanError Disturbances on the group CAN bus have been detected.
Event number: 0035
 Check termination, wiring, shielding
GwCommErr Gateway communication failure (related setup: REM-
Event number: 0036
TYP=6,7,8)
Time Fault The real time clock was corrupted and has now been reset to
01.01.2004.
Event number: 0037
 Use M-1-3-8-1 to set the correct date/time (OFT-A
required)
Time Nms>1h Time synchronization between NMS and Controller greater
Event number: 0038
than 1h
ZKIP Div0 Numerical division by 0 during ZKIP authentication Event number: 0039
<M> <1> <2> <1> <GO ON>

Group function related failures
RNG1 msg data error on Duplex/Triplex ring Event number: 0500
RNG1 time no ring messages received from other car for a specific time Event number: 0501
RNG1 sio framing error on Duplex/Triplex ring Event number: 0502
RNG1 tx ring messages couldn’t be sent in an appropriate time Event number: 0503
No messages are received within a timeout, and NO BREAK
RNG1 rxOff Event number: 0504
is detected.
RNG1 reset Reinitializing RING Service (stm_ring_run expired) Event number: 0505
DES offline DES is not present Event number: 0506
GCB offline no GCB is present Event number: 0507
For Compass, the primary GCB has failed and the secondary
GCB fail Event number: 0508
GCB is used.  Check GCB boards

Date : 2013-06-17
BERLIN GECB
3.3 Elevator failures during installation or maintenance

3.3.1 Failures related to wrong HARDWARE
<M> <1> <2> <1> <GO ON> WrongBoard “blinking message”
The software cannot identify the board
Wrong GECBII  Replace GECBII
<M> <1> <2> <1> <GO ON> GCB fail “blinking message”
For Compass, the primary GCB has failed and the secondary GCB is used.
For Compass, the primary GCB has failed
 Check GCB boards
and the secondary GCB is used.
3.3.2 Failures related to PARAMETER SETUP

<M> <1> <2> <1> <GO ON> SP:en.Feat! Event number 0122
One of the following features is programmed in the E2PROM but not yet enabled by Service Panel:
One of the following features is programmed  Use “Startup-Enable Features” to activate these
in the E2PROM but not yet enabled by features
Service Panel: EFO-POS
EFO EPO-POS
EPO IO1000 CLR
CLR HBP-POS
HBP
3.3.3 Failures related to SOFTWARE UPDATE

<M> <1> <2> <1> <GO ON> S/W Changed Event number:0604
Informational event that new software was installed. The events are automatically cleared. No action necessary.
<M> <1> <2> <1> <GO ON> Update S/W! Event number:0605
New subsystem software was installed that requires new GECB software.

Date : 2013-06-17
BERLIN GECB
Failures related to SOFTWARE UPDATE (CONTINUED)
<M> <1> <2> <1> <GO ON> OmuPresent “blinking message”

A wrong procedure was used to plug the OMU.
 Follow the steps:
A wrong procedure was used to plug the
 While the controller is on, switch TCI off
OMU. It must be ensured that TCI is
(NOR or ERO)
switched OFF while the controller is powered
 switch the controller off
down:
 switch the controller on
3.3.4 Failures related to LEARN RUN

<M> <1> <2> <1> <GO ON> Learn Run “blinking message”
Learn run
The drive package is performing its Learn  Wait until the learn run is completed.
Run to learn the hoistway situation
The drive package is adjusting the encoder.
3.3.5 Failures related to NORMAL RUN

<M> <1> <2> <1> <GO ON> start DCS! “blinking message”
The door check sequence is to be performed.
Normal operation is not allowed until the Door  Enter M-1-3-5 to start the DCS!
Check Sequence has been completed
successfully.
The DCS is required again if one of the
parameters TOP or BOTTOM is changed.
<M> <1> <2> <1> <GO ON> DrvPosInval Event number:0200

Drive set the position invalid, resulting in COR run
<M> <1> <2> <1> <GO ON> Correct.Run Event number:0201

The correction run was performed
A correction run was performed (e.g. after
 Wait until the correction is finished
INS, NAV)

Date : 2013-06-17
BERLIN GECB
Failures related to NORMAL RUN (continued)
<M> <1> <2> <1> <GO ON> TCI/ERO on Event number:0204

TCI or ERO has been switched on, or the RSL 30VDC is dead.
<M> <1> <2> <1> <GO ON> COR Rescue Blinking message
Notifying the operation status that COR rescue is under operation (CR-OPT)
<M> <1> <2> <1> <GO ON> COR > 2min Event number:0116
The elevator is attempting to correct position for more than 2 minutes.
<M> <1> <2> <1> <GO ON> INI > 2min Event number:0117
The elevator is initializing after a power on for more than 2 minutes.
<M> <1> <2> <1> <GO ON> PRK > 2min Event number:0118
The elevator is performing a park run for more than 2 minutes.
<M> <1> <2> <1> <GO ON> WCO > 5min Event number:0119
The elevator is performing wildcar operation for more than 5 minutes.
<M> <1> <2> <1> <GO ON> NOR > 5min Event number:0120
The elevator is in NOR operation for more than 5 minutes. Could be the result of a stuck reversal device.
<M> <1> <2> <1> <GO ON> OpMode ARO Event number:0121
Automatic Rescue Operation was activated due to a power failure or via OFT test menu.
<M> <1> <2> <1> <GO ON> NAV > 30s Event number:0123
The elevator is in NAV mode for more than 30 seconds. This event is only logged when the system is in
NAV mode and no OOS Blockage is detected for 30 seconds..
<M> <1> <2> <1> <GO ON> Event RFS Event number:0135
RfsEvU-T ; RfsEvT-T ; RfsEvC-T ;
Selected events (max: 3) by SVT is detected for pre-determined time.
RfsEvxGr ; RfsEvxId ; RfsEvOpx
<M> <1> <2> <1> <GO ON> DCS run Blinking message
Additional PRS for COR rescue was not properly detected and required to execute DCS run for adaptation
of additional PRS installed status (CR-OPT)
<M> <1> <2> <1> <GO ON> No DCS run Event number:0316
A DCS run must be performed.
A DCS run must be performed.  See description for blinking message 'start DCS!'

Date : 2013-06-17
BERLIN GECB
4 Appendix
4.1 Service Panel
4.1.1 Key lock
Note:
If the SP is not used for 45 minutes, the keypad except button BRB1 is locked so that
the SP is protected from unauthorized use.
This state is indicated by the symbol on the display.
To unlock the keypad, the softkeys 1 + 3 must be simultaneously pushed for 2 seconds.

Date : 2013-06-17
BERLIN GECB
4.1.2 Graphical symbol overview
4.1.2.1 Status Display

Symbol Text Meaning
Battery is charging. Rescue is possible.
Battery is fully charged. Rescue is possible.
Battery fault. Rescue is not possible. Check Battery and BCB.
Service notification for REM/Gateway is on
Keylock is active. All Service Panel buttons except BRB1 (RESCUE)

are locked and must be unlocked manually: Simultaneously press
Softkey1 and Softkey3 for 2 seconds.

Date : 2013-06-17
BERLIN GECB
4.1.2.2 Instructions for User Actions
Symbol Text Meaning
Open! Manually open the door to rescue passengers
Close Door! Close the doors!
OCB off! Switch off the power supply (OCB)
OCB on! Switch on the power supply (OCB)
NORERO! Switch to ERO
ERONOR! Switch to NOR
UIB! Switch to UIB (Up Inspection Button)
DIB! Switch to DIB (Down Inspection Button)
CCBL! Push SP button CCBL (Car Call to Bottom Landing)
CCTL! Push SP button CCTL (Car Call to Top Landing)
Push SP buttons UP or DOWN
BRB1+BRB2! Simultaneously push SP button BRB1 and turn keyswitch BRB2
100%=630kg Fill the car with 100% of duty load, which is 630kg.
Now=80kg Currently the load weighing device measures 80kg.
Menu
Perform all Service Panel functions of the menu CONSTRUCTION
Construct!
Startup:
Perform the Service Panel function as indicated.
Enable ADO!
Startup:
Perform the Service Panel function as indicated.
Enable RLV!

Date : 2013-06-17
BERLIN GECB
4.1.2.3 Confirmations for Automatic Actions
Symbol Text Meaning

OS (1RRD)
Confirm to test Remote Governor Reset
Test Now?
OS (1RTD)
Confirm to test Remote Governor Tripping (car)
Test Now?
OS (3RTD)
Confirm to test Remote Governor Tripping (counterweight)
Test Now?
Reset now? Confirm to reset the Governor
1RTD now? Confirm to trip the Car Governor
Start? Confirm to start a run downwards
Start? Confirm to start a run upwards
Start? Confirm to start several runs in different directions
Find
Confirm to move down to the lowest landing.
Bottom?
Find Confirm to move to the lowest landing. Because 1LS is active, the car
Bottom? first moves up out of 1LS and then moves down to the lowest landing.
Car
Confirm to run the car onto the buffer with full speed.
On Buffer?
+2 mm Adjust the floor level by pressing the buttons and .

Date : 2013-06-17
BERLIN GECB
4.1.2.4 Status Confirmations
Symbol Text Meaning
At Bottom? Confirm that the car is at bottom landing
At Top? Confirm that the car is at top landing
Empty? Confirm that no person is inside the car
Closed? Confirm that the doors are closed
Check Load?
Confirm to manually check the load at bottom floor
100%
Confirm that a platform is installed which is heavier than the
Platform?
counterweight frame.
Car? Confirm that the counterweight is heavier than the car.
4.1.2.5 Status Information
Symbol Text Meaning
Door is closing
Car is moving down
Car is moving up
Brake is closed
Brake is opened
Drive is learning the motor direction. The car will move a few
millimeters during that process.

Date : 2013-06-17
BERLIN GECB
4.1.2.6 Alerts
Symbol Text Meaning
m/s(up) Over speed was detected in up direction
m/s(down) Over speed was detected in down direction
Battery Temperature Fault
Power supply is missing. System is powered by battery.
Battery fault
SERVICE! System Blocked. Call Service Personnel
4.1.2.7 Other Symbols
Symbol Text Meaning
Refer to instruction manual
Wait Please wait until current process has finished
Stop your current action (e.g. Release all buttons)
CAN communication is lost. Therefore Rescue operation is not

possible.
CAN-Fault
In order to reestablish CAN communication, unplug P11 on GECBII_II.
Depending on the cause of the fault, this might enable Rescue again.

Date : 2013-06-17
BERLIN GECB
4.2 GECB-LV interfaces

Date : 2013-06-17
BERLIN GECB
4.3 GECB Setup

4.3.1 Setup allowed Mask

Date : 2013-06-17
BERLIN GECB
4.3.2 Enable Mask
Note:
The R-Bit is not necessary. The handling of Short Landings is completely done by the
drive

Date : 2013-06-17
BERLIN GECB
4.3.3 Cut call Mask

Date : 2013-06-17
BERLIN GECB
4.3.4 Card Reader Mask

Date : 2013-06-17
BERLIN GECB
4.3.5 Position Indicator setup
Code Symbol Code Symbol Code Symbol Code Symbol

0 0 10 (blank) 20 J (*) 30 T (*)
1 1 11 A 21 K (*) 31 U
2 2 12 B (*) 22 L 32 V (*)
3 3 13 C 23 M (*) 33 W (*)
4 4 14 D (*) 24 N (*) 34 X (*)
5 5 15 E 25 O 35 Y (*)
6 6 16 F 26 P 36 Z (*)
7 7 17 G (*) 27 Q (*) 37 -
8 8 18 H 28 R (*) 38 *
9 9 19 I (*) 29 S 39 all segments
(*) for 16-segment position indicator and ELD only!

Date : 2013-06-17
BERLIN GECB
4.3.6 ELD setup

Date : 2013-06-17
BERLIN GECB
4.3.7 Floor Display

Date : 2013-06-17
BERLIN GECB
4.3.8 Edit Display

Date : 2013-06-17
BERLIN GECB
4.3.9 Store Display

Date : 2013-06-17
BERLIN GECB
4.3.10 Default Display
No. ENG GER ITA

0 LOBBY ERDGESCHOSS TERRANO
1 BASEMENT KELLER SOTTERRANEO
2 PENTHOUSE DACHTERASSE ATTICO
List of Default Messages
3 FLOOR ETAGE PIANO

4 RECEPTION EMPFANG RICEZIONE
5 EXIT AUSGANG USCITA
6 GARAGE TIEFGARAGE POSTEGGIO
7 SECRETARY SEKTRETARIAT SEGRETERIA
8 RESTAURANT RESTAURANT RISTORANTE
9 CAFETERIA KAFFEESTUBE CAFFETERIA
10 GARAGE PARKHAUS POSTEGGIO
11 POOL SCHWIMMHALLE PISCINA
12 SAUNA SAUNA SAUNA
13 DOCTOR ARZT DOTTORE
14 0 123 456 789 0 123 456 789 0 123 456 789
15 : . () <> / -, & ’ : . () <> / - , & ‘ : . () <> / - , & ‘
16 ABCD EFGH IJKL ABCD EFGH IJKL ABCD EFGH IJKL
17 MNOP QRST UVWXYZ MNOP QRST UVWXYZ MNOP QRST UVWXYZ
18 ÄÁÅÇØÖÆ ÄÁÅÇØÖÆ ÄÁÅÇØÖÆ
19 empty string

Date : 2013-06-17
BERLIN GECB
4.3.11 Rescue Menu

Date : 2013-06-17
BERLIN GECB
4.4 Remote Stations

4.4.1 RS functionality test

Date : 2013-06-17
BERLIN GECB
4.4.2 Search I/O address


Otis Gecb LV

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Otis Gecb LV

Uploaded by

Copyright:

Available Formats

OTIS - SSI GECB-LV Dwg: GAA25PJ_ADT

FSM Advanced diagnostics and trouble shooting

Software Version: GECB_II: GAA30780EAH

Date Author Page Comment

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

4.4.2 Search I/O address ........................................................................................................................... 64

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

1.1 Step 1: elevator status check

1.2 Step 2: visual check: Service Panel

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

1.3 Step 3: failure group selection

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

1.4 Step 4: failure handling using OFT

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

Battery Battery is charging. Rescue is possible.

Service Service notification for Gateway is ON

Trapped The Trapped Passenger Alarm (TPA) button was pushed.

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

2.2 Service Panel key description

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

2.3 Service Panel: buttons

Button Name Description

DDO Disable Door Operation This button disables door operation.

Up Within the menu, this button moves the menu selection up

END End Only applicable for GCS222MRL, not for GCS222LVA:

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

3 Failures handling using OFT

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

3.1 Elevator is blocked

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

Failures related to the CAR AND HOISTWAY DOOR (continued)

<M> <1> <2> <1> <GO ON> /DFC in FR Event number:0211

<M> <1> <2> <1> <GO ON> /DFC in SR Event number:0212

<M> <1> <2> <1> <GO ON> /DW in FR Event number:0237

<M> <1> <2> <1> <GO ON> /DW in SR Event number:0238

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

Failures related to the car and hoistway door (continued)

<M> <1> <2> <1> <GO ON> DCL in [ ] Event number:0301

<M> <1> <2> <1> <GO ON> DS bypass Event number:0107

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting

3.1.2 Failures related to the SAFETY CHAIN

<M> <1> <2> <1> <GO ON> 2SE-Fault “blinking message”:0244

<M> <1> <2> <1> <GO ON> /ES in FR Event number:0202

<M> <1> <2> <1> <GO ON> /ES in SR Event number:0203

<M> <1> <2> <1> <GO ON> DBP-Fault! “blinking message”:0303

Otis Elevator Company Proprietary Information

FSM Advanced diagnostics and trouble shooting