ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 50 of 147

6.2 Event Log

6.2.1 General Description
All events detected by the drive software are stored in an event log that is accessible through the
service tool. There are two event logs: the current log contains information about events which
have been detected since the most recent POR, and the saved log which is the EEPROM backup
of the events from before the most recent POR.
 Both the current log and the saved log have the same format. Each entry in the log contains
the event code, the name of the event, and the elapsed time since POR that the event was
detected:

705 E2 Invalid
0000:00:00:00.04

The time is in the format: DDDD:HH:MM:SS.SS.

 Enter menu 2-1 to access the current log, events that have occurred since the most recent
POR.
 Enter menu 2-2 to access the saved log, events that occurred before the most recent POR.
 Enter menu 2-3 to clear the current event log.

Clear Log?
Enter to clear.

Hit SHIFT-ENTER to clear.

 Enter menu 2-4 to clear a blockage of the drive that occurs when certain events are
detected.
6.2.2 Event-Specific Data
When viewing an event, event-specific data can be accessed by using the following service tool
keys:

Key Example: Before Example: After

Description
Sequence Key Sequence Key Sequence
Navigates down one level in the Power On Drive State @Evt
event tree to access event-specific
SHIFT- 0000:00:00:00.04 IDLE
data.
ENTER
705 E2 Invalid Go to XX
If the fault is: 705 E2 Invalid 0000:00:00:00.04 Invalid Param
Scrolls forward through event- Drive State @Evt Number of Runs
GO ON
specific data. IDLE 12
Scrolls forward through event- Number of Runs Event Response
GO ON
specific data. 12 Emergency Stop
SHIFT– Scrolls in reverse through event- Event Response Number of Runs
GO BACK specific data. Emergency Stop 12
Navigates up one level in the Number of Runs Power On
CLEAR
event tree. 12 0000:00:00:00.04

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 51 of 147
Event-specific data that is available is shown in the table:

Service Tool
Description
Display
This shows the state of the drive when the event was logged. Note that
Drive State @Evt
this is the state when the event is logged rather than the state when the
IDLE
event is detected.
Number of Runs This counter is incremented if the last run had no events logged other
12 than “001 New Run”.
Event Response
The response of the drive when the event was detected.
Emergency Stop
The number of times the fault was logged since the event log was
cleared. The counter is incremented each time the fault is logged. Note,
the counter is incremented (and event logged) only once in a run even if
the event is detected multiple times during this run.
Event Count:
1. This count is different from the occurrence count that is used to
12
block the drive. See section 6.2.3 for a description of the
occurrence counters that cause blocking.
2. The event counters and logs are cleared via M26.
3. The event count is not cleared at POR.

6.2.3 Shut Down Error Handling

Some error events cause a shut-down (immediate stop) with an additional inverter blockage
immediately or after repeated occurrences in sequence. In case of an inverter blockage, the DC –
link will be disconnected from the mains supply.

WARNING! Before starting the drive again, the error reason must be found and
solved. Otherwise, the inverter can be seriously damaged.

In case of blockage, do the following:

1. Establish service tool connection to the drive.
2. Find out the reason that caused the blockage by viewing the event log menu 2-1.
3. Clear the blockage by going to menu 2-4 and following the prompt:

Clear Block?
Enter to clear.

Hit SHIFT-ENTER to clear.

 Note that the error “517 DDP Error” cannot be cleared using this option. It must be cleared by
the power-reset method (POR) or by software-reset menu 2-5 (see Section 6.2.5).
 Some errors cause blockage only as long as the failure is still present, e.g., if an over heat
occurs then the drive is allowed to do runs again as soon as the drive has cooled down. See
the event descriptions in Section 6.2.8 for further details.

6.2.4 Occurrence Counters

As stated above, some errors have an internal counter that is incremented every time that error
occurs in succession. When the counter has reached a limit, the drive will block itself. The
specific errors that have such counters and the corresponding limits are indicated in the detailed
event descriptions in Section 6.2.8. For example, “E4” means that 4 occurrences in series lead to
a drive blockage.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 52 of 147

Applicability
 The counters are applicable only when the drive is in CAN mode (Interface Type = 1). They
are not applicable when the drive is in MCSS mode.
 The counters are not applicable during TCI and ERO runs; all the counters are reset to zero
when the car is set to TCI or ERO.

Clearing of Occurrence Counters

The occurrence counters are cleared automatically after several consecutive runs without error.
The detail action taken is:
 Two successful runs without error are required before any counters are decremented. After
two successful runs, all the counters are decremented by one for each successful run. The
only exceptions to this are for the events “512 Missing Vane” and “513 No PRS Trans”. For
these two events, five successful runs without error are required before these counters are
decremented (this is so because these faults result in correction runs, but these faults are not
checked during correction runs).

The occurrence counters are manually cleared by any of the following actions:
o The car is placed on TCI or ERO.
o Clear Blockage, menu 2-4
o Software reset, menu 2-5.
o POR

6.2.5 Software Reset

The DSP on the control board can be reset through service tool commands. This is intended to
be used when performing software upgrades to the control board.

The reset is accessed in menu 2-5. A confirmation is required:

Reset DSP?
Enter to reset.

Hit SHIFT-ENTER to reset.

Note, the reset is only allowed when the drive is in the IDLE state or less.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 53 of 147

6.2.6 Event Response

Every event detected by the drive has a defined response, which is summarized in Table below.

Event Abbrev
-iation
Description
Response
INFO I The event is logged for information only and no action is taken by the drive.
The event is logged for warning only and limited or no action is taken by the
WARN W
drive.
The event is logged, the run is allowed to complete, and the drive enters the
ShutDown state. This is used by the drive to communicate to the GECB that the
drive had encountered a fault. The drive sets the Stop-an-Shutdown (SAS) flag
until the fault condition clears.
COMP C
 In CAN mode, the drive will NOT attempt another run until the fault condition
clears.
 In MCSS mode, the drive will attempt another run if requested by the
controller, except for thermal faults.
This response is applicable only for CAN–type controllers during normal
runs.
 The event is logged and the target is changed to the next committable.
 PRS+LS signals are ignored for position corrections.
 The drive sets the stop and shutdown (SAS) flag until the fault condition
clears.
 The run to the next committable will continue only if the fault is determined to
NEXT-
be triggered by a failure of the GECB, a failure “both LS active” or a failure of
COMMITT NC
the CAN communications. This is determined by checking if a follow-up
ABLE
event event “511 1LS & 2LS !” was also logged or the CAN message
“DrHwySignals” has timed out (=event “906 No LS Msg”). Otherwise, the
fault response will transition to a timed decel (DECEL).
 When the run ends, the drive passes through SHUTDOWN and position is
invalidated.
During other run modes than NORMAL, the fault reaction is an immediate
timed deceleration (DECEL).
This response is applicable only for CAN–type controllers.
The event is logged, the run is terminated with a timed decel, and the drive
enters the ShutDown state. The deceleration rate is 105% of contract
deceleration rate with a minimum of 0.5 m/sec^2.
DECEL D
 The drive remains in the ShutDown state until the fault condition clears. The
drive will NOT attempt another run until the fault condition clears.
 For momentary faults, the fault is automatically cleared after the sheave has
stopped, subject to a minimum 250 ms.
The event is logged and the run is immediately terminated by the drive.
 In CAN mode, The drive enters the ShutDown state for certain faults. It
remains in this state until the fault clears, the sheave has stopped, and a
minimum of 100ms. Some faults will set the Stop-an-Shutdown (SAS) flag.
The drive will NOT attempt another run until the fault condition clears.
ESTOP E  In MCSS mode, the drive will attempt another run if requested by the
controller.
 When the estop was caused by a command to stop or by the safety chain
opening, the drive enters Wait for Safety state.
 In either case, if the fault was not a converter-related fault, the converter will
remain active until the sheave has stopped.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 54 of 147

The event is logged, the run is immediately terminated by the drive, and the drive
enters the Power Down state. The drive sets the Stop-an-Shutdown (SAS) flag.
SERVICE S The drive is blocked from further runs. A power on reset (POR) is required for
the drive to recover from this condition or must be reset through the service tool
menu 2-4.
This response is applicable only for CAN–type controllers.
ENDRUN ER The event is logged, the run or brake lift is aborted using a normal deceleration
profile (jerk-in/out), and the drive does not enter the ShutDown state.
This response is applicable only for CAN–type controllers.
The event is logged, the run or brake lift is aborted using a normal deceleration
profile (jerk-in/out), and the drive enters the ShutDown state.
ENDRUN +
ERS  The drive remains in the ShutDown state until the fault condition clears. The
SHD
drive will NOT attempt another run until the fault condition clears.
 For momentary faults, the fault is automatically cleared after the sheave has
stopped and a minimum of 250 ms time.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 55 of 147

6.2.7 Event Overview

Information Events Converter Current 417 Bk SW Oct 601 Inv Tmp Over
000 Power On Faults 418 Bk lft tmout 602 Inv Tmp Fail
001 New Run 200 Cnv SW Oct 419 Bk drp tmout 603 Cnv Tmp Warn
002 SPARE 201 Cnv Id Error Motion Faults 604 Cnv Tmp Over
003 Stack Warn 202 Cnv Iq Error 500 Overspeed 605 Cnv Tmp Fail
004 Power Down 203 Cnv Ix Offst 501 Pos Tracking 606 Mtr Tmp Over
005 Extern FLASH 204 Cnv Iy Offst 502 Vel Tracking 607 Reactor Temp
006 Extern RAM 205 Cnv Gate Flt 503 LRT Motion 608 DBR Tmp Over
007 OMU Present 206 Cnv HW Oct 504 Enc Pos Err 609 AC/DC Calibr
008 OMU Prohibit 207 Cnv Gnd Flt 505 SPARE 610 Batt Ovr Tmp
009 Manual Mode 208 Bus Cap Fail 506 Stopping Err 611 MTC/RTC Flt
010 B_MODE 209 DC Link OCT 507 Pos at 1LS State Faults
011 Battery Mode 210 Cnv IPM Flt 508 Pos at 2LS 700 Safety Chain
012 LearnRun REQ 211 Battry Chrgd 509 Floor at 1LS 701 No Man Input
013 Reset DSP 212 Cnv Vmag Flt 510 Floor at 2LS 702 Prechrg Time
014 Log Cleared Voltage Faults 511 1LS & 2LS ! 703 S Rly Fault
015 AutoTun Mode 300 DC Bus Over 512 Missing Vane 704 DBD Fault
016 Earthquake 301 DC Bus Under 513 No PRS Trans 705 E2 Invalid
017 Block Cleard 302 VAC Over 514 Enc <> Vane 706 E2 Write Lim
018 ALWA CONVRGD 303 VAC Under 515 NTSD failed 707 ADC Offset
019 ALWA ERROR 304 VAC Imbal 516 Corr failed 708 Cmd to Abort
020 ALWA RESET 305 PLL Unlock 517 DDP Error 709 PRS SigNoise
021 ALWA DIVERGD 306 Single Phase 518 BeltCmp Wrng 710 UIB DIB Err
026 UCM-EN clear 307 PLL Freq Rng 519 RlvPermitErr 711 DBD Shutdown
Inverter Current 308 Welded Mx/Px 520 Rllbck Start 712 PostTrq Time
Faults 309 Vscales off 521 Rllbck Stop 713 Block by xxx
100 Inv SW Oct 310 AC Brown-out 522 ManualRescue 714 B_MODE Err
101 Inv I Imbal 311 AC All Err 523 Moved at POF 715 ARO BatPower
102 Inv Id Error 312 DBTR ShrtErr 524 No Enc Signl 716 Illegal Cmd
103 Inv Iq Error 313 AC/DC Calib 525 NoRlv SpdChk 717 Triac Stuck
104 Inv Ix Offst 314 Cnv Res FltV 526 NoRlv TooMny 718 PRS Config
105 Inv Iy Offst 315 Cnv Res FltF 527 NoRlv LostDZ 719 OARO Blocked
106 Inv Iz Offst Brake Faults 528 Profile Err 720 Welded BLV
107 Inv Gate Flt 400 Brake S1 SAS 529 No enc fdbck 721 PwmExistsFlt
108 Inv HW Oct 401 Brake S2 SAS 530 No enc tmout 722 E2 Read CkSm
109 Overload 402 Brake Status 531 PRS Sigs 1LS 723 UCM in Run
110 Drive Limit 403 Brake BY 532 PRS Sigs 2LS 724 UCM in Slide
111 No Id fdbk 404 Brake I Off 533 ARO Overspd 725 UCM BrkBlock
112 No Iq fdbk 405 Brake I Drop 534 ABL Abort:LW 726 Tmout SfcMsg
113 Inv IPM Flt 406 Brake I Hold 535 Timeout PTR 727 TOStp SfcMsg
114 Curr Ovrload 407 Brake I Max 536 Timeout LB Task Overrun Faults
115 Brk Chop Err 408 Brk S1 ESTOP 537 No EndRunCmd 800 1ms Task
116 Inv HW Ovt 409 Brk S2 ESTOP 538 Abort:EndRun 801 10ms Task
117 Inv Pfai Flt 411 Brk S1 DECEL 539 LvTransUnclr 802 40ms Task
118 Overload WAR 412 Brk S2 DECEL 540 Shock Detect 803 Cnv Task
119 Desat Err 413 Bk Desat Err 541 SinCos Warng 804 Inv Task
120 Output Cur 414 Bk Bus Over 542 Decel Req Fl 805 200ms Task
415 Bk Bus Under Temperature Faults Communication
416 Bk fbk tmout 600 Inv Tmp Warn Faults

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 56 of 147
900 MCSS Timeout
901 SVC Tool Err
902 CAN Err
903 E2 CommWrite
904 LWSS Timeout
905 LWSS Bad Val
906 No LS Msg
907 Primary CRC
908 Drive CRC
909 CAN BusOff
910 CAN OPB_Init
911 CAN TxQ Full
912 No FloorInfo
913 MCSS Warning
914 Power E2 Err
915 LWSS not cal
916 Power E2 Rng
917 CPLD Ver Flt
918 ARO Ver Flt
919 Powrbrd miss
920 Micro ChkSum
921 FPGA ChkSum
922 FLASH Warn
923 FPGA Warn
924 Micro Warn
925 No CAN-PRS
926 CAN PRS Msg
927 DSP2FPGA Wrn
928 DSP2FPGA Flt

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 57 of 147

6.2.8 Event Menu Detailed Descriptions

The following list includes all events detected.
Column 1: The name of the event, including the event code
Column 2: The response to the event, followed by the number of occurrences in series that leads
to a drive blockage (see Section 6.2.3).
Column 3: A description of the event including possible causes and potential solutions.

6.2.9 Information Events

SVT Display Description
000 Power On I Power was applied to the drive.
001 New Run I A new run was initiated.
002 SPARE I Not used.
003 Stack Warn W The stack usage has exceeded an acceptable limit.
004 Power Down I The power fail signal in the hardware was activated.
005 Extern FLASH W The GDCB FLASH memory has failed.
006 Extern RAM W The GDCB RAM memory has failed.
007 OMU Present I Indicates that a valid OMU is plugged into the drive OMU port at power-up.
008 OMU Prohibit I Indicates that an OMU software upgrade is prohibited because the previous
run was TCI. The status of the permissive can be viewed in the SVT
parameter OMU Prohibited.

Solution
If this fault occurs, it can be cleared by performing an ERO run (the ERO
run confirms that the mechanic is in the hallway).
009 Manual Mode I Indicates that the drive is in Manual Mode.
010 B_MODE I Applicable only when Interface Type = 2 or 3.
Applicable only when “ARO Type” = 2 or 3.
Logged when the drive received “B_MODE signal” from Battery controller.
011 Battery Mode I Applicable only when Interface Type = 1.
Indicates the drive is in battery (ARO-EN) mode operating on 48Vdc battery
supply. Logged when the drive received SpbMode message “BatteryMode”
from SPBC3.
012 LearnRun REQ I Applicable only when Interface Type = 1.
Indicates that the floor table in the drive is invalid and that a new learn run
is required.
013 Reset DSP I The DSP was reset using the SVT menu 2-5.
014 Log Cleared I The event log was cleared using SVT menu 2-3.
015 AutoTun Mode I The drive is in Auto Tune mode.
016 Earthquake | Applicable only when Interface Type = 2 or 3.
Indicates earthquake detection. This mode is initiated by the recovery
signal from MCSS. In this mode, shock detection and the torque pulsation
detection are activated.
017 Block Cleard I Indicates that a blockage condition was cleared either via the service tool
menu or by a CAN message.
018 ALWA CONVRGD I Indicates that ALWA has converged with a fixed gain and offset.
019 ALWA ERROR I Indicates that ALWA has an algorithmic error.
020 ALWA RESET I Indiactes either an automatic reset by the algorithm or through the service
tool was done. This resets the gain and the offset to 1 and 0 respectively.
021 ALWA DIVERGD I Indicates that the ALWA algorithm has not converged.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 58 of 147
026 UCM-EN clear I Applicable only when Interface Type = 1 and UCM-EN on/off = 1.
Indicates that a blockage according to 723 UCM in Run, 724 UCM in Slide
or 725 UCM BrkBlock has been cleared. .

6.2.10 Inverter Current Faults

SVT Display Description
100 Inv SW Oct E4 The magnitude of the inverter current exceeded an allowed threshold.

Possible Causes & Solutions

 Incorrect motor phasing  change parameter Motor Phase 0/1.
 Shorted motor phase  check motor wiring continuity.
 The fault threshold can be temporarily adjusted by the parameter
Inv I Limit %.
Applicable when Interface Type = 0 or 1:
OCT(A) = Drive I fullscale * Inv I Limit %* 0.9 * 1.05
(Drive I fullscale: 402 80A 404110A)
Applicable when Interface Type = 2 or 3:
OCT(A) = Drive I fullscale * Inv I Limit %* 0.9 * 1.25
101 Inv I Imbal E4 The sum of the three motor currents exceeded 10% full-scale current.

Possible Causes & Solutions

 Ground fault  check there are no motor phases shorted to ground.
 Signal noise  check that wiring guidelines are followed.
102 Inv Id Error E4 The indicated inverter current regulator error exceeded an allowable
103 Inv Iq Error threshold.

Possible Causes & Solutions

 Current regulators are not tuned correctly  check proper motor
parameter settings (see Section 9).
104 Inv Ix Offst E The indicated inverter phase current offset exceeded 5% of full-scale.
105 Inv Iy Offst
106 Inv Iz Offst Possible Causes & Solutions
 Defective circuit  change drive package (if occurs permanently).
107 Inv Gate Flt E4 NOT applicable when Drive Type is 25A.
An inverter IGBT gate supply voltage fault was detected.

Possible Causes & Solutions

 Defective or shorted gate power supply  change drive package (if
occurs permanently).

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 59 of 147
108 Inv HW Oct E4 NOT applicable when Drive Type is 25A.
For 60A V.2 - drives:
The power section has detected a fault and set the discrete input
(ERR1/INV_FLT: P1-12 ) to the GDCB. Because this input is shared
by both HW Overcurrent and HW Overvoltage errors, the measured
DC bus voltage is used to distinguish between them:
- DC bus voltage is below a specified threshold
--> this fault was declared.
- DC bus voltage is above a specified threshold
--> 116 Inv HW Ovt would have been declared.

For all other drives except the 25A drive:

The inverter current exceeded a preset level, detected via hardware,
(ERR1/INV_FLT: P1-12 ) to the GDCB.

Possible Causes & Solutions

 Incorrect motor phasing  change parameter Motor Phase 0/1.
 Shorted motor phase  check motor wiring continuity.
109 Overload E4 An overload condition has been detected. The drive exceeded the
maximum time allowed operating at the rated current of the motor.

Possible Causes & Solutions

 Excessive friction in system  check for dragging brake or hoistway
interference.
 The drive is undersized for the installed duty  confirm system inertia.
 The fault threshold can be adjusted by the parameters: Overload
sec, Rated mtr i Arms, and Rated Acc I PU, but should not be
increased by more than 10%.
110 Drive Limit W The drive is operating at its rated current limit.
111 No Id fdbk E4 An error has been detected with the current feedback of the inverter during
112 No Iq fdbk magnetization of the motor at the beginning of the run.

Possible Causes & Solutions

 Open motor phase  check motor wiring continuity.
 Bad current sensor  return unit for service.
See parameters Vd out thresh PU and Vq out thresh PU.
113 Inv IPM Flt E4 Applicable only when Drive Type is 25A or LCRD.
Indicates a fault has been detected from the inverter Intelligent Power
Module (IPM).

Possible Causes & Solutions

 Defective or shorted gate power supply  change drive package (if
occurs permanently).
 Incorrect motor phasing  change parameter Motor Phase 0/1.
 Shorted motor phase  check motor wiring continuity.
114 Curr Ovrload E4 Not used (was applicable only for non-regen drives).
115 Brk Chop Err E4 Not used (was applicable only for non-regen drives).

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 60 of 147
116 Inv HW Ovt E4 Applicable only for 60A V.2 drives.
The power section has detected a fault and set the discrete input
(ERR1/INV_FLT: P1-12 ) to the GDCB. Because this input is shared by
both HW Overcurrent and HW Overvoltage errors, the measured DC bus
voltage is used to distinguish between them:
- DC bus voltage is above a specified threshold
--> this fault was declared.
- DC bus voltage is below a specified threshold
--> 108 Inv HW Oct would have been declared.
117 Inv Pfai Flt E4 Applicable only for 60A V.2 drives.
Inverter PWM activity has been detected during IDLE (when S1 & S2 are
dropped):
 after 2 seconds in IDLE the inverter PWM driver was still active;
 or after 4 seconds in IDLE the signal PF_IGBT: P1-13 was LOW which
indicated a still active IGBT power supply although it should be
switched OFF.
Possible Causes & Solutions
 Defective gate driver or power supply  change drive package (if
occurs permanently).
118 Overload WAR E See 109 Overload.
119 Desat Err E4 The inverter current and the converter current exceeded a preset level,
detected via hardware.
120 Output Cur E1 This fault indicates the motor has currents while Sx dropped. This
monitoring is a requirement for GB compliance.

6.2.11 Converter Current Faults

SVT Display Description
200 Cnv SW Oct E4 The magnitude of the converter current exceeded an allowed threshold.

Possible Causes & Solutions

 Defective hardware  change drive package (if occurs permanently).
 The fault threshold can be temporarily adjusted by the parameter
Cnv I Limit %.
Applicable when Interface Type = 0 or 1:
OCT(A) = Drive I fullscale * Cnv I Limit %* 0.9 * 1.05
(Drive I fullscale: 402 80A 404110A)
Applicable when Interface Type = 2 or 3:
OCT(A) = Drive I fullscale * Cnv I Limit %* 0.9 * 1.25
201 Cnv Id Error E4 The indicated converter current error exceeded 30% of full-scale.
202 Cnv Iq Error
Possible Causes & Solutions
 Current regulators are not tuned correctly  check proper parameter
settings (see parameter Cnv Custom 0/1).
203 Cnv Ix Offst E The indicated converter phase current offset exceeded 5% of full-scale.
204 Cnv Iy Offst
Possible Causes & Solutions
 Defective circuit  change drive package (if occurs permanently).

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 61 of 147
205 Cnv Gate Flt E4 NOT applicable when Drive Type is 25A.
An inverter IGBT gate supply voltage fault was detected.

Possible Causes & Solutions

 Defective or shorted gate power supply  change drive package (if
occurs permanently).
206 Cnv HW Oct E4 NOT applicable when Drive Type is 25A.
The converter current exceeded a preset level, detected via hardware.

Possible Causes & Solutions

 Defective hardware  change drive package (if occurs permanently).
207 Cnv Gnd Flt S Applicable only when Drive Type is 60A.
A ground fault was detected on the converter.

Possible Causes & Solutions

 Ground fault  disconnect drive from utility power and check that there
are no phases shorted to ground.
208 Bus Cap Fail S The estimated power loss in the drive exceeded a limit. This indicates that
excessive power is being dissipated in the drive and is a strong indication
that a DC link capacitor has failed. The threshold for this fault is set by the
SVT parameters Ploss Thr pre %, Ploss Thr idle %, and Ploss
Thr run %.
209 DC Link OCT S Applicable only when Drive Type is 40A.
Indicates excessive DC link current.

Possible Causes & Solutions

 Shorted motor phase  check motor wiring continuity.
 Ground fault  disconnect drive from utility power and check that there
are no phases shorted to ground.
210 Cnv IPM Flt E4 Applicable only when Drive Type is 25A or LCRD.
Indicates a fault has been detected from the converter Intelligent Power
Module (IPM).

Possible Causes & Solutions

 Defective or shorted gate power supply  change drive package (if
occurs permanently).
 Defective IPM hardware  change drive package (if occurs
permanently).
 Ground fault  disconnect drive from utility power and check that there
are no phases shorted to ground.
211 Battry Chrgd E4 Applicable only during ARO (EN) mode.
The drive detected charging current into the battery during ARO, which is
not allowed. The threshold for the charging currenmt is controlled by the
parameter Max Bat Chrg I A.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 62 of 147
212 Cnv Vmag Flt E Generally, this fault occurs when power is removed from the drive AC input
during a regenerative run. This fault may also occur in concert with certain
loss of safety chain events, but this should not be a concern (loss of safety
chain causes an estop anyways). This fault management is designed to
protect other in-ciruit controller components when the AC line is lost during
a regenerative run.

If this fault occurs in such a way that interrupts normal elevator operation,
then this condition should be reported, and the fault management can be
disabled by increasing the Cnv Vmag Thrs PU parameter.

This fault management is active only when the drive is regenerating and
only when the nominal AC line voltage parameter AC Main Vrms is set
<= 400. This fault management is not active when Low Volt Op 0/1 is set
to 1.

6.2.12 Voltage Faults

SVT Display Description
300 DC Bus Over E3 The DC bus voltage was greater than 108% of the nominal bus voltage of
750 VDC.
301 DC Bus Under E6 The DC bus voltage exceeded a limit. The limits are:
For 415 < Vac <= 480, limit = 70% of nominal (750).
For 380 <= Vac <= 415, limit = 309 Vdc.
For Vac < 380, limit = 70% of nominal (750).
The nominal ac voltage is determined by the EEPROM parameter: AC
Main Vrms.
302 VAC Over C The AC line voltage exceeded a limit. The limits are:
For 415 < Vac <= 480, limit = 112% of nominal.
For 380 <= Vac <= 415, limit = 477 Vrms.
For Vac < 380, limit = 115% of nominal.
The nominal voltage is determined by the EEPROM parameter: AC Main
Vrms.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 63 of 147
303 VAC Under C This fault indicates the AC line voltage was below a limit. The limit value
depends on whether the drive’s “brown-out” functionality is enabled or not:
- For CAN interface (interface type 1), where profile generation is
internal to the drive, the brown-out function is enabled.
o If the AC line voltage falls 15% below nominal, the brown-
out function is activated, the speed is reduced, and the
“310 AC Brown-out” warning is logged.
o If the AC line voltage falls to 30% below nominal, then
additional speed reduction occurs and the “303 VAC
Under” fault is logged.

- For other interfaces, where profile generation is external to the

drive, the brown-out function is disabled.
o If the line voltage falls to 15% below nominal, then the “303
VAC Under” fault is logged.

- In both cases, the fault response to “303 VAC Under” is:

o complete the current run,
o go to drive state shutdown,
o exit shutdown as soon as the fault clears. The fault is self
clearing.

- “Nominal” voltage is defined as follows:

o 380 Vrms for 380 <= Vac <= 415;
Vac otherwise,
where Vac = EEPROM parameter: AC Main Vrms
304 VAC Imbal C The AC line input voltages differ from each other by more than 25%.
305 PLL Unlock E The phase lock loop on the AC input voltage has unlocked. This is likely to
occur when you try to run with a damaged IGBT.
This fault sets the SAS flag.
306 Single Phase S This fault is declared when the drive is set to single-phase mode, and the T
phase is connected to a live input. The power during single-phase
operation should be connected to R and S phases only and the T-phase
should be left open. See EEPROM parameter: Single Phase 0/1
307 PLL Freq Rng E This fault is declared when the drive ac line frequency estimate is outside
of a frequency band specified by the parameter PLL freq band Hz for a
amount of time specified by the parameter PLL freq time ms, while
there is no PLL unlock fault. This fault is logged whenever the AC line is
disconnected. Repeated logging may be an indication of a problem with the
AC line.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 64 of 147
308 Welded Mx/Px S When the drive enters the power down state, if the DC Bus voltage does
not drop below a voltage threshold within a (drive-type depending) wait
time, the system will declare that the MX and/or PX contacts may be
welded.

Warning:
Do not cycle power to drive until fault is verified.
Check the “Inp:Vrms Vdc” SVT display to verify whether the Vdc is
actually stuck to a high value (1.41 times the Vrms value) while the state of
MX and PX in the “MX PX DX BX” SVT display is actually “0”. If these
conditions are met (high Vdc and “0” for both MX and PX), then DO NOT
ATTEMPT TO CYLE POWER TO THE DRIVE. This drive may have a real
welded MX or PX condition that needs to addressed. For this condition,
power down, lock out/tag out energy source, and ship drive back to factory.
309 Vscales off W This fault is logged when the measured AC line voltage and measured DC
bus voltage disagree significantly. This check is performed only after M1 is
picked after the bus has had enough time to settle to its quiescent value.
This fault may indicate that either of the following EEPROM parameters is
not set correctly: DC Bus fscale V, AC Line fscale V.
310 AC Brown-out W Applicable only for Interface Type 1.
This warning indicates that the ac line has dropped 15% below the nominal
value. The drive will continue to run under the "Brown Out" event with
reduced motion profiles.
When the ac line drops 30% below nominal, 303 VAC Under fault is
logged, in which case speed will be further reduced and the drive will finish
the current run and not accept any further runs until the fault clears. See
event “303 VAC Under” for more details.
311 AC All Err E This fault can occur for one of two reasons:

1. The AC line voltage exceeded a limit above the 302 VAC Over threshold.
The limits are:
For 415 < Vac <= 480, limit = 125% of nominal.
For 380 <= Vac <= 415, limit = 519 Vrms.
For Vac < 380, limit = 125% of nominal.
The nominal voltage is determined by the EEPROM parameter: AC Main
Vrms.
OR
2. The following three faults occur at the same time while PTR is active:
302 VAC Over AND
304 VAC Imbal AND
307 PLL Freq Rng
312 DBTR ShrtErr C Applicable only for ARO Type=NIARO (JIS) and Generator Mode.
This fault is set for detecting the short of DBTR.
When using a generator, set Generator Mode for 1.
When using NIARO mode, set ARO Type for 3.
Check DBTR if it has broken.
313 AC/DC Calib I Applicable only when Low Volt Op 0/1 = 1.
This fault is active only in low voltage operation mode. This indicates that
the calibration process ac voltage sensor versus dc voltage sensor resulted
with a cross calibration factor that is either larger than 1.5 or less than 0.5.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 65 of 147
314 Cnv Res FltV E This fault management is active only when the event 304 VAC Imbal is
active. This fault occurs when a converter voltage transient occurs that
exceeds a threshold that is at least 25% greater than the AC Main Vrms
parameter setting. If this fault occurs, then check that the 3 phase AC input
is present and is reasonably balanced.
315 Cnv Res FltF E This fault occurs when a voltage resonance occurs at the AC input of the
drive due to an intermittent loss of an input phase. If this fault occurs, then
check that the 3 phase AC input is present, connected well, and is
reasonably balanced. This fault is active only for the 406R Version 2 drive.

6.2.13 Brake Faults

SVT Display Description
400 Brake S1 SAS C4 The indicated brake switch is in the wrong state. This is checked both
401 Brake S2 SAS when the drive is in the Idle state and when the drive is running.
These faults result in complete the run fault response and set the SAS
flag.

Note: this event is also applicable when Brk Sw Type 0-4 is set to 0 or 4
where constant states are required on BS1 and BS2 inputs.

Possible Causes & Solutions

 Incorrect parameter value  verify correct value of Brk Sw Type 0-4.
 Incorrect brake switch wiring  check brake switch wiring.
 Brake not lifting  check brake wiring & brake power supply.
 Insufficient time allowed  see parameters Brk Pick Time ms and Brk
Setl Time ms.
402 Brake Status E4 Applicable only when Brk Cnt Type 0-3 is set to 0.
The brake status feedback from the brake module is not in the correct
state.
403 Brake BY E4 One or both of the normally-closed BY contacts are not in the correct
state. The BY relays should be energized when PTR is active, before the
lift brake command is initiated.
Note: Actual name is BR relay but still referred here as BY relay for
downward compatibility.
Possible Causes & Solutions
 Incorrect wiring to brake module  check brake module wiring.
 Incorrect brake power supply  check brake power supply & wiring.
 Adjust SVT parameter: SX Pick Time ms
404 Brake I Off E4 Applicable only when Brk Cnt Type 0-3 is set to 2-3.
When using the internal brake control, this fault is logged when the brake
current feedback offset compensation exceeds a certain amount. The
threshold is adjustable with Brk I Offset A.
405 Brake I Drop E4 Applicable only when Brk Sw Type 0-4 is set to 4 and Brk Cnt
Type 0-3 is set to 2-3.
When the internal brake control drops the brake, this fault is logged if the
brake current feedback exceeds a threshold specified by the service tool
parameter Brk Min Hold I A.
406 Brake I Hold E4 Applicable only when Brk Sw Type 0-4 is set to 4 and Brk Cnt
Type 0-3 is set to 2-3.
When the internal brake control picks the brake, this fault is logged if the
brake current feedback is less than a threshold specified by the service
tool parameter Brk Min Hold I A.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 66 of 147
407 Brake I Max E4 Applicable only when Brk Sw Type 0-4 is set to 4 and Brk Cnt
Type 0-3 is set to 2-3.
This fault is logged if the internal brake control current feedback exceeds
a threshold specified by the service tool parameter Brk I Max A.
408 Brk S1 ESTOP E4 The indicated brake switch is in the wrong state. This is checked both
409 Brk S2 ESTOP when the drive is in the Idle state and when the drive is running.
These faults result in an immediate ESTOP and set the SAS flag.

Note: this event is also applicable when Brk Sw Type 0-4 is set to 0 or 4
where constant states are required on BS1 and BS2 inputs.
Possible Causes & Solutions
 Incorrect parameter value  verify correct value of Brk Sw Type 0-4.
 Incorrect brake switch wiring  check brake switch wiring.
 Brake not lifting  check brake wiring & brake power supply.
Insufficient time allowed  see parameters Brk Pick Time ms and Brk Setl
Time ms.
411 Brk S1 DECEL D See: 400 Brake S1 SAS, 401 Brake S2 SAS, 408 Brk S1 ESTOP 409, Brk
S2 ESTOP
412 Brk S2 DECEL D See: 400 Brake S1 SAS, 401 Brake S2 SAS, 408 Brk S1 ESTOP 409, Brk
S2 ESTOP
413 Bk Desat Err E4 The brake current exceeded a preset level, detected via hardware.
414 Bk Bus Over I The brake bus exceeded threshold data.
415 Bk Bus Under I The brake bus fell below threshold data.
416 Bk fbk tmout E4 The brake exceeded threshold data.
417 Bk SW Oct E4 The magnitude of the brake current exceeded an allowed threshold.
418 Bk lft tmout C4* Applicable only when Brk Cnt Type 0-3 is 2-3 or Brk Sw Type
0-4 is 1-3.
This fault is logged if any of the following occur within the amount of time
specified by Brk Pick Time ms after lifting the brake.
 The brake current failed to stay above the threshold specified by
Brk Pick A and Brk Pick % for the amount of time specified
by Brk Lftd Dely ms.
 The brake switches did not hold the expected value for the
amount of time specified by Brk Lftd Dely ms.
419 Bk drp tmout C4* Applicable only when Brk Cnt Type 0-3 is 2-3 or Brk Sw Type
0-4 is 1-3.
This fault is logged if any of the following occur within 3 seconds of
dropping the brake.
 The brake current failed to stay below the threshold specified by
Brk Hold A and Brk Drop % for the amount of time
specified by Brk Setl Time ms.
 The brake switches did not hold the expected value for the
amount of time specified by Brk Setl Time ms.
*Note: For events 418 and 419, the drive state machine does not pass through the SHUTDOWN
state.

6.2.14 Motion Faults

SVT Display Description

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 67 of 147
500 Overspeed E4 The motor speed has exceeded a speed threshold. The speed threshold
is determined by the operating mode of the drive:
MCSS mode: adjustable perecentage of Duty Speed mm/s
Manual Mode: adjustable percentage of Man Speed mm/s
CAN Normal: 110% of Duty Speed mm/s
CAN Relevel: fixed percentage of max relevel = 20 mm/sec
CAN Learn: fixed percentage of max learn = 500 mm/sec
CAN ERO/TCI: fixed percentage of Insp Speed mm/s
CAN Rescue: fixed percentage of max rescue = 300 mm/sec
For MCSS and manual modes, the percentage is adjusted by SVT
parameters: MCSS Overspeed % and MAN Overspeed %.
501 Pos Tracking E4 The position tracking error exceeded a threshold and indicates that the
position feedback was not tracking the position reference from the profile
generator. This fault is checked only when the drive uses its internal
profile generator. See EEPROM parameter: Pos Err Lim mm
502 Vel Tracking E4 The velocity tracking error exceeded a threshold. The velocity feedback
was not tracking the velocity reference.

Possible Causes & Solutions

 Incorrect motor phasing  change parameter Motor Phase 0/1.
 Wrong encoder feedback  check encoder wiring and attachment.
 Incorrect parameter value  verify correct value of Inertia kg-m2.
 Excessive start jerk / improper pre-torque  verify load weigh
device; if no load weigh device present (as during inspection), try
increasing parameter Start Gain Ot PU. See section 4.11 for further
instruction.
 Brake not lifting  check brake wiring & brake power supply.
 Hoistway obstructed  check for obstruction (e.g. car or
counterweight on buffer).
 The fault threshold can be adjusted by parameter Track Error mm/s.
When Manual Mode is active, this fault threshold is automatically
increased by a factor of 3.
503 LRT Motion E4 This fault indicates motion was detected while performing the Locked
Rotor Test. The Locked Rotor Test is performed at the beginning of the
first run after a power-up to determine the position of the magnets when
using a PM motor. The threshold for the fault is specified by the
parameter LRT mot err eDeg. If the fault occurs, the brake may not be
set properly.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 68 of 147
504 Enc Pos Err W This fault indicates that the drive has lost track of the magnet position
when using a PM motor. This fault is necessary to prevent a loss of
torque production. This fault may be caused by the encoder physically
slipping with respect to the motor, or by a bad magnet position
calculation during the locked rotor test (LRT).

This fault is detected by comparing the magnet position, derived from the
encoder and the result of the LRT, to the estimated magnet position
based on the back-EMF of the motor. Since the estimator is back-EMF
based, the fault detection is enabled only when the motor operates
above 30% of the rated motor speed. The default threshold for the fault
is 20 electrical degrees. Another locked rotor test will be performed at the
beginning of the next run to automatically re-determine the magnet
position.

See EEPROM parameter: Mag err thr eDeg

See EEPROM parameter: Rated Motor rpm
See display parameter: Mag Pos Err eDeg
505 SPARE D Not used.
506 Stopping Err W A time-out occurred because the stopping criteria at the end of the run
were not satisfied. See EEPROM parameters: Pos Stop Tol mm
and Vel Stop mm/sec
507 Pos at 1LS NC Applicable only for Interface Type 1.
Unexpected position at 1LS. The 1LS transition occurred at a position
outside the expected range for 1LS, or the 1LS signal state is not
consistent with hoistway position. Applicable only when landing table is
valid and position is valid.
508 Pos at 2LS NC Applicable only for Interface Type 1.
Unexpected position at 2LS. The 2LS transition occurred at a position
outside the expected range for 2LS, or the 2LS signal state is not
consistent with hoistway position. Applicable only when landing table is
valid and position is valid.
509 Floor at 1LS NC Applicable only for Interface Type 1.
Unexpected floor at 1LS. The 1LS transition occurred at a floor that is
different from the expected floor. Applicable only when landing table is
valid and limit switch signals are valid.
510 Floor at 2LS NC Applicable only for Interface Type 1.
Unexpected floor at 2LS. The 2LS transition occurred at a floor that is
different from the expected floor. Applicable only when landing table is
valid and limit switch signals are valid.
511 1LS & 2LS ! NC Applicable only for Interface Type 1.
Both LS signals are valid and active simultaneously.

This fault is used to decide if the NEXT COMMITTABLE fault response

shall continue. If this fault is not detected with a certain time, or the fault
“906 No LS Msg” is not detected within a certain time, then the fault
response is changed from NEXT COMMITTABLE to TIMED DECEL.

If this fault persists at the end of a run, the drive will transition to (state,
substate) = (IDLE AVAILABLE, RescueOnly). When the drive is in this
substate, only commands for Rescue, ERO, ARO and MRO runs are
accepted and LS are subsequently ignored.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 69 of 147
512 Missing Vane NC3 Applicable only for Interface Type 1.
Expected vane is missing. Logged only when outside a vane and an
expected transition onto a vane has not occurred. Not checked in
Inspection or Correction runs.
513 No PRS Trans NC3 Applicable only for Interface Type 1.
Expected transition is missing. Logged only when on a vane and an
expected transition has not occurred. Not checked in Inspection or
Correction runs.
514 Enc <> Vane NC3 Applicable only for Interface Type 1.
An unexpected vane transition occurred. Possible causes could be:

1. Incorrect Car Dir 0/1 setting.

2. Wrong Vane Sensor Type parameter setting.
3. PRS sensor signal wiring mistake.
4. PRS is having false transitions.
5. Encoder is not firmly attached to rotor.
6. Magnet has moved since it was learned during the learn run.
7. Belts are slipping or creeping over the drive sheave excessively.
8. Belts are stretching excessvely.
515 NTSD failed W Applicable only for Interface Type 1.
During a normal run, the normal stopping profile did not decelerate the
car in time to meet the target. The timed-decel is two-phased, containing
a creep region. Only triggered at the terminal landings. The condition for
triggering the fault is that the normal profile overshoots the target
compared to a linear ramp-down of the speed at 110% of normal decel
rate. Only triggered above a certain speed (presently 0.1 m/s).
516 Corr failed D Applicable only for Interface Type 1.
A correction run missed the target. This fault is triggered when a
correction run terminates outside of the limit switches or outside a vane,
or at a different landing other than the terminal landing. The fault is
logged after the car has stopped.
Note: There is a minor bug with the SVT display for this fault. The fault
response in the SVT is shown as ESTOP, when it is actually DECEL.
517 DDP Error E1 Applicable only for Interface Type 1.
Delayed Drive Protection (DDP) fault. The time between vanes has
exceeded a specified value. It is not checked during ERO or TCI runs.
The fault is cleared only by a power cycle or software reset of the drive.
The time is specified by the EEPROM parameter: DDP sec. This
fault sets the SAS flag.
518 BeltCmp Wrng W Applicable only for Interface Type 1.
This indicates that the compensation factors for belt and traveling cable
imbalance determined during the learn run were exceptionally large
(specifically, the offset factor was greater than 25% rated torque). The
compensation factors can be viewed in the SVT display: BeltCmp:Slp
mA/m, BeltCmp:Offset A.
519 RlvPermitErr W Applicable only when Interface Type is 1 and Load Weigh Type is 1.
Controller has given permissive to relevel while load weighing system
indicates overload condition. This contradictory situation has persisted
for >200ms.
520 Rllbck Start W Applicable only for Interface Type 1.
Rollback of more than 5.0 mm at beginning of run
521 Rllbck Stop W Applicable only for Interface Type 1.
Rollback (reverse to direction of run) or overshoot (in direction of run) of
more than 5.0 mm at ending of run

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 70 of 147
522 ManualRescue D Applicable only for Interface Type 1.
SPBC message reports that the car has been moved for manual rescue
(drive powered off, SPBC lifts brake). The drive’s stored position is
invalidated and a locked rotor test initiated before the next run.
523 Moved at POF W Applicable only for Interface Type 1.
The SPBC or GECB and the drive have contradictory position
information (at power up): the SPBC’s or GECB’s position has been
assumed by the drive.
524 No Enc Signl E Applicable only when Encoder Type 0/1 is set to 0 (incremental,
double-ended).
Encoder channel A input is not detected. Encoder may not be connected,
encoder power supply may have failed, or encoder may have failed.
This fault sets the SAS flag.
525 NoRlv SpdChk D1 Relevel speed is too high (>= 0.285 m/s).
1
526 NoRlv TooMny D Attempt to relevel after 20 consecutive relevel runs have been performed
without start of normal run.
527 NoRlv LostDZ D1 Lost DZ signal or detecting UIS/DIS signal disagreeing with mm-position
(on opposite side of target mm-position).
528 Profile Err W The profile chosen is not compatible with the system environment:
A) The LS1 or LS2 lengths (learned during learn run) are too short for
the drive to be able to stop within. This can be caused by too large
speeds in the profile setting or too small deceleration entered. The
other possibility would be a really short LS magnet. Cause A can be
identified in the vane monitor M-1-7 by comparing measured LS to
minimum required.
B) The Nom Speed is set too high for the LS signal latency reported by
the ICD of the GECB/TCBC (e.g. Nom Speed > 1.8m/s with TCBC).
This setting could lead to CORR runs not reaching the target vane.
529 No enc fdbck E4 This fault indicates that the motor started moving without an encoder.
This fault is triggered when the motor voltage exceeds a certain
threshold defined by No Enc VThrs PU while the encoder speed
feedback is below 1mm/s. Check the integrity of the encoder. Also,
check motor parameters.
530 No enc tmout E4 This fault indicates that the drive started commanding velocity profile and
the motor speed feedback did not exceed 1mm/s for the time duration
defined by the parameter No enc flt t sec (default value of the parameter
is 0.4 secs). This fault detection is not active in Manual Mode.

Possible Causes & Solutions

 No encoder feedback signal  check encoder wiring and
mechanical attachment to the sheave.
 Incorrect parameter value  verify correct value of Inertia kg-m2,
Man Acc mm/s2, Accel mm/s2, or any of the acceleration
parameters in the (L)MCSS if operating in 422 mode.
 Excessive start jerk / improper pre-torque  verify load weigh
device; if no load weigh device present (as during inspection), try
increasing parameter Start Gain Ot PU. See section 4.11 for further
instruction.
 Brake not lifting  check brake wiring & brake power supply.
 Hoistway obstructed  check for obstruction (e.g. car or
counterweight on buffer).
 The fault threshold can be adjusted by parameter No enc flt t sec

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 71 of 147
531 PRS Sigs 1LS NC Applicable only for Interface Type 1.
The transition into 1LS occurred with PRS signals that are not expected
near the learned LS transition point. Applicable only when landing table
is valid and limit switch signals are valid.
532 PRS Sigs 2LS NC Applicable only for Interface Type 1.
The transition into 2LS occurred with PRS signals that are not expected
near the learned LS transition point. Applicable only when landing table
is valid and limit switch signals are valid.
533 ARO Overspd E Applicable only when Interface Type = 2 or 3.
Applicable only when “ARO Type” = 2 (Interruptable ARO).
This fault is declared when the motor speed has exceeded a speed
threshold set by the parameter ARO Overspeed % as a percentage of
ARO Speed mm/s. This fault is disabled with ARO Overspeed % =0. If
this fault is logged, the run is immediately terminated by the drive.
534 ABL Abort:LW ER Applicable only for Interface Type 1.
A command for advanced brake lift was received and ignored because
no valid load data was available.
535 Timeout PTR ERS Applicable only for Interface Type 1.
While in state “Prepare To Run” (during Advanced Brake Lift), the drive
did not receive a command to leave this state and timed out after 60s.
536 Timeout LB ERS Applicable only for Interface Type 1.
While in state “Lift Brake” (during Advanced Brake Lift), the drive did not
receive a command to leave this state and timed out after 16s.
537 No EndRunCmd ERS Applicable only for Interface Type 1.
While waiting for a DriveCommand EndRun in substate “STOPPED” the
drive did not receive this command and timed out after 3s..
538 Abort:EndRun ER Applicable only for Interface Type 1.
The run has been terminated with normally profiled deceleration by an
OPB command (DriveCommand EndRun)..
539 LvTransUnclr NC3 Applicable only for Interface Type 1.
With a single-sensor PRS, an ambiguous sensor transition has been
detected, could have been either one of two vane edges. Potential root
cause: Uncertain mm-position (ESTOP sliding, Power Up recovery from
GECB/SPBC, position recovery in LS) and transition occurs within first
5mm of travel.
540 Shock Detect W Applicable only for Interface Type 2 or 3.
The shock condition was detected for REI/REM and EAR.
541 SinCos Warng W This fault will be logged for one of the following conditions:

1. When using a sin/cos encoder

A. If any of the analog encoder signals fail, then this fault will be
logged. Check the encoder connection.
B. If the Encoder Type 0/1 SVT parameter has the wrong setting
of "0", then this fault will be logged.
2. When using an incremental encoder
If the Encoder Type 0/1 SVT parameter has the wrong setting of
"1", then this fault will be logged.
542 Decel Req Fl D Applicable to Interface Type = 3 only.
A fault occurred and a timed decel is required, so a falsg is sent to the
controller to request a timed-decel
1) This Timed Deceleration reaction does not lead to the SHUTDOWN state

6.2.15 Temperature Faults

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 72 of 147

SVT Display Description

600 Inv Tmp Warn W The temperature of the inverter heat sink has exceeded 80C.
1
601 Inv Tmp Over C The temperature of the inverter heat sink has exceeded 85C. The fault
detection includes hysteresis, and will not clear until the temperature of
the heat sink drops 5C below fault value.
1
602 Inv Tmp Fail C Indicates the analog temperature sensor on the inverter heat sink is not
connected or has failed. The fan will turn on and remain on when this
condition is detected.
603 Cnv Tmp Warn W The temperature of the converter heat sink has exceeded 80C.
1
604 Cnv Tmp Over C The temperature of the converter heat sink has exceeded 85C. The fault
detection includes hysteresis, and will not clear until the temperature of
the heat sink drops 5C below fault value.
1
605 Cnv Tmp Fail C Indicates the analog temperature sensor on the converter heat sink is not
connected or has failed. The fan will turn on and remain on when this
condition is detected.
1
606 Mtr Tmp Over C The motor thermal contact has changed state indicating that either the
motor is overheating or there is a problem with the contact circuitry.
Check the motor temperature and the thermal contact. Although motor
thermal contacts can be normally open or normally closed, the drive
always expects a normally closed contact. If the thermal contact is
normally open, a modification must be made to adapt it to the drive.
1
607 Reactor Temp C The thermal switch in the line reactor has opened, indicating an over-
temperature condition in the line reactor.
1
608 DBR Tmp Over C Not used (was applicable only for non-regen drives).
609 AC/DC Calibr C Applicable only when “Low Volt Op 0/1” is set to 1.
A calibration was performed to ensure that the AC voltage sense and the
DC voltage sense are consistant.
610 Batt Ovr Tmp I The thermal sensor at the charger battery unit is reading high
temperatures or disconnected. This could be due to:
 an error during the installation phase where the sensor is not
connected
 the charger spent excessive time in the charge pending phase
 the battery ran into a hot condition.
Since the installation initially needs to be done correctly, this fault would
mean that either battery/charger got into a hot condition due to the
ambient or due to overcharging. If it persists for a long time it needs to be
checked (job site visit). This timer = TBD minutes.
611 MTC/RTC Flt C Applicable to Ultra Drive only.
This indicates that either the motor thermal switch openeded OR the line
reactor thermal switch opened.
1) When these temperature faults occur in 422 mode, PTR is not accepted until the fault condition
clears. When these temperature faults occur in CAN mode, the drive behaves as follows:
1. Normal runs are re-routed to the next committable landing.
2. Inspection runs (TCI+ERO) are terminated by timed deceleration.
3. All other runs (ARO, CORR, Rescue, MRO, Relevel) are completed to their regular end
4. No new run is allowed until the condition clears.
5. The fan is turned on 100%.

6.2.16 State Faults

SVT Display Description

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 73 of 147
700 Safety Chain E/ The safety chain is not present. The opening of the safety chain will cause
W SX relays to drop, causing the drive to de-energized the motor and brake,
thus causing an ESTOP.
 For 422 system, the response is ESTOP
 For CAN system, the response is LOG ONLY
Note: Due to switch timing variation, this event can be logged sporadically
when switching from NORMAL to ERO/TCI (no problem in unit)
701 No Man Input E Applicable only for Interface Type 0.
This fault occurs if the drive is in manual mode and the manual mode
jumper is removed.
702 Prechrg Time E3 This fault is declared when the DC bus fails to reach the charge voltage
threshold within a time limit. The time limit is approximately 2 seconds for
60A V.2 drives and 10 seconds for other regen drives. The timer starts
when the drive enters the precharge state.

For MCSS systems, the drive enters the powerdown state and waits 2
minutes, and then attempts again. For the regen drive, further precharge
attempts are made only if the AC line voltage is within specification. There
is no limit on the number of precharge attempts.

For CAN systems, the drive enters the powerdown state and waits 30
seconds, and then attempts again. For the regen drive, further precharge
attempts are made only if the AC line voltage is within specification. There
is a limit of 3 consequtive precharge timeouts after which the drive will be
blocked.

The voltage threshold is 80% of the actual rectified AC line voltage.

Note: There is a minor bug with the SVT display for this fault. The fault
response in the SVT is shown as WARN, when it is actually ESTOP.
703 S Rly Fault E4 The normally-open S1 contact was in the wrong state.
See SVT parameter SX Pick Time ms.
704 DBD Fault E4 One or more of the normally-closed contacts of S1, S2, BY1 and BY2
were in the wrong state. Three attempts are allowed before the drive is
blocked.
See SVT parameter SX Pick Time ms.
705 E2 Invalid E The data in the EEPROM is set to values incompatible with the current
SCN or new EEPROM parameters have not yet been set. The invalid or
blank values must be corrected. Pressing SHIFT_ENTER tells which
parameter is invalid and what menu it is located.
706 E2 Write Lim W The allowable number of writes to the EEPROM have been exceeded:
Metric writes: 100,000 maximum
Event writes: 1,000,000 maximum
707 ADC Offset C Not applicable to Ultra drive.
708 Cmd to Abort D Applicable only for Interface Type 1.
The run has been terminated with timed deceleration by an OPB
command (DriveRunCommand dir=none). This fault does NOT result in
SHUTDOWN.
709 PRS SigNoise D Applicable only for Interface Type 1.
Too many PRS signal transitions have occurred over a fixed period of
time.
710 UIB DIB Err E Applicable only for Interface Type 1.
The UIB and DIB inputs were not consistent with the run command from
TCBC-type controller. This fault sets the SAS flag.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 74 of 147
711 DBD Shutdown S Three attempts were made to try to correct a relay in the wrong state (one
or more of the normally-closed contacts of S1, S2, BY1 and BY2 were in
the wrong state). The drive is blocked from further runs.
712 PostTrq Time W A log only fault is reported when the current is not ramped down to zero
within a specified time.
713 Block by xxx S The drive has been blocked from further runs. This occurs after certain
critical faults have been detected, indicated by “S” in this table, or when
certain faults have exceeded an allowed number of occurrences, indicated
in this table by the number that follows the fault response category. The
blockage must be cleared following the guidelines in Section 6.2.3.
This fault sets the SAS flag.
714 B_MODE Err W Applicable only when Interface Type = 2 or 3.
Applicable only when “ARO Type” = 3 (NIARO).
This fault is logged when “B_MODE” was not detected in less than 200ms
from the time when the drive received some fault of "201 Cnv Id Error/ 202
Cnv Iq Error/208 Bus Cap Fail/305 PLL Unlock" or detected DC Bus
voltage less than 650V.
715 ARO BatPower D Applicable only in CAN-architecture. The power drawn from the battery
during an MRO/ARO run was too high, e.g. > 15A * 48V for 800ms.
716 Illegal Cmd W Applicable only for Interface Type 1 with systems using GECB
where CarController ICD >= 10, see “CAN ICD type” in M-1-8 ENGINEERING.
An unexpected command has been received in a state where it could not
be executed. It was ignored. Note it is possible that a GECB command
coincides with a state change in the drive making execution of that
command impossible. In such a case, this warning does not indicate a
problem with the system.
717 Triac Stuck E Applicable only for Interface Type 1.
This fault is logged if both triacs are disabled and safety chain feedback is
in the active state. It is not checked during ARO(EN) runs.
718 PRS Config C Applicable only for Interface Type 1.
This fault indicates illegal configuration of the PRS. Causes (see M-3-2):
 “offset mm” for a sensor is outside “Vane Length mm”
(<- Test Variable 2 = 1)
 no DZ configured, i.e. "LV1 config 0/1/2"=0 and "LV2 config
0/1/2"=0, (<- Test Variable 2 = 2)
 gap between 2 sensors configured <5mm or sequence of sensor
positions violated. Required sequence UIS > LV1 > LV2 > DIS
719 OARO Blocked I Applicable only for Optimized ARO.
The pilot AR relay for AR1/AR2 contacts is welded ON. If this fault is
reported, then optimized ARO functionality is blocked, but normal runs are
enabled. The controller will parse this code and request service via REM.
720 Welded BLV I Applicable only for Optimized ARO.
The BLV contact is welded. This means that the drive will allow ARO runs
and normal runs; however the drive will be unable to completely shut
down power after an ARO run. This causes deep discharge of batteries if
the power outage persists (shorter life time and unavailability of ARO) and
it needs to be fixed. The controller will request service via REM.
721 PwmExistsFlt E Applicable to Ultra Drive only.
This fault indicates either PWM is acitve when there is no safety chain or
PWM is blocked when safety is present.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 75 of 147
722 E2 Read CkSm W Applicable to Ultra Drive only.
A checksum fault occurred while reading metrics from E2 at POR. If this
occurs, metrics are reset to zero, current floor is set invalid, and floor
position is set to zero.
723 UCM in Run C Applicable only for Interface Type 1 and UCM-EN on/off = 1.
Indicates that the car has run out of the door zone with open doors!
Note: This fault triggers a blockage which may only be cleared by
authorized personnel after appropriate investigation of the UCM fault
causing the blockage. It cannot be cleared by a power cycle, it can be
cleared by an ERO run or by SVT.
724 UCM in Slide C Applicable only for Interface Type 1 and UCM-EN on/off = 1.
Indicates that the car has slid out of the door zone with open doors after
an ESTOP has aborted a run inside the DZ.
Note: This fault triggers a blockage which may only be cleared by
authorized personnel after appropriate investigation of the UCM fault
causing the blockage. It cannot be cleared by a power cycle, it can be
cleared by an ERO run or by SVT.
725 UCM BrkBlock C Applicable only for Interface Type 1 and UCM-EN on/off = 1.
Indicates that the UCM-EN brake monitoring has detected a fault
potentially compromising the ability of the brake to hold the car.
Note: This fault triggers a blockage which may only be cleared by
authorized personnel after appropriate investigation of the brake fault
causing the blockage. It cannot be cleared by a power cycle, it can be
cleared by an ERO run or by SVT.
726 Tmout SfcMsg C Applicable only for Interface Type 1 and UCM-EN on/off = 1.
Indicates a timeout of the communication of the SafetyChainSignals (used
by UCM-EN) from the GECB. No further run will be started until the
communication is re-established.
727 TOStp SfcMsg D Applicable only for Interface Type 1 and UCM-EN on/off = 1.
Indicates that a timeout according to 726 has caused the abortion of a run
by timed deceleration. This reaction is shown if 726 Tmout SfcMsg occurs
while the the UCM monitoring is active (open door with DBP active).

6.2.17 Task Overrun Faults

SVT Display Description
800 1ms Task S The 1 ms task overran. Contact Enigineering.
801 10ms Task S The 10 ms task overran. Contact Enigineering.
802 40ms Task S The 40 ms task overran. Contact Enigineering.
803 Cnv Task S The Converter task overran. Contact Enigineering.
804 Inv Task S The Inverter task overran. Contact Enigineering.
805 200ms Task S The 200ms Task Overran. Contact Enigineering.

6.2.18 Communication Faults

SVT Display Description
900 MCSS Timeout E Applicable only for Interface Type 0.
Valid MCSS communication has not been received for 80 msecs.
901 SVC Tool Err W Service tool communication error detected via the local service tool port.
902 CAN Err W Applicable only for Interface Type 1.
CAN communication error detected.
903 E2 CommWrite W An error occurred when writing to the EEPROM device.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 76 of 147
904 LWSS Timeout W Applicable only for Interface Type 1 and Load Weigh Type is set to
1 or 2. The drive has not received a loadweigh message within a certain
time. The fault is cleared when a valid LW message is received.
905 LWSS Bad Val W Applicable only for Interface Type 1 and Load Weigh Type is set to
1 or 2. The drive received an erroneous value in the loadweigh message.
Load Weigh Type = 1 :
The drive received the full scale value for load percent from the LWB2.
The load percent value can be checked in the SVT menu of the LWB2.
Load Weigh Type = 2 :
The drive received the full scale value for the hitch load measured in kg
from the Hitch LW device. The value can be checked in the menu Monitor-
Motion, it is the first value in the display “ HitchLW: Empty: “
The fault is cleared when a valid LW message is received.
906 No LS Msg NC Applicable only for Interface Type 1.The drive has not receieved the
DriveHoistwaySignal message for 3 seconds.

This fault is used to decide if the NEXT COMMITTABLE fault response

shall continue. If this fault is not detected with a certain time, or the fault
“511 1LS & 2LS !” is not detected within a certain time, then the fault
response is changed from NEXT COMMITTABLE to TIMED DECEL.
907 Primary CRC W The drive application performs a CRC of the primary loader and this value
does not match the value computed by the conversion utility.
908 Drive CRC S The drive application performs a CRC of the drive software and this value
does not match the value computed by the conversion utility.
909 CAN BusOff W Applicable only for Interface Type 1.
The CAN controller of the drive has shut itself down due to a persistent
communication problem on the CAN bus or CAN power failure (broken
connection).
910 CAN OPB_Init W Applicable only for Interface Type 1.
Initialization of the CAN communication software has failed.
911 CAN TxQ Full W Applicable only for Interface Type 1. Overflow in the transmit queue of
the CAN port, messages have been lost.
912 No FloorInfo W Applicable only for Interface Type 1. Neither the SPBC nor the GECB
have sent valid position in return to the request by the drive (timeout
200ms after request for SPBC, 200ms after its StartUp message for
GECB).
913 MCSS Warning W Applicable only for Interface Type 0.
MCSS Communication error detected. It includes Checksum, Framing,
Parity or invalid format.
914 Power E2 Err S The power section could not be identified because bad or undefined drive
code data has been read from the EEPROM on power section board 1
(DCPB).
This check is only performed at power on.
915 LWSS not cal W Applicable only when Interface Type = 1.
Applicable only when Load Weigh Type = 2.
Hitch load weighing device not calibrated. The calibration is done during a
learn run.
916 Power E2 Rng S Not applicable for ULTRA drives.
Applicable only to drives with eI2C EEPROM storage capability.
This fault is logged if the scaling parameters in one of the power section
EEPROMs are out of range for the specified drive type.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 77 of 147
917 CPLD Ver Flt E1 Not applicable for ULTRA drives.
The CPLD version is not compatible with either the HVIB EERPROM or
the GDCB EEPROm parameter setting. See the attached table for
erroneous combinations.
918 ARO Ver Flt E1 This event indicates an incompatibility between the Primary Loader and
the CPLD version in case of an optimized ARO system. The Primary
Loader must be version AAA31013CAE or later and the CPLD must be
version 9 or greater. This event occurs if either is not satisfied for an
optimized ARO system.
919 Powrbrd miss S Bad or no response from the DCPB EEPROM where the power board
information is stored.
This check is only performed at power on.
920 Micro ChkSum E Applicable to Ultra Drive only.
This fault indicates that the DSP is not communicating to the
microprocessor.
921 FPGA ChkSum E Applicable to Ultra Drive Only
This fault indicates that the DSP is not communicating to the FPGA
device.
922 FLASH Warn W Applicable to Ultra Drive Only
A communication fault was detected by the SPI FLASH test routine. This
log only event indicates that the SPI communication or SPI FLASH device
may have failed.
923 FPGA Warn W Applicable to Ultra Drive 0nly
This warning indicates that DSP received one erroneous packet from the
FPGA.
924 Micro Warn W Applicable to Ultra Drive Only
This warning indicates that the DSP received one or more consecutive
erroneous packets from the microprocessor. Fault threshold is controlled
by parameter
Micro Wrn 0.
925 No CAN-PRS C Requested PrsSignals CAN messages are not received. While the fault
persists, only ERO and MRO runs are allowed.
926 CAN PRS Msg W A discontinuity in the CAN PrsSignals was detected, a message may have
been lost.
927 DSP2FPGA Wrn W Applicable to Ultra Drive Only
This warning indicates that FPGA received one packet with wrong
checksum or stuff bits.
928 DSP2FPGA Flt E Applicable to Ultra Drive only.
This fault indicates that the FPGA received more than one packet with
wrong checksum or stuff bits.

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 78 of 147

6.3 Central Failure Management

The CFM is supported by sending a
 CfmSystemEvent messages after the occurrence of every event.
 CfmSystemEventText message in case of a blockage.

The CFM messages support the “ALL Menu”

The “ALL Menue” provides
 A common error logging of all subsystems.
 A possibility to clear all event logs together
 In case of a blockage the source and a text string are displayed
 If the blockage is clearable it can be cleared

6.3.1 Plug & See

In case of a blockage by any subsystem the servicetool may be plugged in. It displays the “All
Menu” automatically with the
 Source (blinking in the first row)
 Text String (scrolling through the second row)
 If clearable, it can be cleared by “shift 5”

Every event with a defined number of retries may lead to a blockage. The following text
messages are provided by the drive:

Event message Retries Source Text String

allowed
"100 Inv SW Oct " 4 DRIVE, High inverter current detected by software
"101 Inv I Imbal " 4 DRIVE, Asymmetric inverter current
"102 Inv Id Error" 4 DRIVE, High inverter current (field) regulator
"103 Inv Iq Error" 4 DRIVE, High inverter current (torque) regulator
"107 Inv Gate Flt" 4 DRIVE, Inverter IGBT gate supply voltage fault
"108 Inv HW Oct " 4 DRIVE, High inverter current detected by hardware
"109 Overload " 4 DRIVE, Motor current overload
"111 No Id fdbk " 4 DRIVE, Motor phase - no current (field)
"112 No Iq fdbk " 4 DRIVE, Motor phase - no current (torque)
"113 Inv IPM Flt " 4 DRIVE, Inverter intelligent power module fault
"114 Curr Ovrload" 4 DRIVE, Current overload
"115 Brk Chop Err" 4 DRIVE, Brake chop error
"116 Inv HW Ovt " 4 DRIVE, High DC link voltage detected by hardware
"117 Inv Pfai Flt" 4 DRIVE, Inverter PWM activity during IDLE
"120 Output Cur " 1 DRIVE, Motor has currents while Sx dropped
"200 Cnv SW Oct " 4 DRIVE, High converter current detected by software
"201 Cnv Id Error" 4 DRIVE, High converter current (field) control error
"202 Cnv Iq Error" 4 DRIVE, High converter current (torque) control error
"205 Cnv Gate Flt" 4 DRIVE, Converter IGBT gate supply voltage fault
"206 Cnv HW Oct " 4 DRIVE, High converter current detected by hardware
"207 Cnv Gnd Flt " 1 DRIVE, Converter ground fault
"208 Bus Cap Fail" 1 DRIVE, High power loss - check DC link capacitor
"209 DC Link OCT " 1 DRIVE, High DC link current
"210 Cnv IPM Flt " 4 DRIVE, Converter intelligent power module fault
"211 Battry Chrgd" 4 DRIVE, Battery charging during ARO
"300 DC Bus Over " 3 DRIVE, High DC link voltage detected by software
"301 DC Bus Under" 6 DRIVE, Low DC link voltage

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 79 of 147

"302 VAC Over " 0 DRIVE, High AC line voltage

"303 VAC Under " 0 DRIVE, Low AC line voltage
"304 VAC Imbal " 0 DRIVE, AC line voltage imbalanced
"305 PLL Unlock " 0 DRIVE, PLL on AC line frequency unlocked
"306 Single Phase" 1 CONTACTOR, Wrong phase wiring in Single Phase mode
"308 Welded Mx/Px" 1 DRIVE, DC link voltage not 0 - check for welded Mx or
Px relay
"400 Brake S1 SAS" 4 BRAKE, Brake switch BS1 fault
"401 Brake S2 SAS" 4 BRAKE, Brake switch BS2 fault
"402 Brake Status" 4 BRAKE, Brake status feedback disagrees with brake
command
"403 Brake BY " 4 BRAKE, BY energized before lift brake command
"404 Brake I Off " 4 BRAKE, Brake current measurement fault - high offset
"405 Brake I Drop" 4 BRAKE, High brake current during stop
"406 Brake I Hold" 4 BRAKE, Low brake current during run
"407 Brake I Max " 4 BRAKE, High brake current during run
"408 Brk S1 ESTOP" 4 BRAKE, Brake switch BS1 fault - emergency stop
"409 Brk S2 ESTOP" 4 BRAKE, Brake switch BS2 fault - emergency stop
"500 Overspeed " 4 DRIVE ENCODER, Motor overspeed
"501 Pos Tracking" 4 DRIVE ENCODER, Position tracking error
"502 Vel Tracking" 4 DRIVE ENCODER, Velocity tracking error
"503 LRT Motion " 4 BRAKE, Motion detected while brake should be closed
"511 1LS & 2LS !" 0 POSITIONREF, 1LS & 2LS active
"512 Missing Vane" 3 POSITIONREF, Low-to-high vane transition missing
"513 No PRS Trans" 3 POSITIONREF, High-to-low vane transition missing
"514 Enc <> Vane " 3 POSITIONREF, Unexpected low-to-high vane transition
"517 DDP Error " 1 DRIVE, DDP - No vane transition within DDP time limit
"524 No Enc Signl" 0 DRIVE ENCODER, Encoder channel A input not detected
"529 No enc fdbck" 4 DRIVE ENCODER, No encoder feedback after motor started movement
"530 No enc tmout" 4 DRIVE ENCODER, No encoder feedback within timeout
"539 LvTransUnclr" 3 POSITIONREF, Unexpected LV transition
"601 Inv Tmp Over" 0 DRIVE, Inverter over-temperature
"602 Inv Tmp Fail" 0 DRIVE, Temperature sensor failed on inverter
"604 Cnv Tmp Over" 0 DRIVE, Converter over-temperature
"605 Cnv Tmp Fail" 0 DRIVE, Temperature sensor failed on converter
"606 Mtr Tmp Over" 0 DRIVE, Motor over-temperature
"607 Reactor Temp" 0 DRIVE, Line reactor over-temperature
"608 DBR Tmp Over" 0 DRIVE, DBR over-temperature or parameter DBR Mode
"611 MTC/RTC Flt " 0 DRIVE, Motor or line reactor over-temperature
"702 Prechrg Time" 3 DRIVE, DC link not precharged within time limit
"703 S Rly Fault " 4 DRIVE, S1 relay in the wrong state
"704 DBD Fault " 4 CONTACTOR, DBD fault
"705 E2 Invalid " 0 DRIVE, Drive parameter invalid
"707 ADC Offset " 0 DRIVE, ADC offset out of range
"710 UIB DIB Err " 0 DRIVE, UIB/DIB inputs not consistant with run commands
"711 DBD Shutdown" 1 CONTACTOR, DBD fault
"717 Triac Stuck " 0 DRIVE, Unexpected 110VAC on safety chain output
"718 PRS Config " 0 POSITIONREF, Illegal configuration of PRS
"721 PwmExistsFlt" 4 DRIVE, Inverter PWM status disagrees with safety chain
input
"723 UCM in Run " 0 DRIVE, UCM blockage: motor on & car left DZ with open
door
"724 UCM in Slide" 0 DRIVE, UCM blockage: brake dropped & car left DZ with
open door

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.
 ULTRA DRIVE EVENT LOG DETAILS

Document: 31400_UG

Sheet: 80 of 147
"725 UCM BrkBlock" 0 DRIVE, UCM blockage: because of brake failure
"726 Tmout SfcMsg" 0 DRIVE, Drive did not receive SafetyChainSignal CAN msg
for UCM
"800 1ms Task " 1 DRIVE, Software 1ms task overrun
"801 10ms Task " 1 DRIVE, Software 10ms task overrun
"802 40ms Task " 1 DRIVE, Software 40ms task overrun
"803 Cnv Task " 1 DRIVE, Software converter task overrun
"804 Inv Task " 1 DRIVE, Software inverter task overrun
"805 200ms Task " 1 DRIVE, Software 200ms task overrun
"908 Drive CRC" 1 DRIVE, Software checksum fault
"914 Power E2 Err" 1 DRIVE, Power section not identified - E2P data
incorrect
“916 Power E2 Rng” 1 DRIVE Bad or missing calibration of Power section
"917 CPLD Ver Flt" 1 DRIVE, CPLD version fault
“919 Powrbrd miss” 1 DRIVE Power section boards are missing or not
responding

Form PA1021 Unpublished Work - Copyright © Otis Elevator Company

Rev. 2009-01-15

This work and the information it contains are the property of Otis Elevator Company
(“Otis”). It is delivered to others on the express condition that it will be used only for, or
on behalf of, Otis; that neither it nor the information it contains will be reproduced or
disclosed, in whole or in part, without the prior written consent of Otis; and that on
demand it and any copies will be promptly returned to Otis.