Gaa30773baf BD

No: GAA30773BAF_BD
Software Basic Data

OTIS SCN: GAA30773BAF
Version:1.0
SSI Engineering Page: 1 / 45
Berlin Service Panel Board SPBC_III
Date: 2011-Nov-29
Service Panel Board_III

Software Basic Data
Running on PCB: GAA26800KX1 (SPBC_III) or higher

Software Version: GAA 30773 BAF
Document Version : V 1.0
Date SCN Author Comment

07-Sep-2004 GAA 30773 AAA M. Hoinkis V 1.0 limited release
14-Dec-2004 GAA 30773 AAB M. Hoinkis V 1.0 limited release for pilot units
21-Jun-2005 G14 30773 AAC M. Hoinkis V 1.0 add events / LOSP display
12-Jan-2006 GAA 30773 BAA M. Hoinkis V 1.0 ARO update / ARO_Mode output
adaption
26-Apr-2006 GAA 30773 BAB M. Hoinkis no changes
12-Mar-2008 GAA 30773 BAC M. Hoinkis new events: S21, S35, S36, S60;
Event Trace added; RegenDrive adap-
tions; battery state at SVT status display
23-Oct-2008 GAA 30773 BAD M. Hoinkis Pre-charge qualification duration added
21-Jun-2010 GAA 30773 BAE M. Hoinkis event 38 added; less ARO pre conditions
29-Nov-2011 GAA 30773 BAF M. Hoinkis none Overspeed at MRO
Copyright 2011, OTIS GmbH & Co. OHG Berlin.

No part of this document may be copied or reproduced in any form or by any means without the prior written consent of OTIS.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
Table of Contents
1 Introduction ......................................................................................4
1.1 Overview / Software Versions .....................................................................4
1.2 Definitions and Abbreviations.....................................................................5
2 Service Tool......................................................................................5
2.1 Introduction ..................................................................................................5
2.2 Key Overview ................................................................................................6
3 Menu Functions of the Service Tool...............................................7
3.1 Service Tool Tree Structure ........................................................................7
3.2 Status Functions M - 1 .................................................................................8
3.2.1 Status System Display M - 1 - 1 ..............................................................8
3.2.2 Status Input Display M - 1 - 2 ................................................................10
3.2.3 Status Output Display M - 1 - 3 .............................................................11
3.3 Events Menu M - 2 .....................................................................................12
3.4 Setup Menu M - 3.......................................................................................18
3.5 Part Menu M - 5 .........................................................................................19
3.6 Test Functions M - 6 ..................................................................................20
3.6.1 Test ARO Display M - 6 - 1 ...................................................................20
3.6.2 Test Memory Display M - 6 - 9 ..............................................................21
3.7 Trace Menu M - 7 .......................................................................................22
4 Start Up Example ...........................................................................24
5 Trouble Shooting ...........................................................................25
6 PCB User Interface.........................................................................26
6.1 Alive LEDs...................................................................................................26
6.2 Speed Status Led CON_SPEED ................................................................26
6.3 TCBC Status LEDs .....................................................................................26
6.4 Master (TCBC) Button LEDs......................................................................27
6.5 Battery Status LEDs ...................................................................................27
6.6 Buttons........................................................................................................27
6.7 Service Buttons ..........................................................................................28
6.8 Door Zone Indicator ...................................................................................29
6.9 Publishing Position at CAN Bus on Request...........................................29
6.10 Car Position Indicator PI............................................................................29
6.11 Car Speed and Direction Indicator SDI.....................................................30
6.12 Overspeed...................................................................................................31
6.13 Buzzer .........................................................................................................31
7 Start Up Behavior...........................................................................32
8 I/O’s .................................................................................................32
8.1 Rescue Encoder .........................................................................................32
8.2 L1_L2_FAIL Input ......................................................................................33
8.3 L3_FAIL Input (Option at BCB (for ARO)).................................................33
8.4 CDC_ST Input (Option for ARO)................................................................33
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
8.5 Low_Bat (DeepDischarge) Input ...............................................................34

8.6 Output ‘FullCharge’....................................................................................34
8.7 BRK_SPB (BRK_CTRL_SPB) Output........................................................34
8.8 Brake (BRE_enable) output .......................................................................34
8.9 SwPower (EN_DRV_SW) Output...............................................................35
8.10 Power Supply for Relay Contacts (ST_POWER / EN_ST_Vout) .............35
8.11 ARO_MODE output.....................................................................................35
8.12 CAN..............................................................................................................36
9 Internal Functions ..........................................................................36
9.1 Shift Register chain for LED’s...................................................................36
9.2 Request For Service via CAN Bus ............................................................37
9.3 Temperatur Sensor / HTS_Fault................................................................37
9.4 Power Fail Detection / Bat-Mode...............................................................37
9.5 Main Power Status .....................................................................................38
9.6 Power mode................................................................................................38
9.7 RAM / ROM - Test .......................................................................................38
9.8 Supervisor for Drive Encoder....................................................................39
10 Automatic Rescue Operation ........................................................40
11 Manual Rescue Operation .............................................................43
11.1 MRO with drive ...........................................................................................44
11.2 MRO without drive......................................................................................45
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
1 Introduction
1.1 Overview / Software Versions

The SPBC_III is the man machine interface of
• the Traction Control Board
• all Service Tool Menus
• the Manual Rescue Operation

The SPBC controls and supervises additionally the Automatic Rescue Operation of the TCBC and
drive. The brake power supply is 48 Volt.
dependencies to other baselines:

SPBC_III MCB3x TCBC MRO with drive ARO
GAA 30773 AAx GAA 30785 AAx GAA 30781 AAx √ -
≥ GAA 30773 BAA ≥ GAA 30785 BAA ≥ GAA 30781 AAF √ √
Attention:
The MCB3x software version ≥ BAA are not allowed to use with SPBC_III software version AAx
(MRO with drive / ARO will not operate)!
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
1.2 Definitions and Abbreviations

ARO Automatic Rescue Operation
ARPB Automatic Rescue Power Board (48V -> 400V, needs transformer)
BatMode Battery Mode (power fail mode)
BCB Battery Control Board
BRB1 Brake Release Button 1 (at SPB)
BRB2 Brake Release Button 2 (key switch at E&I panel / Controller)
CAN Controller Area Network
CDC Controller Door Contact
DCB Drive Control Board
DZI Door Zone Indicator
GeN2-R Generation 2 Elevator: Residential
LOSP low overhead / shallow pit
MCBIII(-X) Motion Control Board
MRO Manuel Rescue Operation
OCB Over Current Breaker (main switch)
OPB Otis Peripheral Bus (software layers, uses CAN bus)
PCB Printed Circuit Board
PI Position Indicator
POR Power On / Reset
RFS Request For Service (via TCBC and REM5)
RSL Remote Serial Link
SCN Software Configuration Number
SDD System Data Dictionary (OPB / CAN messages definition)
SDI Speed and Direction Indicator
SoC SVT over CAN (libSoC)
SPBC Service Panel Board with CAN
SVT Service Tool
TCBC Traction Control Board with CAN
2 Service Tool
2.1 Introduction
The Service Tool is a pocket terminal that lets you control all elevator functions:
Monitoring of software states and system messages
Setup of installation parameters
Use of software tools.
The access of each function is controlled by the Menu System which allows convenient
work with the Service Tool.
The Service Tool Manual describes the Menu System and the single Service Tool func-
tions.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
2.2 Key Overview

The Menu System allows you to access the single Service Tool functions if you choose the
right path through the Tree Structure by pressing the corresponding key (number 1,2,...9).
The ">" character indicates that you can toggle between the different menus using the
GOON or GOBACK.
The CLEAR key lets you jump one step back.
If you want to jump back to one of the three Main Level of the architecture (MONITOR,
FUNCTION or SET) you can press the Main Level keys M or F .
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3 Menu Functions of the Service Tool

The following chapters describe the functions of the Service Tool.
SPB - Menu >

Status=1 Event=2
3.1 Service Tool Tree Structure

All Service Tool functions are organized under the Tree-Structure.
M F
1
Status 1: System
2: Input
3: Output
2
Events
3
Setup (read only)
5
Part
6
Test 1: ARO
9: Memory
7
Trace
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.2 Status Functions M-1

The Status Functions allows monitoring the status of the SPB and the i/o’s.
3.2.1 Status System Display M-1-1

The following keys can be used in this menu:
GOON / GOBACK to display the next / previous page of inputs
Display description values

1 MRO SPB state NOR: normal power supply
1 2 3 4 BAT: battery power supply
MRO STOP NAV >
0.0m/s HTS:25’. ARO: automatic rescue operation
5 6 MRO: manual rescue operation
2 STOP drive direction ‘nothing’: at BAT idle state
for ARO/MRO STOP: stop / shutdown command from
drive
UP: drive measures up dir. as easier dir.
or DOWN: drive measures down dir. as easier
dir.
battery states at BAT ABSENT: battery disconnected
NOR BAT DEFECT: battery fault
BAT TEMP.: battery over temperature
/BAT SIGNAL: no battery signals
Bat Charged: battery charged (full loaded)
BatCharging: battery charging
3 NAV drive state dur- NAV: Not Available
ing ARO / MRO SHD: Shut Down
POD: Power Down
INI: Init
IUA: Idle Unavailable
IDL: Idle Available
PTR: Preparing To Run
RTR: Ready To Run
RUN: Running
STP: Stopping
ATA: At Target
CAL: Calibration
WFS: Wait For Safety
DDP: DDP
*nn*: Unknown (nn: number of state)
4 > more (push only visible, if drive events happens at ARO /
GoOn) MRO;
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
5 0.0m/s rescue encoder 0 – 3.0 m/s

speed
6 HTS:25’ Hall Tempera- 0 – 70° C (if not low_bat active)
ture Sensor at
SPB
6 LOW_BAT active discret -
input

1 1.Drive hint for received 1.Drive Events (1-3)
1 2 Events: events (only first 2.Drive Events (4-6)
1.Drive Events:> 6) only visible at battery mode !!!
0001 0200 0050 . >
3 4 5
2 more push GoOn to go to first display
3 0001 first event at 0000 – 9999 (see drive documentation)
battery mode
4 0200 second event at 0000 – 9999 (see drive documentation)
battery mode
5 0050 third event at 0000 – 9999 (see drive documentation)
battery mode
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.2.2 Status Input Display M-1-2
GOON / GOBACK to display the next / previous page of inputs

1 brb1 discreet inputs brb1: button at SPB for MRO
1 2 - ... capital letter: active brb2: key switch for MRO
brb1 brb2 . 4 small letters: inactiv bat_pow: battery mode from BCB
bat_pow ocb .
3 4 ocb: main switch
rr_r: both RescueRelays (log. AND)
aro_r: ARO relay contact
cdc: controller door contact
l1l2fail: line fail signal from BCB
l3fail: line fail signal from BCB
low_bat: undervoltage of battery
button: any button at SPB
dzi: door zone indicator of SPB
enc_a: channel A of rescue encoder
enc_b: channel B of rescue encoder
bat_maint: from battery charge circuit
charge: from battery charge circuit
bat_fault: from battery charge circuit
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.2.3 Status Output Display M-1-3
GOON / GOBACK to display the next / previous page of outputs

1 rr1_r discreet outputs fcharge: to BCB, to charge with higher cur
1 2 - ... capital letter: active rent
fcharge st_power 4 small letters: inac- st_power: power supply for _ST contacts
rr1_r rr2_r .
3 4 tive rr1_r: Rescue 1 Relay
rr2_r: Rescue 2 Relay
aro_r: automatic rescue relay
aro_mode: to BCB, to activate ARO power
supply (ARO converter)
swpower: power supply for drive SW relay
brk_spb: brake controlled by SPB (active)
or by drive (inactive)
spb+: power supplay for TCBC and
drive CAN bus receiver
brake: power supply for lifting the brake
(only MRO)
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.3 Events Menu M-2

View all events which have been stored since last PowerOn.
All events are cleared when the power is switched off (battery and main power).
y:day:hh:mm POW.
0:250:02:23 ON.
View Events
GOON / GOBACK displays the next/previous event
DOWN displays additionally info to an event
Description of display:

1 0:250:02:23 time since last power on -
1 power on
y:day:hh:mm POW. 2 no events empty event logging -
0:250:02:23 ON. logged
3 02 Events Number of logged events 00 - 99
2 logged without multiple events
no Events . 4 S23 number of event see event table be-
logged . low
5 L1 L2 Fail name of event see event table be-
3 low
02 Event(s) . 6 01 event counter 01 - 255
logged . 7 0:002:13:05 elapsed time since last 0 - 9:259:23:59
occurrence of this event
4 5 (y:day:hh:mm)
S23 L1 L2 Fail .
01 0:002:13:05.
6 7 8 STOP direction from rescue STOP, UP, DOWN
encoder when the last
4 5 event was logged
S23 L1 L2 Fail . p03
STOP p03 ACTIVE.
9 position when the last p00 – p99; p**
8 9 10 event was logged
10 ACTIVE current state of the event ACTIVE, inact.
(see set and reset column
of event table)
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
Event table:
# name R set reset reason to do
F
S
S00 Task Timing • defect SPB or de- • replace SPB / FLASH
software error POR fect FLASH (soft-
ware)
• other CAN nodes • check other CAN
publishes to many nodes
messages
S01 Encoder A no signal from rescue • check rescue encoder
4 encoder 2 correct pulse / encoder track A wiring
errors POR
• replace rescue en-
coder
S02 Encoder B no signal from rescue • check rescue encoder
4 encoder 2 correct pulse / encoder track B wiring
errors POR
• replace rescue en-
coder
S03 Encoder Dir. • track A and B of • change SDI-Dir pa-
from TCBC from TCBC rescue encoder are rameter (0->1 or 1->0)
controlled run controlled run exchanged or exchange pin 4 and
and encoder with correct
pin 5 at SPB P7
or parameter encoder phase
error shift / POR • invalid phase shift • replace rescue en-
(direction between track A & B coder
failure) • rollbacks • adjust the drive to
prevent rollbacks
S04 EEPROM err defect E2PROM of SPB replace SPB
X storing error successful
storing
S05 Battery err battery cannot be check event #S16 &
X active Bat- inactive BatFault charged #S17 for more details
Fault signal signal
S07 /CAN Master no CAN communication • check power supply of
no communi- communication with master (TCBC) master
cation with with master
• check CAN_OK led at
master
master
• check CAN wiring
between master and
SPB
• check ground connec-
tion between master
and TCBC
S08 Overspeed • car has reached • check Encoder pa-
speed > 115% from TCBC overspeed (OS saf- rameter
of nominal controlled new ety contact has • reset OS contact (REB
speed run with speed <
opened) & RRB)
115%
• parameter Nom- • check parameter
Speed is to low for Nom-Speed
this unit
S09 DZI err DZI is not wired / avail- check DZI and its wiring to
(needs rescue X from TCBC from TCBC able the SPB
encoder track A to controlled run controlled run
detect) with 2 DZ with 2 DZ edges
edges and no and with DZI
DZI signal signal change
change
S10 HTS active The HTS temperature is If the environmental tem-
temperature > temperature < higher than the parame- perature was not higher,
parameter parameter-5°C ter HTS-Temp. check the HTS (sensor at
SPB)
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29

F
S
S12 3x Enc A err track A of rescue en- erase SPB event log (or
X more than 2 SVT (CAN msg. coder fails for 3 times (3 erase events at master
events of # 1 from TCBC) runs) (event stored at (with SVT at TCBC) and
(see to do) E2P) check track A and its wir-
ing)
S13 Para. Range one or more parameters check all SPB parameters
X 1 parameter all parameters in are out of range (re- at master (e.g. TCBC)
out of range range ceived from master)
S16 BAT ABSENT battery absent or over connect battery with cor-
X BatCharge is BatFault off voltage rect voltage to BCB
off AND
BatMaint is
off AND
BatFault is on
S17 BAT DEFECT • battery defect • replace battery
X BatCharge <> BatFault off • charge timeout (no • switch main switch off
BatMaint,
charging, caused by / on and check Full-
AND BatFault
is on, high traffic or defect Charge signal to BCB
FullCharge signal))
S18 BAT TEMP. • battery temperature • check battery envi-
BatFault BatFault on or out of range (0- ronment (defect fans)
flashing with 3 off 40°C)
Hz
• battery temperature • check sensor (at SPB
sensor defect / not or external)
available)
S19 /BAT SIGNALS the BCB transmitts no check connection to BCB
X BatCharge is BatCharge is on signals from the on board and / or replace BCB
off OR BatMaint charging unit
AND Bat- is on
Maint is off OR BatFault is
AND BatFault on
is off
S20 DeepDischar. battery undervoltage charge battery or replace
active Deep- inactive Deep- battery
Discharge Discharge input
input (at
battery mode)
S21 Bat Charged battery is completely for information only
BatMain is on BatMain is off charged
S22 CAN bus off no other CAN node check CAN bus wiring and
CAN_OK led CAN_OK led available at the CAN bus / or check other CAN
off blinking nodes (PCB’s)
S23 L1 L2 Fail the power lines L1 and if there was no real power
X L1_L2_Fail inactive L2 has no power fail, check connection from
active at L1_L2_Fail at SPB to BCB / BCB to
normal mode normal mode power lines and / or re-
place BCB
S24 L3 Fail the power lines L3 has if there was no real power
L3_Fail active inactive L3_Fail no power fail, check connection from
at normal at normal mode SPB to BCB / BCB to
mode power lines and / or re-
place BCB
S25 BRB1 at NOR The BRB1 input at SPB If the BRB1 button was not
X BRB1 active Bat_Mode / was operated for 30s at operated, replace SPB
at normal inactive BRB1 at normal mode.
mode normal mode
S26 BRB2 at NOR The BRB12 input at SPB If the BRB2 key switch was
X BRB2 active Bat_Mode / was operated for 30s at not operated, check key
at normal inactive BRB2 at normal mode. switch and its wiring and /
mode normal mode or replace SPB
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29

F
S
S27 OCB failure The OCB input was check wiring to OCB and
X active OCB_ST inac- active at normal mode or replace SPB
OCB_ST at tive at normal (must be inactive, if the
normal mode mode OCB is switched on)
S28 RR_ST at NOR The RR input was active • check released RR1 &
X RR_ST active Bat_Mode / at normal mode. RR2 relays
at normal inactive RR_ST
• check RR input wiring
mode at normal mode
• replace RR relays /
SPB
S29 ARO_ST atNOR The ARO input was • check released ARO
X ARO_ST Bat_Mode / active at normal mode. relay
active at inactive
• check ARO input
normal mode ARO_ST at
normal mode wiring
• replace SPB
S30 MRO w. drive MRO with drive has been for information only
MRO: running outside MRO started
with drive
S31 MRO wo drive MRO without drive has for information only
MRO: moving outside MRO been started
without drive
S32 ARO started ARO has been started for information only
if the SPB outside ARO
starts power
supply for
ARO
S33 CarMoved/Drv • MRO without drive for information only (some
car movement drive responses • brake lifted external drives need this informa-
detected this information- tion to calibrate its en-
at powered down
during pow- via CAN after coder)
ered down power on drive
drive
S34 SPBF FAILED SPB power supply inter- • check power supply
X SPB at battery normal mode or rupted (e.g. fuse at of SPB
mode and battery mode TCBC for SPBF+) • check main power
L1/L2 are with L1_L2_fail
available supply (undervolt-
age?)
S35 Nor Power main power available for information only
SPB at normal battery mode
mode
S36 Bat Power no main power available for information only
SPB at battery normal model
mode
S37 MroBrakeTout MRO without Drive: • car load at balance:
MRO without outside MRO Brake timeout; ~500ms; add weight on top of
drive: brake or no rescue encoder sig- car or use block
lifted and no at the beginning
movement of MRO run
nals during brake lifted • defect encoder: check
detected without drive rescue encoder
S38 CanRxOverrun The SPB received more disconnect the other CAN
CAN receive not necessary CAN messages than it nodes (one by one) to
queue overrun could handled identify the node, which
sends a burst of CAN
messages
S40 Mro /RR_ST The RR_relays read back check RR_ST wiring and
RR_ST miss- outside MRO contacts signal is missing RR_relay contacts;
ing at MRO RR_relay pulled during
MRO?
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29

F
S
S41 Mro/PrefDir No prefered direction • check CAN connection
missing CAN outside MRO from drive received. to drive
message at
• check, whether drive
MRO
software running
(drive started? ->
fuses at BCB)
• check drive events (#
displayed at status
display (chapter
3.2.1), perhaps drive
not ready to run)
S42 Mro/PrefDir2 The first MRO run in the check drive events (#
missing CAN outside MRO prefered direction failed displayed at status display
message at (no movement). The (chapter 3.2.1))
MRO second run (in the other
direction) was not pre-
pared by the drive.
S43 Mro/DriveIdl The drive is not ready to • check drive events (#
drive not idle outside MRO accept a run command at displayed at status
at MRO MRO (timeout ~4s). display (chapter
3.2.1))
• check fuses at BCB
S44 Mro/DrvCaliX The missing response • check drive software
necessity of outside MRO can be caused by: wrong version
drive encoder drive software version or • check drive events (#
calibration crashed drive after power
without drive displayed at status
response
on display (chapter
3.2.1))
S45 MroDrvMovTou moving in the dictated for information only
drive should outside MRO direction was impossible
start MRO run or (timeout ~3s), a new
and no at the beginning MRO run was initiated in
movement of MRO run with
detected drive
the other direction;
S46 MroBothDirTr the rescue encoder are • check rescue encoder
both directions outside MRO defect; and brake
tried at MRO the brake could not lifted; • check drive events (#
and none the drive could not run;
movement displayed at status
detected display (chapter
3.2.1))
S50 Aro CDC open controller door openend check Controller Door
CDC opened outside ARO during ARO (not at ARO Contact
during ARO test by SVT)
S51 Aro /ARO_ST The ARO_relay read check ARO_ST wiring and
ARO_ST is outside ARO back contacts signal is ARO_relay contacts;
missing at missing ARO_relay pulled during
ARO ARO?
S52 AroARO_STint ARO relay dropped check ARO relay
ARO_ST outside ARO
interrupted
during ARO
S53 Aro /RR_ST The RR_relays read back check RR_ST wiring and
RR_ST miss- outside ARO contacts signal is missing RR_relay contacts;
ing at ARO RR_relay pulled during
ARO?
S54 Aro RR_STint The RR_relays dropped. check RR relays
RR_ST inter- outside ARO
rupted during
ARO
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29

F
S
S55 Aro /OCSS OCSS software is not • check OCSS
OCSS does outside ARO running or has failure • check fuses at BCB
not response with a higher priority than
on ARO re-
• check ARPB
ARO
quest
S56 Aro OCSS rej • position problem • check DZI / PRS
OCSS re- outside ARO • EFS was active • check OCSS
jected ARO
before ARO
request
• OCSS ARO timeout • check OCSS / drive /
door operator
S57 Aro Tout The OCSS needs to long check OCSS / drive
ARO timeout outside ARO to finished ARO run
(~6min.).
S58 Aro/DrvCaliX The missing response • check drive software
necessity of outside ARO can be caused by: wrong version
drive encoder drive software version or • check drive events (#
calibration crashed drive after power
without drive displayed at status
response
on display (chapter
3.2.1))
S59 Aro /Drive drive is not powering up / • check fuses at BCB
no drive outside ARO no CAN comunication • check wiring between
response after between SPB and Drive BCB / RR relays /
operating the
RR relays to Drive
power up the
drive
S60 Aro Ended ARO has been finished for information only
if the SPB outside ARO
switches
power supply
off for ARO
Erase Events
You can either erase all events which are stored in the event log.
Erase all events

UP
Erase EVENTS ?
yes=1 no=2.
Press 1 to continue
or press any other button to cancel
Erase EVENTS ?
yes=ENTER no=2.
Press ENTER to erase all events

no Events .
logged .
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.4 Setup Menu M-3
View Installation Parameters (received from master (TCBC) ).
GOON / GOBACK go to the next/previous parameter

1 00 number of parameter see parameter table
1 2 2 En- name of parameter see parameter table
00 Encoder . coder
013 (read only). 3 013 current value of parame- -
3
ter
Parameter table:
# name min. max. default description
0 Encoder 10 30 13 mm-run / pulse of rescue en-
coder at one track
1 SDI-MAX 2 60 30 cm/s; max SDI speed
2 BRE-MAX 1 12 8 cm/s; drop speed for brake re-
lease (MRO without drive)
3 HTS-Temp 30 70 70 °C; hall temperature sensor
alarm limit
4 Nom-Speed 2 60 16 10 cm/s; nominal speed; at this
speed the led CON_SPEED will
be switched on
5 Top-Floor 1 99 2 This is the highest floor that the
SPB will display.
6 Bottom-Floor 0 98 0 This is the lowest floor that the
SPB will display.
7 SDI-Dir 0 1 0 invers the SDI direction
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.5 Part Menu M-5

Displays the Software Configuration Number (SCN) of the software.
GOON go to the next page
1 1 GAA30773AAA Software Configuration -

GAA30773AAA . Number (SCN) of Software
01-Aug-04 10:00
2 3
2 01-Aug-04 compilation date -
1
GAA30773AAA . 3 10:00 compilation time -
SPBC_III .
4 4 SPBC_III board id SPBC_III,
unknown PCB
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.6 Test Functions M-6
3.6.1 Test ARO Display M-6-1
CLEAR aborts test
Starting the Test will not be possible at battery mode:

test not avail-.
able at bat mode
Test Sequence:
ARO-TEST: start?
car empty? yes=1
Press 1 to continue
or press CLEAR to cancel test.
3 seconds at normal mode
wait f. AROrelay {ARO output will be active for 90s,
to power down . if not pressed CLEAR (for trouble
shooting})
Battery Mode: . abort: no ARO .

wait for ARO 75s relay available.
waits for ARO Press CLEAR to start again
ARO – Test .
on going . abort: ARO mode
waits for end of ARO not available.
ARO – Test . Press CLEAR to start again
finished .
2 minutes without
starting ARO
If the ARO run will be not successfully finished, please check the SPB, TCBC, drive event
log. You can access the SVT menu of the SPB, TCBC and drive during the ARO test. If the
ARO mode (at the SPB) will not be started, please check the ARO conditions (chapter 10).
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.6.2 Test Memory Display M-6-9

Engineering only: to watch memory content
GOON / GOBACK go to the next/previous address
UP / DOWN go to the next/previous memory type
ENTER start / finish address input
1 1 memory XRAM memory type XRAM, IRAM, CODE

memory XRAM .
0000 new: .
2
2 1C45: address -
1
memory XRAM . 3 10:00 content of address -
1C45: DF 7C .
2 3 4 4 SPBC_III content of address + 1 -
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
3.7 Trace Menu M-7

Views the latest 100 events in the sequence which they occur (ring buffer). The first entry is
the oldest event after last power on. The time stamp refers to power on (time = 0).
All events are cleared when the power is switched off (battery and main power).
Current Time .
d0300:23:59:59s
View Trace
GOON / GOBACK displays the next/previous event
ON jumps to oldest entry

1 Current Time time since last power on -
1 d0300:02:23:59s
Current Time . 2 no events in empty event trace -
d0300:23:59:59s Trace
3 02 Events in number of logged events 0-100
Trace
2 S23
4 event number see event table at
no Events . chapter 3.3
in Trace . 5 L1 L2 Fail event name see event table at
3 chapter 3.3
02 Event(s) .
in Trace . 6 d0002:13:05:00s elapsed time since power 0 - 9999:23:59:59
on and ocurence of this
4 5 event (d:h:m:s)
S23 L1 L2 Fail .
d0002:13:05:00s 7 -end of trace- you have seen the newest -
6
event before you pushed
7 GOON
--end of trace--
.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
Erase Trace
You can either erase all events which are stored in the trace.
Erase all Events in Trace

UP
Erase TRACE ?
yes=1 no=2.
Press 1 to continue
Erase TRACE ?
yes=ENTER no=2.
Press ENTER to erase all events

no Events .
in Trace .
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
4 Start Up Example
step to do / expected correction steps

1 switch controller on; plug in battery at BCB -
• check power supply of SPB (SPB plug
check: SPB_OK led blinking
P2.3 P2.2) from TCBC
2 • check fuse at TCBC (for SPB+)
• replace SPB
• check plug P2.4 P2.5 (CAN bus)
check: CAN_OK led blinking
• check other CAN nodes (like TCBC or
3 MCB)
• replace SPB
• check CAN_OK led at TCBC
plug SVT at SPB; push M twice to get SYSTEM
4 MENU from TCBC; select any menu; • check CAN bus wiring between TCBC
and SPB
5 check SPB event logging if not empty, see chapter 3.3
operates some normal runs and watch the SDI if necessary, see chapter 5
6 and position indicator
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
5 Trouble Shooting
start checking the symptoms from top to down of the following table:
symptom possible reason correction steps
SPB_OK led is not blinking • no power • check power supply of SPB (SPB
with 1Hz plug P2.3 P2.2) from TCBC
• check fuse at TCBC (for SPB+)
• self test failed • replace SPB

BAT_MODE led is blinking • battery mode / main switch is • check main switch
off
CON_SPEED led is blinking • overspeed (OS contact / • reset OS contact (buttons REB &
(SDI is blinking in one direc- blocked by governor RRB)
tion) • parameter ENCODER / Nom- • move car with ERO to reset block
Speed are not adjusted • check parameter setup
CAN_OK led is not blinking • no CAN bus connection • check plug P2.4 P2.5 (CAN bus)
with 1 Hz • other nodes are not alive on the • check other CAN nodes (like OCSS
CAN bus or DRIVE)
• check wiring between SPB and other
CAN nodes
• defect CAN hardware at SPB • replace SPB
SDI is blinking in both direc- • Encoder A failure • check SPB event logging
tions while stopping / running
SDI displays speed in both • Encoder B failure • check SPB event logging
directions
SDI is blinking in one direc- • Overspeed • check SPB event logging
tion
position indicator is blinking • an event happens • check SPB event logging
• TCBC transmits chars • see chapter 6.10
SPB event logging is not • see chapter 3.3 • see chapter 3.3
empty
button don’t operate able • defect button • replace SPB (if event logging is
empty, otherwise see chapter 3.3)
MRO is not possible • see chapter 11 • see chapter 11
ARO is not possible • see chapter 10 • see chapter 10
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
6 PCB User Interface
6.1 Alive LEDs

Three LEDs are used to display the functionality of the system:
name description
SPB-OK off: SPB software is not running
on: SPB software is not running
blinking: (1Hz) SPB software is properly running, selftest passed.
CAN-OK off: CAN bus is not available.
on: not defined
blinking: CAN bus is available.
BAT-MODE off: power supply by controller
on: not defined
blinking: power supply by battery (controller is off).
6.2 Speed Status Led CON_SPEED

LED description
CON_SPEED off: the speed is lower than the contract speed / nominal speed (NomSpeed) (v<85%
of NomSpeed)
on: the speed is equal to the contract speed / nominal speed (NomSpeed)
blinking: overspeed (v>115% of NomSpeed)
6.3 TCBC Status LEDs

The states of the following LEDs are defined by the TCBC and are transmitted via CAN.
These LEDs can be switched on, off or blinking:
LED description
GRP Group Mode
NOR Normal Mode
INS Inspection
ES Emergency Stop
DW Door Watch
DFC Door Fully Closed
DOL Door Open Limit
DOB Door Open Button
A description of these LEDs can be found in the TCBC documentation.

No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
The TCBC must take care that short pulses of its inputs (e.g. interuptions of DFC) are en-
larged to a minimum pulse length of 50ms so that the SPB can display these pulses.
6.4 Master (TCBC) Button LEDs

The states of the following LEDs are defined by the master and are transmitted via CAN
bus. These LEDs can be switched on, off or blinking:
LED description
CCTL Car Call to Top Landing
CCBL Car Call to Bottom Landing
CHCS Cancel Hall Calls Switch
DDO Disable Door Operation
NURF Emergency Power Test
RTB Remote Tripping Button LED
RRB Remote Resetting Button LED
A description of these LEDs can be found in the masters documentation.
6.5 Battery Status LEDs
Charge Action State Charge Maintenance Fault Replace

Battery absent or over-voltage fault Low Low High not used
Pre-charge qualification * Flash Low Low not used
Fast charging High Low Low not used
Maintenance charging Low High Low not used
Charge pending (temperature out of range) X X Flash not used
Charging fault X X High not used
* qualification phase should be active for 10s up to 2 minutes
6.6 Buttons
The SPB detects when a button is pressed and publish a message on the CAN bus.
The corresponding LED is switched when the appropriate message is received from the
TCBC.
The buttons and their appropriate LEDs have the following generic behavior:
• Button-X is pressed
• Send “Button-X pressed” message
• LED-X is turned on when the “LED-x turn on” message is received from the TCBC
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
Button Description Type

CCTL Car Call to Top Landing Push
CCBL Car Call to Bottom Landing Push
CHCS Cut Hall Call Switch Toggle
DDO Disable Door Operation Toggle
NURF Emergency Power Test Toggle
REB / Shift Remote Enabling Button Shift
REB & RTB Remote Tripping Button for car Push
REB & RRB Remote Resetting Button for car Push
RRB or RTB are only accepted if REB is pressed simultaneously.
6.7 Service Buttons

In addition to the above buttons there are some more functions which allow the user to dis-
play some information about the SPB itself. These functions will not be transmitted on the
CAN bus.
‘Service’ Button Description Type Display

REB & CCBL Displays environment temperature Push (HTS) Temperature in degrees
of the SPBC at PI; not possible at Celsius (1°C steps)
Bat_Mode
REB & CHCS Displays speed at PI; not possible at Push example:
Bat_Mode ‘1.6’ -> 1.6 m/s
REB & NURF Displays speed with unfiltered direc- Push only for engineering
tion on SDI; not possible at
Bat_Mode
REB & TEST reset (start self test); not possible at Push all LED’s on and off
Bat_Mode
REB & DDO same like pushing TEST alone (to Push see ‘TEST’
be compatible to old SPB)
TEST • Displays the first 16 event num- Push --
bers at SDI
• instead of the TEST button: use
the SVT to get the software ver-
sion and the complete event
logging!
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
6.8 Door Zone Indicator
LED description
DZ off: outside Door Zone
on: inside Door Zone
blinking: not defined
The DZ LED is activated when either the DZI signal from master is received or the battery
backed DZI sensor is active.
6.9 Publishing Position at CAN Bus on Request

The position will be published as ‘Unknown’, if event
• #S01 Encoder A is active
• #S02 Encoder B is active
• #S03 Encoder Dir. is active
• #S09 DZI err is active
6.10 Car Position Indicator PI

Two 7 segment LEDs are used to display the current car position; Bottom Floor is zero as
known from the Service Tool.
The SPB counts the position at the rising edge of DZ. It uses the SDI information to deter-
mine whether the position is counted upward or downwards.
Each time the master sends a valid position information the SPB adjusts its own position
information. This ensures that both positions will not differ.
If the Car Position Indicator is blinking, a failure has occurred (see event SPB SVT logging,
chapter 3.3 ). The position indicator will not be blinking in case of BatMode and only event #
7, 22,23,24,30,31,32 happens. This will happen, if the power supply would be lost.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
If you have a LOSP configuration (low overhead or/and shallow pit), it could be possible to
have blinking the following chars at the position indicator (not displayed at battery mode):
chars meaning
Ed LOSP (down dir.) event happens (see TCBC event log)
Eu LOSP (up dir.) event happens (see TCBC event log)
Sd SOS contact are activated in down direction (safety gear tripped)
Su SOS contact are activated in up direction (safety gear tripped)
The chars are transmitted via CAN from the TCBC. The TCBC decides when these chars
have to be transmitted.
6.11 Car Speed and Direction Indicator SDI

The current car speed, direction and the door zone indicator (DZI) are displayed at the SPB
in normal mode and in battery mode (i.e. the de-energized elevator is moved by lifting the
brake). The display consists of 8 green LEDs for upwards direction and 8 red LEDs for
downwards direction.
The SPB calculates the speed and direction information from two 90° phase shifted signals
provided by two rescue encoder tracks integrated in the machine. The parameter ‘EN-
CODER’ represents the distance of a moving car between two pulses of encoder A. The
SPB can calculate the speed as a result of the distance divided by the time between two
pulses.
All SPB configuration parameters are stored on the master. At each SPB-startup they are
copied to the SPB and stored in an E2PROM on the SPB if they have changed. The SPB
configuration parameters can be changed on site using the SVT in the configuration pa-
rameter setup menu for the master (TCBC).
The scaling of the car speed LEDs is adjustable by the parameter SDI-Max:
LED Car speed

0 > 0 m/s
1
2
3
4
5
6
7 = SDI-MAX
If the car speed exceeds SDI-Max (typically 0.3 m/s) then the appropriate SDI-LEDs are
blinking.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
Encoder-track A is responsible for the speed measurement. Encoder-track B is used for

detection of moving direction.
If the car starts with roll backs (no loadweighing…), perhaps the SDI will display the wrong
direction for this run. The SDI direction will be locked, if the rescue encoder provides the
same direction for 120ms (debounced 3 times (each 40ms)).
6.12 Overspeed
Overspeed is detected, if the car speed will be greater than 115% of nominal speed. The
nominal speed is a parameter (see chapter 3.4). If overspeed will be detected, the
CON_SPEED LED is blinking (chapter 6.2) and the SDI is blinking in the direction of the
last run. Overspeed will not be latched during MRO.
Overspeed will be latched until one of these events happens:
• The master (e.g. TCBC) operates a new run with normal speed or lower (ERO or normal
run).
• The buttons REB & RRB are pushed to reset the OS contact.
• The SPB are switched off and on (or reset).
6.13 Buzzer
The buzzer is used for rescue purposes where the mechanic lifts the brake by operating the
brake release button / key switch (BRB1 and BRB2). During these movements a maximum
speed of SDI-Max must not be exceeded. The buzzer will sound as soon as the speed is
faster than parameter SDI_MAX+0.1 m/s.
The buzzer will also sound when the car reaches a door zone (DZI is used).
It must be ensured that the buzzer does not sound during Normal or Inspection runs. There-
fore the buzzer is only enabled at battery mode of the SPB.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
7 Start Up Behavior
The SPB starts as follows:
Visible Behavior Internal Behavior

• Turn on all LEDs (including PI and SDI) and
buzzer for 1 second (self test).
• Read configuration parameters from E2Prom.
Use default values if the parameters are invalid.
• initialize of SDI and PI
• Master sends parameters and floor information to
SPB
The PI will display ‘- -‘ until a valid position has been received from master.
8 I/O’s
8.1 Rescue Encoder
car full load (kg) 320 – 630 1000

machine typ Yaskawa 1.5T Kollmorgen 2.5T
sheave diameter (mm) 77,5 100
belt diameter (mm) 3 3
effective diameter (mm) 80,5 103
Impulse / round for one channel (ppr) 9 12
suspension 'X : 1' 2 2
circumference (mm) 252,9 323,6
car travel per pulse (mm) 14 13
The rescue encoder has 2 channels (A & B, 90° phase shift). Only channel A will be used
for car travel / speed detection.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
Software limits for Rescue encoder:

Duty cycle (output symmetry): 50% +- 11%(of 360°) means:
Minimum = 39% duty cycle (ton=140°)
Nominal = 50% duty cycle (ton=180°)
Maximum = 61% duty cycle (ton=220°)
maximum number of pulse per channel (at overspeed): 230 Hz
8.2 L1_L2_FAIL Input

L1_L2_Fail are ignored at ARO mode.
The input L1_L2_Fail must be inactive at normal mode. If not, the event ‘L1_L2_Fail at
Normal Mode’ will be logged.
8.3 L3_FAIL Input (Option at BCB (for ARO))

L3_Fail are ignored at ARO mode.
Every L3_Fail at normal mode will be logged.
8.4 CDC_ST Input (Option for ARO)

This input (Controller Door Contact) will be checked at battery and normal mode. If the CDC
was open ARO will be disabled. This will be reset after the following sequence (one behind
the other):
1. normal mode
2. CDC is closed
3. 3 normal runs (nominal speed is measured)
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
8.5 Low_Bat (DeepDischarge) Input

The board has a hardware hysterese for the signal DeepDischarge of battery. This Input is
low active and is debounced by software for 45ms.
In case of ‘active’, the event DeepDischarge (debounced 15s) must be logged and ARO
and MRO with drive will be aborted or disabled.
Only MRO with speed controlled brake lift (without drive) is allowed during an active Deep-
Discharge event.
8.6 Output ‘FullCharge’

The output will be active, if the SPB detects a dropped brake. This will be done by the CAN
msgs. SpbFloorInfo from the TCBC and by using the rescue encoder.
The output must be inactive, if the SPB is at BatMode.
Background: The transformer is not be able to support battery charging and brake lifting at
the same time.
8.7 BRK_SPB (BRK_CTRL_SPB) Output

This SPB internal output switches the power supply for the brake between:
ACTIVE brake controlled by SPB for MRO without drive
inactive brake controlled by Drive for ARO / MRO with drive
The resting state is ‘inactive’, because at normal mode the voltage peaks of the brake will
be blocked by a transistor at the DCB.
8.8 Brake (BRE_enable) output

In case of MRO with drive, the Brake (BRE_enable) signal must be additionally active to
supply power to the brake (controlled by drive).
In case of MRO without drive, the Brake (BRE_enable) signal operates as a brake control
signal.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
8.9 SwPower (EN_DRV_SW) Output

SwPower is the power supply for the drive SW relay. This output is used for MRO with drive
(not at ARO). It is inactive at the moment of the DrvRunCmd msg (drive checks the inactive
SW relay before it starts). After 300ms the output will be active to enable brake lifting by the
drive.
8.10 Power Supply for Relay Contacts (ST_POWER / EN_ST_Vout)

The output EN_ST_Vout enables the power supply (ST_Vout) for the relay contacts
RR_ST, CDC_ST,_OCB_ST, BRB2_ST, L1_L2_Fail, L3_Fail.
The output EN_ST_Vout is permanent active during ARO and MRO mode. In all other
modes (Battery Mode without ARO/MRO or Normal Mode) this output is active every 2 sec-
onds for 200ms. During these 200ms all ST inputs will be read and debounced.
8.11 ARO_MODE output

The output ARO_MODE (SPB P13.6) activates the ARO converter. The chain is:
- SPB P13.6 ARO_MODE connected to BCB P3.6 EN_ARO_CONV
- the BCB ands (&) this signal with P3.5 EN_CONV (hardware signal from SPB)
- output of combined signal: ARO_CONV_ON
- BCB P6.5 ARO_CONV_ON connected to ARPB P1.5 ARO_CONV_ON
The ARO_Mode signal is coded:

The pre series ARO converter needs more information than ‘On’ and ‘Off’. Because an ac-
tive brake coil stresses the converter much more than an inactive brake coil, the converter
needs the 3 commands from the SPB: off, half power, full power.
If the brake will be lifted, the converter must switch into ‘full power’ mode until the brake will
be dropped. The SPB uses the CAN message ‘BrakeState’ (published by the drive on state
change) to produce the converter command.
If the CAN message ‘BrakeState (dropped)’ will be lost and the converter is at ‘full power’
mode, the SPB switches the converter back to the ‘half power’ mode. This will be done by
supervising the rescue encoder signals.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
command to converter ARO_CONV signal

OFF LOW
HALF_POWER HIGH
FULL_POWER 15ms LOW / 60ms HIGH
SPB transmitted speed command to converter

mode brake state
not ARO - - OFF
ARO dropped 0 HALF_POWER
ARO lifted >0 FULL_POWER
ARO lifted 0, for more than 5s HALF_POWER
8.12 CAN
The receive queue has a size of 80 messages.
The SPBC_III can handle a continuous message stream of one message every 6.8ms. This
corresponds to a CAN bus load of 19% (bus baudrate = 125kBit/s), if all messages on the
bus are for the SPBC_III. An overload at the CAN port leads into a reset of the SPBC_III.
9 Internal Functions
9.1 Shift Register chain for LED’s

Seven shift registers are connected to one large shift register (SR) to operate up to 48 out-
puts by two µC outputs (SR_CLK, SR_Data). The take over bit is the first bit (value ’1’),
which is shifted in to the SR (connected to all shift registers). The update cycle of the SR is
250ms.
50 bits (including take over bit) must be shifted into the SR during one update cycle, but the
software shifts 56 bits (7bytes) where the first 6 bits of the first byte are ‘0’ (ineffective). A bit
(SR_Data) will be shifted into the SR with a falling edge of SR_CLK. After POR a synchro-
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
nization is done by shifting 56 bits with the value ‘0’ to delete any ‘1’, which could be misun-
derstood as take over bit.
The SR_CLK and SR_Data timing depends on the µC speed (µC clock). The SPB is
clocked by 16MHz which leads to the following times:
SR_CLK: 375ns high, 750ns low
SR_Data: set, before a falling edge of SR_CLK happens
Every 8 bits (SR_Data) happens a delay of around 8µs (needed for a function call). During
this delay the SR_CLK stays at ‘0’.
9.2 Request For Service via CAN Bus
A request for service will be triggered by some events (see chapter: 3.3).
A ‘RequestForService’ message will be published via CAN (60s delay). Then a REM alert
(RFS) can be triggered by master (e.g. TCBC).
9.3 Temperatur Sensor / HTS_Fault

Every 1.1 seconds the environment temperature of the SPB is measured from 0° to 70°
Celsius. Higher temperatures are displayed as 70° and lower temperature are displayed as
0°. The displayed solution is 1° Celsius. If the measured temperature will be higher than the
parameter HTS-Temp, the HTS event is published via CAN bus. The event will be reset by
a temperature hysteresis of 5°C.
9.4 Power Fail Detection / Bat-Mode

A power fail will be detected by supervising the SPB+_F from the TCBC. SPB+_F is linked
to the software input “BatModeInp”.
The “BatModeInp” input is debounced for 1 second.
If the SPB activates the power supply for the TCBC (output RESCUE_SPB+) at MRO, the
SPB will activate the output REQ_BAT_MODE before (40ms), because otherwise the
Bat_Mode signal to the BCB will be interrupted and SPB will be powered down. In case of
deactivating of RESCUE_SPB+, the output REQ_BAT_MODE will be still active for 1s or
more (measured: 65ms 24V -> 20V) to discharge capacitor at the TCBC.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
If the L1/L2/L3 fail will be detected at Bat-Mode, a countdown counts from 75 to 0. This time
(75s) must be waited before ARO or MRO can be operated, because the drive needs this
time to power down from 600V down to 48V. If the drive supports a lower shutdown time
between main and battery power (used CAN message: DriveInformation), the countdown
start number can be lower or zero.
9.5 Main Power Status

The inputs L1/L2L3_Fail are used to generate the CAN msg. BmsMainPowerStatus. The
msg will be published on request (BmsRequest) :
• immediately at ARO / MRO (40ms delay)
• after 840ms at all other modes: normal, battery (not ARO / MRO)
This is caused by a debouncing delay. At ARO / MRO the debouncing delay is already
passed.
9.6 Power mode

If the SPB powers up the system at ARO / MRO by battery, the message BmsPower-
Mode(battery) will be published on request. In all other case the SPB publishes BmsPow-
erMode(mainPower) if it will be requested.
9.7 RAM / ROM - Test

The functionality of the RAM is verified by testing all available memory locations.
The checksum for the ROM test is stored at the end of the ROM.
During the initializations phase the RAM/ROM test is done.
If the RAM or ROM test fails, the brake will be closed and the SPB will stay in an endless
loop. So the watchdog will not be triggered. That will provoke a hardware reset and a new
self test will perform. In this case you must change the ROM.
Additionally the ROM test will be executed in the background during normal mode (end-
less). The scanning of the complete ROM needs 20h.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
9.8 Supervisor for Drive Encoder
The drive encoder can loose its position (relation: encoder to sheave) by a movement dur-
ing a powered down drive. For that case (stored at E2PROM) the SPB has to send the
CAN message SpbCarMovementDuringDrivePowerDown (message oriented) after receiv-
ing the next drive state ‘INI’. This will be repeated until the CAN message SpbCarMove-
mentDuringDrivePowerDownAck will be received (node oriented).
The following table shows when the ‘encoder position lost’ will be detected and published to
the drive:
drive POR after SPB state: drive encoder position drive encoder position
known by drive unknown by drive
NOR - - 1)
BAT - - 1)
BAT & CAN off & outside movement √ √
MRO with drive - - 1)
MRO without drive √ √
aborted MRO with drive (OCB, DeepDis- √ √
charge)
aborted MRO without drive (OCB) √ √
ARO - - 1)
1) must be covered by drive

No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
10 Automatic Rescue Operation

The SPB starts and supervises ARO. The rescue run is controlled by the TCBC and drive.
In case of a power fail of all 3 phases for longer than 75 seconds ARO will be started by the
SPB (for single phase failure see table). During the countdown of 75 seconds, the RR2 re-
lay is active to power down the DC-Link of the drive in any case (single phase failure). ARO
will be done only once (remembered until L1_L2_Fail & L3_Fail is inactive at normal mode).
An L1 and / or L2 failure will be detected by supervising the BCB power supply from the
main transformer.
An L3 failure will be detected by supervising L3 / N. If the L3_Fail input is active and not the
L1_L2_Fail input, the CDC input is active (controller door closed) and no battery fault (#16 /
#17) is logged at normal mode, the ARO_Relay output will be operated for 90 seconds to
switch off the complete system to provoke the battery mode at the SPB, to start the count-
down and ARO.
L1_L2_Fail and L3_Fail (500ms debounced) are powered by ST_POWER. That means that
the inputs can be evaluated for 200ms every 1800ms. The state of these Inputs are not
changed during the inactive phase (1800ms) Consequence: To be sure to detect a line fail,
the power drop must be for 2000ms. But it could be detected by power drops from 200ms.
Exception: If the SPB switched into battery mode by L1/L2 failure, the output ST_POWER
will be permanent active for 1s and failure can be detected within 900ms. The SPB oper-
ates in battery mode, if the voltage becomes lower than 68% between L1 and L2.
There are 3 types of trigger conditions:

• power fail (see table below) -> line fail test / if necessary ARO
• Drive is at shutdown for 40s (or shutdown is coming back once during the next 40s after
a shutdown) and car is not moving and outside door zone -> ARO
• SPB at battery mode -> pull RR2 for 1s once to cut off filter and drive to check the main
power lines / if necessary ARO
After ARO: In all 3 case the system must operate one normal run at main power to enable a
new ARO run.
If the drive supports a lower shutdown time between main and battery power (used CAN
message: DriveInformation), the countdown start number can be lower than 75 or zero.
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
ARO voltage level trigger overview:

L1 to L2 (%) L3 to N detected detected SPB at if line state changed back
(%) after by SPB battery to normal level during
input mode countdown
100-71 100-35
71-68 100-35 √
100-68 34-0 8s L3_Fail ARO performed
67-35 100-35 √
√ countdown aborted, no ARO
67-35 34-0 900ms L3_Fail performed
34-0 100-35 900ms L1L2_Fail performed
34-0 34-0 900ms L1L2_Fail performed
Sequence at SPB:
pull ARO relay, read active ARO_R input, activate BCB converter (400Vac) and pull RR1/2
relays, TCBC (and Drive) powered up and confirms ARO to the SPB, SPB reads active
RR_R input, TCBC operates ARO run, SPB supervises ARO (timeout 6 minutes)
ARO will be aborted, if the OCB is switched off or the controller door is opened or the
LOW_BAT signal is activated.
If ARO is finished or aborted, the SPB will dropped the RR1 relay and with a delay of 1
seconds the RR2 relay.
If the drive refuses operating at battery mode, you can check the first drive events at the
SPB SVT Status display (see chapter 3.2.1).
conditions for ARO:

condition signal
SPB is in battery mode no power supply from TCBC
(SPB_F+)
The SPB is for more than 75 s at battery mode (to discharge the drive countdown at position indicator is
DC Link) running off
L1 and L2 powered down active L1_L2_Fail input
OCB is still on (not switched off during first 75s) inactive OCB input
BRB2 is not operated inactive BRB2
controller door is closed (exception ARO test) active CDC input
controller door was not open since last normal mode (3 normal runs with CDC input was not inactive
CON-SPEED are necessary since last open door) (exception ARO test)
no SPB power supply problem (SPBF) no event # 34
ARO was not done before (moved at least once at normal mode after -
last ARO)
Position is known by SPB (to provide it to Drive and OCSS during ARO) -
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
additional conditions for ARO until GAA30773BAD:

condition signal
no E2PROM failure no event # 04
no overspeed happened no event # 08
rescue encoder track A is operating no event # 12
all parameters in range no event # 13
ARO timing table

time (s) event / state if main power
coming back
0 power fail switch to NOR
1 SPB at battery mode / RR_2 relay activated / countdown from switch to NOR
75 -> 0 (or less)
76 ARO relay activated stay at ARO
76.5 ARO converter activated / RR_1 relay activated stay at ARO
80 TCBC active / Drive active stay at ARO
83 car starts run (up to 4 min. until DZ will be reached and door will stay at ARO
be opened for DAR-T)
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
11 Manual Rescue Operation

Switching off the OCB (main switch), waiting 75s and operating BRB1 and BRB2 starts
MRO. At first the SPB tries to power up the TCBC (by SPB+) and the drive (by RR1/2 re-
lays). The TCBC is necessary to provide the power supply for the drive CAN driver. If the
drive is not able to move the car, the drive and TCBC will be powered down and the MRO
will be finished with out drive support.
The position indicator rotates its segments until the run is started during the power up
phase of the drive / TCBC.
If the RR_R input will not be active after pulling both RR1/2 relays (timeout 1s)
or the LOW_BAT input will be active
or the drive does not responds (timeout 6s),
MRO with out drive is started.
MRO will be aborted, if the OCB is switched on or if the L1_L2_Fail signal is inactive or if
the MRO run needs more than 5 minutes. Then the RR1 relay will be dropped. After 1 sec-
onds the RR2 relay will be dropped.
If the drive was not able to move the car, you can abort this try by waiting for 25 seconds or
operate the OCB (on/off) to get a new try of MRO with drive.
If the BRB1 button or BRB2 key switch was released, the run will be stopped. Then after 5
seconds the RR1 relay will be dropped. Then after 20 seconds MRO will be aborted. Then
after 1 seconds RR2 will be dropped.
A MRO run will be aborted and the Buzzer will be sounds (BRB must be released and op-
erated again for a new run), if the next DZ is reached or the run takes longer than 2 min-
utes.
A new MRO run will be always started with operating BRB1 and BRB2 simultaneously.
The SDI must be always watched by the operator and in case of overspeed and / or active
BUZZER, BRB1 and BRB2 must be released.
If the drive cannot move (both directions tried), the SPB will switched into ‘MRO without
drive’ after releasing and operating BRB1/2 again.
If the drive supports a lower shutdown time between main and battery power (used CAN
message: DriveInformation), the countdown start number can be lower than 75 or zero.
hints for trouble shooting:

If the brake is not connected to HL1 on one side, the brake will not be lifted at MRO and the
drive will be switched off. If an error pulls a high current at battery mode (the battery voltage
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
goes down), MRO will not be possible because the voltage is to low to read the ST (relays,
cdc, ocb...) contacts.
conditions for MRO:

condition signal MRO with MRO with-
drive out drive
SPB is in battery mode no power supply from X X
TCBC (SPB_F+)
The SPB is for more than 75 s at battery mode countdown at position X X
(to discharge the drive DC Link) indicator is running off
L1 and L2 powerded down active L1_L2_Fail input X X
OCB is switched off active OCB input X X
controller door is open inactive CDC input X X
both RR relays are dropped inactive RR_R input X not nec.
no E2PROM failure no event # 04 X X
no Overspeed happens no event # 08 X X
rescue encoder track A is operating no event # 12 X X
all parameters in range no event # 13 X X
no deep discharge of battery no event # 20 X not nec.
no OCB failure no event # 27 X X
no RR failure at line power mode no event # 28 X X
BRB1 & BRB2 are operated active BRB1 & BRB2 X X
input
11.1 MRO with drive

The drive transmits the regenerative (easy) direction to the SPB. If the SPB does not re-
ceive this direction, no direction will be displayed at SVT (see chapter 3.2.1). If the SPB
receives a shutdown/unavailable from drive, a ‘STOP’ will be displayed at SVT status dis-
play.
If the drive cannot move the car in the regenerative direction within 3s (up to 15s / depends
on drive) after run command (detected by rescue encoder track A), the SPB requests the
drive for a new ‘easy’ direction. If the second try fails too, the SPB will be switching to MRO
without drive.
The SPB will publish a stop command to the drive and dropped the brake, if the car moves
faster than 0.3 m/s. After stopping a new rescue run command will be published.
If the drive refuses operating at battery mode, you can check the first drive events at the
SPB SVT Status display (see chapter 3.2.1).
No: GAA30773BAF_BD
Software Basic Data
Version:1.0
Date: 2011-Nov-29
The drive needs 2-3 seconds to change the direction (if necessary). During this time the
BRB1/2 has not to be released.
11.2 MRO without drive

The car can accelerate only by the earth acceleration. The SPB lifts the brake and waits for
car movement.
The SPB will drop the brake, if the car moves faster than parameter BRE-MAX. After stop-
ping the brake will be lifted again.
If the car does not move within 500ms after lifting the brake, the brake will be closed to pre-
vent an uncontrolled movement with a defect rescue encoder track A. Then BRB1/2 must
be released and operated again.

Gaa30773baf BD

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Gaa30773baf BD

Hochgeladen von

Copyright:

Verfügbare Formate

No: GAA30773BAF_BD

Software Basic Data

Service Panel Board_III

Running on PCB: GAA26800KX1 (SPBC_III) or higher

Document Version : V 1.0

Date SCN Author Comment

Copyright 2011, OTIS GmbH & Co. OHG Berlin.

8.5 Low_Bat (DeepDischarge) Input ...............................................................34

1.1 Overview / Software Versions

• the Traction Control Board

• all Service Tool Menus

• the Manual Rescue Operation

dependencies to other baselines:

1.2 Definitions and Abbreviations

2.2 Key Overview

The CLEAR key lets you jump one step back.

3 Menu Functions of the Service Tool

SPB - Menu >

3.1 Service Tool Tree Structure

3.2 Status Functions M-1

3.2.1 Status System Display M-1-1

GOON / GOBACK to display the next / previous page of inputs

Display description values

5 0.0m/s rescue encoder 0 – 3.0 m/s

Display description values

3.2.2 Status Input Display M-1-2

The following keys can be used in this menu:

GOON / GOBACK to display the next / previous page of inputs

Display description values

3.2.3 Status Output Display M-1-3

The following keys can be used in this menu:

GOON / GOBACK to display the next / previous page of outputs

Display description values

3.3 Events Menu M-2

GOON / GOBACK displays the next/previous event

DOWN displays additionally info to an event

Display description values

# name R set reset reason to do

# name R set reset reason to do

# name R set reset reason to do

# name R set reset reason to do

The following keys can be used in this menu:

Erase all events

Press ENTER to erase all events

3.4 Setup Menu M-3

View Installation Parameters (received from master (TCBC) ).

The following keys can be used in this menu:

GOON / GOBACK go to the next/previous parameter

Display description values

3.5 Part Menu M-5

The following keys can be used in this menu:

GOON go to the next page

Display description values

1 1 GAA30773AAA Software Configuration -

3.6 Test Functions M-6

3.6.1 Test ARO Display M-6-1

CLEAR aborts test

Starting the Test will not be possible at battery mode:

Battery Mode: . abort: no ARO .

3.6.2 Test Memory Display M-6-9

GOON / GOBACK go to the next/previous address

UP / DOWN go to the next/previous memory type

ENTER start / finish address input