Académique Documents
Professionnel Documents
Culture Documents
Unpublished Work - Otis Elevator Company. Any unauthorized reproduction, disclosure, or distribution of copies or content by any person of any portion of this work may be a violation of
Copyright Law of the United States of America. All rights reserved.
April 6, 1992
This work and the information it contains (collectively referred to as Work) are the confidential property of the
Otis Elevator Company (Otis). This Work is delivered on the express condition that: it will be used or reproduced
by Otis employees exclusively for, or on behalf of, Otis; it will not be disclosed, reproduced, or distributed by or to
others, in whole or in part, without the prior written consent of Otis: and, it and any copies will be promptly
returned to Otis upon demand or upon termination of employment.
REQUIRED READING:
X
Field Operations Manager
X
Maintenance Supervisor
X
Service Supt.
X
Construction Supt.
X
Modernization Supt.
X
Field Engineer
E311, E311M, E411, E411M
SYSTEM:
MCSS
COMPONENT/SUB-SYS:
Troubleshooting
SUB-ASSY/PARTS:
AUTHOR:
Paul C. Hoppie
--Description:
This manual is written to assist the Adjuster an examiner in understanding and trouble-shooting the Elevonic
Modular Control System (MCS) Motion Command Sub System (MCSS). This document is based on the use of
the following hardware and software.
MCSS-A MICROPROCESSOR BOARD
AAA26800ABA001
AAA26800ABB001
MCSS SOFTWARE
AAA30045AAE
The software and hardware provides Event Counting, Event Logging, and Light Emitting Diode (LED) indications,
in binary form, of the events and faults. The Event Counter and Event Log are accessed through use of the Otis
Modular Control System (MCS) Service Tool (P/N MT-120059).
Event Counter
Event Log
Led Indicators
Page 1 of 30
Page 2 of 30
Event Counter
The Event Counter data obtained through the use of the Service Tool is divided into 4 categories.
1. COMM RS422 communication events which occur between the MCSS and the other sub systems.
2. SFTY Safety related events which are monitored by the MCSS.
3. DBSS Events directly related to the operation of the Drive and Brake Sub System (DBSS).
4. MOTN Motion related events which are monitored by the MCSS.
Event Log
The Event Log provides a 1 frame, 40 millisecond, snapshot of MCSS data at the time an event is logged. The
event Log will retain the 25 most recent events but only the five latest events will have the data snapshots
attached.
Led Indicators
The faults indicated in the Service Tool Event Counter are also indicated by the red Light Emitting Diode (LED)
group located at the bottom edge of the MCSS-A microprocessor board. The error reporting via these LEDs is
limited from the standpoint that only the first Safety Event detected during a run will illuminate the LEDs. The
binary combination of the FC01 through FC32 LEDs indicates the event trapped. For example, HEARTBEAT in
the Event Log shows as SFTY11 in the Event Counter and would be indicated by the following:
FC01
on
FC02
on
FC04
off
FC08
on
FC16
off
FC32
0ff
The LEDs remain illuminated until the Motion Logic State (MLS) reaches PREP_TO_RUN (MLS 3), while the
Motion Command Mode (MCM) is not in RECOVER or RELEVEL (MCM 5 or 6).
Page 3 of 30
Highest
Lowest
30 VOLTS
ACCESS ZONE
RECOVERS FAIL
SFTY CHN
HEARTBEAT
SPD RLYS
SENSORS
UX, DX RLYS
DRV TRCTN LOS
VEL TRKNG ERR
DIR TST FAULT
NTSD TBL
NTSD OVERSPD
NTSD MALFUNC
LINE OVERSPED
DOOR OPEN
BYPASS DROP
DOOR ZONE BYP
E STOP SWITCH
DRIVE FAULTS
EEPROM JUMPER
DBSS FAULTS
BAD BRK STATE
BAD RTR STATE
BAD DBD STATE
BRAKE TIMEOUT
GSMON TIMEOUT
POSINIT FAULT
Page 4 of 30
Page 5 of 30
Page 6 of 30
Page 7 of 30
Page 8 of 30
Page 9 of 30
1. Access the Service Tool function, MCSS, MONITOR, DISCRETE INPUTS, (M, 2, 1, 2) DZ and/or ADZ. The
symbols should toggle between upper case and lower case letters as the relay is pushed in or dropped out.
See MCSS Service Tool document TIP 31.4-1 for further information. If this test is successful go directly to
step 5.
2. Use a volt meter to check for 30 VDC at relay contacts DZ-33 and ADZ-33. See Straight Line diagram.
3. Use a volt meter to check for 30 VDC at MCSS-B plug P5-2 when the DZ relay is pushed in. See Straight
Line diagram.
4. Use a volt meter to check for 30 VDC at MCSS-B plug P4-3 when the ADZ relay is pushed in. See Straight
Line diagram.
5. Access the Service Tool Function, MCSS, TEST, OUTPUTS, (M, 2, 1, 2) DZ and / or ADZ. The selected relay
should pick when the display is in upper case letters and drop when in lower case letters. See MCSS Service
Tool document TIP 31.4-1 and Straight Line Diagram.
Note: This check is disabled whenever the MCSS is in a MANUAL (ACCESS, INSPECTION) or Initialization
(INIT) MODE.
SFTY02-LINE OVERSPD -LINE OVERSPEED
Event Counter label - SFTY02
Event Log label - LINE OVERSPD
Fault Code LED lit 2 (binary 2)
The CAR SPEED sent from the SPPT PRIMARY channel was determined by the MCSS to be in excess of 110
percent of contract speed.
1. Access the Service Tool Function, MCSS, DATA CAPTURE, DISPLAY VARIABLES, (M, 2, 5, 1) to monitor
the PRIMARY CAR VELOCITY and the DICTATED VELOCITY during a normal full speed run. Neither
parameter should exceed the CONTRACT VELOCITY as set in the CONTRACT/CODE section of the SET
UP procedure. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
2. If the PRIMARY CAR VELOCITY is greater than the contract velocity check the value of SPPT POS SCALER
and SPPT VEL SCALER with the POSITION/VELOCITY section of the MCSS, SET UP procedure.
SPPT POS SCALER must equal 394, and SPPT VEL SCALER must equal 67295. Values are for a 1524 mm
circumference ( 20 inch diameter ) SPPT drive sheave. See MCSS Service Tool Users Manual TIP 31.4-1 for
further information.
3. Access the Service Tool Function, MCSS, SET UP, RIDE QUALITY, (M, 2,3,2) to verify the values of
CONTRACT ACCEL, CONTRACT JERK, AND CONTRACT VEL. These parameters are contract dependent.
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
4. If the scalers and profile values are correct and the DICTATED VELOCITY is greater than the CONTRACT
VELOCITY replace the MCSS-A microprocessor board.
5. Access the Service Tool Function, DBSS, MONITOR, DRIVE DATA, (M, 4, 1, 6) to monitor SPEED
REFERENCE (SPD REF) and SPEED FEEDBACK (SPD FBK). Both parameters are scaled in mm/sec. See
DBSS Service Tool Users manual TIP 31.2-1 for further information.
Page 10 of 30
Page 11 of 30
4.4. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETER (M, 2, 3, 4). Check the
value of SPPT VEL SCALER. The value should be 67295. See MCSS Service Tool Users manual TIP 31.41 for further information.
5.5. Access the Service Tool Function, DBSS, MONITOR, DRIVE DATA (m, 4, 1, 6) to monitor SPEED REF
in mm/sec (Dictated Velocity form MCSS) and SPEED FEEDBACK in mm/sec. If the SPEED, RPM, and
TACH CNTS. See MCSS Service Tool Users manual TIP 31.2-1 for further information
6.6. If SPEED REF is incorrect. Access the Service Tool Function, MCSS, SET UP, RIDE QUALITY
PARAMETER (M, 2, 3, 2). Verify that CONTRAT VELOCITY IS set correctly.
7.7. Access the Service Tool Function, DBSS, MONITOR, STABILITY, (M, 4, 1, 2). Verify that the GAIN is
properly set. Typical GAIN settings range from 8 to 13. Low gain settings cause tracking errors while high
gain setting cause oscillation. See MCSS Service Tool Users Manual TIP 31.2-1 for further information.
8.SFTY05- DRV TRCTN ERR - DRIVE TRACTION LOSS
9.Event Counter label - SFTY05
10.Event Log label - DRV TRCTN LOS
11.Fault Code LEDs lit - 1 and 3 (binary 5)
12.The difference between the SPPT Primary channel velocity, PRIMARY CAR VELOCITY, and the PVT
velocity, MACHINE CAR VELOCITY, is greater than the value of TRCT LOSS VEL TL and the difference has
been present for more than the TRCT LOSS CT MAX.
13.1. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETERS (M, 2, 3, 5). Check that
the value of TRCT LOSS VEL TOL, is set to 500 mm/sec, and TRCT LOSS CT MAX, is set to 24 40 ms
cycles. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
14.2. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (M, 2, 3, 4). Check that
the value of SPPT VEL SCALER, is set to 67295 for a 1524 mm circumference SPPT drive sheave. See
MCSS Service Tool Users manual TIP 31.4-1 for further information.
15.3. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (M, 2, 3, 4). Check the
value of PVT POS SCALER, see MCSS I & A document TIP 31.4-2 for values and formula for calculations
based on drive sheave size. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
16.4. Access the Service Tool Function, MCSS, DATA CAPTURE, DISPLAY VARIBALES (M, 2, 5, 1) to
compare the PRIMARY CAR VELOCITY to the MACHINE CAR VELOCITY. Both values should have the
same sign, + for up and - for down. The MACHINE CAR VELOCITY should be the correct sign this data is
sent from the DBSS. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
17.5. If the MACHINE CAR VELOCITY is the wrong sign check the DBSS to MCSS (PVT) communications
wiring.
18.6. If the PRIMARY CAR VELOCITY has the wrong sign check the Rotation orientation DIP SWITCH in
the SPPT. See SPPT document TIP 2.7.1-5.
19.SFTY06- UX, DX RLYS - UP/DOWN RELAYS
20.Event Counter label - SFTY06
21.Event Log label- UX, DX RLYS
Page 12 of 30
Page 13 of 30
Page 14 of 30
Page 15 of 30
Page 16 of 30
Page 17 of 30
Page 18 of 30
Zone 3, a 500 millimeter overrun zone above the top of zone 2 access motion limited to the down direction.
Zone 4, from the top of zone 3 to the bottom of zone 5 no access motion allowed.
Zone 5, a 500 millimeter overrun zone below the bottom of zone 6 access motion limited to the up direction.
Zone 6, from level with the top landing down to the dimension set in ACCESS ZONE LENGTH, both up and
down access motion allowed.
Zone 7, above the top landing access motion limited to down direction only.
1. A valid floor and Door Table must be stored in the EEPROM before Access operation.
2. Access the Service Tool Function MCSS. SET UP, CONTRACT/CODE PARAMETERS (M, 2, 3, 1). Verify
that ACCESS ZONE CHECKING is set to 255 (enabled ). See MCSS Service Tool Users manual TIP 31.4-1
for further information.
3. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (M, 2, 3, 4). Verify that
ACCESS ZONE LENGTH is set to the dimension necessary to bring the crosshead level with the top landing
sill. This dimension is in millimeters. See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
4. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (M, 2, 3, 4). Verify that SPPT
POS SCALER is set to 394 for a 1524 mm circumference SPPT drive sheave. See MCSS Service Tool
Users manual TIP 31.4-1 for further information.
SFTY16- NTSD TBL - NTSD TABLE INTEGRITY
Event Counter label - SFTY16
Event Log label - NTSD TBL
Fault Code LED lit - 5 (binary 16)
At power up, the Normal Terminal Slow Down (NTSD) Random Access Memory (RAM) table is built. If the
checksum calculated at power does not match the dynamically calculated checksum for the NTSD table a fault is
declared.
This fault indicates corruption of data in the microprocessor Random Access Memory (RAM). Replace the
MCSS-A microprocessor card.
SFTY 17 - EPROM CHKSUM - EPROM CHECKSUM ERROR
Event Counter label - SFTY17
Event Log label - EPROM CHKSUM
Fault Code LEDs lit - 1 and 5 (binary 17)
If the dynamically calculated checksum for the EPROM does not match the checksum is the EPROM calculated
at burn in time a fault is declared.
1. Data has been corrupted in the EPROM. Replace the MCSS-A EPROMS.
Page 19 of 30
Page 20 of 30
The MCSS has determined that the feed-back from the U and/or D relay is inconsistent with the Primary Velocity
Transducer (PVT) direction. This test is only performed when the Speed Check (SC) relay is de-energized.
1. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS (m, 2, 2, 1), to command UX to pick.
Verify that the U relay is energized. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
2. Access the Service Tool Function, MCSS, TEST, DISCRETE, OUTPUTS (m, 2, 2, 1), to command DX to pick.
Verify that the D relay is energized. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
3. Access the Service Tool Function, MCSS, MONITOR, DISCRETE INPUTS (M, 2, 1, 2). Verify that when the
U relay is pushed in the UX label goes high, upper case letters, (UX) and when the U relay is out the UX label
is low, lower case letters (ux). See MCSS Service Tool Users manual TIP 31.4-1 for further information.
4. Access the Service Tool Function, MCSS, MONITOR DISCRETE INPUTS (m, 2, 1, 2). Verify that when the D
relay is pushed in the DX label goes high, upper case letters, (DX) and when the D relay is out the DX label is
low, lower case letters (dx). See MCSS Service Tool Users manual TIP 31.4-1 for further information.
5. Access the Service Tool Function, MCSS, MONITOR, DISCRETE INPUTS (m, 2, 1, 2). Verify that when the
SC relay is pushed in the SC label goes high, upper case letters, (SC) and when the SC relay is out the SC
label is low, lower case letters (sc). See MCSS Service Tool Users manual TIP 31.4-1 for further information.
SFTY21- B44 RELAY FAULT - B44 RELAY FAULT
Event Counter label - SFTY21
Event Log label - B44 RELAY FAULT
Fault Code LEDs lit 1, 3 and 5 (binary 21)
The MCSS has determined that the B44 relay, used for Canadian low speed car protection, has failed to pick
when tested at the beginning of a run. This check is only performed if B44 OPTION is ENABLED (255).
1. Use a volt meter to check for 30 VDFC at B44 - 14 relay contact.
2. Push in the B44 relay and check for 30 VDC at P5 - 7 of the MCSS-b board. Also access the Service Tool
Function, MCSS, MONITOR DISCRETE INPUTS, J5-7. With the relay pushed in the display should be in
upper case letters (j5-7) and with the relay out the display should be in lower case letters (J5-7). See MCSS
Service Tool Users Manual TIP 31.4-1 for further information.
3. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, J7-7 to issue the MCSS commands
to pick/drop the B44 relay. See the MCSS Service Tool Users Manual for further information.
SFTY22-B44 TRIPPED - B44 CIRCUIT TRIPPED
Event Counter label- SFTY22
Event Log label - B44 TRIPPED
Fault Code LEDs lit 2, 3 and 5 (binary 22)
MCSS has determined that the car was in motion at a speed greater than the value of B44 TRIP SPEED with the
doors opened. This fault activates the governor solenoid causing the OCS and/or the OIS switches to be opened
and the car and/or counterweight safeties to be set.
Page 21 of 30
Page 22 of 30
Page 23 of 30
Page 24 of 30
A Power On Reset (POR) of the MCSS board is required to clear this fault.
1. Access the Service Tool Function, MCSS, SET UP, MOTION PARAMETERS (m< 2, 3,7). Verify that MLS5
RETRY COUNT MAX is set to 3, and MLS5 TIMEOUT is set to 250 ms. See MCSS Service Tool Users
manual TIP 31.4-1 for further information.
2. Access the Service Tool Function, DBSS, MONITOR, ELEVATOR CONSTANTS (M, 4, 1,). Verify that BRK
HOLD AMP equals the current necessary to hold the brake up, BRK PICK AMP equals the current necessary
to pick the brake, BRK UP RARE equals the length of time necessary to pick the brake fully, BRK DRP RATE
equals the length of time necessary to drop the brake fully. See MCSS Service Tool Users manual TIP 31.21 for further information.
3. Access the Service Tool Function, DBSS, TEST, DISPLAY LIMIT SWITCH.
4. If display indicates BRAKE SWITCH IS IN, observe that the BRAKE LIFTED indicator LED 13 is lit. If LED 13
is not lit check Brake Switch circuit. Caution should be observed as this is a 24 VDC circuit which originates
in the DBSS.
5. If display indicates BRAKE SWITCH IS NOT IN, observe that the BRAKE LIFTED indicator LED 13 is lit. If
LED 13 is not lit use the Service Tool DBSS, MONITOR, ELEVATOR CONSTANTS to verify percent PICK
UP equals 75 this states that if there is greater than 75 percent of the PICK UP current in the circuit the brake
is declared dropped.
DBSS03- STOP & SHUTDOWN - RECEIVED "STOP AND SHUTDOWN" MESSAGE
Event Counter label - DBSS03
Event Log Label - STOP &SHUTDOWN
Fault Code LED lit - NONE
DBSS has sent a single coded bit to the MCSS labeled Stop &SHUTDOWN via the RS422 serial communications
link. This label is used in conjunction with the Motion Fault 01.
DBSS04 - BRK NOT DRPD - TIMED OUT WAITING FOR "BRAKE DROPPED"
Event Counter label - DBSS04
Event Log label - BRK NOT DRPD
Fault Code LEDs lit - 1, 2, 3, 4, 5, 6 flashing (binary 63)_
After a demand has been satisfied the MCSS switches to Motion Logic State (MLS 10) DROP BRAKE. The LIFT
BRAKE command to the DBSS is removed and simultaneously a timer, DROP BRK TIMEOUT is initiated. If the
DBSS does not respond with a BRAKE NOT LIFTED message before the timeout period, the MCSS opens the
safety circuit with the EES relay. This in turn then drops the Brake contactors 1M and 2M located behind the field
and brake control card, this will remove the power from the brake circuit.
A Power On Reset (POR) of the MCSS board is required to clear this fault. This is indicated by all 6 fault code
LEDs flashing.
1. Use the Service Tool MCSS, SET UP, MOTION PARAMETERS, to verify DROP_BRK_TIMEOUT equals
10000 milliseconds.
Page 25 of 30
Page 26 of 30
B. For installations that do not have machine blowers. Check that the factory installed jumper, 6TB-1 to 6TB-2
for a direct drive, or P1 on transformer TRF1 to 10TB-1 in a Ward Leonard drive, is in place.
C. For machines with blowers. Check that the blower vane switch is operating properly (contact closes when
blower is running), and that the blower is operating properly.
D. Use the Service Tool DBSS, TEST, DISPLAY FAULTS, (M, 4, 2, 2) to verify for the occurrences of a Motor
Field Overcurrent condition.
3. If the time since occurrence agrees between MOTN01 and DBSS00:
A. For a Direct Drive check the LEDs on the DBSS Control Card for the presents of a CPU FAULT, IST , LOW
AC LINE, MOTOR FIELD LOSS, BLOWN DC FUSE, MOTOR FIELD OR BRAKE IST, TACH FAULT, BRAKE
OR LOOP CONTACTOR FUALT, or a SERIAL FAULT.
B. For a Ward-Leonard check the LEDs on the DBSS Control Card for the presents of a CPU FAULT, MOTOR
GENERATOR FAULT, LOW DC BUS, MOTOR FIELD LOSS, H-BRIDGE IST, MOTOR FIELD OR BRAKE
IST, TACH FAULT, BRAKE FAULT, or a SERIAL FAULT.
C. Use the Service Tool DBSS, TEST, DISPLAY FAULTS, (M, 4, 2, 2) to verify for the occurrences of DBSS fault
condition.
MOTN02 - BAD BRK STATE - INVALID BRAKE STATE
Event Counter label - MOTN02
Event Log label - BAD BRK STATE
Fault Code LEDs lit - 1, 2, and 6 (binary 35)
The MCSS has determined that the BRAKE STATE sent form the DBSS via the RS422 communications line is
inconsistent with the current MCSS Motion Logic State (MLS) for a time of 3 seconds.
A Power On Reset (POR), indicated by the Fault Code LEDs flashing, of the MCSS board is required to clear this
fault.
1. Place the car in Inspection on the Car Controller Inspection Panel. Trey to run the car using the Up or Down
buttons on the Car Controller Inspection Panel. Verify that the BRAKE LIFTED LED lights when the brake
picks.
2. Use the Service Tool DBSS, SET UP, BRAKE SW I/O is enable (equal to 255).
A. If display indicates BRAKE SW I/O is enabled (255), observe that while attempting motion the BRAKE LIFTED
indicator LED 13 in the DBSS is lit. If LED 13 is not lit check Brake Switch circuit. Caution should be
observed as this is a 24 VDC circuit which originates in the DBSS.
B. If display indicates BRAKE SW I/O is disabled (0), observe that while attempting motion the BRAKE LIFTED
indicator LED 13 in the DBSS is lit. If LED 13 is not lit use the Service Tool DBSS, SET UP, BRAKE PRAMS
(M, 4, 3, 2) to verify percent PICK UP equals 75 this states that if there is greater than 75 percent of the PICK
UP current in the circuit the brake is declared picked, and percent HOLD equals 50 this states that if there is
less than 50 percent of the HOLD current in the circuit the brake is declared dropped.
3. Access the service tool MCSS, SET UP, MOTION PARAMETERS (m, 2, 3, 7). Verify that INV BRK RTRY
MA is set to 3. See MCSS Service Tool Users Manual T.I,P.
31.4-1 for further information.
Page 27 of 30
Page 28 of 30
Page 29 of 30
B. If the MCSS determines an absolute difference between the SPPT primary position value and the SPPT
secondary position value greater than the value of POSITION ERROR TOLERANCE, 500 millimeters, it will
then force a timed deceleration and a reinitialization of the SPPT.
1. Use the Service Tool Function MCSS, DATA CAPTURE, DISPLAY VARIABLE, to view the PRIMARY CAR
POS and the SECONDARD CAR POS. If either of these values is 0 the SPPT has forced the Position Fault.
2. Use the Service Tool Function MCSS,, DATA CAPTURE, DISPLAY VARIABLE, to view the PRIMARY CAR
POS and the SECONDARY CAR POS. If the difference between these 2 values is greater than 500
(millimeters) the MCSS has forced the Position Fault.
3. Replace the SPPT microprocessor printed circuit board.
4. Use the Service Tool Function MCSS, SET UP, POS/VEL, POS ERR TOL to verify that the tolerance is set to
500 millimeters.
5. Replace the MCSS microprocessor printed circuit board.
MOTN09 - LOW AC LINE - LOW AC LINE
Event Counter label - MOTN09
Event Log label - LOW AC LINE
Fault Code LEDs lit - 2, 4 and 6 (binary 42)
The J2 power monitor discrete input has switched indicating that the controller AC power has dipped below 113
VAC (Brown Out Condition). The MCSS will then select REDUCED CONTRACT ACCEL, REDUCED
CONTRACT JERK, and REDUCED CONTRACT VELOCITY, as the active profile.
1. Use a voltmeter to verify the controller AC voltage at J2 voltage monitor terminals J2-7 to J2-2. Voltage
should be 120 VAC nominal.
2. Verify that the adjustment knobs on the top of the J2 voltage monitor are set to the marks on the top of the
monitor case. Pick up is preset to 116 VAC and drop out is preset to 113 VAC.
3. Use the Service Tool Function MCSS, MONITOR, DISCRETE INPUTS, LAC, to verify that the label LAC is in
lower case letters (lac) indicating that the system is not in low AC operation.
Page 30 of 30