MCSS Troubleshooting Guide

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e

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.

Ap ri l 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 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 SYSTEM: E311, E311M, E411, E411M COMPONENT/SUB-SYS: MCSS SUB-ASSY/PARTS: Troubleshooting 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 Motion Command Sub System (MCSS). (MCSS). This document is based on the use of the following hardware and software. MCSS-A MICROPROCESSOR BOARD

AAA26800ABA001 AAA26800ABA0 01

MCSS-B INPUT/OUTPUT INPUT/OUTPUT BOARD

AAA26800ABB001

MCSS SOFTWARE

AAA30045AAE AAA30045 AAE

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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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 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 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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 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 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 Drive and Brake Sub System (DBSS). (DBSS). 4. MOTN Motion related events events which are monitored by the MCSS.

Event 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 Indicators The faults indicated in the Service Tool Event Counter are also i ndicated by the red Light Emitting Diode (LED) group located at the bottom edge of the MCSS-A microprocessor 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 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e Note: There is a priority for LED LED code display in cases where faults faults are declared in the same 40 millisecond frame. Priority list of LED Indication for Simultaneous Faults FC18

Highest

30 VOLTS

FC15

ACCESS ZONE

FC10

RECOVERS FAIL

FC09

SFTY CHN

FC11

HEARTBEAT

FC08

SPD RLYS

FC07

SENSORS

FC06

UX, DX RLYS

FC05

DRV TRCTN LOS

FC04

VEL TRKNG ERR

FC20

DIR TST FAULT

FC16

NTSD TBL

FC03

NTSD OVERSPD

FC19

NTSD MALFUNC

FC02

LINE OVERSPED OVERSPED

FC14

DOOR OPEN

FC13

BYPASS DROP

FC01

DOOR ZONE BYP

FC12

Lowest

E STOP SWITCH

FC17 power up onl y ERPM CHKSUM FC63 PRO required

DRIVE FAULTS

The following faults have the highest priority. FC25

EEPROM JUMPER

FC26

DBSS FAULTS

FC27

BAD BRK STATE

FC28

BAD RTR STATE

FC29

BAD DBD STATE

FC30

BRAKE TIMEOUT

FC31

GSMON TIMEOUT

FC32

POSINIT FAULT

MCSS MCSS Event Codes

Page 4 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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 TIME-OUT = 300 milliseconds): This is located in the COMMUNICATIONS COMMUNICATIONS TIMING PARAMETERS of th e MCSS EEPROM SET UP. UP. 1. Verify that the OCSS board is up and running. running. OCSS board mounted LEDs 1 and 2 should be flashing. 2. Verify that the the MCSS is up and running. The MCSS-A board mounted Heartbeat Heartbeat (HRTB) (HRTB) LED should be flashing. 3. Check the MCSS 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 (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 of hardware interrupts from from the Dual User Asynchronous Asynchronous Receive and Transmit (DUART) communication controller. 1. Power on Reset Reset (POR) the MCSS-A board this provides a DUART hardware reset. 2. Replace the MCSS-A microprocessor card. COMM02- DBSS RCV ERR - DB SS 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e MCSS EEPROM SET UP. 1. Verify that the DBSS DBSS board is up and running. DBSS operation operation can be verified by plugging the Service Tool directly into the drive. 2. Verify that the the MCSS is up and running. The MCSS-A board mounted Heartbeat Heartbeat (HRTB) (HRTB) LED should be flashing. 3. Check the MCSS MCSS communications wiring to and from the DBSS. DBSS. Check that connector connector P7 t the MCSS board and 3TB at the DBSS board are properly connected. 4. Check that the shielding, is properly properly grounded ( one end only ), DBSS DBSS transmit to 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 DBSS XMIT ERR - DBSS TRANSMIT ERROR ERROR Event Counter label - COMM03 Event Log label - DBSS XMIT ERR DBSS communications LED flashing. The MCSS RAM transmission buffer 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 MCSS-A board this provides provides a DUART hardware 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 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 Heartbeat (HRTB) LED Should be flashing. 3. Check the MCSS communications wiring to and from from the DCSS. Check that MCSS MCSS board connector P7 and DISS board connector P2 are properly connected. 4. Check that the shielding is properly grounded grounded ( one end only) at the car controller ground bus.

Page 6 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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 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) (POR) the MCSS-A MCSS-A board this this provides a DUART DUART hardware 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 CHANNEL within the 5 100 ms time-out periods. SPPTP COMM_TIME COMM_TIME =20 milliseconds, this is located in the COMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP. 1. Verify that the 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 the MCSS is up and running. The MCSS-A board mounted Heartbeat Heartbeat (HRTB) (HRTB) LED should be flashing. 3. Check the MCSS MCSS communications wiring to and from the SPPT. SPPT. Check that MCSS MCSS board connector connector P6 and SPPT assembly 25 pin "D" connector are are properly connected. 4. Check that the shielding is properly grounded ( one end only) at the MCSS 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e The MCSS RAM transmission buffer for for the SPPT PRIMARY 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) (POR) The MCSS-A MCSS-A board this provides a DUART DUART hardware reset. 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 SECONDARY CHANNEL within the time-out period. SPPTS_COMM_TIME SPPTS_COMM_TIME = 20 milliseconds, this is located in the COMMUNICATIONS COMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP. 1. Verify that the 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 MCSS is up and running. The MCSS-A MCSS-A board mounted Heartbeat (HRTB) LED should be flashing. 3. Check the MCSS MCSS communications wiring to and from the SPPT. SPPT. Check that MCSS MCSS board connector 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 for the SPPT SECONDARY SECONDARY communications channel has overflowed. 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 MCSS-A board this provides provides a DUART hardware hardware reset. 2. Replace the MCSS-A microprocessor card.

Page 8 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e COMM10 - E4RSS RCV ERR - EMERGENCY RESCUE 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 EMERGENCY RESCUE SUB SYSTEM (JERO) (JERO) or the DCSSA (double deck) channel within the time-out period. period. DCSSA COMM_TIME COMM_TIME = 300 milliseconds, this is located in the COMMUNICATIONS COMMUNICATIONS TIMING PARAMETERS PARAMETERS of the MCSS EEPROM SET UP. 1. Verify that the JERO/DCSSA JERO/DCSSA board is up and running. 2. Verify that the the MCSS is up and running. The MCSS-A board mounted Heartbeat Heartbeat (HRTB) (HRTB) LED should be flashing. 3. Check the MCSS communications communications wiring to and from the JERO/DCSSA. JERO/DCSSA. Check that MCSS board 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 JERO/DSSA board. 6. Replace the MCSS-A board. COMM11 - EERS XMIT ERR - EMERGENCY RESCUE 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 EMERGENCY RESCUE SUB SYSTEM (JERO) or DCSSA (Double Deck) communications channel has has overflowed. This is usually caused by the absence of hardware hardware interrupts from the Dual User Asynchronous Receive and Transmit (DUART) communication controller. 1. Power On Reset (POR) the MCSS-A MCSS-A board this provides provides a DUART hardware hardware reset. 2. Replace the MCSS-A microprocessor card. Safety Group SFTY01 - DOOR ZONE ZONE BYP - DOOR ZONE 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


1. Access the Service Service Tool function, MCSS, MONITOR, MONITOR, DISCRETE 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 for further information. If this test is successful go directly to step 5. 2. Use a volt meter to check for 30 VDC VDC at relay contacts contacts DZ-33 and ADZ-33. See Straight Line diagram. 3. Use a volt meter to check for 30 VDC VDC at MCSS-B MCSS-B plug P5-2 P5-2 when the DZ relay is pushed in. See Straight Line diagram. 4. Use a volt meter 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 Service Tool Function, MCSS, MCSS, TEST, OUTPUTS, (M, 2, 1, 2) DZ and / or ADZ. 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, (ACCESS, INSPECTION) INSPECTION) or Initialization (INIT) MODE. SFTY02-LINE OVERSPD -L INE 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 DATA CAPTURE, CAPTURE, DISPLAY VARIABLES, VARIABLES, (M, 2, 5, 1) to monitor the PRIMARY CAR CAR VELOCITY and the DICTATED DICTATED VELOCITY during a normal full speed run. Neither parameter should exceed the CONTRACT CONTRACT VELOCITY as set iin n the CONTRACT/CODE section of the SET UP procedure. See MCSS Service Tool Users manual TIP 31.4-1 for further further information. 2. If the PRIMARY PRIMARY CAR VELOCITY VELOCITY is greater greater than the contract velocity velocity check the value of SPPT SPPT POS SCALER SCALER and SPPT VEL SCALER with the POSITION/VELOCITY section of the MCSS, SET UP procedure. SPPT POS SCALER SCALER must equal 394, and SPPT VEL 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 SET UP, RIDE QUALITY, (M, (M, 2,3,2) to verify the values of CONTRACT ACCEL, ACCEL, CONTRACT JERK, AND 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 profile values are correct and the DICTATED DICTATED VELOCITY VELOCITY is greater than the CONTRACT CONTRACT VELOCITY replace the MCSS-A microprocessor board. 5. Access the Service Tool Function, DBSS, MONITOR, MONITOR, DRIVE DRIVE DATA, (M, (M, 4, 1, 6) to monitor SPEED REFERENCE REFERENCE (SPD REF) and SPEED SPEED FEEDBACK 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 6. If the SPEED SPEED FEEDBACK FEEDBACK is incorrect check the TACH COUNTS, COUNTS, RPM, and RATED RATED SPEED SPEED under ELEVATOR CONSTANTS CONSTANTS in the DBSS. 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 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 Service Tool Function, MCSS MCSS SET UP, RIDE RIDE QUALITY, QUALITY, (M, 2, 3, 2) DECEL DECEL RATIO. RATIO. Verify that the value, A percent of CONTRACT CONTRACT ACCEL does not exceed 1500 mm/s. Also verify that none of the 7 ALT PROFILE DEC rates rates exceed 1500 mm/s2. See MCSS Service Tool Users manual TIP 31.4-1 for further further information. 2. Access the Service Tool Function, MCSS, DATA DATA CAPTURE, DISPLAY DISPLAY VARIBALES, VARIBALES, (M, 2, 5, 1) PRIMARY CAR POS and SECONDARY SECONDARY POS. 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 incorrect Access the Service Service Tool Function, MCSS, SET UP, POS/VEL POS/VEL (M, 2, 3, 4) and verify that the val ue 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 further information. SFTY04 - VEL TRKNG ERR - VEL OCITY 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 VELOCITY has exceeded the value set in TRACKING ERR ERR VEL TOL in MCSS, SET UP, SAFETY PARAMETERS. PARAMETERS. If this occurs for 6 consecutive confirmation cycles, a Velocity Tracking Error is logged. 1.1. Access the Service Tool Function, Function, MCSS DATA DATA CAPTURE, (M, 2, 5, ) DISPLAY VARIABLE VARIABLE to compare the value of the DICTATED VELOCITY and PRIMARY CAR CAR VELOCITY. See MCSS Service Tool Users Manual TIP 31.4-1 for further information. 2.2. Access the Service Service Tool Function, MCSS, SET SET UP, SAFETY SAFETY PARAMETER PARAMETER (m, (m, 2, 3, 5). Check the value of TRCK ERR VEL TOL. The value should be 6. See MCSS Service Service Tool Users manual TIP 31.4-1 for further information. 3.3. Access the Service Service Tool Function, MCSS, SET SET UP, SAFETY SAFETY PARAMETERS PARAMETERS (M, 2, 3, 4). Check the value of VL TRK ERR CT MAX. The value should be 6. See MCSS Service Tool Users Users manual TIP 31.4-1 for further information.

Page 11 of 30


4.4. Access the Service Service Tool Function, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETER PARAMETER (M, 2, 3, 4). Check the value of SPPT VEL VEL SCALER. The value should be 67295. See MCSS Service Service Tool Users manual TIP 31.41 for further information. 5.5. Access the Service Tool Function, DBSS, MONITOR, MONITOR, DRIVE DRIVE DATA (m, (m, 4, 1, 6) to monitor SPEED REF in mm/sec (Dictated Velocity form MCSS) and SPEED FEEDBACK FEEDBACK in mm/sec. If the SPEED, RPM, and TACH CNTS. See MCSS Service Tool Users manual TIP 31.2-1 for for further information 6.6. If SPEED SPEED REF is incorrect. Access the Service Service Tool Function, MCSS, SET SET UP, RIDE RIDE QUALITY QUALITY PARAMETER (M, 2, 3, 2). Verify that CONTRAT VELOCITY VELOCITY IS set correctly. 7.7. Access the Service Service Tool Function, DBSS, DBSS, MONITOR, MONITOR, STABILITY, STABILITY, (M, (M, 4, 1, 2). Verify that the GAIN is properly set. Typical GAIN settings settings range from 8 to 13. Low gain settings cause tracking errors errors while high gain setting cause oscillation. See MCSS Service Tool Users Manual TIP 31.2-1 31.2-1 for further information. 8.SFTY058.SFTY05- DRV TRCTN ERR - DRIVE TRACTION L OSS 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 channe l velocity, PRIMARY CAR VELOCITY, and the PVT velocity, MACHINE CAR VELOCITY, 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 Service Tool Function, MCSS, SET SET UP, SAFETY SAFETY PARAMETERS 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 31.4-1 for further information. 14.2. Access the Service Service Tool Function, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS 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 Service Tool Function, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS 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 calcul ations based on drive sheave size. See MCSS Service Tool Users manual TIP 31.4-1 for further further information. 16.4. Access the Service Tool Function, Function, MCSS, DATA DATA CAPTURE, CAPTURE, DISPLAY DISPLAY VARIBALES VARIBALES (M, 2, 5, 1) to compare the PRIMARY CAR VELOCITY VELOCITY to the MACHINE CAR VELOCITY. VELOCITY. Both values should have the same sign, + for up and - for down. The MACHINE CAR VELOCITY 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 further information. 17.5. If the MACHINE MACHINE CAR VELOCITY VELOCITY is the wrong wrong sign check the DBSS to MCSS (PVT) (PVT) communications wiring. 18.6. If the PRIMARY PRIMARY CAR VELOCITY VELOCITY has the wrong sign check the Rotation Rotation orientation DIP SWITCH SWITCH in the SPPT. See SPPT document TIP 2.7.1-5. 19.SFTY0619.SFTY06- UX, DX RLYS - UP/DOWN RELAYS 20.Event Counter label - SFTY06 21.Event Log label- UX, DX RLYS

Page 12 of 30


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 monitored by the relay sense inputs on the MCSS-B MCSS-B I/O board. 25.Or 26.B. The direction relay picked is wrong when 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, Function, MCSS, DATA DATA CAPTURE, CAPTURE, DISPLAY DISPLAY VARIABLE, VARIABLE, (M, 2, 5, 1) PRIMARY CAR CAR VELOCITY, to 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 Service Tool Function, MCSS, SET SET UP, SAFETY SAFETY PARAMETERS, PARAMETERS, (M, 2, 3, 5). Check that the value of UXDX CHECK percent equals 60, and UX & DX CT MAX MAX equals 6. See MCSS Service Service Tool Users manual TIP 31.4-1 for further information. 30.3. Use a volt meter to check for 30 VDC 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, MONITOR, DISCRETE DISCRETE INPUTS, (M, 2, 1, 2) UX. 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. board. Also access the Service Tool Function, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS, (M, 2, 1, 2) DX. 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 DISCRETE OUTPUTS, OUTPUTS, (M, (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 further information. 34)7. Access the Service Tool Function, MCSS, TEST, DISCRETE DISCRETE OUTPUTS, OUTPUTS, (M, (M, 2, 2, 1) DX, DX, to issue MCSS commands to pick the D relay. See MCSS Service Tool Users manual TIP 31.4-1 for further further information. 35)SFTY07-SENSORS-DOOR 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 i n the ON state instead of the OFF state. This test is performed in a window created by the SENSOR CHK CHK BEGIN DIST< DIST< normally 2000 millimeters and SENSOR CHK CHK END, DIST, DIST, normally 600 millimeters. These distances are taken from the SPPT

Page 13 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e Primary channel during the approach 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, SETUP, SAFETY PARAMETERS PARAMETERS (M,2,3, 5). 5). Check that SENS SENS CHK END-DIST END-DIST is equal to 600. See MCSS Service Tool Users manual TIP 31.4-1 31.4-1 for further information. 2. Access the Service Service Tool Function, MCSS, MCSS, SETUP, SETUP, SAFETY SAFETY PARAMETERS PARAMETERS (m< (m< 2, 3, 4). Check that SENS CHK BEG-DIS 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 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 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 DISCRETE INPUTS (m, 2, 1, 2) and verify that al l Door Zone inputs are OFF. Lower case letters (fid1, fodz, fid2, aid1, aodz, aid2). See MCSS Service Tool users manual TIP 31.4-1 31.4-1 for further information. 5. Repair wiring wiring or replace sensors sensors as necessary, SFTY08 - SC RLY - SPEED RELA YS Event Counter label - SFTY08 Event Log label - SC RLY Fault Code LED lit - 4 (bi nary 8) This fault can be generated in two possible ways: A. MCSS determines that that the Speed Check (SC) (SC) relay feed back contacts 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 CODE LEVELING VELOCITY, multiplied by the NORMAL_VEL_TOL_PERCENT, 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 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 30 VDC at P5 - 1 of the MCSS-B MCSS-B board. Also access the Service Tool Function, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS, (M, (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 displ ay should be in lower case letters (sc). See MCSS Service Tool Users manual TIP 31.4-1 for further information. 3. Access the Service Service Tool Function, MCSS, MCSS, SETUP, SETUP, CONTRACT/CODE 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 further information.

Page 14 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 4. Access the Service Service Tool Function, MCSS, MCSS, SETUP, SETUP, SAFETY SAFETY PARAMETERS PARAMETERS (m, (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 Service Tool Users manual TIP 31.4-1 for further information. 5. Access the Service Tool Function, MCSS, SETUP, SETUP, POS/VEL POS/VEL PARAMETERS PARAMETERS (M, 2, 3, 4) to verify SPPT SPPT POS SCALER is equal to 394 for a 1524 mm circumference (20 inch diameter) SPPT 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 discrete independent speed check input between the SPPT and the MCSS-B MCSS-B phoenix connector connector J4-5. The SC relay 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 DISCRETE INPUTS INPUTS (m, 2, 1, 2) and verify that with with the J4-5 wire removed the speed Check Drive Check (SCDC) (SCDC) input is low, (lower case letters scdc). See Service Tool Users manual TIP 31.4-1 for further information. 8. Reconnect the wire wire from the the SPPT to the MCSS-B MCSS-B Phoenix connector connector J4-5. The SC relay should pick up. 9…Access the Service Tool Function, MCSS, MONITOR< DISCRETE INPUTS INPUTS (M, 2,1, 2) and verify that with the (SCDC) input is high, (upper case letters SCDC). SCDC). See MCSS Service Tool Users manual TIP 31.4-1 for for further information. 10. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (m, (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 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 SPPT processor board. 12. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (M, (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 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 Controller Inspection Panel. Verify that the SC relay drops drops out. If the SC relay remains energized, at 800 mm/s, measure the voltage between MCSS-B MCSS-B J4-5 (+) to J4-6 (-). If this voltage is 5 VDC replace the SPPT SPPT Processor board. If the voltage is 0.0 VDC VDC replace the MCSS-B MCSS-B board. See MCSS Service Tool Users manual TIP 31.4-1 for further information. 14. Remove all temporary jumpers and reset INSPECTION INSPECTION VELOCITY VELOCITY equal to 400 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for further information. SFTY09- SFTY CHN CHN - SAFETY CHAIN B ROKEN Event Counter label - SFTY09 Event Log label - SFTY CHN Fault Code LEDs lit - 1 and 4 (binary 9) MCSS has determined that SAFEOUT SAFEOUT is active, EES relay driver (SAFEOUT) (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 will be declared each time the car is placed on Access or Inspection operation 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 1. Operation of a safety switch switch is indicated if SCS1 and SCS2 remain high when when SAFEIN goes low. low. 2. A failure of one of the following: FGDS1, FGDS2, AGDS1, AGDS1, or AGDS2, AGDS2, is indicated by: The DZ relay status indicates that the DZ and/or the ADZ relay i s not picked, and the SC relay status indicates that the SC relay is picked, and the SCS1 and/or the SCS2 sense sense point is low. All relay status can be checked by accessing the Service Tool Function, MCSS, MONITOR, DISCRETE 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 or gate switch is indicated if the DZ relay status indicates that the DZ and/or or the the ADZ relay is not picked, the the FGDS and/or AGDS 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 OUTPUTS (M, 2, 1, 2). See MCSS Service Tool Users manual TIP 31.4-1 for further information. SFTY10 - RECOVERS FAIL - RECOVERY ATTEMPTS 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). (5). If this counter exceeds the value in the label, MAX RECOVER TRIES, TRIES, a Safety Fault 10 is declared. This fault requires a Power On Reset (POR) of the MCSS. 1. Access the Service Service Tool Function, MCSS, MCSS, SET SET UP, RIDE RIDE QUALITY QUALITY PARAMETERS PARAMETERS (M, (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 31.4-1 for further information. 2. Access the Service Service Tool Function, MCSS, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS PARAMETERS (M, 2, 3, 4). Verify that the value of RELEVEL ZONE DISTANCE DISTANCE is equal to 76 mm. See MCSS Service Tool Users manual TIP 31.4-1 31.4-1 for further information. 3…Access the Service Tool Function, MCSS, SET UP , SAFETY PARAMETERS PARAMETERS (M, 2, 3, 5). Verify that the value of MAX RECOVER RECOVER TRIES is equal to 5. See MCSS Service Tool Users manual TIP 31.4-1 31.4-1 for further information. 4. Place the car on inspection and move move the car more than 76 mm away from from the landing. Take the car off of inspection. The car should recover to the the floor. If the recovery fails trouble shoot the system to find 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) AGDS) relays. If any of these checks fail a SFTY11 fault is declared.

Page 16 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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 Service Tool Function, MCSS, MCSS, SET SET UP, SAFETY SAFETY PARAMETERS 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 Service Tool Function, MCSS, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS, INPUTS, DBDC. DBDC. Verify that with the "CIO" "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 further information. 3. Access the Service Tool Function, MCSS, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS (m, 2, 1,2) Verify Verify that with the 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 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 Service Tool Function, MCSS, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS 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 i n the STOP position. See MCSS Service Tool Users manual TIP 31.4-1 31.4-1 for further information. 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 brought up to Motion Logic State (MLS) 6, Low Level Phase Plane, the MCSS MCSS performs a Door Zone Bypass Drop Test. During this test the Door Zone (DZ) and Alternate Door Zone (ADZ) (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 Service Tool Function, MCSS, MCSS, SET SET UP, SAFETY SAFETY PARAMETERS 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 31.4-1 for further information. 2. Access the Service Service Tool Function, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS 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 further information.

Page 17 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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 Service Tool Function, MCSS, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS 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 LEVELING ZN DISTANCE DISTANCE is set to Service Tool Users manual TIP 31.4-1 for further information. 2. Access the Service Service Tool Function, MCSS MCSS SET SET UP, MOTION MOTION CONTROL CONTROL PARAMETERS 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 31.4-1 for further information. 3. Use the Car Controller Controller Inspection Panel to place the car on inspection. Access the Service Tool Function, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS 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 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 Service Tool Function, MCSS, MCSS, MONITOR, MONITOR, STATES/COMMA STATES/COMMANDS NDS (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 - A CCESS 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


Zone 3, a 500 mil limeter 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 mil limeter 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 Service Tool Function MCSS. MCSS. SET SET UP, CONTRACT/CO CONTRACT/CODE DE PARAMETERS PARAMETERS (M, 2, 3, 1). Verify that ACCESS ZONE ZONE CHECKING CHECKING is set to 255 (enabled ). See MCSS Service Tool Users manual TIP 31.4-1 31.4-1 for further information. 3. Access the Service Service Tool Function, MCSS, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS PARAMETERS (M, 2, 3, 4). Verify that ACCESS ZONE ZONE LENGTH is set to the dimension necessary to to bring the crosshead level with the top landing sill. This dimension is in millimeters. See MCSS Service Tool Users Users manual TIP 31.4-1 for further further information. 4. Access the Service Service Tool Function, MCSS, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS PARAMETERS (M, 2, 3, 4). Verify that SPPT POS SCALER is set to 394 for a 1524 mm circumference circumference SPPT drive sheave. See MCSS Service Tool Users manual TIP 31.4-1 for further information. SFTY16- NTSD NTSD TBL - NTSD TABL E 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 Random Access Memory (RAM) (RAM) table is built. If the checksum calculated at power does not match the dynamical ly calculated checksum for the NTSD table a fault is declared. This fault indicates corruption of data in the microprocessor Random Access Memory 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 corrupted in the EPROM. EPROM. Replace the MCSS-A EPROMS.

Page 19 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 2. This fault indicates corruption of data in the microprocessor microprocessor Random Access Memory (RAM). Replace the MCSS-A microprocessor card. SFTY18- 30 VOLTS - THIRTY VOLT FAIL URE Event Counter label - SFTY18 Event Log label - 30 VOLTS Fault Code LEDs lit - 2 a nd 5 (binary 18) MCSS hardware samples the 30 VDC supply for the Door 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 Service Tool Function, MCSS, MCSS, SET SET UP, SAFETY SAFETY PARAMETERS PARAMETERS (M, 2, 3, 5). Verify THIRTY VOLT TIMEOUT, and THIRTY THIRTY VOLT RECOVER 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 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 SFTY19-NTSD MAL FUNC- NTSD MAL FUNCTION Event Counter label - SFTY19 Event Log label - NTSD MALFUNC Fault Code LEDs lit - 1, 2, and 5 (binary 19) Normal Terminal Slow Down (NTSD) (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 Service Tool Function, MCSS, MCSS, SET SET UP, RIDE RIDE QUALITY QUALITY (M, 2, 3, 2). Verify that INIT VELOCITY VELOCITY equals 600 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for further further information. 2. Access the Service Service Tool Function, MCSS, MCSS, SET SET UP, POS/VEL POS/VEL PARAMETERS PARAMETERS (M, 2, 3, 4). Verify that SPPT 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 further information. 3. Access the Service Service Tool Function, MCSS, MCSS, DATA DATA CAPTURE, CAPTURE, DISPLAY DISPLAY VARIABLES VARIABLES (M, (M, 2, 5, 1). Verify that SECONDARY SECONDARY POS and SEC CAR VEL 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


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, TEST, DISCRETE 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 for further information. 2. Access the Service Tool Function, MCSS, TEST, TEST, DISCRETE, DISCRETE, OUTPUTS (m, 2, 2, 1), to command DX to 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 Service Tool Function, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS INPUTS (M, 2, 1, 2). Verify that when the U relay is pushed i n 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 for further information. 4. Access the Service Service Tool Function, MCSS, MCSS, MONITOR MONITOR DISCRETE DISCRETE INPUTS 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 further information. 5. Access the Service Service Tool Function, MCSS, MONITOR, MONITOR, DISCRETE DISCRETE INPUTS 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 further information. SFTY21SFTY21- B44 RELAY FAULT - B 44 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 ENABLED (255). 1. Use a volt meter meter to check for 30 VDFC VDFC at B44 - 14 relay contact. 2. Push in the B44 B44 relay and check check for 30 VDC at P5 - 7 of the MCSS-b board. Also access the Service Tool Function, MCSS, MONITOR MONITOR DISCRETE 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, TEST, DISCRETE OUTPUTS, J7-7 J7-7 to issue the MCSS commands to pick/drop the B44 relay. See the MCSS Service Tool Users Manual for further information. information. SFTY22-B44 TRIPPED - B 44 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 1. Use the Service Tool Function, MCSS, SETUP, SETUP, SAFETY PARAMETERS, PARAMETERS, to verify the setting of B44 TRIP SPEED is 50 millimeters per second. 2. Use the Service Service Tool Function, MCSS, SETUP, SETUP, POS/VEL POS/VEL PARAMETERS. 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 DATA CAPTURE, DISPLAY DISPLAY VARIABLE, VARIABLE, MCHN VEL VEL (MACHINE CAR 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, TEST, DISCRETE OUTPUTS, B44 B44 to issue the MCSS MCSS commands to pick/drop the B44 relay. See the MCSS Service Tool Users Manual for further information. 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 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 ANSI A17.1 or by the CAN/CSA-B44 CAN/CSA-B44 Safety Codes. 1. Use a volt meter to check for 30 VDC VDC at ETSD ETSD - XX relay contact. 2. Push in the ETSD ETSD relay and check for 30 VDC at P5-7 of the MCSS-b board. board. Also access the Service Tool Function, MCSS, MONITOR MONITOR DISCRETE 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, TEST, DISCRETE OUTPUTS, J7-7 J7-7 to issue the MCSS commands to pick/drop the ETSD relay. See the MCSS Service Tool Users Manual Manual for further information. SFTY24 - ICES CHK FAIL - IN CAR EMERGECNY STOP SWITCH SWITCH CHECK FAIL URE 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, SETUP, CONTRACT/CODE, CONTRACT/CODE, CIO RELAY OPTION to verify verify that this option is enabled (255). 2. Push in the CIO CIO relay and check for 30 VDC at J4-1 of the MCSS-b board. Also access the Service Tool Function, MCSS, MONITOR MONITOR DISCRETE INPUTS, ICES. 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 3. Access the Service Tool Function, MCSS, TEST, TEST, DISCRETE DISCRETE OUTPUTS, CIO to issue the MCSS MCSS commands to pick/drop the CIO relay. See the MCSS Service Tool Users Manual for further information. 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 a nd 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, SETUP, CONTRACT/CODE, 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 the MCSS-b board. Also access the Service Tool Function, MCSS, MONITOR MONITOR DISCRETE DISCRETE INPUTS, INA. 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, TEST, DISCRETE DISCRETE OUTPUTS, CIO to issue the MCSS MCSS commands to pick/drop the CIO relay. See the MCSS Service Tool Users Manual for further information. 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 solenoid’s, thus checking their continuity at the same time. 1. Use the Service Tool Function, MCSS, SETUP, SETUP, CONTRACT/CODE, 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 FGDS2 relays drop out. Also verify that the AGDS1 and AGDS2 relays, if provided, drop out. 3. Access the Service Service Tool Function, MCSS, MONITOR MONITOR DISCRETE DISCRETE INPUTS, INPUTS, FGDS 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, TEST, DISCRETE OUTPUTS, CIO CIO to issue the MCSS MCSS commands to pick/drop the CIO relay. See the MCSS Service Tool Users Manual for further 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-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 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), 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 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 Reset (POR) of the MCSS board is required to clear this fault. Access the Service Tool Function, MCSS, SET SET UP, MOTION MOTION PARAMETERS PARAMETERS (M, 2, 3, 7). Verify that MLS3 RETRY COUNT COUNT MAX is set to 3, and MLS3 TIMEOUT TIMEOUT is set to 1500 ms. See MCSS Service 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 Service Tool Function, DBSS, DBSS, MONITOR, MONITOR, DRIVE DRIVE DATA (M< 4, 1, 6). Verify that FIELD CURRENT is equal to FULL FIELD located in the FIELD CONSTANTS CONSTANTS branch of MONITOR. MONITOR. See DBSS Service Tool Users manual TIP 31.2-1 for further information. DBSS02- BRK NOT LFTD- TIMED TIMED OUT WAITING 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 the MLS5 RETRY MAX a DBSS02 fault is logged.

Page 24 of 30


A Power On Reset Reset (POR) of the MCSS board is required to clear this fault. 1. Access the Service Service Tool Function, MCSS, MCSS, SET SET UP, MOTION MOTION PARAMETERS PARAMETERS (m< 2, 3,7). 3,7). Verify that MLS5 RETRY COUNT 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 Service Tool Function, DBSS, DBSS, MONITOR, MONITOR, ELEVATOR ELEVATOR CONSTANTS 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.231.21 for further information. 3. Access the Service Service Tool Function, DBSS, DBSS, TEST, TEST, DISPLAY DISPLAY LIMIT SWITCH. SWITCH. 4. If display indicates BRAKE BRAKE SWITCH SWITCH IS IN, observe that the BRAKE LIFTED indicator LED 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 BRAKE SWITCH SWITCH IS NOT IN, observe that the BRAKE LIFTED LIFTED indicator LED LED 13 is lit. If LED 13 is not lit use the Service Tool DBSS, MONITOR, MONITOR, ELEVATOR CONSTANTS 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 State (MLS 10) DROP DROP BRAKE. BRAKE. The LIFT BRAKE command 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 board is required to clear this fault. This is indicated by all 6 fault code LEDs flashing. 1. Use the Service Tool MCSS, MCSS, SET UP, UP, MOTION PARAMETERS PARAMETERS,, to verify DROP_BRK_TIMEOU DROP_BRK_TIMEOUT T equals 10000 milliseconds.

Page 25 of 30

TIP 31.4-1 31.4-12 2 - MCSS MCSS Troub leshoo tin g Guid Guide e 2. Use the Service Tool DBSS, DBSS, MONITOR, MONITOR, ELEVATOR ELEVATOR CONSTANTS, CONSTANTS, to verify BRK BRK HOLD AMP equals the current necessary to hold the brake up, BRK PICK AMP equals the current necessary to pi ck the brake, BRK UP RATE equals the length of time necessary to pi ck the brake fully, BRK DRP RATE equals the length of time necessary to drop the brake fully. 3. Use the Service Service Tool DBSS, TEST, DISPLAY DISPLAY LIMIT LIMIT SWITCH. 4. If display indicates BRAKE BRAKE SWITCH SWITCH IS IN, observe that the BRAKE LIFTED indicator LED 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 BRAKE SWITCH SWITCH IS NOT IN, observe that the BRAKE LIFTED LIFTED indicator LED LED 13 is lit. If LED 13 is not lit use the Service Tool DBSS, MONITOR, MONITOR, ELEVATOR CONSTANTS 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 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 DISABLE position replace the the MCSS-A board. 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 SHUTDOWN message from the DBSS. 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, MCSS, TEST, EVENT EVENT COUNTER, COUNTER, RAM COUNTER, COUNTER, DBSS, DBSS, (M, 2, 2, 3, 3) to verify verify the time since occurrence for DBSS00 or DBSS03 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 occurrence agrees between MTON01 and DBSS03: DBSS03: A. Check the DBSS theremogards for an OVERTEMPER OVERTEMPERATURE ATURE condition. Thermoguards are normally closed contacts which OPEN under over temperature temperature conditions. DBSS Thermoguards are located on the Silicon Controlled Rectifier (SCR) rack, on the Motor Field and Brake Controller back pl ate 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


B. For installations that do not have machine blowers. Check that the 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 switch is operating properly (contact closes when blower is running), and that the blower is operating properly. D. Use the Service Tool DBSS, TEST, TEST, DISPLAY FAULTS, FAULTS, (M, 4, 2, 2) to verify for the occurrences of a Motor Field Overcurrent condition. 3. If the time since occurrence occurrence agrees between MOTN01 MOTN01 and DBSS00: DBSS00: A. For a Direct Drive check the LEDs on the DBSS DBSS Control Card for the presents of a CPU FAULT, IST , LOW AC LINE, MOTOR MOTOR FIELD LOSS, LOSS, BLOWN DC FUSE, MOTOR FIELD OR BRAKE IST, TACH FAULT, FAULT, BRAKE OR LOOP CONTACTOR FUALT, or a SERIAL FAULT. B. For a Ward-Leonard check the LEDs on the DBSS Control Control Card for the presents of a CPU FAULT, MOTOR 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 MOTN02 - BAD B RK 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, flashing, of the MCSS board is required to clear this this fault. 1. Place the car in Inspection on the Car Controller 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 LIFTED LED lights when the brake picks. 2. Use the Service Tool DBSS, SET UP, UP, BRAKE BRAKE SW I/O is enable (equal to 255). A. If display indicates BRAKE BRAKE SW I/O is enabled (255), (255), observe that while attempting attempting motion the BRAKE BRAKE LIFTED indicator LED 13 in the DBSS DBSS is lit. If LED 13 is not lit check check Brake Switch circuit. 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 while attempting motion the BRAKE LIFTED LIFTED indicator LED 13 in the DBSS is lit. If LED 13 is not lit use the Service Tool DBSS, SET UP, UP, BRAKE PRAMS PRAMS (M, 4, 3, 2) to verify percent PICK UP equals 75 this states that if there 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, MCSS, SET UP, UP, MOTION PARAMETERS PARAMETERS (m, 2, 3, 7). Verify that INV BRK RTRY MA is set to 3. See MCSS Service Service Tool Users Manual T.I,P. T.I,P. 31.4-1 for further information.

Page 27 of 30


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). (MLS). This fault will return the Motion Logic State to SHUTDOWN (0) and then retry the start. 1. Observe the Motion Motion Logic State LEDs on the front of the 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 li t. 2. If the MLS is equal or greater than 4 and less than or equal to 10 the READY READY TO RUN LED on the DBSS 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 DISCONNECT discrete signal sent from the DBSS is inconsistent with the current MCSS Motion 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 Motion Logic State LEDs on the front of the 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, MCSS, MONITOR, DISCRETE INPUTS (M, (M, 2, 1, 2). Verify the DRIVE AND AND BRAKE DISCONNECT 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, MONITOR, DISCRETE INPUTS, to verify the DRIVE AND BRAKE DISCONNECT 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 manual mode for more than 3 minutes. This fault will return the Motion Motion Logic State (MLS) to SHUTDOWN (0) and then retry the start. 1. Verify that when the car is at rest the BRAKE BRAKE LIFTED LED on the DBSS DBSS Control Card Card is extinguished.

Page 28 of 30

TIP 31.4-12 - MCSS Troubleshoo tin g 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 FAUL T - POSITION INITIAL IZATION 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 Z one 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 FAUL T 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


B. If the MCSS determines an absolute difference between between the SPPT primary position value and the SPPT secondary position value greater than the val ue of POSITION ERROR TOLERANCE, TOLERANCE, 500 millimeters, it will then force a timed deceleration and a reinitialization of the SPPT. 1. Use the Service Tool Function MCSS, DATA DATA CAPTURE, DISPLAY DISPLAY VARIABLE, VARIABLE, to view the PRIMARY CAR POS and the SECONDARD SECONDARD CAR POS. POS. If either of these values is 0 the SPPT has forced the Position Fault. 2. Use the Service Tool Function MCSS,, DATA DATA CAPTURE, DISPLAY DISPLAY VARIABLE, VARIABLE, to view the PRIMARY PRIMARY CAR POS and the SECONDARY SECONDARY CAR POS. If the difference between these 2 values is greater greater than 500 (millimeters) the MCSS has forced the Position Fault. 3. Replace the SPPT microprocessor printed circuit circuit board. 4. Use the Service Service Tool Function MCSS, MCSS, SET SET UP, POS/VEL, POS POS ERR TOL to verify that the tolerance is set to 500 millimeters. 5. Replace the MCSS microprocessor printed circuit circuit board. MOTN09 - LOW AC LINE - LOW AC LINE Event Counter label - MOTN09 Event Log label - LOW AC LINE Fault Code LEDs 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 REDUCED CONTRACT JERK, and REDUCED CONTRACT VELOCITY, 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 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, MONITOR, DISCRETE 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

MCSS Troubleshooting Guide

Recommend Documents