MCSS Troubleshooting Guide

(1)

Unpublished Work - © Otis Elevator Company.

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 Any unauthorized reproduction, disclosure, or distribution of copies or content by any person of any portion of this work may be a violation ofviolation of Copyright Law of the United States of America.

Ap

Ap riri l 6, 1992l 6, 1992

TIP Revision History (Author to complete this section) TIP Revision History (Author to complete this section) Original

Original Author: Author: Paul Paul C. C. Hoppie Hoppie Original Date: Original Date: 04-06-1992 04-06-1992 Previous Previous TIP TIP # # (if (if applicable):applicable): Revision

Revision Author: Author: Revision Revision Date: Date: Reason Reason for for Revision:Revision: Revision

Revision Author: Author: Revision Revision Date: Date: Reason Reason for for Revision:Revision: This work and the information it contains

This work and the information it contains (collectively referred to as ‘Work’) are the (collectively referred to as ‘Work’) are the confidential property of theconfidential property of the Otis Elevator Company

Otis Elevator Company (‘Otis’). (‘Otis’). This Work is delivered on the express condition This Work is delivered on the express condition that: it will be used or rthat: it will be used or reproducedeproduced by Otis employees exclusively for, or on behalf

by Otis employees exclusively for, or on behalf of, Otis; it will not of, Otis; it will not be disclosed, reproduced, or distributed by or tobe disclosed, reproduced, or distributed by or to others, in whole or in part, without the

others, in whole or in part, without the prior written consent of Otis: and, it and prior written consent of Otis: and, it and any copies will be promptlyany copies will be promptly returned to Otis upon demand or upon termination of employment.

returned to Otis upon demand or upon termination of employment. REQUIRED READING:

REQUIRED READING: X

X Field Field Operations Operations ManagerManager X

X Maintenance Maintenance SupervisorSupervisor X

X Service Service Supt.Supt. X

X Construction Construction Supt.Supt. X

X Modernization Modernization Supt.Supt. X

X Field Field EngineerEngineer SYSTEM:

SYSTEM: E311, E311M, E411, E411ME311, E311M, E411, E411M

COMPONENT/SUB-SYS:

COMPONENT/SUB-SYS: MCSSMCSS

SUB-ASSY/PARTS:

SUB-ASSY/PARTS: TroubleshootingTroubleshooting

AUTHOR:

Paul C. Hoppie

---Description:

Description:

This manual is written to assist

This manual is written to assist the Adjuster an examiner in understanding and the Adjuster an examiner in understanding and trouble-shooting the Elevonictrouble-shooting the Elevonic Modular Control System (MCS) M

Modular Control System (MCS) Motion Command Sub System (MCotion Command Sub System (MCSS). SS). This document is based on the use ofThis document is based on the use of the following hardware and software.

the following hardware and software. MCSS-A

MCSS-A MICROPROCESSOR MICROPROCESSOR BOARD BOARD AAA26800ABA0AAA26800ABA00101 MCSS-B

MCSS-B INPUT/OUTPINPUT/OUTPUT UT BOARD BOARD AAA26800ABB001AAA26800ABB001

MCSS

MCSS SOFTWARE SOFTWARE AAA30045AAA30045AAEAAE

The software and hardware provides Event Counting, Event Logging, and

The software and hardware provides Event Counting, Event Logging, and Light Emitting Diode (LED) indications,Light Emitting Diode (LED) indications, in binary form, of the events and faults.

in binary form, of the events and faults. The Event Counter and Event Log are accessed through use of the OtisThe Event Counter and Event Log are accessed through use of the Otis Modular Control System (MCS) Service Tool

Modular Control System (MCS) Service Tool (P/N MT-120059).(P/N MT-120059). Event Counter Event Counter Event Log Event Log Led Indicators Led Indicators

(2)

Communications Fault Group Communications Fault Group

COMM00 - OCSS RCV ERR - OCSS RECEIVE ERROR COMM00 - OCSS RCV ERR - OCSS RECEIVE ERROR COMM01 - OCSS XMIT ERR - OCSS TRANSMIT ERROR COMM01 - OCSS XMIT ERR - OCSS TRANSMIT ERROR COMM02 - DBSS RCV ERR - DBSS RECEIVE ERROR COMM02 - DBSS RCV ERR - DBSS RECEIVE ERROR COMM03 - DBSS XMIT ERR - DBSS TRANSMIT ERROR COMM03 - DBSS XMIT ERR - DBSS TRANSMIT ERROR COMM04 - DCSS RCV ERR - DCSS RECEIVE ERROR COMM04 - DCSS RCV ERR - DCSS RECEIVE ERROR COMM05 - DCSS XMIT ERR - DCSS TRANSMIT ERROR COMM05 - DCSS XMIT ERR - DCSS TRANSMIT ERROR

COMM06 - PPTP RCV ERR - SPPT PRIMARY RECEIVE ERROR COMM06 - PPTP RCV ERR - SPPT PRIMARY RECEIVE ERROR COMM07 - PPTP XMIT ERR - SPPT PRIMARY TRANSMIT ERROR COMM07 - PPTP XMIT ERR - SPPT PRIMARY TRANSMIT ERROR COMM08 - PPTS RCV ERR - SPPT SECONDARY RECEIVE ERROR COMM08 - PPTS RCV ERR - SPPT SECONDARY RECEIVE ERROR COMM09 - PPTS XMIT ERR - SPPT SECONDARY TRANSMIT ERROR COMM09 - PPTS XMIT ERR - SPPT SECONDARY TRANSMIT ERROR

COMM10 - ERSS RCV ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA RECEIVE COMM10 - ERSS RCV ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA RECEIVE ERROR

ERROR

COMM11 - EERS XMIT ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA TRANSMIT COMM11 - EERS XMIT ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE DECK DCSSA TRANSMIT ERROR

ERROR Safety Group Safety Group

SFTY01 - DOOR ZONE BYP - DOOR ZONE BYPASS SFTY01 - DOOR ZONE BYP - DOOR ZONE BYPASS SFTY02 - LINE OVERSPD - LINE OVERSPEED SFTY02 - LINE OVERSPD - LINE OVERSPEED SFTY03 - NTSD OVERSPD - NTSD OVERSPEED SFTY03 - NTSD OVERSPD - NTSD OVERSPEED SFTY04 - VEL

SFTY04 - VEL TRKNG ERR - VELOCITY TRACKING ERRORTRKNG ERR - VELOCITY TRACKING ERROR SFTY05 - DRV TRCTN ERR - DRIVE TRACTION LOSS

SFTY05 - DRV TRCTN ERR - DRIVE TRACTION LOSS SFTY06 - UX, DX TLYS - UP/DOWN RELAYS

SFTY06 - UX, DX TLYS - UP/DOWN RELAYS SFTY07 - SENSORS - DOOOR ZONE SENSORS SFTY07 - SENSORS - DOOOR ZONE SENSORS SFTY08 - SC TLY -

SFTY08 - SC TLY - SPEED RELAYSSPEED RELAYS SFYT09 - SFTY CHN -

SFYT09 - SFTY CHN - SAFETY CHAIN BROKESAFETY CHAIN BROKENN SFTY10 - RECOVERS FAIL -

SFTY10 - RECOVERS FAIL - RECOVERY ATTEMPTSRECOVERY ATTEMPTS

SFTY11 - HEARTBEAT - HEARTBEAT SFTY11 - HEARTBEAT - HEARTBEAT

SFTY12 - E STOP SWITCH - EMERGENCY STOP SWITHCH SFTY12 - E STOP SWITCH - EMERGENCY STOP SWITHCH SFTY13- BYPASS DROP - DOOR ZONE BYPASS DROP TEST SFTY13- BYPASS DROP - DOOR ZONE BYPASS DROP TEST SFTY14 - DOOR OPEN -

SFTY14 - DOOR OPEN - DOOR OPEN SAFETYDOOR OPEN SAFETY SFTY15 - ACCESS ZONE - ACCESS ZONE SFTY15 - ACCESS ZONE - ACCESS ZONE SFTY16 - NTSD TBL -

SFTY16 - NTSD TBL - NTSD TABLE INTEGRITYNTSD TABLE INTEGRITY

SFTY17 - EPROM CHKSUM - EPROM CHECKSUM ERROR SFTY17 - EPROM CHKSUM - EPROM CHECKSUM ERROR SFTY18 - 30 VOLTS

SFTY18 - 30 VOLTS - THIRTY VOLT FAILURE- THIRTY VOLT FAILURE SFTY19 - NTSD MALFUNC -

SFTY19 - NTSD MALFUNC - NTSD MALFUNCTIONNTSD MALFUNCTION

SFTY20 - DIR TEST FAULT -

SFTY20 - DIR TEST FAULT - DIRECTION TEST FAILUREDIRECTION TEST FAILURE SFTY21 - B44 RELAY FAULT -

SFTY21 - B44 RELAY FAULT - B44 RELAY FAULTB44 RELAY FAULT SFTY22 - B44 TRIPPED - B44

SFTY22 - B44 TRIPPED - B44 CIRCUIT TRIPPECIRCUIT TRIPPEDD

SFTY23 - ETSD SPD RELAY - EMERGECNY TERMINAL SLOW DOWN RELAY CHECK FAILURE SFTY23 - ETSD SPD RELAY - EMERGECNY TERMINAL SLOW DOWN RELAY CHECK FAILURE SFTY24 - ICES CHK FAIL - IN CAR EMERGENCY STOP SWITCH CHECK FAILURE

SFTY24 - ICES CHK FAIL - IN CAR EMERGENCY STOP SWITCH CHECK FAILURE SFTY25 - INA CHK FAIL - INSPECTION RELAY CHECK FAILURE

SFTY25 - INA CHK FAIL - INSPECTION RELAY CHECK FAILURE SFTY26 - DOOR CHN FAIL - DOOR CHAIN CHECK FAILURE SFTY26 - DOOR CHN FAIL - DOOR CHAIN CHECK FAILURE DBSS Group

DBSS Group

DBSS00 - DRIVE FAULT - DRIVE FAULT DBSS00 - DRIVE FAULT - DRIVE FAULT

DBSS01 - NO RDY TO RUN- TIMED OUT WAITING FOR READY TO RUN DBSS01 - NO RDY TO RUN- TIMED OUT WAITING FOR READY TO RUN DBSS02 - BRK NOT LFTD -

DBSS02 - BRK NOT LFTD - TIMED OUT WAITING FOR "BRAKE LIFTED"TIMED OUT WAITING FOR "BRAKE LIFTED"

DBSS03 - STOP&SHUTDOWN - RECEIVED "STOP AND SHUTDOWN" MESSAGE DBSS03 - STOP&SHUTDOWN - RECEIVED "STOP AND SHUTDOWN" MESSAGE DBSS04 - BRK NOT

(3)

Motion Faults Motion Faults

MOTN00 - EEPROM JUMPER - EEPROM SWITCH MOTN00 - EEPROM JUMPER - EEPROM SWITCH MOTN01 - DBSS FAULT - DBSS FAULT

MOTN01 - DBSS FAULT - DBSS FAULT

MOTN02- BAD BRK STATE - INVALID BRAKE STATE MOTN02- BAD BRK STATE - INVALID BRAKE STATE

MOTN03 - BAD RTR STATE - INVALID READY TO RUN STATE MOTN03 - BAD RTR STATE - INVALID READY TO RUN STATE

MOTN04 - BAD DBD STATE - INVALID DRIVE AND BRAKE DISCONNECT STATE MOTN04 - BAD DBD STATE - INVALID DRIVE AND BRAKE DISCONNECT STATE MOTN05 - BRAKE TIMEOUT - BRAKE LIFTED TIME EXCEEDED

MOTN05 - BRAKE TIMEOUT - BRAKE LIFTED TIME EXCEEDED MOTN06 - GSMON TIMEOUT -

MOTN06 - GSMON TIMEOUT - GATE SWITCH MONITOR TIMEOUTGATE SWITCH MONITOR TIMEOUT MOTN07 - POSINIT FAULT - POSITION INITIALIZATION FAILURE MOTN07 - POSINIT FAULT - POSITION INITIALIZATION FAILURE MOTN08 - POSITION FLT - POSITION FAULT

MOTN08 - POSITION FLT - POSITION FAULT

Eve

Event

nt Counter

Counter

The Event Counter data obtained through the use

The Event Counter data obtained through the use of the Service Tool is of the Service Tool is divided into 4 categories.divided into 4 categories. 1.

1. COMM RS422 communication events wCOMM RS422 communication events which occur between the MCSS and the other sub systems.hich occur between the MCSS and the other sub systems. 2.

2. SFTY Safety related SFTY Safety related events which are monitored by events which are monitored by the MCSS.the MCSS. 3.

3. DBSS Events directly related to the operation of the DrDBSS Events directly related to the operation of the Drive and Brake Sub System (DBSS)ive and Brake Sub System (DBSS).. 4.

4. MOTN Motion related evMOTN Motion related events which are monitored by ents which are monitored by the MCSS.the MCSS.

Eve

Event Log

nt Log

The Event Log provides a 1 frame, 40 millisecond, snapshot of MCSS data at the time an event is logged.

The Event Log provides a 1 frame, 40 millisecond, snapshot of MCSS data at the time an event is logged. TheThe

event Log will retain the 25 most recent events but only the five latest events will have the data snapshots event Log will retain the 25 most recent events but only the five latest events will have the data snapshots attached.

attached.

Led I

Led Indicators

ndicators

The faults indicated in

The faults indicated in the Service Tool Event Counter are also ithe Service Tool Event Counter are also i ndicated by the red Light Emitting Diode ndicated by the red Light Emitting Diode (LED)(LED) group located at the bottom edge of the MCSS-A micropr

group located at the bottom edge of the MCSS-A microprocessor board. ocessor board. The error reporting via these LEDs isThe error reporting via these LEDs is limited from the standpoint that only the first Safety Event detected during a run will illuminate the LEDs.

limited from the standpoint that only the first Safety Event detected during a run will illuminate the LEDs. TheThe

binary combination of the FC01 through FC32 LEDs indicates the event trapped.

binary combination of the FC01 through FC32 LEDs indicates the event trapped. For example, HEARTBEAFor example, HEARTBEAT inT in the Event Log shows as SFTY11 in

the Event Log shows as SFTY11 in the Event Counter and would be indicated the Event Counter and would be indicated by the following:by the following:

FC01 on FC01 on FC02 on FC02 on FC04 off FC04 off FC08 on FC08 on FC16 off FC16 off FC32 0ff FC32 0ff

The LEDs remain illuminated until

The LEDs remain illuminated until the Motion Logic State (MLS) reaches PREP_TO_RUN (MLS 3), while thethe Motion Logic State (MLS) reaches PREP_TO_RUN (MLS 3), while the Motion Command Mode (MCM) is

(4)

Note:

Note: There is a priority for LEThere is a priority for LED code display in cases where fD code display in cases where faults are declared in the same aults are declared in the same 40 millisecond40 millisecond frame.

frame.

Priority list of LED Indication for Simultaneous Faults Priority list of LED Indication for Simultaneous Faults

FC18

FC18 Highest Highest 30 30 VOLTSVOLTS

FC15

FC15 ACCESS ACCESS ZONEZONE

FC10

FC10 RECOVERS RECOVERS FAILFAIL

FC09 FC09 SFTY SFTY CHNCHN FC11 HEARTBEAT FC11 HEARTBEAT FC08 FC08 SPD SPD RLYSRLYS FC07 SENSORS FC07 SENSORS FC06

FC06 UX, UX, DX DX RLYSRLYS

FC05

FC05 DRV DRV TRCTN TRCTN LOSLOS

FC04

FC04 VEL VEL TRKNG TRKNG ERRERR

FC20

FC20 DIR DIR TST TST FAULTFAULT

FC16 FC16 NTSD NTSD TBLTBL FC03 FC03 NTSD NTSD OVERSPDOVERSPD FC19 FC19 NTSD NTSD MALFUNCMALFUNC FC02

FC02 LINE LINE OVERSPEOVERSPEDD

FC14

FC14 DOOR DOOR OPENOPEN

FC13

FC13 BYPASS BYPASS DROPDROP

FC01

FC01 DOOR DOOR ZONE ZONE BYPBYP

FC12

FC12 Lowest Lowest E E STOP STOP SWITCHSWITCH FC17 power up onl

FC17 power up onl y ERPM CHKSUMy ERPM CHKSUM FC63

FC63 PRO PRO required required DRIVE DRIVE FAULTSFAULTS The following faults have the

The following faults have the highest priority.highest priority. FC25

FC25 EEPROM EEPROM JUMPERJUMPER

FC26

FC26 DBSS DBSS FAULTSFAULTS

FC27

FC27 BAD BAD BRK BRK STATESTATE

FC28

FC28 BAD BAD RTR RTR STATESTATE

FC29

FC29 BAD BAD DBD DBD STATESTATE

FC30

FC30 BRAKE BRAKE TIMEOUTTIMEOUT

FC31

FC31 GSMON GSMON TIMEOUTTIMEOUT

FC32

FC32 POSINIT POSINIT FAULTFAULT

MCS

(5)

Communications Fault Group

COMM00 - OCSS ERR - OCSS RECEIVE ERROR COMM00 - OCSS ERR - OCSS RECEIVE ERROR

Event Counter label - COMM00 Event Counter label - COMM00 Event Log label - OCSS RCV ERR Event Log label - OCSS RCV ERR OCSS communication LED lit steady. OCSS communication LED lit steady. The MCSS has not been able to

The MCSS has not been able to successfully decode a valid successfully decode a valid message from the OCSS within the time-out periodmessage from the OCSS within the time-out period (OCSS

TIME-(OCSS TIME-OUT = 300 milliseconds): OUT = 300 milliseconds): This is located in theThis is located in the COMMUNICCOMMUNICATIONS TIMING PARAMETERS ofATIONS TIMING PARAMETERS of th

th e MCSS EEPROM SET UPe MCSS EEPROM SET UP.. 1.

1. Verify that the Verify that the OCSS board OCSS board is up and ris up and running. unning. OCSS board OCSS board mounted LEDs mounted LEDs 1 and 2 should 1 and 2 should be flashing.be flashing. 2.

2. Verify that tVerify that the MCSS he MCSS is up and running. is up and running. The MCSS-A The MCSS-A board mounted Hboard mounted Heartbeat (HRTBeartbeat (HRTB) LED should ) LED should bebe flashing.

flashing. 3.

3. Check the MCCheck the MCSS communications SS communications wiring to and wiring to and from OCSS. from OCSS. Check that Check that the OCSS the OCSS board, connector board, connector P4 andP4 and MCSS board, connector P5 are

MCSS board, connector P5 are properly connected.properly connected. 4.

4. Check that the Check that the shielding, used on the shielding, used on the NAO version new NAO version new sales controller only, sales controller only, is properly grounded (is properly grounded (one endone end only ) at the MCSS card cage.

only ) at the MCSS card cage. 5.

5. Replace Replace the the OCSS OCSS board.board. 6.

6. Replace Replace the the MCSS-A MCSS-A board.board.

COMM01- OCSS XMIT ERR _ OCSS TRANSMIT ERROR COMM01- OCSS XMIT ERR _ OCSS TRANSMIT ERROR

Event Counter label - COMM01 Event Counter label - COMM01 Event Log label - OCSS XMIT ERR Event Log label - OCSS XMIT ERR OCSS Communication LED flashing. OCSS Communication LED flashing.

The MCSS Random Access Memory (RAM) transmission buffer

The MCSS Random Access Memory (RAM) transmission buffer for the OCSS communications channel for the OCSS communications channel hashas overflowed.

overflowed. This is usually caused by the absence oThis is usually caused by the absence of hardware interrupts frf hardware interrupts from the Dual User Asynchrom the Dual User Asynchronousonous Receive and Transmit (DUART) communication controller.

Receive and Transmit (DUART) communication controller. 1.

1. Power on RPower on Reset (POR) eset (POR) the MCSS-A the MCSS-A board this provides board this provides a DUART a DUART hardware reset.hardware reset. 2.

2. Replace Replace the the MCSS-A MCSS-A microprocessor microprocessor card.card. COMM02- DBSS RCV ERR - DB

COMM02- DBSS RCV ERR - DB SS RECEIVE ERRORSS RECEIVE ERROR

Event Counter label - COMM02 Event Counter label - COMM02 Event Log label - DBSS RCV ERR Event Log label - DBSS RCV ERR DBSS communication LED lit steady. DBSS communication LED lit steady. The MCSS has not been able to

The MCSS has not been able to successfully decode a valid message successfully decode a valid message from the DBSS within the time-out period.from the DBSS within the time-out period. DBSS TIME-OUT = 150 milliseconds, this is located in the

(6)

MCSS EEPROM SET UP. MCSS EEPROM SET UP. 1.

1. Verify that Verify that the DBSthe DBSS board S board is up and is up and running. running. DBSS operDBSS operation can be ation can be verified by plugging verified by plugging the Service the Service ToolTool directly into the drive.

directly into the drive. 2.

flashing. 3.

3. Check the MCSCheck the MCSS communications S communications wiring to and wiring to and from the DBfrom the DBSS. SS. Check that conneCheck that connector P7 t ctor P7 t the MCSS the MCSS boardboard and 3TB at the DBSS board are properly connected.

and 3TB at the DBSS board are properly connected. 4.

4. Check that the shielding, is properlCheck that the shielding, is properly grounded ( one end only ), Dy grounded ( one end only ), DBSS transmit tBSS transmit to MCSS at the o MCSS at the DBSS GroundDBSS Ground BUS< MCSS transmit to DBSS at the MCSS card

BUS< MCSS transmit to DBSS at the MCSS card cage.cage.

5.

5. Replace Replace the the DBSS DBSS board.board. 6.

6. Replace Replace the the MCSS-A MCSS-A board.board. COMM03 - D

COMM03 - DBSS XMIT ERR BSS XMIT ERR - DBSS TRANSMIT ER- DBSS TRANSMIT ERRORROR Event Counter label - COMM03

Event Counter label - COMM03 Event Log label - DBSS XMIT ERR Event Log label - DBSS XMIT ERR DBSS communications LED flashing. DBSS communications LED flashing. The MCSS RAM transmission buff

The MCSS RAM transmission buffer for the DBSS communications channel has overflowed. er for the DBSS communications channel has overflowed. This is usuallyThis is usually caused by the absence of hardware interrupts from the Dual

caused by the absence of hardware interrupts from the Dual User Asynchronous Receive and Transmit (DUART)User Asynchronous Receive and Transmit (DUART) communication controller.

communication controller. 1.

1. Power On Reset Power On Reset (POR) the MC(POR) the MCSS-A board this proSS-A board this provides a DUART hardvides a DUART hardware reset.ware reset. 2.

2. Replace Replace the the MCSS-A MCSS-A microprocessor microprocessor card.card.

COMM04 - DCSS RCV ERR - DCSS RECEIVE ERROR COMM04 - DCSS RCV ERR - DCSS RECEIVE ERROR

Event Counter label - COMM04 Event Counter label - COMM04 Event Log label - DCSS RCV ERR Event Log label - DCSS RCV ERR DCSS communication LED lit steady. DCSS communication LED lit steady. The MCSS has not been able to

The MCSS has not been able to successfully decode a valid message successfully decode a valid message from the DCSS within the time-out period.from the DCSS within the time-out period. DCSS TIME-OUT = 300 ms, this is located in the

DCSS TIME-OUT = 300 ms, this is located in the COMMUNICATIONS TIMING PARAMETERS of the MCSSCOMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP.

EEPROM SET UP. 1.

1. Verify that tVerify that the DCSS he DCSS board is up and board is up and running. running. DCSS operation DCSS operation can be verified can be verified by the illumination of by the illumination of the LEDthe LED on the DISS board.

on the DISS board. 2.

2. Verify that the Verify that the MCSS is MCSS is up and running. up and running. The MCSS-A The MCSS-A board mounted Hboard mounted Heartbeat (HRTB) eartbeat (HRTB) LED Should LED Should bebe flashing.

flashing. 3.

3. Check the MCSS Check the MCSS communications wiring to and fcommunications wiring to and from the DCSS. rom the DCSS. Check that MCSCheck that MCSS board connector P7 S board connector P7 andand DISS board connector P2 are properly connected.

(7)

5.

5. Replace Replace the the DISS DISS board.board. 6.

COMM05 - DCSS XMIT ERR - DCSS TRANSMIT ERROR COMM05 - DCSS XMIT ERR - DCSS TRANSMIT ERROR

Event Counter label - COMM05 Event Counter label - COMM05 Event Log label - DCSS XMIT ERR Event Log label - DCSS XMIT ERR DCSS communications LED flashing. DCSS communications LED flashing. The MCSS RAM transmission buffer f

The MCSS RAM transmission buffer for the DCSS communications channel has overflowed. or the DCSS communications channel has overflowed. This is usuallyThis is usually caused by the absence of

caused by the absence of hardware interrupts from the Dual User Asynchronous Receive and Transmit *DUART)hardware interrupts from the Dual User Asynchronous Receive and Transmit *DUART) communication controller.

communication controller. 1.

1. Power On Power On Reset (PORReset (POR) the MCS) the MCSS-A board tS-A board this provides a Dhis provides a DUART hardwUART hardware reset.are reset. 2.

2. Replace Replace the the MCSS_A MCSS_A microprocessor microprocessor card.card.

COMM06 - PPTP RCV ERR - SPPT PRIMARY RECEIVE ERROR COMM06 - PPTP RCV ERR - SPPT PRIMARY RECEIVE ERROR

Event Counter label - COMM06 Event Counter label - COMM06 Event Log label - PPTP RCV ERR Event Log label - PPTP RCV ERR PPT1 communications LED lit steady. PPT1 communications LED lit steady. The MCSS has not been able to successfully

The MCSS has not been able to successfully decode a valid message decode a valid message from the SPPT PRIMARY CHfrom the SPPT PRIMARY CHANNELANNEL within the 5 100 ms time-out periods.

within the 5 100 ms time-out periods. SPPTP COMM_TISPPTP COMM_TIME =20 milliseconds, this is located in theME =20 milliseconds, this is located in the COMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP.

COMMUNICATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP. 1.

1. Verify that tVerify that the SPPT board he SPPT board is up and running. is up and running. SPPT operation SPPT operation can be verified can be verified by the illumination of by the illumination of the 2the 2 green LEDs on the SPPT.

green LEDs on the SPPT. 2.

flashing. 3.

3. Check the MCCheck the MCSS communications SS communications wiring to and wiring to and from the SPfrom the SPPT. PT. Check that MCCheck that MCSS board connecSS board connector P6 andtor P6 and SPPT assembly

SPPT assembly 25 pin 25 pin "D" connector ar"D" connector are properly connected.e properly connected. 4.

4. Check that the Check that the shielding is properly grounded shielding is properly grounded ( one end only) ( one end only) at the MCSat the MCSS card cage.S card cage. 5.

5. Replace Replace the the SPPT SPPT board.board. 6.

COMM07 - PPTP XMIT ERR - SPPT PRIMARY TRANSMIT ERROR COMM07 - PPTP XMIT ERR - SPPT PRIMARY TRANSMIT ERROR

Event Counter label - COMM07 Event Counter label - COMM07 Event Log label - PPTP XMIT ERR Event Log label - PPTP XMIT ERR PPT1 communications LED flashing. PPT1 communications LED flashing.

(8)

The MCSS RAM transmission buffer f

The MCSS RAM transmission buffer for the SPPT PRIMARor the SPPT PRIMARY communications channel has overflowed. Y communications channel has overflowed. This isThis is usually caused by the absence

usually caused by the absence of hardware interrupts form the Dual User Asynchronous Receive and Transmitof hardware interrupts form the Dual User Asynchronous Receive and Transmit (DUART) communication controller.

(DUART) communication controller. 1.

1. Power On Power On Reset (PORReset (POR) The MCS) The MCSS-A board this S-A board this provides a DUARprovides a DUART hardware rT hardware reset.eset. 2.

2. Replace Replace the the MCSS-A MCSS-A microprocessor microprocessor card.card.

COMM08 - PPTS RCV ERR - SPPT SECONDARY RECEIVE ERROR COMM08 - PPTS RCV ERR - SPPT SECONDARY RECEIVE ERROR

Event Counter label - COMM08 Event Counter label - COMM08 Event Log label - PPTS RCV ER Event Log label - PPTS RCV ER PPT2 communications LED lit steady. PPT2 communications LED lit steady. The MCSS has not been able to successfully

The MCSS has not been able to successfully decode a valid message from the decode a valid message from the SPPT SECONDSPPT SECONDARY CHANNELARY CHANNEL within the time-out period.

within the time-out period. SPPTS_COMM_TISPPTS_COMM_TIME = 20 milliseconds, this is located in the COMMUNICATIME = 20 milliseconds, this is located in the COMMUNICATIONSONS TIMING PARAMETERS of the MCSS EEPROM SET UP.

TIMING PARAMETERS of the MCSS EEPROM SET UP. 1.

1. Verify that tVerify that the SPPT board he SPPT board is up and running. is up and running. SPPT operation SPPT operation can be verified can be verified by the illumination of by the illumination of the 2the 2 green LEDs on the SPPT.

green LEDs on the SPPT. 2.

2. Verify that Verify that the MCSthe MCSS is S is up and up and running. running. The MCSS-The MCSS-A A board mounted board mounted Heartbeat Heartbeat (HRTB) (HRTB) LED should LED should bebe flashing.

flashing. 3.

3. Check the MCCheck the MCSS communications SS communications wiring to and wiring to and from the SPfrom the SPPT. PT. Check that MCCheck that MCSS board connecSS board connector P6 andtor P6 and SPPT assembly 25 pin "D" connector are properly

SPPT assembly 25 pin "D" connector are properly connected.connected. 4.

4. Check that the Check that the shielding is properly grounded shielding is properly grounded (one end only) at (one end only) at the MCSS the MCSS card cage.card cage. 5.

5. Replace Replace the the SPPT SPPT board.board. 6.

COMM09 - PPTS XMIT ERR - SPPT SECONDARY TRANSMIT ERROR COMM09 - PPTS XMIT ERR - SPPT SECONDARY TRANSMIT ERROR

Event Counter label - COMM09 Event Counter label - COMM09 Event Log label - PPTS XMIT ERR Event Log label - PPTS XMIT ERR PPT2 communication LED flashing. PPT2 communication LED flashing. The MCSS RAM transmission buffer f

The MCSS RAM transmission buffer for the SPPT SECONor the SPPT SECONDARY communications channel has overflowDARY communications channel has overflowed. ed. ThisThis is usually caused by

is usually caused by the absence of hardware interrupts form the Dual User Asynchronous Receive and Transmitthe absence of hardware interrupts form the Dual User Asynchronous Receive and Transmit (DUART) communication controller.

(DUART) communication controller. 1.

(9)

COMM10 - E4RSS RCV ERR - EMERGENCY RESC

COMM10 - E4RSS RCV ERR - EMERGENCY RESCUE SUB UE SUB SYSTEM / DOUBLE DECK SYSTEM / DOUBLE DECK DCSSA RECEIVEDCSSA RECEIVE ERROR

ERROR

Event Counter label -

Event Counter label - EERS RCV ERREERS RCV ERR Event Log label - COMM10

Event Log label - COMM10

ERO communications LED on STEADY ERO communications LED on STEADY The MCSS has not been able to

The MCSS has not been able to successfully decode a valid successfully decode a valid message from the EMERGENCmessage from the EMERGENCY RESCUE SUBY RESCUE SUB SYSTEM (JERO

SYSTEM (JERO) or the DCSSA (double deck) channel within the time-out per) or the DCSSA (double deck) channel within the time-out period. iod. DCSSA COMMDCSSA COMM_TIME = 300_TIME = 300 milliseconds, this is

milliseconds, this is located in the located in the COMMUNICCOMMUNICATIONS TIMING PARAMEATIONS TIMING PARAMETERS of the MCSS EEPROM SET UP.TERS of the MCSS EEPROM SET UP. 1.

1. Verify that Verify that the JEROthe JERO/DCSSA /DCSSA board is up board is up and running.and running. 2.

flashing. 3.

3. Check the Check the MCSS comMCSS communications wiring munications wiring to and to and from the from the JERO/DCSSJERO/DCSSA. A. Check that Check that MCSS boarMCSS board connectord connector P4 and JERO/DCSSA assembly connector are properly

P4 and JERO/DCSSA assembly connector are properly connected.connected.

4.

4. Check that the Check that the shielding is properly grounded shielding is properly grounded (one end only) at (one end only) at the MCSS the MCSS card cage.card cage. 5.

5. Replace Replace the the JERO/DSSJERO/DSSA A board.board. 6.

COMM11 - EERS XMIT ERR - EMERGENCY RESC

COMM11 - EERS XMIT ERR - EMERGENCY RESCUE SUB SYSTEM/DOUBLE UE SUB SYSTEM/DOUBLE DECK DCSSA DECK DCSSA TRANSMITTRANSMIT ERROR

ERROR

Event Counter label - COMM11 Event Counter label - COMM11 Event Log label - ERSS XMIT ERR Event Log label - ERSS XMIT ERR ERSS communications LED flashing. ERSS communications LED flashing. The MCSS RAM transmission

The MCSS RAM transmission buffer for the buffer for the EMERGENCEMERGENCY RESCUE SUB SYSTEM (JERO) or DCSSA (DoubleY RESCUE SUB SYSTEM (JERO) or DCSSA (Double Deck) communications channel h

Deck) communications channel has overflowed. as overflowed. This is usually caused by the absence of harThis is usually caused by the absence of hardware interruptsdware interrupts from the Dual User Asynchronous Receive

from the Dual User Asynchronous Receive and Transmit (DUART) communication controller.and Transmit (DUART) communication controller. 1.

2. Replace Replace the the MCSS-A MCSS-A microprocessor microprocessor card.card. Safety Group

Safety Group SFTY01 -

SFTY01 - DOOR ZONDOOR ZONE BYP - E BYP - DOOR ZONDOOR ZONE BYPASSE BYPASS Event Counter label -

Event Counter label - DOOR ZONE BYPDOOR ZONE BYP Event Log label - SFTY01

Event Log label - SFTY01 Fault Code LED lit - 1

Fault Code LED lit - 1 (binary 1)(binary 1)

The MCSS has determined, by the relay sense contact, that the

The MCSS has determined, by the relay sense contact, that the Door Zone (DZ) or Alternate Door Zone (ADZ)Door Zone (DZ) or Alternate Door Zone (ADZ) relay is in a

(10)

1.

1. Access the SAccess the Service Tool function, ervice Tool function, MCSS, MMCSS, MONITOR, DONITOR, DISCRETE ISCRETE INPUTS, INPUTS, (M, 2, 1, (M, 2, 1, 2) DZ and/or 2) DZ and/or ADZ. ADZ. TheThe symbols should toggle between upper case and

symbols should toggle between upper case and lower case letters as the relay is lower case letters as the relay is pushed in or dropped out.pushed in or dropped out. See MCSS Service Tool document TIP 31.4-1 fo

See MCSS Service Tool document TIP 31.4-1 for further information. r further information. If this test is successful go directly toIf this test is successful go directly to step 5.

step 5. 2.

2. Use a volt Use a volt meter to check meter to check for 30 VDfor 30 VDC at relay coC at relay contacts DZ-33 ntacts DZ-33 and ADZ-33. and ADZ-33. See Straight See Straight Line diagram.Line diagram. 3.

3. Use a volt Use a volt meter to check meter to check for 30 VDfor 30 VDC at MCSC at MCSS-B plug PS-B plug P5-2 when the 5-2 when the DZ relay is pushed DZ relay is pushed in. in. See StraightSee Straight Line diagram.

Line diagram. 4.

4. Use a volt mUse a volt meter to check eter to check for 30 VDC for 30 VDC at MCSS-B at MCSS-B plug P4-3 when plug P4-3 when the ADZ relay the ADZ relay is pushed in. is pushed in. See StraightSee Straight Line diagram.

Line diagram. 5.

5. Access the SAccess the Service Tool Function, MCervice Tool Function, MCSS, TEST, SS, TEST, OUTPUTS, OUTPUTS, (M, 2, 1, (M, 2, 1, 2) DZ and 2) DZ and / or AD/ or ADZ. Z. The selected relayThe selected relay should pick when the display is in upper case letters and drop when in lower case letters.

should pick when the display is in upper case letters and drop when in lower case letters. See MCSS ServiceSee MCSS Service Tool document TIP 31.4-1 and Straight Line Diagram.

Tool document TIP 31.4-1 and Straight Line Diagram. Note:

Note: This check is disabled whenever the MCSS is in a MANUAL (ACThis check is disabled whenever the MCSS is in a MANUAL (ACCESS, INSPCESS, INSPECTION) or InitializationECTION) or Initialization (INIT) MODE.

(INIT) MODE.

SFTY02-LINE OVERSPD -L

SFTY02-LINE OVERSPD -LINE OVERSPEEDINE OVERSPEED

Event Counter label - SFTY02 Event Counter label - SFTY02 Event Log label

Event Log label - LINE OVERSPD- LINE OVERSPD Fault Code LED lit 2 (binary 2) 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 The CAR SPEED sent from the SPPT PRIMARY channel was determined by the MCSS to be in excess of 110 percent of contract speed.

percent of contract speed. 1.

1. Access the Service Tool Function, Access the Service Tool Function, MCSS, DAMCSS, DATA CAPTURETA CAPTURE, DISPLAY , DISPLAY VARIABLESVARIABLES, (M, 2, 5, , (M, 2, 5, 1) to monitor1) to monitor the PRIMARY CA

the PRIMARY CAR VELOCITY and the DICR VELOCITY and the DICTATED VELOCITY TATED VELOCITY during a normal full speed run. during a normal full speed run. NeitherNeither parameter should exceed the

parameter should exceed the CONTRACCONTRACT VELOCITY as set iT VELOCITY as set in the CONTRACT/CODE section of the SETn the CONTRACT/CODE section of the SET UP procedure.

UP procedure. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for further information.urther information. 2.

2. If the PRIMAIf the PRIMARY CAR VRY CAR VELOCITY is greatELOCITY is greater than the contract ver than the contract velocity check the value of SPelocity check the value of SPPT POS SCPT POS SCALERALER and SPPT VEL SCALER with the POSITION/VELOCITY section of the MCSS, SET UP procedure.

and SPPT VEL SCALER with the POSITION/VELOCITY section of the MCSS, SET UP procedure. SPPT POS SCA

SPPT POS SCALER must equal 394, and SPPT VELER must equal 394, and SPPT VEL SCALER must equal 67295. L SCALER must equal 67295. Values are for a 1524 mmValues are for a 1524 mm circumference ( 20 inch diameter ) SPPT drive sheave.

circumference ( 20 inch diameter ) SPPT drive sheave. See MCSS Service Tool Users Manual TIP 31.4-1 forSee MCSS Service Tool Users Manual TIP 31.4-1 for further information.

further information. 3.

3. Access the Service Tool Function, Access the Service Tool Function, MCSS, SEMCSS, SET UP, RIDE T UP, RIDE QUALITY, (QUALITY, (M, 2,3,2) to verify M, 2,3,2) to verify the values ofthe values of CONTRACT ACC

CONTRACT ACCEL, CONTRACT JERK, ANEL, CONTRACT JERK, AND CONTRACT VEL. D CONTRACT VEL. These parameters are contract dependent.These parameters are contract dependent. See MCSS Service Tool Users manual TIP 31.4-1 for further information.

See MCSS Service Tool Users manual TIP 31.4-1 for further information. 4.

4. If the scalers and profIf the scalers and profile values are correct and the DIile values are correct and the DICTATED VELOCTATED VELOCITY is greater than CITY is greater than the CONTRACthe CONTRACTT VELOCITY replace the

VELOCITY replace the MCSS-A microprocessor board.MCSS-A microprocessor board. 5.

5. Access the Service Tool Function, Access the Service Tool Function, DBSS, MONDBSS, MONITOR, DRIVITOR, DRIVE DATA, (E DATA, (M, 4, 1, 6) to M, 4, 1, 6) to monitor SPEEDmonitor SPEED REFERENC

REFERENCE (SPD REF) and SPEE (SPD REF) and SPEED FEEDBACED FEEDBACK (SPD FBK). K (SPD FBK). Both parameters are scaled in mm/sec. Both parameters are scaled in mm/sec. SeeSee DBSS Service Tool Users manual TIP 31.2-1 for further information.

(11)

6.

6. If the SPEEIf the SPEED FEEDBACD FEEDBACK is incorrect check the K is incorrect check the TACH COUNTSTACH COUNTS, RPM, and R, RPM, and RATED SPEEATED SPEED underD under ELEVATOR CO

ELEVATOR CONSTANTS in the DBSSNSTANTS in the DBSS. . Also visually inspect the TACH and coupling for physical flaws orAlso visually inspect the TACH and coupling for physical flaws or damage.

damage. 7.

7. If values If values are correct are correct replace the replace the DBSS DBSS control card.control card. SFTY03 - NTSD OVERSPD - NTSD OVERSPEED SFTY03 - NTSD OVERSPD - NTSD OVERSPEED

Event Counter label - SFTY03 Event Counter label - SFTY03 Event Log label

Event Log label - NTSD OVERSPD- NTSD OVERSPD Fault Code LEDs lit - 1 and

Fault Code LEDs lit - 1 and 2 (binary 3)2 (binary 3)

The MCSS has determined that the velocity dictation is

The MCSS has determined that the velocity dictation is in excess of the Normal Terminal Slow Down (NTSD)in excess of the Normal Terminal Slow Down (NTSD) velocity limit as calculated from the

velocity limit as calculated from the SPPT Secondary channel positiSPPT Secondary channel position information. on information. This data is compared againstThis data is compared against the calculated NTSD_RAM table, assembled at power up, together with the NTSD_DECEL parameter set to 1500 the calculated NTSD_RAM table, assembled at power up, together with the NTSD_DECEL parameter set to 1500 mm/sec.

mm/sec. 1.

1. Access the SerAccess the Service Tool Function, Mvice Tool Function, MCSS SET CSS SET UP, RIDUP, RIDE QUALITYE QUALITY, (M, 2, , (M, 2, 3, 2) DEC3, 2) DECEL RATIOEL RATIO. . Verify thatVerify that the value, A percent of CONTRAC

the value, A percent of CONTRACT ACCEL does not exceed 1500 mm/s. T ACCEL does not exceed 1500 mm/s. Also verify that none of the 7 ALTAlso verify that none of the 7 ALT PROFILE DEC rat

PROFILE DEC rates exceed 1500 mm/s2. es exceed 1500 mm/s2. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for furtherurther information.

information. 2.

2. Access the Service Tool Function, MCSS, DAAccess the Service Tool Function, MCSS, DATA CAPTURE, DTA CAPTURE, DISPLAY VARISPLAY VARIBALES, (M, 2, 5, 1) IBALES, (M, 2, 5, 1) PRIMARYPRIMARY CAR POS and SEC

CAR POS and SECONDARY POONDARY POS. S. Verify that these positions are the same and correct for the position inVerify that these positions are the same and correct for the position in the hoistway.

the hoistway. See further See further information.information. 3.

3. If the positions displayed above are incorIf the positions displayed above are incorrect Access the Servrect Access the Service Tool Function, MCSS, ice Tool Function, MCSS, SET UP, PSET UP, POS/VELOS/VEL (M, 2, 3, 4) and verify that the val

(M, 2, 3, 4) and verify that the val ue for SPPT POS SCALER is set to 394 for a 1524 mm circumference SPPTue for SPPT POS SCALER is set to 394 for a 1524 mm circumference SPPT drive sheave.

drive sheave. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for further information.urther information. SFTY04 - VEL TRKNG ERR - VEL

SFTY04 - VEL TRKNG ERR - VEL OCITY TRACKING ERROROCITY TRACKING ERROR Event Counter label - SFTY04

Event Counter label - SFTY04

Event Log Label - VEL TRKNG ERR Event Log Label - VEL TRKNG ERR Fault Code LED lit - 3

Fault Code LED lit - 3 (binary 4)(binary 4) The difference between the

The difference between the SPPT Primary channel velocity (PRIMARY CAR VEL) and the SPPT Primary channel velocity (PRIMARY CAR VEL) and the DICTATED VELOCIDICTATED VELOCITYTY has exceeded the value set in

has exceeded the value set in TRACKING ERTRACKING ERR VEL TOL in MCSS, SET UP, SAFETY PARAMER VEL TOL in MCSS, SET UP, SAFETY PARAMETERS. TERS. If thisIf this occurs for 6 consecutive confirmation cycles, a

occurs for 6 consecutive confirmation cycles, a Velocity Tracking Error is logged.Velocity Tracking Error is logged. 1.1.

1.1. Access the Service Tool FunAccess the Service Tool Function, MCSS DAction, MCSS DATA CAPTURE, TA CAPTURE, (M, 2, 5, ) (M, 2, 5, ) DISPLAY VDISPLAY VARIABLE to ARIABLE to comparecompare the value of the DICTATED VELOCITY and PRIMARY CA

the value of the DICTATED VELOCITY and PRIMARY CAR VELOCITY. R VELOCITY. See MCSS Service Tool UsersSee MCSS Service Tool Users Manual TIP 31.4-1 for

Manual TIP 31.4-1 for further information.further information. 2.2.

2.2. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SEMCSS, SET UP, ST UP, SAFETY PARAFETY PARAMETER (mAMETER (m, 2, 3, , 2, 3, 5). 5). Check theCheck the value of TRCK ERR

value of TRCK ERR VEL TOL. VEL TOL. The value should be 6. The value should be 6. See MCSS SerSee MCSS Service Tool Users manual TIP vice Tool Users manual TIP 31.4-1 for31.4-1 for further information.

further information. 3.3.

3.3. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SEMCSS, SET UP, ST UP, SAFETY PARAFETY PARAMETERS AMETERS (M, 2, 3, (M, 2, 3, 4). 4). Check theCheck the value of VL

value of VL TRK ERR TRK ERR CT MAX. CT MAX. The value should be The value should be 6. 6. See MCSS See MCSS Service Tool UserService Tool Users manual TIP s manual TIP 31.4-131.4-1 for further information.

(12)

4.4.

4.4. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SMCSS, SET UP, PET UP, POS/VEL POS/VEL PARAMETER ARAMETER (M, 2, (M, 2, 3, 4). 3, 4). Check theCheck the value of SPPT VE

value of SPPT VEL SCALER. L SCALER. The value should be 67295. The value should be 67295. See MCSS SSee MCSS Service Tool Users manual TIP ervice Tool Users manual TIP 31.4- 31.4-1 for further information.

1 for further information. 5.5.

5.5. Access the Service Tool Function, Access the Service Tool Function, DBSS, MODBSS, MONITOR, DRIVNITOR, DRIVE DATA (mE DATA (m, 4, 1, 6) to , 4, 1, 6) to monitor SPEED monitor SPEED REFREF in mm/sec (Dictated Velocity form MCSS) and SPEED FEEDBA

in mm/sec (Dictated Velocity form MCSS) and SPEED FEEDBACK in mm/sec. CK in mm/sec. If the SPEED, RPM, andIf the SPEED, RPM, and TACH CNTS.

TACH CNTS. See MCSS Service Tool Users manual TIP 31.2-1 fSee MCSS Service Tool Users manual TIP 31.2-1 for further informationor further information 6.6.

6.6. If SPEEIf SPEED REF is D REF is incorrect. incorrect. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SMCSS, SET UP, RET UP, RIDE QUAIDE QUALITYLITY PARAMETER

PARAMETER (M, 2, 3, 2). (M, 2, 3, 2). Verify that CONTRAT VEVerify that CONTRAT VELOCITY IS set correctly.LOCITY IS set correctly. 7.7.

7.7. Access the SAccess the Service Tool Function, Dervice Tool Function, DBSS, MOBSS, MONITOR, STANITOR, STABILITY, (MBILITY, (M, 4, 1, , 4, 1, 2). 2). Verify that Verify that the GAIN the GAIN isis properly set.

properly set. Typical GAIN setTypical GAIN settings range from tings range from 8 to 13. 8 to 13. Low gain settings Low gain settings cause tracking errorcause tracking errors while highs while high gain setting cause oscillation.

gain setting cause oscillation. See MCSS See MCSS Service Tool Users Service Tool Users Manual TIP 31.2-Manual TIP 31.2-1 for further 1 for further information.information. 8.

8.SFTY05- DRV TRCTN ERR - DRIVE TRACTION LSFTY05- DRV TRCTN ERR - DRIVE TRACTION L OSSOSS 9.Event Counter label - SFTY05

9.Event Counter label - SFTY05

10.Event Log label - DRV TRCTN LOS 10.Event Log label - DRV TRCTN LOS 11.Fault Code LEDs lit - 1 and

11.Fault Code LEDs lit - 1 and 3 (binary 5)3 (binary 5)

12.The difference between the SPPT Primary channe

12.The difference between the SPPT Primary channe l velocity, PRIMARY CAR VELOCITY, and the PVTl velocity, PRIMARY CAR VELOCITY, and the PVT velocity, MACHINE CAR VE

velocity, MACHINE CAR VELOCITY, is greater than the value of TRCT LOSS VEL TL and LOCITY, is greater than the value of TRCT LOSS VEL TL and the difference hasthe difference has been present for more than the TRCT LOSS CT MAX.

been present for more than the TRCT LOSS CT MAX. 13.1.

13.1. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SMCSS, SET UP, SET UP, SAFETY PARAFETY PARAMETERS AMETERS (M, 2, (M, 2, 3, 5). 3, 5). Check thatCheck that the value of TRCT LOSS VEL TOL, is set to

the value of TRCT LOSS VEL TOL, is set to 500 mm/sec, and TRCT LOSS CT MAX, is set to 24 40 500 mm/sec, and TRCT LOSS CT MAX, is set to 24 40 msms cycles.

cycles. See MCSS Service Tool Users manual TIP 31.4-See MCSS Service Tool Users manual TIP 31.4-1 for further information.1 for further information. 14.2.

14.2. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SMCSS, SET UP, PET UP, POS/VEL POS/VEL PARAMETERS ARAMETERS (M, 2, 3, (M, 2, 3, 4). 4). Check thatCheck that the value of SPPT VEL SCALER, is set to 67295 for a

the value of SPPT VEL SCALER, is set to 67295 for a 1524 mm circumference SPPT drive sheave. See1524 mm circumference SPPT drive sheave. See MCSS Service Tool Users manual

MCSS Service Tool Users manual TIP 31.4-1 for further information.TIP 31.4-1 for further information. 15.3.

15.3. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SMCSS, SET UP, PET UP, POS/VEL POS/VEL PARAMETERS ARAMETERS (M, 2, 3, (M, 2, 3, 4). 4). Check theCheck the value of PVT POS SCALER, see MCSS I & A document TIP 31.4-2 for values and formula for calcul

value of PVT POS SCALER, see MCSS I & A document TIP 31.4-2 for values and formula for calcul ationsations

based on drive sheave size.

based on drive sheave size. See MCSS Service Tool Users manual TIP 31.4-1 for furSee MCSS Service Tool Users manual TIP 31.4-1 for further information.ther information. 16.4.

16.4. Access the Service Tool FunctAccess the Service Tool Function, MCSS, DAion, MCSS, DATA CAPTURETA CAPTURE, DISPLA, DISPLAY VARIBALEY VARIBALES (M, 2, 5, S (M, 2, 5, 1) to1) to compare the PRIMARY CAR VELO

compare the PRIMARY CAR VELOCITY to the MACHINE CAR VELOCITY to the MACHINE CAR VELOCITY. CITY. Both values should have theBoth values should have the same sign, + for up and - for down.

same sign, + for up and - for down. The MACHINE CAR VThe MACHINE CAR VELOCITY should be the correct sign this data isELOCITY should be the correct sign this data is sent from the DBSS.

sent from the DBSS. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for further information.urther information. 17.5.

17.5. If the MACHIIf the MACHINE CAR VNE CAR VELOCITY is the wELOCITY is the wrong sign check the DBSS rong sign check the DBSS to MCSS (Pto MCSS (PVT) communicationsVT) communications wiring.

wiring. 18.6.

18.6. If the PRIMAIf the PRIMARY CAR VRY CAR VELOCITY has the ELOCITY has the wrong sign check the Rotwrong sign check the Rotation orientation DIP Sation orientation DIP SWITCH inWITCH in the SPPT.

the SPPT. See SPPT document See SPPT document TIP 2.7.1-5.TIP 2.7.1-5. 19.

19.SFTY06- UX, DX RLYS - UP/DOWN RELAYSSFTY06- UX, DX RLYS - UP/DOWN RELAYS 20.Event Counter label - SFTY06

(13)

22.Fault Code LEDs lit - 2 and

22.Fault Code LEDs lit - 2 and 3 (binary 6)3 (binary 6) 23.This fault can be generated in

23.This fault can be generated in two possible ways.two possible ways. 24.A.

24.A. The U or D relay, is in a state, opposite to the MCSS commanded state, as mThe U or D relay, is in a state, opposite to the MCSS commanded state, as monitored by the relayonitored by the relay sense inputs on

sense inputs on the MCSS-the MCSS-B I/O B I/O board.board. 25.Or

25.Or 26.B.

26.B. The direction relay picked The direction relay picked is wrong wis wrong when compared to hen compared to the actual direction the actual direction of travel. of travel. This is based onThis is based on the SPPT Primary velocity channel when the car speed

the SPPT Primary velocity channel when the car speed reaches 60 percent of contract speed.reaches 60 percent of contract speed. 27.These checks are only performed in non-manual

27.These checks are only performed in non-manual modes with the Motion Logic State (MLS) greater than ormodes with the Motion Logic State (MLS) greater than or equal to Run (MLS 7).

equal to Run (MLS 7). 28.1.

28.1. Access the Service Tool FunctAccess the Service Tool Function, MCSS, DAion, MCSS, DATA CAPTURETA CAPTURE, DISPLA, DISPLAY VARIABLEY VARIABLE, (M, 2, 5, , (M, 2, 5, 1)1) PRIMARY CA

PRIMARY CAR VELOCITY, tR VELOCITY, to see if the fault occurs near 60 percent of contract speed. o see if the fault occurs near 60 percent of contract speed. See MCSS ServiceSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Tool Users manual TIP 31.4-1 for further information. 29.2.

29.2. Access the SAccess the Service Tool Function, ervice Tool Function, MCSS, SMCSS, SET UP, SET UP, SAFETY PARAFETY PARAMETERS, AMETERS, (M, 2, (M, 2, 3, 5). 3, 5). Check thatCheck that the value of UXDX

the value of UXDX CHECK CHECK percent equals 60, and UX percent equals 60, and UX & DX CT M& DX CT MAX equals 6. AX equals 6. See MCSS SSee MCSS Service Toolervice Tool Users manual TIP 31.4-1 for further information.

Users manual TIP 31.4-1 for further information. 30.3.

30.3. Use a volt Use a volt meter to check meter to check for 30 VDfor 30 VDC at U-43, C at U-43, and D43 relay and D43 relay contacts. contacts. See MCSS See MCSS Service Tool UsersService Tool Users manual TIP 31.4-1 for

manual TIP 31.4-1 for further information.further information. 31)4.

31)4. Push in the Push in the U relay and U relay and check for 30 check for 30 VDC at VDC at P4 - 8 of P4 - 8 of the MCSS-B the MCSS-B board. board. Also access the Also access the ServiceService Tool Function, MCSS, MONITO

Tool Function, MCSS, MONITOR, DISCRER, DISCRETE INPUTS, (M, 2, 1, 2) UTE INPUTS, (M, 2, 1, 2) UX. X. With the relay pushed in the displayWith the relay pushed in the display should be in upper case

should be in upper case letters (UX) and with the relay out the letters (UX) and with the relay out the display should be in display should be in lower case letters (ux).lower case letters (ux). See MCSS Service Tool Users manual TIP 31.4-1 for further information.

See MCSS Service Tool Users manual TIP 31.4-1 for further information. 32)5.

32)5. Push in the Push in the D relay and D relay and check for 30 check for 30 VDC at P4 VDC at P4 -10 of the -10 of the MCSS-B boaMCSS-B board. rd. Also access the Also access the ServiceService Tool Function, MCSS, MONITO

Tool Function, MCSS, MONITOR, DISCRER, DISCRETE INPUTS, (M, 2, 1, 2) DTE INPUTS, (M, 2, 1, 2) DX. X. With the relay pushed in the displayWith the relay pushed in the display should be in upper case

should be in upper case letters (DX) and with the relay out the letters (DX) and with the relay out the display should be in display should be in lower case letters (dx).lower case letters (dx). See MCSS Service Tool Users manual TIP 31.4-1 for further information.

See MCSS Service Tool Users manual TIP 31.4-1 for further information. 33)6.

33)6. Access the Service Tool Function, Access the Service Tool Function, MCSS, TEST, DMCSS, TEST, DISCRETE OISCRETE OUTPUTS, (MUTPUTS, (M, 2, 2, 1) UX , 2, 2, 1) UX to issueto issue MCSS commands to pick the U relay.

MCSS commands to pick the U relay. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for furtherurther information.

information. 34)7.

34)7. Access the Service Tool Function, Access the Service Tool Function, MCSS, TEST, DMCSS, TEST, DISCRETE OISCRETE OUTPUTS, (MUTPUTS, (M, 2, 2, 1) DX, 2, 2, 1) DX, to issue, to issue MCSS commands to pick the D relay.

MCSS commands to pick the D relay. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for furtherurther information.

information. 35)

35)SFTY07-SENSORS-DOOR ZONE SENSORSSFTY07-SENSORS-DOOR ZONE SENSORS 36)Event Counter label - SFTY07

36)Event Counter label - SFTY07 37)Event Log label

37)Event Log label - SENSORS- SENSORS 38)Fault Code LEDs lit - 1,2 and

38)Fault Code LEDs lit - 1,2 and 3 (binary 7)3 (binary 7)

The MCSS has determined that one or more Door Zone Sensor transducers are i

The MCSS has determined that one or more Door Zone Sensor transducers are i n the ON state instead of then the ON state instead of the OFF state.

OFF state. This test is performed in a window created by the SENSOR CThis test is performed in a window created by the SENSOR CHK BEGIN DISHK BEGIN DIST< normally 2000T< normally 2000 millimeters and SENSOR CH

(14)

Primary channel during the appro

Primary channel during the approach to the landing. ach to the landing. If the ON state is If the ON state is detected for 6 consecutive 40 milliseconddetected for 6 consecutive 40 millisecond cycles a SFTY07 (Door Zone Sensor Fault) is

cycles a SFTY07 (Door Zone Sensor Fault) is declared and Advanced Door Opening is disabled.declared and Advanced Door Opening is disabled. 1.

1. Access the Service Tool Function, Access the Service Tool Function, MCSS, SMCSS, SETUP, SAFETY ETUP, SAFETY PARAMETERPARAMETERS (M,2,3, 5)S (M,2,3, 5). Check that SE. Check that SENSNS CHK END-DI

CHK END-DIST is equal to 600. ST is equal to 600. See MCSS Service Tool Users manual TIP 31.See MCSS Service Tool Users manual TIP 31.4-1 for further information.4-1 for further information. 2.

2. Access the SerAccess the Service Tool Function, Mvice Tool Function, MCSS, SECSS, SETUP, SAFETUP, SAFETY PARATY PARAMETERS (METERS (m< 2, 3, m< 2, 3, 4). 4). Check that Check that SENSSENS CHK BEG-DI

CHK BEG-DIS is equal to 394 for a 1524 mm circumference SPPT drive sheave. S is equal to 394 for a 1524 mm circumference SPPT drive sheave. See MCSS Service ToolSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Users manual TIP 31.4-1 for further information. 3.

3. With the car With the car level at the landing, level at the landing, check to see check to see that all sensors athat all sensors are on. re on. The Door Zone The Door Zone indicator LEDs indicator LEDs ifif provided, on the Car Controller Inspection Panel should be ON.

provided, on the Car Controller Inspection Panel should be ON. Access the Service Tool Function, MCSS,Access the Service Tool Function, MCSS, MONITOR, DISC

MONITOR, DISCRETE INPUTS (M, 2, 1, 2) and verify that all Door Zone RETE INPUTS (M, 2, 1, 2) and verify that all Door Zone inputs are ON, upper case lettersinputs are ON, upper case letters (FID1, FODZ,

(FID1, FODZ, FID2, AID1, FID2, AID1, AODZ, AID2). AODZ, AID2). See MCSS Service Tool See MCSS Service Tool Users manual TIP 31.4-1 Users manual TIP 31.4-1 for furtherfor further information.

information. 4.

4. Move the car Move the car 600 millimeters away 600 millimeters away from the landing, from the landing, check to see check to see that all sensors that all sensors are OFF. are OFF. The Door ZoneThe Door Zone indicator LEDs, if provided, on the Car Controller Inspection Panel should be OFF.

indicator LEDs, if provided, on the Car Controller Inspection Panel should be OFF. Access the Service ToolAccess the Service Tool Function, MCSS, MONITOR, DISCR

Function, MCSS, MONITOR, DISCRETE INPUTS (m, 2, 1, 2) ETE INPUTS (m, 2, 1, 2) and verify that aland verify that al l Door Zone l Door Zone inputs are OFF.inputs are OFF. Lower case letters (fid1, fodz, fid2, aid1, aodz, aid2).

Lower case letters (fid1, fodz, fid2, aid1, aodz, aid2). See MCSS Service Tool users manual TIP 31.4-See MCSS Service Tool users manual TIP 31.4-1 for1 for further information.

5. Repair wRepair wiring or iring or replace senreplace sensors as sors as necessary,necessary, SFTY08 - SC RLY - SPEED RELA

SFTY08 - SC RLY - SPEED RELA YSYS

Event Counter label - SFTY08 Event Counter label - SFTY08 Event Log label - SC RLY Event Log label - SC RLY Fault Code LED lit - 4 (bi

Fault Code LED lit - 4 (binary 8)nary 8)

This fault can be generated in two possible ways: This fault can be generated in two possible ways: A.

A. MCSS determines tMCSS determines that the Speed Check (hat the Speed Check (SC) relay feed back contSC) relay feed back contacts are not in agreement acts are not in agreement with the state ofwith the state of the Speed Check relay command.

the Speed Check relay command. Or

Or B.

B. The elevator speed, as provided by the SPPT Primary channel, is greater than the CODThe elevator speed, as provided by the SPPT Primary channel, is greater than the CODE LEVELINGE LEVELING VELOCITY, multiplied by the NORMAL_VEL_TOL_PERCEN

VELOCITY, multiplied by the NORMAL_VEL_TOL_PERCENT, at the T, at the same time that the same time that the speed Check feedspeed Check feed back is high or there is

back is high or there is voltage present at SCS1 or SCS2.voltage present at SCS1 or SCS2. 1.

1. Use a volt Use a volt meter to check meter to check for 30 VDfor 30 VDC at the C at the SC Relay sense SC Relay sense contact. contact. See MCSS See MCSS Service Tool Users Service Tool Users manualmanual TIP 31.4-1 for further information.

TIP 31.4-1 for further information. 2.

2. Push in the Push in the SC relay and SC relay and check for 3check for 30 VDC at 0 VDC at P5 - 1 of P5 - 1 of the MCSS-the MCSS-B board. B board. Also access the Also access the Service ToolService Tool Function, MCSS, MON

Function, MCSS, MONITOR, DISCRITOR, DISCRETE INPUTS, (ETE INPUTS, (M, 2, 1, 2) SC. M, 2, 1, 2) SC. With the relay pushed in the displayWith the relay pushed in the display should be in upper case

should be in upper case letters (SC) and with the relay out the displletters (SC) and with the relay out the displ ay should be in ay should be in lower case letters (sc).lower case letters (sc). See MCSS Service Tool Users manual TIP 31.4-1 for further information.

See MCSS Service Tool Users manual TIP 31.4-1 for further information. 3.

3. Access the SerAccess the Service Tool Function, Mvice Tool Function, MCSS, SECSS, SETUP, CONTUP, CONTRACT/CODE TRACT/CODE (M, 2, 3, (M, 2, 3, 1). 1). Verify that Verify that CODECODE LEVELING VEL IS equal to 750 millimeters per second for ANSI applications, and 450

LEVELING VEL IS equal to 750 millimeters per second for ANSI applications, and 450 millimeters per secondmillimeters per second for CEN applications.

(15)

4.

4. Access the SerAccess the Service Tool Function, Mvice Tool Function, MCSS, SECSS, SETUP, SAFETUP, SAFETY PARATY PARAMETERS (METERS (m, 2, 3, m, 2, 3, 5). 5). Verify thatVerify that NORMAL VEL TOL percent is equal to 110, and SC RELAY TIME is equal

NORMAL VEL TOL percent is equal to 110, and SC RELAY TIME is equal to 8 (8, 40 millisecond to 8 (8, 40 millisecond cycles).cycles). See MCSS Ser

See MCSS Service Tool Users manual TIP vice Tool Users manual TIP 31.4-1 for further 31.4-1 for further information.information. 5.

5. Access the Service Tool Function, MCSS, SAccess the Service Tool Function, MCSS, SETUP, POS/VEETUP, POS/VEL PARAMETERL PARAMETERS (M, 2, 3, 4) to verify SPPS (M, 2, 3, 4) to verify SPPT POST POS SCALER is equal to 394 for a 1524 mm circumference (20 inch diameter) SP

SCALER is equal to 394 for a 1524 mm circumference (20 inch diameter) SPPT drive sheave. PT drive sheave. See MCSSSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Service Tool Users manual TIP 31.4-1 for further information. 6.

6. With the car With the car parked at a parked at a landing disconnect the discretlanding disconnect the discrete independent speed check e independent speed check input between the input between the SPPTSPPT and the MCS

and the MCSS-B phoenix conS-B phoenix connector J4-5. nector J4-5. The SC reThe SC relay should drop out. lay should drop out. See MCSS See MCSS Service Tool UsersService Tool Users manual TIP 31.4-1 for

manual TIP 31.4-1 for further information.further information. 7.

7. Access the Service Tool Access the Service Tool function, MCSS, function, MCSS, MONITOR, DISMONITOR, DISCRETE INPCRETE INPUTS (m, 2, UTS (m, 2, 1, 2) and verify that w1, 2) and verify that with theith the J4-5 wire removed the speed Check Drive Check (SC

J4-5 wire removed the speed Check Drive Check (SCDC) input is low, (lower case letters scdc). DC) input is low, (lower case letters scdc). See ServiceSee Service Tool Users manual TIP 31.4-1 for further information.

Tool Users manual TIP 31.4-1 for further information. 8.

8. Reconnect the wReconnect the wire from tire from the SPPT he SPPT to the MCSto the MCSS-B Phoenix connectS-B Phoenix connector J4-5. or J4-5. The SC relay The SC relay should pick up.should pick up. 9…Access the Service Tool

9…Access the Service Tool Function, MCSS, MONITOR< DISCRETE INPUFunction, MCSS, MONITOR< DISCRETE INPUTS (M, 2,1, 2) and TS (M, 2,1, 2) and verify that with theverify that with the (SCDC) input is high, (upper case letters SCD

(SCDC) input is high, (upper case letters SCDC). C). See MCSS Service Tool Users manual TIP 31.4-1 fSee MCSS Service Tool Users manual TIP 31.4-1 foror further information.

further information.

10. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (m

10. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (m, 2, 3, 2). , 2, 3, 2). Set the INSPECTIONSet the INSPECTION VELOCITY equal to 600 mm/s.

VELOCITY equal to 600 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for further information.urther information. 11. Run the car using the up or down buttons on the car Controller Inspection Panel.

11. Run the car using the up or down buttons on the car Controller Inspection Panel. Verify that the SC RelayVerify that the SC Relay remains energized.

remains energized. If the SC relay If the SC relay drops out, replace the Sdrops out, replace the SPPT processor board.PPT processor board. 12. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (M

12. Access the Service Tool Function, MCSS, SETUP, RIDE QUALITY (M, 2, 3, 2). , 2, 3, 2). Set the INSPECTIONSet the INSPECTION VELOCITY equal to 800 mm/s.

VELOCITY equal to 800 mm/s. See MCSS Service Tool Users manual TIP 31.4-1 for fSee MCSS Service Tool Users manual TIP 31.4-1 for further information.urther information. 13. Temporarily place a jumper across the

13. Temporarily place a jumper across the SC 13-14 contacts in the Safety Circuit. Run the car using SC 13-14 contacts in the Safety Circuit. Run the car using the up orthe up or down buttons on

down buttons on the Car Contthe Car Controller Inspection Panel. roller Inspection Panel. Verify that Verify that the the SC relay drSC relay drops out. ops out. If the SC If the SC relayrelay remains energized, at 800 mm/s, measure the voltage between MC

remains energized, at 800 mm/s, measure the voltage between MCSS-B J4-5 (+) to J4-6 (-). SS-B J4-5 (+) to J4-6 (-). If this voltage isIf this voltage is 5 VDC replace the S

5 VDC replace the SPPT Processor board. PPT Processor board. If the voltage is 0.0 VDIf the voltage is 0.0 VDC replace the MCSC replace the MCSS-B board. S-B board. See MCSSSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Service Tool Users manual TIP 31.4-1 for further information. 14. Remove all temporary jumpers and reset INSP

14. Remove all temporary jumpers and reset INSPECTION VELOCECTION VELOCITY equal to 400 mm/s. ITY equal to 400 mm/s. See MCSS ServiceSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Tool Users manual TIP 31.4-1 for further information. SFTY09- SFTY CH

SFTY09- SFTY CHN - SAFETY CHAIN BN - SAFETY CHAIN B ROKENROKEN Event Counter label - SFTY09

Event Counter label - SFTY09 Event Log label - SFTY CHN Event Log label - SFTY CHN

Fault Code LEDs lit - 1 and 4 (binary 9) Fault Code LEDs lit - 1 and 4 (binary 9) MCSS has determined that SA

MCSS has determined that SAFEOUT is active, EES relay driver (SAFEOUT is active, EES relay driver (SAFEOUT) is turned on. FEOUT) is turned on. SCS5 Safety ChainSCS5 Safety Chain sensing, has gone low or SCS6 Safety Chain sensing

sensing, has gone low or SCS6 Safety Chain sensing has gone high (SAFE) indication the opening has gone high (SAFE) indication the opening of the Safetyof the Safety Chain.

Chain. Note:

Note: A Safety Fault 9 wA Safety Fault 9 will be declared each time the car is ill be declared each time the car is placed on Access or Inspection operatplaced on Access or Inspection operation and eachion and each time a door lock is opened during

time a door lock is opened during inspection operation. inspection operation. This is due to the automatic This is due to the automatic dropping of the Doordropping of the Door Zone (DZ) relay the contacts of which are

(16)

1.

1. Operation of a safety sOperation of a safety switch is indicated if SCS1 and witch is indicated if SCS1 and SCS2 remain high wSCS2 remain high when SAFEIN goes lowhen SAFEIN goes low.. 2.

2. A failure of A failure of one of the one of the following: FGDS1, following: FGDS1, FGDS2, AFGDS2, AGDS1, or AGDS1, or AGDS2, is indicated GDS2, is indicated by: by: The DZ relay The DZ relay statusstatus indicates that the DZ and/or the ADZ relay i

indicates that the DZ and/or the ADZ relay i s not picked, and the s not picked, and the SC relay status indicates that the SC relay isSC relay status indicates that the SC relay is picked, and the SCS1 and/or the SCS2 sen

picked, and the SCS1 and/or the SCS2 sense point is low. se point is low. All relay status can be checked by accessing theAll relay status can be checked by accessing the Service Tool Function, MCSS, MONITOR, DISC

Service Tool Function, MCSS, MONITOR, DISCRETE OUTPUTS (M, 2, 1, 2). RETE OUTPUTS (M, 2, 1, 2). See MCSS Service ToolSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Users manual TIP 31.4-1 for further information. 3.

3. A failure of the door lock oA failure of the door lock or gate switch is indicated if the r gate switch is indicated if the DZ relay status indicates that DZ relay status indicates that the DZ and/or or tthe DZ and/or or thehe ADZ relay is not picked, t

ADZ relay is not picked, the FGDS and/or Ahe FGDS and/or AGDS sense point is low GDS sense point is low and the SC relay status and the SC relay status indicates that theindicates that the SC relay is picked, and the SCS1 and/or the SCS2 sense point is low.

SC relay is picked, and the SCS1 and/or the SCS2 sense point is low. All relay status can be checked byAll relay status can be checked by accessing the Service Tool Function, MCSS, MONITOR, DISCRETE O

accessing the Service Tool Function, MCSS, MONITOR, DISCRETE OUTPUTS (M, 2, 1, 2). UTPUTS (M, 2, 1, 2). See MCSSSee MCSS Service Tool Users manual TIP 31.4-1 for further information.

Service Tool Users manual TIP 31.4-1 for further information. SFTY10 - RECOVERS FAIL -

SFTY10 - RECOVERS FAIL - RECOVERY ATTEMPTRECOVERY ATTEMPTSS Event Counter label - SFTY10

Event Counter label - SFTY10 Event Log label

Event Log label - RECOVER FAIL- RECOVER FAIL Fault Code LEDs lit - 2

Fault Code LEDs lit - 2 and 8 (binary 10)and 8 (binary 10)

The MCSS contains a counter that records the number of times

The MCSS contains a counter that records the number of times that the Motion Logic State (MLS) is Pre Run (4)that the Motion Logic State (MLS) is Pre Run (4) while in the Motion Command Mode (MCM) is Recover (

while in the Motion Command Mode (MCM) is Recover (5). 5). If this counter exceeds the value in the label, MAXIf this counter exceeds the value in the label, MAX RECOVER TRIE

RECOVER TRIES, a Safety Fault S, a Safety Fault 10 is declared.10 is declared.

This fault requires a Power On Reset (POR) of the MCSS. This fault requires a Power On Reset (POR) of the MCSS. 1.

1. Access the SerAccess the Service Tool Function, Mvice Tool Function, MCSS, SECSS, SET UP, RT UP, RIDE QUAIDE QUALITY PARALITY PARAMETERS (METERS (M, 2, 3, M, 2, 3, 2). 2). Verify thatVerify that the value of Recover Velocity is equal to 600 mm/s.

the value of Recover Velocity is equal to 600 mm/s. See MCSS Service Tool Users manual TIP 31.See MCSS Service Tool Users manual TIP 31.4-1 for4-1 for further information.

2. Access the SerAccess the Service Tool Function, MCvice Tool Function, MCSS, SESS, SET UP, PT UP, POS/VEL PAOS/VEL PARAMETERS RAMETERS (M, 2, (M, 2, 3, 4). 3, 4). Verify that Verify that thethe value of RELEVEL ZONE D

value of RELEVEL ZONE DISTANCE is equal to 76 mm. ISTANCE is equal to 76 mm. See MCSS Service Tool Users manual TIP 31.See MCSS Service Tool Users manual TIP 31.4-14-1 for further information.

for further information.

3…Access the Service Tool Function, MCSS, SET UP , SAFETY PARAMETER

3…Access the Service Tool Function, MCSS, SET UP , SAFETY PARAMETERS (M, 2, 3, 5). S (M, 2, 3, 5). Verify that theVerify that the value of MAX RECOVE

value of MAX RECOVER TRIES is equal to 5. R TRIES is equal to 5. See MCSS Service Tool Users manual TIP 31.4-See MCSS Service Tool Users manual TIP 31.4-1 for further1 for further information.

information. 4.

4. Place the car Place the car on inspection and mon inspection and move the car ove the car more than 76 more than 76 mm away fmm away from the landing. rom the landing. Take the car Take the car off ofoff of inspection.

inspection. The car should recover to tThe car should recover to the floor. he floor. If the recovery fails trouble If the recovery fails trouble shoot the system to fshoot the system to find what isind what is inhibiting recovery.

inhibiting recovery.

SFTY11-HEARTBEAT- HEARTBEAT SFTY11-HEARTBEAT- HEARTBEAT

Event Counter label - SFTY 11 Event Counter label - SFTY 11 Event Log label - Heartbeat Event Log label - Heartbeat

Fault Code LEDs lit 1, 2 and 4 (binary 11) Fault Code LEDs lit 1, 2 and 4 (binary 11)

Before each run MCSS performs a check to verify the ability

Before each run MCSS performs a check to verify the ability to drop the safety chain via to drop the safety chain via the "CIO" relay, thethe "CIO" relay, the status of the Drive and Brake Disconnect (DBD) signal, and the status of

status of the Drive and Brake Disconnect (DBD) signal, and the status of the Front and Alternate Gate and Doorthe Front and Alternate Gate and Door Status (FGDS and AG