FSD GAA30780EAN Feature and Set Up Description - 2015!05!28

No.
: GAA30780EAN_FSD
OTIS Software Basic Data SCN: GAA30780EAN
Page: 1 / 196
Engineering Center GCS – GECB Date: 2015-04-22
Berlin
Feature Setup Description
GCS - GECB
Authorization Date D1 2015-03-25
Running on PCB GCA26800LC (GECB-EN) or higher

GCA26800MD (GECB_II) or higher
GBA26800NK (LCB_IIC) or higher
KBA26800ABG (Asian-IO) or higher
DAA26800AY (GECB-AP) or higher
GCA26800NR (GECB_LV) or higher
Software Version GAA30780EAN
Document Revision V 1.1
Date SCN Author Comment

2015-03-25 GAA30780EAN A. Pfeffer Original document
2015-04-22 GAA30780EAN A. Pfeffer Expanded OOLxx description for EFO
Copyright 2015, OTIS GmbH Berlin

No part of this document may be copied or reproduced in any form or by any means without the prior written consent of OTIS GmbH.
No.: GAA30780EAN_FSD
Page: 2 / 196
Berlin
Table of Contents
1 Revision History............................................................................................................6
2 Operational Modes...................................................................................................... 11
2.1 ACP - Anti-Crime Protection .............................................................................................................. 11
2.2 BLC - Better Living Circuit ................................................................................................................. 12
2.3 ANS - Anti-Nuisance Operation ......................................................................................................... 13
2.4 ARO - Automatic Rescue Operation.................................................................................................. 14
2.5 ATT - Attendant Operation ................................................................................................................. 16
2.6 Alternative Simplex Zone Parking ..................................................................................................... 18
2.7 CCB - Car Calls Behind....................................................................................................................... 20
2.8 CFT - Cafeteria Position ..................................................................................................................... 20
2.9 CGS - Buzzer control for Detecting Landing Door Opened ........................................................... 20
2.10 CK, CBC - Car Button Cancel ............................................................................................................. 21
2.11 Compass - Destination Entry ............................................................................................................. 22
2.12 COR Rescue operation ....................................................................................................................... 23
2.13 CTL,CBL - Car Calls to Terminal Landings ...................................................................................... 27
2.14 DBF - Drive / Brake Fault .................................................................................................................... 29
2.15 DHB - Door Hold Button ..................................................................................................................... 30
2.16 EQO - Earthquake Operation ............................................................................................................. 31
2.17 EFO according to EN81-73 ................................................................................................................. 39
2.18 EFO – Dynamic EFO............................................................................................................................ 41
2.19 EFO - Hong Kong Fire Alarm Home Landing ................................................................................... 43
2.20 EFS - Hong Kong Code for Fireman’s Lifts ...................................................................................... 43
2.21 EFS-TYPs ............................................................................................................................................. 44
2.22 EFS - Emergency Firemen Service without correction runs .......................................................... 45
2.23 EFS according EN81-72 ...................................................................................................................... 45
2.24 EFS with Safety Chain Bypass for Korea / Taiwan .......................................................................... 47
2.25 FCL - Full Collective with Car Call Priority Services for Korea ...................................................... 52
2.26 HAD - Hoistway Access Detection .................................................................................................... 52
2.27 HCC - Hall Call Cancel ........................................................................................................................ 52
2.28 PTC - Penthouse Control .................................................................................................................... 53
2.29 Stuck Hall Button Detection ............................................................................................................... 55
2.30 SHO - Shabat Operation ..................................................................................................................... 55
2.31 WDOB/WDCB - Wheel Chair DOB/DCB ............................................................................................. 57
2.32 Wheel Chair Service (WCS) ................................................................................................................ 58
2.33 Door Open Hold By Trunk Key (DH-Trunk)....................................................................................... 59
2.34 Position Recovery after Power Fail ................................................................................................... 60
3 Energy Saving ............................................................................................................. 61
3.1 Cut off Position Indicator during Parking Mode .............................................................................. 61
3.2 Door Power Save ................................................................................................................................. 61
3.3 Drive Power Save ................................................................................................................................ 62
3.4 LR - Car Light ....................................................................................................................................... 62
Page: 3 / 196
Berlin
3.5 RGEN - Regenerative mode display .................................................................................................. 62

4 Security Functions...................................................................................................... 65
4.1 Overview .............................................................................................................................................. 65
4.2 CRO - Car Call Card Reader Operation ............................................................................................. 65
4.3 HCRO - Hall Call Card Reader ............................................................................................................ 67
4.4 CCO - Car Call Cutoff .......................................................................................................................... 68
4.5 HCO - Hall Call Cutoff ......................................................................................................................... 68
4.6 CHCS - Cutoff Hall Call Switch .......................................................................................................... 68
4.7 EMS Security Options ......................................................................................................................... 69
4.8 Hong Kong Anti Burglar Operation ................................................................................................... 69
4.9 SAO - Car Security Access Operation .............................................................................................. 70
4.10 PET Operation ..................................................................................................................................... 73
5 Drive Related Setup .................................................................................................... 76
5.1 Drive OverHeat .................................................................................................................................... 76
5.2 ETS - Emergency Terminal Slowdown with Safety Switches (PX2.1=2) ....................................... 77
5.3 ETS - Emergency Terminal Slowdown with Reed Switches (PX2.1=4 or 5) .................................. 82
5.4 RPD-P2 - Low Cost Single Position Sensor ..................................................................................... 84
5.5 SMART Charger for “LVA Switch” .................................................................................................... 86
5.6 TPOS - Cyclic Parking......................................................................................................................... 87
5.7 UCM EN81 - Unintended Car Movement ........................................................................................... 89
5.8 UCM Korea - Unintended Car Movement (UCM-K) .......................................................................... 92
5.9 UCM Japan - Unintended Car Movement (UCM-JIS) ....................................................................... 98
5.10 6LS - Emulation via Software ........................................................................................................... 101
5.11 Alternate Profiles ............................................................................................................................... 103
6 Door Related Setup................................................................................................... 104
6.1 Generic Door Operator ..................................................................................................................... 104
6.2 DO-5 / AT120 ...................................................................................................................................... 115
6.3 Generic Door Operator (DO/DC RSL interface) .............................................................................. 117
6.4 SGS2 - Secondary Safety Gate Shoe for Korea ............................................................................. 119
6.5 Door Bypass ...................................................................................................................................... 119
6.6 Door Reversals after Power On ....................................................................................................... 120
7 Car related Setup ...................................................................................................... 121
7.1 CGS - Door Short Protection for Korea ........................................................................................... 121
7.2 CMG - Car Mounted Governor ......................................................................................................... 121
7.3 FAN - Fan Control for Asia ............................................................................................................... 122
7.4 Hong Kong Car Door Locks ............................................................................................................. 123
7.5 GECB: SO(Safe to Open) Signal for Japan ..................................................................................... 124
8 Group Related Setup ................................................................................................ 126
8.1 OTIS2000 Openings .......................................................................................................................... 126
8.2 Dummy Doors .................................................................................................................................... 127
8.3 DEK with RSL Encoded Interface .................................................................................................... 128
9 Hoistway Setup ......................................................................................................... 129
9.1 OHLOW/SHPIT - Reduced Hoistway................................................................................................ 129
Page: 4 / 196
Berlin
9.2 LOWPIT1 - Low Pit ............................................................................................................................ 131

10 Controller Related Setup .......................................................................................... 135
10.1 GCS222MRL ....................................................................................................................................... 135
10.2 GCS 222 LVA ..................................................................................................................................... 136
10.3 ACD with CSPB ................................................................................................................................. 140
11 Signal Devices .......................................................................................................... 141
11.1 CPI-11 - ELD Car Position Indicator ................................................................................................ 141
11.2 OOS - Out Of Service ........................................................................................................................ 141
11.3 CDI,HDI,CDL,HDL,CNG - Direction Indicator / Lantern / Gong ..................................................... 142
11.4 FMO - Fixture Maintenance Operation ............................................................................................ 144
11.5 REM Signals ....................................................................................................................................... 144
11.6 TRIC - Trip Counter ........................................................................................................................... 147
11.7 Voice Announcement for Handicapped Person for Korea ............................................................ 147
12 LW - Load Weighing ................................................................................................. 147
12.1 In Car Load Weighing via CAN Bus ................................................................................................. 147
12.2 Dead End Hitch Load Weighing via CAN Bus ................................................................................ 148
12.3 Discrete In Car Load Weighing via RS Inputs for CAN drives ...................................................... 148
12.4 Discrete Inputs for hydraulic ........................................................................................................... 149
12.5 Discrete Car Inputs for none CAN drives ....................................................................................... 149
12.6 Discrete Machineroom Inputs for none CAN drives ...................................................................... 150
12.7 Disable Overload (OLD) .................................................................................................................... 150
13 Inputs ......................................................................................................................... 151
13.1 1TH - Thermal contact 1 ................................................................................................................... 151
13.2 2TH - Thermal contact 2 ................................................................................................................... 151
13.3 HTS - Hall Temperature Sensor ....................................................................................................... 151
14 TBF - Time Based Features (Real Time Clock) ....................................................... 152
14.1 DST - Daylight Saving Time (Summertime/Wintertime) ................................................................ 152
14.2 NNR - Night Noise Reduction ........................................................................................................... 153
14.3 TFA - Time Based Feature Activation ............................................................................................. 153
15 Battery Backup Rescue ............................................................................................ 155
15.1 ARO (Automatic Rescue Operation) ............................................................................................... 155
15.2 MRO (Manual Rescue Operation) .................................................................................................... 160
16 Remote Elevator Inspection (REI) ........................................................................... 170
16.1 MEL – Manual Error Log Collection ................................................................................................ 170
16.2 REI Operation General (Manual REI) ............................................................................................... 170
16.3 Self-Trigger REI ................................................................................................................................. 181
16.4 Sequential REI ................................................................................................................................... 182
16.5 REI Test by SVT ................................................................................................................................. 182
16.6 REI Data Collection ........................................................................................................................... 183
17 Remote Elevator Monitoring (REM) ......................................................................... 192
17.1 REM6 Setup ....................................................................................................................................... 192
17.2 RFS Alarm .......................................................................................................................................... 192
Page: 5 / 196
Berlin
17.3 OOS Alarm ......................................................................................................................................... 195

18 Parameter and RSL IO management ....................................................................... 196
18.1 Adjusting Bad parameter ................................................................................................................. 196
Page: 6 / 196
Berlin
1 Revision History
Date Rev Author Comment

18-Jan-2001 V1.0 A. Gerwing first issue
14-Mar-2002 V 1.1 A. Gerwing RBU-1 added
V 1.2 M. Hoinkis HCB-Features added
7-Oct-2002 V1.3 H.-K. Spielbauer EQO added
Dec-2002 V 2.0 A. Pfeffer Document applicable for LCB2, TCB,
HCB, TCBC
May-2003 GAA30082CAC A. Pfeffer new AT25; EFS without COR; REM
signals; Direction lanterns added
Aug-2003 GAA30081AAE A. Pfeffer no changes
25-Sep-2003 GAA30084CAB A. Pfeffer no changes
M. Hoinkis SAC extended
A. Pfeffer SAC extended
A. Pfeffer EFS for EN81-72 added, clearer de-
scription for EN-HCRO
07-Sep-2004 GAA 30781 AAA M. Hoinkis added TCBC 30781 baseline
14-Dec-2004 GAA 30781 AAB M. Hoinkis no changes
2005-04-06 GAA 30780 AAA A. Pfeffer no changes for GECB
2005-04-14 GAA 30781 AAC M. Hoinkis TCBC: ACG for DO-5 / AT120
2005-07-21 GAA 30780 AAB A. Pfeffer Compass added for GECB
2005-08-04 GAA 30781 AAD M. Hoinkis Automatic Rescue Operation update
2005-08-16 GAA 30781 AAE M. Hoinkis add EQO-4, RSL load weighing
2005-09-02 GAA 30781 AAE M. Hoinkis add Taiwan EFS, DBF, 1TH, 2TH, HTS
2005-10-04 GAA 30781 AAE M. Hoinkis add AROL output for ARO
2005-10-20 GAA 30781 AAE M. Hoinkis add reduced hoistway / ARO update
2005-11-15 GAA 30781 AAE M. Hoinkis Dir. Ind. / ARO / EFS / corr.
2005-12-07 GAA 30781 AAE M. Hoinkis RFS reduction
2006-01-05 GAA 30781 AAE M. Hoinkis Taiwan EFS update
2006-02-22 GAA 30781 AAF M. Hoinkis HAD added / Taiwan EFS update
2006-10-27 GAA 30780 BAA M. Hoinkis EN-81-73 (EFO) added
2006-11-1 GAA 30780 BAA B. Braasch Op. Mode: Anti-Crime Protection
(ACP); Anti-Nuisance Operation (ANS);
Attendant Operation (ATT); Cafeteria
Position (CFT); Cancel Door Dwell
Time; Car Calls Behind; Car Calls to
Terminal Landings; added
Security: Car Call Cutoff; Hall Call
Cutoff; Cutoff Hall Call Switch; added
2006-11-9 H. Spielbauer EN 81-73 Flowchart
2007-01-03 GAA 30781 AAG M. Hoinkis EFS-TYP table added, DO/DC RSL
interface added
2007-01-08 GAA 30780 CAA B. Braasch Op. Mode: (ATT) new description ;
2007-04-03 GAA 30781 AAH M. Hoinkis ARO description extended
2007-04-04 GAA 30780 DAA A. Pfeffer no changes
2007-08-29 GP1 30780 DAA A. Pfeffer no changes
2007-04-20 GAA 30781 AAH M. Hoinkis REM signals: OOS / RFS / SPBF ex-
tended for TCBC
2007-05-02 M. Hoinkis LOSP: hint for HWY-TYP = 0
2007-05-23 M. Hoinkis REM OOS: 60 min suppression after
ERO removed
Page: 7 / 196
Berlin

2007-12-14 GAA30780DAB A. Pfeffer Added: Time Based Features; Hall Call
Cancel; Test Fixture
Revised: 1TH, 2TH, HTS, CCTL
2008-06-13 GAA30082DAC M. Hoinkis EFO: EFO-LOCK added; HAD & LCB_II
added
2008-06-30 GAA30082DAC M. Hoinkis EFO: EFO-LOCK & EN-BAK parameter
removed
2008-07-22 G1530780DAC A. Pfeffer Added Hong Kong Features: Homing
Floor (EFO), Fireman’s Lift (EFS), Car
Door Lock, Anti Burglar Operation.
2008-07-22 G1530780DAC A. Pfeffer Added Korean Fan Control, Door Short
Protection, One Sensor PRS, Voice
Anouncement, UCM
2008-07-22 G1530780DAC A. Pfeffer Added ETS
2008-09-25 G1530780DAC H. Spielbauer EN 81-73 Flowchart update
2008-11-12 G2330780DAC A. Pfeffer No changes
2008-12-04 GAA30780DAC A. Pfeffer Car Button Cancel (CK, CBC)
7ewriteten.
2009-04-17 A. Pfeffer GCS222MRL added
2009-05-05 GAA30780DAD M. Hoinkis Battery Backup Rescue added; RFS for
GECB
2009-06-08 G1330780DAE A. Pfeffer EN-CK expanded
2009-06-19 GAA30780DAE A. Pfeffer Release
2009-07-16 G1630780DAF H.-K. Spielbauer Application for GECB only
2009-09-08 GAA30780DAF A. Pfeffer No changes
2009-10-09 A. Pfeffer TRIC description added
2009-11-10 A. Pfeffer OPERAT=0 added for Compass
2009-12-10 G2130780DAG A. Pfeffer, Added Korean Features: Car Call Priori-
Kang DongHo ty , Cut Off Position Indicator during
PKS, Stuck Hall Button Detection,
Buzzer Control for Opened Landing
Door, ARO for GECB-EN
2010-01-21 S. Seelmann Generic Door Description added
2010-01-22 GAA30780DAG A. Pfeffer Sticky Brake Prevention added
Parameter DOL-D added for Generic
Door
2010-02-05 A. Pfeffer “Vector: 6LS Emulation” added
2010-02-18 G1330780DAH A. Pfeffer “Vector: Car Mounted Governor (CMG)”
added
2010-03-17 G1630780DAH A. Pfeffer “Cyclic Parking” modified
2010-03-17 G1630780DAH A. Pfeffer Chapter “Energy Saving” added;
“Cut Off Position Indicator during PKS”
moved to “Energy Saving”
2010-05-07 GAA30780DAH A. Pfeffer Release
2010-06-15 G1130780DAJ M. Hoinkis i/o’s AEFO, ASL, EFK, EFO explained
2010-10-26 GAA30780DAJ H.-K. Spielbauer Release
2011-01-04 G1130780EAA A.Pfeffer Added UCM EN81
2011-02-10 GAA30780EAA H.-K. Spielbauer Release
2011-04-06 GAA30780EAB A.Pfeffer Release
2011-05-09 G1130780EAC M. Hoinkis MRO_EB added

2011-05-18 G1430780EAC D. Cominelli Added ETSD with Reed Switches –
Page: 8 / 196
Berlin

ET_Px table still TBD
2011-06-27 G1730780EAC M. Hnida Added Low Pit
2011-07-20 G1730780EAC SG Cho Added option 2 for DS-CCB
Added WDOB/WDCB
2011-07-07 G1730780EAC DH Kang Added UCM fault clearing for Korea;
Added how to clear UCM fault by unin-
tended UCM-TYP =1;
Added EFS-TYP=12
2011-08-26 G2030780EAC A. Pfeffer Moved chapter DHB
2011-08-31 G2030780EAC M. Hnida Added blink messages “LOPIT cfg!”,
“KS-L fault”, and “APS fault” and errors
0619 HWY-TYP, 0334 KS-L fault, and
0335 APS fault
2011-10-24 G2530780EAC D. Cominelli Defined the ET_Px and ET_Sx inputs
as inverted, and describe the ETSD with
Reed Switch setup in table form.
2011-10-26 G2530780EAC A. Pfeffer - Renamed and Reordered chapters.
- Deleted EAR, CSP-5.
- Adapted setup table formatting of
ACP, ANS, ATT, CCB, CFT, CCO, HCO
- Added “OTIS2000 Openings” and
“Dummy Doors”.
- Revised DBF
2011-10-26 G2530780EAC A. Pfeffer Added Parameter Requirement for
UCM-EN81 Test
2011-10-28 GAA30780EAC D. Cominelli - Removed ET_Px table because will be
described in the startup routine docu-
ment.
2011-10-28 GAA30780EAC A. Pfeffer - Removed descriptions for other boards
than GECB.
2011-11-21 G1130780EAD M Hoinkis - 6.1.4 extension (hidden door setup)
- 6.5 Door Bypass LCB_IIC (new)
- 12.4-6 discrete LW for LCB_IIC (new)
2011-11-25 G1330780EAD M Hoinkis - Door setup extended for LCB_IIC
- 2.27 Pos recover added
- 6.6 Door rev. after power on added
2012-04-13 G2630780EAD A. Pfeffer - UCM3: UCM-EN81 Test via RSL
2012-04-13 G2630780EAD D. Cominelli Added Alternate Profiles section under
Drive-Related Setup.
2012-04-13 GAA30780EAD A. Pfeffer Release
2012-06-04 G1230780EAE SG Cho Adapted for JIS: 2.10 EN-CK, 2.26
HCC, 7.3 FAN
Added 2.6 Alternative Simplex Zone
Parking, 2.29 WCS, 12.7 Disable OLD,
16. REI, 17. REM
2012-06-04 G1230780EAE DH Kang Added 2.2 BLC, 2.30 DH-Trunk, 5.10
Drive OverHeat, 7.5 SO
2012-06-04 G1230780EAE GS Wang Added 2.15.2 EQO-5(Japan), 4.10 PET
operation
2012-08-14 G2230780EAE SG Cho Updated 2.14 DHB, 2.29 WCS, 4.10
PET Operation, 5.6 UCMK, 16.1 REI
Deleted 5.1 DHB
2012-09-11 GAA30780EAE DH Kang Added 5.10 UCM Japan
Updated 5.6 UCM Korea
Page: 9 / 196
Berlin

2012-10-10 GAA30780EAE H.-K. Spielbauer Release
2012-11-15 GP130780EAE H.-K. Spielbauer Release
2012-12-20 GAA30780EAF H.-K. Spielbauer Release
2012-12-06 GAA30780EAG GS Wang Added COR rescue operation
2013-01-09 GAA30780EAG D. Cominelli Added section 10.2 – ACD with CSPB
2013-01-08 GAA30780EAG H.-K. Spielbauer Release
2013-03-07 G1530780EAH A. Pfeffer Added section 10.2 - GCS 222 LVA
2013-03-27 G1630780EAH A. Pfeffer Modified section 10.2 - GCS 222 LVA
2013-04-04 G1730780EAH A. Pfeffer Added exampled for 3.5 RGEN Display
2013-04-11 G1830780EAH A. Pfeffer Section 5.5 – Added instruction for pa-
rameter changes
2013-04-24 GP130780EAG A. Pfeffer Release
2013-06-12 GAA30780EAH A. Pfeffer Release
2013-07-08 GP230780EAG GS Wang Updated COR rescue operation about
mode change to DCS when abnormal
APRS detected.
2013-09-06 GP230780EAG A. Pfeffer Release
2013-10-10 G2230780EAJ A. Pfeffer In section 10.2 - GCS 222 LVA, added
parameter description “LVA-TYP”
2013-10-14 Gxx30780EAJ D. Cominelli Added section 8.3 “DEK with RSL
Encoded Interface”
2013-10-28 G2730780EAJ A. Pfeffer In section 10.2 - GCS 222 LVA, added
CARIO I/O Mapping
2013-11-04 GAA30780EAJ A. Pfeffer Release
2013-12-09 Gxx30780EAK D. Cominelli Added section 17.1 “REM6 Setup”
2013-12-13 GAA30780EAK A. Pfeffer Release
2014-01-14 GP330780EAG GS Wang Added section 18.1 – Automatic adjust-
ing parameter
2014-02-11 GAA30780EAL A. Pfeffer Release
2014-04-02 GP130780EAL H.-K. Spielbauer Release
2014-05-23 GP230780EAL A. Pfeffer Release
2014-06-10 GP230780EAL A. Pfeffer Corrected CAR I/O Mapping for RDOS
2014-06-03 G7130780EAL M. Hnida Added Low Pit with pit access from
both front and rear door
2014-05-02 G2230782GAA A. Pfeffer Modified 8.2 Dummy Doors – now
includes setting of Allowed Mask and
Drive parameter
2014-05-21 G2230782GAA DH Kang Added Automatic adjusting parameter
2014-05-23 GAA30782GAA A. Pfeffer Release
2014-07-16 GP130782GAA A. Pfeffer Release
2014-07-17 GP230782GAA A. Pfeffer Release
2014-09-01 G1430782GAB A. Pfeffer EFS: Removed obsolete parameter
EN-EVT from description
2014-11-14 Gxx30782GAB M. Ifland In section 2.4 “ARO”, added DIS-ARO,
ARO-T
2014-11-17 Gxx30782GAB M. Ifland Added section 2.28 “Penthouse Con-
trol”
Page: 10 / 196
Berlin

2014-12-04 Gxx30782GAB M. Ifland Renamed ARO-T to ARO-D
2014-12-18 G1930782GAB A. Pfeffer In “Drive Releated Features”, changed
order of chapters for alphabetical order
2014-12-18 G1930782GAB A. Pfeffer Added “Smart Charger for LVA Switch”
2015-02-02 G2330782GAB A. Pfeffer For LVA, added type of RSL LT
2015-02-09 G2330782GAB M. Ifland Added section 2.18 “EFO – Dynamic
EFO”
2015-02-27 G2430782GAB M. Ifland In section 2.28 “PTC” swapped modes
133 and 153
2015-03-06 G2630782GAB A. Pfeffer Added "15.1.1 ARO with GECB_LV"
and "15.2.3 MRO with GECB_LV"
2015-03-19 G2730782GAB A. Diethert 2.28 “PTC” only mode 153 is suited
2015-03-25 G2830782GAB A. Pfeffer Renamed 1338 P-DET to PDET
2015-03-25 G2930782GAB A. Diethert Minor revisions for 2.28 “PTC”
2015-03-25 GAA30782GAB A. Pfeffer Release for GECB_V2
(AxA26800AVPx)
2015-03-25 GAA30780EAN A. Pfeffer Release for GECB_V1
(AxA26800AMLx)
2015-04-22 GAA30780EAN A. Pfeffer Expanded OOLxx description for EFO
Page: 11 / 196
Berlin
2 Operational Modes
2.1 ACP - Anti-Crime Protection
Anti-crime protection forces each car to stop at a pre-defined landing and open it’s doors.
This allows a security guard or receptionist at the landing to visually inspect the passengers.
The car stops at this landing as it passes to serve further demand.
Install-Parameters:
Group name value description
9-SECURITY IST-P 0-99 Intermittent Stop Position
0..99: enabled, valid floor
>99: disabled
9-SECURITY EN-IST 1-7 Enable Intermittent Stop
0: disabled
1: up direction only
2: down direction only
3: both directions
4: not used
5: up direction when ISTS active
6: down direction when ISTS active
7: both directions when ISTS active
I/O-Numbers:
no. name description type location
616 ACSC Anti Crime Switch Car in car
617 ACSH Anti Crime Switch Hall in car
745 ISTS Intermittent Stop in group
When Anti-Crime Protection is triggered from the keyswitch ACSC or ACSH the mode
changes immediately to ACP. The car stops at every floor and opens the door enroute to
serving any registered car calls. The car shall be able to answer hall calls directly without
stopping if no car calls are registered.
Anti-Crime Protection can also be activated via installation parameters. When IST-P is set
to a valid floor and EN-IST is enabled, the car shall operate in normal operation until it
reaches the IST-P position. The car shall then stop at the IST-P position and open the doors
fully allowing for visual inspection. This feature can be configured to only occur in the up
direction, down direction, both directions, and/or only when the ISTS switch is activated on
the group link.
ACP has priority over SCX, CHN, MIT, LNS, ANS, DCP, PRK, NOR, and IDL modes.
Page: 12 / 196
Berlin
2.2 BLC - Better Living Circuit

Introduced in GAA30780EAE
This is the specification to be added for the apartment building constructed by the Housing
Corporation for Japan. When the Emergency Call Button (ECB) in the car is pressed, the
following operations for each type will be executed.
Parameters:
5-DOORS DCB-ACP 0,1 Enable DCB during ACP (Triggered by Better Living
Circuit)
0 DCB/RDCB/WDCB/RWDCB is disabled during ACP
1 DCB/RDCB/WDCB/RWDCB is enabled during ACP
9-SECURITY BLC-TYP 1-4 Better Living Circuit Type:
0 Invalid
1 Execute Type 1 (Buzzer only)
2 Execute Type 2 (Buzzer & ACP mode)
3 Execute Type 3 (Buzzer & ACP mode with timer)
4 Execute Type 4 (New Nagoya Sepc.)
BLC-T 10-255 BLC Buzzer Timeout:
10 (1) 255 s
BLC-DCB 0,1 Enable DCB during BLC
0 DCB/RDCB/WDCB/RWDCB is disabled during ACP
triggered by BLC
1 DCB/RDCB/WDCB/RWDCB is enabled during ACP
triggered by BLC
ECB-TYP 0,1 ECB button type:
0 Normal
1 Detection of rising edge
ECB-TYP can be selected depending on ECB devices.
I/O-Numbers:
23 BUZ Buzzer out car
1193 BRB1H Buzzer Reset Button for Hall Link w/ ACP reset in hall
1194 BRB2H Buzzer Reset Button for Hall Link w/o ACP reset in hall
1211 BUZH Buzzer for Hall Link out hall
1229 ECBC Emergency Call Button for Car Link in car
Type 1:
The alarm buzzer sounds and [ACP] is not activated while the emergency call button (ECBC)
button is being pressed.
Type 2:
Alarm sound is activated when the ECBC is pressed and deactivated when buzzer reset
button (BRB1H) is active. [ACP] mode is active while the alarm is sounding. When BRB1H
pressed, the alarm buzzer stops [ACP] is reset and return to normal operation mode. If
Page: 13 / 196
Berlin
BRB1H pressed during moving, the car will stop at the nearest floor and then return to
normal operation mode.
Type 3:
When the ECBC is pressed, the alarm sounds for about 3 minutes (BLC-T). This timer value
is initiated whenever ECBC is pressed. [ACP] mode is active while the alarm is sounding.
When the preset 3 minutes are expired or BRB1H is pressed, the alarm buzzer stops, [ACP]
is reset and return to the normal operation mode. If the preset time is expired or BRB1H is
pressed during moving, the car will stop at the nearest floor and then return to the normal
operation mode.
Type 4:
When the ECBC is pressed, the alarm sounds for about 3 minutes (BLC-T). This timer value
is initiated whenever ECBC is pressed. [ACP] mode is active while the alarm is sounding.
When the preset 3 minutes are expired, the alarm buzzer stops, [ACP] is reset and returns
to the normal operation mode. If the preset time is expired during moving, the car will stop at
the nearest floor and then return to the normal operation mode. When BRB1H is pressed,
[ACP] is immediately reset and returned to the normal operation mode. If BRB1H is pressed
during car moving, the car stops at the nearest floor and then returns to the normal
operation mode even before the preset time of 3 minutes elapses, but warning buzzer
continuously active until BRB2H is active or 3 minutes are expired. When BRB2H is pressed,
the warning buzzer immediately stops sounding even before the preset 3 minutes elapsed,
but [ACP] is continuously active until BRB1H is active or 3 minutes are expired.
2.3 ANS - Anti-Nuisance Operation
Upon activation, all registered car calls are cancelled. This is used to prevent the car from
answering car calls when no one is in the car.
Install-Parameters:
1-SYSTEM ANS 1-255 Anti Nuisance Call Limit
0: disabled, all calls answered
1..255: calls needed to trigger ANS if car is loaded with
ANS load (input: LWX)
If the car is empty (i.e. less than 10% of rated load), and there are more calls entered than
defined by the parameter ANS, all car calls are deleted.
Page: 14 / 196
Berlin
2.4 ARO - Automatic Rescue Operation

The operational mode ARO is available since GAA30780DAB.
Install-Parameters:
5-DOORS DAR-T 15-255 Door Time for Automatic Release:
In case of a fault the door is kept open for DAR-T and then
closed.
9-SECURITY RSC-SEC 0,1 Rescue Security Options:
0 Do not open secured doors after a rescue run
1 Open doors after a rescue run, even if secured
1-SYSTEM DIS-ARO 0,1 Disable ARO
0 ARO enabled
1 ARO disabled
1-SYSTEM ARO-D 0-240 Delay ARO
The system waits for ARO-D before ARO is started.
I/O-Numbers:
1045 AROL Automatic Rescue Operation Light out car
The features ARO and EPO are mutual exclusive. The OCSS ARO mode will not be started,
if the GECB is in inspection mode.
The ARO mode will be aborted, if the EFS Phase II were activated before ARO. Phase I
(EFO) also prevents ARO.
More Details about the preparing the ARO phase are described in chapter 15.1.
The OCSS will reject the ARO request in case of:
 INS mode
 Position from Drive is invalid
 EFS mode
 EFO mode (since version GAA30780DAB)
 ARO run would be up at TOP floor or down at BOTTOM floor
 DIS-ARO is set to 1
 the following timeouts happens:
max. time what for

60s drive must be idle and published a valid position to the GECB after the beginning of ARO
4:20min the target must be reached after the drive became idle
60s the safety chain must be closed after the beginning of closing
Page: 15 / 196
Berlin
ARO-Sequence:
The drive publishes the rescue direction (generative direction, determined by load weighing)
to the GECB. The GECB starts a rescue run to the next DZ (if not at DZ) and checks it. If it
is a dummy floor, the car will move to the next DZ in the same direction. If the car stays /
reaches a DZ which is not a dummy floor, the GECB will open one door if the door is not
secured. At first the front door will be checked. If the front door is not available or secured
(parameter ‘RSC-SEC’, fire proof door, SAC, card reader, EMS security), the rear door will
be checked and opened (if available or not secured). The buzzer will be switched on, if one
door opens. The door open time depends on the parameter ‘DAR-T’. The buzzer will be
switched off, if both doors are closed. During closing of the door, the DOB will be enabled. If
the doors are closed or a timeout of 1 minute happens (for closing the doors), the GECB will
sends a message (ARO finished) to the SPBC_III or the internal rescue module (GECB_II).
Since version GAA30780DAB: After closing the door the DOB would open the door
(possible for 30s after the DAR-T).
Since version GAA30780DAD: A run to the next DZ will be executed, even though the posi-
tion is invalid. Then the door opens only, if no rear door, no dummy door and no secured
door is programmed. If the position is invalid, a run up within 2LS or run down within 1LS is
not possible.
Since version GAA30780EAK: ARO can be disabled with the parameter DIS-ARO for con-
trollers which do not support this option.
Since version GAA30782GAB: ARO runs can be delayed by a time period specified in the
parameter ARO-T. Until this time has elapsed, the system waits for power to resume.
ARO times:
time what for
DAR-T the door will be open for this time
30s DOB will be evaluated after DAR-T before switched off
(since GAA30780DAB)
ARO-T ARO will not be started until ARO-T has elapsed
Rescue direction will change, if load weighing fails:
delay what happens

0 drive publishes the rescue direction (preferred direction)
up to 200ms GECB sends rescue run command
1s brake drops (stop by drive, because the drive needs to much power; caused by failed load
weighing -> wrong preferred direction)
up to 50ms drive publishes new rescue direction ( inverted)
up to 200ms GECB send new rescue command
up to 500ms drive starts rescue run
This direction change happens only once (controlled by drive).

Page: 16 / 196
Berlin
2.5 ATT - Attendant Operation
The Attendant Service Operation feature shall accommodate semiautomatic operation un-
der manual control.
The car shall be placed on and removed from attendant operation by a key switch(ATK) in
the car operation panel.
Once on attendant operation, a car shall operate automatically except that judgments as to
car loading, door closing, and hall call bypass are made by the attendant. The optional Auto
Running Light(ARL) indicates that the car is under attendant operation.
Doors shall be commanded to open automatically for each car or hall stop and remain open
until the Door Close Button(DCB) ( Alternativly Door Close Button RDCB for alternate door)
is pressed. Doors shall be commanded to re-open when the Door Close Button is released
before the doors have fully closed.
Constant pressure applied to the non-stop button(NSB) bypasses hall calls as the car trav-
els through the Hoistway to serve registered car calls. Upon entering attendant operation,
any previous car calls registered are deleted.
Nudging, door protection devices and load weighing bypass are inhibited.
Install-Parameters:
1-SYSTEM ATT 0 Attendant Operation Type:
0: Press DCB or RDCB until the door is fully closed (start
demand exists (ATT-1))
1: Press ATTU/ATTD until the door is fully closed (start
demand exists (ATT-3))
2: Like 0, but the door may also be closed without any de-
mand
I/O-Numbers:
548 ATK Attendant Service Key in car
3 DCB Door Close Button in car
591 ATTD Attendant Down Button in car
590 ATTU Attendant Up Button in car
594 NSB Non Stop Button in car
740 FDL Further Demand Lamp out car
595 NSL Non Stop Lamp out car
593 FDLD Further Demand Down Lamp out car
592 FDLU Further Demand UP Lamp out car
742 ARL Attendant Running Lamp out hall
5500-5599 AUHCL 0-99 Annunciator Up out car
5600-5699 ADHCL 0-99 Annunciator Down out car
Page: 17 / 196
Berlin
The inputs and outputs need to be addressed according to the operation type selected and
whether the additional lamps are required.
Page: 18 / 196
Berlin
2.6 Alternative Simplex Zone Parking
With PRK-TYP=1, after responding to the last call, the car shall move to pre-determined
floor after ARD-T is expired. In this case, the [PRK] mode is displayed on SVT.
This function is only for simplex operation.

Install-Parameters:
2-OCSS FIX-PRK 0-8 Enable Fixed Zone Parking:
0 (1) 8 Number of Fixed Zones
FIX-MASK 0-255 Enable Fixed Zone Parking:
1 Bit for each zone where the car is allowed to park in
PRK-TYP 0-1 Alternative Simplex Parking Type:
0 If PCLKx is operated, the car will park at PARK-x imme-
diately. (If all PCLKx inputs OFF, the car parks at ARD-P.)
1 If PCLKx is operated, the car will park at PARK-x after
ARD-T is expired. (If all PCLKx inputs OFF, it seems that
ARD-P is ignored.)
Note: Simplex only

PARK-1 0-255 Park Clock Position 1:
Simplex: If PCLKx is operated, the car will park at PARK-x
instead of ARD-P.
PCLK1 has highest, PCLK8 has lowest priority.
Group: Bottom position of the Fixed Parking Zone x.
0 (1) 99
> 99 Disabled
Note: Simplex only
0 (1) 99
> 99 Disabled
Note: Simplex only
0 (1) 99
> 99 Disabled
Note: Simplex only
0 (1) 99
> 99 Disabled
Note: Simplex only
0 (1) 99
> 99 Disabled
Note: Simplex only
0 (1) 99
> 99 Disabled
Note: Simplex only
Page: 19 / 196
Berlin

0 (1) 99
> 99 Disabled
Note: Simplex only
0 (1) 99
> 99 Disabled
Note: Simplex only
I/O-Numbers:
no. name description type location since
753 PCLK 1 Park Car Clock 1 in group
This table shows how to determine parking run floor by combination of parameters and in-
puts. (Applicable for PRK-TYP=1)
Parameter Value Input

Parking Run Floor
PARK-1 PARK-2 PCLK1 PCLK2
- - - - No parking run
OFF - No parking run

valid invalid
ON Run to PARK-1
ON ON Run to PARK-1
ON OFF Run to PARK-1

valid valid
OFF ON Run to PARK-2
OFF OFF No parking run
ON Run to PARK-2
invalid valid -
OFF No parking run
Note: PCLK1 has higher priority than PCLK2. (PCLKx>PCLKx+1)
Page: 20 / 196
Berlin
2.7 CCB - Car Calls Behind
This feature allows car calls to be registered anywhere in the building. Normally, car calls
are only allowed to be entered in the direction the car is moving.
Install-Parameters:
2-OCSS DS-CCB 0-2 Disable CCs behind moving car
0 CCs behind allowed
1 CCs behind not allowed
2 CCs behind allowed but canceled when direction re-
versed
The parameter DS-CCB defines whether car calls are allowed in the opposite direction of
the car’s current moving direction.
0 = enabled, car calls always allowed
1 = disabled, calls only allowed in moving direction
2 = car calls behind allowed but canceled when direction reversed
2.8 CFT - Cafeteria Position
At the defined Cafeteria Pos, longer than normal door times are desired to handle the addi-
tional traffic.
Install-Parameters:
1-SYSTEM CFT-P 1-99 Floor with restaurant/cafeteria
0...99: valid position
<99: disabled
5-DOORS CFT-NT 255 Cafeteria Door Dwell time:
0..25.5 seconds
Note: This door time is used at CFT-P if it is longer than

MIN-H.
2.9 CGS - Buzzer control for Detecting Landing Door Opened

Introduced in GAA30780DAG
If a landing door is opened with the closed car door for 1.5sec while the operation mode is
not INS mode, a car buzzer will be sounded. The sound time is about 10seconds but buzzer
will not be sounded when the operation mode is the INS mode by TCI or ERO switch. To
enable this feature also during run, select EN-CGS = 2.
Page: 21 / 196
Berlin

5-DOORS EN-CGS 2 Enable Door short Protection with CGS signal
0 disabled
1 enabled
2 like 1, but warning buzzer is enabled for the opened
landing door
2.10 CK, CBC - Car Button Cancel

With this feature, you can reduce the remaining door dwell time or delete an existing car
call.
Install-Parameters:
5-DOOR EN-CK 0 Feature disabled. Door remains open until door dwell time
has expired normally. Entered car calls cannot be cleared.
1 CK - When a car call button is pushed, the door immediate-
ly begins to close.
2 CBC - While the car is stopped, enter car button twice again
to delete an inadvertandly entered car call.
3 Options 1 + 2 together
4 CBCR1 - Cancel registered car call with car button (press
once) even during run
5 Options 1 + 4 together
6 CBCR2 - Cancel registered car call with car button (press
twice) even during run
Cancel Door Dwell Time

This feature reduces the door dwell time if a car call button is pushed. That means that the
door immediately begins to close after a car call has been entered.
Reversal devices are still active and will cause a normal reopening of the door. The door will
stay open again for MIN-C.
To enable this feature, select EN-CK=1.
Cancel Car Call

With this feature, the car call can be deleted if the same car button is pushed again twice.
To enable this feature only during stop, select EN-CK=2. To enable this feature also during
run, select EN-CK=4(press once), EN-CK=6(press twice; since GAA30780EAE).
Note: If JIS with EN-CK=6, the car call shall not be canceled when EFS mode or there is
only one car call.
Page: 22 / 196
Berlin
2.11 Compass - Destination Entry

The GECB software GAA30780AAB supports Destination Entry using the Group Control
Board (GCB). The following parameters must be programmed to enabled this feature:
Use M-1-1-5 to verify whether a GCB is online and whether Compass is active.
Install-Parameters:
1-SYSTEM OPERAT 0 FCL Full Collective
2-OCSS DOC 255 Disable Door Reopening
3-GROUP MIT-ST 0 Disable MIT (handled by GCB)
MIT-T 0 Disable MIT (handled by GCB)
MIT-VD 0 Disable MIT (handled by GCB)
MIT-DOOR 0 Disable MIT (handled by GCB)
SEL-COMP 3
RNG-BAUD 1 19200 baud
DEST-DE 5 1: no Annunciator, no COP
3: Annunciator, but no COP
5: COP, but no Annunciator
7: Annunciator and COP
For a simulation environment (i.e. no real passengers) add

'8' to the above values.
GCB-EN 8
4-DRIVE DUTY-HI xx low two digits of the car capacity (e.g. 50 for 1150kg)
DUTY-LO xx high two digits of the car capacity (e.g. 11 for 1150kg)
5-DOOR MIN-C 20 MIN-C and MAX-C must be identical (adjustable by GCB)
MAX-C 20 MIN-C and MAX-C must be identical (adjustable by GCB)
MIN-H 40 MIN-H and MAX-H must be identical (adjustable by GCB)
MAX-H 40 MIN-H and MAX-H must be identical (adjustable by GCB)
EXT-C 80 8s dwell time for handicapped car calls
EXT-H 30 30s dwell time for handicapped hall calls
EXT-H*10 1 select EXT-H as "1 sec" timer
I/Os
IO Symbol Description Since Def Type LOC
5500 AUHCL 0 Annunciator Front Call Lantern 0 0 out car
... ... ... ... ... ... ...
5599 AUHCL 99 Annunciator Front Call Lantern 99 0 out car
Page: 23 / 196
Berlin
2.12 COR Rescue operation
The objective of this function is to rescue passenger at the rescue floor before entering
correction run to terminal landing when lost its position.
Note: the rescue floor means the nearest door valid floor matched secured status
according to the bit 1 of CR-OPT.
Notice: There is a risk to open door at wall for CR-CHK-T * 100 ms when APRS was not
detected at dummy floor (landing door invalid floor) with the enabled bit 3 of CR-OPT or
when APRS was abnormally detected at dummy floor with the disabled bit 3 of CR-OPT.
Notice: COR rescue is available for front door only at phase 1
1. Rescue run to the nearest door valid floor is allowed when enabled rescue at the
nearest door valid floor under COR (bit 0 of CR-OPT) and DAR-T is higher than 0.
2. In order to identify the correct door for the rescue operation, conditions for door installed
condition and acceptance to open door at then secured floor shall be checked as shown
below.
2.1 Front doors only for all landing
If it is accepted to open door at the secured floors, OCSS can move car to the
nearest landing without additional position reference which can provide the
information to check which side door is valid,
If it is not accepted to open door at the secured floors, additional position reference
for front (CR-FSO) at all secured floors is required to provide the landed floor is
allowed or not to open front door when APRS installed at landing disabled to open
door under COR rescue.
2.2 Front and rear doors at all landings
If it is accepted to open door at the secured floors, OCSS can move car to the
nearest landing without additional position reference which can provide the
information to check which side door is valid
If it is not accepted to open door at the secured floors, additional position references
for front (CR-FSO) at all secured floors or rear (CR-RSO) at all secured floors is
required to provide the landed floor is allowed or not to open door at each side
when APRS installed at landing disabled to open door under COR rescue.
2.3 Front and rear doors at some landings
Recue run to the nearest floor with front and rear doors at some landings is not
available at this moment regarding of the risk of car door opening in front of a
concrete wall.
Page: 24 / 196
Berlin
To support rescue run to the nearest floor under condition like front and rear doors
at some landings, additional position references for front (CR-FSO) at all front
dummy floors or rear (CR-RSO) at all rear dummy floors is required check the
landed floor is allowed or not to open door at each side when APRS installed at
landing disabled to open door under COR rescue.
3. Monitoring APRS installed status
3.1 APRS installed status for each floor shall be inspected during learn-run or DCS run
and being saved in non-volatile memory.
3.2 When changed the service floor to dummy floor or dummy floor to service floor, the
installed status of APRS shall be reset.
3.3 If APRS is active after 500ms since leveling sensor turned off during run, APRS
abnormal operation detected and ERR_0275(CR-FSO Flt) & ERR_0276 (CR-RSO
Flt) is logged.
3.4 if physical address of APRS was not set and COR rescue operation is enabled,
ERR_0275 (CR-FSO Flt) & ERR_0276 (CR-RSO Flt) is logged
3.5 ERR_0275 and ERR0276 shall be ignored when “DCS Run” message displayed at
SVT because “DCS Run” message is enough to notify user to re-check APRS
installed status.
3.6 APRS can be truly active when signal de-bounced for 500ms during COR rescue
operation
3.7 When APRS was improperly installed like missed APRS at dummy floor or detected
APRS at normal service floor with set of +8 in CR-OPT, operation mode shall be set
to DCS if not set +16 in CR-OPT.
4. Abort COR rescue operation
4.1 Before entering COR rescue operation
A. When APRS abnormal operation was monitored, the rescue run to the nearest
floor shall be aborted and op mode changed to DCS except for option not-entering
DCS.
B. When APRS was not installed at dummy floor and set to install APRS at dummy
floor (bit 3 of CR-OPT=1), op mode changed to DCS except for option not-entering
DCS.
C. When APRS was not detected and set to install APRS at service floor (bit 3 of CR-
OPT=0), the rescue run to the nearest floor shall be rejected and directly move to
run to terminal landing.
D. When limit switch failure detected like simultaneous 1LS and 2LS activation, the
rescue operation shall be aborted.
4.2 While moving to the nearest landing
A. When 2LS detected while moving upward, the rescue operation shall be aborted.
Page: 25 / 196
Berlin
B. When 1LS detected while moving downward, the rescue operation shall be
aborted.
C. When position recovered during run with rescue command under COR rescue
operation, the position from drive shall be discarded to avoid the unexpected
position recovery cause the stuck NOR. If position is correct after stopped, accept
the position from drive.
4.3 When try to open door at the nearest landing
A. When landing door switch was not open status after CR-CHK-T since door open
command active at the rescue floor, the rescue operation is immediately aborted,
close door. This is to protect against an APRS failure that indicates a door exists
where one truly does not exist. Exceptionally, CR-CHK-T is not effective when no
dummy floor exist. When failed in detection of landing door open, operation mode
shall be set to DCS after position recovered if not set +16 in CR-OPT.
B. If car door was not physically opened for a specified time (DAR-T), entered the
generic COR returning to terminal landing.
5. Moving to the nearest landing
5.1 CR-DIR shall be preferred direction at the initial run for COR rescue.
5.2 When 2LS detected before entering COR rescue, preferred direction shall be down
5.3 When 1LS detected before entering COR rescue, preferred direction shall be up.
5.4 Real moving direction and stop door zone shall be controlled by drive
6. When the below condition satisfied, door open is allowed
6.1 Both leveling sensors like LV1 & LV2 are active. When using single LV, LV1 or LV2
active.
6.2 Signal leveling sensor like LV1 or LV2 is active and UIS or DIS is active
6.3 Both UIS and DIS are active
6.4 Limitation in stop control before opening door
When use 4 sensors type PRS with LCRD drive, drive can’t stop car at door zone
under the below condition.
 Not able to stop car at both direction when both UIS and DIS failed
 Not able to stop car at upward when UIS failed
 Not able to stop car at downward when DIS failed
7. Door selection to be opened when car stopped at door zone
7.1 If there was no dummy floor for front and secured floor allowed to open door, front
door is always allowed to open.
Page: 26 / 196
Berlin
7.2 If there was no dummy floor for rear and secured floor allowed to open door, rear
door is always allowed to open.
7.3 When both front and rear door is allowed to open, front is override rear door.
7.4 If there was dummy floor or secured floor was not allowed to open door, APRS input
from each side is criteria to decide door to be opened.
7.5 Door open is allowed if APRS detected inside door zone when APRS installed at
service floor(bit 3 of CR-OPT=0) and is allowed if APRS was not detected when
APRS installed at dummy floor(bit 3 of CR-OPT=1)
8. Door opening at the nearest landing
8.1 If door open was tried and door open is invalid at the stop position when APRS
installed at service floor (bit 3 of CR-OPT=0)
Moving to the next door zone when APRS installed at service floor (bit 3 of CR-
OPT=0) and APRS was detected during normal operation.
COR rescue operation shall be aborted after max 3 times movement which is
counted by checking door zone senor or UIS or DIS.
8.2 If door open was tried and door open is invalid at the stop position when APRS
installed at dummy floor (bit 3 of CR-OPT=1)
Abort COR rescue operation and return to terminal landing according to generic
COR when APRS installed at dummy floor (bit 3 of CR-OPT=1.
8.3 After confirmed door was successfully opened, below fixture control shall be
followed while door open for a specified time (DAR-T)
1) Turn on GOL (Get Off Light) while door open
2) Buzzer will be flickered except for disabled buzzer flickering with bit 2 of CR-OPT.
8.4 After waiting at the rescue floor with door opened for a specified time (DAR-T)
perform the general COR to terminal landing. The time should be adjustable by
parameter which the range of value is from 5 to 30sec and default value is 15 sec.
When door reversal device active while opening door, waiting time at the rescue
floor will restart.
8.5 After expired waiting time (DAR-T) at the rescue floor, close door, turn off GOL (Get
Off Light) and car enter to COR run to terminal landing and turn on MD_COR until
returned to normal operation.
9. When returned from COR to normal operation mode which can service hall call or
ISC/PKS/OLD or REI, MD_BTN will be turned on for 3 seconds to notify car was
successfully returned to normal operation. MD_BTN shall be turned on after 2 sec from
position recovered regarding of the specific case that drive can recover position for 1
sec and return to the invalid position status.
Install-Parameters:
Page: 27 / 196
Berlin

1-SYSTEM CR-OPT 0 Option for COR operation:
+1 Enable rescue at the nearest door valid floor
+2 Allow door open at the secured floor
+4 Disable buzzer at the rescue floor
during door opened
+8 Installed APRS at floor disabled to open door
+16 Do not enter to DCS mode when abnormal APRS de-
tected.
Note: When secure floor exist, prohibited to open door at the

secured floor and no additional PRS installed at the secured
floor, rescue to the nearest floor will be aborted.
1-SYSTEM CR-DIR 0 Correction Fast Run Preferred Direction:

0 Down
1 Up
5-DOOR DAR-T 15 Door Time for Automatic Release:

closed.
15 (1) 255 s
Note: Applies for MCLS, CLR, SKL, DLM, HAD, 1TH/2TH,
DBF
Or
Door time for COR rescue operation:
0 Disable rescue at the nearest door valid floor
1 (1) 5 Default 15 second
6 (1) 255 second
5-DOOR CR-CHK-T 8 Delay to check landing door opened after open command:
When DW is closed after DOR-CHKT since door open
command active, immediately close door under rescue
operation with dummy floor.
0 (0.1) 2 s
I/O Name Link Description

1163 WTL car Waiting light
1164 GOL car Car indicating light - "Please get off"
1276 MD_COR car Mode display for COR run
1316 MD_BTN car Mode display for back to normal
1317 CR-FSO car Front Safe to open when position lost
1318 CR-RSO car Rear Safe to open when position lost
1163 WTL car Waiting light
2.13 CTL,CBL - Car Calls to Terminal Landings
If the controller has switches available, car calls to the terminal landings can be defined.
When activated, the car registers a call to either the bottom landing or the top, dependent
Page: 28 / 196
Berlin
upon the switch activated. Note that DCDS must be activated before CCTL or CCBL can be
used.

13 CCTL car Car call to top landing, only if DCDS is active
14 CCBL Car Car call to bottom landing, only if DCDS is active
786 DCDS Car Disable call and door switch (DDO+CHCS)
The inputs must be addressed correctly. Note that for buildings with unequal travel, the calls
to the top or bottom landing are based upon the allowed mask.
Page: 29 / 196
Berlin
2.14 DBF - Drive / Brake Fault

In case of a failure (e.g. car light, HTS, 1TH, 2TH, drive not ready) the car stops at the next
commitable landing, deletes all calls, opens door for DAR-T, then closes the door.
New calls will not be accepted. Only the DOB is operating.
Install-Parameters:
1-DOOR DAR-T 15-255 Door Time for Automatic Release:
closed.
DBF is performed for the following conditions:

Feature Detection
Car Light Failure Detected by I/O 1000 CLR.
Requires (1-SYSTEM) CLR-RUN=0
This input is low-active
Drive Fault Contact GECB-EN, -AP:

Detected by discrete inputs 1TH and 2TH, located at the GECB.
GECB_II:
Detected by discrete inputs 2TH and 2SE, located at the BCB_II
These inputs are low-active
Overtemperature Detected by Hall Temperature Sensor HTS, located at SPB, SPBC or SP.
The temperature limit is defined by the parameter (7-SERVICE) SPB-TEMP
ETS Fault Refer to separate ETS chapters 5.1 and 5.3.
6LS-TYP Mismatch Mismatching parameters (4-DRIVE)6LS-TYP on GECB and (Contract)6LS-TYP

on the Drive.
Refer to separate 6LS chapter 5.9
LowPit/APS Failure Refer to separate LowPit chapter 9.2
Hong Kong Door Lock: Detected by the I/Os 1039 XLV1 and 1040 XLV2
External LV Failure
Page: 30 / 196
Berlin
2.15 DHB - Door Hold Button

When the DHB keyswitch is operated the door opens for a specific duration. After that dura-
tion has expired the door closes automatically.
By pressing any Car Call Button or the Door Close Button the doortime can be canceled
manually and the door will close.
If DHB-TYP is set to ‘+1’ the door time can also be canceled by activating DHB again. If you
have opened the front door by using DHB, the activation of RDHB will open the rear door
and will not close the front door. To close a door you have to use the same keyswitch as
you have used to open a door.
If DHB-TYP is set to ‘+2’, existing car calls are deleted in DHB mode.
If DHB-TYP is set to ‘+4’, existing hall calls are not deleted in DHB mode.
If DHB-TYP is set to ‘+8’, the car direction is memorized in DHB mode.
IO-Numbers:
I/O name description
620 DHB Door Hold Button for front door
628 RDHB Door Hold Button for rear door
Install Parameters:
2- OCSS DHB-TYP DHB doortime can be canceled by...
0 press DCB or any CCB
(in this case the DHB-T is a 1-sec-timer
+1 press DCB or any CCB, or press DHB again
(in this case the DHB-T is a 10-sec-timer!)
+2 delete car calls when in DHB (since DAJ)
+4 keep hall calls when in DHB (since DAJ)
+8 keep car direction when in DHB with forward hall calls (since
EAE)
5-DOORS DHB-T Defines the door open time if DHB is operated. It specifies a 1-
sec-timer if DHB-T=0 and specifies a 10-sec-timer if DHB-T=1
Page: 31 / 196
Berlin
2.16 EQO - Earthquake Operation

Earthquake operation occurs when seismic activity is detected - via the counterweight sen-
sor or a seismic sensor.
Install-Parameters:
8-Emergency EQO Version of Earthquake Operation:
0 EQO-6 (New Zealand / Australia)
Earthquake operation mode can be reset with input signal
EQRS
1 EQO-7 (Mexico)
Earthquake operation mode can be reset by deactivating
EQS
2 EQO-4 (PAO)
EQC1 and EQC2 (60s after door open at the earliest)
3 EQO-5 (JAPAN)
EQC1 (60s after door open at the earliest), and EQC2 and
EQC3 can be manullay reset.
8-Emergency Mid Pos Mid Shaft Position:
0-31 Position, where the CWT meets the car
The car will not run to the CWT position at EQO.
255 disabled
EQO mode overrides all forms of security. EQO mode does not override Fire Proof Doors
and overrides not EFO/ EFS modes. The DCB and RDCB will be ignored at EQO.
In group operation each car reacts independent of the other cars in the group. If a common
reaction is required for cars in the same shaft the sensors have to be wired accordingly.
If the car is traveling and EQO is requested by the corresponding input:

 operational mode EQO – Earth Quake Operation is entered (EQL switched on)
 set target to next commitable
 stop at target, open doors and stay with open doors
If the car is stopped in a door zone and EQO is requested by the corresponding input:
 stay at floor, open doors and stay with open doors
Page: 32 / 196
Berlin
If the car is traveling, the parameter ‘Mid Pos’ is set to a landing and EQO is requested by
the corresponding input:
 set target to next commitable
 if target is equal to ‘Mid Pos, then stop immediately, turn direction and start rescue run to
next floor, else keep direction and target
 stop at target, open doors and stay with open doors
2.16.1 EQO-4 (PAO)

This EQO type uses the following I/O Numbers:
I/O-Numbers:
1008 EQC1 Earth Quake Contact 1 (80 Gal) in con
1009 EQC2 Earth Quake Contact 2 (120 Gal) in con
1010 EQR1 Earth Quake Reset 1 out con
0738 EQL Earth Quake Light out car
0026 LR Light Relay (car light / fan) out car
0553 PKL Parking Light out hall
sensor unit: 1Gal = 0.01m/s² 981Gal = 9.81m/s² = 1g

The EQO mode will be activated, if EQC1 or EQC2 is active. The output EQR1 tries to reset
the sensor 1 every 3s (active for 2s) after the door has been opened for 60s. The sensor 2
has been reset manualy. Normal operation is resumed if the door has been opened for 60s
and both signals are inactive.
When the car is in Parking Shut Off (PKS) mode, it does not go into the Earthquake
Operation mode.
EQO mode is memorized even when the power is switched off.
The buzzer will be sound until the door is fully open. If the door becomes fully open, the LR
(car light / fan) output will be switched off and the PKL output will be switched on.
To avoid a run to the CWT position, the parameter ‘Mid Pos’ must be enabled.
Page: 33 / 196
Berlin
2.16.2 EQO-5 (Japan)
There are several types of earthquake sensor is valid in EQO-5 like P-wave Sensor(PWC),
Emergency Earthquake Flas(EEQF), special low-gal(EQC1), low-gal(EQC2) and high-
gal(EQC3 & SEQS). Low-gal and high-gal sensor maunually reset and exceptionally low-gal
sensor can be automatically reset if earthquake automatic recovery operation (EN-EQAR) is
successfully completed.
If car is running inside express zone and earthquake sensor active, immediately stop the car.
When car stops between floors with earthquake sensor active, car try to move to the near-
est floor thru EQO restart (EN-EQAR).
After arrived nearest floor, doing general EQO operation like opening door for 15 sec (EQO-
NT) or EEQF-T when EEQF active, and stayed at EQO mode for 60 sec.
EQAR-NT minutes after completion general EQO operation, try to return to normal
operation by checking operatable status which is running floor to floor and bottom to top thru
Earthquake Auto Recovery Operation. Earthquake Auto Recovery Operation is permitted
when remote service is valid if EQAR-O was set to check remote service connection status
and EQAR-NT
2.16.2.1 EQO Restart (EQO-R)
1. When car stop between floors with general sensor except for low-gal and high-gal,
car immediately try to run to nearest floor.
2. When car stop between floors with low-gal sensor active, Car can runs to the near-
est floor with the low speed (0.33m/sec) within 10 sec or after 60 sec. If car is inside
express zone and not run to nearest floor within 10 sec, car can move to nearest
floor by turning on EQLSS & continuously pushing DCB.
3. When car stop between floors with high-gal sensor active, Car can runs to the near-
est floor within 10 sec or by turning on EQLSS & continuously pushing with the low
speed (0.33m/sec) at counter weight away direction. If car is inside express zone,
car can move to nearest floor by turning on EQLSS & continuously pushing DCB.
2.16.2.2 EQO operation with express zone (EQO-EZ)

Page: 34 / 196
Berlin
1. There are 2 types of method to determine whether the car can decelerate and stop
at the nearest floor within 10 seconds while running in the express zone is described
below.
2. Type1 is based on parameters with AMEZ1 sensor input. If the decelerate and stop
possible position is above EZ1-BOT (3F) and below "AMEZ1" when the car is run-
ning up in the express zone, it is impossible to stop at the nearest floor within 10
seconds. If the decelerate and stop possible position is below EZ1-TOP(10F) and
above AMEZ1 when the car is running down in the express zone, it is impossible to
stop at the nearest floor within 10 seconds.
Express Zone 3F - 10F
11F
10F ← EZ1-TOP Position = 10F
9F
8F
7F ← "AMEZ" sensor is set at the middle in the
express zone.
6F
5F
4F
3F ← EZ1-BOT Position = 3F
2F
1F
3. Type2 is based on parameters without AMEZ1 sensor input. If the car position is be-
tween EZ1-BOT (3F) and EZ1-UPST (5F) during car running up in the express zone,
it is regarded as impossible to decelerate and stop at the nearest floor (11F) within
10 seconds. Therefore, the car makes an emergency stop. If the car position is be-
tween EZ1-TOP (10F) and EZ1-DNST (8F) during car running down in the express
zone, it is regarded as impossible to decelerate and stop at the nearest floor (2F)
within 10 seconds. Therefore, the car makes an emergency stop.
Express Zone 3F - 10F
11F
10F EZ1-TOP = 10F
9F
8F EZ1-DNST = 8F
7F
6F
5F EZ1-UPST = 5F
4F
3F EZ1-BOT = 3F
2F
1F
Page: 35 / 196
Berlin
2.16.2.3 Set Up Parameters

IO-Numbers:
646 EQRS Earthquake reset swich in hall
1008 EQC1 Special low-gal detector I/O address in car
1009 EQC2 Low-gal detector I/O address in car
1010 EQR1 Earth Quake Reset 1 out car
1201 EEQFL Emergency Earthquake Flash Lamp out car
1208 NOL No Operation Lamp out hall
1212 PWC P-wave sensor in hall
1213 EEQFH Emergency Earthquake Flash input for Hall Link in hall
1214 EEQFG Emergency Earthquake Flash input for Group Link in group
1215 EQC3 High-gal detector from CAR link in car
1216 EQSR1 Special low gal sensor reset relay out hall
1217 EQSR2 Low-gal sensor reset relay out hall
1218 SEQS Earthquake switch for S.I.P in hall
1219 EQLSS EQO slow speed switch located at HALL or SIP in hall
1221 EQC1H Special low-gal detector from Hall link in hall
1222 EQC2H Low-gal detector from Hall link in hall
1223 EQC3H High-gal detector from Hall link in hall
1224 PWCL EQO sensor(Pwc) operated light for S.I.P. out hall
1235 AMEZ1 EQO sensor (Special low) operated light for S.I.P. in hall
Install Parameters:
8- SECURI- Earthquake Operation Type:
TY EQO 3 3 EQO-5 (Japan) EQO-P
EQO Door Time:

When door time expires after the door fully opens, the door
closes
EQO-NT 15
0: Standby with the door opened
1(1) 255 s: Door time 1-255s
EQO-P default door:

0 Both doors will open
EQO-DO 1
1 Only front door opens
2 Only rear door opens
EEQF Type:
0 light/fan off and DOBL on
EEQF-TYP 0 1 light/fan light on and DOBL off
2 light/fan light on and DOBL on
EEQF-timeout:
0 Invalid
EEQF-T 90
1(1) 255 s
Enable EQAR operation

0 Disabled
EN-EQAR @
1 Enabled
Page: 36 / 196
Berlin
Timer used from completion of EQO to start EQAR(Default is

programmed as 10min)
EQAR-NT 10
1 (1) 255 min
Option for EQAR:

+1 Active NOL(Car Not in Operation light)
+2 Active CFS when EQAR failed
EQAR-O 3
+4 Execute EQAR without REM
+8 Prohibit EQAR with load > 80KG
Enable EQO-Restart operation

0 Disabled
EN-EQOR @
1 Enabled
Bottom floor of express zone for EQO-Restart

1-99 valid floor
EZ1-BOT @
100-255 invalid
Top floor of express zone for EQO-Restart

1-99 valid floor
EZ1-TOP @
100-255 invalid
Emergency stop limit position in express zone(UP)

0-99 valid floor
EZ1-UPST @
100-255 invalid
Emergency stop limit position in express zone(DN)

0-99 valid floor
EZ1-DNST @
100-255 invalid
Earthquake Operation Type:

EQO 3 3 EQO-5 (Japan) EQO-P
EQO Door Time:

When door time expires after the door fully opens, the door
closes
EQO-NT 15
0: Standby with the door opened
1(1) 255 s: Door time 1-255s
EQO-P default door:

0 Both doors will open
EQO-DO 1 1 Only front door opens
2 Only rear door opens
EEQF Type:
0 light/fan off and DOBL on
EEQF-TYP 0 1 light/fan light on and DOBL off
2 light/fan light on and DOBL on
EEQF-timeout:
0 Invalid
EEQF-T 90
1(1) 255 s
Enable EQAR operation

EN-EQAR @
0 Disabled
Page: 37 / 196
Berlin
1 Enabled
Timer used from completion of EQO to start EQAR(Default is
programmed as 10min)
EQAR-NT 10
1 (1) 255 min
Enable device for EQAR

+1 Active NOL(Car Not in Operation light)
+2 Active CFS when EQAR failed
EQAR-O 3
+4 Execute EQAR without REM
+8 Prohibit EQAR with load > 80KG
Enable EQO-Restart operation

0 Disabled
EN-EQOR @
1 Enabled
Bottom floor of express zone for EQO-Restart

1-99 valid floor
EZ1-BOT @
100-255 invalid
Top floor of express zone for EQO-Restart

1-99 valid floor
EZ1-TOP @
100-255 invalid
Emergency stop limit position in express zone(UP)

0-99 valid floor
EZ1-UPST @
100-255 invalid
Emergency stop limit position in express zone(DN)

0-99 valid floor
EZ1-DNST @
100-255 invalid
14. RE- EqrTrg-T 255 Elapsed hours since temporary operation after finished EQR
MOTE 0 Disabled
1 (1) 255 hours
2.16.3 EQO-6 (New Zealand / Australia)
I/O-Numbers:
623 EQS Earth Quake Switch in hall
645 EQCW Earth Quake Counterweight Switch in con
646 EQRS Earth Quake Reset Signal in con
Page: 38 / 196
Berlin
The seismic sensor EQS provides a static high active signal in case of seismic activity. The
EQCW signal is used to trigger the earthquake operation and requires a separate reset sig-
nal EQRS. Both signals force the car to stop at the next commitable landing, with doors
open, and shut down.
Normal operation is resumed if both signals are inactive and EQRS has been reset. EQO
mode is memorized even when the power is switched off.
The buzzer will be sound during the complete EQO operation.
To avoid a run to the CWT position, the parameter ‘Mid Pos’ must be enabled and the
EQCW input must be active. If only the EQS input is activ and the EQCW input is inactive,
the parameter ‘Mid Pos’ will be ignored (same situationen like ‘Mid Pos’ = disabled).
2.16.4 EQO-7 (Mexico )
I/O-Numbers:
623 EQS Earth Quake Switch in hall
The seismic sensor EQS provides a static high active signal in case of seismic activity. The
EQS signal force the car to stop at the next commitable landing, with doors open, and shut
down. Normal operation is resumed if EQS is inactive again.
The buzzer will be sound during opening the door.
To avoid a run to the CWT position, the parameter ‘Mid Pos’ must be enabled.
Page: 39 / 196
Berlin
2.17 EFO according to EN81-73

This feature is available since GECB software version GP130780DAB.
This feature describes how to setup the inputs and parameters for the control of lifts in the
event of fire.
These are the key requirements if a fire signal has been initiated:
 Landing / car controls (incl. DOB) must be rendered inactive
 Registered calls to be cancelled
 The lift shall return immediately to the designated floor
- If the lift stays at a different landing than the EFO position.
- If the lift is moving in the direction of the designated floor it should continue the run
without stop
- If the lift is moving in the other direction it should stop at the next landing without
opening the doors and run non-stop to the designated floor
 Safety devices have priorities
 Door reversals to be rendered inactive
 One lift of a group must not influence the others
 Lift will stay at the designated landing with open doors
 LRD and EDP shall be rendered inoperative.
The following flowchart explains the decision logic during this operation.
Page: 40 / 196
Berlin
Fire Occured
EFO mode active? No
Fire Sensor at the main

evacuation floor active and
No
EFO override inactive?
[AEFO, EF-I-LT] Other Fire Sensors
active and EFO
No
override inactive?
[EFO, EF-I-LT] Manual Recall
device operated?
Yes [EFO, EF-I-LT]
Yes Yes
Select Alternate Select Main Designated

Designated Landing as Landing as evacuation
evacuation floor [ASL-P] floor [EFO-P]
Yes
Render Landing/Car
Controls incl. DOB inactive
[EFONDG, EFO-REV]
Cancel Registered Calls

No Buzzer operation
[EFO-BUZ, EFO-SD]
Activate EFO mode
Car is stopped at
Yes No
evacuation floor?
No
Car is stopped at Doors are open?
No
different floor?
No
Car is moving in
Open Doors
the direction of the
No [EFO-DC, EFO-DO] Yes
evacuation floor?
Yes
Yes Activate "No Entry"
Stop at the next landing
Indicator
without opening the doors
[ASLPL, EFOPL]
Move directly to the Reset Condition true?

evacuation floor without [!EFO&!AEFO; EFKB]
intermediate stop
No Yes
EFO override active?

Yes
[EFO-OP, XEFO]
No
Normal Operation
Page: 41 / 196
Berlin
I/O-Numbers:
no. name description type
624 EFO Initiate Emergency Fire Operation to designated landing in
772 AEFO Initiate EFO to alternate landing in
775 XEFO EFO override in
1011 ASLPL Alternate service landing position light out
1012 EFOPL EFO position light out
I/O to Parameter relation:

no. name leads into run to position of parameter
624 EFO EFO-P
772 AEFO ASL-P
hint: EFK 016 & ASL 586 are used for EFS (not for EFO)
The following parameters must be programmed for EN81-73:
SVT Display description value comment remark

EFO-P EFO position contract-
specific
EFO-NC EFO Next Commitable 0 Go directly to designated landing
Position
EFO-DC EFO with Doors Closed 0 Stop at designated landing with
open doors
EFO-DO EFO default door 0 Both doors
EFO-OP EFO override option 1 XEFO input overrides EFO after
arrival at return landing
EFONDG Enable nudging speed for 1 Nudging enabled
EFO
EFO-REV Allowed Reversal Devices 1 only SGS/DOS allowed
during EFO
EFO-MP EFO mode priority 0
EFO-MP-T EFO mode priority time 0
EFO-SD EFO signal devices 0 No buzzer operation
EFO-BUZ EFO buzzer operation for 0 No buzzer operation
EN81-72
ASL-P Alternate Service Landing contract-
specific
EF-I-LT EFO/EFS input latching 0 EFO and AEFO are not latched
2.18 EFO – Dynamic EFO
This feature is available since GECB software version GAA30782GAB.

In addition to the Common Fire Alarm Signal an option to modify the evacuation floor de-
pending on the current state of FPD inputs is available (EN-FPD = 3/4). If the FPD input in
Page: 42 / 196
Berlin
the designated evacuation floor is active at the time the evacuation is triggered, the elevator
moves to a neighbouring floor.
FPD-RUN determines the preferred direction for the next available floor (with FPD input
inactive). If the elevator is moving at the time the evacuation is triggered, the current travel
direction overrules the preferred search direction.
FPD-RUN allows to prevent running through a fire area while running to the evacuation
floor. It must be noted, that this option does not comply with EN-81-73.
An option to trigger evacuation with any activated FPD input is also added.
The following parameters must be programmed in addition to those for the common EFO
mode:

EN-FPD Enable FPD 3 Disable floors with FPD active as
EFO/AEFO target
4 Same as 3, additionally FPD
input also triggers evacuation
FPD-RUN FPD Run Options 0 Preferred direction up, runs
through fire area
1 Preferred direction down, runs
through fire area
2 Preferred direction up, no run
through fire area
Not according to EN81-73
3 Preferred direction down, no run
through fire area
Not according to EN81-73
Page: 43 / 196
Berlin
2.19 EFO - Hong Kong Fire Alarm Home Landing
This feature is available since GECB software version GAA30780DAC.
In addition to the Common Fire Alarm Signal there are three separate inputs for Smoke
Sensors.
Upon receiving the Common Fire Alarm Signal (EFO), the lift will return to the homing floor.
If the lift receives a Fire Alarm Signal from the homing floor, however, it will run to ASL1
floor.
If the lift receives a Fire Alarm Signal from the homing floor and the ASL1 floor, it will run to
ASL2 floor.
If the lift receives Fire Alarm Signals from all of the homing floor and the ASL1 and ASL2
floors, it will run to the homing floor.
Install-Parameters:
8-EMERGENCY EFO-P Homing landing
ASL-P Alternate Service Homing Landing
ASL2-P 2nd Alternate Service Homing landing
I/O-Numbers:
1031 AEFL Output to indicate Fire Alarm Homing operation out
1032 FOSS1 Fire Operation Smoke Sensor at Homing Landing in
1033 FOSS2 Fire Operation Smoke Sensor at ASL landing in
1034 FOSS3 Fire Operation Smoke Sensor at 2nd ASL landing in
The inputs FOSS1 – 3 are, by default, high active, but can be inverted by setting the invert
bit when programming the io number.
2.20 EFS - Hong Kong Code for Fireman’s Lifts
If the lift is in EFS mode and loses the Power, the lift will automatically recover to the near-
est floor in the direction of the homing floor when the power is restored.
Install-Parameters:
8-EMERGENCY EN-BAK 2 Enable automatic recover run
HDWPOS 3 Enable position retention in case of power failure
Page: 44 / 196
Berlin
2.21 EFS-TYPs
The following parameters (EFSINI, EFSCLD, EFSOPD, EFS-RC, EFS-EX, EF-I-LT) are set
internal, if the parameter EFS-TYP will be set to ‘0’ to ‘9’.
EFS-TYP EFSINI EFSCLD EFSOPD EFS-RC EFS-EX EF-I-LT

0 EFO 0 0 0 0 0 0
1 EFS 1 (Aut) 1 1 1 0 0 0
2 EFS 2 (Man.) 2 1 1 0 0 0
3 ANSI 4+32 2 2 64 0 0
4 British 1 1 2 1 0 0
5 Swiss 4 1 1 2+4+8+16 0 0
6 Australia 8 8 2 0 2 0
7 New Zealand 8 8 2 0 0 0
8 EFS 2 (ESK) 4 1 1 0 0 0
9 New Zealand 1 2 2 0 0 0
(DCB)
10 Generic (no pre - - - - - -
setup)
11 Reserved for - - - - - -
Japan
12 EFS Korea - - - - - -
Note1: if EFS-TYP is over than Generic (10), just use EFS-TYP for regional difference
control and parameter definition in Generic.
Note2: EFS Korea: same as GENERIC (10) but IO970 and 971 are available in this option
only. These IOs are not available any more in other options of EFS-TYP.
hint to EFSOPD:
For old software the value 4 has to be added for 2 & 8, to get the desired functionality; this
is not necessary since GECB version GAA30780DAB;
I/O to Parameter relation (common for all EFS-Types):

no. name leads into run to position of parameter
016 EFK EFO-P
586 ASL ASL-P
hint: EFO 624 & AEFO 772 are used for EFO (not for EFS)
Page: 45 / 196
Berlin
2.22 EFS - Emergency Firemen Service without correction runs

In some areas (e.g. UK, Düsseldorf) it is required that no correction run may be performed
during EFO or EFS mode.
This chapter describes how you can setup this feature.
1. Make sure that the E2Prom can store data during power-off:
 Switch to ERO and to NOR again
 In the event-list, you will see "0204 TCI/ERO on"
 Switch the power off and on again
 In the event-list, you must still see "0204 TCI/ERO on".
If this is not the case, the E2Prom does not support the page-write-mode and you
have to order a new E2Prom from the factory. See Baseline Release Document for
ordering details.
2. Make sure that the LV sensors are buffered long enough

 Install a voltage buffer which keeps the voltage of the LV sensors for at least 5 sec-
onds after the power has been switched off
 While the car is parked at a floor, use the Service Tool to monitor the LV1, LV2 sig-
nals (must be displayed in uppercase)
 Switch the power off
 The status of the sensors LV1, LV2 must be still displayed in uppercase for at least 5
seconds. If this is not the case, the system would not detect whether the car slides
over a doorzone if it is switched off during a run.
If these two checks are successful, the system is able to avoid a correction run during
EFO/EFS.
Install-Parameters:
8-EMERGENCY EN-BAK 1 Enables that all necessary information is stored into
E2Prom when the system is switched off.
HDWPOS 3 Enables hardware position backup:
No sensor is needed. The position backup is completely
handled by the Drive.
2.23 EFS according EN81-72

This EFS-type is available since software version GAA30780BAA:
Page: 46 / 196
Berlin
These are the key requirements of the Emergency Firemen Service:

EFO (Phase 1):
 The DOB and SGS inputs shall be functional during Phase 1. LRD and EDP shall be
ignored.
 When Phase 1 is initiated and the door is open for longer than 2 minutes, an audible
signal in the car shall sound, which shall be distinguishable from other warnings.
 When Phase 1 is initiated and the car is in inspection mode, the same audible signal
shall sound.
EFS (Phase 2):
 It shall not be possible to register more than one car call simultaneously. Registering a
new car call will cancel the previous car call.
 After arriving at a floor, the door shall not open automatically. DOB must be pressed
constantly to open the door. When DOB is released before the door is completely open,
the door shall automatically re-close. When DOB is released after the door has
completely opened, the door shall remain open until a new car call is registered.
The following parameters must be programmed for EN81-72:

specific
EFO-NC EFO Next Committable 0
Position
EFO-DC EFO with Doors Closed 0
EFO-DO EFO default door 0
EFO-OP EFO override option 0
EFO
EFO-REV Allowed Reversal Devices 2 DOB and SGS/DOS allowed
during EFO
EFO-MP EFO mode priority 0
EFO-MP-T EFO mode priority time 0
EFO-SD EFO signal devices 0
EFO-BUZ EFO buzzer operation for 1...120 Distinguishable buzzer (short- new parameter
EN81-72 long-...) when EFO is requested.
Set this parameter to '1' to start
the buzzer immediately.
Set this parameter to '120' to
start the buzzer after 2 minutes.
ASL-P Alternate Service Landing 255 not required
EFS-TYP Type of Emergency Fire- 10
man
EFS-DO EFS default door 0
EFSINI EFS initiation of Phase 2 1=automatically
2=ISS (IO 4)
Page: 47 / 196
Berlin

4=ESK (IO 626)
EFS-CALL EFS car call handling 2 Latest Call Wins new parameter
EFSCLD EFS close door type 1 car button (constant pressure)
EFSOPD EFS open door type 2 when DOB constantly pressed
EFS-EX EFS exit type 0
EFS-RT EFS return time 40
EFS-RC EFS recall type 128 deactivate EFK for 1..5 sec to new option
repeat EFO
EF-I-LT EFO/EFS input latching 0
EN-BAK Enable E2P-backup of 1 Set to '1' if correction runs shall
EFO/EFS be avoided. Requires additional
voltage buffer.
HDWPOS Hardware position refer- 3 Set to '3' if correction runs shall
ence be avoided. Requires additional
voltage buffer.
The relationship between EFO-SD and EFO-BUZ is shown in the following table:
condition while EFO-SD=0 EFO-SD=1 EFO-SD=0 EFO-SD=1

Phase 1 is re- EFO-BUZ=0 EFO-BUZ=0 EFO-BUZ=120 (*) EFO-BUZ=120 (*)
quested
Door open (e.g. While the door is buzzer is constantly no buzzer buzzer is constantly
DOB) nudging, the buzzer on on
is constantly on
Door open for see above see above buzzer is beeping buzzer is beeping
longer than 120 "short-long-..." "short-long-..."
seconds (*)
(e.g. DOB)
ERO buzzer is constantly buzzer is constantly buzzer is beeping buzzer is beeping
on on "short-long-..." "short-long-..."
TCI buzzer is constantly buzzer is constantly buzzer is beeping buzzer is beeping
on on "short-long-..." "short-long-..."
NAV buzzer is constantly buzzer is constantly buzzer is constantly buzzer is constantly
on on on on
(*) If the "short-long-..." buzzer sequence shall start earlier than after 120 seconds, EFO-
BUZ has to be programmed to a lower value.
2.24 EFS with Safety Chain Bypass for Korea / Taiwan

This EFS-type is available since the following software versions:
GECB: GAA30780BAA
Page: 48 / 196
Berlin
I/O-Numbers:
no. name description connected to type location
016 EFK Emergency Fireman Keyswitch key switch at land- in hall
ing
st
955 1EFS 1 Emergency Fire Service Car FSS1 key (COP) in car
nd
956 2EFS 2 Emergency Fire Service Car FSS2 key (COP) in car
970 DDSCR Disable DS relay contact DDSR1&2 contacts in con
971 DEMERC Disable Emergency relay contact DESBR & DEECR in con
contacts
810 DESBR Disable ESB relay DESBR coil out con
811 DDSR1 Disable DS relay (for hwy. door) DDSR1 coil out con
812 DEECR Disable EEC relay DEECR coil out con
813 DSGSR spare (SGS) - out con
974 DDSR2 Disable SGS relay (for car door) DDSR2 coil out con
no. name description EFK 1EFS 2EFS location

957 EFOL Emergency Fire Operation Light on, if car - - car
not at
EFO-P
1063 EFOAL Emergency Fire Operation Active on - - car
Light
0023 BUZ Buzzer on - on, if not car
moving
999 EFSL Emergency Fire Service Light - on on car
024 FSL Fireman Service Light on on on car
716 EFL Emergency Fireman Light on on on hall
959 EFLM Emergency Fire Light Machineroom on, if INS on, if INS on, if INS con
960 EFLTC Emergency Fire Light Top of Car on, if INS on, if INS on, if INS car
The RSL inputs 1EFS and 2EFS must be connected to a three position key switch (off,
1EFS, 2EFS) located in the car (instead ESK). If the position 2EFS is active, the position
1EFS must be also still active. If 2EFS is active, the safety chain of the car and landing door
will be bridged.
Parameters:
SVT Display description value comment
specific
EFO-NC EFO Next Commitable 0 move to EFO-P
Position
EFO-DC EFO with Doors Closed 0 The doors will be kept open at EFO-P
Page: 49 / 196
Berlin

EFO-DO EFO default door 0 Both doors will be open at EFO-P
EFO-OP EFO override option 0 disabled
EFO
EFO-REV Allowed Reversal Devices 0 all devices disabled
during EFO
EFO-MP EFO mode priority 0 disabled
EFO-MP-T EFO mode priority time 0 not used
EFO-SD EFO signal devices 4 constantly on (during recall phase)
EFO-BUZ EFO buzzer operation for 0 no buzzer at TCI/ERO
EN81-72
ASL-P Alternate Service Landing 255 disabled
EFS-TY Type of Emergency Fire- 10 must be GENERIC !
man
EFS-DO EFS default door 0 Both doors will open
EFSINI EFS initiation of Phase 2 16 when 1EFS operated
EFS-CALL EFS car call handling 0 Nearest Call Wins
EFSCLD EFS close door type 1 car button (constant pressure)
EFSOPD EFS open door type 1 automatically
EFS-EX EFS exit type 1 if not moving and door is open
EFS-RT EFS return time 0 disabled
EFS-RC EFS recall type 32 1EFS off
EF-I-LT EFO/EFS input latching 0 disabled
EN-BAK Enable E2P-backup of 0 disabled
EFO/EFS
HDWPOS Hardware position refer- 0 disabled
ence
Behavior Table:
st nd
device recall operation (EFK) 1 fireman operation 2 fireman operation
(1EFS) (1EFS & 2EFS)
door reversal devices override override override
Emergency Exit Contact override override override
Light Relay (LR) dropped (car light on) dropped (car light on) dropped (car light on)
Moving prevented by override override override
Overload (OLD)
Buzzer triggered by OLD effective override override
Overload Signal (OLS) effective effective effective
door safety chain (DS/GS) effective effective override
Recall Phase (EFK):

The EFK input starts fetching the car to the EFO-P. All calls will be deleted. The buzzer will
be sounded until the door is fully closed (if open before). If the car travelling away from the
designated floor, it will reverse the direction at the next landing without opening the doors
Page: 50 / 196
Berlin
and will go directly to the EFO-P. If the car arrived the EFO-P, the car stays there with open
doors.
1st Fireman Operation Phase (1EFS):

The 1EFS input switches the car into Fireman Service. Only car calls will be accepted. If
none car call operated, the doors will be closed (if not fully open). A car call must be
pushed until the door is fully closed to start a run to a target. If the car is running, other car
calls can be operated. In that case the car will be running to the nearest floor and all car
calls will be deleted after stopping. The doors opens automatically.
2nd Fireman Operation Phase (2EFS):

The 2EFS input activates the 2nd fireman operation phase, where the door safety chain will
be bridged. The 2EFS input is connected to a spring return key switch. The 2EFS key
switch must be held until the run starts. A car call must be pushed for 3 seconds to start a
run to a target. If the door contacts not closed during these 3s, the fireman door bypass
bridge (not the normal door bypass) will be activated. The car call button and 2EFS key
switch must be held until the run starts. With the beginning of the run the buzzer will be
turned off. The doors opens automatically.
Return to Normal operation (NOR):

The sequence “2EFS off, 1EFS off, EFK off at EFO-P” switches back to normal mode.
Alternative: If the car is at the EFO-P position with open doors, 2EFF, 1EFS and EFK can
be switched off together to leave EFS.
Fireman Door Bypass Bridge:

The following contacts will be bridged: EEC (Emergency Exit Contact [car rooof]), ESB
(Emergency Stop Button [COP]), GS (Gate Switch [car door], DS (Door Switch [hwy. door]).
Bypass Outputs:
RSL output for NOR OpMode EFO OpMode EFS OpMode EFS & 2EFS input &
device (recall operation) car call for 3s & DS open
810 DESBR ESB - on - -
812 DEECR EEC - on on on
st
811 DDSR1 DS - - - on, until door opens 1 time
st
974 DDSR2 GS - - - on, until door opens 1 time
(813 DSGSR) spare - - on on
The inputs DEMERC and DDSRC supervises the bypass. In case of a failure the
operational mode NAV will be active (events 0107 or 0108).
Page: 51 / 196
Berlin
Bypass Inputs (expected levels):

RSL output for device not EFO & OpMode EFO OpMode EFS OpMode EFS event #
not EFS (1EFS) (2EFS & DDSR1 (if
(io811) active) failed)
971 DEMERC ESB / EEC high - - - 0108
970 DDSCR GS / DS high high high - 0107
Note : DDSRC(IO970) and DEMERC(IO971) are available in EFS_TYP=12 only. These IOs
are not available any more in other options of EFS-TYP.
Page: 52 / 196
Berlin
2.25 FCL - Full Collective with Car Call Priority Services for Korea
Introduced in GAA30780DAG.
This feature allows that car calls have priority over hall calls. For example, the registered
hall calls shall not be answered even if there are hall calls until the registered all car calls
are servered but additional hall call can be registered. If there is hall call with the same
direction in landing that car is stopped by car call, this hall call will be answered. (This
feature is generally to protect a personal privacy in motel). To enable this feature also
during run, select OPERAT=6. This feature is only for simplex.
Parameter:
1-SYSTEM. OPERAT 0 FCL (Full Collective)
1 DCL (Down Collective)
2 SAPB (Single Automatic Push Button)
3 SAPB with Car Coming Light
4 FCL, delete both calls on arrival
5 FCL with single button for both directions
6 FCL with car call priority services (simplex only)
2.26 HAD - Hoistway Access Detection

If the car door is closed and the hoistway door opens for more than 4s, the OCSS mode
HAD will be activated. When the hoistway door is closed, the car runs to the next floor
(dummy doors and active FPD’s jumped over) with rescue speed and opens the doors for
the DAR-T. Then the car is blocked until ERO, TCI or PES will be activated for more than
4s. Stops inside 1LS or 2LS will never be a target for the rescue run (exception: 2 stop unit).
2.27 HCC - Hall Call Cancel

Introduced in GAA30780DAB.
This feature allows the passenger to delete a hall call if a hall button was accidentally
pushed.
There are two methods to cancel a hall call. Use EN-HCC to select either of these methods:
Page: 53 / 196
Berlin
Parameter:
2-OCSS. EN-HCC 0 Hall call canceling not possible
1 Hall call is deleted if the hall button is pushed once again.
2 Hall call is deleted if the hall button is pushed twice again

(within approximately 1 second).
Note: The hall call shall not be canceled conditions below:

 EN-HCC=1, if re-press the same hall call within 500ms.
 EN-HCC=2, if the interval of between two press hall call is more than 1s for EN, 2s
for JIS.
 If JIS, when EFS mode or there is only one hall call.
2.28 PTC - Penthouse Control

Introduced in GAA30782GAB.
This feature allows penthouse functionality via EMT-mode.
Install-Parameters:
1-System LW-TYP Suitable Load Weighing Device to be selected
2-OCSS EN-EXT 1 Enable extended calls
2-OCSS ANS(kg) To be adjusted for Passenger Detection via LWX
3-GROUP SEL-COMP 3 Select Compatible Communication for GCS_ Systems
8-Emergency EMT-TYP 153 Penthouse function including detection of empty car
8-Emergency EMT-T 10-255 Waiting time for priority run
I/O-Numbers:
7 LWX ANS Load Weight if LW-TYP=2 in car
607 LRD Light Ray Device in car
1338 PDET Passenger Detection Device in car
3900-3999 eEHC 0-99 Extended Emergency Hall Call In/out group
Notes:
 The penthouse entry is required to be a front door.
 For Empty Car Detection either PDET or LWX is required.
 Extended Emergency Hall Calls must be set in the lobby and in the top floor.
 In the allowed mask the eEHC-calls must be setup at the according landings.
Page: 54 / 196
Berlin
General PTC Functionality:

 Protection of the penthouse floor during normal operation is usually realized by a key
switch (disable input to penthouse floor call button).
Penthouse TTL is activated when the call to the penthouse is entered.
 Two buttons for Express Calls eEHC are located at top floor (in penthouse) for top
floor (penthouse) and lobby (for Visitor Pick-Up).
Confirmation light TTL for the Penthouse or Lobby eEHC call is activated when the
according Express Call is entered.
 On Express Call hall calls are ignored (automatic CHCS in EMT mode).
 All pending car calls are served prior Express Call is executed.
 On execution of Express Call empty car is detected by PDET and LWX.
The car waits with open door until car is empty.
As long as the car is occupied, further car calls can be entered and will be served.
Extended Hall Call to Penthouse Floor:
 Express Call eEHC to top floor (in penthouse) is served in EMT mode with priority
considering the above listed PTC functionality.
 In EMT mode the car call (from penthouse floor) is executed with priority (CHCS).
 If EMT-T time is elapsed before any car call is entered the system returns to NOR
mode to serve hall calls.
Visitor Pick-up at Lobby with automatic Call to Penthouse Floor:
 Express Call eEHC to lobby floor is served in EMT mode with priority considering the
above listed PTC functionality.
 When the visitor enters the car, the Express Call eEHC to top floor (in penthouse) is
atomatically executed in EMT mode with priority.
This automatic eEHC is triggered by Light Beam Gate LRD at car door, Load Weigh-
ing signal LWX or Passenger Detection PDET.
Note: Visitors must be instructed to enter only empty cars.
 If EMT-T time is elapsed before anyone enters the car (no passenger detected) the
system returns to NOR mode to serve any calls.
Page: 55 / 196
Berlin
2.29 Stuck Hall Button Detection

A stuck button can occur by the mechanical trouble or intentional operation by passenger
(HB-DOB). Especially, a stuck hall button can frequently occur over against a car call button
and DCB(door close button) and so on. Therefore, we need to separate the detection of
stuck hall button from the detection of stuck button for car call button and dcb, and to add
the adjustable parameter timer (HBDOB-T). The adjustable parameter timer can be used for
discrimination between the mechanical trouble and intentional operation by passenger. For
example, after a car is arrived in a landing with hall call, the corresponding ttl for each call
type to be deleted is switched off, and if an input of hall button still exists until HBDOB-T
expired, a stuck hall button will be detected. In this time, ERR_0112 event (Stuck HB) will
be set as the information event.
For example, if we assume that the max. time for intentional operation by passenger is 3
minutes from experience, we can set HBDOB-T 180seconds. In this case, a stuck hall
button for the corresponding landing can be detected after HBDOB-T.

2-OCSS HBDOB-T 180 HB DOB Delay
10 - 255 seconds until Hall Button
is detected as stuck und function
is canceled
2.30 SHO - Shabat Operation
1. On Shabat day the lifts will run automatically according to a fixed program.
There will be no possibilty to call or to send the car by means of a push button. The car
will stop at any landing as fixed in the program, will wait for a fixed time at the landing
and will then proceed to the next stop automatically.
2. Shabat program will be operated and cancelled by means of a two position key operated
switch (ON-OFF) located at the main floor panel and a contact of an electrical clock
mounted in the controller.
When the key switch is placed in the "ON" position:

 The hall and car call buttons are rendered inoperative.
 The lift will be disconnected from group operation.
 The lift will respond to the existing car calls, afterwards it will return to the main floor,
the door will open and remain open.
Page: 56 / 196
Berlin
 When the electrical clock contact is than closed, the special shabat service will start
and the lift will run and stop at each floor in both directions automatically or when
enabled according to the setup in the special operation allowed mask.
3. The car will be illuminated during the whole time the lift is switched to shabat program.
All signaling lights including the position indicator (optional the PI is not turned off) are
turned off. The only exception are the direction arrows, which will only change whenever
the car has to change the direction in one of the terminal landings.
4. An optional buzzer will inform the passengers two seconds before the door starts to
close and during the door closing.
Page: 57 / 196
Berlin
I/O-Numbers:
666 SHAC Keyswitch to initiate Shabat operation in
667 SHAT Timer to start automatic runs in
668 SHLC Shabat operation Light Car out
751 SHBUZ Shabat door close Buzzer out
752 SHLH Shabat operation Light Hall out
Install-Parameters:
2-OCSS SHO-POS Start Position (Lobby) for Shabat Operation
SHO-PI If set to 1, the PI is disabled during Shabat Operation
SHO-Mask If set to 0, the car will stop at each floor in both directions
and open all doors present at that floor
If set to 1, the SHO Allowed Mask will apply.
5-DOORS SHO-T Adjustable door time for each stop other than main floor
SHO-LT Adjustable door time for stops at main floor
Special Operation Mask:
By pressing M 1 3 3 4 on the service tool , special operation mask can be set up:
The display will look like this:
At SUDFR WUDFR
00 0000 0000
The S stands for Shabat Operation, the W for Wild Car Operation.
The U stands for stop in Up direction
The D stands for stop in Down direction
The F stand for the Front door to be opened
The R stand for the Rear door to be opened
2.31 WDOB/WDCB - Wheel Chair DOB/DCB

This feature is a Japan requirement to extend door time separately for handicapped person.
The doortime for wheel chair DOB (WDOB) is extended to EXT-C.
The other operation is exactly the same with normal DOB/DCB.
Note: This feature is available only for 3-wired door system.
I/O-Numbers:
1166 WDOB Wheel chair Door Open Button 0 in car
1167 WDCB Wheel chair Door Close Button 0 in car
1168 WDOBL Wheel chair Door Open Button Light 0 out car
1169 WDCBL Wheel chair Door Close Button Light 0 out car
1170 RWDOB Wheel chair Rear Door Open Button 0 In car
1171 RWDCB Wheel chair Rear Door Close Button 0 In car
Page: 58 / 196
Berlin

1172 RWDOBL Wheel chair Rear Door Open Button Light 0 out car
1173 RWDCBL Wheel chair Rear Door Close Button Light 0 out car
2.32 Wheel Chair Service (WCS)

If there is an extended car call demands and the IO 1165 WISS input is active (WISS=01 0)
then the car is into WCS mode. In this case, ths car bypasses all hall calls and serves car
calls only.
The doortime for wheel chair DOB (WDOB) is extended to EXT-C.
During the period of wheel chair independent service, either the Independent Lights (INL) or
the Non-Stop Lights (NSL) in the car and hall are on according to parameter setting.
When an extended car button is pressed, standard car call can be simultaneously registered
with parameter CB-EXT=1. Simultaneously registered standard car call can be cancelled by
pressing just extended car button with parameter EN-CK=4, 5.
Install-Parameters:
Group name value Description
2-OCSS INL-TYP 0,1 Independent Light Type
0 INLH light up during ISC
+1 INLH light up during WCS, EHS, EMT
Note: I/O 597 INLH

NSL-TYP 0,1 Non Stop Lamp Type
0 NSLC light up during ATT
NSLH light up during LNS
+1 NSLH light up during WCS, EHS, EMT
Note: I/O 595 NSLC, 741 NSLH

Page: 59 / 196
Berlin
CB-EXT 0-2 Simultaneous registeration/cancellation for stand-

ard/extended car call
0 Registeration - registered separately
Cancellation - both are canceled (with EN-CK=1~3)
Cancellation - canceled separately (with EN-CK=4~6)
1 Registeration
- standard is registered only when standard car call is
pressed
- both are registered when extended car call is pressed
Cancellation
- standard is canceled only when standard car call is
pressed
- both are canceled when extended car call is pressed
2 Registeration - both are registered (with EN-CK=4~6)
Cancellation - both are canceled (with EN-CK=4~6)
Note: CB-EXT=2 is available with EN-CK=4,5,6.
I/O-Numbers:
Wheel Chair Independent Service key
1165 WISS in car EAE
Switch
2.33 Door Open Hold By Trunk Key (DH-Trunk)

When the trunk opens during car stop by TRUNK input from the key contact, the [DHB]
mode is immediately set, and the door open hold time is extended. During the [DHB] mode,
“[DHB]” is displayed on the service tool. This function corresponds to JEAS-A514B
(Standard Revision 03-02) “Standard of Elevator with TRUNK”.
The TRUNK operation methods are regarded as follows.

 The door open time is about 30 seconds at the floor where the elevator stops when
the TRUNK door is opened.
 When the door open button is pressed with the TRUNK door open, the door open
time can be extended about 30 more seconds.
 The car can depart the floor with immediate door close by the door close button
being pressed.
 With TRUNK door open, the elevator operation shall execute as same as the normal
operation.
The door open hold time by TRUNK is about 30 seconds (DHB_TK-T Setting) since TRUNK
input. When the time elapses, the [DHB] mode is reset and the door automatically closes. In
this case, during the period from the door start to close to five seconds before the door
Page: 60 / 196
Berlin
starts to close, overloaded buzzer in the car (BUZ) warns a door closing notice. Moreover,
with or without a buzzer sound before door close can be changeable on the service tool.
When the car call is assigned, before 30 seconds of the door open hold time expires, the
door close button is pressed, the [DHB] mode is reset and the door close is executed. In the
group operation, all assigned hall calls immediately shift to other cars when the [DHB] mode
is set.
Note) This feature cannot correspond to the rear door.
Parameter:
5. DOORS DHB_TK-T 30 Door Open Hold Time for Trunk Key:
0 (1) 254 s
0, 255 Disabled
DS-TKBUZ 0 0: Sound
1: No Sound
I/O-Numbers:
1161 TRUNK Trunk Key switch in car EAE
2.34 Position Recovery after Power Fail

The position recovery needs the following adjustment or hardware:
PCB condition
GECB  SPBx & rescue encoder & DZI or
 PRBB (position retention buffer board) or
 parameter EN-BAK = 1 *
GECB_II  BCB_II/III & rescue encoder or
 parameter EN-BAK = 1 *
LCB_IIC  standard * (not for OVF10/OVF20CRO)
 DZ must be active within 3s after power on
* Position recovery only at DZ, if the car did not move before and during power fail
For EFS and position recovery see chapter 2.22!

Page: 61 / 196
Berlin
3 Energy Saving
3.1 Cut off Position Indicator during Parking Mode

The Position Indicator is switched off while a car is in parking mode by parking key switch
PKS.

2-OCSS PKS-OPT 1 Position Indicator in Parking mode
0: Position Indicator stays on
1: Position Indicator is switched off
3.2 Door Power Save

Introduced in GAA30780DAH.
When the doors are idle for 1 minute, the door system deenergizes the motor to reduce
energy consumption.
Depending on the door mechanic, the software can be configured to deenergize the door
motor while the door is closed, opened or both.

5-DOOR DOOR-PWR 1,2,3 0 no power save mode
1 power save mode while door is fully closed
2 power save mode while door is fully opened
3 power save mode while door is fully closed or opened
If the safety chain opens while the CLOSED door is deenergized, the door is commanded to
close so that the safety chain is closed again. This is necessary to reliably detect HAD.
If this occurs 3 times at the same floor, the event “0323 FDOOR /Deen” is logged and the
Door-Energy-Saving feature for closed doors is disabled until the current floor is left.
At another floor, the Door Energy Saving feature is enabled again.
If the car door leaves the OPENED position (e.g. DOL signal is lost), the car door shall be
commanded to open again to avoid passenger annoyance.
If this occurs 3 times at the same floor, the event “0324 RDOOR /Deen” is logged and the
Door Energy Saving feature for opened doors is disabled until the current floor is left.
At another floor, the Door Energy Saving feature is enabled again.
Page: 62 / 196
Berlin
3.3 Drive Power Save

After an adjustable time, the Drive package is commanded to switch off its power section.
When a demand is registered, the drive is switched on again.

4-DRIVE PDR-D 4 - 42 Minutes
Until GAA30780DAG, the lower limit of PDR-D was 15 minutes.

Since GAA30780DAH, the lower limit of PDR-D is 4 minutes.
3.4 LR - Car Light

After an adjustable time, the car light is switched off.

1-SYSTEM LR-T 20 Time after which the car light is switched off.
LR-MODE 0, 2 0 LR-T is in “seconds”. Used for LED lamps
2 LR-T is in “minutes”. Used for flourescent lamps which are
not allowed to be switched too often.
3.5 RGEN - Regenerative mode display

Regenerative mode display is used to display how much energy saving is on thru
regenerative operation. This function is valid since GAA30780DAK
3.5.1 Set Up Parameters

2-OCSS RGEN_TYP 1 Type of regenerative status display
0 Disabled
1 Direct level direct port control (level 3 => port 3)
2 Decoded level bit control(level 3 => port1 & 2 on, others off)
RGEN_LVL 1 Level count of regenerative status display
0 Disabled
1-100 Level display(0:no regenerative, level range=100%/level
count)
Page: 63 / 196
Berlin
3.5.2 Setup I/O

1238 RGEN_D1 Regenerative mode display output port1 out car
3.5.3 Example
Example of parameter setup: On/off status display correspondent to regenerative status by
using RGEN_D1. Less than 2% was considered as no regerative status regarding of vari-
ance.
RGEN_TYP=1, RGEN_LVL=1: range between levels = 100% (100%/RGEN_LVL (1))
Port ID(RGEN_xx)
Regenerative
Level
status
D1 D2 D3 D4 D5 D6 D7 D8 D9
0 ~ 2% 0 off off off off off off off off off
3 ~ 9% 1 on off off off off off off off off
90% ~ 1 on off off off off off off off off

Page: 64 / 196
Berlin
Example of parameter setup: 10 level lamp control

RGEN_TYP=1 & RGEN_LVL=10: range between levels = 10% (100%/RGEN_LVL (10))
Port ID(RGEN_xx)
Regenerative
Level
status
D1 D2 D3 D4 D5 D6 D7 D8 D9
11 ~ 20% 2 off on off off off off off off off
21 ~ 30% 3 off off on off off off off off off
31 ~ 40% 4 off off off on off off off off off
41 ~ 50% 5 off off off off on off off off off
51 ~ 60% 6 off off off off off on off off off
61 ~ 70% 7 off off off off off off on off off
71 ~ 80% 8 off off off off off off off on off
81 ~ 90% 9 off off off off off off off off on
91% ~ 10 off off off off off off off off on
Example of parameter setup: 10 level digital display control

RGEN_TYP=2 & RGEN_LVL=10: range between levels = 10% (100%/RGEN_LVL (10))
Port ID(RGEN_xx)
Regenerative
Level
status
D1 D2 D3 D4 D5 D6 D7 D8 D9
11 ~ 20% 2 off on off off off off off off off
21 ~ 30% 3 on on off off off off off off off
31 ~ 40% 4 off off on off off off off off off
41 ~ 50% 5 on off on off off off off off off
51 ~ 60% 6 off on on off off off off off off
61 ~ 70% 7 on on on off off off off off off
71 ~ 80% 8 off off off on off off off off off
81 ~ 90% 9 on off off on off off off off off
91% ~ 10 off on off on off off off off off

Page: 65 / 196
Berlin
4 Security Functions
4.1 Overview
The system provides a wide variety of security methods in an attempt to cover the needs of
as many building configurations as possible. The following sections shall provide an over-
view to the different security methods available.
 Car Call Card Reader Operation (CRO)

 Hall Call Card Reader (HCRO)
 Car Security Access (SAO)
 Car Call Cutoff
 Hall Call Cutoff
 EMS Security Options
4.2 CRO - Car Call Card Reader Operation
Most important is now the support of full selective operation. The CRS n inputs follow now
the OTIS 2000 opening counting scheme (like the hall calls) and are fully selective.
The Card Reader Mask has been expanded to allow more options:
The 1st line of the SV display looks like this now
CLD- CLD-
The C bit, if set, determines that this car call is always enabled, regardless of the state of
any of the card reader inputs.
The L bit, if set, forces the car to the lobby, if the DOB is operated when the car is stationary
at a landing with the respective door closed.
The D bit, if set, enables the DOB even if the door is closed, any setting of the L bit is ig-
nored.
Page: 66 / 196
Berlin
Install Parameters:
9-SECURITY EN-CRO 0 no card reader operation
1 card reader via CRC contact, applies to all landings with the
C bit not set to 1
2 card reader via CRS n contacts, applies to all landings with
the C bit not set to 1
3 combination of 1 and 2, so both CRC and CRS n can be
used at the same time
Note: If the CRSn input is set to 00-0, then the correspond-
ing floor is secured.
4 no card reader operation
5 like 1, but ISC will override any CRS security
I/O-Numbers:
639 CRC general card reader contact in
665 BOS Boss override inputs, overrides CRS n contacts, not CRC contact in
1020 LDOS Lobby Door Open Switch, determines the door to open when return- in
ing to the lobby because of DOB at secured landing input low =
front door, high = rear door
480 - CRS00 - Card Reader Security (Car) for Floor 0-31 in
511 CRS31
4632 CRS 32 Card Reader Security (Car) 32 in
... ... ... ...
4699 CRS 99 Card Reader Security (Car) 99 in
Page: 67 / 196
Berlin
4.3 HCRO - Hall Call Card Reader
Several options can now be set for the SECxx inputs:

 EN-HCRO=1..3 selects that the inputs work as card reader inputs, enabling the ac-
ceptance of hall calls.
 EN-HCRO=5..7 selects that the inputs work as security inputs, disabling hall calls and
deleting them if the corresponding landing is secured.
Install Parameters:
GROUP 9-SECURITY
EN-HCRO description normal hall EHC calls
calls
0 no card reader operation always allowed always allowed
1 normal hall calls only if SEC n input is operated, if SEC operated always allowed
EHC calls are always allowed
2 EHC calls if SEC n input is operated, normal calls always allowed if SEC operated
are always allowed
3 all hall call types only if SEC n input is operated if SEC operated if SEC operated
4 no security operation always allowed always allowed
5 if SEC n input is operated, normal hall calls are SEC disable always allowed
disabled
6 if SEC n input is operated, EHC calls are disabled always allowed SEC disable
7 if SEC n input is operated, all hall call types are SEC disable SEC disable
disabled
Note:
 “if SEC operated ” means that the SEC input for the corresponding opening must be op-
erated to enter a hall call at that opening.
 “SEC disable” means that the hall call is disabled when the SEC input for that opening is
operated. An existing hall call will be deleted.
I/O-Numbers:
1022 HCRC allows access to all landings when operated in
512 - SEC 00- Card Reader Security (Hall) for Floor 0-31 in
543 SEC 31
4732 SEC 32 Card Reader Security (Hall) 32 in
... ... ... ...
4799 SEC 99 Card Reader Security (Hall) 99 in
Page: 68 / 196
Berlin
4.4 CCO - Car Call Cutoff
Activation of this feature shall disable all car calls for the standard as well as the extended
call set. The car remains in the group. The switch can be located on the car or hall link.
I/O-Numbers:
610 CCOC Car Call Cutoff from Car in car
Default = 01-0
611 CCOH Car Call Cutoff from Hall in hall
Default = 01-0
4.5 HCO - Hall Call Cutoff
Activation of this feature shall disables all hall calls (Up, Down, EHS) for the standard as
well as the extended call set. The car remains in the group. The switch can be located on
the car, hall, or group link.
I/O-Numbers:
746 HCOC Hall Call Cutoff from Car in car
Default = 01-0
612 HCCO Hall Call Cutoff from Hall in hall
Default = 01-0
613 GCCO Group Call Cutoff in hall
Default = 01-0
4.6 CHCS - Cutoff Hall Call Switch
Activation of this feature shall disable all hall calls (Up, Down, EHS) for the standard as well
as the extended call set. Car calls are allowed.
When the car has no further demand, it parks with a door open at the last landing served.
The car is removed from group operation and the mode shown is CHCS. The operation can
be activated via a toggle switch on the car link.
I/O-Numbers:
618 CHCC Cutoff Hall Call from Car in car
Page: 69 / 196
Berlin
4.7 EMS Security Options
Several choices can now be setup for landings secured via EMS
Install Parameters:
9-SECURITY EMS-SEC 0 no options enabled
1 ISC overrides EMS security of car calls
2 pending calls are not cleared when landing is se-
cured
3 options 1 and 2 together
4 EMS security mask is not cleared if EMS goes offline
7 options 1, 2 and 4 together
For Australia a new input has been included to allow maintenance personal the access to the termi-
nal landings. When this input is operated, all call cut off and EMS security functions related to the
terminal landings are cancelled.
I/O-Numbers:
1021 MAS Maintenance Access Switch in
4.8 Hong Kong Anti Burglar Operation
This feature is available since GECB software version GAA30780DAC
A 3 position key switch will put the lift to Anti Burglar Operation, returning it non-stop to a
predetermined landing and keeping it locked with doors closed until the Door is commanded
to open via the 3rd position of the key switch.
During this mode of operation, the service tool displays ‘ROT’ as operational mode.
Install Parameter (Security):

9-SECURITY RIOT-P must be set to the desired Anti Burglar return land-
ing.
I/O-Numbers:
1041 ADON Anti Burglar ON switch in
1042 ABDO Anti Burglar Door Open switch In
Page: 70 / 196
Berlin
4.9 SAO - Car Security Access Operation
4.9.1 Description
Each car floor button should be able to be secured, unsecured or cleared. If a car floor but-
ton is secured, it will not register a call unless a 3 digit access code is correctly entered on
the car call buttons within a specific time period after the secure car button is pressed.
When a car call to a secured landing is attempted, the "landing secured" lamp in the COP
will be illuminated. This lamp will remain illuminated for a 5 second time period, or until a
valid access code is entered.
Selection and changing of the floor access codes and secured states shall be done on the
car operating panel using the Car Secure Access key switch.
Activation of unsecured but not cleared landings shall be done using the Group Secure Ac-
cess key switch, located in the hall or lobby. This activation is acknowledged by the illumina-
tion of the "group secured" lamp in the hallway.
Depending on the secured state selected, a landing can be always secured or only be se-
cured as long as the Group Secure Access key switch is active.
During the entry of a 3-Digit code any pressing of a car call button to be used for code entry
will be acknowledged by a Car Secure Access Buzzer.
The master code (parameter D1-3) allows access to all secured landings.
4.9.2 Definition of Terms
Landing code assigned: If Group Secure is ON, the landing code must be entered to ac-
cess the landing.
Landing is secured: The landing code must be entered in any case to access the
landing.
Page: 71 / 196
Berlin
4.9.3 Handling
Assigning an access code to a landing:
1. Place the Car Secure Access key switch in the SECURE position.
2. Press the car button of the landing to be secured.
3. Use up to six car buttons to enter the 3-digit master access code.
4. Use up to six car buttons to enter the 3-digit landing access code desired.
5. Release the Car Secure Access key switch.
The landing is now prepared to be secured. If the Group Secure Access is active, the
landing can only be accessed by entering the access code.
Clearing an access code from a landing:

1. Place the Car Secure Access key switch in the CLEAR position.
2. Press the car button of the landing to be cleared.
3. Use up to six car buttons to enter the 3-digit master access code.
The landing is now unsecured and can be accessed normally.
Changing a landing to a secured state:

1. Place the Car Secure Access key switch in the SECURE position.
2. Press the car button of the landing to be secured.
3. Use up to six car buttons to enter the 3-digit landing access code.
The landing is now secured regardless of the state of the Group Secure Access key
switch and can only be accessed by entering the access code.
Changing a landing to an unsecured state:

1. Place the Car Secure Access key switch in the CLEAR position.
2. Press the car button of the landing to be unsecured.
3. Use up to six car buttons to enter the 3-digit landing access code.
The landing is now prepared to be secured. If the Group Secure Access is active, the
landing can only be accessed by entering the access code.
To active Secure Access operation for unsecured landings:

1. Place the Group Secure Access key switch in the ON position.
2. All landings that have an access code assigned will now be only accessible with the
proper landing access code.
To deactivate Secure Access operation for unsecured landings:

1. Place the Group Secure Access key switch in the OFF position.
Page: 72 / 196
Berlin
2. All landings that have an access code assigned and are in the unsecured state will now
be accessible by all passengers.
3. All landings that are in the secured state will still be only accessible with the proper land-
ing access code.
4.9.4 Setup
I/O-Numbers:
761 CSA1 Car Secure Access Button 1 in
767 CSAC Car Secure Access Clear Key switch in

768 CSAK Car Secure Access Secure Key switch in
769 CSAL Car Secure Access Lamp out
770 GSAK Group Secure Access Key switch in

771 GSAL Group Secure Access Lamp out
961 CSABUZ Car Secure Access Buzzer out
Install Parameters:
9-SECURITY SACTYP 0 SAC is disabled
1 SAC is enabled, ISC will not override SAC
3 SAC is enabled, ISC will override SAC
5 SAC is enabled, ISC will not override SAC, landings can
only be cleared if security is in operation (GSAK on)
7 SAC is enabled, ISC will override SAC, landings can only
be cleared if security is in operation (GSAK on)
SAC-D1 SAC Master Code Digit 1
The signals CSA1 - CSA 6 are normally programmed to the same address and pin as the
Car Buttons used for Floor 1 - 6 (CB1-CB6).
The CSAC and CSAK signals are connected to a 3-position keyswitch located in the COP
and the CSAL signal is an indicator lamp located in the COP.
The CSABUZ is an buzzer also located in the COP.
The GSAK and GSAL signals are normally located in the hall.
Page: 73 / 196
Berlin
4.9.5 Limitations
This operation currently can only be used for single COP units, but Full Selective, Semi Se-
lective or Double Door Operation is possible.
The I/Os CS1-CSA6 may not be mapped to rear car calls.
4.10 PET Operation
4.10.1 Operation
Objective of PET operation is to prevent passenger accompanied by a pet in the car from
any passengers who feel uncomfortable with any pet animals by notifying prevent
passenger accompanied by a pet in the car to users at landing.
1. Control of PET operation consist of

1) Control PET button which is used to initiate PET operation
2) Control PET DHB which is used to extend door open time
3) Control PET fan which is used to operate specific FAN to refresh air
4) Control PE lamp which is used to notify passenger accompanied by a pet in the
car
2. 4 types of PET operation available thru parameter setting

1.1 General operation
When pushed PET button or PET DHB, PET call input hold timer is active and turn on
PET buttons for PET call input hold time (PET-SWNT).
When pushed PET DHB, door open hold time is extended to PET-SWNT.
1.2 TYPE 1 operation

1) PET call can be set to the newly pushed first call within PET call input hold time
since pushed PET button or PET DHB.
2) Turn on PET buttons when pushed PET buttons or PET DHB and turn off PET
buttons when pushed first call
3) Turn on PET lamp when set PET call to the newly pushed first call and turn off
PET lamp after served the newly pushed first call
Page: 74 / 196
Berlin
4) Turn on PET fan when set PET call to the newly pushed first call and turn off PET
fan after PET-FNT sec since served the newly pushed first call.

1) PET call can be set to the newly pushed first call within PET call input hold time
since pushed PET button or PET DHB.
buttons when served all car calls.
3) Turn on PET lamp when pushed PET button or PET DHB and turn off PET lamp
after served all car calls
4) Turn on PET fan when set PET call to the newly pushed first call and turn off PET
fan after PET-FNT sec since served PET call

1) PET call can be set to all assigned car calls when pushed PET button or PET DHB.
4) Turn on PET fan when pushed PET button or PET DHB and assigned call exist
and turn off PET fan after PET-FANT sec since served PET call

1) PET call can be set to all assigned car calls when pushed PET button or PET DHB
and newly pushed first call.
4) Turn on PET fan when pushed PET button or PET DHB and assigned call exist
and turn off PET fan after PET-FANT sec since served PET call
4.10.2 Setup
IO-Numbers:
no. name description since def type loc
Page: 75 / 196
Berlin
1277 PET_BT1 Pet function trigger button input1 EAE 0 in car

1280 PET_DHB1 Pet function door open NT expand input1 EAE 0 in car
1283 PET_BL1 Pet button detect active lamp1 EAE 0 out car
1286 PET_DHL1 Pet door hold status lamp1 EAE 0 out car
1289 PET_FAN Pet function FAN control relay output EAE 0 out car
1290 PET_LAMP Pet mode output EAE 0 out hall
Install Parameters:
8- SECURITY PET-TYP 0-4 Enable PET function:
0 Disabled
1 PET TYPE 1
2 PET TYPE 2
3 PET TYPE 3
4 PET TYPE 4
PET-NT 0-25 PET switch enable interval & door open NT timer:
0 Disabled
1 (1) 25 (sec)
PET-FANT 0-255 PET fan activating delay timer:
0 Disabled
1 (1) 255 (sec)
Page: 76 / 196
Berlin
5 Drive Related Setup
5.1 Drive OverHeat

5.1.1 Feature Description

In case of a failure (Drive OverHeat signal from Drive) the car stops at the nearest floor,
deletes all calls, opens door for DAR-T, then closes the door. New calls will not be
accepted. Only the DOB is operating.
When the drive overheat is detected while the car is parking, the door once opens and then
closes at the door time of DAR-T timer, then the elevator halts. In this time, the inspection
mode is invalid.
If the drive overheat is recovered during running the car is running to the nearest floor, the
car stops at the nearest floor. While the door is opening at the nearest floor, the "PLEASE
EXIT" light (GOL) flickers.
If the drive overheat is canceled during the halt, the car is immediately restored to the
normal operation. During the drive overheat, "[DBF]" is displayed on the service tool.
When the drive overheat lasts for 10 seconds or more, a Car Failure Signal (CFS, SCFS) is
generated. While the car is halting and waiting for recovery, the No Operation (NOL) lights
and a call can not be assigned. During the halt, the light and fan in the car are held operated
and not stopped.
5.1.2 Setup
I/O-Numbers:
1208 NOL No Operation Lamp out hall
1209 CFS Car Failure Signal out hall
1210 SCFS Subsidiary Car Failure Signal out hall
5.1.3 Failure Handling

Event:
Event Description
0251 DrvOverHeat When the drive overheat signal is received from Drive thru CAN bus.
 Check GDCB events
Blink Message:
Page: 77 / 196
Berlin
Message Description
>DrvOvrHeat When the drive overheat signal is received from Drive thru CAN bus.
 Check GDCB events
5.2 ETS - Emergency Terminal Slowdown with Safety Switches

(PX2.1=2)
In accordance with the code requirements elevators with a speed higher than 2.5 m/s and
short buffer stroke must have an Emergency Terminal Slowdown circuit to control the speed
during the deceleration in the top and bottom floor. The speed is measured with two
independent systems: the GDCB and the ANSI Speed Check Board (ASCB).
2 channels (A and B) from the 3 channel speed encoder are connected to the GDCB Board,
and 1 channel ( C ) is connected to the ANSI Board.
The GDCB Board calculates the speed via channel A and B of the encoder and sends an
appropriate message depending on the parameter ETP SpE %DutySpe to the GECB which
in turn activates the ETS1 relay.
The ASCB calculates the speed via channel C of the speed encoder and activates the ETS2
relay.
The switching point of the ETS1 and ETS2 relays is usually 80 % of the contract speed. If
the speed is less than 80 % the ETS1 and ETS2 relays are energised and bridges both ETS
control switches SS1 and SS2 (see wiring diagram) in the stopbox mounted on top of the
car.
5.2.1 Parameter and limit switch set up

Check the following parameter with the Service Tool:
 To activate the ETS function the parameter “PX2.1” in the GECB must be set to 2 to en-
able the use of the PX2.1 output for the ETS1 relay.
 The IO-Numbers 576 UP and 577 DN must be set to the approbiate adress/pin of the
remote station where the U and D relays are connected.
 In the GDCB the parameter “ETP Spe %DutySpe” should be set to 80
 Select from the following table the SS1, SS2 limit switch distances.
5.2.2 Velocity parameter and SS1/SS2 limit switch distances
VELOCITY NORMAL SS1/SS2 Dist.

[mm/s] [mm]
2500 1500
3000 2400
3500 3500
Page: 78 / 196
Berlin
4000 4500
Table 5-1: SS1/SS2 limit switch distances

Page: 79 / 196
Berlin
5.2.3 Setting of the ETS2 relay trip point
The ANSI Speed Check Board (ASCB) should now be set up to a preliminary setting (which
will be very close to the final setting. Only the SP (ETS2 relay) output of the ASCB is used,
the SC circuit is not connected. Above a selectable percent of contract speed (usually 80 %)
the ETS2 relay will be de-energised.
SC ETSC VTR
Led´s
U2 U3 F3 Pin 1
4A/250V
J1
F2
1A/250V
F2
1A/250V
SW1 SW2 SW3 SW4
J3 SC SP J2 Pin 2
Setpoint Setpoint
Figure 5\1: ANSI Speed Check Board
ASCB on Board Led´s
When the car is on idle, the ETSC Led´s on the ASCB should be lit, and the ETS2 relay
should be energised. If the car starts and reach 80 % of contract speed the ETSC Led
should be off and the ETS2 relay de-energised.
The VTR Led should be off. When the car starts to move, the VTR Led on the ASCB should
begin blinking. The blinking rate will increase as the car speed increases until the VTR Led
appears to be constantly.
The SC Led is not used.

Page: 80 / 196
Berlin
5.2.4 Calculation of the SP value

Use the following formula to determine the setting of SP:
With VELOC ETSD = 0.8 * VELOC NORMAL
The RPM value can be found by looking at the parameter MOTOR SPEED.
1024 PPR encoder 4096 PPR encoder 8000 PPR encoder

192545 48120 24646
SP= 255 - ---------- SP= 255 - ---------- SP= 255 - ----------
RPM RPM RPM
Convert the decimal SP to their hexadecimal value with following table.
Conversion table decimal into hexadecimal
SW4  SW3 
hex 00h 10h 20h 30h 40h 50h 60h 70h 80h 90h A0h B0h C0h D0h E0h F0h
00h 00 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
01h 01 17 33 49 65 81 97 113 129 145 161 177 193 209 225 241
02h 02 18 34 50 66 82 98 114 130 146 162 178 194 210 226 242
03h 03 19 35 51 67 83 99 115 131 147 163 179 195 211 227 243
04h 04 20 36 52 68 84 100 116 132 148 164 180 196 212 228 244
05h 05 21 37 53 69 85 101 117 133 149 165 181 197 213 229 245
06h 06 22 38 54 70 86 102 118 134 150 166 182 198 214 230 246
07h 07 23 39 55 71 87 103 119 135 151 167 183 199 215 231 247
08h 08 24 40 56 72 88 104 120 136 152 168 184 200 216 232 248
09h 09 25 41 57 73 89 105 121 137 153 169 185 201 217 233 249
0Ah 10 26 42 58 74 90 106 122 138 154 170 186 202 218 234 250
0Bh 11 27 43 59 75 91 107 123 139 155 171 187 203 219 235 251
0Ch 12 28 44 60 76 92 108 124 140 156 172 188 204 220 236 252
0D h 13 29 45 61 77 93 109 125 141 157 173 189 205 221 237 253
0E h 14 30 46 62 78 94 110 126 142 158 174 190 206 222 238 254
0F h 15 31 47 63 79 95 111 127 143 159 175 191 207 223 239 255
Table 5\2: Conversion table decimal into hexadecimal
Example: If you convert 85 decimal to hexadecimal look into the horizontal and vertical
hex field, add both values and set appropriate the SW3 and SW4 switch.
50h + 05h = 55h = 85d

Page: 81 / 196
Berlin
5.2.5 Function test of the ETS relays

After setting up the GDCB and the ASCB speed limits runs with contract velocity can be
performed.
During a high speed run with contract velocity the ETS relays must energise or de-energise
at the same time. If the switch time of both relays is not within 1 second it will cause ETS
stops.
If the ETS2 relay does not drop out at the same time as the ETS1 relay, increase the setting
of the SW4 switch one setting at a time. If switch SW4 is set to F, move it to the „0“ position
and set SW3 up to one position.
To adjust the stopswitches SS1, SS2 you have to run the car with contract speed into the
top or bottom floor.
The adjustment screws for the SS1, SS2 switches must be turned further after every run
(approx. ½ turn) until the exact switch point is found and the elevator makes an ETS stop.
Then the adjustment screw has to be turned back approx. ½ turn and then fixed.
Page: 82 / 196
Berlin
5.3 ETS - Emergency Terminal Slowdown with Reed Switches

(PX2.1=4 or 5)
In accordance with the code requirements elevators with a speed higher than 2.5 m/s and
short buffer stroke must have an Emergency Terminal Slowdown circuit to control the speed
during the deceleration in the top and bottom floor. The speed is measured with two
independent systems: the GDCB and the ANSI Speed Check Board (ASCB).
2 channels (A and B) from the 3 channel speed encoder are connected to the GDCB Board,
and 1 channel ( C ) is connected to the ANSI Board.
The GDCB Board calculates the speed via channel A and B of the encoder and sends an
appropriate message depending on the parameter(s) “ETP Spe %DutySpe” (and “ETP2
Spe %Duty” for 2-step ETSD) to the GECB which in turn activates the ET_S1 (and ET_S3
for 2-step ETSD) relay(s).
The ASCB calculates the speed via channel C of the speed encoder and activates the
ET_S2 (and ET_S4 for 2-step ETSD) relay(s).
If the speed is less than “ETP Spe %DutySpe”, the ET_S1 and ET_S2 relays are energised
and bridge both ET_P1 and ET_P2 contacts in the safety chain (see wiring diagram). Simi-
larly, for 2-step ETSD, if the speed is less than “ETP2 Spe %Duty”, the ET_S3 and ET_S4
relays are energised and bridge both ET_P3 and ET_P4 contacts in the safety chain
5.3.1 Parameter and limit switch set up

Check the following parameters and IOs with the Service Tool:
For 1-step ETSD:

 To activate the 1-step ETSD function the following GECB parameter must be configured:

PX2.1 Defines PX2.1 output 4 Output used as ET_S1 (1-step)
 The following GECB IO-Numbers must be set to the appropriate adress/pin of the remote
station where the corresponding relays are connected and inverted.

st
1257 ET_P1 1 step terminal zone position reed switch 1 in
st
st
1259 ET_S1 1 step SW-controlled speed relay in
st
1260 ET_S2 1 step ASCB-controlled speed relay in
 In the GDCB the parameter “ETP Spe %DutySpe” should be set appropriately.
 Select from the table below the ET_P1/ET_P2 sensor distances.
Page: 83 / 196
Berlin
For 2-step ETSD:

 To activate the 2-step ETSD function the following GECB parameters must be config-
ured:

PX2.1 Defines PX2.1 output 5 Output used as ET_S1 (2-step)
PX2.2 Defines PX2.2 output 1 Output used as ET_S3
 The following GECB IO-Numbers must be set to the appropriate adress/pin of the remote
station where the corresponding relays are connected and inverted.

st
st
st
st
nd
nd
nd
nd
 In the GDCB the parameter “ETP Spe %DutySpe” and “ETP2 Spe %Duty” should be set
appropriately.
 Select from the table below the ET_P1/ET_P2 and ET_P3/ET_P4 sensor distances.
5.3.2 Setting of the ET_S2 and ET_S4 relay trip points
1. temporarily set the Drive ET_S2 switching percent, "ETP Spe %DutySpe", and the
ET_S4 switching percent, "ETP2 Spe %Duty", to 100%, "ETP Delta %" to 1
2. set the ET_S2 knobs (labelled "SP") and the ET_S4 knobs (labelled "SC") on the ANSI
speed check board to 0xF0
3. set Drive "Nom speed" to the desired ET_S2 switching percent of duty speed, for exam-
ple, if the desired ET_S2 switching percent is 80% and the duty speed is 4000, set "Nom
speed" to 3200
4. perform run from bottom terminal to top terminal
4.1. during constant speed, turn the first hex character knob slowly decreasing until the
ET_S2 relay opens and stays open (no flickering). Note that an ESTOP may occur
when reaching the terminal zone
5. set the second hex character knob to "F", for example, if the relay opened at 0xA0, set
the knobs to 0xAF
6. perform run from top terminal to bottom terminal
6.1. during constant speed, turn the second hex character knob slowly decreasing until
the ET_S2 relay opens and stays open (no flickering), e.g., 0xA5.
7. ET_S2 is now adjusted, repeat steps 3 through 6 for the ET_S4 adjustment using the SP
knob, if 2-step ETSD is desired
Page: 84 / 196
Berlin
8. set Drive "Nom speed", "ETP Spe %DutySpe" and "ETP2 Spe %Duty" to the correct
desired settings
9. set Drive "ETP Delta %" to 2
SC ETSC VTR
Led´s
U2 U3 F3 Pin 1
4A/250V
J1
F2
1A/250V
F2
1A/250V
SW1 SW2 SW3 SW4
J3 SC SP J2 Pin 2
Setpoint Setpoint
Figure 5\2: ANSI Speed Check Board
ASCB on Board Led´s
In a 1-step or 2-step ETSD system:

When the car is idle, the ETSC Led on the ASCB should be lit, and the ET_S2 relay should
be energised. If the car starts and reachs "ETP Spe %DutySpe" percent of contract speed,
the ETSC Led should be off and the ET_S2 relay de-energised.
In a 2-step ETSD system:

When the car is idle, the SC Led on the ASCB should be lit, and the ET_S4 relay should be
energised. If the car starts and reachs "ETP2 Spe %Duty" percent of contract speed, the SC
Led should be off and the ET_S4 relay de-energised.
The VTR Led should be off. When the car starts to move, the VTR Led on the ASCB should
begin blinking. The blinking rate will increase as the car speed increases until the VTR Led
appears to be constantly.
5.4 RPD-P2 - Low Cost Single Position Sensor

Page: 85 / 196
Berlin
This PRS is supported since GECB software version GAA30780DAC.
Basically this type is same as DZ-TYP = 0 but the status of on-off from sensor is inverted.
Install Parameters:
6-POS.REF DZ-TYP 3 Single door zone sensor (RPD-P2) with inverted signal
5.4.1 Function test of the ET_S1-4 relays

After setting up the GDCB and the ASCB speed limits runs with contract velocity can be
performed.
During a high speed run with contract velocity the ET_S1/2 and the ET_S3/4 relays must
energise or de-energise at the same time. If the opening time of both relays during acceler-
ation is not within 1 second it will cause ETSD blockages. The event 0259 "LateET_S2/4" is
a pre-warning that the ASCB relays are out of adjustment. Event 0259 should never occur.
If it does occur, follow the process in section 5.3.2 to adjust the ASCB properly.
Page: 86 / 196
Berlin
5.5 SMART Charger for “LVA Switch”

The Smart charger works with a different charging algorithm, switching off the recharge
according to the state of charge of the batteries (SoC : max 80%).
The information about running status of the car is provided by GECB_LV (P_SP2.4 output)
as a discrete signal, and it’s adopted by the smart charger to apply the sufficient relaxation
time measuring the state of charge of the traction batteries .
The SMART Charger is connected to the UD output at P_SP2.4, which must be configured
to indicate whether the car is running or not.
Install Parameters:
1-SYSTEM TRIC-TYP 0 Counts all runs including RLV, ERO, TCI

Page: 87 / 196
Berlin
5.6 TPOS - Cyclic Parking

The following description applies to GAA30780DAH or later.
Specific types of brake might get stuck if they have not been lifted for a long time. To
prevent that the brake fails to lift, the elevator can be configured to perform automatic runs
between preselected floors after a specified time.
This feature might also be usefull for glass hoistways which are heated by the sun. If the air
in the hoistway gets too hot, the elevator might shut down because of overheat. Cyclic
Parking can help to push the hot air out of the hoistway so that the elevator stays in
operation.
After the time specified by TDELAY and TDEL-TIM, the car will perform an automatic run as
specified below:
TPOS-TYP=0:
The car will run to floor TPOS1. If the car is already parked at that floor, the car will run to
floor TPOS2. These runs are performed by using regular car calls, that means at the end
of this run the car will cycle the doors.
TPOS-TYP=1:
The car will perform a park run to TPOS1 or TPOS2, depending on the last park target. If
the last cycle park target was TPOS1, the car will run to TPOS2 and vice versa.
These runs are performed as regular parking runs (like ARD) without opening the doors.
These runs can be interrupted by call demands at any time.
You can also select TPOS1=TPOS2=255: In this case, the car will perform a park run the
the next floor (if possible, in down direction).
For TPOS1 and TPOS2, you need to select floors which are not secured by any means
(e.g. card reader).
Additionally, you can enable or disable these parking runs with an RSL input. If I/O 1115
EN-POS is not programmed, this feature is always active. If that I/O is programmed to a
valid address/pin, the feature is only enabled if the input is active.
Install Parameters:
10-TEST TPOS 1 0-99 Primary target floor for automatic runs
TPOS 2 0-99 Alternative target floor for automatic runs
TDELAY 0-255 Duration until an automatic run is performed
TDEL-TIM 0 Time base of TDELAY is seconds
1 Time base of TDELAY is minutes
Page: 88 / 196
Berlin
2 Time base of TDELAY is hours

TPOS-TYP 0 With door opening
1 Without door opening
I/Os
1115 EN-TPOS Enable automatic runs by parameter TPOS
Examples
1) After 8 hours, the car shall perform an automatic run to floor 1 and open the doors. If the
car is already parked at floor 1, the car shall instead run to floor 2.
Set the following parameters:
TPOS1 = 1
TPOS2 = 2
TDELAY = 8
TDEL-TIM = 2
TPOS-TYP = 0
2) After 8 hours, the car shall perform an automatic park run to floor 1 without opening the
doors. After another 8 hours, the car shall perform an automatic park run to floor 2 without
opening the doors.
TPOS1 = 1
TPOS2 = 2
TDELAY = 8
TDEL-TIM = 2
TPOS-TYP = 1
3) After 90 minutes, the car shall perform an automatic park run to the next floor in down
direction without opening the doors.
TPOS1 = 255
TPOS2 = 255
TDELAY = 90
TDEL-TIM = 1
TPOS-TYP = 1
Page: 89 / 196
Berlin
5.7 UCM EN81 - Unintended Car Movement

This function is available since GAA30780EAA.
5.7.1 Overview
EN81-1 A3 requires to stop the car and keep it stopped when the car moves out of the
doorzone with the doors not in closed position.
This is achieved by monitoring the door bypass:
When, within the doorzone, the door bypass is active and the door is opened, the UCM
Monitor is activated. It is deactivated when the door is closed and also 160 msec after the
door bypass has been opened.
The UCM Monitor observes whether the door bypass drops while leaving the doorzone.
If such a situation is detected, the elevator is shutdown with OpMode NAV. The event “0234
UCM Detect” is logged and the blink message “>UCM Detect” is shown in the SVT status
display. In the Service Panel, the blink message “Service – UCM Reset” is shown.
The shutdown is memorized even if the power is switched off. Normal operation is resumed
by performing an ERO run.
GECB-Parameter:
Drive DRV-TYP 1 Extended Drive Interface
System UCM-TYP 3 UCM according to EN81-1 A3
Drive-Parameter:
Contract UCM-EN ON/OFF 1 UCM according to EN81-1 A3
Because the UCM configuration is determined during startup, you must switch off and on
the system before changes of the above parameters are taking effect.
Required Software Versions:
Board SCN
GECB GAA30780EAA or later
GDCB (ReGen Drive) AAA30924CAM or later
DCPB (Ultra Drive) AAA31400AAD or later

Page: 90 / 196
Berlin
5.7.2 Handover Test

In the Handover phase, the proper function of the UCM Monitor must be verified. There are
different options to perform this test:
Handover Test via Service Panel

This is done with the Service Panel functions “Handover – Test UCM Up” and “Handover –
Test UCM Down”.
Please refer to the document GAA30780EAN_SP.doc for more information.
Handover Test via Field Tool / Service Tool

Execute the OFT function M-1-4-1 SYSTEM-CHECK-UCMEN81.
Please refer to the document GAA30780EAN_STM.doc for more information.
Handover Test via RSL (UCM3)

This function is available since GAA30780EAD.
Feature name: UCM3
This test is intended for the repetitive verification of the UCM functionality without OFT. It is
not intended for the Handover Test, because there is no indication about proper
redundancy.
In the controller, a keyswitch is provided which is connected to the RSL inputs 1272
UCMEN-UP and1273 UCMEN-DN.
Sequence:
1) Activate the keyswitch “UCM-EN81 Test” in up or down direction for longer than 1
second.
- The controller sets the Opmode LRN and automatically activates DDO and
CHCS.
- The controller prepares to perform the UCM Test
2) Release the keyswitch.
3) Remove testplug “UCM-EN81 Test”.
4) Activate the keyswitch into the desired direction.
- The controller activates the doorbypass and performs the UCM Testrun into
the selected direction.
- After the car has left the doorzone, the safety chain opens and the car is
blocked with “UCM Fault”.
5) Release the keyswitch.
6) Measure the displacement of the car.
7) Insert testplug “UCM-EN81 Test”.
8) Switch to ERO and push UIB or DIB.
Page: 91 / 196
Berlin
- This clears the blockage.
Notes:
- To start a new test, ERO must be activated and deactivated. Also, the keyswitch
must be turned off.
- To resume normal operation, DDO and CHCS must be deactivated by the corre-
sponding service buttons.
Setup:
I/Os
1272 ECMEN-UP Start UCM-Test in up direction
Must be programmed to a valid address
1273 UCMEN-DN Start UCM-Test in down direction
Must be programmed to a valid address
5.7.3 Clearing the UCM Fault

The UCM Fault is cleared by switching to ERO and performing an ERO run.
The Service Panel provides a function “Service – UCM Reset” which guides the mechanic
through these steps.
Page: 92 / 196
Berlin
5.8 UCM Korea - Unintended Car Movement (UCM-K)

Unintended car movement is detected in automatic operation as well as all manual operat-
ing modes. The intent of the code requirements is to provide protection when the movement
is NOT intended to occur. The emergency brake is controlled by both software functions
and hardware devices. To detect such an event while the car is parked at a landing, the
door zone sensors are used. The discrete output port in GECB is used for driving UCM con-
trol relay.
Parameter:
System UCM-TYP 1 0 disabled
1 UCM for Korea
2 UCM for Japan/JIS
3 UCM for EN81 (since EAA)
The operation mode is changed to NAV and UCM event is logged when the GECB receives
the shutdown message from the UCM board.
Event:
Event Description
0234 UCM Detect UCM fault detected when the car has the UCM conditions.
 Check the causes of UCM fault by using <M-M-1-9-4>.
0232 UCMRWelded The UCM relay is stuck.

 Check the relays for UCMCR and UCMR1 & UCMR2.
Blink Message:
Message Description
>UCM Detect UCM fault detected when the car has the UCM conditions.
>UCMRWelded The UCM relay is stuck.

 Check the relays for UCMCR and UCMR1 & UCMR2.
5.8.1 Uncontrolled movement at Door Open Status:

- GDCB will create UCM control signal (On / Off) from door zone and encoder status to
detect unintended car movement and then it is sent to GECB via CAN bus.
- GECB will get the UCM control signal from GDCB via CAN bus.
- GECB will decide UCM detection by UCM control signal from GDCB and door open
status.
- UCMCR(UCM control relay) is powered at UCM condition using discrete output port
in I/O board. The UCMCR is activated when the car moves to the outside of door
zone or the UCM control signal from GDCB is activated during opened door.
Page: 93 / 196
Berlin
- Cutoff Emergency Brake and Brake Power.
5.8.2 Checking the cause of UCM fault
To check the cause of the UCM fault, SVT command <M-M-1-1-9-4> can be used
Display description values
1 Z Missing doorzone with door opens z-Z
UCM-ERR: . 2 D GDCB detects UCM with door d-D

z d n q o c . opens
1 2 3 4 5 6 3 N CAN message is not received from n-N
GDCB for x seconds
4 Q Count data from GDCB is wrong q-Q
5 O UCM relay open error o-O
6 C UCM relay close error c-C
5.8.3 Clearing UCM Fault

UCM fault can be cleared by SVT command <M-M-1-1-9-3>.
It can be also cleared by ERO toggle 3 times within 10 sec.( since GP330780EAC)
NOTE: With Korean UCM(UCM-TYP = 1), the door should be closed and CAN communica-
tion between GECB and GDCB should be available in order to clear UCM fault.
5.8.4 Interface between OCSS and Drive

Operational Control Motion Control
Power On Power On
Initialize system Initialize system
Initialize Operational control Initialize Motion control
Communication control UCM detected Communication control

(receive data and monitoring) (send UCM detection event)
CAN Bus
PRS & gate PRS & encoder

UCM detection UCM detection
switch counter
UCM relay control (output)
Power off Power off

Page: 94 / 196
Berlin
5.8.5 The Detection for UCM Fault

- Operational Control:
If car is in door zone and door opens, car moves out of door zone.
- Motion Control:
If car is in door zone and door opens, moving distances based on rotary encoder
excess defined value.
UCM detected
by Drive
Page: 95 / 196
Berlin
5.8.6 Wiring diagram for UCM relay control
5.8.7 UCM Relay Monitoring:

- UCM relay is currently controlled by the output port on I/O board.
- Additionally, we will use the P_C:2 input port for detection of welded status of UCM
relay.
- The P_C:2 port is connected to another point of contact of UCM relay.
- P_C:2 input will be checked after designated time whether UCM relay is controlled
correctly when the UCM control signal is sent to UCM output port.
Error detection of UCM Relay circuit consists of two discrete UCM Relay. It can detect the
error of UCM Relay to monitor the contact while power ON and UCM detect condition.
Power On
(UCMR Welded)
Page: 96 / 196
Berlin
When power is on, check UCM Relay contact is welded or not. If UCM Relay is welded,
detect error and into the NAV mode.
Normal Mode
(UCM Detect)
(relay delay time)
(UCMR Welded)
If one of two relay is welded when UCM detected condition, cut off brake by another relay.
Then detect UCM relay error, Into the NAV mode.
And if UCM relay is off when UCM is not detected, then detect UCM relay error.
Page: 97 / 196
Berlin
5.8.8 Basic Timing Chart for detecting UCM Fault

Page: 98 / 196
Berlin
5.9 UCM Japan - Unintended Car Movement (UCM-JIS)

Basically the separated UCM board has the logic to detect the UCM fault. The following
operations shall be performed in GECB.
 UCM-J function is available if the parameter UCM-TYP is set to “2”.

Parameters:
1- SYSTEM UCM-TYP 2 0 Disabled
1 UCM for Korea
2 UCM for Japan
3 UCM for EN81
 UCM fault can be canceled by SVT. The GECB sends the cancel command to
UCM board thru CAN when UCM fault cancel command is entered on SVT.
 The operation mode is changed to NAV and UCM event is logged when the
GECB receives the shutdown message from the UCM board.
Event:
Event Description
0234 UCM Detect UCM fault detected when the car has the UCM conditions.
 Check UCM fault conditions.
Blink Message:
Message Description
>UCM Detect UCM fault detected when the car has the UCM conditions.
 Check UCM fault conditions.
>UCMComEr CAN communication fault between GECB and UCM board

 Check CAN line between GECB and UCM board.
 The GECB sends the stop command to the GDCB to stop the car immediately
when the GECB receives timedecel command from the UCM board. In this case,
the car can be stopped in the out of door zone.
 The detail of UCM fault can be displayed in SVT by using “M194”. The SCN of
UCM software on UCM board can be checked on SVT by using “M195”.
Page: 99 / 196
Berlin
SVT command Description

M193 Cancel UCM fault
M194 Detail of UCM fault
M195 SCN of UCM software on UCM board
 The detail of UCM fault can be displayed in SVT by using “M194” as shown below.
Fault Description
UCM No Response No message from UCM board
Door OpenRun Err Door Open Run Fault
Over Speed Err Over Speed Fault in door open run
DZ Senser Err Short mode failure of Door Zone Sensers(1LV and 2LV)
BS Err Consecutive failure of Brake Switches(BS1, BS2)
S-RelayErr Short mode failure of S-relays(S1, S2, S3, BY)
CGS Err Short mode failure of CGS relays(CGS and CGS2)
BypassCircuitErr Short mode failure of Door Bypass Circuit(LV1, LV2, LVC
contacts)
PVT Err Open mode failure of PVT
UCMR Err Short mode failure of UCMR contact
SCR Err Short mode failure of Speed Check Relay
WD Reset Watch dog reset happen and latch up the
system at boot-up
Memory Error Check sum mismatch detected and latch
up the system at boot-up
 The GECB requests UCMR(UCM relay) check to UCM board in the specified
time(use the time based feature activation code – 21) every day.
Parameters:
11- Time TFAx-OP 21 Time Based Feature Operation x:
0 not used
21 UCMR check
Note: Requires that the date/time is set in SVT menu M-1-3-8
TFAx-TYP 1 Type of Time Based Feature Activation x:
0 not used
1 Time Based
2 Week Based
3 Time and Week
TFAx-SHR Contract Start Hour of TBFAx:
0-23 Hour at which the feature defined by TFAx-OP will start
TFAx-SMI Contract Start Minute of TBFAx:
0-59 Minute at which the feature defined by TFAx-OP will start
TFAx-EHR Contract End Hour of TBFAx:
0-23 Hour at which the feature defined by TFAx-OP will end.
TFAx-EMI Contract End Minute of TBFAx:
0-59 Minute at which the feature defined by TFAx-OP will end.
Page: 100 / 196
Berlin
TFAx-WEK 0 Weekday of TBFAx:

Weekday at which the feature defined by TFAx-OP will be activat-
ed.
1 Sunday
2 Monday
4 Tuesday
8 Wednesday
16 Thursday
32 Friday
64 Saturday
Note: If the feature should be activated at more than one day, add
the corresponding
values (e.g. Saturday+Sunday = 65, Monday to Friday = 62)
Page: 101 / 196
Berlin
5.10 6LS - Emulation via Software

The limit switch “6LS” limits the TCI run in up direction to prevent that a field person on top
of car might get trapped in the hoistway.
In the Vector Controller, this hardware switch has been eliminated so that this functionality
is provided by software:
A TCI run in up direction is automatically stopped as soon as 2LS is activated.
5.10.2 Setup
It is important that this function is not unintentionally deactivated when a component is
replaced by a sparepart. Therefore the parameter for this feature is located in GECB as well
as the drive.
Both parameters must be set to enable 6LS software emulation.
GECB Parameter:
Group name Description
4-DRIVE 6LS-TYP Type of 6LS
0 Hardware 6LS wired in safety chain.
1 No physical 6LS switch. Function is emulated in software:
During TCI-Up run, the car will stop at 2LS.
Default: 0
Drive Parameter:
MCB3x (since GAA30785CAG):
Contract 6LS-TYP Type of 6LS
0 Hardware 6LS wired in safety chain.
1 No physical 6LS switch. Function is emulated in software:
During TCI-Up run, the car will stop at 2LS.
Default: 0
GDCB: (not yet available)

Page: 102 / 196
Berlin

If the parameter at the GECB is set to a different value than at the drive, the elevator is
taken out of service, so that the mechanic is forced to correct the setup:
 Opmode DBF is activated
 At a landing the doors are opened for DAR-T seconds, thereafter the doors are closed.
 DOB is operative
 No calls are accepted.
 TCI/ERO is not possible
 event “0250 6LS-TYP!” is logged
 blink message “>6LS-TYP!” is shown in the GECB status menu.
Event:
Event Description
0250 6LS-TYP! The parameter “6LS-TYP” at GECB has a different value than the parameter “6LS-
TYP” at the drive.
 Check GECB Parameter “6LS-TYP”
 Check MCB3/MCB3x/GDCB Parameter “6LS-TYP”
Blink Message:
Message Description
>6LS-TYP! The parameter “6LS-TYP” at GECB has a different value than the parameter “6LS-
TYP” at the drive.
 Check GECB Parameter “6LS-TYP”
 Check MCB3/MCB3x/GDCB Parameter “6LS-TYP”
Page: 103 / 196
Berlin
5.11 Alternate Profiles

The following description applies to GAA30780EAD or later.
Alternate profiles are selectable via the following RSL inputs:
GECB I/Os
1293 APRF1C Alternate Profile 1 – car link
1294 APRF1H Alternate Profile 1 – hall link
The standard motion profile is profile 0 and is used if none of the above inputs is active.
If multiple inputs are active, profile 1 takes precedence, then profile 2, then profile 3.
If an alternate profile input is active before a run begins, the run will be performed with the
corresponding alternate profile.
If an alternate profile input becomes active or changes during a run, the car will stop at the
next committable landing, and then continue on to the target with the new alternate profile.
The profile characteristics (velocity, acceleration, jerk) for the alternate profiles are
programmable via the following Drive installation parameters:
GDCB Install Parameters:

Group name description
Profile Numb AltProfiles Number of Alternate profiles defined (max 3)
Alt1 Speed mm/s Alternate Profile 1 Speed
Alt1 AcDec mm/s2 Alternate Profile 1 Acceleration/Deceleration
Alt1 Jerk mm/s3 Alternate Profile 1 Jerk
Page: 104 / 196
Berlin
6 Door Related Setup
6.1 Generic Door Operator
6.1.1 Introduction
By use of the Generic Door Operator you are not restricted to fixed door operators as
FCO9550 or DO2000, but you can define exactly how a specific door operator is to be han-
dled.
A set of parameters is used to setup the door handling as required by the existing door sys-
tem:
You can define:

 Is the DC relay energized while the door is completely closed?
 Is the DO relay energized while the door is completely opened?
 Is a DOL or DCL contact available?
 Automatic or manual landing doors?
 Has the cam to be pulled while the door is closing?
 How is the cam to be handled during ERO?
 Do we have telescopic landing doors with a cam?
All parameters of the Generic Door Operator can be pre-installed to the profile of already
known doortyps as FCO9550, DO2000 etc. This makes further finetuning more easy (Not
available for OVL!)
Use ServiceTool Menu M-2-4 Setup Door to program the Generic Door Parameters so that
the selected door can be used without further changing of the parameters.
6.1.2 Description of Parameters
LCB_IIC only: Multi Door

To install automatic plus manual landing doors, the parameter MD/AES must be set to ‘1’.
In addition the MD input must be connected to the safety chain after the automatic landing
door contact. The DW input must be connected to the safety chain after the manual landing
door contact. SAF Input sequence: ERO, ES, DW, MD, DFC.
Door Handling
If DOOR=0..10 is selected, all ‘F:****’ parameters are ignored and a fixed door handling is
done.
If DOOR=11 is selected, the parameters ‘F:***’ become active and the door handling is fully
adjustable by these parameters.
The same applies for the parameter REAR and the ‘R:****’ parameters.
Page: 105 / 196
Berlin
CAM Handling
If either DOOR=11 or REAR=11 is selected, the CAM parameters become active.
All ‘xx-TYP’ parameters are designed so that the first digit defines the behaviour of the cor-
responding output during the door movement (i.e. opening or closing, respectively) and the
second digit defines the behaviour during the following stop (i.e. fully opened or fully closed,
resp.)
General Parameters
DOOR, REAR 0..15 doortype at front/rear.
Parameters for Door Handling

F:DO-TYP, R:DO-TYP DO-behaviour
00 DO never active
01 DO active when door is fully opened
10 DO active while door is opening
11 DO active when door is opening and also when opened
F:DC-TYP, R:DC-TYP DC-behaviour

00 DC never active
01 DC active when door is fully closed
10 DC active while door is closing
11 DC active when door is closing and also when closed
F:EN-ACG, R:EN-ACG Type of Hoistway Doors

0 automatic hoistway doors (TLD/CLD)
1 manual hoistway doors (ACG)
F:EN-DCL, R:EN-DCL Limit Switch DCL

0 no DCL
1 DCL at IOs 694/695 (DC is dropped, if DCL is active)
2 DCL at IOs 694/695 (DC stays on even if DCL is active)
F:DOL-D, R:DOL-D Limit Switch DOL

0 DOL at IOs 000/544
1..255 DOL will be simulated by software xx,x seconds after
door has started to open (e.g. FLH, MLI)
Page: 106 / 196
Berlin
Parameters for CAM Handling

CM-TYP CM-behaviour
00 CM never active
01 CM active when door is closed
02 CM active when door is closed and demand exists
(parking with closed doors)
03 CM active when door is closed and delay CM-D has expired
(TLD/CLD with CAM)
10 CM active while door is closing
11 CM active while door is closing or door is closed
21 CM active while door is closing and delay CM-D has expired
(for doors without DCL, because safety chain cannot be
closed if CAM is deenergized).
CM-PROT CM-behaviour during ERO-STOP

0 CM deenergized
1..254 CM is deenergized after xxx0 seconds
255 No protection; CM is always energized
(only for 100%ED!)
SEL-CMR Where is CMR connected?

0 CMR at P6:10 (RDC) (1 car door / only for LCB_IIC)
1 CMR at IO 785 (1 or 2 car doors)
DO-D Time Delay of DO

0..255 DO is energized xx,x seconds after CAM has been
deenergized
For CLD/TLD with CAM
CM-D Time Delay of CM

0..255 CM is energized xx,x seconds after door has been
closed.
CM-OP-D Delay of CM when door is opening

0..255 xx,x seconds delay between pulling DO and dropping
CM (Ignored, if the car door is fully open).
Page: 107 / 196
Berlin
Parameter for TRO Handling

Some dooroperators require to be powered down during TCI. For this purpose the TRO
output is used. It is pulled in normal operation and dropped under the following conditions:
TRO-TYP Type of TRO handling (IO 1107 or LCB_IIC discrete output)

0 no TRO output
1 TRO dropped if TCI is operated (e.g. for DO2000)
(LCB_IIC: TRO at P6:5 (DC))
2 dropped if TCI active without TCIB, TDCB or TDOB
for MLI / Kiekert-2
(LCB_IIC: TRO at P6:7 (DO))
3 same as 2
(LCB_IIC:TRO at P6:5 (DC) for AT20)
Additional Parameters
DOR-T, RDOR-T Time Delay between DO and DC during Reversal Operations.
20..255 During any Reversal (i.e. opening -> closing or
closing -> opening) both DO and DC outputs are
deenergized for xx,x seconds.
For heavy doors
DTC-T Door Time Protection

0..254 duration after which protection starts
255 disabled for parking with closed doors and dropped
cam
Page: 108 / 196
Berlin
6.1.3 Graphical Description
6.1.3.1 Overview
Activation of the generic Parameters
DOOR = 11 F:DO-TYP
F:DC-TYP
F:EN-DCL
F:EN-ACG
F:DOL-D
REAR = 11 R:DO-TYP
R:DC-TYP
R:EN-DCL
R:EN-ACG
R:DOL-D
DOOR = 11
oder CM-TYP
REAR = 11 CM-PROT
SEL-CMR
TRO-TYP
DO-D
CM-D
Page: 109 / 196
Berlin
6.1.3.2 Timing-Diagrams
DO-output
][ <> [] >< ][
DO (DO-TYP=10) 9550, Meiller
DO (DO-TYP=11) Kiekert, MLI
DO (DO-TYP=01)
DC-output
][ <> [] >< ][
DC (DC-TYP=10) 9550, Meiller
DC (DC-TYP=11)
DC (DC-TYP=01)
DCL-input (DC-TYP=10)
[] >< ][
DCL
DFC
DC (EN-DCL=1)
9550
DC (EN-DCL=0)
Page: 110 / 196
Berlin
DOL-input
][ <> []
DOL (DOL-D=0)
DOL (DOL-D<>0) FLH, MCG
DOL-D Signal is
simulated by
software
CMR-output, CM-DELAY
][ <> [] >< ][
CM-OP-D
CMR (CM-TYP=01) ACG with DCL
CM-OP-D call
1 x TLD,n x ACG
CMR (CM-TYP=02) CM-OP-D call or
CM-D
TLD with CMR
CM-OP-D DW CM-D
CMR (CM-TYP=03) TLD with CMR
CMR (CM-TYP=10)
CM-OP-D
CMR (CM-TYP=11) as used without
Generic DoorOp
CM-OP-D CM-D
CMR (CM-TYP=21) without DCL
Page: 111 / 196
Berlin
DO-DELAY
][ <>
CMR
DO-D
DO TLD with CAM
DOR-T
<> >< <>
DOR-T
DO
DOR-T
DC
CM-PROT
ERO-run ERO-stop NOR ERO-stop ERO-run
ERO
run
CMR (CM-PROT=0) 1
CM-PROT CM-PROT
CMR (CM-PROT=100) 2
CMR (CM-PROT=255) only 100%ED!!
see CM-TYP
1: start inside DZ: CM relay must be pushed to close SAF
2: start inside DZ: UIB/DIB must be pushed within CM-PROT
Page: 112 / 196
Berlin
6.1.4 Factory Setup

Door Setup for some door types:
Feature Name DOOR DO-TYP DC-TYP EN-ACG EN-DCL DOL-D CM-TYP CM-PROT TRO-TYP
SLYCMA 11 0 11 note 1 0 40 note 2 note 3 2
DOC12 MLI 11 0 11 note 1 0 40 note 2 note 3 2
Kiekert 11 0 11 note 1 0 40 note 2 note 3 2
DOC19 Kiekert-1 11 11 11 note 1 0 40 note 2 note 3 0
DOC9 Kiekert-2 11 0 11 note 1 0 40 note 2 note 3 2
DDC
DOC20 AT20 11 11 0 note 1 0 40 note 2 note 3 3
DOC25 AT25 (old) 11 11 0 note 1 1 0 note 2 note 3 3
DOAT25 AT25 (new) 11 11 11 note 1 0 0 note 2 note 3 0
Fedo 11 0 11 note 1 0 40 note 2 note 3 2
DO2000, DCSS4 11 11 0 note 1 0 0 note 2 note 3 note 4
DO-1, DO-4
DOC40 AT40 11 11 11 note 1 0 0 note 2 note 3 0
DOC21 Fermator 11 0 11 note 1 0 40 note 2 note 3 2
VVF3
SEL105
SEM 2000
DOT1/2/3 FCO9550T 1,2 0 0 0 0 0 0 0 0

DOC5 Falconi 1,2 0 0 0 0 0 0 0 0
DOC10 Meiller AC, 1,2 0 0 0 0 0 0 0 0
Selcom AC
DOC11 Meiller DC 1,2 0 0 0 0 0 0 0 0
DOC22 PIUMA 1,2 0 0 0 0 0 0 0 0
DOC23 Sematic 1,2 0 0 0 0 0 0 0 0
DOC27 RCF… 1,2 0 0 0 0 0 0 0 0
DOC28 Fermator 1,2 0 0 0 0 0 0 0 0
VVV4
DOC29 Wittur 1,2 0 0 0 0 0 0 0 0
ECO_DC
DOC30 SUPRA SM 1,2 0 0 0 0 0 0 0 0
DOCX 1,2 0 0 0 0 0 0 0 0
RC24, 1,2 0 0 0 0 0 0 0 0
RC48
DOMR MRDS 3,4,9, 0 0 0 0 0 0 0 0

10
FLH 0 0 0 0 0 0 0 0 0
note1: ACG-2: EN-ACG=1

note2: FLH or ACG-2 für France: CM-TYP=11
FLH: CM-TYP=11
ACG-2, with DCL: CM-TYP=2
ACG-2, without DCL: CM-TYP=11
note3: FLH or ACG-2: CM-PROT=10
note4: with ERO: TRO-TYP=1
Page: 113 / 196
Berlin
Internal (hidden) setup of preconfigured DO/DC door types (DOOR = 0 – 10)

[corresponding GENERIC (DOOR = 11) setup]:
Name DOOR DO-TYP DC-TYP EN-ACG CM-TYP DOL-D EN-DCL GENERIC

(Door=11)
FLH 0 10 10 1 11 10 0 √
9550T & ACG 1 10 11 1 11 0 1 √
9550T & TLD/CLD 2 10 11 0 00 0 1 √
OVL 3 11 11 1 11 0 1 not
(LCB_IIC: MRDS & ACG) possible
(note 1)
OVL & TLD/CLD 4 11 11 0 0 0 1 not
(note 1) possible
DO2000 (DO-Relay) 5 11 00 0 0 0 0 √
MCG (DC-relay) 6 10 10 1 11 40 0 √
MLI & ACG (DC-relay) 7 11 11 1 11 40 0 √
MLI & TLD/CLD(DC-relay) 8 11 11 0 00 40 0 √
OVL-PENANG & ACG 9 11 11 1 11 0 1 not
(note 2) possible
OVL-PENANG & TLD/CLD 10 11 11 0 00 0 1 not
(note 2) possible
The following parameters are set internally for the DOOR types above:
CM-PROT = 10, TRO-TYP = 0, DO-D = 0, CM-D = 0
note 1: MRDS for 2-entrances (DLN generated by external hardware)

note 2: MRDS for single entrance (DLN handled by RDO output)
Page: 114 / 196
Berlin
RSL i/o setup:

Feature Name
606 RDOS/SGS
605 DOS/SGS
788 RDCM
545 RDOB
637 RNDG
544 RDOL
608 RLRD
695 RDCL
546 REDP
808 RREV
1017 DPP
031 DMD
787 DCM
001 DOB
027 NDG
000 DOL
607 LRD
694 DCL
002 EDP
806 REV
805 UD
DOC12 MLI 1 √ √ 1 1 √ √ 1
DOC19 Kiekert-1 √ √ √ √ √ √ √ √ √ √
DOC9 Kiekert-2 √ √ √ √ √ √ √ √ √ √
DDC
DOC20 AT20 √ √ √ √ √ √ √ √ √ √ √ √
DOC25 AT25 (old)
DOAT25 AT25 √ √ √ √ √ √ 1 √ √ √ √ √ √ 1 √
(new)
Fedo
DO2000, DCSS4 √ √ √ √ √ 1 √ √ √ √ √ 1 √ √
DO-1,
DO-4
DOC40 AT40 √ √ √ √ √ √ √ √ √ √ √ √ √ √ √
DOC21 Fermator 1 √ √ √ √ 1 1 √ √ √ √ 1
VVF3
DOC29 Wittur √ √ √ √ √ √ √ √ √ √ √ √ √ √
ECO_DC
DOT1/2/3 FCO9550 √ √ √ √ √ √ √ √ √ √ √ √ √
DOC5 Falconi √ √ √ √ √ √ √ √ √ √ √ √
DOC10 Meiller √ √ √ √ √ √ √ √ √ √ √ √
AC,
Selcom
AC
DOC11 Meiller DC √ √ √ √ √ √ √ √ √ √ √ √
DOC22 PIUMA √ √ √ √ √ √ √ √ √ √ √ √
DOC23 Sematic √ √ √ √ √ √ √ √ √ √ √ √ √ √
DOC27 RCF… √ √ √ √ √ √ √ √ √ √ √ √
DOC28 Fermator √ √ √ √ √ √ √ √ √ √ √ √ √ √
VVV4
DOC30 SUPRA √ √ √ √ √ √ √ √ √ √ √ √
SM
DOCX √ √ √ √ √ 1 √ 1 1 √ √
DOMR MRDS √ √ √ √ √ 1 1
FLH 1 1
1: these i/o’s must be set to address 010

not marked i/o’s must be set to address 000
Page: 115 / 196
Berlin
6.2 DO-5 / AT120
6.2.1 Parameters
The following parameters must be set to use a DO-5/AT120:
group parameter value remark
5-DOORS DOOR 12
13 if DOB is additionally connected to DO-5 (DOBF) and for
AT120
REAR 12
13 if DOB is additionally connected to DO-5 (DOBF) and for
AT120
F:DO-TYP 0
F:DC-TYP 0
F:EN-ACG 0
F:EN-DCL 0
F:DOL-D 0
R:DO-TYP 0
R:DC-TYP 0
R:EN-ACG 0
R:EN-DCL 0
R:DOL-D 0
CM-TYP 0
TRO-TYP 0
10-TEST DEBUG 0
DEBUG1 0
Please note that all DOOR=12/13 enables all Generic Door parameters!
GECB (since GAA30780DAB): For ACG with DO-5/AT120 set the following parameter:
F:EN-ACG
R:EN-ACG
CM-PROT
Page: 116 / 196
Berlin
6.2.2 I/Os
These are the I/Os and the corresponding default addresses:
Nr name MCS120 MCS220 GEN2_A GEN2_B GEN2C_A GEN2C_B VF_MRL

000 DOL 17,1 17,1 17,1 13,1 17,1 13,1 17,1
002 EDP 00,0 00,0 00,0 00,0 00,0 00,0 00,0
027 NDG 00,0 00,0 00,0 00,0 00,0 00,0 00,0
544 RDOL 19,1 19,1 19,1 00,0 19,1 00,0 19,1
546 REDP 00,0 00,0 00,0 00,0 00,0 00,0 00,0
605 DOS / SGS 17,4 17,4 17,4 13,4 17,4 13,4 17,4
606 RDOS / RSGS 19,4 19,4 19,4 00,0 19,4 00,0 19,4
607 LRD 17,3 17,3 17,3 13,3 17,3 13,3 17,3
608 RLRD 19,3 19,3 19,3 00,0 19,3 00,0 19,3
691 TCI 16,3 16,3 16,3 12,3 17,2 13,2 16,3
694 DCL 01,0 01,0 01,0 01,0 01,0 01,0 01,0
695 RDCL 01,0 01,0 01,0 01,0
783 TCIB 01,0 01,0 01,0 01,0
787 DCM 00,0 00,0 00,0 00,0
991 DOOR_ST1 17,3 17,3 17,2 13,2
992 DOOR_ST2 17,4 17,4 17,3 13,3
993 DOOR_ST3 16,3 16,3 17,4 13,4
994 DOOR_ST1R 19,3 19,3 19,2 00,0
995 DOOR_ST2R 19,4 19,4 19,3 00,0
996 DOOR_ST3R 00,0 00,0 19,4 00,0
note: LRD & RLRD are low active for DOOR=12/13.

Page: 117 / 196
Berlin
6.3 Generic Door Operator (DO/DC RSL interface)
Since GAA30780DAG the software provides additional outputs on the Remote Serial Link to
drive door operators with DO / DC interface.
For safety reason two separate Door Open relays must be used and should be assigned to
2 different remote stations.
outputs:
IO symbol description def type
27 NDG Nudging 0/0 out
637 RNDG Rear Nudging Relay 0/0 out
997 DDM Deenergize Door Motor (Stop) 0/0 out
998 RDDM Deenergize Rear Door Motor (Stop) 0/0 out
1017 DPP Disable Passenger Protection (during EFO) (for AT25) 0/0 out
1094 DO1 Door Open relay 1 0/0 out
1095 DO2 Door Open relay 2 0/0 out
1096 DC Door Close relay 0/0 out
1097 DSDOB Disable Door Open Button (low active) 0/0 out
1098 DSLRD Disable Light Ray Device (low active) 0/0 out
1099 CLT Closed Torque (keep door closed during run) (for Meiler MAT) 0/0 out
1100 RDO1 Rear Door Open relay 1 0/0 out
1101 RDO2 Rear Door Open relay 2 0/0 out
1102 RDC Rear Door Close relay 0/0 out
1103 RDSDOB Rear Disable Door Open Button (low active) 0/0 out
1104 RDSLRD Rear Disable Light Ray Device (low active) 0/0 out
1105 RCLT Rear Closed Torque (keep door closed during run) (for Meiler MAT) 0/0 out
1106 ESD Emergency Stop of Door (turns off door in ES) (for AT25) 0/0 out
inputs:
IO symbol description def type
0 DOL Door Open Limit 1/0 in
1 DOB Door Open Button (only low active for DOOR=13) 0/0 in
544 RDOL Rear Door Open Limit 1/0 in
545 RDOB Rear Door Open Button (only low active for DOOR=13) 0/0 in
605 DOS / SGS Door Open Signal / Safety Gate Shoe 0/0 in
606 RDOS / RSGS Rear Door Open Signal / Rear SGS 0/0 in
607 LRD Light Ray Device (only low active for DOOR=12/13) 0/0 in
608 RLRD Rear Light Ray Device (only low active for DOOR=12/13) 0/0 in
694 DCL Door Close Limit Switch 1/0 in
695 RDCL Rear Door Close Limit Switch 1/0 in
parameters:
5 - DOORS
Symbol Default Purpose and Range
DOOR 11 Type of Doors:11 GENERIC (DO/DC) ...
Page: 118 / 196
Berlin
5 - DOORS
REAR 11 Type of Doors:11 GENERIC (DO/DC) ...
F:DO-TYP 0 type of DO handling
00 DO never pulled
01 DO pulled when car door fully opened
10 DO pulled during opening
11 DO pulled when car door opening and also when fully opened
F:DC-TYP 0 type of DC handling
00 DC never pulled
01 DC pulled when car door fully closed
10 DC pulled during closing
11 DC pulled when car door closing and also when fully closed
F:EN-DCL 0 enable DCL input at IO 694
0 no DCL switch
1 DCL at IO no. 694
F:DOL-D 0 GenDoor: automatic DOL generation
0 DOL at IO 0000
0.1 (0.1) 25.5 s DOL is simulated after specified time
(necessary if no DOL exists)
R:DO-TYP 0 type of RDO handling
same description as front door
R:DC-TYP 0 type of RDC handling
R:EN-DCL 0 enable RDCL input at IO 695
R:DOL-D 0 GenDoor: automatic DOL generation
0 RDOL at IO 0544
0.1 (0.1) 25.5 s DOL is simulated after specified time
(necessary if no DOL exists)
6.3.1 RCF1, AT25 or MAT Door System
Symbol Value Meaning

DOOR 11 GENERIC (DO/DC)
REAR 11 GENERIC (DO/DC)
F:DO-TYP 11 DO pulled when car door opening and also when fully opened
F:DC-TYP 11 DC pulled when car door closing and also when fully closed
F:EN-DCL 1 DCL at IO no. 0694
F:DOL-D 0 DOL at IO no. 0000
R:DO-TYP 11 DO pulled when car door opening and also when fully opened
R:DC-TYP 11 DC pulled when car door closing and also when fully closed
R:EN-DCL 1 RDCL at IO no. 0695
R:DOL-D 0 RDOL at IO no. 0544
Page: 119 / 196
Berlin
6.3.2 RC24, RC48 Door System
Symbol Value Meaning

DOOR 11 GENERIC (DO/DC)
REAR 11 GENERIC (DO/DC)
F:DO-TYP 10 DO pulled during opening
F:DC-TYP 10 DC pulled during closing
F:EN-DCL 1 DCL at IO no. 694
F:DOL-D 0 DOL at IO no. 0000
R:DO-TYP 10 DO pulled during opening
R:DC-TYP 10 DC pulled during closing
R:EN-DCL 1 RDCL at IO no. 695
R:DOL-D 0 RDOL at IO no. 0544
6.4 SGS2 - Secondary Safety Gate Shoe for Korea
In Korea, the safety gate shoe(SGS) is a common requirement. But the door lock(DTO) can
be detected when door is opened by the existing SGS with DOS for a long time, because
the door can’t be fully opened by DOS(door opening signal). So new SGSs w/o DOS are
needed(1155 SGS2, 1156 RSGS2).
The existing DOS/SGS(RDOS/RSGS) has priority over new SGS2(RSGS2). For example,
the existing DOS/SGS is available when the RSL addresses of the existing DOS/SGS and
new SGS are set to the valid address at the same time.
inputs:
IO symbol description def type link
1155 SGS2 Secondary Safety Gate Shoe 0/0 in car
1156 RSGS2 Secondary Rear Safety Gate Shoe 0/0 in car
6.5 Door Bypass
6.5.1 LCB_IIC
The LCB_IIC supports an external door bypass. The LCB_IIC has none door bypass relays
on board. The LV connection from the PRS to the drive can be done via relay contacts or
Page: 120 / 196
Berlin
directly. The RegenDrives needs a directly connection, otherwise position recovery after
power on is not possible.
for RegenDrives LV inputs ’s have to be connected directly to the PRS

for OVF10 / OVF20CRO 1LV input has to be connected directly to the PRS
all other drive types LV inputs’s could be connected directly or via relay
6.6 Door Reversals after Power On
The door reversals will be always considered especially after power on, if the floor position
is valid and the car is inside a door zone with open door(s). To get a valid position after
power on, the position must be successfully recovered (see chapter 2.34). An open manual
hoistway door will be handled as an active reversal (parameter EN-ACG).
Attention:
The OVF10 and the OVF20CRO prevents the door zone signal to the LCB_II after power
on.
Exception:
The OVF20CRO software GP130763CAA (or newer) contains the partameter
“DZafterPOR”, which must be activated to consider door reversals after power on.
If the customer wants none moving doors during micro power cuts, the door must be
stopped during power fail and stopped by the de-energize command (DEEN). This must be
guaranteed by the door operator and the door mechanic. A door initialization run without a
close or open command is not allowed.
A stopped door by a de-energize command is only possible with the following door interfac-
es: RSL, CAN, Multidrop, DO / DC (only DO does not work). The following door operators
react correctly on the de-energize command: DCSS5e, DCSS5, AT120, Selcom with RSL
interface, AT25 with DO/DC interface, 9550 with DO/DC interface. In addition the door me-
chanic must hold the door during the de-energized phase.
The following door operators does not support the de-energize command: DCSS4, AT25
with DO interface, AT25 with DO interface, 9550 with DO interface.
The door gets always the de-energize command during the 8s OCSS ini-phase after power
on. After this time the reversals will be considered, if the above described conditions are
fulfilled (DZ & valid floor Position).
Page: 121 / 196
Berlin
7 Car related Setup
7.1 CGS - Door Short Protection for Korea

In EN-81 system, the controller can’t detect CGS stuck because DFC is not powered when
DW is off. So an alternate input by an additional device is used for detecting CGS stuck in
Korea application. The door bridge error is set when Car gate Switch is shorted. A door
short state will be detected when Car gate switch is not opened though OLS is activated.
An additional device(contactor) and wiring is needed for that.
Install Parameters:
5-DOORS EN-CGS 1 Enable Door short protection
Inputs:
Pin Signal
P_C:1 CGS
7.2 CMG - Car Mounted Governor

The "Car Mounted Governor" (CMG) is located on the car and can be remotely tripped via
two separate RSL outputs.
The governor can be tripped by the following means:
 On SPBC, with the buttons REB+RTB
 On GECB-EN, with the buttons REB+RTB
 On SP, with the menus “Construction – Test RTD/RRD”, “Service – Governor Trip”,
“Handover – Overload Safeties”
When triggered, the outputs are activated as shown below:
RTD_OUT1
RTD_OUT2
Typ. 700ms
RTD is pushed here CMG tripping starts here

Page: 122 / 196
Berlin
I/O-Numbers:
I/O Name Description Type Link
1112 RTD_OUT1 Remote Tripping Device Output 1 out Car
1113 RTD_OUT2 Remote Tripping Device Output 1 out Car
For robustness reasons, both I/Os must be programmed to different RSL addresses!
7.3 FAN - Fan Control for Asia

This feature is available since GECB software GAA30780DAC.
The car FAN separated from LR is used for turning off the FAN in car when car is in parking,
EFS mode or finishing landing to EFO target floor with open door. The existing FANR(1089)
will be used for the FAN separated from LR. The FAN-TYP=2, 3 has been added for remote
service, the FAN is permanently ON(FAN-TYP=2), OFF(FAN-TYP=3).
Install Parameters:
1-SYSTEM FAN-TYP 0-3 0 Push button activates the fan for FAN-T seconds, using
I/O 1089 FANR
1 Uses I/O 1089 FANR to switch off the fan after LR-T and
also during EFO, EFS, PKS (independent from LR-T)
2 Uses I/O 1089 FANR to switch on the fan always (for
remote service)
3 Uses I/O 1089 FANR to switch off the fan always (for
remote service)
I/O-Numbers:
I/O Name Description Type Link
1089 FANR FAN Relay (operated low-active) out car
Page: 123 / 196
Berlin
7.4 Hong Kong Car Door Locks

The lift is fitted with a special car door lock device, and the door can only open if that device
is energised. To avoid the door to try to open against the unreleased lock, a back contact of
the device is used to check for an unlocked door, and only then the door will open.
Install Parameter:
None
I/O-Numbers:
1035 XDO Output to drive the locking device out car
1036 RXDO Rear Output to drive the locking device out car
1037 CCDC Input for the Back Contact of the locking device In car
1038 RCCDC Rear input for the Back Contact of the locking device in car
Additionally the software provides optional inputs to monitor the state of the separate DZ
sensors used for the locking devices.
I/O-Numbers:
1039 X1LV Input check LV1 Relay In car
1040 X2LV Input check LV2 Relay In car
If the software detects that one of the extra LV sensors is still operated outside the Door
zone, the car enters the DBF mode and shuts down at the next floor.
The blinking message “> Ext LV Err” shows up on the service tool and this fault can be reset
by placing the lift on ERO/TCI or by pressing the DDO button on the Service Panel Board.
This feature is only enabled if both I/O-numbers 1039 and 1040 are programmed to a valid
address and pin of a remote station.
Page: 124 / 196
Berlin
7.5 GECB: SO(Safe to Open) Signal for Japan

SO signal is used to decide whether the door is allowed to open with DOB even if the car is
stopped w/o normal run. This signal is sent to the door operator for openning door thru RSL
line.
SO relay is active by the RSL based upon conditions as below:
GECB mode Communica-
Thresh hold
1LV & 2LV UIB/DIB tion with FSO output
speed*
(CAN message) drive
Normal Operation
True ON/ON True Active True
Including ARO mode
TCI / ERO mode True Any True Active True
Re-leveling True ON/ON True Active True
* thresh hold speed status(0.3m/sec) from drive.

The GECB checks consistency of FDZ and CHK_SO with 1LV and 2LV, and if detect
inconsistency, system should be shutdown. At this time, the following event is logged. The
car starts to check consistency after 800ms of Car Stopped and the GECB shifts to
shutdown after checking 10 times with inconsistency
Event:
Event Description
0253 FSO Rly Err When the inconsistency is detected for front SO relay
 Check SO relay for front door
 Check IO FDZ(1195), FSO(1197) and CHK_SO(1196)
0254 RSO Rly Err When the inconsistency is detected for rear SO relay
 Check SO relay for rear door
 Check IO RDZ(0661), RSO(1199) and CHK_RSO(1198)
Blink Message:
Message Description
>FSO RlyErr When the inconsistency is detected for front SO relay
 Check SO relay for front door
 Check IO FDZ(1195), FSO(1197) and CHK_SO(1196)
>RSO RlyErr When the inconsistency is detected for rear SO relay
 Check SO relay for rear door
 Check IO RDZ(0661), RSO(1199) and CHK_RSO(1198)
I/O-Numbers:
1195 FDZ Front Door Zone in car
1196 CHK_SO SO relay in car
1197 FSO Front Safe to open out car
Page: 125 / 196
Berlin
1198 CHK_RSO Rear SO relay in car

1199 RSO Rear Safe to open out car
0661 RDZ Rear Door Zone in car
Install Parameters:
1-SYSTEM EN-SO 0 Enable SO signal
0 Disabled
1 Enabled
System configuration for SO interface:
Note) This feature cannot correspond to the rear door.

Page: 126 / 196
Berlin
8 Group Related Setup
8.1 OTIS2000 Openings

For GECB, the numbering system of openings and levels is somewhat different from the
pure floor counting.
Car fixtures are related to the floor levels, separately for front and rear. Hall fixtures are
related to the opening numbers.
The following four examples for simplex configurations explain the relationship between
levels and openings:
The rule to define the openings is:
Count the front- and rear-doors for each level beginning at front/level 0.
The software will determine the openings according to this rule.

Page: 127 / 196
Berlin
8.2 Dummy Doors

For groups (G2C-G8C) it is absolutely necessary that doors at corresponding locations are
assigned to the same opening number in each hoistway. If there are doors in the building
which are not served by all cars of the group, the remaining cars must have Dummy Doors
at this locations:
CAR A CAR B CAR C

openings: openings: openings:
front rear front rear front rear
Level 4 6 7 6 7 6 7
Level 3 4 5 4 5 4 5
Level 2 2 3 2 3 2 3
Level 1 1 1 1
Level 0 0 0 0
Dummy Doors
GECB Parameters
“BOTTOM”=0 “BOTTOM”=2 “BOTTOM”=2
“TOP”=4 “TOP”=4 “TOP”=4
GECB Allowed Mask

level CUDE CUDE CUDE CUDE CUDE CUDE
4: 1010 1010 1010 1010 1010 1010
3: 1110 1110 1110 1110 1110 1110
2: 1110 1110 1100 1100 1100 1100
1: 1110 0000 2000 0000 2000 0000
0: 1100 0000 2000 0000 2000 0000
DRIVE Parameters
“Bottom DZ”=0 “Bottom DZ”=2 “Bottom D”Z=2
The Dummy Doors are programmed using the Allowed Mask. Please refer to
GAA30780EAN_STM.doc for more information.
Page: 128 / 196
Berlin
8.3 DEK with RSL Encoded Interface

The DEK will be connected via the existing RSL to the GECB based elevator controller.
The DEK provides a user interface for elevator passengers to enter their destination floor
and to get feedback about the number entered and the assigned car.
The device consists of a tactile keypad and a display.
For users with disabilities it provides a “disability button” and voice generation.
Install Parameters:
3-GROUP GRP-NO 1 or 2 Car identifier in group. For DEK, Max 2.
3-GROUP GROUP 1 or 2 Number of cars in group. For DEK, Max 2.
3-GROUP DEST-DE 0 or 8 Defines when the DEK destination car call is entered.
0: on LRD
8: on DOL
3-GROUP DEK-TYP 1 DEK with encoded RSL interface
I/O-Numbers:
Each DEK device connected to the RSL requires 4 consecutive RSL addresses. The base
address is configured manually within the DEK device and automatically within the GECB
upon powering up the DEK. If 4 consecutive addresses are not free beginning with the DEK
base address, a configuration error is reported. For example, if the DEK base address is
configured to 44, then no RSL IOs are allowed to be programmed at the following address-
es, otherwise, error:
44-1, 44-2, 44-3, 44-4
45-1, 45-2, 45-3, 45-4
46-1, 46-2, 46-3, 46-4
47-1, 47-2, 47-3, 47-4
Page: 129 / 196
Berlin
9 Hoistway Setup
If the hoistway has a reduced pit depth, there are two different approaches:
 Shallow Pit With safety triggering devices TDM
 Low Pit With KS-L at bottom landing door and a manually operated prop in the
pit
The first approach and the optional reduced overhead is described in section 9.1. The
second approach is described in section 9.2.
9.1 OHLOW/SHPIT - Reduced Hoistway

Reduced hoistway is available since the following software versions:
GECB: GAA30780DAB
Needed environment:
SPBC_III with software GAA30773BAA or higher.
The GECB software monitors the triggering moduls, which triggers the safety in a case of a
mechanic can be crushed by the car in the top of the hoistway or in the pit. The monitoring
should prevent a tripped safety, caused by a malfunction of the triggering modul (not retract-
ing), by stopping the car immediately (stay at NAV). An error can be reset by ERO (not by
TCI or Power off). The triggering moduls are controlled by hardware. The RS inputs 1054 /
1055 are used to display a tripped car at the SPB position indicator.
Triggering Modul released:
The safeties will be activated, if the car would passes the modul.
Triggering Modul retracted:
The safeties cannot be activated (thats independent to ‘overspeed’), if the car would
passes the modul.
The switches TUDS (Triggering Up Modul Deactivation Switch) and TDDS (Triggering Down
Modul Deactivation Switch) activate the retraction of the trigger moduls. They are located
around 1.5m before the top and bottom floor.
The triggering moduls are released at power off and if the car is not moving (depends on
SW relay). At a Normal, ERO or ARO run the triggering moduls are released, if the car is
not near the top or bottom. At Inspection run the triggering moduls are always released.
At MRO run the triggering moduls TUM1 and TDM are retracted, TUM2 is released.
The RS inputs TUM1/2 and TDM are high, if the triggering modul will be retracted (TUDS or
TDDS activated) and the car is running (near top / bottom). The RS inputs TUPS and TDPS
are high during every run.
The TCI-Lock will be suppressed, if the parameter HWY-TYP is set to ‘low overhead’ or ‘low
overhead & shallow pit’. If the parameter HWY-TYP is set to 0 and the triggering devices
Page: 130 / 196
Berlin
are mopunted, then TCI-Lock cannot be reseted by closing the hoistway door (after switch-
ing TCI-NOR), because the aux. door contact KS is still open.
I/O-Numbers:
no. name description connected to type location
1047 TUM1 Triggering Up Modul 1 Contact TUAC1 in hall
1048 TUM2 Triggering Up Modul 2 Contact TUAC2 in hall
1049 TDM Triggering Down Modul Contact TDAC in hall
1050 TUPS Triggering Up Modul Power Supply State before TUM1/2 coil in hall
switch
1051 TDPS Triggering Down Modul Power Supply State before TDM coil in hall
switch
1054 SOSU Safety Operated Switch Up SOS-U in car
1055 SOSD Safety Operated Switch Down SOS in car
Install-Parameters:
1 - SYSTEM
No. Symbol Default Purpose and Range since
30 HWY-TYP 0 Hoistway Type: AAD
0 Normal
1 low overhead (io1047, 1048, 1050, 1054)
2 shallow pit (io1049, 1051, 1055)
3 low overhead & shallow pit (1+2)
(extended in EAC with Low Pit)
Hint: The Parameter BRK-TYP must be set correctly. The brake signal is used for the check
of the trigger modul contacts.
Events:
event reason related setup
System
0607 / TUM1 TUM1 missing after run at TOP or active during TUM1 (1047)
standstill; (reduced overhead: trigger modul con- HWY-TYP
tacts)
0608 / TUM2 TUM2 missing after run at TOP or active during TUM2 (1048)
standstill; (reduced overhead: trigger modul con- HWY-TYP
tacts)
0609 / TDM TDM missing after run at BOTTOM or active during TDM (1049)
standstill; (shallow pit: trigger modul contacts) HWY-TYP
0610 / TUPS TUPS missing during run; (reduced overhead: TUPS (1050)
trigger modul power supply) HWY-TYP
0611 / TDPS TDPS missing during run; (shallow pit: trigger mod- TDPS (1051)
ul power supply) HWY-TYP
0612 SOS up Safety Operated Switch Up triggered SOSU (1054)
HWY-TYP
Page: 131 / 196
Berlin
event reason related setup

0613 SOS down Safety Operated Switch Down triggered SOSD (1055)
HWY-TYP
SVT INPUTS:
input group Description is displayed when ...
UM1 reduced hwy i/o 1047 TUM1 HW-TYP = 1 or 3

UM2 i/o 1048 TUM2 HW-TYP = 1 or 3
UMP i/o 1050 TUPS HW-TYP = 1 or 3
OSU i/o 1054 SOSU HW-TYP = 1 or 3
DM i/o 1049 TDM HW-TYP = 2 or 3
DMP i/o 1051 TDPS HW-TYP = 2 or 3
OSD i/o 1055 SOSD HW-TYP = 2 or 3
Display at SPB Position Indicator:

prio display events Description is displayed
when ...
1 Su 0612 Safety Operated Switch Up triggered HW-TYP = 1 or 3
2 Sd 0613 Safety Operated Switch Down triggered HW-TYP = 2 or 3
3 Eu 0607, 0608, 0610 Error Triggering Modul Up HW-TYP = 1 or 3
4 Ed 0609, 0611 Error Triggering Modul Down HW-TYP = 2 or 3
The SPB displays always its own position content, if ERO will be switched on or the SPB
will be switched into battery mode.
9.2 LOWPIT1 - Low Pit

Low Pit is available since SW version GAA30780EAC.
Page: 132 / 196
Berlin

If configured for Low Pit the GECB supervises KS-L, APS/RAPS, and the manually
operated prop position and controls the PBUZ when the pit is accessed.
9.2.2 Setup
Depending on the order parameters the factory configures the E²PROM to require the
configuration parameter HWY-TYP and Low Pit RSL IOs to be set according to the ordered
APS and RAPS.
Order Parameters:
Name Description
SHPIT = LOWPIT1 Sets-up Low Pit with KS-L at bottom landing door and prop in pit
APSF = YES Specifies a retractable apron with monitoring contact at the front car entrance
APSR = YES Specifies a retractable apron with monitoring contact at the rear car entrance
KSMF = YES Specifies a lockable key switch at the bottom front landing door
KSMR = YES Specifies a lockable key switch at the bottom rear landing door
Install Parameters:
Group Name Description
1-SYSTEM HWY-TYP Hoistway Type:
0 Normal
1 Low overhead
2 Shallow pit
3 Low overhead & shallow pit (1+2)
4 Low Pit with APS only
8 Low Pit with RAPS only
12 Low Pit with both APS and RAPS
28 Low Pit with both APS and RAPS and pit access from both front
and rear door in landings BOTTOM and BOTTOM+1 (4+8+16),
order parameters KSMF and KSMR
(since GP3EAL)
Default: 0
I/O Numbers:
Number Name Description Type Link
1251 KS-L Lockable key switch at bottom landing door in hall
1252 DS1 Landing door switch (bottom) in hall
1253 PMSI Prop manual switch at inspection position in hall
1254 APS Apron fully deployed switch in car
1255 PBUZ Pit buzzer out hall
1256 RAPS Rear apron fully deployed switch in car
Page: 133 / 196
Berlin

Low Pit failures can be caused by
 wrong configuration
 hardware failures
Page: 134 / 196
Berlin
Event:
Event Description
0334 KS-L fault KS-L is stuck closed (KS-L=off) although the bottom landing door is open (DS1=off) for >
4 s while the car is not at DZ of the bottom floor (or at DZ of bottom+1 floor if HWY-
TYP=28).
 Check KS-L and DS1 switches and wiring.
0335 APS fault Front or rear Toe Guard is “folded” above 1LS (APS=off or RAPS=off) for > 2 s or
front or rear Toe Guard is “unfolded” at bottom floor (APS=ON or RAPS=ON) for > 2 s.
 Check APS and RAPS switches and wiring.
Note:
If the car has been moved since detection of the error (e.g. by ERO) the car must be
moved back into the area where the error occurred “car is above 1LS” or “car is at bot-
tom floor” before removing the error.
0619 HWY-TYP The parameter HWY-TYP is not configured for Low Pit (4 for APS, 8 for RAPS, 12 for
APS and RAPS, or 28 for APS and RAPS with pit access from BOTTOM and BOT-
TOM+1) although the E²PROM has been configured in the factory to require Low Pit to
be configured.
 Set APS and RAPS according to the factory setup.
OR
HWY-TYP is set to 4, 8, 12, or 28 but the Ultra Drive installation parameter Low Pit is set
to 0.
 For a Low Pit configuration set Ultra Drive Low Pit to 1 (15 cm/s) or 2 (10 cm/s) and
for a normal pit configuration set HWY-TYP accordingly (e.g. 0).
OR
HWY-TYP is set to 0 but Ultra Drive Low Pit is set to 1 or 2.

 For a Low Pit configuration set HWY-TYP according to the present APS/RAPS and
for a normal pit configuration set HWY-TYP accordingly (e.g. 0).
OR
RSL IOs KS-L, DS1, PMSI, APS (if present), RAPS (if present), PBUZ do not have valid
addresses.
 Set RSL IOs to valid addresses.
Blink Message:
Message Description
>KS-L fault Event 0334 KS-L fault occurred (please refer to the previous table)
>APS fault Event 0335 APS fault occurred (please refer to the previous table)
>LOPIT cfg! Event 0619 HWY-TYP occurred (please refer to the previous table)
Page: 135 / 196
Berlin
10 Controller Related Setup
10.1 GCS222MRL
The E&I Panel Controller, consisting of the boards GECB_II, BCB_II and SP, requires the
following parameter setup:
Install Parameters:
4-DRIVE DRV-TYP 1 Drive ICD13 or higher required for Installation without Service
Tool
7-SERVICE SPB-TYP 1 Service Panel with graphic display.
Page: 136 / 196
Berlin
10.2 GCS 222 LVA

The controller for the „Low Voltage Architecture“ consists of the following boards:
GECB-board: GECB_LV
CARIO-board: TOCB or COPG_III
BCBIO-board: LVPB
Limitations:
Inverted signals like DOB, LRD and TCI shall not be connected to car RSL.
Note that the “LVA Basic” Controller has a limited power supply.
 RLEV is not allowed as long as any door is moving.
This means that RLEV will only occur while the door is fully opened.
 ADO is not allowed.
Install Parameters:
Group Name value Description

1-SYSTEM EN-CARIO 7 PRS and RSL are connected to the TOCB
1-SYSTEM LVA-TYP 0 “Basic”, with LVPB, with UD401 / UD402 / UD403
1 “Switch”, with LVPB, with LVD
2 “Extended” with LVPB + BCB_II, with LCRD404 / LCRD406
3 “Extended” with LVPB + LVPB, with UD402 / UD403
4 “Extended” with LVPB + BCB_II, with UD404
4-DRIVE DRV-TYP 1 “Basic” or “Extended”, with Ultra Drive or LCRD
3 “Switch”, with Low Voltage Drive
4-DRIVE LW-TYP 1 Dinacel load weighing
4-DRIVE EN-ADO 0 Lifting the brake is not allowed while any door is moving
7-SERVICE SPB-TYP 1 Service Panel with graphic display.
I/Os:
Below is the list of standard addresses of the CARIO board for the basic I/Os:
IO Number Name Description Type Link Address

0000 DOL Door Open Limit in cario 93 4
0001 DOB Door Open Button in cario 93 8
0605 DOS Door Open Signal in cario 93 5
0607 LRD Light Ray Device in cario 93 6
0691 TCI Top-of-Car Inspection switch in cario 96 5
0991 ST1 ST1 for front DO1000 (DCSS5) out cario 93 8
0993 ST3 ST3 for front+rear DO1000 (DCSS5) out cario 93 6
Page: 137 / 196
Berlin
CARIO-Mapping (TOCB, COPG, CSPB):

Below is a list of the CARIO-I/Os and the related GECB addresses.
GECB GECB
CARIO Address GECB IO CARIO Address GECB IO
IN00 90,8 32 CB00 OUT00 90,8 32 CTTL00
IN01 90,7 33 CB01 OUT01 90,7 33 CTTL01
IN02 90,6 34 CB02 OUT02 90,6 34 CTTL02
IN03 90,5 35 CB03 OUT03 90,5 35 CTTL03
IN04 90,4 36 CB04 OUT04 90,4 36 CTTL04
IN05 90,3 37 CB05 OUT05 90,3 37 CTTL05
IN06 90,2 38 CB06 OUT06 90,2 38 CTTL06
IN07 90,1 39 CB07 OUT07 90,1 39 CTTL07
IN08 91,8 40 CB08 OUT08 91,8 40 CTTL08
IN09 91,7 41 CB09 OUT09 91,7 41 CTTL09
IN10 91,6 42 CB10 OUT10 91,6 42 CTTL10
IN11 91,5 43 CB11 OUT11 91,5 43 CTTL11
IN12 91,4 44 CB12 OUT12 91,4 44 CTTL12
IN13 91,3 45 CB13 OUT13 91,3 45 CTTL13
IN14 91,2 46 CB14 OUT14 91,2 46 CTTL14
IN15 91,1 47 CB15 OUT15 91,1 47 CTTL15
IN16 92,8 48 CB16 OUT16 92,8 48 CTTL16
IN17 92,7 49 CB17 OUT17 92,7 49 CTTL17
IN18 92,6 50 CB18 OUT18 92,6 50 CTTL18
IN19 92,5 51 CB19 OUT19 92,5 51 CTTL19
IN20 92,4 52 CB20 OUT20 92,4 52 CTTL20
IN21 92,3 53 CB21 OUT21 92,3 53 CTTL21
IN22 92,2 54 CB22 OUT22 92,2 54 CTTL22
IN23 92,1 55 CB23 OUT23 92,1 55 CTTL23
IN24 93,8 001 DOB OUT24 93,8 991 ST1
IN25 93,7 003 DCB OUT25 93,7 992 ST2
IN26 93,6 607 LRD/REV OUT26 93,6 993 ST3
IN27 93,5 605 DOS OUT27 93,5 994 RST1
IN28 93,4 000 DOL OUT28 93,4 995 RST2
IN29 93,3 545 RDOB OUT29 93,3 996 RST3
IN30 93,2 547 RDCB OUT30 93,2 026 LR
IN31 93,1 608 RLRD/RREV OUT31 93,1
Page: 138 / 196
Berlin
GECB GECB
CARIO Address GECB IO CARIO Address GECB IO
IN32 94,8 606 RDOS OUT32 94,8 1323 Visual Alarm
IN33 94,7 544 RDOL OUT33 94,7 023 Buzzer
IN34 94,6 793 LEV/SAC OUT34 94,6
IN35 94,5 1000 CLR OUT35 94,5
IN36 94,4 694 DCL OUT36 94,4
IN37 94,3 OUT37 94,3
IN38 94,2 OUT38 94,2
IN39 94,1 OUT39 94,1
IN40 95,8 1254 APS OUT40 95,8 578 CDLU
IN41 95,7 1255 R-APS OUT41 95,7 579 CDLD
IN42 95,6 705 TDOB OUT42 95,6 580 CDGU (GNCUP)
IN43 95,5 706 TDCB OUT43 95,5 581 CDGD (GNCDN)
IN44 95,4 707 R-TDOB OUT44 95,4 582 RCDLU
IN45 95,3 708 R-TDCB OUT45 95,3 583 RCDLD
IN46 95,2 1002 DOP/DFO OUT46 95,2 584 RCDGU
IN47 95,1 1030 RDOP/RDFO OUT47 95,1 585 RCDGD
IN48 96,8 SE OUT48 96,8 LVC
IN49 96,7 TCI_UP OUT49 96,7 RRD
IN50 96,6 TCI_DOWN OUT50 96,6 RTD1
IN51 96,5 691 TCI OUT51 96,5 RTD2
IN52 96,4 OUT52 96,4
IN53 96,3 OUT53 96,3
IN54 96,2 OUT54 96,2
IN55 96,1 OUT55 96,1
Page: 139 / 196
Berlin
I/O Architecture:
For each I/O, the location of the signal can be individually programmed.
The following locations are possible:
1) RSL at GECB
2) CARIO-board (new for LVA)
3) RSL at CARIO board (new for LVA)
When programming an I/O, first select the location, then the desired address/pin, as de-
scribed in GAA30780EAN_STM.doc
Note that both RSLs (GECB and CARIO) have an own complete address range 4-63.
The CARIO board has a fixed address range 90-95, where each address provides bits 1-8.
Controller Car
GECB TOCB/COPG-III
OFT:
M132-2 „CARIO“
CAN
M132-3 „RSLviaCAN“
M132-1 „RSL“
CARIO
(90.1 - 95.8)
RSL - hall/group RSL - car

(4.1 - 63.4) (4.1 - 63.4)
LT2 LT2
(50 Ohm) (50 Ohm)
For the hall and group RSL, use M-1-3-2, and select 1=RSL.
For the discrete I/Os at the CARIO board, use M-1-3-2, and select 2=CARIO
For the car RSL at the CARIO board, use M-1-3-2, and select 3=RSL via CAN.
Page: 140 / 196
Berlin
10.3 ACD with CSPB

The ACD Controller with a CSPB CarIO board requires the following parameter and IO
setup:
Install Parameters:
1-SYSTEM EN-CARIO 5 CARIO supports LV signals and includes RSL Master
I/O Numbers:
Use M-1-3-2, and select 2=CARIO to program IOs on the cario link.
IO Number Name Description Type Link Address

0000 DOL Door Open Limit in cario 93 4
0001 DOB Door Open Button in cario 93 8
0605 DOS Door Open Signal in cario 93 5
0607 LRD Light Ray Device in cario 93 6
0694 DCL Door Close Limit in cario 94 4
0691 TCI Top-of-Car Inspection switch in cario 96 5
0993 ST3 ST3 for front+rear DO1000 (DCSS5) out cario 93 6
0026 LR Light relay out cario 93 2
Page: 141 / 196
Berlin
11 Signal Devices
11.1 CPI-11 - ELD Car Position Indicator

The setup procedure for GECB is exactly the same as for RCBII. Please refer to the
Field Component Manual for MCS-RCB_II: Feature Description and Setup Guide
GCA21270A VIIIe, since version GAE30075GAA from 30-Sep-96.
For GECB there is one additional parameter which is not described in the a.m. document. It
enables/disables the customer messages of the ELD:
Install Parameters (Group):

1-SYSTEM EN-MSG 0 Customer messages can be setup in the E2PROM of the GECB
and downloaded to the ELD, but the automatic Customer Mes-
sage Initialization after PowerOn is disabled so that the ELD will
loose the Customer Messages after the power has been turned
off.
1 A complete initialization is done at every PowerOn so that the
messages are available all the time.
11.2 OOS - Out Of Service

To indicate that the elevator is not on service there are three types of outputs available:
557 OOS1B (active = high) Is active when the lift is not able to run.
558 OOS1M (active = low) (OCSS Modes DAR, DBF, INS, NAV, UFS)
737 OOL (active = low)
878-909 OOL0-31 (active = low) Is active when the lift is not able to run (i.e. as OOS1)
(OCSS Modes DAR, DBF, INS, NAV, UFS)
Since GAA30780EAN, is also active during EFO
559 OOS2B (active = high) Is active when the lift is not available for ‘normal’ passengers.
560 OOS2M (active = low) (OCSS Modes CHC, CTL, DTC, DTO, ISC, PKS)
713 OOS for REM See description below

(active = low)
Page: 142 / 196
Berlin
11.3 CDI,HDI,CDL,HDL,CNG - Direction Indicator / Lantern / Gong

The following tables describe the outputs which can be used for direction indicators,
lanterns and gongs.
I/O Name Name Loc. Description
549 HUDL Hall Up Direction Light hall car is moving up or has a demand in up direction.
Flickering can be enabled by EN-SFR=2
550 HDDL Hall Down Direction Light hall car is moving down or has a demand in down direction
29 STH Stop Signal Hall hall is active when car does not move
566 RHUDL Rear Hall Up Direction Light hall car is moving up or has a demand in up direction
567 RHDDL Rear Hall Down Direction Light hall car is moving down or has a demand in down direction
572 RSTH Rear Stop Signal Hall hall is active when car does not move

20 CUDL Car Up Direction Light car car is moving up or has a demand in up direction; for front COP
21 CDDL Car Down Direction Light car car is moving down or has a demand in down direction; for front COP
30 STC Stop Signal Car car is active when car does not move; for front COP
564 RCDUL Rear Car Up Direction Light car car is moving up or has a demand in up direction; for rear COP
565 RCDDL Rear Car Down Direction Light car car is moving down or has a demand in down direction; for rear COP
573 RSTC Rear Stop Signal Car car is active when car does not move; for rear COP
578 CDLU Car Direction Lantern Up car car has a demand in up direction; for front COP
579 CDLD Car Direction Lantern Down car car has a demand in down direction; for front COP
582 RCDLU Rear Car Direction Lantern Up car car has a demand in up direction; for rear COP
583 RCDLD Rear Car Direction Lantern Down car car has a demand in down direction; for rear COP

723 FCDGU Front Car Direction Gong Up car while the front door is not closed and the car has a demand in up
direction; for front COP
724 FCDGD Front Car Direction Gong Down car while the front door is not closed and the car has a demand in down
direction; for front COP
584 RCDGU Rear Car Direction Gong Up car the car has a demand in up direction; for rear COP…
CONFIG=0:
while the rear door is not closed
CONFIG0:
for 1.5 seconds after rear door began to open
585 RCDGD Rear Car Direction Gomg Down car the car has a demand in down direction; for rear COP…
CONFIG=0:
while the rear door is not closed
CONFIG0:
for 1.5 seconds after rear door began to open
580 CDGU Car Direction Gong Up car the car has a demand in up direction…
CONFIG=0:
any door is not closed
CONFIG0:
for 1.5 seconds after front door began to open
581 CDGD Car Direction Gong Down car the car has a demand in down direction…
CONFIG=0:
any door is not closed
CONFIG0:
for 1.5 seconds after front door began to open
Page: 143 / 196
Berlin

719 UHDI Up Hall Direction Indicator hall car is moving up or has a demand in up direction
718 DHDI Down Hall Direction Indicator hall car is moving down or has a demand in down direction

128 – 159 UHL0 – UHL 31 Up Hall Lantern hall Up Hall Lantern for each opening
160 – 191 DHL0 – DHL31 Down Hall Lantern hall Down Hall Lantern for each opening
384 – 415 RUHL0 – RUHL31 Rear Up Hall Lantern hall not used
416 – 447 RHDL0 – RHDL31 Rear Down Hall Lantern hall not used
814 – 845 UHDL0 – UHDL31 Up Hall Direction Indictor / Lantern hall HDL-TYP=0:
Up Hall Direction Indicator for each opening
HDL-TYP=1:
Up Hall Lantern for each opening
846 – 877 DHDL0 – DHDL31 Down Hall Direction Indictor / Lan- hall HDL-TYP=0:
tern Down Hall Direction Indicator for each opening
HDL-TYP=1:
Down Hall Lantern for each opening
Related parameters:
1-SYSTEM EN-SFR Affects the behaviour of the I/Os 549 HUDL, 550 HDDL, 718 DHDI, 719
UHDI, 814-845 UHDLxx and 846-877 DHDLxx
0 The above I/Os are constantly on.

2 The above I/Os are constantly on, when the car has stopped and
are blinking, when the car moves.
1-SYSTEM HDL-TYP Affects the behaviour of the I/Os 814-845 UHDLxx and 846-877 DHDLxx
0 I/Os are used as Direction Indicator, i.e. all I/Os are showing the
same information at all landings.
1 I/Os are used as Hall Lantern, i.e. only that lantern will be lit
where the door will open.
2 Hall Lantern with flickering
Page: 144 / 196
Berlin
11.4 FMO - Fixture Maintenance Operation

This function allows to easily verify the proper function of the hall TTLs and lanterns.
1. Use SVT to activate M-1-2-8 Test Fixture

2. Enter car
3. Activate ISC (I/O 0004 ISS)
4. Move from floor to floor to inspect the hall fixtures
5. Deactivate ISC
6. Leave SVT menu M-1-2-8
Affected I/Os:
I/O Name Name Loc.
64..., 3200... UHB Up Hall TTL group
96..., 3300... HB Down Hall TTL Group
192..., 3400... EHC Emergency Hall TTL Group
3700... eUHB Extended Up Hall TTL Group
3800... eHB Extended Down Hall TTL Group
3900... eEHC Extended Emergency Hall TTL Group
128..., 4000... UHL Up Hall Lantern Hall
160..., 4100... DHL Down Hall Lantern Hall
814..., 4200... UHDL Up Hall Lantern / Direction Indicator Hall
846..., 4300... DHDL Down Hall Lantern / Direction Indicator Hall
11.5 REM Signals
The following signals are provided for REM and are transmitted simultaneously on the RSL
outputs and the Service Tool output (for REM-SL):
signal Name The signal is active when: GECB
ARO Automatic Res- operational mode ARO is executed +

cue Operation
BUT Button  There are outstanding calls to a different landing +
 A correction run is done
 The car is moving in INS
BUT is not activated during a Releveling run
DO Door Open LCB_IIC: +
REM-TYP=0: When any door is opening or fully
opened
REM-TYP=1: When input DFO is active (stays active
for at least 200 ms)
REM-TYP=2: When front door is opening or fully
opened
Page: 145 / 196
Berlin
DO Door Open GECB:

opened
REM-TYP=1: When input DFO is active (stays active
for at least 200 ms)
opened (same as REM-TYP=0)
DC Door Close  When front door is closing or fully closed +

RDO Rear Door Open  When rear door is opening or fully opened +
RDC Rear Door  When rear door is closing or fully closed +
Close
CPR Car Park  Car is parking +
 Moving to bottom in DAR mode
NORM Normal  Is inactive in the following modes: +
ATT, EFO, EFS, EHS, EPC, EPR, EPW, ISC
MF Main Floor REM-TYP = 1 (REM-G, HKM): +
 Is activated when car is approaching a landing; is
deactivated when the car is leaving the landing
REM-TYP = 0, 2: +
 when car is in lobby floor
LND Landing  Activated in every doorzone +
LEV Level  input LEV (I/O 0793) is active +
DZ Door Zone  Activated in every doorzone +
OOS Out Of Service Activated immediately when:

 DDP -
 DTO +
 DTC +
 DCS-Fault +
 UFS -
 SE-Fault +
 OTS-Lock for AHVS -
 DoorStall -
 DPB-Fault -
 Door Lock Monitoring +
 Hoistway Access +
 EAR (HCB) -
 TCI-Lock +
 RBU-Fault (LCB_IIC) -
30 sec after:
 NAV +
 Doors closed but DOL active +
 DBSS not available (DAR, DBF) +
 MCSS not available +
 OLD +
 LNS but no further demand +
Page: 146 / 196
Berlin
UP Moving Up the car is moving upwards +

DOWN Moving Down the car is moving downwards +
BRK Brake  Brake is lifted +
SAF Safety Chain  ES input is active (safety chain closed) +
RFS Request for  SPB reports an error (event 0600) +
Service  BAT-Fault (HCB) -
 SPB-Comm failure (event 0011) +
 Drive (event 0220) (only up to GAA30780BAA) +
 LWB_II (event 0602) (only up to GAA30780BAA) +
 SPBC (event 0606) +
 ARO (event 0603) +
SPBF Service Panel  SPB reports an error (event 0600) +
Board Fault  SPBC (event 0606) +
 ARO (event 0603) +
SCS Slack Belt  input 2TH is active +
Switch  input 2SE (BCB_II) is inactive -
HTS Hall Tempera-  SPB reports that Hall Temperature in the E&I Pan- +
ture Sensor el is too high (event 0601)
DS Door Switch  if door bypass enabled: input DW is active +
if door bypass disabled: input DFC is active
CLM Car Light Moni-  Is activated when CLR (I/O 1000) is active +
toring
CLS Car Light Signal For House Keeper Module (HKM) +
I/O1001  Is activated when CLR is active (I/O 1000)
DOP Door Open  input DFO/DOP is active (I/O 1002) +
RDOP Rear Door Open  input RDFO/RDOP is active (I/O 1030) +
Notes:
(1) signal is only sent if REM-TYP=2
(2) signal is only sent if REM-TYP=2 and rear door exists in Allowed Mask
RFS from GECB:

Since version GAA30780DAD the RFS signal is delayed for 5 minutes for REM-TYP 0-5.
signal Name The signal is active when: GECB GECB_II
RFS Request for  SPB reports an error (event 0600) + +
Service  SPB-Comm failure (event 0011) + +
 SPBC (event 0606) + +
 ARO (event 0603) + +
 BCB_II missing (event 0702) - +
 BCB_II I/O failure (event 0703) - +
 BCB_II HW failure (event 0704) - +
 Rescue Encoder failure(event 0706) - +
 OCB failure (event 0707) - +
 over speed (event 0708) - +
 battery missing (event 0710) - +
- +
 battery temperature out of range (event 0711)
- +
 battery defect (event 0712)
- +
 no battery charge signals (event 0713) - +
 battery low voltage (event 0714) - +
Page: 147 / 196
Berlin
11.6 TRIC - Trip Counter

The Trip Counter is used to count the number of runs of a unit. This can be used to evaluate
the wearance of relays etc.
There are several possibilities to connect the TRIC device to the controller:
I/O-Numbers for all Controllers:
no. name Description connected to type location
805 UD Up Down TUAC1 out car
In addition to the RSL output, the GECB also provides a discrete output signal:
Discrete Output
no. Board Controller parameter
PX2.1 GECB-EN Gen2, GCS222MMR SYSTEM – PX2.1 = 1
P3.16 GECB_II GCS222MRL (E&I Panel Controller) None
11.7 Voice Announcement for Handicapped Person for Korea

ACD2 is using the indicator information on CPI11 protocol for the Korean SSM (Speech
Synthesis Module). Additionally, the voice message for handicapped person was added.
This message is sent to the Korean SSM when a car call is registered and the Korean SSM
will output "floor x is registered" to the speaker in SSM.
Also a message (e.g. "floor x is canceled") will be sent to the Korean SSM when a
registered car call is canceled.
Install Parameters:
1-SYSTEM PI 7 Korean PI Protocol
12 LW - Load Weighing
12.1 In Car Load Weighing via CAN Bus

Used parameters:
LW-TYP (0)
Needed environment:
Page: 148 / 196
Berlin
LWB_II or MCB_III with integrated analog load weighing
12.2 Dead End Hitch Load Weighing via CAN Bus

Used parameters:
LW-TYP (1); ANS(kg); PEAK(%); LNS(%); OLD(%);
Needed environment:
Dinacell rope sensor with CAN interface
MCB_IIIx with software GAA 30785 AAA or higher
The drive receives the rope load from the sensor via CAN, calculates the ‘in car load’ for the
OCSS and transmitts it to the OCSS via CAN.
12.3 Discrete In Car Load Weighing via RS Inputs for CAN drives
This load weighing typ is available since the following software version:
GECB: GAA30780BAA
used parameters:
LW-TYP (2)
used RSL io’s:

RSL io # name load active SVT Status Input:
displayed as
0007 LWX (ANS) < 10 % X LWX
0007 LWX (ANS) > 10 % - lwx
1043 LW30 > 30 % X L30
1044 LW50 > 50 % X L50
0006 LNS > 80 % X LNS
0005 LWO (OLD) >110 % X LWO
Page: 149 / 196
Berlin
needed environment:
5 discrete load sensors
The drive can request via CAN the load information from the OCSS. The OCSS answers
with the load information in % (not in kg) via CAN.
12.4 Discrete Inputs for hydraulic

This load weighing typ is available since the following software versions:
GAA 30780 EAD
used parameters:
LW-TYP (4) (only useable at LCB_IIC)
Plug name
P1.7 OLD-M
P1.8 LNS-M
12.5 Discrete Car Inputs for none CAN drives

GAA 30780 EAD
used parameters:
used RSL io’s:

Page: 150 / 196
Berlin

displayed as
0007 LWX (ANS) < 10 % X LWX
0007 LWX (ANS) > 10 % - lwx
0006 LNS > 80 % X LNS
0005 LWO (OLD) >110 % X LWO
12.6 Discrete Machineroom Inputs for none CAN drives

GAA 30780 EAD
used parameters:
used RSL io’s:

displayed as
0007 LWX (ANS) < 10 % X LWX
0007 LWX (ANS) > 10 % - lwx
0721 LNS-M > 80 % X LNS
0722 OLD-M >110 % X LWO
12.7 Disable Overload (OLD)

Used parameters:
LW-TYP (253, 255)
 LW-TYP=253, ‘Disable OLD’ is available only if actual load percent is less than 125%.
(since GAA30780EAE)
 LW-TYP=255, no limitation.
Page: 151 / 196
Berlin
13 Inputs
13.1 1TH - Thermal contact 1

Upon activation of 1TH, the event 0222 “1TH-Fault” is logged and the OCSS mode DBF is
entered. That means that the car will finish the current run and opens the door at the target
landing for DAR-T and then shutdown with closed doors. Once the car has stopped, the
drive is powered down to allow cool-down.
Note that 1TH is not effective during MRO.
The devices which are typically connected to this input are:
DBR, THB, J-Relay
When the input is inactive, the drive is powered up and normal operation is resumed.
13.2 2TH - Thermal contact 2

Upon activation of 2TH, the event 0223 “2TH-Fault” is logged and the OCSS mode DBF is
entered. That means that the car will finish the current run and opens the door at the target
landing for DAR-T and then shutdown with closed doors.
Note that 2TH is not effective during MRO.
The devices which are typically connected to this input are:
THB, SCS, BID (CSB Monitor)
When the input is inactive, normal operation is resumed.
13.3 HTS - Hall Temperature Sensor

The Hall Temperature Sensor HTS is located at the Service Panel Board SPB and is
transmitted to the control board via CAN bus. The trigger level of the HTS can be adjusted
with the parameter SPB-Temp.
The HTS is not effective during EFO, EFS and MRO.
When the temperature raises above the trigger level, the event 0601 “SPB:TempHTS” is
logged and the OCSS mode DBF is entered. That means that the car will finish the current
run and opens the door at the target landing for DAR-T and then shutdown with closed
doors.
When the temperature falls below the trigger level, normal operation is resumed.
Page: 152 / 196
Berlin
14 TBF - Time Based Features (Real Time Clock)

The functions described in this chapter are only available in GECB. They were introduced in
GAA30780DAB.
The GECB includes a real time clock which can be used to activate selected features at a
specific time. The user can select up to 4 features, with separate time settings for each
feature.
The software is able to automatically adjust the clock for Daylight Saving Time (i.e.
Summertime/Wintertime).
14.1 DST - Daylight Saving Time (Summertime/Wintertime)

1. Set the correct date and time using the Service Tool menu M-1-3-8. For a description of
this menu, please refer to Gxx30780xxx_STM.
2. If your country has Daylight Saving Time (i.e. Summertime/Wintertime), set the
parameters to tell the software when to automatically adjust the clock. The clock will be
adjusted at 2:00 am.
If Summertime starts at the last Sunday in March, set the following parameters:
SUMtmMTH = 3
SUMtmSUN = 0
If Wintertime starts at the last Sunday in September, set the following parameters:
WINtmMTH = 9
WINtmSUN = 0
Related parameters:
11-TIME SUMtmMTH 0 automatic summer time setting is disabled
1-12 Month in which the clock is automatically set ahead by one
hour.
(1=Jan, 12=Dec).
SUMtmSUN 0 The clock will be automatically set ahead at the last Sunday
of the month.
st th
1-4 The clock will be automatically set ahead at the 1 – 4
Sunday of the month.
WINtmMTH 0 automatic winter time setting is disabled

1-12 Month in which the clock is automatically set back by one
hour.
(1=Jan, 12=Dec).
WINtmSUN 0 The clock will be automatically set back at the last Sunday
of the month.
st th
4 The clock will be automatically set back at the 1 – 4
Sunday of the month.
Page: 153 / 196
Berlin
14.2 NNR - Night Noise Reduction

This feature can be used to prevent the ambient noise by chime, gong and voice
synthesizer during the night in an apartment.
The chime or gong is deactivated and synthesizer volume is decreased (or excluded) when
the Real Time Clock reaches a designated time zone.
Related parameters:
11-TIME NNR-SHR 0-23 Hour at which Night Noise Reduction starts
NNR-SMI 0-59 Minute at which Night Noise Reduction starts
NNR-EHR 0-23 Hour at which Night Noise Reduction ends
NNR-EMI 0-59 Minute at which Night Noise Reduction ends
Affected I/Os:
723 FCDGU car Front Car Direction Gong Up
724 FCDGD Car Front Car Direction Gong Down
584 RCDGU Car Rear Car Direction Gong Up
585 RCDGD Car Rear Car Direction Gong Down
580 GNCUP Car Car Direction Gong Up
581 GNCDN car Car Direction Gong Down
Affected Devices:
Korean Speech Board
Example:
If the gong shall be switched off between 22:30 and 6:45 every night, set the following
parameters:
NNR-SHR = 22
NNR-SMI = 30
NNR-EHR = 6
NNR-EMI = 45
14.3 TFA - Time Based Feature Activation

The Real Time Clock can be used to activate specific features like PKS or CCO at defined
times. The user can select 4 of 11 different features and define separate time settings for
each feature. These 4 features are defined by the parameters TFA1-xxx to TFA4-xxx:
1. Set TFAx-OP to select which feature shall be activated.
2. Set TFAx-TYP to define whether that feature shall be activated based on time or based
on weekday or both.
Page: 154 / 196
Berlin
3. If desired, set TFAx-SHR and TFAx-SMI to define the time when the feature shall be
activated.
4. If desired, set TFAx-EHR and TFAx-EMI to define the time when the feature shall be
deactivated.
5. If desired, set TFAx-WEK to define on which weekday the feature shall be activated
Example:
Normally, a Simplex elevator shall park at the lobby, which is at floor 1. From Monday to
Friday at the end of lunch time (13:00 – 14:00), the car shall park at the restaurant, which is
at floor 4.

1-SYSTEM LOBBY 1 Floor 1
2-OCSS ARD-P 1 Floor 1 (Lobby)
PARK-1 4 Floor 4 (Restaurant)
11-TIME TFA1-OP 4 Activate PCLK1 as defined below
TFA1-TYP 3 Activate PCLK1 based on time and weekday
TFA1-SHR 13 Activate PCLK1 at 13:00 (1:00 pm)
TFA1-SMI 0
TFA1-EHR 14 Deactivate PCLK1 at 14:00 (2:00 pm)
TFA1-EMI 0
TFA1-WEK 62 Activate PCLK1 on Monday to Friday
Page: 155 / 196
Berlin
15 Battery Backup Rescue

For Systems with BCB_II the BAT-CHRG parameter must be configured:
1- SYSTEM
No. Symbol needed possible values for this feature
value
051 BAT-CHRG 0-1 Battery Charge Mode
0 not during run (for small transformer configurations)
1 always (for normal transformer configurations)
15.1 ARO (Automatic Rescue Operation)
15.1.1 ARO with GECB-EN

ARO will be initiated by the SPBC_III. More Details about the preparing ARO phase are
described in the SPBC_III Software Basic Data (GAA30773xxx_BD or GAA31049xxx_BD).
needed environment:
SPBC_III with software GAA 30773 BAA or higher
MCB_IIIx with software GAA 30785 BAA or higher
GDCB with software AAA 30924 CAC or higher
ARO-Sequence:
The SPBC_III powers up the GECB by battery power. The GECB confirms the operational
mode ARO (requested by the SPBC_III). The SPBC_III powers up the drive after the
confirmation. Then the operational mode ARO is running (see chapter 2.4). The SPBC_III
waits for the message “AROfinished” from the GECB to switch off the drive and GECB from
battery power.
Optimized ARO-Sequence (for ACD Controller):

The SPBC_III powers up the drive by battery power. The regen drive generates and
supplies power to the rest of the control system. GECB confirms the operational mode ARO
(requested by the SPBC_III). Then the operational mode ARO is running (see chapter 2.4).
The SPBC_III waits for the message “AROfinished” from the GECB to switch off the drive
from battery power.
Page: 156 / 196
Berlin
15.1.2 ARO with GECB_II

ARO will be initiated and controlled internally by the GECB_II. The GECB_II is powered
uninterruptable by the main power or a battery. The GECB_II controls the rescue relays and
the ARPB. The BCB_II is only a remote I/O CAN node and battery control unit. The BCB_II
decides between battery and normal mode. If the BCB_II does not detect a power fail, the
drive can detect a line fail and communicates it to the GECB_II.
needed environment:
BCB_II with software GAA 31054 AAA or higher
GDCB with software AAA 30924 CAF or higher
ULTRA with software AAA 31400 AAD or higher
The SVT menu’s M-1-1-9 “Status-Rescue” and M-1-2-9 “Test-ARO” are useful to investigate
ARO. ARO initiated by “TEST-ARO” ignores the pre-conditions “3 normal runs have been
executed after OCB switched off/on or after TCI/ERO state”.
A line L1 and / or L2 failure will be detected by supervising the BCB_II power supply from
the main transformer. A line L3 failure will be detected by the drive. At the end of ARO the
GECB_II resets itself, if the main power will be back. This prevents synchronization prob-
lems with other upcoming components (like drive…).
If ARO cannot be finished (e.g. drive is in shutdown mode for a long time after start up), the
GECB_II will start 2 further tries with a delay of 2 minutes.
ARO-Sequence:
Step Description
1 power fail
2 RR2 active; ARO relays active; event ‘AROstarted’ logged; operational mode ARO requested
3 read back contact of ARO relays checked
4 RR1 active (drive powered up)
5 read back contact of RR relays checked
6 ARPB active (main transformer operates)
7 operational mode ARO running (see chapter 2.4)
8 operational mode ARO is executed
9 ARPB inactive
10 RR1 inactive
11 RR2 inactive
12 waiting for main power
13 reset of the GECB_II
Page: 157 / 196
Berlin
Pre-conditions for ARO:

condition signal
none BCB_II detected -
BCB_II is in battery mode or Drive detected line fail BCB_II TRF_VOLT is too low or
(both: longer than 1.5s) L1/L2/L3 is to low at drive
rescue encoder speed is 0m/s -
OCB is still on OCB_STB inactive /
OCB_STM active
3 normal runs have been executed after OCB switched off/on or after -
TCI/ERO state (exception: ARO test via SVT)
3 normal runs has been executed after the last ARO -
(exception: ARO test via SVT)
EFO & EFS & EQO are not executed -
TCI / ERO / TCI-Lock is inactive discrete: /ERO
RSL: IO691
none OCB failure none event 0707
battery available none event 0710
inactive RR relays BCB_II RR_IN inactive
battery voltage is above 43.5 Volt Ubat
Abort-conditions for ARO:

abort condition signal
OCB switched off OCB_STB active /
OCB_STM inactive
Operational mode ARO aborts ARO see chapter 2.4
TCI / ERO discrete: /ERO
ARO operates for longer than 6 minutes -
battery voltage is below 43.5 Volt for more than 15s Ubat
ARPB controlling:
The ARPB (ARO converter) is used to transform 48Volt to 400V for the main transformer.
The ARPB is controlled via BCB_II output EN_ARO_CONV. The ARPB needs more
information than ‘On’ and ‘Off’. Because an active brake coil stresses the converter much
more than an inactive brake coil, the converter needs the 3 commands: off, low power, full
power.
If the brake will be lifted, the converter must switch into ‘full power’ mode until the brake will
be dropped. The GECB_II uses the drive states & the rescue encoder to decide the
converter command.
command to converter EN_ARO_CONV

OFF LOW
LOW_POWER HIGH
FULL_POWER 15ms LOW / 60ms HIGH
Page: 158 / 196
Berlin
15.1.1 ARO with GECB_LV

ARO will be initiated and controlled internally by the GECB_LV. The GECB_LV is powered
uninterruptable by the main power or a battery. The GECB_LV controls the rescue relays.
The LVPB is only a remote I/O CAN node and battery control unit. The LVPB decides
between battery and normal mode. If the LVPB does not detect a power fail, the drive can
detect a line fail and communicates it to the GECB_LV.
Needed environment:
LVPB with software GAA 30891AAB or higher
GDCB with software AAA 30924 GAF or higher
ULTRA with software AAA 31400 DAA or higher
SP with software GAA 31061 BAB or higher
The SVT menu’s M-1-1-9 “System-Status-Rescue” and M-1-2-9 “System-Test-ARO” are

useful to investigate ARO. ARO initiated by “TEST-ARO” ignores the pre-conditions “3
normal runs have been executed after OCB switched off/on or after TCI/ERO state”.
A line L1 and / or L2 failure will be detected by supervising the LVPB power supply from the
main transformer. A line L3 failure will be detected by the drive. At the end of ARO the
GECB_LV resets itself, if the main power will be back. This prevents synchronization prob-
lems with other upcoming components (like drive…).
If ARO cannot be finished (e.g. drive is in shutdown mode for a long time after start up), the
GECB_LV will start 2 further tries with a delay of 2 minutes.
ARO-Sequence:
Step Description
1 power fail
2 RR2 active; ARO relays active; event ‘AROstarted’ logged; operational mode ARO requested
3 read back contact of ARO relays checked
4 RR1 active (drive powered up)
5 read back contact of RR relays checked
6 operational mode ARO running (see chapter 2.4)
7 operational mode ARO is executed
8 RR1 inactive
9 RR2 inactive
11 reset of the GECB_LV
Page: 159 / 196
Berlin
Pre-conditions for ARO:

condition signal
none LVPB detected -
LVPB is in battery mode or Drive detected line fail LVPB DC_GOOD is low or L1/L2/L3
(both: longer than 1.5s) is too low at drive
rescue encoder speed is 0m/s -
OCB is still on OCB_ON active
3 normal runs have been executed after OCB switched off/on or after -
TCI/ERO state (exception: ARO test via SVT)
3 normal runs has been executed after the last ARO -
(exception: ARO test via SVT)
EFO & EFS & EQO are not executed -
TCI / ERO / TCI-Lock is inactive discrete: /ERO
RSL: IO691
none OCB failure none event 0707
battery available none event 0710
inactive RR relays RR_IN inactive
Abort-conditions for ARO:

OCB switched off OCB_ON inactive
Operational mode ARO aborts ARO see chapter 2.4

TCI / ERO discrete: /ERO
ARO operates for longer than 6 minutes -
Page: 160 / 196
Berlin
15.2 MRO (Manual Rescue Operation)
15.2.1 MRO with GECB-EN

MRO controlled by the SPBC / SPBC_II:
The GECB is not powered during MRO.
MRO controlled by the SPBC_III:
The GECB is powered by battery to enable SVT navigating. The operational mode NAV is
active during MRO.
15.2.2 MRO with GECB_II

MRO will be controlled internally by the GECB_II. The GECB_II is powered uninterruptable
by the main power or a battery. The GECB_II controls the rescue relays. The BCB_II /
BCB_III is only a remote I/O CAN node and battery control unit. The SP is used a position
and speed indicator. In addition the SP controls the BRB1 button (Brake Release Button to
start MRO). The rescue encoder is connected at the GECB_II.
needed environment:
BCB_III with software GAA 31054 AAC or higher
GDCB with software AAA 30924 CAF or higher
ULTRA with software AAA 31400 AAD or higher
SP with software GAA 31061 AAA or higher
Page: 161 / 196
Berlin
Install-Parameters:
7- SERVICE
value
000 SPB-TYP 1 Type of Service Panel Board
1 SP (Service Panel) (e.g. GCS222MRL)
001 Encoder 13-15 Pulse Width of Rescue Encoder (mm car movement between
2 pulses), depends on machine
Yaskawa 1.5T: 14
Kollmorgen 2.5T: 13
Kollmorgen 5T: 15
004 BRE-MAX 1-12 Maximum speed for Brake Release Electrical
0.01 (0.01) 0.12 m/s
Rescue Architecture Example
Car CAN Bus
SP GECB_II GDCB BCB_II

SCN: 31061
SCN: 30780 SCN: 30924 SCN: 31054
features: features: features:

•MRO •add. Line fail detection •battery control
•ARO Power Supply Control •MRO / ARO support •I/O
SVT Plug
•BCB_II control •rescue power supply
SVT Plug •Rescue Encoder Supervisor •temperatur meas.
•SP control •battery V. meas.
SVT Plug
•transformer V. meas.
48 Vdc
+ -
400 Vac 24/69 Vac

Rescue encoder speed encoder
Page: 162 / 196
Berlin
The SVT menu’s M-1-1-9 “Status-Rescue” is useful to investigate MRO.

The OCB must be switched off to enable MRO. The GECB_II starts MRO after operating
the BRB1 at the SP. The BRB2 (key switch) must be operated directly after (or before)
operating the BRB1.
The speed indicator at the SP must be always watched by the operator and in case of over
speed and / or an active buzzer, BRB1 and BRB2 must be released. The buzzer sounds for
1s after reaching DZ.
If the car speed will be faster than 0.3m/s during MRO run, the buzzer sounds until BRB1 or
BRB2 will be released or the speed goes lower than 0.3m/s.
If you switch the OCB on after MRO and the main power is available, the GECB_II resets
itself. This prevents synchronization problems with other upcoming components (like
drive…).
15.2.2.1 MRO_BL (with BCB_II & 4x 12V battery)
MRO Balancend Load (MRO_BL):

The GECB_II tries always to move the car in “MRO with drive” mode. If this does not work,
the GECB_II switches in “MRO without drive” mode (brake & speed control by the
GECB_II).
MRO_BL - Sequence:
Step Description
1 OCB switched off by user
2 BRB1 & BRB2 operated by user
3 GECB_II activates RR1 & RR2; OCSS mode NAV active; drive powered up by battery
4 read back contact of RR relays checked by GECB_II
5 Drive publishes “preferred direction” to GECB_II
6 GECB_II command to BCB_II: input BRB2_IN routed to output VF_BR
7 GECB_II waits for drive state IDLE
8 GECB_II sends rescue run command to drive; GECB_II activates BRB1_OUT (brake power supply)
9 300ms delay (drive can check it’s UIB/DIB inputs)
10 GECB_II activates BCB_II output MRO_SAF (110V)
11 Drive runs
12 Drive stops at DZ (flush with hall level)
13 GECB_II activates the buzzer for one second; GECB_II deactivates BRB1_OUT (brake power supply);
GECB_II deactivates BCB_II output MRO_SAF (110V)
14 BRB1 & BRB2 released by user
15 5 seconds delay
16 GECB_II deactivates RR1 & RR2
17 OCB switched on by user
Page: 163 / 196
Berlin
Pre-conditions for MRO_BL:

condition signal
OCB is off OCB_STB active
BRB1 is operated at the SP via CAN
BRB1_ON (internal GECB_II input connected to P6.2 BRB1_OUT) is off BRB1_ON inactive
before MRO was initiated (prevents problems with wrong wiring)
BRB2 is operated before the drive starts to run BRB2_IN active
inactive DISRD (displayed as input: AB2) AUX_B2_IN active
none encoder failure before none event 0706
none OCB failure before none event 0707
none over speed before none event 0708
Abort-conditions for MRO_BL:

OCB switched on OCB_STB inactive
active DISRD AUX_B2_IN inactive
BRB1 released for more than 20 seconds -
encoder failure event 0706
MRO direction turn:

The GECB_II turns the rescue direction and starts a new rescue run, if the car does not
move within 6s seconds after rescue run command. The direction turn happens only once. If
the car does not move within 6s in the other direction, the GECB_II will switch into “MRO
without drive” mode.
There are 3 reasons for the GECB_II to switch automatically into “MRO without drive” mode:
 The drive does not respond with the “preferred direction” after request within 6 sec-
onds at the initialize phase of MRO.
 The drive cannot move the car (both directions tried).
 The battery voltage is below 43.5 Volt for more than 15 seconds during MRO.
“MRO without drive” differences:

 RR1 & RR2 are deactivated
 GECB_II controls directly the brake (GECB_II command to BCB_II: input BRB2_IN
routed to output MRO_BR)
 The brake will be lifted as long as the speed is below the parameter BRE-MAX. This
lets the car move by gravitation.
 The brake drops as soon as the DZ will be detected (not flush with hall level).
Page: 164 / 196
Berlin
 If the car does not move within 500ms after lifting the brake, the brake will be
dropped to prevent an uncontrolled movement with a defect rescue encoder. Then
BRB1/2 must be released and operated again. This could also happen, if the car
weight + car load is equal to the counterweight (balance load).
If the GECB_II operates in “MRO without drive” mode, you can try “MRO with drive” anytime
again by releasing BRB1 for more than 20s (or switching the OCB off and on) and operating
BRB1 & BRB2 again.
15.2.2.2 MRO_EB (with BCB_III & 12V battery)
MRO External Brake (MRO_EB):

The GECB_II tries always to move the car in “MRO without drive” mode. If this does not
work, the GECB_II switches in “MRO with drive” mode. In both cases the drive doesn’t con-
trols the brake (external brake control). The GECB_II controls always the brake & speed.
MRO_EB - Sequence:
Step Description
3 GECB_II activates 48V_REQUEST output at BCB_III
4 GECB_II activates BRB1_OUT output to lift the brake
5 GECB_II controls car movement by rescue encoder & brake (BRB1_OUT)
6 If the car does not move within 500ms after brake lifting, the GECB_II switches into ‘MRO with Drive’
mode
7 GECB_II activates RR1 & RR2; OCSS mode NAV active; drive powered up by battery
8 Drive publishes “preferred direction” to GECB_II
9 GECB_II waits for drive state IDLE
10 GECB_II sends rescue run command to drive;
11 1s delay to prepare the drive
12 GECB_II activates BRB1_OUT to lift the brake
13 The Drive controls the run & speed.
14 GECB_II controls the speed limit of 0.3m/s by rescue encoder & brake (BRB1_OUT)
15 GECB_II checks the DZ; if DZ reached, the GECB_II drops the brake and sends a stop command to
the drive;
16 GECB_II activates the buzzer for one second;
18 5 seconds delay
19 GECB_II deactivates RR1 & RR2 & 48V_REQUEST
20 OCB switched on by user (or earlier)
Page: 165 / 196
Berlin
Pre-conditions for MRO_EB:

condition signal
OCB is off OCB_STB active
BRB1_ON (internal GECB_II input connected to P6.2 BRB1_OUT) is off BRB1_ON inactive
before MRO was initiated (prevents problems with wrong wiring)
BRB2 is operated (not checked by software)
inactive DISRD (displayed as input: AB2) AUX_B2_IN active
Abort-conditions for MRO_EB:

OCB switched on OCB_STB inactive
active DISRD AUX_B2_IN inactive
MRO direction sequence:

 first run: direction independent (without drive, depends on gravitation)
speed < BRE-MAX
 second run: light direction (with drive)
speed < 0.3m/s
 third run: opposite direction (with drive)
speed < 0.3m/s
The GECB_II switches always to the next run type, if the car does not move within 500ms.
After the third run, the BRB’s must be released before a new run can be initiated.
Page: 166 / 196
Berlin
15.2.3 MRO with GECB_LV

MRO will be controlled internally by the GECB_LV. The GECB_LV is powered
uninterruptable by the main power or a battery. The GECB_LV controls the rescue relays.
The LVPB / BCB_II is only a remote I/O CAN node and battery control unit. The SP is used
a position and speed indicator. In addition the SP controls the BRB1 button (Brake Release
Button to start MRO). The rescue encoder is connected at the GECB_LV.
Needed environment:
LVPB with software GAA 30891AAB or higher
GDCB with software AAA 30924 GAF or higher
ULTRA with software AAA 31400 DAA or higher
SP with software GAA 31061 BAB or higher
Install-Parameters:
7- SERVICE
value
000 SPB-TYP 1 Type of Service Panel Board
1 SP (Service Panel) (e.g. GCS222MRL)
001 Encoder 13-15 Pulse Width of Rescue Encoder (mm car movement between
2 pulses), depends on machine
Yaskawa 1.5T: 14
Kollmorgen 2.5T: 13
Kollmorgen 5T: 15
004 BRE-MAX 1-12 Maximum speed for Brake Release Electrical
0.01 (0.01) 0.12 m/s

Page: 167 / 196
Berlin
Rescue Architecture Example
Car CAN Bus
SP GECB_LV GDCB/DCPB LVPB

SCN: 31061
SCN: 30780/30782 SCN: 30924/31400 SCN: 30891
features: features: features:

•MRO •add. Line fail detection •battery control
•ARO Power Supply Control •MRO / ARO support •I/O
SVT Plug
•BCB_II control •rescue power supply
SVT Plug •Rescue Encoder Supervisor •temperatur meas.
•SP control •battery V. meas.
SVT Plug
•transformer V. meas.
48 Vdc
+ -
230 Vac
Rescue encoder speed encoder
The SVT menu’s M-1-1-9 “System-Status-Rescue” is useful to investigate MRO.

The OCB must be switched off to enable MRO. The GECB_LV starts MRO after operating
the BRB1 at the SP. The BRB2 (key switch) must be operated directly after (or before)
operating the BRB1.
The speed indicator at the SP must be always watched by the operator and in case of over
speed and / or an active buzzer, BRB1 and BRB2 must be released. The buzzer sounds for
1s after reaching DZ.
If the car speed will be faster than 0.3m/s during MRO run, the buzzer sounds until BRB1 or
BRB2 will be released or the speed goes lower than 0.3m/s.
If you switch the OCB on after MRO and the main power is available, the GECB_LV resets
itself. This prevents synchronization problems with other upcoming components (like
drive…).
Page: 168 / 196
Berlin
15.2.3.1 MRO-DRV
The GECB_LV tries always to move the car in “MRO with drive” mode. If this does not work,
the GECB_LV switches into “MRO without drive” mode (brake & speed control by the
GECB_LV).
MRO-DRV - Sequence:
Step Description
3 GECB_LV activates 48VDC from LVPB;
GECB_LV switches on CARIO and Drive, Drive is powered up by battery;
OCSS mode NAV active;
4 GECB_LV activates output MRO_48V_OUT and checks input MRO_48V_IN
5 GECB_LV activates outputs RR1 & RR2 and check inputs RR_IN and MRO_BRK_IN
6 Drive publishes “preferred direction” to GECB_LV
7 GECB_LV waits for drive state IDLE
8 GECB_LV sends rescue run command to drive;
GECB_LV activates MRO_BRK
9 Drive runs
10 Drive stops at DZ (flush with hall level)
11 GECB_LV activates the buzzer for one second; GECB_LV deactivates MRO_BRK
13 20 seconds delay
14 GECB_LV deactivates RR1 & RR2
15 OCB switched on by user
17 reset of the GECB_LV
Pre-conditions for MRO-DRV

condition signal
OCB is off OCB_ON active
LVPB in Battery Mode via CAN
MRO_48V_IN (internal GECB_LV input) is off before MRO was initiated MRO_48V_IN inactive
MRO_BRK_IN (internal LVPB input) is off before MRO was initiated MRO_ BRK _IN inactive
No MROBRK fault detected none event 0709
Page: 169 / 196
Berlin
Abort-conditions for MRO-BRK:

OCB switched on OCB_ON inactive
active DISRD: TCI from CARIO, ES, ERO
- If CARIO is not available, MRO is forbidden for TCI or TES, but
allowed for ERO or ES.
- If CARIO is not available, MRO is forbidden for ERO (might be
TCI or TES)
MRO direction turn:

The GECB_LV turns the rescue direction and starts a new rescue run, if the car does not
move within 6s seconds after rescue run command. The direction turn is attempted 5 times.
If the car does not move within 6s in the other direction, the GECB_LV will switch into “MRO
without drive” mode.
There are 3 reasons for the GECB_LV to switch automatically into “MRO without drive”
mode:
 The drive does not respond with the “preferred direction” after request within 6 sec-
onds at the initialize phase of MRO.
 The drive cannot move the car (both directions tried).
 5 drive shutdowns after a run command
“MRO without drive” differences:

 RR1 & RR2 are deactivated
 The brake will be lifted as long as the speed is below the parameter BRE-MAX. This
lets the car move by gravitation.
 The brake drops as soon as the DZ will be detected (not flush with hall level).
 If the car does not move within 500ms after lifting the brake, the brake will be
dropped to prevent an uncontrolled movement with a defect rescue encoder. Then
BRB1/2 must be released and operated again. This could also happen, if the car
weight + car load is equal to the counterweight (balance load).
If the GECB_LV operates in “MRO without drive” mode, you can try “MRO with drive” any-
time again by releasing BRB1 for more than 20s (or switching the OCB off and on) and op-
erating BRB1 & BRB2 again.
Page: 170 / 196
Berlin
16 Remote Elevator Inspection (REI)

The objective of REI operation is to collect data which related elevator performance during
pre-determined operation. (Also, some data shall be collected during normal operation.) The
collected data can be used to adjust elevator system configuration in an effective way. This
feature is recommended for job site under contract with Elite service.
16.1 MEL – Manual Error Log Collection

When the MEL is requested from NMS, the controller shall perform BeforeLog collection
only, the REI operation shall not be performed.
16.2 REI Operation General (Manual REI)

For overall, OCSS shall perform REI operation as following sequence. During the REI mode
operation, the OCSS shall collect the data which is defined as REI mode data collection.
And the elevator shall provide the service to passenger as high priority if hall/car call is
registered by passenger. After service to passenger, elevator shall return to the remained
REI operation. The manual REI by NMS command can be performed regardless of TRG-
TYP.
REI-STEP:
Step Description Remark
0 Normal mode NORMAL
1 Collect log data before REI operation (Before Log) COLLECT_BEFORELOG
2 Return to bottom landing RETURN_BOTTOM
3 going up stopping each floor with door operation STOP_UP
4 going down stopping each floor without door operation STOP_DOWN
5 going up without stopping GOING_UP
6 going down without stopping GOING_DOWN
7 H/W inspection (Car Light) HW_CL
8 H/W inspection (Emergency Light) HW_EL
9 Brake Torque Inspection BTI
10 collect log data after REI operation (After Log) COLLECT_AFTERLOG
11 Return to floor REI operation started RETURN_START
12 Stop to collect before log data STOP_BEFORELOG
13 Wait for normal WAIT
REI-MODE:
Mode Description Remark
0 The REI operation is not initiated. DEACTIVE
1 The REI operation is performing. ACTIVE
2 The REI operation is paused by some reason. (calls..etc) PAUSE
3 The REI operation is recovering from paused. RECOVERED
4 The REI operation is aborted by some reason. (OOS, TPA..) ABORT
Page: 171 / 196
Berlin
5 The REI operation is finished successfully. COMPLETE
Install-Parameters:
10-TEST DBG-REI 0-255 Debug REI Parameter:
95 Clear all variables
97 Display data collection
100 Set REI start from step x (100+x)
251 BTI NG for all 3 steps
st nd rd
252 BTI NG for 1 ,2 steps, OK for 3 step
st nd
253 BTI NG for 1 step, OK for 2 step
254 BTI Test by SVT
255 REI Test by SVT
Note: This parameter is for engineering test and remote expert

12-REI REI-TYP 0-4 REI Type
0 REI disabled
1 REI enabled, no stop at the cut-off floor.
(The GOL blink during the car stop.)
2 REI enabled, stops at the cut-off floor without door operation.
REI is impossible if all floors are cut-off.
(The GOL blink during the door state between opening and
closing.)
3 REI enabled, stops at the cut-off floor without door operation.
REI is possible even if all floors are cut-off.
(The GOL is not blinking.)
4 like 0, but Before logs can still be collected via NMS
TRG-TYP 0-2 REI trigger type
0 By Start Time (self trigger)
1 By Sequential operation (multicar, non-primary units on)
2 No self trigger (uses NMS initiation&collection)
16.2.1 BeforeLog Collection

1. When the REI start command is received from NMS, the OCSS clears all the
measurement results and the logged data of the previous remote inspection under REI
mode. (This step is called ‘BeforeLog Collection’.)
2. The OCSS shall check the condition that REI operation is available or not after finished
BeforeLog Collection. If available, the OCSS starts Returning operation to the lowest
floor. Otherwise, the OCSS shall abort REI operation and stays under step ‘Stop
BeforeLog’.
16.2.2 Returning Operation

1. If REI is available, the car starts running to the lowest floor which is not cut-off floor with
REI-TYP is set to 1. If REI-TYP set to 2 or 3, the car running to bottom floor even if
bottom is cut-off floor.
2. The car responds to any existing or new calls during move to the return floor. However,
in group, it becomes easily allocate hall calls to the other normal operation cars.
Page: 172 / 196
Berlin
3. On reaching the bottom floor, the "PLEASE EXIT Light" (GOL) shall be blinking as
defined REI-TYP.
4. When the door opens at the bottom floor, the measurement of the door opening time
begins. In this case, the door time for bottom floor is fixed to 3 seconds.
5. Even if the car stays at the bottom floor under IDL mode before start REI, the door open
operation is also implemented once under REI mode.
16.2.3 Remote Elevator Inspection Run

1. Upon arrival at the bottom floor, the elevator initiates the remote inspection operation
after the door open, and OCSS starts to send the inspection operational signals to
NMS. (RDO#505)
2. After finished the Returing operation, the OCSS performs floor to floor run from bottom
to top floor with door operation. (This step is called ‘Stop up’.) In this case, the door time
is fixed to 1 second.
3. After finished door operation at top floor, the OCSS performs floor to floor run from top
to bottom flor without door operation. (This step is called ‘Stop down’.)
4. Upon arrival at the bottom floor, the OCSS performs long run from bottom to top floor.
(This step is called ‘Going up’.)
5. Upon arrival at the top floor, the OCSS performs long run from top to bottom floor. (This
step is called ‘Going down’.)
6. During the REI operation, REI data shall be measured.
7. If the top and bottom floors are cut-off floor with REI-TYP is 1, the car runs to the
nearest floor where is not cut-off. With REI-TYP is 2 or 3, the car runs to top and bottom
floor even if there is cut-off floor.
8. During the REI operation, DCB/WDCB are invalid and the door reversal devices, such
as DOB/WDOB/SGS/LRD/EDP are valid. However, the door opening by door reversal
devices is invalid at cut-off floors if REI-TYP is 2 or 3.
9. The OpMode shall be changed if the OLD or DHB is detected during REI. In this case,
the REI shall not be aborted but be paused.
10. Also, calls are assignable during REI. If calls are assigned by passenger, the REI shall
be paused and the car shall serve calls under NOR mode.
11. After 5 seconds without any demands under IDL mode, the car returns to floor where
the REI was paused and restarts REI operation.
Page: 173 / 196
Berlin
16.2.4 Remote Elevator Inspection Check

After finished ‘Going down’, the OCSS starts to check car light, emergency light, and brake
torque in the order.
16.2.4.1 Car Light Check

The confirmation of the lighting-up condition of the car light
1. After the remote inspection operation ends, the lighting-up condition of the car light shall
be monitored for 5 seconds.
2. The lighting-up condition of the car light shall be judged by the input signal from the
electric current sensor.
3. An input signal is provided from the sensor to OCSS via the remote station. However,
an input number depends on the numbers of the car light.
I/O-Numbers:
1177 LIGHT1 Car Light1 in car EAE
1178 LIGHT2 Car Light2 In car EAE
4. The sensor outputs a signal when the car light is turned off.
5. By the input from the sensor which was detected to 5 seconds, the fluorescence light
conditions shall be judged as follows:
6. Data format:
6.1. High Byte 00H (Not used)
6.2. Low Byte Car Light Error
 1 = No Error
 2 = Does not turn on the Light
 3 = Flicker the Light
7. The inspection result of the car light shall be recorded to the log data.
16.2.4.2 Emergency Light Check
- Objective
The ‘Emergency Light Check’ is to collect information about the condition of car emergency
light. This feature is performed as part of REI Operation.
Page: 174 / 196
Berlin
- Operation of the function

1. Data format:
1.1. High Byte 00H (Not used)
1.2. Low Byte: Emergency Light Condition
 Emergency Light condition is OK (01)
 Emergency Light condition is fault (02)
 Hardware error (03)
Install-Parameters:
5 - REI
EmgL-TYP 0 Emergency light type
0 Halogen emergency light (not used)
1 Flueoscent emergency light (not used)
2 LED emergency light
EmgL-T 10 Emergency LED light check time
0-4 default (5 s)
5 (1) 255 s
2. In case of the emergency light is the LED emergency light, (EmgL-TYP=2)

2.1. A switching relay of power supply in the car light is operative by active ELOUT after
the confirmation on the condition of the car light.
2.2. I/O is judged as a fault other than the defect of the car light such as circuit failures if
ELIN1 or ELIN2 is detected before ELOUT becomes active.
2.3. The judgement result of the power supply in the emergency light shall be recorded to
the Logging code.
I/O-Numbers:
1179 ELIN1 Emergency Light Input1 in car EAE
1180 ELIN2 Emergency Light Input2 In car EAE
1181 ELOUT Emergency Light Output out car EAE
3. The criteria of Emergency Light Check

 The car emergency light check is performed for ‘EmgL-T’.
 Switch ELOUT ON for ‘EmgL-T’.
3.1. If both ELIN1/2 are valid

 If both ELIN1 and ELIN2 are not OFF for more than 600ms during ‘EmgL-T’ since
ELIN1 and ELIN2 are ON, the result shall be (01 – OK).
Page: 175 / 196
Berlin
 If either ELIN1 or ELIN2 is OFF for more than 600ms during ‘EmgL-T’ since ELIN1 or
ELIN2 are ON, the result shall be (02 – Fault).
 If either ELIN1 or ELIN2 is ON before ELOUT ON, the result shall be (03 – HW Error).
 If either ELIN1 or ELIN2 is never ON during ‘EmgL-T’, the result shall be (03 – HW
Error).
3.2. If one is valid, the other is invalid

 If valid ELINx is not OFF for more than 600ms during ‘EmgL-T’ since ELINx is ON,
the result shall be (01 – OK).
 If valid ELINx is OFF for more than 600ms during ‘EmgL-T’ since ELINx is ON, the
result shall be (02 – Fault).
 If valid ELINx is ON before ELOUT ON, the result shall be (03 – HW Error).
 If valid ELINx is never ON during ‘EmgL-T’, the result shall be (03 – HW Error).
3.3. If both ELIN1/2 are invalid

 The result shall be (02 – Fault).
16.2.4.3 BTI - Brake Torque Operation
- Objective
The objective of this feature is to inspect whether brake torque is good or not.
There are two kinds of BTI, one is Manual BTI and the other is Remote BTI. The Manual
BTI is performed by field mechanic at job site. The Remote BTI is performed by Elite expert
at remote station. The manual BTI is performed independently while the remote BTI is nor-
mally performed as part of REI Operation. To perform BTI, REI-DRV should be set to 1 or 3.
- Operation of the function
- Manual BTI (Master: Drive)

1. Upon arrival at the lowest floor, mechanic shall active ERO switch to make the car into
INS mode. With service tool key which is defined, DBSS shall transmit BTI Permit to
OCSS.
2. On receiving the BTI Permit Request, OCSS check the elevator status, and if it is true,
OCSS shall transmit the BTI Permit Ack to DBSS.
 The elevator stops at bottom floor or 1 upper floor of bottom (if bottom floor is se-
cured).
 Doors are fully closed.
3. DBSS shall start BTI.
Page: 176 / 196
Berlin
4. Finish the BTI, DBSS transmit ‘finish BTI’ to OCSS.

Note: For more details, please refer to 55661_OPMAN.doc
16.2.4.4 Remote BTI (Master: GECB)

1. Upon arrival at the lowest floor, OCSS check the elevator status, and if it is true, OCSS
shall transmit the BTI start request (150 or 190% torque) to DBSS.
 The elevator stops at bottom floor or 1 upper floor of bottom (if bottom floor is se-
cured).
 Doors are fully closed.
 There is no car call or hall call.
2. On receiving the BTI start request, DBSS shall transmit BTI permit request to OCSS.
3. On receiving the BTI permit request, OCSS transmit BTI Permit Ack to DBSS.
4. DBSS shall start BTI.
5. Finish the BTI, DBSS transmit the BTI result to OCSS.
6. On receiving the BTI result, OCSS check and logged this, and if this is OK, finish BTI
and move to next step of REI.
7. If this result is NG, OCSS move car 1 floor up and down immediately without door
opening, then try BTI start request (150 or 190% torque) to DBSS.
8. Start 2nd time BTI, same as item 2-6.
9. If this result is NG again, OCSS move car 1 floor up and down without door opening,
then try BTI start request (130% torque) to DBSS.
10. Start 3rd time BTI, same as item 2-5.
11. On receiving the BTI result, OCSS check and logged this, and if this is OK, generate
alert to NMS and finish BTI and move to next step of REI.
12. If this result is NG again, OCSS generate alarm to NMS and finish BTI and move to next
step of REI.
Note:
(1) If Hall or Car call is registered during BTI, OCSS transmit interrupt request to DBSS,
and DBSS stops BTI immediately.
(2) Then OCSS moves car to answer calls. The car shall wait for 5s with door closed after
answered call.
(3) After 5s, the car shall return to bottom floor and re-start BTI operation.
(4) If bottom floor and 1 upper floor of bottom are set as security floor, OCSS record abort
log immediately (without wait 60min timeout) and move next step.
Page: 177 / 196
Berlin
Install Parameters:
2-OCSS INSL-TYP 0-1 Inspection Lamp Type
0 INSLH light up during BTI
+1 INSLH light up during all of REI
Note: I/O 1204 INSLH

12-REI REI-DRV 0-3 Enable BTI and Drive REI Data(RDO#34191)
0 Disabled
+1 Enable BTI
+2 Drive REI data (RDO#34191) supported
Event:
Event Description
0271 BTI NG 3rd BTI result is no good at every 3rd trial.
0272 BTI OK 3rd BTI result is good at 3rd trial.
0273 BTI Fault BTI is not available or aborted.
Page: 178 / 196
Berlin
OCSS DBSS
Remote BTI Requested
BTI Permit Initialize BTI Ready
Check Elevator Status Check Drive Status
BTI Request BTI Permit Request
BTI Permit Ack. Start BTI
(150% or 190% torque request)

BTI Results
BTI Permit Finalize Finish BTI
Check BTI Results
OK
NG Finish
st
1 Inspection
Move 1 floor up and down
nd
2 Inspection
(150% or 190% torque request)
NG
Move 1 floor up and down
Page: 179 / 196
Berlin
(130% torque request)
Check BTI Results
OK
Finish Generate Alarm rd
3 Inspection
NG
Finish Generate Alarm

16.2.5 AfterLog Collection
After finished BTI, the OCSS shall collect all the measurement results and the logged data
of the REI operation. (This step is called ‘AfterLog Collection’.)
16.2.6 Return to floor REI was started

After finished AfterLog collection, the car shall return to the floor where REI was started. If
group, the car runs to the optimal floor by the zoning.
16.2.7 End of REI operation

1. The inspection result data shall be sent to NMS according to REI scheduling method
that was used.
2. Upon receiving the completion signal from controller, NMS sends request signal for REI
result to controller.
3. Upon receiving the request signal from NMS, OCSS sends REI results to NMS.
4. Upon receiving the results from controller, NMS sends end signal to OCSS.
5. Upon receiving the end signal from NMS, OCSS ends the remote inspection.
6. In addition, NMS transmits the request signal of the logging data to OCSS.
7. Upon receiving the request signal, OCSS transmits the logging data to NMS.
8. The end signal of the remote inspection, the request signal of the remote inspection
measurement result and the request signal of the logging data are independent and
when OCSS receives these request signals, it transmit data to NMS irrespective of the
remote inspection.
Page: 180 / 196
Berlin
Pre-conditions for REI:

Condition Remark
REI-TYP is 1~3 If REI-TYP=4, the OCSS performs Before-
Log collection only.
The car is not PKS shutdown at PKS-P PKS Shutdown only, OpMode PKS is OK.
Higher OpMode than REI is not active.
Service button input is not activated ServInC (1157) and ServInH (1265) are
not active
Pause-conditions for REI:

Condition Remark
OpMode is OLD or DHB
If there is any call assigned
Abort-conditions for REI:

Condition Remark
REI timeout (60 min.) is expired. -
OOS reason event occurred -
TPA alarm is generated -
Higher OpMode than REI is requested except OLD, DHB, PKS -
Service button input is activated ServInC (1157) or ServInH (1265) is active
Page: 181 / 196
Berlin
16.3 Self-Trigger REI

1. The Self-Trigger REI is commonly used in Korean market, the REI can be started by
controller itself. To use Self-Trigger REI, TRG-TYP should set to 0.
2. The user can set time on NMS screen by edit configuration.
3. After set configuration, the user shall perform ‘write configuration’ to copy these time set
to controller parameters listed below.
4. The OCSS shall start REI automatically when the Real Time Clock reaches to
designated time zone regardless of NMS connection.
5. The general REI operation sequence is the same with manual REI by NMS command.
Install-Parameters:
Group name Value description
12-REI TRGstrtH 0-23 REI trigger start hour
0 (1) 23 hours
Note: only applicable for TRG-TYP=0

TRGstrtM 0-59 REI trigger start minute
0 (1) 59 minutes

TRGstopH 0-23 REI trigger stop hour
0 (1) 23 hours

TRGstopM 0-59 REI trigger stop minute
0 (1) 59 minutes

TRG-DofM 0-31 REI trigger day of month
0 N/A
1 (1) 31 day

TRG-DofW 0-7 REI trigger day of week
0 N/A
1 SUN
2 MON
3 TUE
4 WED
5 THU
6 FRI
7 SAT

Page: 182 / 196
Berlin
TRG-WofM 0-5 REI trigger week of month

0 N/A
1 (1) 5 week
16.4 Sequential REI

TBD
16.5 REI Test by SVT

The REI Operation can be performed by SVT command. With DBG-REI=255, the REI
Operation shall be performed as the same sequence. If user wants to test some specific
step, it is possible by set DBG-REI=102~108. With this configuration, the REI shall be
performed from the step which was chosen by user. In this case, collect AfterLog step shall
be skipped due to avoid confusion about REI data collection. So the step shall be jump to
WAIT after finished BTI. To use this function properly, refer to floor condition listed below.
The BTI test is also possible by set DBG-REI=251~254.
These tests are available when the condition is OK to perform REI Operation.
Install-Parameters:
10-TEST DBG-REI 0-255 Debug REI Parameter:
95 Clear all variables
97 Display data collection
(100+x) Set REI start from step x
- 102 from RETURN_BOTTOM
- 103 from STOP_UP
- 104 from STOP_DOWN
- 105 from GOING_UP
- 106 from GOING_DOWN
- 107 from Car Light Check
- 108 from Emergency Light Check
251 BTI is NG for all steps

252 BTI is OK at step3
253 BTI is OK at step2
254 BTI Test by SVT
255 REI Test by SVT
Note: This parameter is for engineering and remote expert

102, 103, 105, 107, 108 – available at bottom floor only.
104, 106 – available at top floor only.
Page: 183 / 196
Berlin
16.6 REI Data Collection

16.6.1 REI data collection for Korean market requirement

REI data means the set of statistical data and performance data that is collected during the
REI operation mode and normal operation time because the Elite Report needs normal time
performance data as well as REI operation result data.
For Korean Elite Report, following items of performance data are collected during the
normal operation time.
1. Hourly Run Counts collection
2. LRD Count collection
3. SGS Count collection
4. Total lighting time collection
5. Data collection for REI
6. Performance data counter for number of power ons
Above items are collected as daily-based database records.
During the REI mode, following items of REI result measurements are collected;
1. The time to begin running to start (Same as Japanese requirement)
2. Elapsed time of acceleration (UP & DOWN sepatarely)
3. Elapsed time of decceleration (UP & DOWN sepatarely)
4. Errors (max value & landing) in landing level according to the direction of UP&DOWN
(Same as Japanese requirement)
5. Door open time for each floor
6. Door close time for each floor
Above data items are reported to NMS by Performance Collection feature in NMS by the
definition of RDO#34189 and RDO#34190 that are existing format for REM performance
data by adding additional fields for Elite Report. In addition, RDO#34191 and RDO#34192
were newly added to existing protocol (NMS / Gateway II / Controller Data Dictionary –
SID00052) to report REI mode data to NMS. Controller has the implementation for these
new RDO’s.
Page: 184 / 196
Berlin
RDO # 34189 - GENERIC_PERF_DATA_SUMMED

CONTROLLER
With Parameter (Day) (Current day = FF)
NMS – RO
Description
Generic RDO to read performance data:
Byte 1&2: Perf Id (1-65535); 0 indicates no perf data. Perf Id 1-19999 have two byte values, and Perf Ids >
20000 have four byte values.
Byte 3-4: Two byte value or lower two bytes of four byte value
Byte 5-6: Higher two bytes of four byte values
Controller Detail:
NMS Data Property
Item # Len NMS Id De- Name Description

fault
1 2 0 Pdata 1 – Perf ID
1 2 or 4 0 Pdata 1 – Perf Data (2 or 4 bytes)
2 4 Pdata 2
3 4 Pdata 3
4 4 Pdata 4
Variable 4 Pdata 5.. variable
RDO # 34190 - GENERIC_PERF_DATA_PER_FLOOR

CONTROLLER
With Parameters (Day, Floor Number) (Current day = FF)
NMS – RO
Description
Generic RDO to read performance data:
Byte 1&2: Perf Id (1-65535); 0 indicates no perf data.
Controller Detail:
NMS Data Property

fault
1 2 0 Pdata 1 – Perf ID
1 2 or 4 0 Pdata 1 – Perf Data (2 or 4 bytes)
2 4 Pdata 2
3 4 Pdata 3
4 4 Pdata 4
Variable 4 Pdata 5.. variable
Page: 185 / 196
Berlin
RDO # 34191 - GENERIC_REI_DATA_SHAFT

CONTROLLER
With Parameter (Day) (Current day = FF)
NMS – RO
Description
Generic RDO to read REI data:
Byte 1&2: Id (1-65535); 0 indicates no REI data. Id 1-19999 have two byte values, and Ids > 20000 have
four byte values.
Controller Detail:
NMS Data Property

fault
1 2 0 REI 1 – ID
1 2 or 4 0 REI 1 – REI Data (2 or 4 bytes)
2 4 REI 2
3 4 REI 3
4 4 REI 4
Variable 4 REI 5.. variable
RDO # 34192 - GENERIC_REI_DATA_PER_FLOOR

CONTROLLER
With Parameters (Floor Number)
NMS – RO
Description
Generic RDO to read REI data:
Byte 1&2: Id (1-65535); 0 indicates no perf data.
Controller Detail:
NMS Data Property

fault
1 2 0 REI 1 – ID
1 2 or 4 0 REI 1 – Perf Data (2 or 4 bytes)
2 4 REI 2
3 4 REI 3
4 4 REI 4
Variable 4 REI 5.. variable
Page: 186 / 196
Berlin
NMS has a user interface to configure REI mode triggering time and method. This
information is configured by modem communication via GW2. This communication is
defined as RDO#546 that is newly added to the “NMS / Gateway II / Controller Data
Dictionary” (SID00546) ACD2 controller has the feature for this communication and
configuration.
RDO # 546 - CONFIG_REI_CONTROLLER_TRIGGER

CONTROLLER
NMS - RW
Description
This RDO gives the start time (and stop time if applicable) of the REI Controller Trigger.
NMS Data Property

rem_property_group_id = ??? – on the NMS side, If posible put this into a REI group, and make it mix proper-
ties of lists, string, value. This is for user convenience of editing all in one place. If not posible or comlex, let
Joe know.
Item Len NMS Id Default Name Description
#
1 1 0 Start Trigger Type 00 = By Start Time; 01 = By Sequential opera-
tion (multicar, non-primary units on)
2 2 0 Start Trigger Time
3 2 0 Stop Trigger Time
4 1 value 0 Start Day of Month 1-31; 0 if not applicable
5 1 lists 0 Start Day of Week 1-7; 0 if not applicable (1=Sun, 2=Mon, etc…)
6 1 lists 0 Start Week Of Month 1-5; 0 if not applicable (1=first, 2=second,
3=third, 4=fourth, 5=last)
(For the “Start Trigger Type’ field, current version provides only one feature – 00=By Start
Time)
16.6.2 REI data collection for Japanese market requirement

Japanese REI data means three types of performance or REI result data; Daily performance
data (daily-based performance), Monthly performance data and REI result data. REI
operator generates REI report for customer by utilizing these types of new data fields as
well as the performance data that have been used for REM operation.
In normal time, following items of daily performance data are collected additionally to the
existing data collection;
1. One Floor Run Count
2. One Floor Run Time
3. Demand Time
Page: 187 / 196
Berlin
In normal time, following items of monthly performance data are collected additionally to the
existing data collection;
1. System errors of OCSS and MCSS
2. The number of times replied to any calls per landing
3. The number of times replied to car calls per landing
4. The number of times replied to up hall calls per landing
5. The number of times replied to down hall calls per landing
6. The number of times open the door per landing
7. The number of times re-open the door per landing
8. The number of times detected the failure of the car button
9. The number of times detected the failure of the up hall button
10. The number of times detected the failure of the down hall button
11. The number of times detected the failure of the emergency call button
12. The number of times detected DTC mode by lack of DFC
13. The number of times detected DTC mode by lack of DLC
14. The number of times detected extraordinary temperature in machine room.
15. The number of times DOB input
16. The number of times DCB input
18. The number of times SGS input
19. The number of times LRD input
20. Number of 5LS, 6LS errors
21. Maximum Door Open Time & Floor# at maximum
22. Maximum Door Close Time & Floor# at maximum
23. Minimum Door Open Time & Floor# at minimum
24. Minimum Door Close Time & Floor# at minimum
25. The input count and the maximum elapsed time of DOB from all floors
26. The input count and the maximum elapsed time of DCB from all floors
27. The input count and the maximum elapsed time of SGS from all floors
28. The input count and the maximum elapsed time of LRD from all floors
Page: 188 / 196
Berlin
During the time of REI mode, following items of REI result data are collected from GDCB;
1. Errors(max value & landing) in landing level according to the direction of UP&DOWN
2. The number of times with the start shock according to the direction of UP&DOWN
3. The number of times with the stop shock according to the direction of UP&DOWN
4. The time to begin running to the start (UP&DOWN direction)
5. The acceleration deflection (UP&DOWN direction)
6. The fixed speed deviation (UP&DOWN direction)
7. The deceleration deflection (UP&DOWN direction)
8. The condition of the car light
9. The condition of emergency light check
9. Brake Torque Inspection Result
While Daily performance data is reported to NMS by the definition of RDO#34189 and
RDO#34190 as same as Korean, Monthly performance and REI result data is reported by
the definition of RDO#505, RDO#507, RDO#544 and RDO#33274.
These RDO’s were already defined in the SID00052 for Japanese REI, and new EN-
baseline controller also has the implementation on this.
Page: 189 / 196
Berlin
RDO # 505 – REI_CONTROLLER_STATUS

CONTROLLER (JPN)
NMS – RO
Description
This is status of a REI task while running at the controller. Primary usage is to display on the NMS screen for user.
NMS Data Property

rem_property_group_id = l07001 (REI)
Item Len NMS Id Default Name Description
#
1 1 107005 ---- Controller Status 00: Normal; 01:Error Log Collection Active; 02:REI
Wait; 03:REI Running; 04:REI Results Ready:05:REI
Abort
RDO # 507 – REI_RESULTS

CONTROLLER
NMS – Read only
Description
This is the result of the REI run.
NMS Data Property

n/a – No NMS Ids. This data is stored in the “remote_elevator_inspection” table in the NMS db. Each data item is stored
as a column in the table.
Item # Len NMS Id Default Name Description

1 1 ---- ---- ---- Velocity Fluctuation Up
2 1 ---- ---- ---- Velocity Fluctuation Up (Standard)
3 1 ---- ---- ---- Velocity Fluctuation Down
4 1 ---- ---- ---- Velocity Fluctuation Down (Standard)
5 1 ---- ---- ---- Maximum Levelling Error
6 1 ---- ---- ---- Maximum Levelling Error Landing Position
7 1 ---- ---- ---- Maximum Levelling Error Direction
8 1 ---- ---- ---- Maximum Levelling Error Standard
9 1 ---- ---- ---- Door Open Time Maximum (divided by 10)
10 1 ---- ---- ---- Door Open Time Landing Position
11 1 ---- ---- ---- Door Open Time Maximum (Standard) (divided by
10)
12 1 ---- ---- ---- Door Close Time Maximum (divided by 10)
13 1 ---- ---- ---- Door Close Time Landing Position
14 1 ---- ---- ---- Door Close Time Maximum (Standard) (divided by
10)
15 1 ---- ---- ---- Judgement (0 = in-range, 1 = out of range)
16 1 ---- ---- ---- Error Log Code MSB #1
17 1 ---- ---- ---- Error Log Code LSB #1
Page: 190 / 196
Berlin

26 1 ---- ---- ---- Spare
27 1 ---- ---- ---- Spare
RDO # 544 – REI_ERRORLOG_STATUS

CONTROLLER
NMS – Read only
Description
This RDO provides status for the NMS to read during the REI/Error log processing at the controller. Items 1-3 are read
by the NMS comm server in order start/stop REI as well determine whether REI is currently running and/or has completed
successfully. The start/stop times are used primarly for NMS display purposes during REI operation.
With GW, this RDO will be expanded to provide status for Starting the REI by using trigger timing in the Controller. This
trigger is determined by ____
A value of 0 for time stamp means the operation has been reset/not started
NMS Data Property

rem_property_group_id = 107001 (REI)

1 1 107021 ---- Current Operation (As com- 00 = Idle
manded by NMS) 01 = REI Mode (‘before’ error logs, REI, ‘after’ error logs)
02 = Collect Error Logs Only.
03 = Close
04 = Close/Reset Mode (restarts REI state machine)
10 = Idle – waiting Controller Trigger
11 = REI Mode (triggered by controller)
14 = Clear data and status after successful collection
from NMS
Fe = abort
2 1 107020 ---- Curennt Process 00 = Idle (None)

01 = In Process REI run
02 = In Process collecting ‘Before’ error logs
03 = In Process collecting ‘After’ error logs
04 = Completed (success)
05 = Completed (failed)
3 1 107022 ---- Results Status 0 = Success (set when Current Operation Status = “Done”)
01 = Lost COMMV (after successfully started)
02 = Timed Out (exceeded RDO 543 time limit)
03 = Aborted by NMS
04 = Aborted by Controller
05 = Aborted due to TPA
06 = Command rejected because there is still log data to
collect.
(collect the data, and then issue the Close/Reset cmd)
07 = Command rejected, unknown command
08 = Command rejected, unit is already in idle state (re-
sponse to abort while in idling)
4 2 107006 ---- ---- Count of ‘Before’ logs 0-600 (Count divided by 100 plus 1 (if
remainder) =# of available buffers)
5 1 107023 ---- ---- REI log available flag (0=false, non-0 = true)
6 2 107011 ---- ---- Count of ‘After’ logs 0-200 (Count divided by 100 plus 1 (if
remainder) =# of available buffers)
7 8 107008 ---- ---- Date/Time ‘Before’ Error Log operation started
Page: 191 / 196
Berlin
8 8 107010 ---- ---- Date/Time ‘Before’ Error Log operation completed (only if
successful)
9 8 107017 ---- ---- Date/Time REI operation started
10 8 107019 ---- ---- Date/Time REI operation completed (only if successful)
11 8 107013 ---- ---- Date/Time ‘After’ Error Log operation started
12 8 107015 ---- ---- Date/Time ‘After’ Error Log operation completed (only if
successful)
13 8 ---- ---- ---- Date/Time this rdo was last updated (used to determine
when a failure occurred, because after the failure, this rdo
won’t be updated again until commanded by NMS
14 32 ---- ---- ---- Diagnostics buffer. ‘ff’ is end of buffer. ‘0’ is null entry.
Each non-0 entry maps to a SLNK Log_Error message as
defined in rmh-errs.h To map these numbers to those in
rmh-errs.h, add SLNK_ERROR_BASE to the number.
15 1 ---- ---- ---- Timer Active (0 == inactive, non-0 == sometime is being
timed
RDO # 33274 – REI_ERROR_LOGS

CONTROLLER
NMS – Read only
Description
These are error logs that are collected “before” and “after” the REI run. The error logs are stored in eight 900-byte
blocks (each block is 100 error logs). The first six blocks are used for the “before” logs and the last two blocks are used
by “after” logs. This corresponds to a maximum of 600 before logs and maximum of 200 after logs.
The basic definition of the nine byte error logs record is:
Byte 1 = Error Log Code - High byte (MSB = 1 indicates Last Error Log)
Byte 2 = Error Log Code - Low byte.
Byte 3 = Error log counts (1-127) **
Byte 4 = Error log landing positions **
Byte 5 = Time – minutes (0-59) **
Byte 6 = Time – hours ( 0 - 23) **
Byte 7 = Time – day (1 - 31)**
Byte 8 = Time – month ( 1 - 12)**
Byte 9 = Time – year (00 - 99)**
** The meaning of the 9 bytes changes based on the error code. For example, error codes greater than 10,000 do not
have date/time information, instead sending 2 error codes/values in single 9 bytes.
NMS Data Property

n/a – No NMS Ids. This data is stored in the “error_log” & “error_log_detail” tables in the NMS db. There is special
processing that saves error logs into different columns based on the type of data (defined by error log number ranges).

1 900 ---- ---- ---- Block 1 – Before Error logs
7 900 ---- ---- ---- Block 7 – After Error logs
8 900 ---- ---- ---- Block 8 – After Error logs
Page: 192 / 196
Berlin
17 Remote Elevator Monitoring (REM)
17.1 REM6 Setup

A REM-Group is defined as multiple controllers that share a single REM telephone line.
The multiple controllers might be a group of elevators, or multiple simplex elevators.
A REM-Simplex is defined as a simplex elevator that shares no telephone line with other
elevators.
Install-Parameters:
1 - SYSTEM
Symbol Value Purpose and Range
REM-TYP 0-5 Legacy REM-TYPs (see Reference Manual)
REM6 REM-TYPs:
6 GW2/OAD+ connected to SVT SIO via RS/CAN Converter
7 GW2/OAD+ connected to Group/Diagnostics CAN bus
8 GW2/OAD+ connected to Car CAN bus (REM-Simplex)
9 REM5+ (Diagnostics+ with Legacy RMH HW but new RMH SW)
10 OAD+ connected to Car CAN bus (REM-Group)
REM-ID 1-12 For a REM-Simplex, this is always 1. For a REM-Group, this is a unique
identifier of each controller within the REM-Group. The REM-ID must
be set to agree with the dip-switch setting of OAD SW1.
REM-SSM The type of OAD+ supported speech to be used. Only applicable to
REM6 REM-TYPs.
0 No speech
1 legacy REM speech (generic floor and door announcements)
2 SSM4-style speech (programmable via SVT MM1:1-3-7 (Setup Speech)
DIS-CAN Defines whether the Diagnostics/Group CAN bus is enabled.
0 Group CAN bus enabled (use for REM-TYPs 7, 10)

2 Group CAN bus disabled (use for REM-TYPs 6, 8, 9)
17.2 RFS Alarm

17.2.1 EQR Remain Detection

This alarm will be RFS, instead of SGDI of Gen2-JIS/LTD/PB in Japan.
1. If the time (EqrTrg-T) is elapsed since the controller returned to normal from Earthquake
Auto Recovery operation (EQR). In this case, the controller generates RFS alarm to
NMS to request maintenance by field mechanic. This RFS alarm means the job site
Page: 193 / 196
Berlin
which was performed EQR should be checked by manually to make sure the status of
safety devices which were potentially damaged during earthquake.
2. If the OpMode changed to INS by mechanic, a timer (EqrClr-T) to clear RFS status shall
be started. If the EqrClr-T is expired, the controller generates RFS clear alarm to NMS.
Install-Parameters:
14 - REMOTE
Symbol Value Purpose and Range
EqrTrg-T 0-255 Elapsed hours since temporary operation after finished EQR
0 Disabled
1 (1) 255 hours
EqrClr-T 0-255 Seconds to trigger RFS clear alarm after detecting EQR clear
0 Disabled
1 (1) 255 s
Event:
Event Description
0133 EQAR > Time No maintenance since EQAR for defined time
Note) EQR: EarthQuake automatic Recovery. (JIS: EAR)
17.2.2 RFS Event detection

1. If the selected OCSS event log number (maximum 3 numbers could be set) is detected,
then controller shall trigger RFS alarm after a period that was configured by SVT. User
can configure one, two or three event numbers.
2. Operators in the logical formula shall be one of “AND”, “OR” or “No Operator”.
2.1. If the first operator is “No Operator”, then the first operand parameter shall be ignored.
2.2. If the second operator is “No Operator”, then the second operand parameter shall be
ignored.
2.3. If the formula has mixed operators (AND and OR), then the AND operation shall be
calculated first.
3. If the result of the formula becomes TRUE, a timer to generate RFS alarm shall be
started. If the result remains TRUE until the timer expires, controller shall generate
event 0135 “Event RFS” and trigger an RFS alarm.
4. If the result of the formula becomes FALSE, a timer to generate RFS clear alarm shall
be started. If the result remains FALSE until the timer expires, controller shall trigger
RFS clear alarm.
Install-Parameters:
Page: 194 / 196
Berlin
14 - REMOTE
RfsEvU-T 0 Seconds to stay the logged status in case of err_update_xxx(ErrCode)
to wait for RFS alarm delay
0 (1) 255 s
RfsEvT-T 0 Seconds to trigger RFS alarm after detecting TRUE of the RFS event
detecting formula.
0 (1) 255 s
RfsEvC-T 0 Seconds to clear RFS alarm after detecting TRUE of the RFS event de-
tecting formula.
0 (1) 255 s
RfsEv1Gr 0 First operand for RFS event detection alarm
0 Operating System
1 OCSS
2 MCSS
3 DCSS
4 Signaling Sub System
5 Group
6 System
7 Rescue
RfsEv1Id 0 First operand for RFS event detection alarm
0-99 Event number
RfsEvOp1 0 Operator between 1st & 2nd operand.
0 default (no operation)
1 AND
2 OR
0 Operating System
1 OCSS
2 MCSS
3 DCSS
5 Group
6 System
7 Rescue
0-99 Event number
RfsEvOp2 0 Operator between 2nd & 3rd operand.
0 default (no operation)
1 AND
2 OR
0 Operating System
1 OCSS
2 MCSS
3 DCSS
5 Group
6 System
7 Rescue
0-99 Event number
Event:
Page: 195 / 196
Berlin
Event Description
0135 Event RFS Selected events by SVT (max: 3) is detected for pre-determined time.
17.3 OOS Alarm

17.3.1 EQO Mode Detection

This alarm will be OOS-EQO mode, instead of SGDI of Gen2-JIS/LTD/PB in Japan.
1. If EQO mode is detected, then controller shall trigger OOS alarm. (EqoAlarm=1)
2. If EqoClr-T is expired since EQO mode is cleared, the OOS state shall be cleared and
alarm shall be sent to NMS.
Install-Parameters:
14 - REMOTE
EqoAlarm 0 Enable EQO Alarm
0 Disabled
1 Enabled
EqoClr-T 0 Seconds to clear alarm after recovered from EQO
0 Disabled
1 (1) 255 s
Event:
Event Description
0134 OpMode EQO Earthquake is occurred.
Note) EQO: EarthQuake Operation mode.
17.3.2 EQR Inspection Fault Detection

This alarm will be OOS-EQAR_Fail, instead of OOSREM79&80(EQAR_Fail) of Gen2-
JIS/LTD/PB in Japan.
1. If the controller detects failure (like NAV, Safety failure or kind of these failures) during
the EQR inspection mode, the controller shall stop EQR inspection and into the
shutdown, then generate OOS alarm immediately.
2. Operation modes that regarded as failure are;
ARO, NAV, DTC, EPC, EPR, EPW, DBF, HAD, COR, EFS, EFO, EQO
Page: 196 / 196
Berlin
3. If the elevator returns to the normal mode (IDL, NOR) the OOS state shall be cleared
and alarm shall be sent to NMS.
Event:
Event Description
0131 EQAR Fail EQAR start was not permitted by drive for 60 sec after completion EQO gen-
eral operation.
Note) EQR: EarthQuake automatic Recovery. (JIS: EAR)
18 Parameter and RSL IO management

Introduced in GAA30782GAA
18.1 Adjusting Bad parameter

Adjusting Bad parameter is available since GAA30782GAA.
All installation parameter would be checked if the value is between min and max value
defined. If the value of parameter is less than min or higher than max, the value of
parameter on the shadow RAM would be automatically adjusted to default value defined.
Additionally the value of parameter on the E2PROM would be manually adjusted to default
value by using SVT<M-3-2>.
The purpose of this function is to avoid the unexpected feature activation by illegally set
value of parameter. For Example,when REI-TYP is defined from 0 to 4 and REI-TYP was
set to 170 by abnormal E2PROM default setting, REI operation can be abnormally executed
and impact to other function. In this case, REI-TYP was automatically set to 0(default value)
by this function.
Event:
Event Description
0043 Bad Params Some parameters are out of range
 Use M-3-2 to set the default values
To adjust to the default value, SVT command <M-3-2> can be used

Display description values
1 006 The number of parameters to be changed to 000-999
1 2 3 the default value
006 COP-OPY=011 2 COP-OPY Parameter name
Set to 000? 1=Y
4 5
3 011 Current value
4 000 Default value
5 1=Y Enter ‘1’ : store default value and show the
next bad parameter.
Press “GOON” or “GOBACK” : show the next
bad or the previous bad parameter without
storing default value.

FSD GAA30780EAN Feature and Set Up Description - 2015!05!28

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

FSD GAA30780EAN Feature and Set Up Description - 2015!05!28

Uploaded by

Copyright:

Available Formats

No.

Authorization Date D1 2015-03-25

Running on PCB GCA26800LC (GECB-EN) or higher

Software Version GAA30780EAN

Document Revision V 1.1

Date SCN Author Comment

Copyright 2015, OTIS GmbH Berlin

3.5 RGEN - Regenerative mode display .................................................................................................. 62

9.2 LOWPIT1 - Low Pit ............................................................................................................................ 131

17.3 OOS Alarm ......................................................................................................................................... 195

Date Rev Author Comment

Date Rev Author Comment

2011-05-09 G1130780EAC M. Hoinkis MRO_EB added

Date Rev Author Comment

Date Rev Author Comment

Date Rev Author Comment

2.1 ACP - Anti-Crime Protection

2.2 BLC - Better Living Circuit

2.3 ANS - Anti-Nuisance Operation

2.4 ARO - Automatic Rescue Operation

max. time what for

Rescue direction will change, if load weighing fails:

delay what happens

This direction change happens only once (controlled by drive).

2.5 ATT - Attendant Operation

2.6 Alternative Simplex Zone Parking

This function is only for simplex operation.

Note: Simplex only

PARK-7 0-255 Park Clock Position 7:

Parameter Value Input

OFF - No parking run

ON OFF Run to PARK-1

OFF OFF No parking run

2.7 CCB - Car Calls Behind

2.8 CFT - Cafeteria Position

Note: This door time is used at CFT-P if it is longer than

2.9 CGS - Buzzer control for Detecting Landing Door Opened

Group name value description

2.10 CK, CBC - Car Button Cancel

Cancel Door Dwell Time

Cancel Car Call

2.11 Compass - Destination Entry

For a simulation environment (i.e. no real passengers) add

2.12 COR Rescue operation

Group name value description

Note: When secure floor exist, prohibited to open door at the

1-SYSTEM CR-DIR 0 Correction Fast Run Preferred Direction:

5-DOOR DAR-T 15 Door Time for Automatic Release:

I/O Name Link Description

2.13 CTL,CBL - Car Calls to Terminal Landings

I/O Name Link Description

2.14 DBF - Drive / Brake Fault

DBF is performed for the following conditions:

This input is low-active

Drive Fault Contact GECB-EN, -AP:

These inputs are low-active

ETS Fault Refer to separate ETS chapters 5.1 and 5.3.

6LS-TYP Mismatch Mismatching parameters (4-DRIVE)6LS-TYP on GECB and (Contract)6LS-TYP

LowPit/APS Failure Refer to separate LowPit chapter 9.2

2.15 DHB - Door Hold Button

2.16 EQO - Earthquake Operation

If the car is traveling and EQO is requested by the corresponding input:

2.16.1 EQO-4 (PAO)