Vous êtes sur la page 1sur 30

TIP 31.

4-12 - MCSS Troubleshooting Guide

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

TIP Revision History (Author to complete this section)


Original Author: Paul C. Hoppie
Original Date: 04-06-1992
Revision Author:
Revision Date:
Revision Author:
Revision Date:
Revision Author:
Revision Date:

Previous TIP # (if applicable):


Reason for Revision:
Reason for Revision:
Reason for Revision:

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

MCSS-B INPUT/OUTPUT BOARD

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

TIP 31.4-12 - MCSS Troubleshooting Guide


Communications Fault Group
COMM00 - OCSS RCV ERR - OCSS RECEIVE ERROR
COMM01 - OCSS XMIT ERR - OCSS TRANSMIT ERROR
COMM02 - DBSS RCV ERR - DBSS RECEIVE ERROR
COMM03 - DBSS XMIT ERR - DBSS TRANSMIT ERROR
COMM04 - DCSS RCV ERR - DCSS RECEIVE ERROR
COMM05 - DCSS XMIT ERR - DCSS TRANSMIT ERROR
COMM06 - PPTP RCV ERR - SPPT PRIMARY RECEIVE ERROR
COMM07 - PPTP XMIT ERR - SPPT PRIMARY TRANSMIT ERROR
COMM08 - PPTS RCV ERR - SPPT SECONDARY RECEIVE ERROR
COMM09 - PPTS XMIT ERR - SPPT SECONDARY TRANSMIT ERROR
COMM10 - ERSS RCV ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA RECEIVE
ERROR
COMM11 - EERS XMIT ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA TRANSMIT
ERROR
Safety Group
SFTY01 - DOOR ZONE BYP - DOOR ZONE BYPASS
SFTY02 - LINE OVERSPD - LINE OVERSPEED
SFTY03 - NTSD OVERSPD - NTSD OVERSPEED
SFTY04 - VEL TRKNG ERR - VELOCITY TRACKING ERROR
SFTY05 - DRV TRCTN ERR - DRIVE TRACTION LOSS
SFTY06 - UX, DX TLYS - UP/DOWN RELAYS
SFTY07 - SENSORS - DOOOR ZONE SENSORS
SFTY08 - SC TLY - SPEED RELAYS
SFYT09 - SFTY CHN - SAFETY CHAIN BROKEN
SFTY10 - RECOVERS FAIL - RECOVERY ATTEMPTS
SFTY11 - HEARTBEAT - HEARTBEAT
SFTY12 - E STOP SWITCH - EMERGENCY STOP SWITHCH
SFTY13- BYPASS DROP - DOOR ZONE BYPASS DROP TEST
SFTY14 - DOOR OPEN - DOOR OPEN SAFETY
SFTY15 - ACCESS ZONE - ACCESS ZONE
SFTY16 - NTSD TBL - NTSD TABLE INTEGRITY
SFTY17 - EPROM CHKSUM - EPROM CHECKSUM ERROR
SFTY18 - 30 VOLTS - THIRTY VOLT FAILURE
SFTY19 - NTSD MALFUNC - NTSD MALFUNCTION
SFTY20 - DIR TEST FAULT - DIRECTION TEST FAILURE
SFTY21 - B44 RELAY FAULT - B44 RELAY FAULT
SFTY22 - B44 TRIPPED - B44 CIRCUIT TRIPPED
SFTY23 - ETSD SPD RELAY - EMERGECNY TERMINAL SLOW DOWN RELAY CHECK FAILURE
SFTY24 - ICES CHK FAIL - IN CAR EMERGENCY STOP SWITCH CHECK FAILURE
SFTY25 - INA CHK FAIL - INSPECTION RELAY CHECK FAILURE
SFTY26 - DOOR CHN FAIL - DOOR CHAIN CHECK FAILURE
DBSS Group
DBSS00 - DRIVE FAULT - DRIVE FAULT
DBSS01 - NO RDY TO RUN- TIMED OUT WAITING FOR READY TO RUN
DBSS02 - BRK NOT LFTD - TIMED OUT WAITING FOR "BRAKE LIFTED"
DBSS03 - STOP&SHUTDOWN - RECEIVED "STOP AND SHUTDOWN" MESSAGE
DBSS04 - BRK NOT DRPD - TIMED OUT WAITING FOR "BRAKE DROPPED"

Page 2 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


Motion Faults
MOTN00 - EEPROM JUMPER - EEPROM SWITCH
MOTN01 - DBSS FAULT - DBSS FAULT
MOTN02- BAD BRK STATE - INVALID BRAKE STATE
MOTN03 - BAD RTR STATE - INVALID READY TO RUN STATE
MOTN04 - BAD DBD STATE - INVALID DRIVE AND BRAKE DISCONNECT STATE
MOTN05 - BRAKE TIMEOUT - BRAKE LIFTED TIME EXCEEDED
MOTN06 - GSMON TIMEOUT - GATE SWITCH MONITOR TIMEOUT
MOTN07 - POSINIT FAULT - POSITION INITIALIZATION FAILURE
MOTN08 - POSITION FLT - POSITION FAULT

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

TIP 31.4-12 - MCSS Troubleshooting Guide


Note: There is a priority for LED code display in cases where faults are declared in the same 40 millisecond
frame.
Priority list of LED Indication for Simultaneous Faults
FC18
FC15
FC10
FC09
FC11
FC08
FC07
FC06
FC05
FC04
FC20
FC16
FC03
FC19
FC02
FC14
FC13
FC01
FC12

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

FC17 power up only ERPM CHKSUM


FC63 PRO required

DRIVE FAULTS

The following faults have the highest priority.


FC25
FC26
FC27
FC28
FC29
FC30
FC31
FC32

EEPROM JUMPER
DBSS FAULTS
BAD BRK STATE
BAD RTR STATE
BAD DBD STATE
BRAKE TIMEOUT
GSMON TIMEOUT
POSINIT FAULT

MCSS Event Codes

Page 4 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


Communications Fault Group
COMM00 - OCSS ERR - OCSS RECEIVE ERROR
Event Counter label - COMM00
Event Log label - OCSS RCV ERR
OCSS communication LED lit steady.
The MCSS has not been able to successfully decode a valid message from the OCSS within the time-out period
(OCSS TIME-OUT = 300 milliseconds): This is located in the COMMUNICATIONS TIMING PARAMETERS of
the MCSS EEPROM SET UP.
1. Verify that the OCSS board is up and running. OCSS board mounted LEDs 1 and 2 should be flashing.
2. Verify that the MCSS is up and running. The MCSS-A board mounted Heartbeat (HRTB) LED should be
flashing.
3. Check the MCSS communications wiring to and from OCSS. Check that the OCSS board, connector P4 and
MCSS board, connector P5 are properly connected.
4. Check that the shielding, used on the NAO version new sales controller only, is properly grounded (one end
only ) at the MCSS card cage.
5. Replace the OCSS board.
6. Replace the MCSS-A board.
COMM01- OCSS XMIT ERR _ OCSS TRANSMIT ERROR
Event Counter label - COMM01
Event Log label - OCSS XMIT ERR
OCSS Communication LED flashing.
The MCSS Random Access Memory (RAM) transmission buffer for the OCSS communications channel has
overflowed. This is usually caused by the absence of hardware interrupts from the Dual User Asynchronous
Receive and Transmit (DUART) communication controller.
1. Power on Reset (POR) the MCSS-A board this provides a DUART hardware reset.
2. Replace the MCSS-A microprocessor card.
COMM02- DBSS RCV ERR - DBSS RECEIVE ERROR
Event Counter label - COMM02
Event Log label - DBSS RCV ERR
DBSS communication LED lit steady.
The MCSS has not been able to successfully decode a valid message from the DBSS within the time-out period.
DBSS TIME-OUT = 150 milliseconds, this is located in the COMMUNICATIONS TIMING PARAMETERS of the

Page 5 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


MCSS EEPROM SET UP.
1. Verify that the DBSS board is up and running. DBSS operation can be verified by plugging the Service Tool
directly into the drive.
2. Verify that the MCSS is up and running. The MCSS-A board mounted Heartbeat (HRTB) LED should be
flashing.
3. Check the MCSS communications wiring to and from the DBSS. Check that connector P7 t the MCSS board
and 3TB at the DBSS board are properly connected.
4. Check that the shielding, is properly grounded ( one end only ), DBSS transmit to MCSS at the DBSS Ground
BUS< MCSS transmit to DBSS at the MCSS card cage.
5. Replace the DBSS board.
6. Replace the MCSS-A board.
COMM03 - DBSS XMIT ERR - DBSS TRANSMIT ERROR
Event Counter label - COMM03
Event Log label - DBSS XMIT ERR
DBSS communications LED flashing.
The MCSS RAM transmission buffer for the DBSS communications channel has overflowed. This is usually
caused by the absence of hardware interrupts from the Dual User Asynchronous Receive and Transmit (DUART)
communication controller.
1. Power On Reset (POR) the MCSS-A board this provides a DUART hardware reset.
2. Replace the MCSS-A microprocessor card.
COMM04 - DCSS RCV ERR - DCSS RECEIVE ERROR
Event Counter label - COMM04
Event Log label - DCSS RCV ERR
DCSS communication LED lit steady.
The MCSS has not been able to successfully decode a valid message from the DCSS within the time-out period.
DCSS TIME-OUT = 300 ms, this is located in the COMMUNICATIONS TIMING PARAMETERS of the MCSS
EEPROM SET UP.
1. Verify that the DCSS board is up and running. DCSS operation can be verified by the illumination of the LED
on the DISS board.
2. Verify that the MCSS is up and running. The MCSS-A board mounted Heartbeat (HRTB) LED Should be
flashing.
3. Check the MCSS communications wiring to and from the DCSS. Check that MCSS board connector P7 and
DISS board connector P2 are properly connected.
4. Check that the shielding is properly grounded ( one end only) at the car controller ground bus.

Page 6 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


5. Replace the DISS board.
6. Replace the MCSS-A board.
COMM05 - DCSS XMIT ERR - DCSS TRANSMIT ERROR
Event Counter label - COMM05
Event Log label - DCSS XMIT ERR
DCSS communications LED flashing.
The MCSS RAM transmission buffer for the DCSS communications channel has overflowed. This is usually
caused by the absence of hardware interrupts from the Dual User Asynchronous Receive and Transmit *DUART)
communication controller.
1. Power On Reset (POR) the MCSS-A board this provides a DUART hardware reset.
2. Replace the MCSS_A microprocessor card.
COMM06 - PPTP RCV ERR - SPPT PRIMARY RECEIVE ERROR
Event Counter label - COMM06
Event Log label - PPTP RCV ERR
PPT1 communications LED lit steady.
The MCSS has not been able to successfully decode a valid message from the SPPT PRIMARY CHANNEL
within the 5 100 ms time-out periods. SPPTP COMM_TIME =20 milliseconds, this is located in the
COMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP.
1. Verify that the SPPT board is up and running. SPPT operation can be verified by the illumination of the 2
green LEDs on the SPPT.
2. Verify that the MCSS is up and running. The MCSS-A board mounted Heartbeat (HRTB) LED should be
flashing.
3. Check the MCSS communications wiring to and from the SPPT. Check that MCSS board connector P6 and
SPPT assembly 25 pin "D" connector are properly connected.
4. Check that the shielding is properly grounded ( one end only) at the MCSS card cage.
5. Replace the SPPT board.
6. Replace the MCSS-A board.
COMM07 - PPTP XMIT ERR - SPPT PRIMARY TRANSMIT ERROR
Event Counter label - COMM07
Event Log label - PPTP XMIT ERR
PPT1 communications LED flashing.

Page 7 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


The MCSS RAM transmission buffer for the SPPT PRIMARY communications channel has overflowed. This is
usually caused by the absence of hardware interrupts form the Dual User Asynchronous Receive and Transmit
(DUART) communication controller.
1. Power On Reset (POR) The MCSS-A board this provides a DUART hardware reset.
2. Replace the MCSS-A microprocessor card.
COMM08 - PPTS RCV ERR - SPPT SECONDARY RECEIVE ERROR
Event Counter label - COMM08
Event Log label - PPTS RCV ER
PPT2 communications LED lit steady.
The MCSS has not been able to successfully decode a valid message from the SPPT SECONDARY CHANNEL
within the time-out period. SPPTS_COMM_TIME = 20 milliseconds, this is located in the COMMUNICATIONS
TIMING PARAMETERS of the MCSS EEPROM SET UP.
1. Verify that the SPPT board is up and running. SPPT operation can be verified by the illumination of the 2
green LEDs on the SPPT.
2. Verify that the MCSS is up and running. The MCSS-A board mounted Heartbeat (HRTB) LED should be
flashing.
3. Check the MCSS communications wiring to and from the SPPT. Check that MCSS board connector P6 and
SPPT assembly 25 pin "D" connector are properly connected.
4. Check that the shielding is properly grounded (one end only) at the MCSS card cage.
5. Replace the SPPT board.
6. Replace the MCSS-A board.
COMM09 - PPTS XMIT ERR - SPPT SECONDARY TRANSMIT ERROR
Event Counter label - COMM09
Event Log label - PPTS XMIT ERR
PPT2 communication LED flashing.
The MCSS RAM transmission buffer for the SPPT SECONDARY communications channel has overflowed. This
is usually caused by the absence of hardware interrupts form the Dual User Asynchronous Receive and Transmit
(DUART) communication controller.
1. Power On Reset (POR) the MCSS-A board this provides a DUART hardware reset.
2. Replace the MCSS-A microprocessor card.

Page 8 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


COMM10 - E4RSS RCV ERR - EMERGENCY RESCUE SUB SYSTEM / DOUBLE DECK DCSSA RECEIVE
ERROR
Event Counter label - EERS RCV ERR
Event Log label - COMM10
ERO communications LED on STEADY
The MCSS has not been able to successfully decode a valid message from the EMERGENCY RESCUE SUB
SYSTEM (JERO) or the DCSSA (double deck) channel within the time-out period. DCSSA COMM_TIME = 300
milliseconds, this is located in the COMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP.
1. Verify that the JERO/DCSSA board is up and running.
2. Verify that the MCSS is up and running. The MCSS-A board mounted Heartbeat (HRTB) LED should be
flashing.
3. Check the MCSS communications wiring to and from the JERO/DCSSA. Check that MCSS board connector
P4 and JERO/DCSSA assembly connector are properly connected.
4. Check that the shielding is properly grounded (one end only) at the MCSS card cage.
5. Replace the JERO/DSSA board.
6. Replace the MCSS-A board.
COMM11 - EERS XMIT ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA TRANSMIT
ERROR
Event Counter label - COMM11
Event Log label - ERSS XMIT ERR
ERSS communications LED flashing.
The MCSS RAM transmission buffer for the EMERGENCY RESCUE SUB SYSTEM (JERO) or DCSSA (Double
Deck) communications channel has overflowed. This is usually caused by the absence of hardware interrupts
from the Dual User Asynchronous Receive and Transmit (DUART) communication controller.
1. Power On Reset (POR) the MCSS-A board this provides a DUART hardware reset.
2. Replace the MCSS-A microprocessor card.
Safety Group
SFTY01 - DOOR ZONE BYP - DOOR ZONE BYPASS
Event Counter label - DOOR ZONE BYP
Event Log label - SFTY01
Fault Code LED lit - 1 (binary 1)
The MCSS has determined, by the relay sense contact, that the Door Zone (DZ) or Alternate Door Zone (ADZ)
relay is in a state other than that commanded by the MCSS.

Page 9 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

TIP 31.4-12 - MCSS Troubleshooting Guide


6. If the SPEED FEEDBACK is incorrect check the TACH COUNTS, RPM, and RATED SPEED under
ELEVATOR CONSTANTS in the DBSS. Also visually inspect the TACH and coupling for physical flaws or
damage.
7. If values are correct replace the DBSS control card.
SFTY03 - NTSD OVERSPD - NTSD OVERSPEED
Event Counter label - SFTY03
Event Log label - NTSD OVERSPD
Fault Code LEDs lit - 1 and 2 (binary 3)
The MCSS has determined that the velocity dictation is in excess of the Normal Terminal Slow Down (NTSD)
velocity limit as calculated from the SPPT Secondary channel position information. This data is compared against
the calculated NTSD_RAM table, assembled at power up, together with the NTSD_DECEL parameter set to 1500
mm/sec.
1. Access the Service Tool Function, MCSS SET UP, RIDE QUALITY, (M, 2, 3, 2) DECEL RATIO. Verify that
the value, A percent of CONTRACT ACCEL does not exceed 1500 mm/s. Also verify that none of the 7 ALT
PROFILE DEC rates exceed 1500 mm/s2. See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
2. Access the Service Tool Function, MCSS, DATA CAPTURE, DISPLAY VARIBALES, (M, 2, 5, 1) PRIMARY
CAR POS and SECONDARY POS. Verify that these positions are the same and correct for the position in
the hoistway. See further information.
3. If the positions displayed above are incorrect Access the Service Tool Function, MCSS, SET UP, POS/VEL
(M, 2, 3, 4) and verify that the value for 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.
SFTY04 - VEL TRKNG ERR - VELOCITY TRACKING ERROR
Event Counter label - SFTY04
Event Log Label - VEL TRKNG ERR
Fault Code LED lit - 3 (binary 4)
The difference between the SPPT Primary channel velocity (PRIMARY CAR VEL) and the DICTATED VELOCITY
has exceeded the value set in TRACKING ERR VEL TOL in MCSS, SET UP, SAFETY PARAMETERS. If this
occurs for 6 consecutive confirmation cycles, a Velocity Tracking Error is logged.
1.1. Access the Service Tool Function, MCSS DATA CAPTURE, (M, 2, 5, ) DISPLAY VARIABLE to compare
the value of the DICTATED VELOCITY and PRIMARY CAR VELOCITY. See MCSS Service Tool Users
Manual TIP 31.4-1 for further information.
2.2. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETER (m, 2, 3, 5). Check the
value of TRCK ERR VEL TOL. The value should be 6. See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
3.3. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETERS (M, 2, 3, 4). Check the
value of VL TRK ERR CT MAX. The value should be 6. See MCSS Service Tool Users manual TIP 31.4-1
for further information.

Page 11 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

TIP 31.4-12 - MCSS Troubleshooting Guide

22.Fault Code LEDs lit - 2 and 3 (binary 6)


23.This fault can be generated in two possible ways.
24.A. The U or D relay, is in a state, opposite to the MCSS commanded state, as monitored by the relay
sense inputs on the MCSS-B I/O board.
25.Or
26.B. The direction relay picked is wrong when compared to the actual direction of travel. This is based on
the SPPT Primary velocity channel when the car speed reaches 60 percent of contract speed.
27.These checks are only performed in non-manual modes with the Motion Logic State (MLS) greater than or
equal to Run (MLS 7).
28.1. Access the Service Tool Function, MCSS, DATA CAPTURE, DISPLAY VARIABLE, (M, 2, 5, 1)
PRIMARY CAR VELOCITY, to see if the fault occurs near 60 percent of contract speed. See MCSS Service
Tool Users manual TIP 31.4-1 for further information.
29.2. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETERS, (M, 2, 3, 5). Check that
the value of UXDX CHECK percent equals 60, and UX & DX CT MAX equals 6. See MCSS Service Tool
Users manual TIP 31.4-1 for further information.
30.3. Use a volt meter to check for 30 VDC at U-43, and D43 relay contacts. See MCSS Service Tool Users
manual TIP 31.4-1 for further information.
31)4. Push in the U relay and check for 30 VDC at P4 - 8 of the MCSS-B board. Also access the Service
Tool Function, MCSS, MONITOR, DISCRETE INPUTS, (M, 2, 1, 2) UX. With the relay pushed in the display
should be in upper case letters (UX) and with the relay out the display should be in lower case letters (ux).
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
32)5. Push in the D relay and check for 30 VDC at P4 -10 of the MCSS-B board. Also access the Service
Tool Function, MCSS, MONITOR, DISCRETE INPUTS, (M, 2, 1, 2) DX. With the relay pushed in the display
should be in upper case letters (DX) and with the relay out the display should be in lower case letters (dx).
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
33)6. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, (M, 2, 2, 1) UX to issue
MCSS commands to pick the U relay. See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
34)7. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, (M, 2, 2, 1) DX, to issue
MCSS commands to pick the D relay. See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
35)SFTY07-SENSORS-DOOR ZONE SENSORS
36)Event Counter label - SFTY07
37)Event Log label - SENSORS
38)Fault Code LEDs lit - 1,2 and 3 (binary 7)
The MCSS has determined that one or more Door Zone Sensor transducers are in the ON state instead of the
OFF state. This test is performed in a window created by the SENSOR CHK BEGIN DIST< normally 2000
millimeters and SENSOR CHK END, DIST, normally 600 millimeters. These distances are taken from the SPPT

Page 13 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


Primary channel during the approach to the landing. If the ON state is detected for 6 consecutive 40 millisecond
cycles a SFTY07 (Door Zone Sensor Fault) is declared and Advanced Door Opening is disabled.
1. Access the Service Tool Function, MCSS, SETUP, SAFETY PARAMETERS (M,2,3, 5). Check that SENS
CHK END-DIST is equal to 600. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
2. Access the Service Tool Function, MCSS, SETUP, SAFETY PARAMETERS (m< 2, 3, 4). Check that SENS
CHK BEG-DIS is equal to 394 for a 1524 mm circumference SPPT drive sheave. See MCSS Service Tool
Users manual TIP 31.4-1 for further information.
3. With the car level at the landing, check to see that all sensors are on. The Door Zone indicator LEDs if
provided, on the Car Controller Inspection Panel should be ON. Access the Service Tool Function, MCSS,
MONITOR, DISCRETE INPUTS (M, 2, 1, 2) and verify that all Door Zone inputs are ON, upper case letters
(FID1, FODZ, FID2, AID1, AODZ, AID2). See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
4. Move the car 600 millimeters away from the landing, check to see that all sensors are OFF. The Door Zone
indicator LEDs, if provided, on the Car Controller Inspection Panel should be OFF. Access the Service Tool
Function, MCSS, MONITOR, DISCRETE INPUTS (m, 2, 1, 2) and verify that all Door Zone inputs are OFF.
Lower case letters (fid1, fodz, fid2, aid1, aodz, aid2). See MCSS Service Tool users manual TIP 31.4-1 for
further information.
5. Repair wiring or replace sensors as necessary,
SFTY08 - SC RLY - SPEED RELAYS
Event Counter label - SFTY08
Event Log label - SC RLY
Fault Code LED lit - 4 (binary 8)
This fault can be generated in two possible ways:
A. MCSS determines that the Speed Check (SC) relay feed back contacts are not in agreement with the state of
the Speed Check relay command.
Or
B. The elevator speed, as provided by the SPPT Primary channel, is greater than the CODE LEVELING
VELOCITY, multiplied by the NORMAL_VEL_TOL_PERCENT, at the same time that the speed Check feed
back is high or there is voltage present at SCS1 or SCS2.
1. Use a volt meter to check for 30 VDC at the SC Relay sense contact. See MCSS Service Tool Users manual
TIP 31.4-1 for further information.
2. Push in the SC relay and check for 30 VDC at P5 - 1 of the MCSS-B board. Also access the Service Tool
Function, MCSS, MONITOR, DISCRETE INPUTS, (M, 2, 1, 2) SC. With the relay pushed in the display
should be in upper case letters (SC) and with the relay out the display should be in lower case letters (sc).
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
3. Access the Service Tool Function, MCSS, SETUP, CONTRACT/CODE (M, 2, 3, 1). Verify that CODE
LEVELING VEL IS equal to 750 millimeters per second for ANSI applications, and 450 millimeters per second
for CEN applications. See MCSS Service Tool Users manual TIP 31.4-1 for further information.

Page 14 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


4. Access the Service Tool Function, MCSS, SETUP, SAFETY PARAMETERS (m, 2, 3, 5). Verify that
NORMAL VEL TOL percent is equal to 110, and SC RELAY TIME is equal to 8 (8, 40 millisecond cycles).
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
5. Access the Service Tool Function, MCSS, SETUP, POS/VEL PARAMETERS (M, 2, 3, 4) to verify SPPT POS
SCALER is equal to 394 for a 1524 mm circumference (20 inch diameter) SPPT drive sheave. See MCSS
Service Tool Users manual TIP 31.4-1 for further information.
6. With the car parked at a landing disconnect the discrete independent speed check input between the SPPT
and the MCSS-B phoenix connector J4-5. The SC relay should drop out. See MCSS Service Tool Users
manual TIP 31.4-1 for further information.
7. Access the Service Tool function, MCSS, MONITOR, DISCRETE INPUTS (m, 2, 1, 2) and verify that with the
J4-5 wire removed the speed Check Drive Check (SCDC) input is low, (lower case letters scdc). See Service
Tool Users manual TIP 31.4-1 for further information.
8. Reconnect the wire from the SPPT to the MCSS-B Phoenix connector J4-5. The SC relay should pick up.
9Access the Service Tool Function, MCSS, MONITOR< DISCRETE INPUTS (M, 2,1, 2) and verify that with the
(SCDC) input is high, (upper case letters SCDC). See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
10. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (m, 2, 3, 2). Set the INSPECTION
VELOCITY equal to 600 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
11. Run the car using the up or down buttons on the car Controller Inspection Panel. Verify that the SC Relay
remains energized. If the SC relay drops out, replace the SPPT processor board.
12. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (M, 2, 3, 2). Set the INSPECTION
VELOCITY equal to 800 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
13. Temporarily place a jumper across the SC 13-14 contacts in the Safety Circuit. Run the car using the up or
down buttons on the Car Controller Inspection Panel. Verify that the SC relay drops out. If the SC relay
remains energized, at 800 mm/s, measure the voltage between MCSS-B J4-5 (+) to J4-6 (-). If this voltage is
5 VDC replace the SPPT Processor board. If the voltage is 0.0 VDC replace the MCSS-B board. See MCSS
Service Tool Users manual TIP 31.4-1 for further information.
14. Remove all temporary jumpers and reset INSPECTION VELOCITY equal to 400 mm/s. See MCSS Service
Tool Users manual TIP 31.4-1 for further information.
SFTY09- SFTY CHN - SAFETY CHAIN BROKEN
Event Counter label - SFTY09
Event Log label - SFTY CHN
Fault Code LEDs lit - 1 and 4 (binary 9)
MCSS has determined that SAFEOUT is active, EES relay driver (SAFEOUT) is turned on. SCS5 Safety Chain
sensing, has gone low or SCS6 Safety Chain sensing has gone high (SAFE) indication the opening of the Safety
Chain.
Note: A Safety Fault 9 will be declared each time the car is placed on Access or Inspection operation and each
time a door lock is opened during inspection operation. This is due to the automatic dropping of the Door
Zone (DZ) relay the contacts of which are in the Door Lock Bypass circuit.

Page 15 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


1. Operation of a safety switch is indicated if SCS1 and SCS2 remain high when SAFEIN goes low.
2. A failure of one of the following: FGDS1, FGDS2, AGDS1, or AGDS2, is indicated by: The DZ relay status
indicates that the DZ and/or the ADZ relay is not picked, and the SC relay status indicates that the SC relay is
picked, and the SCS1 and/or the SCS2 sense point is low. All relay status can be checked by accessing the
Service Tool Function, MCSS, MONITOR, DISCRETE OUTPUTS (M, 2, 1, 2). See MCSS Service Tool
Users manual TIP 31.4-1 for further information.
3. A failure of the door lock or gate switch is indicated if the DZ relay status indicates that the DZ and/or or the
ADZ relay is not picked, the FGDS and/or AGDS sense point is low and the SC relay status indicates that the
SC relay is picked, and the SCS1 and/or the SCS2 sense point is low. All relay status can be checked by
accessing the Service Tool Function, MCSS, MONITOR, DISCRETE OUTPUTS (M, 2, 1, 2). See MCSS
Service Tool Users manual TIP 31.4-1 for further information.
SFTY10 - RECOVERS FAIL - RECOVERY ATTEMPTS
Event Counter label - SFTY10
Event Log label - RECOVER FAIL
Fault Code LEDs lit - 2 and 8 (binary 10)
The MCSS contains a counter that records the number of times that the Motion Logic State (MLS) is Pre Run (4)
while in the Motion Command Mode (MCM) is Recover (5). If this counter exceeds the value in the label, MAX
RECOVER TRIES, a Safety Fault 10 is declared.
This fault requires a Power On Reset (POR) of the MCSS.
1. Access the Service Tool Function, MCSS, SET UP, RIDE QUALITY PARAMETERS (M, 2, 3, 2). Verify that
the value of Recover Velocity is equal to 600 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
2. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (M, 2, 3, 4). Verify that the
value of RELEVEL ZONE DISTANCE is equal to 76 mm. See MCSS Service Tool Users manual TIP 31.4-1
for further information.
3Access the Service Tool Function, MCSS, SET UP , SAFETY PARAMETERS (M, 2, 3, 5). Verify that the
value of MAX RECOVER TRIES is equal to 5. See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
4. Place the car on inspection and move the car more than 76 mm away from the landing. Take the car off of
inspection. The car should recover to the floor. If the recovery fails trouble shoot the system to find what is
inhibiting recovery.
SFTY11-HEARTBEAT- HEARTBEAT
Event Counter label - SFTY 11
Event Log label - Heartbeat
Fault Code LEDs lit 1, 2 and 4 (binary 11)
Before each run MCSS performs a check to verify the ability to drop the safety chain via the "CIO" relay, the
status of the Drive and Brake Disconnect (DBD) signal, and the status of the Front and Alternate Gate and Door
Status (FGDS and AGDS) relays. If any of these checks fail a SFTY11 fault is declared.

Page 16 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


If this test fails 10 consecutive times a Power On Reset (POR) of the MCSS is required to clear this fault.
1. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETERS (M, 2, 3, 5). Check that the
value of HEARTBEAT DELAY equals 280 ms for a direct drive system, or 500 ms for a ward Leonard system.
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
2. Access the Service Tool Function, MCSS, MONITOR, DISCRETE INPUTS, DBDC. Verify that with the "CIO"
relay de-energized the display is in lower case letters, (dbdc) and with the "CIO" relay pushed in the display is
in upper case letters (DBDC). 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 with the
safety circuit relays "C1" and "C2" and the Drive relays "4CR" and "5CR" energized the display is in lower
case letters, (DBDC) and if the relays "C1", or "C2", are de-energized with the drive relays "4CR" and "5CR"
energized the display is in upper case letters (DBDC). See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
SFTY12 - E STOP SWITCH - EMERGENCY STOP SWITCH
Event Counter label - SFTY12
Event Log label - E STOP SWITCH
Fault Code LEDs lit - 3 and 4 (binary 12)
The 30 VDC input to MCSS-B Phoenix connector J4 pin 1 has gone low. This initiates a timed deceleration of the
elevator.
1. Access the Service Tool Function, MCSS, MONITOR, DISCRETE INPUTS (M, 2, 1, 2). Verify that with the In
Car Emergency Stop Switch in the RUN position the input is displayed in lower case letters (ices). If the
display is in upper case letters (ICES) it is an indication that the Stop Switch in the car is in the STOP
position. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
SFTY13 - BYPASS DROP - DOOR ZONE BYPASS DROP TEST
Event Counter Label - SFTY13
Event Log label - BYPASS DROP
Fault Code LEDs lit - 1, 3, and 4 (binary 13)
At the start of a run the system is brought up to Motion Logic State (MLS) 6, Low Level Phase Plane, the MCSS
performs a Door Zone Bypass Drop Test. During this test the Door Zone (DZ) and Alternate Door Zone (ADZ)
relays are commanded to drop at the same time a counter is started. If the DZ and ADZ relay feed-back status
does not indicate that the relays have dropped, a fault is declared and the system is shut down.
A Power On Reset (POR) of the MCSS is required to clear this fault.
1. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETERS (m, 2, 3, 5). Verify that DZ
RELAY TIME is set to 8 (8, 40 millisecond cycles ). See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
2. Access the Service Tool Function, MCSS, MONITOR, DISCRETE INPUTS (M, 2, 1, 2). Verify that when the
DZ relay is de-energized, the display is in lower case letters (dz) and if the relay is energized or pushed in the
display is in upper case letters (DZ). See MCSS Service Tool Users manual TIP 31.4-1 for further
information.

Page 17 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


3. Repeat step 2 for the Alternate Door Zone relay (ADZ) if supplied.
SFTY14 - DOOR OPEN - DOOR OPEN SAFETY
Event Counter label - SFTY14
Event Log Label - DOOR OPEN
Fault Code LEDs lit - 2, 3 and 4 (binary 14)
The MCSS has determined that the Front and/or Alternate Doors are opened outside of the Leveling Zone.
1. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (m, 2, 3, 4). Verify that SPPT
POS SCALER is set to 394 and SPPT VEL SCALER equals 67295 for a 1524 mm circumference SPPT drive
sheave. Also verify that the LEVEL ZONE DISTANCE is set to 6 mm, LEVELING ZN DISTANCE is set to
Service Tool Users manual TIP 31.4-1 for further information.
2. Access the Service Tool Function, MCSS SET UP, MOTION CONTROL PARAMETERS ( M, 2, 3, 7). Verify
that STOP TOL VEL is set to 18 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for further
information.
3. Use the Car Controller Inspection Panel to place the car on inspection. Access the Service Tool Function,
MCSS, MONITOR, DISCRETE INPUTS (m, 2, 1, 2). Monitor FID1, FODZ, and FIDZ. Run the car up and
down on inspection and verify that all sensors change state in the correct order. See MCSS Service Tool
Users manual TIP 31.4-1 for further information.
4. If the car has alternate doors, use the Car Controller Inspection Panel to place the car on inspection. Access
the Service Tool Function, MCSS, MONITOR DISCRETE INPUTS (M, 2, 1, 2). Monitor AID1, AODZ, and
AID2. Run the car up and down on inspection and verify that all sensors change state in the correct order.
See MCSS Service Tool Users manual TIP 31.4-1 for further information.
5. Park the car level at a landing. Access the Service Tool Function, MCSS, MONITOR, STATES/COMMANDS
(M, 2, 1, 1). Operate the doors and verify that the Door Fully closed symbols ( ][ ][) appear in the upper right
hand corner of the Service Tool display for both the front and alternate doors. See MCSS Service Tool Users
manual TIP 31.4-1 for further information.
6. Check that the Door Zone sensor vane is properly set at the landing where the fault occurred. The top of the
vane should be level with the top of the sensor bracket when the car level at the landing. The blade of the
vane must project 60 mm +/- 10 mm into the sensor. See E411 Door Zone Sensor Installation and
Adjustment pamphlet TIP 3.5.4-1 for further information.
SFTY15 - ACCESS ZONE - ACCESS ZONE
Event Counter label - SFTY15
Event Log label - ACCESS ZONE
Fault Code LEDs lit - 1, 2, 3, and 4 (binary 15)
If an attempt at access motion is made in a direction which is not permitted in that zone a fault is logged. The
Access zones are:
Zone 1, below bottom landing access motion limited to up direction only.
Zone 2, from level with the bottom landing up to the position set in ACCESS ZONE LENGTH both up and
down access motion allowed.

Page 18 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

TIP 31.4-12 - MCSS Troubleshooting Guide


2. This fault indicates corruption of data in the microprocessor Random Access Memory (RAM). Replace the
MCSS-A microprocessor card.
SFTY18- 30 VOLTS - THIRTY VOLT FAILURE
Event Counter label - SFTY18
Event Log label - 30 VOLTS
Fault Code LEDs lit - 2 and 5 (binary 18)
MCSS hardware samples the 30 VDC supply for the Door Zone sensors and the relay status contacts. This
voltage must be 30 volts +/- 6 volts, or a failure is declared. If the car is at rest, it will not be allowed to start; if in
flight, a timed deceleration will be made and an attempt to recover to the landing. Once a 30 volt failure has been
declared it cannot be cleared until the 30 VDC is back within its operating range.
1. Access the Service Tool Function, MCSS, SET UP, SAFETY PARAMETERS (M, 2, 3, 5). Verify THIRTY
VOLT TIMEOUT, and THIRTY VOLT RECOVER are set to 500 ms. See MCSS Service Tool Users manual
TIP 31.4-1 for further information.
2. Check the 30 VOK LED on the front of the MCSS-B card just below connector J6. When the LED is lit, 30
VDC is within parameters.
3. Use a voltmeter to monitor the 30 VDC at the power supply. See applicable Straight Wiring diagram for
further details.
SFTY19-NTSD MALFUNC- NTSD MALFUNCTION
Event Counter label - SFTY19
Event Log label - NTSD MALFUNC
Fault Code LEDs lit - 1, 2, and 5 (binary 19)
Normal Terminal Slow Down (NTSD) information is obtained from the SPPT secondary channel. If the SPPT
secondary channel velocity information is in excess of 125 percent of INITIALIZATION VELOCITY with no SPPT
secondary position known, an NTSD malfunction is logged.
1. Access the Service Tool Function, MCSS, SET UP, RIDE QUALITY (M, 2, 3, 2). Verify that INIT VELOCITY
equals 600 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for further information.
2. Access the Service Tool Function, MCSS, SET UP, POS/VEL PARAMETERS (M, 2, 3, 4). Verify that SPPT
POS SCALER is set to 394, and 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.
3. Access the Service Tool Function, MCSS, DATA CAPTURE, DISPLAY VARIABLES (M, 2, 5, 1). Verify that
SECONDARY POS and SEC CAR VEL are valid. See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
SFTY 20- DIR TEST FAULT-DIRECTION TEST FAILURE
Event Counter label - SFTY20
Event Log label - DIR TST FAULT
Fault Code LEDs lit - 3 and 5 (binary 20)

Page 20 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

TIP 31.4-12 - MCSS Troubleshooting Guide


1. Use the Service Tool Function, MCSS, SETUP, SAFETY PARAMETERS, to verify the setting of B44 TRIP
SPEED is 50 millimeters per second.
2. Use the Service Tool Function, MCSS, SETUP, POS/VEL PARAMETERS. Verify the value of PVT POS
SCALER, see MCSS I&A document TIP 31.4-2 for the table of values and the formula for calculations based
on the drive sheave size.
3. Use the Service Tool Function, MCSS, DATA CAPTURE, DISPLAY VARIABLE, MCHN VEL (MACHINE CAR
VELOCITY) to verify the value of the data from the PVT (Primary Velocity Transducer) is correct.
4. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, B44 to issue the MCSS commands
to pick/drop the B44 relay. See the MCSS Service Tool Users Manual for further information.
SFTY23 - ETSD SPD RELAY - EMERGENCY TERMINAL SLOW DOWN RELAY CHECK FAILURE
Event Counter label - SFTY23
Event Log label - ETSD SPD RLY
Fault code LEDs lit 1, 2, 3, and 5 (binary 23)
MCSS has determined that the ETSD relay is in a state not consistent with the MCSS commanded state, as
monitored by the relay sense inputs on the MCSS-B board.
Note: The ETSD OPTION and B44 OPTION are mutually exclusive as they both use the same relay driver and
the same contact sense input. Use of the ETSD OPTION is not allowed by the ANSI A17.1 or by the
CAN/CSA-B44 Safety Codes.
1. Use a volt meter to check for 30 VDC at ETSD - XX relay contact.
2. Push in the ETSD 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 for further information.
3. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, J7-7 to issue the MCSS commands
to pick/drop the ETSD relay. See the MCSS Service Tool Users Manual for further information.
SFTY24 - ICES CHK FAIL - IN CAR EMERGECNY STOP SWITCH CHECK FAILURE
Event Counter label -SFTY24
Event Log label - ICES CHK FAIL
Fault Code LEDs lit 4, and 5 (binary 24)
MCSS did not see the In Car Emergency Stop Switch (ICES) input (j4-1) go to 0.0 volts when the CIO relay is
tested prior to a run.
1. Use the Service Tool Function, MCSS, SETUP, CONTRACT/CODE, CIO RELAY OPTION to verify that this
option is enabled (255).
2. Push in the CIO relay and check for 30 VDC at J4-1 of the MCSS-b board. Also access the Service Tool
Function, MCSS, MONITOR DISCRETE INPUTS, ICES. With the relay pushed in the display should be in
lower case letters (ices) and with the relay out the display should be in upper case letters (ICES). See MCSS
Service Tool Users Manual TIP 31.4-1 for further information.

Page 22 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


3. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, CIO to issue the MCSS commands
to pick/drop the CIO relay. See the MCSS Service Tool Users Manual for further information.
SFTY25 - INA CHK FAIL - INSPECTION RELAY CHECK FAILURE
Event Counter label - SFTY25
Event Log label - INA CHK FAIL
Fault Code LEDs lit 1, 4 and 5 (binary 25)
MCSS did not see the Inspection/Normal input (J4-2) go to 0.0 volts when the CIO relay is tested prior to a run.
1. Use the Service Tool Function, MCSS, SETUP, CONTRACT/CODE, CIO RELAY OPTION to verify that this
option is enabled (255).
2. Push in the CIO relay and check for 30 VDC at J4 - 2 of the MCSS-b board. Also access the Service Tool
Function, MCSS, MONITOR DISCRETE INPUTS, INA. With the relay pushed in the display should be in
lower case letters (ina) and with the relay out the display should be in upper case letters (INA). See MCSS
Service Tool Users Manual TIP 31.4-1 for further information.
3. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, CIO to issue the MCSS commands
to pick/drop the CIO relay. See the MCSS Service Tool Users Manual for further information.
SFTY26 - DOOR CHN FAIL _ DOOR CHAIN CHECK FAILURE
Event Counter label - SFTY26
Event log label - DOOR CHN FAIL
Fault Code LEDs lit 2, 4, and 5 (binary 26)
MCSS has determined that when the CIO relay test was performed, at the beginning of a run, the FGDS input
channel J6- 1 and/or the AGDS input channel J7- 12 did not go high (115 VAC). If this is a Canadian installation
the feed to drive the channels high is through the Car and Counterweight governor solenoids, thus checking their
continuity at the same time.
1. Use the Service Tool Function, MCSS, SETUP, CONTRACT/CODE, CIO RELAY OPTION to verify that this
option is enabled (255).
2. Push in the CIO relay and check that FGDS1 and FGDS2 relays drop out. Also verify that the AGDS1 and
AGDS2 relays, if provided, drop out.
3. Access the Service Tool Function, MCSS, MONITOR DISCRETE INPUTS, FGDS and or AGDS. With the
CIO relay pushed in the display should be in lower case letters (fgds and or agds) and with the relay out the
display should be in upper case letters (FGDS and or AGDS). See MCSS Service Tool Users Manual TIP
31.4-1 for further information.
4. Access the Service Tool Function, MCSS, TEST, DISCRETE OUTPUTS, CIO to issue the MCSS commands
to pick/drop the CIO relay. See the MCSS Service Tool Users Manual for further information.
DBSS GROUP
Events listed in the DBSS section of the MCSS EVENT LOG do not have their own MCSS Fault Code but are
there to alert you that fault conditions that may exist in the DBSS.

Page 23 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


DBSS00-DRIVE FAULT- DRIVE FAULT
Event Counter label - DBSS00
Event Log label - DRIVE FAULT
Fault Code LED(s) lit - NONE
DBSS has sent a single coded bit to the MCSS labeled Drive Fault via the RS422 Serial communications link.
This label is used in conjunction with Motion fault 01. See MCSS Service Tool Users manual TIP 31.4-1 for
further information.
DBSS01- NO RDY TO RUN - TIMED OUT WAITING FOR "READY TO RUN"
Event Counter label - DBSS01
Event Log label - NO RDY TO RUN
Fault Code LEDs lit - 1, 2, 3, 4, 5, 6 flashing (binary 63)
In response to a demand, MCSS has proceeded to Motion Logic State (MLS 3), PREPARE TO RUN. This
message is sent to the DBSS, simultaneously MLS3 TIMEOUT, timer, is started in MCSS to allow a waiting time
for the DBSS to send a response message READY TO RUN. If MLS3 TIMEOUT is allowed to time out for the
MLS3 RETRY MAX, a DBSS01 fault is logged.
A Power On Reset (POR) of the MCSS board is required to clear this fault.
Access the Service Tool Function, MCSS, SET UP, MOTION PARAMETERS (M, 2, 3, 7). Verify that MLS3
RETRY COUNT MAX is set to 3, and MLS3 TIMEOUT is set to 1500 ms. See MCSS Service Tool Users
manual TIP 31.4-1 for further information.
Verify that all fault LEDs in the DBSS are extinguished.
Verify that in the DBSS, the Brake contactors 1M and 2M are energized, located behind the Brake and Motor
Field control card on a Direct Drive or the GFS relay for a Ward Leonard.
Verify that in the DBSS, the Loop contactors 1M and 2M are energized, the contactors are located at the left hand
center of the back panel on the Direct Drive, or the H relay for a Ward Leonard are energized.
5. Access the Service Tool Function, DBSS, MONITOR, DRIVE DATA (M< 4, 1, 6). Verify that FIELD
CURRENT is equal to FULL FIELD located in the FIELD CONSTANTS branch of MONITOR. See DBSS
Service Tool Users manual TIP 31.2-1 for further information.
DBSS02- BRK NOT LFTD- TIMED OUT WAITING FOR "BRAKE LIFTED"
Event Counter label -DBSS02
Event Log label - BRK NOT LFTD
Fault Code LEDs lit - 1, 2, 3, 4 , 5, 6 flashing (binary 63)
In response to a demand, MCSS has proceeded to Motion Logic State (MLS 5) LIFT BRAKE, this message is
sent to the DBSS Simultaneously a timer, MLS5 TIMEOUT, is started in MCSS this allows a waiting time for the
DBSS to send a response message BRAKE LIFTED which indicates that pre-torque current has been applied to
the armature and the brake profile has been run. If the MLS5 TIMEOUT timer times out for the MLS5 RETRY
MAX a DBSS02 fault is logged.

Page 24 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

TIP 31.4-12 - MCSS Troubleshooting Guide


2. Use the Service Tool DBSS, MONITOR, ELEVATOR CONSTANTS, to verify 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 RATE 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.
3. Use the Service Tool 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 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.
Motion Faults
MOTN00 - EEPROM JUMPER - EEPROM SWITCH
Event Counter label - MOTN00
Event Log label - EEPROM JUMPER
Fault Code LEDs lit - 1, and 6 (binary 33)
Motion was attempted with MCSS dipswitch segment 1 in the ENABLE position. Dipswitch segment 1 must be in
the DISABLE position to allow motion. All motion is inhibited with the dipswitch in the ENABLE position, and all
writes to the EEPROM are inhibited in the DISABLE position.
1. If this fault occurs and dipswitch segment 1 in the DISABLE position replace the MCSS-A board.
MOTN01 - DBSS FAULT - DBSS FAULT
Event Counter label - MOTN01
Event Log label - DBSS FAULT
Fault Code LEDs lit - 2, and 6 (binary 34)
MCSS has received either a DRIVE FAULT or a STOP AND SHUTDOWN message from the DBSS. The
message sent can be determined by checking the event log of DBSS messages, a DBSS00 message indicates
DRIVE FAULT, while a DBSS03 message indicates STOP AND SHUTDOWN.
1. Use the Service Tool MCSS, TEST, EVENT COUNTER, RAM COUNTER, DBSS, (M, 2, 2, 3, 3) to verify the
time since occurrence for DBSS00 or DBSS03 and the time since occurrence for MOTN01. See MCSS
Service Tool Users manual TIP 31.4-1 for further information.
2. If the time since occurrence agrees between MTON01 and DBSS03:
A. Check the DBSS theremogards for an OVERTEMPERATURE condition. Thermoguards are normally closed
contacts which OPEN under over temperature conditions. DBSS Thermoguards are located on the Silicon
Controlled Rectifier (SCR) rack, on the Motor Field and Brake Controller back plate mounting assembly, and
in the windings of the Input Power Transformer (1PT) in a Direct Drive or on the heat sink assembly of the
Power Converter Module (PCM) and in the windings of transformer TRF1 in a Ward Leonard drive.

Page 26 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

TIP 31.4-12 - MCSS Troubleshooting Guide

MOTN03 - BAD RTR STATE - INVALID READY TO RUN STATE


Event Counter label - MOTN03
Event Log Label - BAD RTR STATE
Fault Code LEDs lit 4, and 6 (binary 36)
The MCSS has determined that the READY TO RUN STATE sent from the DBSS via the RS422 communications
line is inconsistent with the current MCSS Motion Logic State (MLS). This fault will return the Motion Logic State
to SHUTDOWN (0) and then retry the start.
1. Observe the Motion Logic State LEDs on the front of the MCSS-A card. These LEDs are a binary count of the
greater than 10 the READY TO RUN LED on the DBSS control card should be lit.
2. If the MLS is equal or greater than 4 and less than or equal to 10 the READY TO RUN LED on the DBSS
Control Card should be lit.
MOTN04 - BAD DBD STATE - INVALID DRIVE AND BRAKE DISCONNECT STATE
Event Counter label - MOTN04
Event Log label - BAD DBD STATE
Fault Code LEDs lit - 1, 4, and 6 (binary 37)
The MCSS has determined that the DRIVE AND BRAKE DISCONNECT discrete signal sent from the DBSS is
inconsistent with the current MCSS Motion Logic State (MLS). This fault will return the Motion Logic State (MLS)
to 0 SHUTDOWN and then retry the start.
1. Observe the Motion Logic State LEDs on the front of the MCSS-A card. These LEDs are a binary count of the
Motion Logic State (MLS).
2. If the MLS is less than 11 or greater than 3, use the Service Tool MCSS, MONITOR, DISCRETE INPUTS (M,
2, 1, 2). Verify the DRIVE AND BRAKE DISCONNECT is in lower case letters (dbdc).
3. If the MLS is equal or greater than 11 and less than or equal to 3, use the Service Tool MCSS, MONITOR,
DISCRETE INPUTS, to verify the DRIVE AND BRAKE DISCONNECT is in upper case letters (DBDC).
MOTN05 - BRAKE TIMEOUT - BRAKE LIFTED TIMED EXCEEDED
Event Counter label - MOTN05
Event Log label - BRAKE TIMEOUT
Fault Code LEDs lit - 2, 4, and 6 (binary 38)
The MCSS has determined that the BRAKE LIFTED signal sent from the DBSS via the RS422 communications
line has indicated "LIFTED" in a non manual mode for more than 3 minutes. This fault will return the Motion Logic
State (MLS) to SHUTDOWN (0) and then retry the start.
1. Verify that when the car is at rest the BRAKE LIFTED LED on the DBSS Control Card is extinguished.

Page 28 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide


MOTN06 - GSMON TIMEOUT - GATE SWITCH MONITOR TIMEOUT
Event Counter label - MOTN06
Event Log label - GSMON TIMEOUT
Fault Code LEDs lit - 1, 2, 3 and 6 (binary 39)
MCSS has determined that the GATE SWITCH MONITOR (GS), a discrete signal from the GS1 contact in the
DCSS to MCSS-B plug J6-2, has not gone high within 30 seconds of the Door Fully Closed and/or Alternate Door
Fully Closed signals which are serially transmitted from the Door Interface Sub System (DISS) via the RS422 link
to the top of the car. This fault will return the Motion Logic State (MLS) to SHUTDOWN (0) and retry the start.
1. Use the Service Tool MCSS, MONITOR, STATES/COMMANDS (M, 2, 1, 1) to command the Front Doors
and/or Alternate Doors to close. Door Fully Closed (][ ][ ) status is indicated in the upper right hand corner of
the Service Tool display the first set of brackets is the front doors the second set is the alternate doors. See
MCSS Service Tool Users manual TIP 31.4-1 for further information.
2. Use the Service Tool MCSS, MONITOR DISCRETE INPUTS (M, 2, 1, 2). Verify that GATE SWITCH
MONITOR is in upper case letters (GSM). If the label is in lower case letters (gsm) check the wiring and the
GS1 cam setting in the Door Command Sub System (DCSS) control box on the top of the car. See MCSS
Service Tool Users manual TIP 31.4-1 for further information.
MOTN07 - POSINIT FAULT - POSITION INITIALIZATION FAILURE
Event Counter label - MOTN07
Event Log label - POSINIT FAULT
Fault Code LEDs lit - 4, and 6 (binary 40)
MCSS has tried, unsuccessfully, to initialize the Smart Primary Position Transducer (SPPT) by running the car at
Initialization Velocity for more than 30 seconds. The car will make a Timed Deceleration. Failure to initialize will
run the car at Creep Speed to the next landing in the down direction, unless the Initialization Direction (IDIR)
contact SS11 in the Stopping Switch is opened in which case the car will Recover in the up direction. The car will
continue at Recovery Speed until an Inner Door Zone and/or Alternate Inner Door Zone is sensed, stopping the
car and opening the appropriate door.
1. Verify that the SPPT coupling is tight and not broken. See SPPT installation document TIP 2.7.1-5.
2. Remove cover from the SPPT and verify the ribbon cables are properly connected. See SPPT installation
document TIP 2.7.1-5.
MOTN08 - POSITION FLT - POSITION FAULT
Event Counter label - MOTN08
Event Log label - POSITION FLT
Fault Code LEDs lit - 1, 4, and 6 (binary 41)
This fault can be generated by either the SPPT or the MCSS.
A. If the SPPT Software logic decides that it needs re-initialization it will send a value of all zeros (0) to the MCSS
on either the primary or secondary SPPT communications channel (PPTP or PPTS). The MCSS will then
force a timed deceleration and a reinitialization of the SPPT.

Page 29 of 30

TIP 31.4-12 - MCSS Troubleshooting Guide

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

Vous aimerez peut-être aussi