Icontrol DC Aug 08 Rel 42-02-7222 B7
Icontrol DC Aug 08 Rel 42-02-7222 B7
Icontrol DC Aug 08 Rel 42-02-7222 B7
User Guide,
iControl with DC Drive
Trademarks
All trademarks or registered product names appearing in this document are the exclusive property
of the respective owners.
Limited Warranty
Motion Control Engineering (manufacturer) warrants its products for a period of 15 months from
the date of shipment from its factory to be free from defects in workmanship and materials. Any
defect appearing more than 15 months from the date of shipment from the factory shall be
deemed to be due to ordinary wear and tear. Manufacturer, however, assumes no risk or liability for
results of the use of the products purchased from it, including, but without limiting the generality
of the forgoing: (1) The use in combination with any electrical or electronic components, circuits,
systems, assemblies or any other material or equipment (2) Unsuitability of this product for use in
any circuit, assembly or environment. Purchasers rights under this warranty shall consist solely of
requiring the manufacturer to repair, or in manufacturer's sole discretion, replace free of charge,
F.O.B. factory, any defective items received at said factory within the said 15 months and
determined by manufacturer to be defective. The giving of or failure to give any advice or
recommendation by manufacturer shall not constitute any warranty by or impose any liability upon
the manufacturer. This warranty constitutes the sole and exclusive remedy of the purchaser and
the exclusive liability of the manufacturer, AND IN LIEU OF ANY AND ALL OTHER WARRANTIES,
EXPRESSED, IMPLIED, OR STATUTORY AS TO MERCHANTABILITY, FITNESS, FOR PURPOSE SOLD,
DESCRIPTION, QUALITY PRODUCTIVENESS OR ANY OTHER MATTER. In no event will the
manufacturer be liable for special or consequential damages or for delay in performance of this
warranty.
Products that are not manufactured by MCE (such as drives, CRT's, modems, printers, etc.) are not
covered under the above warranty terms. MCE, however, extends the same warranty terms that
the original manufacturer of such equipment provide with their product (refer to the warranty
terms for such products in their respective manual).
End User License Agreement
This End User License Agreement (Agreement) grants you the right to use the software con-
tained in this product (the Software) subject to the following restrictions: You may not: (i) copy
the Software, except for archive purposes consistent with your standard archive procedures; (ii)
transfer the Software to a third party apart from the entire product; (iii) modify, decompile, disas-
semble, reverse engineer or otherwise attempt to derive the source code of the Software; (iv)
export the Software or underlying technology in contravention of applicable U.S. and foreign
export laws and regulations; and (v) use the Software other than in connection with operation of
the product.
LICENSOR'S SUPPLIERS DO NOT MAKE OR PASS ON TO END USER OR ANY OTHER THIRD PARTY,
ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY OR REPRESENTATION ON BEHALF OF SUCH
SUPPLIERS, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON-
INFRINGEMENT, TITLE, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Important Precautions and Useful Information
This preface contains information that will help you understand and safely maintain MCE
equipment. We strongly recommend you review this preface and read this manual before
installing, adjusting, or maintaining Motion Control Engineering equipment. This preface dis-
cusses:
Safety and Other Symbol Meanings
Safety Precautions
Environmental Considerations
Danger
This manual symbol is used to alert you to procedures, instructions, or situations which, if
not done properly, might result in personal injury or substantial equipment damage.
Caution
This manual symbol is used to alert you to procedures, instructions, or situations which, if
not done properly, might result in equipment damage.
Note
This manual symbol is used to alert you to instructions or other immediately helpful informa-
tion.
Safety Precautions
Danger
This equipment is designed to comply with ASME A17.1, National Electrical Code, CE, and
CAN/CSA-B44.1/ASME-A17.5 and must be installed by a qualified contractor. It is the
responsibility of the contractor to make sure that the final installation complies with all
local codes and is installed in a safe manner.
This equipment is suitable for use on a circuit capable of delivering not more than 10,000
rms symmetrical amperes, 600 volts maximum. The three-phase AC power supply to the
Drive Isolation Transformer used with this equipment must originate from a fused discon-
nect switch or circuit breaker sized in conformance to all applicable national, state, and local
electrical codes in order to provide the necessary motor branch circuit protection for the
Drive Unit and motor. Incorrect motor branch circuit protection will void the warranty and
may create a hazardous condition.
Proper grounding is vitally important to safe and successful operation. Bring your ground
wire to the system subplate. You must choose the proper conductor size and minimize the
resistance to ground by using the shortest possible routing. See National Electrical Code
Article 250 or the applicable local electrical code.
Before applying power to the controller, physically check all the power resistors and other
components located in the resistor cabinet and inside the controller. Components loosened
during shipment may cause damage.
For proper operation of the AC Drive Unit in your controller, you must make sure that: 1) A
direct solid ground is provided in the machine room to properly ground the controller and
motor. Indirect grounds such as the building structure or a water pipe may not provide
proper grounding and could act as an antenna to radiate RFI noise, thus disturbing sensi-
tive equipment in the building. Improper grounding may also render any RFI filter ineffec-
tive. 2) The incoming power to the controller and the outgoing power wires to the motor are
in their respective, separate, grounded conduits.
This equipment may contain voltages as high as 1000 volts. Use extreme caution. Do not
touch any components, resistors, circuit boards, power devices, or electrical connections
without ensuring that high voltage is not present.
Environmental Considerations
Keep the machine room clean.
Controllers are generally in NEMA 1 enclosures.
Do not install the controller in a dusty area.
Do not install the controller in a carpeted area.
Keep room temperature between 32 and 104 degrees F (0 to 40 degrees C).
Prevent condensation on the equipment.
Do not install the controller in a hazardous location or where excessive amounts of
vapors or chemical fumes may be present.
Make certain that power line fluctuations are within plus or minus 5% of proper value.
i
Section 2. Construction Mode
In This Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Overview of Construction Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Machine Room Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Equipment Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Environmental Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Ethernet and Internet Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Recommended Tools and Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
About MCE Job Prints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Controller Cabinet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
Overview of Typical Connection Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11
Peripheral Inputs and Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Equipment Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Check for Shorts to Ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
AC Voltage Verification and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Verifying Main Line Power and Wiring the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Initial Controller Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
DC Hoist Motor, Brake, and Encoder/Tachometer . . . . . . . . . . . . . . . . . . . . . 2-21
Checking the Hoist Motor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Wiring the Hoist Motor to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Wiring the iField Motor Field Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Verifying Brake Current Resistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Wiring the Brake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Tachometer or Encoder Installation and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Tachometer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Velocity Encoder Installation and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Basic Safety String and Associated Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Cartop Safety Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Hoistway Safety Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Temporary CTS Relay Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Access Locks and Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Rope Gripper Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Temporary Rope Gripper Bypass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Temporary Cartop Inspection Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Applying Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Setting Initial Operating Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Connecting the iView PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Verifying Initial Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Learning the Safety Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
iii
Installing the Floor Leveling Magnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Cabling Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
iLand Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Setting the Position Encoder Resolution parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Calibrating the Floor Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Installing iLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
iLink Enclosure Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
iLink Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Front and Rear Door and Leveling Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Leveling Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Cartop Inspection Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Cartop Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Landing System Pulse Streams to iControl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
iLink to iControl Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
iLink Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Car Operating Panel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
iLink Cartop Wiring Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Installing the Hoistway Limit Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Installing the Load Weigher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Installing Brake Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Installing the Earthquake Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Temporary Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Earthquake Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Installing the Serial Hall Call System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
Installing the Serial COP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
Verifying Cartop Voltages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23
Verifying Door Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Verifying Safety Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25
Exit Construction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25
Running on Machine Room Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Verifying Quadrature Pulse Sequence and Encoder Resolution . . . . . . . . . . . . . . . . . . . 3-27
Position Encoder Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Quadrature Pulse Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Prepare for Final Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Door Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Counterweight Learn Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Counterweight Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Run Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Empty Car Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
v
Load Weigher Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Load Weigher Selection and Threshold Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Learning Load Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Load Weigher Learn Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Pre-Start Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Allow machine to be energized: After doors are locked. . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Allow the machine to be energized:
When the door position monitor is activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Allow the machine to be energized:
While doors are closing with motor only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Allow the machine to be energized:
While doors are closing with motor and partially picked brake . . . . . . . . . . . . . . . 4-43
Allow the machine to be energized:
While doors are closing with motor and fully picked brake . . . . . . . . . . . . . . . . . . 4-44
Calibration and Verification of Safety Functions . . . . . . . . . . . . . . . . . . . . . . 4-45
Tach Error Tripping Threshold Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Verify Tach Error Does Not Trip on Emergency Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Armature Overcurrent Overload Protection Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Safety Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Running a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Car/Counterweight Safety Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Electrical Governor Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Car/Counterweight Buffer Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Inspection Overspeed Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Contract Overspeed Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Leveling Overspeed Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Emergency Brake Test - Unintended Motion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Normal Terminal Switch Overspeed Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
Emergency Terminal Switch Overspeed Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Normal and Emergency Terminal Switch Position Tests . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Terminal Switch Overspeed and Position Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Before Release to Passenger Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-57
vii
EMCO Load Weigher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Installing the Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
Installing the Control Unit and Connecting the Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
PROGRAMMING the EMCO VK-3v Control Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Description of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
How to Program the EMCO Load Weigher Control Unit . . . . . . . . . . . . . . . . . . . . . . . 5-54
Menu/Programming Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
Manual Calibration with Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
Auto-zero Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
Final Calibration with iControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
Additional iControl Settings and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
Installation with 2 to 1 Roping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Verifying the zero calibration (empty car weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
MCE Load Weigher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
Installation Method #1 Preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
Method #1 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
Installation Method # 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
Installation Method # 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
Section 6. Troubleshooting
About Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Troubleshooting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
Safety String Bypass Jumper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Message Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
iControl Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Circuit Boards and Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
Circuit Board Removal and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
iBox Removal and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
iBox Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
iBox Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
iBox Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
iBox File Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
iControl Circuit Board Quick References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83
ICE-COP-2 Serial Car Operating Panel Board QR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
Board Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
Software Version Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
ICE-CTP Cartop Processor Board Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86
ICE-CTP Cartop Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
ICE-EB Emergency Brake Board Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92
ICE-FML Field Module Logic Board Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-93
ICE-IEQ Earthquake Board Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96
ICE-IMP Main Processor Board Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98
ix
Section 8. Using iView
About iView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
How iView Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Installing iView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
LAN Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Creating a New LAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Working Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Viewing and Adjusting Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Sending Adjustments to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Saving Parameters to a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Save to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Saving Default Parameters to a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Loading Parameters from a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Working Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
iView Windows and Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Controller - Configuration Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Controller - Diagnostic Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Controller - Setup Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Additional Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Controller - Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
System View Windows and Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
System - Configuration Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
System - Diagnostic Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Additional Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Pinning and Unpinning Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Resizing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
Docking and Undocking Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Printing Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Setting the Systems Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Editing Dynamic Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
Updating Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-41
Upgrade Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43
Bootrom Recovery via OBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44
xi
Car Operation - Fire Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-47
Fire Service - Fire Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
Fire Code - Recall - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Fire Code - Recall - Front / Rear Door Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Fire Code - In-Car - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Fire Code - In-Car - Front / Rear Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Fire Code - In-Car Recall - Front / Rear Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
Car Operation - Independent Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Car Operation - Elevator Recall Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-64
Car Operation - Earthquake Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-67
Car Operation - EMS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-69
Car Operation - Emergency Power Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-73
Car Operation - CFSS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Car Operation - Flood Operation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-79
Car Operation - Attendant Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-81
Car Operation - Auto Stop Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-82
Car Operation - Sabbath Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-84
Car Operation - Shuttle Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-87
Car Operation - Heat Detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-89
Configuration - Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-90
Drive - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-91
Drive - Safety Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-93
Drive - Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-95
Drive - Filters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-99
Drive - Dampening Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-103
Drive - Pretorque Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-105
Drive - Calibration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-106
Configuration - Floor Heights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-107
Configuration - General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-108
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-108
General - Floor Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-109
General - Car Call Eligibility Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-110
Configuration - I/O Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-113
I/O Board - Configurable outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-118
Input Signal Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-119
Output Signal Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-128
Configuration - iBox Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-139
Configuration - Load weigher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-140
Configuration - Motor Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-142
Configuration - Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-145
Pattern - Common Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-146
Pattern - Modes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-148
Configuration - Terminal Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-151
xiii
Parking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Parking Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Set Parking Delay Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Choose Dynamic or User-Defined Parking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Sector Dispatching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Sending Changes to iControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Parking Eligibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Split Bank Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Remote Monitoring Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Local Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Configuration Tabs - Emergency Power Tab . . . . . . . . . . . . . . . . . . . . . . . . . .10-33
Defining Emergency Power Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Configuration Tabs - Legacy Group Interface . . . . . . . . . . . . . . . . . . . . . . . . .10-36
Cross-registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Cross-cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
Configuration Tabs - Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
General - Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
General - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
General - Manage Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
Hall Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
Per-Floor Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
Per-Car Lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-44
Car Calls - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45
Car Calls - Mode Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
Car Calls - Passcodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Car Calls - Passcodes - Floor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Car Calls - Passcodes - Passenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
Configuration Tabs - System I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-51
System Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-51
Default Calls Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-52
Configure Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-52
Configuring System I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53
System I/O - Bus Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-60
Configuration Tabs - Timer Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-62
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-62
Timer Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
Configuration Tabs - User Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-65
Configuration Tabs - Remote Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
Diagnostic Tabs - Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
System - Hoistway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-70
Per Car Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
Call Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-74
System - Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-75
xv
xvi Manual # 42-02-7222 B7, February 2014
Introduction
iControl - August 2008 Release
Welcome! This user guide is intended for use with the August 2008 release of iControl. It
includes additional features and capabilities which are outlined in this section and described in
detail elsewhere in this guide. If you are viewing this document on a PC, click the hyperlinks to
jump to the topics shown in blue.
Intro-1
In This User Guide:
This is the installation, adjustment, and troubleshooting guide for iControl DC traction eleva-
tors. When viewed online as a pdf file, hyperlinks link to related topics and informational web-
sites. The user guide includes:
Contents: Table of Contents. When viewed online as a pdf file, hyperlinks in the Con-
tents link to the associated topic in the body of the manual.
Introduction: Introduction. Provides an overview of whats in this user guide and
whats new in this release.
Section 1: iControl Description. Provides an overview and introductory information
about iControl, the iBox, the iView graphical user interface, and other system options.
Section 2: Construction Mode. Complete instructions on installing iControl and
bringing the elevator up on Construction Mode.
Section 3: Inspection Mode. Complete instructions on continuing the elevator installa-
tion and adjustment up to Inspection Mode.
Section 4: Final Adjustment. Step-by-step instructions on making the final adjust-
ments necessary to release the elevator to normal passenger operation.
Section 5: System Options. Installation instructions for various system options includ-
ing Central Dispatching, Local/Dispatching, Serial Hall Call, Serial COP, EMCO Load
Weigher and MCE Load Weigher.
Section 6: Troubleshooting. Information about diagnosing and correcting improper
system operation.
Section 7: iBox Front Panel Controls. Detailed information about the parameter dis-
plays/adjustments and function switches on the front panel of the ibox.
Section 8: Using iView. Detailed information about the iView graphical user interface.
iView software runs on any PC running Windows 2000 or Windows XP and is the pri-
mary tool used to view and adjust iControl parameters, diagnose problems, and monitor
system health.
Section 9: iView - Controller View. Detailed information about the adjustable Con-
troller parameters, screen-by-screen and parameter-by-parameter.
Section 10: iView - System View. Detailed information about the adjustable System
parameters, screen-by-screen and parameter-by-parameter.
Section 11: Reference. Additional technical information provided for elevator mechan-
ics and adjusters.
Index: Index. Alphabetical index to help you find information in the manual. When
viewed online as a PDF file, index entry page references are hyperlinks to the associated
information in the body of the manual.
Status Bar - Controller Type The status bar, at the bottom-left of the iView window,
indicates the type of controller to which iView is connected (see iView Status Bar on page 9-
3).
Split Bank Dispatching Split Bank operation allows some of the cars in a group to be
dispatched as a separate group and to respond to hall calls from an alternate riser. For more
information see Split Bank Operation on page 10-29.
Third Party Authorization In order to control access to iControl data, this tool is used
to authorize a third party monitoring tool to connect to the iControl system (see Management
on page 10-31).
System I/O Status Indicators LEDs indicate the current status, On or Off, of the
input and/or output at each node address (see System I/O - Bus Tab on page 10-60).
Per-car Hall Call Security Hall call lock out can now be applied per-car, per-floor and
per-direction (see Per-Car Lockout on page 10-44).
Per-passenger Car Call Security Unique car call enable passcodes may be assigned
to individual passengers. Activity associated with the use of these passcodes may be viewed
using iReport (see Car Calls - Passcodes - Passenger on page 10-49).
System - User Events Users can assign a name to an Input / User Event. Up to 10
Input / Event Names can be programmed. This event name can then be assigned to a hardware
input. An event is logged, on the System Event Log, when the input is activated and again when
it is deactivated (see Configuration Tabs - User Events on page 10-65).
System - Remote Outputs Users can configure system outputs which can be wired to
an input or other device. The outputs can be turned on and off remotely via iView or iMonitor or
via a timer (see Configuration Tabs - Remote Outputs on page 10-66).
System Event Log An Event Log has been created to record the System events (see
Diagnostic Tabs - Event Log on page 10-68).
Enhanced Controller Event Log An event filter has been added to the controller
Event Log to allow the user to select which events are logged (see Diagnostics - Diagnostic Out-
puts on page 9-14). Troubleshooting Tips for each event can now be displayed with the click of
a button.
Intro-3
Clear Event Log The data stored in the event logs, controller and system, can be easily
cleared using the Clear all button on the event logs button bar.
Data Trap This diagnostic tool automatically records controller data including input and
output states, internal flags and parameter values (see Controller - Safety Tests on page 9-
172).
Hoistway Access Recall To facilitate ease of gaining hoistway access, controls have
been added to allow the activation of a hoistway access switch/input to also recall the car (see
Hoistway Access Recall on page 9-66).
Shuttle Service The Shuttle Service option allows a local car to provide express service
for a subset of the buildings floors. For more information see Car Operation - Shuttle Service
on page 9-87.
I/O Assertion This troubleshooting tool allows the user to bypass the current state of a
terminal on an I/O board and assert a desired state (on or off) via iView (see I/O Assert on
page 9-115).
System I/O for Simplex and Swing Cars The inputs and outputs normally sup-
plied to the dispatcher via the Serial Hall Call system are now available on the MIAC and MOR
boards.
Controller - User Events Users can assign a name to an Input / User Event. Up to 10
Input / Event Names can be programmed. This event name can then be assigned to a hardware
input. An event is logged, on the Controller Event Log, when the input is activated and again
when it is deactivated (see Configuration - Advanced - User Events on page 9-155).
Rope Tension Load Weigher An additional load weighing option, which measures
tension of the wire ropes, is now available for use with iControl (see EMCO Load Weigher on
page 5-51).
Default Configuration File The Controller and/or System default parameter settings
can be saved to a configuration (.cfg) file. The default parameter values can then be loaded onto
the controller (see Saving Default Parameters to a Configuration File on page 8-21).
Brake Contact Input Controls have been added to allow the polarity of the brake con-
tact input to be set to either active high or low (see Brake - Control Tab - Switch on page 9-
26).
TAPS Interface Controls and logic have been added to allow iControl with AC Drive to
use the new Traction Auxiliary Power Supply (TAPS) (see Car Operation - Emergency Power
Tab on page 9-73).
Car Statistics iControl accumulates statistical data which can be used in maintaining
the elevator. The statistics include distance traveled (odometer), power up cycles, front and rear
door cycles, motion cycles, floor time, floor runs, inspection runs, auto runs and auto relevels.
This data can be viewed on the iBox onboard display (Car menu), which also allows the data to
be cleared.
Write Privilege Time-Out Controls have been added to the iBox OBD Mgmt menu to
set the write privilege time-out time and to cancel write privilege (see Mgmt Menu Parame-
ters on page 7-9).
Clone Controller Data Allows the controllers parameter settings to be saved to flash
memory in order to facilitate easy field replacement of an iBox (see Mgmt Menu Parameters
on page 7-9).
Upgrade Wizard A special utility has been created to facilitate field upgrade of iBox
firmware programs.
Intro-5
Using iView On-line Help
iView is a graphical user interface which runs on a Windows PC or laptop computer. The com-
puter is typically connected to iControl through a Local Area Network. The iView program pro-
vides the main user interface to iControl. It allows the user to view and set Controller and
System operating parameters.
On-line help is incorporated into iView to provide information about iControl screens and
parameters. You can access iView On-line Help in the following ways:
Context Sensitive Help You can view On-line Help information about any screen or
tab by pressing function-key one (F1) while a screen or tab has focus. Do the following:
Click the title bar of a window, e.g., the Hoistway window, to bring focus to the window.
The background color of the windows title bar darkens indicating that the window has focus.
Then press the F1 key. iView Help will display the topic that describes the window.
Click a tab (title). An outline will appear around the tab title indicating that the tab has
focus. Then press the F1 key. iView Help will display the topic that describes the tab.
Context Sensitive Event Help iControl logs status and error information in the Con-
troller - Event Log (see Diagnostics - Diagnostic Outputs on page 9-14). To view the Event
Log, Event Properties and Context Sensitive Event Help:
1. In the Controller view, click View > Diagnostics > Event Log to display the Event Log.
2. Double click an event in the Event Log to display the Event Properties dialog.
3. Click the Help button in the Event Properties dialog to display the Troubleshooting Tips
dialog which provides a description of the event, an indication of what action is taken,
and troubleshooting tips if appropriate.
Help Viewer iView On-line Help provides three additional ways of locating information.
The Contents and Index tabs let you find general information. The Search tab lets you look up
specific words or phrases.
To start iView On-line Help:
1. On the iView menu bar, click Help.
2. On the Help menu, click iView Help. The help viewer is displayed. Use the Contents,
Index or Search tabs to locate the desired information.
Intro-7
Installation Checklist (page 2 of 3)
Perform the automated drive setup procedure (see Automated Drive Setup Procedure on
page 2-49).
Calibrate the motor field (see Motor Field Calibration on page 2-53).
Calibrate the brake (see Brake Calibration on page 2-57).
Verify that the brake is picking properly (see Verify Brake Picking on page 2-60).
Verify proper car movement on inspection (see Verifying Car Movement on page 2-61).
Calibrate the car speed (see Calibrating Actual Car Speed on page 2-62).
Verify proper armature voltage and current (see Current Limit Adjustments on page 2-
63).
Adjust PID parameters to improve car response (see Car Response and Speed Loop Gain
on page 2-65),
Set the following error parameter - tach error tripping threshold (see Following Error Mar-
gin on page 2-67 and see Tach Error Tripping Threshold Adjustment on page 2-68).
Perform the tach failure calibration (see Tach Failure Calibration on page 2-69).
Verify proper mounting of iLand landing system (see Cartop Mounting on page 3-3).
Verify proper installation of the floor magnets (see Floor Leveling Magnets on page 3-9).
Verify iLand connection to iLink (see Cabling Connections on page 3-11).
Verify proper installation of iLink (see Installing iLink on page 3-13).
Install the hoistway limit switches per the job prints (see Installing the Hoistway Limit
Switches on page 3-19).
Install the Load Weigher, if applicable (see Installing the Load Weigher on page 3-19 and
see EMCO Load Weigher on page 5-51 or see MCE Load Weigher on page 5-61).
Install the optional Brake Pick Switch, if applicable (see Installing Brake Monitoring on
page 3-20).
Install the earthquake sensor, if applicable (see Installing the Earthquake Sensor on
page 3-21).
Install the serial hall call system (see Installing the Serial Hall Call System on page 3-22).
Install the serial COP system, if applicable (see Installing the Serial COP System on
page 3-22).
Verify the cartop voltages (see Verifying Cartop Voltages on page 3-23).
Verify door operation (see Verifying Door Operation on page 3-24).
Verify the safety configuration (see Verifying Safety Configuration on page 3-25).
Exit construction mode / begin running on inspection (see Exit Construction Mode on
page 3-25 and see Running on Machine Room Inspection on page 3-26).
Verify the quadrature pulse sequence (see Verifying Quadrature Pulse Sequence and
Encoder Resolution on page 3-27).
Perform final door operator checks (see Door Operator on page 3-28).
Perform the counterweight learn and counterweight balancing procedures (see Counter-
weight Learn Procedure on page 3-28).
Perform the run and empty car tests (see Run Testing on page 3-30 and see Empty Car
Tests on page 3-31).
Learn the building floor heights (see Learning the Floor Heights on page 4-2).
Intro-9
Intro-10 Manual # 42-02-7222 B7, February 2014
About iControl
Features
Function
iControl
iVIEW
iLand
iLink
iCUE
iMONITOR
iReport
Load Weigher
iControl Description 1
About iControl
iControl from MCE intelligently integrates and coordinates every element of your
elevator installation. Grounded securely in twenty-plus years of MCE experience and
innovative design expertise, iControl reflects a uniquely-qualified, absolute focus on
meeting and exceeding customer expectations.
iControl includes:
iController Next generation iBox intelligence for control logic and safety process man-
agement designed around proven Power PC microcomputer technology (see page 1-5).
iView A Windows-native, graphical user interface for direct system analysis, diagnos-
tics, and parameter adjustment (see page 1-11).
iLand An innovative, maintenance-free landing system unencumbered by tape, struts,
or switches (see page 1-17).
iLink A convenient, cartop, single-point interconnect, converting discrete car signals to
economical, dependable, serial communications. Optional serial COP available (see
page 1-18).
iCue The most powerful, intuitive, and adaptable dispatching engine available (see
page 1-19).
iMonitor Centralized, on site or remote system monitoring capability (see page 1-21).
iReport System logging and report generating tool (see page 1-22).
1-1
iControl Description
The system overview diagram below provides a high-level view of an iControl installation,
including peripheral devices and associated iControl equipment.
Laptop PC to #3
Ethernet Port LAN Hub
with iView
PC
iCue
with iView
Dispatcher
System Hub
Serial to Ethernet
Converter
Drive Drive Drive
Serial Hall
Call Driver
iLink iLand
Optional
Serial COP
iControl Features
MCE designed iControl to provide:
Compliance: Fully ASME A17.1 - 2000 compliant. CE and CSA certified.
Safety: Two independent processors verify all safety checks. Safety A is a microprocessor
(firmware) and Safety B is a PLD.
Support: Outstanding MCE Technical Support at regional and factory level, electronically
or on site.
Reduced Installation Expense: Simplified installation for minimum time and expense.
Reliability: Solid-state construction, minimized point-to-point wiring, integrated design,
and non-volatile FLASH memory contribute to exemplary reliability.
Scalability: Flexible capacity and system configuration, scalable control, networked com-
munications capability, and expandable I/O adapt to future requirements.
Serviceability:
All user parameters fully field programmable.
Secure on site and remote access to user parameters.
Supports multiple, simultaneous iView connections for near real-time, diagnostic
coordination and support. 1
Real-time status display.
Single point location for system control switches.
At-a-glance, LED display of 15 most important system functions.
Virtual oscilloscope iView display.
Informative, near real-time, iView hoistway display.
Report generation.
On line help for iView.
Complete hard copy and electronic (pdf) documentation.
Reduced Maintenance Requirements:
Minimal point-to-point wiring.
Reliable, D-subminiature component interconnection.
Slide-track mounted I/O boards for easy addition or substitution with no reprogram-
ming required.
Maintenance-free landing system.
Cartop, single-point wiring interconnect, converting discrete car signals to economical,
dependable, serial communications.
Tuned Acceleration/Deceleration Pattern for passenger comfort and maximum efficiency.
Self-optimizing technology the system adapts without intervention, fine-tuning perfor-
mance over time as use patterns are learned.
1-3
iControl Description
iControl Function
iControl provides the modular building blocks required to efficiently address elevator installa-
tions ranging from a single car servicing only a few floors to those requiring elevator groups
operating according to sophisticated dispatching functionality and servicing up to a design
maximum 150 floors. In all cases, MCE can provide iControl components to support system
capabilities including remote elevator controller diagnosis and support (iView), remote moni-
toring capabilities (iMonitor) and a system logging and report generating tool (iReport). iCon-
trol components include:
iController enclosure containing iBox elevator controller, the motor drive, and peripher-
als specific to the job
Cartop-mounted iLand precision landing system
Cartop-mounted iLink wiring and interconnect system
MCE Serial Hall Call system
Dispatching iCue dispatching allows a single group controller to accommodate up to a
design maximum 20 cars and 150 floors. iCue can handle myriad dispatching configura-
tions, enabled manually or by automation, and allow configuration of variables sufficient
to meet virtually any dispatching need including multiple lobbies, intelligent hall call
assignment, parking variations, and automated response to changing traffic conditions
within the building. Dispatching can be configured with redundancy for protection against
individual system failure or disconnect. Elevator security and emergency power operation
are also important iCue capabilities.
Graphical User Interface The MCE iView application runs on any PC or laptop with the
Windows 2000 or XP operating systems. Through a standard 10/100 Base-TX Ethernet
connection, iView lets you efficiently and easily:
View and adjust over 500 controller, motor, and brake parameters
Copy controller configurations to files on the computer hard drive
Send some or all parameters from a computer file to a controller
Monitor system performance in real time
Send car and hall calls to evaluate system response
Configure extremely flexible dispatching behaviors
Use the iView virtual oscilloscope to tune acceleration and deceleration patterns
Configure elevator response to fire, earthquake or other emergency or alternative
operating modes
With internet access, connect to one controller port while MCE support technicians
simultaneously connect to that same controller through a separate port for factory-
assisted diagnosis or performance monitoring.
Access and print extensive controller logs where important system events are automat-
ically recorded
Central Monitoring MCE iMonitor software allows personnel at local or remote moni-
toring sites extensive capability to monitor and control safety and security aspects of your
installation. Refer to the iMonitor manual, 42-02-S025.
Logging and Reporting - iReport is a system logging and report generating tool that allows
local or remote analysis of iControl elevator groups from a personal computer running the
iReport client software. Because iControl dispatchers are Ethernet capable, you can use
iReport to connect to them through a local area network or remotely through internet/
modem technology. Refer to the iReport manual, 42-02-S026.
ICONTROL
iControl provides the latest in integrated digital elevator control. With SCR drive technology,
iControl brings premium performance to elevators using DC motors. Controller parameters can
be easily adjusted using MCE iView software running on any Windows 2000 or better personal
computer. All parameters can be saved to a file on your computer hard drive, providing a secure
archive. iView even allows you to work offline in a saved controller file and easily write that
data to a controller later.
The sophisticated iControl distance and velocity feedback system is continuously aware of exact
car position and speed. The 32-bit processor provides smooth pattern generation for any appli-
cation easily accommodating irregularities like short floors. Each iControl includes:
The iBox, including onboard diagnostics
SCR Drive
The illustration below shows a typical iControl layout.
1
Resistor cabinet
iBox
SCR drive
iPower box
1-5
iControl Description
Easy Installation
iControl is designed to make installation and adjustment as simple as possible. Before ship-
ment, each controller is carefully tested against specific job requirements. iControl is shipped
from MCE with preset, default adjustment values that generally require little additional adjust-
ment.
Detailed MCE job prints, specifically engineered for each installation, provide connection-by-
connection instruction for mechanics and electricians. Elevator adjusters will find that iControl
has the intelligence to automatically learn many previously tedious, adjuster-intensive opera-
tions including:
All floor heights to within 0.0469 (1.191mm)
All Normal and Emergency Terminal switch positions
High-current brake modulation across the calibration range
Empty and full car, analog load weigher values at every landing served
Elevator safety device configuration
Hoist motor control across the calibration range
iControl makes specific code-compliance as easy as possible too, providing automated fire and
earthquake presets for:
A17.1 (1996 and 2000)
Title 8
New York
Nebraska
Chicago
CSA B44-00
Australia
If necessary for specific job requirements, adjusters have access to detailed, decision-making
adjustments within the compliant defaults for various jurisdictions.
iBox
The iBox is the heart of iControl. Built around Power PC technology, the iBox brings flexible,
computing power into the elevator machine room. The iBox is an efficient, powerful elevator
controller and supports Simplex (Group control parking and dispatching subset) functionality
as well. Configured for iControl, the iBox includes:
Onboard diagnostics display and keypad
System I/O, control and communications ports (serial, discrete, and Ethernet)
Figure 1.3 iBox
Car
11/30/2003 LCD Display and Keypad
1 2 3 4
ENTER
1
System Status Display
COMPUTER UP SAFETY OK
SAFETY A ENABLE DOORS LOCKED
SAFETY B DOWN INSPECTION
CARTOP FLOOR RUN IN GROUP
CONTROLLER FAULT/FUNCTION
System Control Switches
INSPECTION STOP BYPASS
F3 F3HA F2MC
1-7
iControl Description
Typically, when you need to view or change system parameters in an iControl, you connect to
the iBox through the PC or LAN Ethernet port and use the iView graphical user interface run-
ning on a Windows OS PC to easily access, view, or edit any desired parameter.
However, during initial system setup, parameters that allow PC access to your system can be
directly accessed and edited through the keypad and LCD display located on the front panel of
every iBox. (For detailed information about keypad parameter entry, please see Parameter
Entry on page 7-5.)
LCD Display
Directional Arrows /
1 2 3 4 Value Incrementers
Select Parameter /
Enter Value
Move Cursor
ENTER
Connections to the iBox are all on pluggable connectors. Serial, Ethernet, and Serial Hall Call
connections on the right side of the iBox are primarily pre-molded cable assemblies with D or
RJ-45 connectors. Connections on the left side of the iBox (position encoder, cartop link, code-
mandated car, limit, hoistway, and other field connections) are also pluggable primarily indi-
vidual conductors, terminated and locked into connectors that plug into mating connectors on
the iBox.
Field wiring (wiring completed by the installer) is addressed in Sections 2 and 3 of this guide.
The illustration below is only intended to provide an overview of the inputs and outputs to the
iBox. A description of every input and output is in Section 11.
Motor Tachometer
1
Logic & Analog Power
Position Encoder
Serial PC
Velocity Encoder
Motor Field Module
Cartop Link
Brake Field Module
Car
Ethernet (3 ports)
Limits
Hoistway
AC/DC Drive
Locks/Contacts
J3
Drive
Serial Hall Call (4 ports)
Safety
Encoder Output
Spares
Drive Serial
Common
120VAC
110VDC
STP 1 Test Point
STP 2 Test Point
GND Test Point
1-9
iControl Description
SCR Drive
The SCR drive converts three phase AC input power to variable DC voltage for the hoist motor.
The illustration below shows the DC Drive used in MCE iControls. Drive circuit boards and
troubleshooting are described in Section 6 of this guide (see System 12 SCR Drive on page 6-
123.)
This section provides an overview of iView. Section 8 of this manual provides a more complete
description of the iView screens. iView on-line Help and Section 9 provide the most complete
description of the screens.
Controller Screen
When you start iView, a splash screen appears
for a few seconds, followed by the iView Con-
troller screen. From the File menu, select Con-
nection and click Open. The Open dialog is
displayed.
1-11
iControl Description
Once the connection has been established, the Operational Status tab and Hoistway window are
displayed.
To access the controllers configuration parameters, click View on the menu bar. Select Configu-
ration and click one of the listed tabs.
A typical parameter screen, the Pattern/Common tab, is shown below. Before you can edit con-
troller parameters, you must request write privileges (click Write privilege on the menu bar,
then click Acquire) and must be granted those privileges at the controller. (The iBox will display
your request and a yes response must be entered by pressing the iBox #1 softkey.)
1-13
iControl Description
Active Displays
The Virtual Oscilloscope allows you to display and track two signals over time simultaneously.
The selected signal values are shown on the Test point 1 and 2 displays and output on the STP 1
and STP 2 physical test points on the iBox. Please refer to Controller - Layouts on page 9-173.
System Interconnect
It can be helpful to have a general understanding of the way the entire iControl system is inter-
connected. This section contains high-level interconnection drawings for:
System Interconnection: Basic car control and dispatcher interconnections.
iControl Interconnection: More detail for car controller interconnections.
Cartop Interconnection: More detail for cartop interconnections.
Dispatcher Interconnection: More detail for dispatcher interconnections.
Figure 1.6 iControl System Interconnection
DISPATCHER
LAN: iView,
iMonitor,
1
iReport CAR CONTROL CAR CONTROL CAR CONTROL
iView
Car Car Car
Calls Calls Calls
Ethernet
LAN: iView, iMonitor, iReport Connectivity
Other
1-15
iControl Description
Safeties iBox
Limits OBD
Cartop
Motor
Module
Serial Bus
Ethernet
LAN Direct Connect (iView)
Other
SYSTEM
Signal Board
(LS-IPH)
Serial Car Call Serial Link
iLand Compact is a rugged, highly accurate landing system. iLand uses an encoder to gauge pre-
cise hoistway position and three separate Hall-effect sensors to level the elevator car accurately
at each landing. iLand is designed for easy installation and adjustment and to provide mainte-
nance-free service.
1-17
iControl Description
Battery
Note
iMonitor or iReport
DISPATCHER
Monitor
iView
LAN
Switch
Keyboard To Cars
LAN: iView, iMonitor, iReport
SC- iCue connectivity.
General Field Inputs
to Dispatcher ION
SYSTEM
Ethernet
Other
1-19
iControl Description
Local/Dispatcher
Beginning with the December 2006 Release, in addition to performing car control functions,
iControllers can assume full dispatching responsibilities for a group of elevators. MCE uses the
term Local to refer to an individual car that is part of a group, hence the term Local/Dispatcher.
One or more Local cars can be designated as an Alternate Dispatcher, meaning that they can
act as a backup for a central dispatcher or as one of several potential dispatchers for a group
that has no central dispatcher. An iController that is currently performing the dispatching func-
tions is called the Local/Dispatcher.
LAN
To Cars
LAN: iView, iMonitor, iReport
SC- connectivity.
General Field Inputs
to Dispatcher ION
SYSTEM
Ethernet
Other
iMonitor:
Provides local or remote viewing and control of elevator groups.
Provides a graphical representation of elevator groups, allowing their activity and status to
be quickly and easily viewed.
Provides remote control. The user may register car and hall calls, control many group
security functions, and enable or disable certain elevator operating modes.
Monitoring
1
Controller
Controller
Controller
Text messaging
PDA
1-21
iControl Description
System Description
iReport consists of the iReport server and iReport clients. iControl dispatchers may be con-
nected to iReport directly through a local area network or they may be connected remotely
through a DSL or other high-speed ethernet connection and the internet. The dispatcher pro-
vides iReport with hall call and car operating mode information. The individual car controllers
provide iReport with event and fault notifications.
You connect to and use iReport through the iReport client program on your PC. The block dia-
gram below illustrates a possible system interconnection. Various local and remote connections
are possible depending upon system requirements.
Web Server
Report
PRINTER
1-23
iControl Description
Construction Mode
2
In This Section
This section provides the information you need to install iControl and get the eleva-
tor running in Construction Mode:
Machine Room Preparation (see page 2-4).
Recommended Tools and Test Equipment (see page 2-6).
About MCE Job Prints (see page 2-7).
Controller Cabinet Installation (see page 2-9).
Equipment Grounding (see page 2-14).
Check for Shorts to Ground (see page 2-16).
AC Voltage Verification and Wiring (see page 2-17).
Motor and Brake Wiring (see page 2-21).
Tachometer or Encoder Installation (see page 2-23 or page 2-26)
Safety String Wiring (see page 2-28).
Applying Power (see page 2-30).
LAN Connections (see page 2-30).
Initial Parameter Settings (see page 2-43).
Drive Check (see page 2-47).
Initial Drive Settings (see page 2-49).
Motor Field Calibration (see page 2-53).
Brake Calibration (see page 2-57).
Running on Machine Room Inspection (see page 2-61).
2-1
Construction Mode
Danger
This equipment contains voltages up to 1000V, rotating motor parts, and driven machinery
that can cause serious or fatal injury. Only qualified personnel who are familiar with this
manual and driven machinery should attempt to start up or troubleshoot this equipment.
USE EXTREME CAUTION Do not touch circuit boards, resistors, or motor electri-
cal connections without ensuring that the unit is properly grounded and no high volt-
age is present. Do not apply AC power before grounding the equipment in accordance
with applicable local codes, the job prints, and instructions contained in this manual.
BE CERTAIN that any possible violent motion of the motor shaft and driven
machinery will not cause personal injury or damage. Peak torques of up to ten times
rated motor torque can occur during a control failure.
HIGH VOLTAGE may be present on the motor and drive whether or not AC power is
applied, even if the motor is not rotating.
BEFORE BEGINNING WORK read these instructions. Become familiar with proce-
dures. Proceed cautiously. These instructions assume adequate electrical trouble-
shooting experience. Follow procedures carefully and, if the elevator does not respond
correctly, obtain necessary assistance.
Required Connections The following connections are necessary to run the car on Con-
struction Mode:
Motor, Brake, and Drive
Velocity Encoder or Tachometer
SAFH, GOV, ESC, Rope Gripper (if enabled)
SAFC (provide temporary Emergency stop switch between SAFH and SAFC if iLink is not
yet installed)
UNTD and DNTD (Up and Down Normal Limit Switches)
GS, DLMS, DLAT, DLAB, DPM (Verify the iView/Safety Configuration screen settings for
these options)
INCT, ICTU, and ICTD
Emergency Power Input
Faults While operating in Construction Mode, faults may be generated due to incomplete
installation. These may be disregarded in this phase and include:
Invalid Front and/or Rear Doors
Terminal Sync
System Sync
Floor Sync
2-3
Construction Mode
Equipment Location
When choosing equipment location, consider:
Adequate working space for comfort and efficiency.
Logical arrangement, taking into consideration other equipment in the machine room and
routing of electrical power, control, and Local Area Network (10/100 Base TX) wiring.
Do not install equipment in a hazardous location.
Installing a telephone in the machine room is desirable as it makes remote diagnostics and
adjustment assistance more readily available.
Wiring the machine room for internet access will allow MCE technical support to use the
iView application to remotely view system parameters, diagnose problems, and assist you
in adjusting elevator controller settings.
If any areas in the machine room are subject to vibration, they should be avoided or rein-
forced to prevent equipment from being adversely affected.
Provide adequate lighting for the control cabinets and machines. A good working space
such as a workbench or table should also be provided.
Environmental Considerations
Ambient temperature should remain within 32 to 104 Fahrenheit (0 to 40 Celsius).
Temperatures outside these guidelines may be tolerated, but will shorten equipment life.
Adequate ventilation is required. Air conditioning may be necessary.
The air in the machine room should be free of excessive dust, corrosive elements, and
excessive moisture. A NEMA 4 or NEMA 12 enclosure can help meet these requirements if
machine room conditions are inadequate. If the machine room has open or unglazed win-
dows or other direct outside openings, place equipment cabinets far enough from them so
that severe weather does not damage the equipment.
Very high levels of radio frequency (RF) radiation from nearby sources should be avoided.
RFI may interfere with controller components, degrading elevator performance. Using
hand-held communication devices close to the controller may also cause interference.
Interference from permanently installed radio transmitting antennas is not common.
Power line fluctuation should not be greater than 10% of proper value.
Through a net modem, ISDN, DSL or other internet access, this port may provide remote
access to the controller. This access allows MCE technical support staff to view controller
parameters at the same time you view them through your LAN or direct/local connection.
Elevator parameters are protected from meddling or accidental change because in order to
write data to a controller, permission must be granted in the machine room.
For installations not requiring a central dispatching capability or for single car installations,
Ethernet or internet connectivity may not be required. 2
If you want to take advantage of Ethernet or internet connectivity benefits, the machine room
must be appropriately wired. Most commercial buildings use Ethernet Local Area Networks
that can readily be extended to accommodate machine room access.
2-5
Construction Mode
Become familiar with the following information as well as the wiring prints provided with this
control system.
Note
Drawing Name: Some drawings have a drawing name directly above the title block or at the top 2
of the drawing. The drawing name may also be used to refer to a particular drawing.
MCE job print drawing numbers use the format Job Number Car Number Drawing Iden-
tifier. Thus they are specifically keyed to particular installations. It makes using and under-
standing job prints much easier if you take some time to review the job prints package before
beginning controller installation. Drawing identifiers and the information you can expect to
find on that job print drawing are listed below:
N: Nomenclature drawing schematic symbols, wire gauge information, circuit board
names and symbols.
INT: iLink cartop wiring interconnect box to controller connections.
CVR: iBox controls and indicators.
1: AC power connections, power bus information.
2 through nn: iBox/controller wiring.
CC: Contact Count drawing System contact/relay information.
SH: Serial Hall Call wiring.
CT: Cartop wiring (iLink cartop wiring interconnect box).
CW: Traveling Cable Wiring
F: iDC Filter (remote)
COP: Car Operating Panel to cartop box (iLink) wiring.
CW: Car to cartop box (iLink) wiring.
MRW1, -MRW2: Machine Room and Hoistway wiring.
D1, -D2, -D3, -D4: Controller and drive wiring.
2-7
Construction Mode
GND: Grounding
PI: Peripheral Interface (iView, iMonitor)
IP: IP Address Scheme
Note
Depending on your installation, you may have extra sheets of particular drawings. Extra sheets
are indicated by an x following the drawing identifier. You may also have different or addi-
tional equipment in your installation accompanied by different or additional drawings in your
job prints. In any case, take the time to become familiar with the job prints before beginning
work.
Symbols
Every job print set contains a drawing depicting and describing schematic and other symbols
used in the job prints. Review this page to acquaint yourself with symbols and their meanings.
Nomenclature
The following table lists MCE part numbers and provides a brief description for each. Your
installation may not use all boards listed.
32 ICE-MIAC Input expansion board. Used as needed in iControl and the iLink cartop
box to support equipment inputs.
51 ICE-MOR Output expansion board. Used as needed in iControl and the iLink cartop
box to support equipment outputs.
80 ICE-LCB Low Current Brake board, used in low current braking applications.
Note
Review the wiring guidelines in this section before bringing wires into the controller.
Caution
When drilling or cutting access holes or during other machining, do not allow any metal
chips to fall into the electronics. Keep drive or other covers in place while wiring to prevent
damage to components.
MCE applies labels inside the cabinet to identify suggested wiring hole locations. The MCE con-
troller cabinet does not require rear access.
Field wiring should enter the cabinet from the side at the lower left corner or from the bot-
tom directly under the wiring trough. The wires must be routed through the wiring 2
trough on the left side of the controller cabinet in a way that allows the power
box door to open fully.
All conductors entering or leaving the controller cabinet must be through conduit. High
voltage, high current conductors, such as power conductors from the fused disconnect or
isolation transformer, must be separated from control wires. It is essential that Tachome-
ter/Velocity Encoder control wires be routed through a separate conduit away from high
current conductors.
The traveling cable must have at least four twisted shielded pairs to be used for the posi-
tion pulser quadrature signal and the iLINK communication link from the Car Top Proces-
sor board (ICE-CTP) to the iBox Safety Processor board (ICE-SAF). The shielded cable
should be used all the way to the controller. If there are more shielded pairs still available,
route the ULM, DLM and DZ signals from the iLink Car Top Processor board through a
shielded pair (especially if the building has more than eight floors). The shields must be
grounded at both ends by connecting them to a SHLD terminal.
2-9
Construction Mode
Resistors
Input / Output
boards
Wiring Trough - (field wiring goes here)
SCR
Drive
M
Contactor
iPower box
Note
Customer peripheral
inputs (card read-
ers,etc.) Signal/Pin ICE-MIAC: Inputs
assignments made in 2
iView screens.
ICE-MIAC: Inputs
Serial fixture interface.
Floor indicators, etc.
Earthquake sensor I/O. ICE-SF: Srl. Fixtures
processor.
Contactor
Discrete car connections,
limit switches, hoistway, iBox Panel
and door system connec-
tions.
ICE-IMP: Main
Safety I/O. Processor
Spare I/O. Common, Motor contactor AC connections.
120VAC, and 110VDC wiring.
buses.
ICE-IRB:
Emergency Brake
connection
Rear door processing ICE-RG Rope Gripper
ICE-IRD Rear Door
2-11
Construction Mode
Typically an installation will have at least one MIAC and one MOR board in the controller cabi-
net to handle requirements local to the machine room and at least one MIAC and one MOR
board in the cartop interconnect box (iLink) to handle requirements local to the elevator car.
Inputs Refer to your job prints (drawings -9 nn or -CT) to see exactly how your periph-
eral inputs are configured. Typical usages include car call buttons, card reader inputs, fire
return switches, smoke sensors, etc. To complete an input, the installer wires a switch or con-
tact closure provided by the peripheral equipment between a power bus (120 VAC) and one of
the ICE-MIAC board input connections. Exact requirements are collected during the job survey
and documented in the job prints. The illustration below shows a typical switch wiring example.
Peripheral or
COP switch
Outputs Refer to your job prints (drawings -9 nn or -CT) to see exactly how your out-
puts are configured. Typical usages include in-service lights, emergency power lights, nudging
buzzers, floor chimes, car-riding lanterns and chimes, and car call button indicators (lights). To
complete an output, the installer wires the lamp, buzzer, etc. between a power bus and one of
the ICE-MOR output connections. Exact requirements are collected during the job survey and
documented in the job prints. Different blocks of outputs may be connected to different buses.
The illustration below shows a typical (lamp driving) output wiring example.
The correlation between input and output is assigned at the factory according to the job survey
and the correct wiring is stipulated on the job prints. It is imperative that, if any changes or
additions are made, MCE be contacted so that the job prints may be updated to reflect current
connections.
Input/Output Wiring Inputs and outputs are wired to pluggable terminals on the car-
top or controller ICE-MIAC (inputs) and ICE-MOR (outputs) boards. The connector numbering
is the same on input and output boards. Terminal arrangement is shown in the illustration
below.
#16 #32
#1 #17
2-13
Construction Mode
Equipment Grounding
For good grounding, quality materials and methods must be used. Grounding must conform to
all applicable codes. Proper grounding is essential to safety and reduces noise-induced prob-
lems:
Provide equipment grounding in accordance with NEC Article 250 and/or the local electri-
cal code, as applicable.
The grounding wire between equipment cabinets may follow a branching or daisy-chain
configuration but the wire must terminate at the last controller and NOT loop back.
You must provide a direct, solid ground to the controller and motor. An indirect ground,
such as the building structure or a water pipe, may not provide proper grounding and
could act as an antenna radiating RFI noise and interfering with electronic equipment
in the building.
The conduit containing the AC power feeders must not be used for grounding.
Figure 2.5 Controller Cabinet Ground Wiring
ACCEPTABLE ACCEPTABLE
NOT ACCEPTABLE
Input
Power Output
Ground Ground
Ground
Ground
2
Building Ground
Note
The grounding instructions provided in the job prints are specific to your job and are the con-
trolling document if any question arises.
2-15
Construction Mode
Danger
Be certain that power is OFF at the main disconnect before proceeding.
Caution
Typically, the iLink cartop box has not been installed at this point. If the cartop box has
been installed and connected, it MUST be disconnected before checking for shorts in the
controller cabinet. This is easily done by simply unplugging all field-wired connectors in the
cartop box before checking for shorts to ground.
1. Using a standard screwdriver, temporarily disengage all fuses at the top of the iPower
box by turning them counterclockwise until they pop up. Dont place a cap on a fuse
holder without a fuse in it. The cap can get stuck and be hard to remove.
2. Disengage all fuses at the bottom of the iBox (just below the logo).
3. Release the screws that hold the iPower box
closed and open the enclosure. Disengage all
the fuses from the fuse block inside (towards
the top of) the iPower box by lifting them clear
of their sockets at one end.
4. Measure the resistance between the iBox #1
(Common) bus and terminals that have a field
connection (DZ down to SP4 on the left side of
the iBox).
5. Measure the resistance between the #2
(120VAC) bus terminals and the #1 bus.
6. Measure the resistance between the #3 (110VDC) bus terminals and the #1 bus.
7. Check for shorts to ground on motor power terminals L1, L2, and L3.
8. Check for shorts to ground on brake terminals B1 and B2.
9. If no shorts to ground are discovered, re-engage the fuses. Refer to the job prints for fuse
location if necessary.
Note
All conductors entering or leaving the controller cabinet must be through conduit. High voltage,
high current conductors, such as power conductors from the fused disconnect or isolation
transformer, must be separated from control wires. It is essential that tachometer/velocity
encoder control wires be routed through a separate conduit away from high current conductors.
Incoming power to the controller and outgoing power wires to the motor must be in their
respective grounded conduit.
2
The majority of iControl installations use an iField Brake Module to provide selective voltages
to precisely control brake picking, brake hold, brake application, and brake timing. DC installa-
tions may also use auxiliary power inputs. In these cases, the job print details for AC input wir-
ing from the transformer may include connections specifically for auxiliary brake and input
power. Read and follow the job prints carefully.
2-17
Construction Mode
Note
Proper motor branch circuit protection in the form of a fused disconnect switch or circuit
breaker must be provided for each elevator according to applicable electrical code. Each discon-
nect or breaker must be clearly labeled with the elevator number. The electrical contractor must
determine the wire size for the main AC power supply and for the wiring from the disconnect or
breaker to the drive isolation transformer.
2. If the car is part of a group, the cars in the group must be wired to provide power to the
group cabinet. If this is the case, refer to the Group Supervisor Field Wiring print in the
job prints. Group power is provided by the car controllers as shown in drawing -2. The
main AC power supply wiring size must be determined by the electrical contractor.
2a. Check the phase-offset of the individual car ST2-bus lines before connecting them
to the Group cabinet. Use a voltmeter set to AC volts to measure between adjacent
car ST2-bus terminals in the Group cabinet. The meter must read less than
10VAC. If the reading is higher, reverse the power leads going to the car T1 trans-
former at L1 and L2 and measure again.
Caution
All 2 bus power from car to Group cabinets must be in phase. Connecting out-of-phase
power WILL cause damage.
2b. A separate conduit or wiring trough must be provided for the System (car-to-car)
Ethernet network. Wiring is fully detailed in the job prints. These details must be
followed exactly.
2c. If applicable, also wire according to the Group Interconnects to Individual Car
Cabinets print. Be sure to ground all cabinets according to instructions.
2d. Refer to the iCentral (Group Supervisor) Field Wiring Print for Group Controller
field wiring instructions.
3. Connect AC supply wiring to the isolation transformer, and wiring from the transformer
to the controller exactly as shown in the job prints.
Caution
This procedure assumes that no field wiring has been connected to the controller. If field
wiring has been connected, disconnect it before beginning this procedure. Before applying
power, physically check all power resistors and other components located in the resistor and
controller compartments. Components loosened during shipment may cause damage.
NOT FUNCTIONAL
Note
The controller microprocessor board has battery backup for logic retention. An insulator pre-
vents the battery from discharging during shipment. Remove the insulator now if has not
already been done.
2-19
Construction Mode
2. Power up the controller. The system will take about 60 seconds to boot.
3. If the controller fails to power up, refer to the job prints and check supply connections
and fuses.
Inside the controller cabinet, 120VAC and 110VDC output buses are presented at the lower left
corner of the iBox as shown in the illustration below.
4. Measure from any #2 bus terminal to a Common (#1) terminal and verify 120VAC (+/-
10%).
5. Measure from any #3 bus terminal to a Common (#1) terminal and verify 110VDC (+/-
10%).
-1
COM
-1
-1
-1
-2PI
120 VAC
-2PI
-2
-2
-3HA
110 VDC
-3HA
-3
-3
Power for PC board circuitry is provided through a 5-position, pluggable connector on the right
side of the iBox (near the Computer and Drive Reset buttons) as shown below.
6. Measure from each of the voltage terminals to GND to verify -15VDC, +15VDC, and
+5VDC respectively (+/- 2%). Note: Place meter on AC range and check each supply to
ensure AC voltage does not exceed 0.050 VAC.
7. If any bus voltage is missing, check the associated fuse. The fuses are labeled with the
bus numbers and are located at the top and bottom of the iBox.
8. Check voltages at panel mounted terminals L1X, L2X, and L3X (if present).
9. Check voltages at X1, X2, X3, and Y1, Y2, and Y3 on the SCR drive. They must be within
-5% to +8% of the value shown on page -SCR of the job prints. If they are not, contact
MCE Technical Support.
10. Power the controller down (in preparation to continue wiring equipment).
Keep DC motor wires separate from control wires both inside and outside the controller cabi-
net. Encoder or tachometer wiring must use a separate grounded conduit.
1. Refer to job print drawing -D1 for SCR drive connections to rotating equipment.
2. Make connections as shown. Be certain to follow schematic notes regarding wire size
and specific motor connections.
2-21
Construction Mode
Note
During adjustment, the resistance across RB may be further adjusted to achieve smooth brake
setting. Refer to job prints for instructions.
RB is in this area
Loosen and slide
the center-tap
The controller i Power ring to change
box release screws resistance.
are in the top and
bottom right corners
of the enclosure. Door
must remain closed
during operation.
Note
Tachometer
(If you are using a velocity encoder, please see the next topic.) When installing a tachometer, do
not mount it near a magnetic field (for example, the motor field coils). Magnetic fields may
cause the tachometer to report incorrect speeds. Note also that any vibration caused by the
tachometer cannot be corrected inside the drive. The tachometer wheel and the surface on
which it runs must be smooth and the tachometer must be mounted so that it can maintain con-
tact without binding or bouncing.
Alignment of the tachometer coupling is extremely important. Most vibration problems are
caused by the tachometer or the way in which it was mounted. The tachometer mounting must
be rigid and the tachometer wheel must be aligned precisely with the surface it is running on
(i.e., the brake drum or drive sheave).
Caution
In geared applications, do not drive the tachometer from the sheave because gear lash
cannot be compensated by the drive unit.
2-23
Construction Mode
Tach wheel
Note
The surface on which the tach wheel rides must NOT be out-of-round. Distortion will cause
poor control and oscillation.
Tachometer Wiring
Note
The tachometer wiring must use a separate grounded conduit. Inside the controller cabinet, if
control wires must cross power wires, they must cross at right angles to reduce the possibility of
interference.
The cable must be routed into the controller cabinet in a separate conduit. The following illus-
tration shows the wiring at the controller end.
Insulate shield at
tachometer end --
Do not connect the
shield to the tach.
iBox Connection End
2-25
Construction Mode
Note
Encoder wiring must use a separate, grounded conduit. Inside the controller cabinet, if control
wires must cross power wires, they must cross at right angles to reduce the possibility of inter-
ference.
Encoder Mounting The following illustration shows two typical encoder installations.
Figure 2.9 Typical Encoder Installations
Typical mounting
Hoist motor bracket
9-pin D
Connector
Velocity
Encoder Hoist motor shaft
Flexible coupling
Hoist motor
Isolator Phenolic
shaft
bushing isolator
Velocity Encoder
It is very important that the encoder does not slip, wobble, bounce, or vibrate due to poor instal-
lation of the shaft extension, coupling, or encoder mounting. It is also important that the
encoder housing be electrically insulated from the motor, machine, or other ground if the
encoder is manufactured by BEI. An insulated encoder mount has been furnished with the BEI
encoder. However, this type of mounting may not be practical for all applications, therefore, the
best method for mounting the encoder and coupling it to the motor must be determined at the
job site.
Encoder Isolation The encoder housing must be electrically isolated from the machine
(ground). To check this:
1. Measure the resistance between the encoder case and the frame of the motor.
The measured value must be infinite for complete isolation.
Encoder Wiring A shielded cable with an appropriate connector at the encoder end is
provided. The controller end of the cable exposes trimmed and tinned individual conductors.
The encoder cable must be routed into the controller cabinet in a separate conduit. The follow-
ing illustration shows the encoder wiring at the controller end of the cable.
Note
These connections are shown for illustration purposes only. Follow the job print instructions
for your specific encoder connections they may be different than those shown here. Z+ and Z-
connections are rarely used at the controller-end.
Drain/Shield
Purple
Gray
Green Quadrature 2
data from
Blue encoder
Black
Power to
White encoder
iBox
Caution
The encoder used must be rated up to 15-volts.Do not coil excess Encoder cable near high
voltage components noise may be induced. If the cable must be shortened, trim it at the
controller end. Do not cut and re-splice in the middle of the cable or shorten at the Encoder
end.
2-27
Construction Mode
The wiring instructions for these switches are on the job prints.
1. Refer to the job prints.
2. Wire the cartop safety switches as shown.
Note
The Cartop Safety Relay is located in the cartop interconnect box. If the box is not yet installed,
the relay must be temporarily bypassed to get the car operating in construction mode. For now,
using the switches and terminals available to you, wire as much of the string as you are able.
The wiring instructions for these switches are on the job prints.
1. Refer to the job prints.
2. Wire the hoistway safety string switches as shown.
Danger
Make sure the Emergency Stop switch is wired in series between SAFH and SAFC to allow
emergency stopping while working on the cartop.
2-29
Construction Mode
3. Connect a Safe push button switch between the #3 bus and the direction push buttons.
4. Connect a Down push button switch between the Safe switch and the iControl ICTD ter-
minal as shown (active high).
5. Connect an Up push button switch between the Safe switch and the iControl ICTU ter-
minal as shown (active high).
Applying Power
1. Set the iBox Inspection switch to the Inspection position.
2. Set the Controller Stop switch to the Stop position.
3. Set the Test switch to On.
4. Turn on power at the main disconnect.
5. Watch the front panel displays of the iBox, the controller will take about 60 seconds to
initialize.
6. Check the iBox Computer, Safety A, and Safety B status LEDs. The LEDs should be
lighted solid green.
The iBox may be accessed using iView or the iBox keypad. However, both are not allowed to
make changes at the same time. By default, the iBox keypad has control but once an iView user
has acquired write privileges (Privilege/Acquire) the keypad is prevented from making changes
until the iView user relinquishes the write privilege.
Note
About LANs: LAN stands for Local Area Network. A LAN is basically several computers (or
smart equipment with a computer inside like the iBox) all connected to a common point (the
hub) so they can communicate with each other. In order for a message from one computer to
reach the computer (or iControl/iBox) it wants to talk to, all the computers connected to the
LAN have to have their own address. The address is called a TCP/IP number. Please refer to
System and LAN Ethernet on page 11-15 for more detail.
Caution
Before connecting the System ethernet cable to the iBox:
1. Verify that the Car ID, in the upper right corner of the iBox display, is correct. Press the
iBox Computer Reset button and when the display returns, verify that Car ID is still
correct. The Car identifier is set on the iView > Controller > Configuration > General tab
(see Configuration - General on page 9-108).
2. Verify that no other iBox in this group of controllers has the same Car ID (see Figure
2.10).
3. Check the Alternate Dispatcher settings on the iView > System > System Configura-
tion > Building tab (see System Configuration tab on page 10-6). Verify that the Auto-
select Preference Order settings are identical on every car in this group of controllers
(see Figure 2.10).
Figure 2.10 Check before connecting the System ethernet cable to the iBox
Check for correct Car ID. Verify that no two Car IDs in the group are the same.
On the iView > System > System Configuration > Building tab, verify that the Alternate
Dispatcher Auto-select Preference Order settings are identical for all cars in the group.
2-31
Construction Mode
Swing Car Additional System Hub Connections for Serial Hall Call
Hall Calls
Group 1
Serial Hall Call
SYSTEM HUB
1 2
Serial
Hall Hall Hall Hall
Call Call Call Call
Driver Driver Driver Driver
iView, Direct
PC used for Direct Connection
192.168.193.2
255.255.255.0 Subnet Mask iCue Group Controller
0.0.0.0 ( . . . ) Gateway
iCue LAN
192.168.191.201
255.255.255.0 Subnet Mask
192.168.191.254 Gateway
iCue SYSTEM
192.168.192.201
255.255.255.0 Subnet Mask
0.0.0.0 ( . . . ) Gateway
2
iView, LAN
PC used for LAN Connection
192.168.191.101
255.255.255.0 Subnet Mask
192.168.192.214
Serial
to
Ethernet
Hall
Call
Driver
2-33
Construction Mode
iView, LAN
BLUE CABLES PC used for LAN Connection
LAN HUB
192.168.191.001
192.168.191.101
255.255.255.0 Subnet Mask
Serial Hall Call
Isolation
1
Board
Serial
Hall
2
Call
Driver
The table below lists factory default addresses for elevator and group controllers. The #3 iBox
port (PC = Direct) is set to 192.168.193.001 and should not be changed. Do not use leading zeros
when setting IP Addresses on a PC (i.e., .021 is entered as .21). (When entering IP Addresses on
the iBox keypad, you must use leading zeros.)
Direct Connections
Unless a Local Area Network (Ethernet) hub has already been installed, you will find it easiest
to connect a PC to the iBox using the #3 PC port on the iBox (direct connection). To make a
direct connection:
1. Connect the iView PC to the controller 3=PC port using only a standard Ethernet cable.
(Do not connect the #3 port through a hub or router.)
Figure 2.13 Ethernet Cable and iBox Ethernet Ports
1 = LAN 2 = System 3 = PC
Direct (no hub) connection to
PC only
Note
iBox #3 Ethernet port address, gateway, and mask are set to default values by MCE. If you have
used your PC to connect to other iBoxes, you probably only need to connect the cable, launch
iView, and select the connection with the appropriate IP information and use that to connect.
When creating direct connections in the iView connections folder, it is a good practice to name
them clearly so they are easy to distinguish (i.e., CarA Direct). The instructions here are
intended to help a first-time user make a direct Ethernet connection between a PC and the iBox.
2-35
Construction Mode
Note
8. In the Local Area Connection Properties dialog, select Internet Protocol (TCP/IP).
9. Click Properties to open the Internet Protocol (TCP/IP) Properties dialog.
2-37
Construction Mode
10. Set the IP Address to match the iBox EXCEPT FOR the last set of numbers. The #3 iBox
port is defaulted to 192.168.193.1. Typically, you can set your PCs IP address to
192.168.193.2.
Note
Note
It is important that a PC have only one IP address assigned. Click the Advanced button and ver-
ify that the PC is configured for only a single IP address (192.168.193.2). If there is more than
one IP address, highlight the additional IP address and then click Remove.
Creating a Direct Connection in iView Once you have set your computer TCP/IP
as described previously, you need to create a connection in iView.
1. Double-click on the iView icon on your computer screen to launch iView.
2. Click File on the menu bar.
3. Select Connection and click New to open the Connection dialog.
2-39
Construction Mode
8. Enter a File name for this connection in the Save As dialog. The suggested file name will
be the same as the one you entered in the Connection dialog.
9. The suggested (default) location for a connection is the Connections folder (My Docu-
ments > Motion Control Engineering > iView > Connections). You may choose another
location using standard windows methods. You may also create sub-folders inside the
Connections folder in which groups of connections can be stored.
10. Click Save to save the connection.
Connecting to the iBox Once the connection is created and saved, you are ready to
connect.
2-41
Construction Mode
Note
If you change the drive type, you must press Computer Reset on the iBox so that iControl can
detect the change on power up.
14. Select the Safety tab. If the Safety tab is not displayed, select Safety from the View >
Configuration menu.
15. On the Safety tab, verify that Construction Mode is checked.
16. Edit and Send changes to iControl as needed.
2-43
Construction Mode
Job Contract Speed 200 fpm 350 fpm 400 fpm 500 fpm 600 + fpm Unit
Pattern scaling 100% 100% 100% 100% 100% %
Door pre-opening dis. 0.00 0.00 0.00 0.00 0.00 inches
Leveling speed 005 005 005 005 005 fpm
Releveling speed 008 008 008 008 008 fpm
Leveling distance 1.20 0.72 0.60 0.60 0.60 inches
Releveling distance 0.60 0.60 0.60 0.60 0.60 inches
Dead zone distance 0.25 0.25 0.25 0.25 0.25 inches
Relevel dead zone dis. 0.15 0.15 0.15 0.15 0.15 inches
2-45
Construction Mode
The safety configuration for the job is stored in two locations in iControl (FLASH and EEPROM
on the SAF board). iControl constantly checks current safety information against stored data
and also compares the data in the two stored locations to make certain they continue to match.
If you make a change on the Safety screen, you will need to do a learn operation to write the
new data to iControl:
1. From the View menu select Setup and click Safety.
2. On the Setup > Safety > Configuration tab, make necessary changes.
3. Select Acquire from the Write privilege menu (if you have not yet acquired write privi-
leges to the iBox), then click Send to save the changes to iControl.
The controller will generate a safety mismatch fault because the settings you have just sent do
not match its stored information.
4. Verify that the iBox is in Inspection mode (Inspection switch set to INSP). Set the Learn
switch to ON.
5. The Learn section of the Safety > Configuration tab should indicate that the controller
is ready to learn.
6. Click on the Learn button. The controller will take a few seconds to learn the new infor-
mation and will then confirm that the safety configurations again match.
7. Set the iBox Learn switch back to the OFF position.
The message window on the Safety> Configuration tab should report Safety Configura-
tions OK.
While iControl is in Construction Mode, specific safety and operational features are automati-
cally bypassed. These are:
All cartop signals, including DP1 and DP2 (position encoder pulse streams).
Normal and Emergency limit switches, NTS and ETS velocity and position logic. Except
Normal Limit Switches DNTD and UNTD.
Only Machine Room and Cartop Inspection are allowed. Will not allow Hoistway Access or
COP Inspection.
EQ signals, both seismic and counterweight derailment, are absent.
Fire sensor signals are absent.
No cartop comm.
2-47
Construction Mode
16. The controller is fully tested according to the connections shown in the job prints before
being shipped from MCE, however, depending upon lighted LEDs noted in Step 15
above:
If Delta P.R., Wye P.R., and 300 P.R. were all ON, interchange any two of the three
wires on the primary winding of the Drive Isolation Transformer.
If Delta P.R. and 300 P.R. were ON, interchange the wires on the SCR Drive between
terminals X1 and X2 or X1 and X3.
If Wye P.R. and 300 P.R. were ON, interchange the wires on the SCR Drive between
terminals Y1 and Y2 or Y1 and Y3.
If only the 300 P.R. LED was ON, then move the wires on the SCR Drive from X1 to X2,
X2 to X3, and X3 to X1. It may be necessary to repeat this step if the 300 P.R. LED is
still ON after power up.
17. If the 300 P.R. LED remains on even after the X1, X2, and X3 wires have been moved a
second time, verify Drive Isolation Transformer labeling:
Interchange any two of the three wires feeding the Drive Isolation Transformer pri-
mary.
Interchange wires X1 and Y1 on the SCR Drive.
Interchange wires X2 and Y2 on the SCR Drive.
Interchange wires X3 and Y3 on the SCR Drive.
Power up and check the 300 P.R. LED.
If the 300 P.R. LED remains ON, power down, then move the wires on the SCR Drive
from X1 to X2, X2 to X3, and X3 to X1. It may be necessary to repeat this step if the 300
P.R. LED is still ON after an additional power up.
If all P.R. LEDs do not turn OFF at this point, there is a probable defect not related to
transformer hookup.
18. If any of the Low Line red LEDs were on, power down and:
Remove the SCR Drive cover.
Check that the 20-pin header (U81) with resistors and jumper plugs is firmly plugged
into the SCR-LGA board (top center) and that the number on the edge of the header
matches the header number on page -SCR of the job prints. Please refer to Current
Limit Adjustments on page 2-63.
19. If, after completing the checks and adjustments listed in Steps 14 through 18, the Drive
Ready LED still does not light, contact MCE Technical Support.
20. If the Drive Ready indicator did light, restore hoist motor brush contact. Reconnect the
brake terminal B1 wire. Please refer to Motor Field Calibration on page 2-53.
2. Follow the on-screen instructions, To perform the drive offsets calibration, ... (cali-
brates Input ADC, Output DAC, Current Sensor, and Current Loop Integral Offset).
2-49
Construction Mode
3. Once the calibration is Done, the offset values shown on the Setup > Drive tab should
match those shown on the Drive Configuration tab (Configuration > Drive > Calibration
tab).
2. Loosen the four captive screws securing the cover on the System 12 drive. Set the cover
aside.
The SCR-LGA board is visible at the top left of the drive enclosure. (The LEDs visible through
the drive cover are mounted on a small PC board which is, in turn, mounted on the SCR-LGA
board.) Refer to Figure 2.14 for the location of test points referenced in this procedure.
3. Output DAC: With the multimeter, measure between jumper JP3 and ground. If nec-
essary, adjust Output DAC on the iView screen until you measure as close to 0.0 volts as
possible (less than 1mV). (Remember to increment or decrement the iView setting, then
Send the value so the adjustment will take effect.)
4. Current loop integral: Use a multimeter to measure between jumper JP7 (A posi-
tion on jumper) and ground. If necessary, adjust Current loop integral on the Drive >
Calibration tab until you measure as close to 0.0 volts as possible (less than 1mV). (You
will need to increment or decrement the iView setting, then Send the value before the
adjustment will take effect.)
5. Current sensor: With the multimeter, measure between test point TP3F and ground.
If necessary, adjust Current sensor on the iView screen until you measure as close to 0.0
volts as possible (less than 1mV). (Remember to increment or decrement the iView set-
ting, then Send the value so the adjustment will take effect.)
6. Zero crossing: Note that the Zero crossing parameter is set to 0.0. This adjustment is
used only if zero crossing must be adjusted for ride quality reasons and the zero crossing
trim pot (R388 on the SCR-LGA board) does not allow sufficient adjustment. See the
following Note.
2-51
Construction Mode
Note
Note trim pot R376 and test point IZO (near jumper JP2). These components are used to set the
zero crossing point if necessary. Trim pot R376 is set and locked at the factory and should not
require adjustment. If, when adjusting the ride quality of the car in later steps, you notice a
sharp bump when transitioning from acceleration to steady speed or from steady speed to
deceleration, you may need to adjust zero crossing.
7. Display the iView Virtual Oscilloscope (View > Oscilloscope) and obtain Write Privilege.
8. On the Virtual Oscilloscope, set Test point 1 = Tachometer Signal.
9. Input ADC - Tachometer: Adjust the Input ADC - Tachometer parameter by enter-
ing and sending small negative or positive values until the Test point 1 value is as close
to 0.0 as possible. The ADC adjustment range is from 0.5 to +0.5.
10. Input ADC - Brake current: Set the Virtual Oscilloscope Test Point 1 = Brake Current
Feedback and then adjust the Input ADC - Brake current parameter by entering and
sending small negative or positive values until the Test point 1 value is as close to 0.0 as
possible.
11. Input ADC - Brake voltage: Set the Virtual Oscilloscope Test Point 1 = Brake Voltage
Feedback and then adjust the Input ADC - Brake voltage parameter by entering and
sending small negative or positive values until the Test point 1 value is as close to 0.0 as
possible.
12. Input ADC - Armature current: Set the Virtual Oscilloscope Test Point 1 = Armature
Current Dampened Feedback and then adjust the Input ADC - Armature current
parameter by entering and sending small negative or positive values until the Test point
1 value is as close to 0.0 as possible.
13. Input ADC - Armature voltage: Set the Virtual Oscilloscope Test Point 1 = Armature
Voltage Dampened Feedback and then adjust the Input ADC - Armature voltage
parameter by entering and sending small negative or positive values until the Test point
1 value is as close to 0.0 as possible.
14. Input ADC - Absolute armature current: Set the Virtual Oscilloscope Test Point 1 =
Armature Current Dampened Feedback and then adjust the Input ADC - Absolute
armature current parameter by entering and sending small negative or positive values
until the Test point 1 value is as close to 0.0 as possible.
15. For the next two adjustments, the Armature Current Test must be enabled in order to
shut off the armature current (Please refer to Armature Current Test Procedure: on
page 9-96).
16. Input ADC - Motor field current: Set the Virtual Oscilloscope Test Point 1 = Field Cur-
rent Feedback and then adjust the Input ADC - Motor field current parameter by enter-
ing and sending small negative or positive values until the Test point 1 value is as close
to 0.0 as possible.
17. Input ADC - Motor field voltage: Set the Virtual Oscilloscope Test Point 1 = Field Volt-
age Feedback and then adjust the Input ADC - Motor field voltage parameter by enter-
ing and sending small negative or positive values until the Test point 1 value is as close
to 0.0 as possible.
Danger
Do not attempt to move the car during calibration.
1. Display the Motor Field layout (View > Layouts > Motor Field).
2. On the Configuration > Motor Field > Control tab, set Field Operation to Open Loop.
3. Place the iBox Inspection switch in the INSP position. Verify that the iBox displays
Machine room insp.
Note
If the iBox does not indicate that you are in Machine Room Inspection even though the Inspec-
tion switch is in the INSP position, another inspection mode (i.e., cartop inspection) is probably
active. Other inspection modes must be OFF before Machine Room Inspection can be activated.
2-53
Construction Mode
7. On the Setup > Motor Field tab, verify that the Ready indicator is lighted. If it is not, set
the Learn switch to OFF for two seconds, then set it back to ON. (The Learn switch has a
fifteen minute timer. When the timer elapses, software generates a time-out fault, then
ignores the switch setting until it is reset.)
8. Click Calibrate. The indicators show progress through the various phases of motor field
calibration. The message window provides feedback and instructions as required. The
Waiting LED will light while waiting for an instruction to be completed.
9. During calibration, the Calibrating LED will be lighted. When the Done indicator lights,
calibration is complete.
10. Set the Learn switch to the OFF position.
Note
If the system detects a field failure fault, press the Fault Reset button on the iBox after the
motor field is calibrated.
The following messages may be displayed while the Motor Field Calibration procedure is being
performed.
Message/Meaning
The controller is not ready for Motor Field Calibration. Please place the elevator on Machine Room Inspection
and place the LEARN switch in the ON position.
The system is waiting for the CONTINUE button to be pushed.
The system is ready to start the calibration process. Push the START button if you wish to start calibrating
the motor field or push the DEFAULT button if you wish to load the default calibration values.
The controller is done with motor field calibration. Please turn the LEARN switch off.
Caution
The Motor Field > Configuration tab is populated with values learned during motor field
calibration. These values affect motor operation and should not be changed without con-
sulting MCE Technical Support.
2-55
Construction Mode
Note
These manual adjustments are almost never necessary. They are useful only in instances of
extremely poor motor field response.
If, after calibration and settings checks are complete, there are still performance issues, e.g. the
drive Current Limit LED lights at the beginning and/or end of runs or you feel spotting (hesita-
tion) coming into a floor, the hoist motor response to control inputs may not be rapid enough.
In these instances you may be able to manually adjust motor field gains to compensate.
1. On the Configuration > Motor Field > Control tab, set PID/Field proportional to 1.0 and
PID Field integral to 3.0.
If satisfactory performance is not achieved with the above settings:
2. Select Virtual Oscilloscope from the View menu.
3. Set Test point 1 to Field Integral Gain.
4. Monitor iBox test point STP 1 with an oscilloscope.
5. Observe response while changing Voltage/Field standing voltage from the standing
voltage value to the forcing voltage value and back again.
If oscillation or overshoot is observed:
6. Decrease PID/Field proportional by 0.2 and repeat step 4.
7. If reducing PID/Field proportional had no effect, reduce PID/Field integral by 0.2 and
repeat step 4. UNDER NO CIRCUMSTANCES should Field proportional or Field inte-
gral be below 0.25.
If no oscillation or overshoot is observed:
8. Increase PID/Field proportional by 0.5 and repeat step 4. If there is still no oscillation
or overshoot, continue increasing Field proportional by 0.5 increments and repeating
step 4 until you see oscillation or overshoot. When you see oscillation or overshoot,
reduce Field proportional to 50% of its value (not below 0.25).
9. Next, increase PID/Field integral in 0.5 increments while repeating step 4 until oscilla-
tion or overshoot is observed. (DO NOT set Field integral above 10.0.) When oscillation
or overshoot is visible, reduce Field integral by 10%.
The preceding two steps are designed to achieve the desired response using the lowest Field
proportional and integral values possible.
Brake Calibration
This section describes brake calibration for DC systems using the iField Module advanced brak-
ing system. The iField module electronically controls brake voltage output.
Rollback Compensation
In later adjustments, drive and motor settings will be adjusted to control rollback. Since that
has not yet been done, we need to control rollback by adjusting Brake Pick Delay and offsetting
Speed pick delay 1 so that the brake remains set until the motor builds sufficient torque.
1. From the Controller > View menu select Layout and click Brake.
2. On the Brake > Control tab, set Pick delay to 0.000 seconds.
3. Set Speed pick delay 1 to 0.100 seconds.
4. Select Acquire from the Write privilege menu. Then press the yes button on the iBox
to grant the privilege.
5. Click Send to send the changed values to the controller.
2-57
Construction Mode
Calibration
Calibration allows iControl to learn the characteristics of the machine brake.
1. Verify that the iBox Safety OK LED is solidly on.
2. Set the iBox Learn switch to ON.
3. Place the iBox Inspection switch in the INSP position. Verify that the iBox displays
Machine Room Insp.
Note
If the iBox does not indicate that you are in Machine Room Inspection even though the Inspec-
tion switch is in the INSP position, another inspection mode (i.e., cartop inspection) is probably
active. Other inspection modes must be OFF before Machine Room Inspection can be activated.
CONTROLLER FAULT/FUNCTION
INSPECTION STOP BYPASS
INSP RUN ON
OFF OFF
7. On the Setup > Brake tab the Ready indicator should be On. The text box will indicate
any steps that need to be performed.
8. With the Ready indicator lighted, click the Calibrate button. As calibration begins,
watch the display on the tab. The display will report calibration progress and will also
display instructions if you need to complete additional steps along the way. The Waiting
LED will light while waiting for an instruction to be completed. If necessary, click Con-
tinue to continue calibration after performing an instruction.
9. When iControl is ready to begin learning, the screen will display The controller is wait- 2
ing for a direction command in order to proceed. You may command either the Up or
the Down direction. When it does, press and hold the iBox Enable and Up (or Down)
buttons. (The car will not be moved during this procedure.)
10. The Calibrating LED will light as calibration begins. Continue to hold the Enable and Up
(or Down) buttons pressed. The progress indicators to the left of the display will keep
you informed as calibration progresses.
11. When the Done indicator lights, release the Enable and Up (or Down) buttons. Calibra-
tion is complete.
12. Set the iBox Learn switch to OFF.
The following messages may be displayed during brake calibration.
Message/Meaning
The controller is not ready for Brake Calibration. Please place the elevator on Machine Room
Inspection and place the LEARN switch in the ON position.
The system is ready to start the calibration process. Push the CALIBRATE button if you wish to start
calibrating the brake or push the DEFAULT button if you wish to load the default calibration values.
The controller is waiting for a Direction command in order to proceed. You may command either
the UP or the DOWN direction.
The controller is done with brake calibration. Please drop direction and turn the LEARN switch OFF.
2-59
Construction Mode
3. Display the Operational Status tab. Note that Brake voltage is charted in the Machine
section of the Operational Status tab.
4. With a digital volt meter set to DC volts,
measure brake output voltage across termi-
nals B1 and B2 (located just below the iBox
panel). (A typical terminal block is shown to
the right. B1 and B2 will be labeled.)
5. Press the Enable and Up (or Down) buttons
to lift the brake. Verify that the voltages on
the volt meter are the same as the com-
manded voltage (Pick voltage / Hold voltage
parameters on the Brake > Voltages tab) and
Brake voltage on the Operational Status tab.
The brake should lift but the car should not
move since Pattern scaling is set to com-
mand zero speed.
6. Change the Pick and Hold voltages to one half the current value of the Pick voltage
parameter and save the new values.
7. Press and hold Enable and Up (or Down) and verify brake voltage again. (The brake will
probably not lift since we are outputting only half the Pick voltage.)
8. Change the Pick and Hold voltages back to their job print settings and save them.
9. Change Pattern scaling (Pattern > Common tab) to 100% and send that value to the con-
troller.
2. If you have not yet done so, select Acquire under the Write privilege menu and press the
Yes softkey on the iBox to grant yourself write permission. In iView, click the Send
button to send the changed value to iControl.
3. Reverse the motor field wires at MF1 and MF2.
4. Run the car using the Enable and Up (or Down) buttons. Verify that it travels in the 2
direction commanded.
If any of the System 12 SCR Drive protective devices trip, the DRIVE READY light will go OFF.
Push the Fault Reset button on the iBox and the READY light will turn ON again after a few sec-
onds (if there is no fault in the System 12 SCR Drive).
2-61
Construction Mode
Note
If iLand and iLink are already installed, use the landing system speed (Speed/Actual on the
Operational Status tab) as the speed reference for calibration. If not, use a hand-held tachome-
ter.
1. If you are using a hand-held tachometer, hold it against the hoist or governor rope on
the machine. The car must run at the commanded inspection speed. (iView: Configura-
tion > Pattern > Modes tab/Inspection - High speed, or iBox: Car/Pattern Profile/
Inspection high velocity.) If the measured inspection speed (actual speed) does not
match the commanded value, verify the following:
2. Verify that Pattern scaling is set to 100% (Configuration > Pattern > Common tab).
Analog Tachometer
3. If the job uses an analog tachome-
ter, set the Scaling parameter (Con-
figuration > Drive > General tab >
Speed Reference section) to an ini-
tial value of 1.000.
4. Display the Virtual Oscilloscope
(View > Virtual Oscilloscope).
5. Set Test point 1 = Pattern (Com-
mand) and Test point 2 - Speed
Feedback.
6. Run the car and verify that the Pattern (Command) and Speed
Feedback (Test point 1 and 2 traces) are the same amplitude.
TACH ADJ. trimpot
On the iView oscilloscope (or a DVM connected between STP1
and STP2), compare Pattern Command and Speed Feedback
readouts. They must match within 0.050 VDC while the car is TACH
ADJ.
running at steady state speed. If not, adjust the TACH ADJ
MODEM
trimpot (upper right corner of iBox). The iPower Box door can
be opened slightly to improve access to the TACH ADJ. trim-
pot. Turn the pot slowly. This is a 15 turn trimpot, but the
RS 232
(Digital) Encoder
7. Adjust the Rotational coupling ratio up or down in 0.1 increments until the car is run-
ning at the correct speed.
The first two numbers represent the armature voltage and the
last two numbers represent the armature current for which the
drive is set. Only the most significant two digits are used to represent values. For example, 24
and 07, indicate 240V and 75A respectively. Loosen the four captive screws holding the System
12 Drive cover in place and remove the cover.
The large circuit board at the top of the drive is the SCR-LGA board. The header is approxi-
mately at the top, center of the board.
8. Check the header label and verify that it looks correct for the hoist motor being used on
this job. (Motor plate armature voltage and armature current labels approximately
match the drive header label.)
The drive header label should also match the armature voltage and current specifications shown
in the prints for the job (see Output Ratings on page -D1).
2-63
Construction Mode
Increasing Standard Integral or Proportional gain provides stiffer response while decreasing
them dampens and loosens response. If too little Integral gain (close to 0) is used, the car will
drift when the brake is lifted and control may be sloppy during all aspects of operation, or
severely affected by varying loads. Too much Integral gain and/or Proportional gain will cause
unstable operation, violent oscillation, or overshoot. If some vibration is encountered through-
out the run, increase Drive > Dampening tab/Speed Control, Armature voltage/Dampening-
speed by 0.01 until the oscillation stops (adding Dampening speed voltage will add lag to the
system). Integral gain must be a value greater than 0.0. Otherwise, there may be a steady-state
speed error.
2-65
Construction Mode
2. Next, increase PID-Standard Integral error slowly. Now there will be less rollback at
takeoff and the car will reach the desired speed faster. Too much Integral gain will cause
a speed overshoot or a slower bobbing oscillation.
3. If the car snaps away from the floor, increase Speed pick delay 1 on the Brake > Timers
tab. At this point, a little rollback is not critical as later adjustments will compensate for
it.
4. Monitor the actual car motion by viewing Raw Pattern on the Virtual Oscilloscope. Posi-
tive voltage should indicate the up direction and negative voltage the down direction.
While monitoring, adjust the values of PID-Standard Proportional and Integral gains to
achieve best response. For now, leave PID-Standard Differential Error = 0.00.
The final Error compensation setting should be below 9.0. The goal here is to obtain acceptable
response during Inspection operation of the elevator. Fine tuning for turnover to normal opera-
tion is accomplished in Section 4 of this guide.
1. On the Configuration > Pattern > Modes tab, verify that Standard Profile/High Speed
and Inspection Profile/High Speed parameters are set correctly for this job.
2. Verify that actual car speed on Inspection is equal to the Inspection High speed setting.
Please refer to Calibrating Actual Car Speed on page 2-62.
Verify Pattern Command and Drive Speed Feedback
1. From the View menu, select Virtual Oscilloscope, and set Test point 1 = Pattern (Com-
mand) and Test point 2 = Speed Feedback.
2. Run the car on Inspection and verify that the Speed Feedback trace is following the Pat-
tern (Command) trace. (If Standard Profile/High Speed, Inspection Profile/High Speed,
and actual car speed are correct, this will be the case. If not, verify and correct these set-
tings.)
Default setting
Caution
The default setting for the Following error parameter is 25%. For a car that has
been properly adjusted as described above, after performing the Tach Error Tripping
Threshold Adjustment, a Following Error setting of 10% is fairly typical. You may choose to
leave the Following error parameter at the default setting or higher, but keep in mind that
Following error is a percentage of speed. On a 500fpm job a 25% Following Error allows a
125fpm contract speed deviation before a fault is generated.
2-67
Construction Mode
Note
A Following error setting of 10% is fairly typical. Keep in mind that the Following error margin
is a percentage of commanded speed. On a 500fpm job a 10% Following error allows a 50fpm
deviation from contract speed before a fault is generated.
2-69
Construction Mode
Note
If the Terminal Switches (UNT5/DNT5) have been installed, and you wish to use the reduced
inspection speed option, you may enable it by checking Reduced inspection speed on the Con-
figuration > Pattern > Modes tab. If not, you may enable Reduced Inspection speed after the
Terminal Switches are installed. (Enabling it now, without switches, would cause the car to run
at 25 fpm.)
3. Stop the car so that the car top can be accessed from the top hall door.
Note
NOTE: Car Top Inspection operation automatically overrides Car Panel Inspection operation.
4. Run the car from the Car Top Inspection station, checking the up and down buttons and
the stop switch.
5. While running the car, check clearances and door locks. When all doors are locked,
remove any jumpers from door lock terminals.
6. Verify directional limit switch and final limit switch operation and position according to
page MRW1 or MRW2 of the job prints. The distance between the two switches should
ideally be greater than the distance required to stop the car after the direction command
is removed when the car is on Inspection operation.
7. Verify that the brake has sufficient tension to hold the car under all conditions likely to
be encountered during the installation phase.
Inspection Mode
In This Section
This section provides the information you need to complete field wiring and pre- 3
pare the elevator to operate in Inspection Mode:
iLand Landing System Installation (see page 3-2).
iLink Interconnect Installation (see page 3-13).
Hoistway Limit Switches (see page 3-19).
Load Weigher Installation (see page 3-19).
Brake Monitoring (see page 3-20).
Earthquake Sensor (see page 3-21).
Serial Hall Call (see page 3-22).
Serial COP (see page 3-22).
Cartop Voltage Verification (see page 3-23).
Running on Machine Room Inspection (see page 3-26).
Preparing for Final Adjustments (see page 3-28).
Caution
Instructions in this section assume you have completed all Construction Mode instructions
in the previous section and that the elevator car is running safely and reliably in Construc-
tion Mode. Note that, in the course of installing the iLink cartop box, YOU MUST UNDO the
temporary cartop CTS bypass used to run the car on Construction Mode with no iLink car-
top box installed).
3-1
Inspection Mode
Position Feedback
A simple, durable wheel assembly rides the elevator rail as the car moves. Wheel-to-rail tension
is maintained by two springs. Mounted with the wheel is a magnet that rotates as the wheel
turns. The rotation of the magnet is detected by an integrated circuit (encoder) which generates
two pulse streams, phase-offset by 90 degrees. The encoder generates 348 pulses per foot of
travel.
Direction
By monitoring both pulse streams, iControl Pulse Stream DP1
can tell the direction of elevator travel by
detecting which stream is the first to Pulse Stream DP2
arrive. For example, when the elevator is moving up, DP1 leads DP2. When the elevator is mov-
ing down, DP2 leads DP1.
Position
During floor height learn operations, iControl counts the total number of pulses from the bot-
tom to the top of hoistway travel and also stores the floor height position (pulse count) at each
landing. During normal elevator operation, iControl uses the floor height information and the
encoder pulse count to accurately track the elevator car position in the hoistway. Please refer to
Learning the Floor Heights on page 4-2.
Landing Accuracy
During installation, running in Inspection mode, the elevator is manually leveled at each land-
ing. With the car level at the landing, a six-inch strip magnet is placed near the hollow of the rail
curvature, vertically aligned with a row of three sensors on the iLand landing system. If the car
has both front and rear doors, a second strip magnet is placed on the opposite side of the rail
and a second set of sensors is used. Placement of the magnets in vertical alignment with the
sensors should be as accurate as possible.
During automatic operation, the iController uses signals from the three sensors (Up Level, Door
Zone, and Down Level), factors in speed and position information, and comfortably and accu-
rately lands the elevator car to within 1/32 of floor level.
Logic
If required, the Floor Offset Distance parameter may be adjusted to compensate for inexactly
placed floor magnets (see Calibrating the Floor Offsets in Section 4 of the User Guide). Using
this parameter, you can offset the car level-at-floor point by 0.5 inches.
The positions of the floor magnets are recorded during hoistway learn operations (see Learning
the Floor Heights in Section 4 of the User Guide). Each time a magnet is encountered, the iCon-
troller learns the position of the magnet with respect to the bottom floor. This learned height,
the floor height, is stored in system memory.
Cartop Mounting
The iLand Compact landing system is usually mounted on a pedestal on the elevator cartop
such that the encoding wheel rides the center ridge of the hoistway rail. MCE offers a mounting
pedestal designed to work in most installations, which can be purchased separately (LS-PED-
ESTAL-BSE), or the pedestal may be provided by the installer. Typically, the iLand mounting
pedestal is bolted to the crosshead beams.
Positioning
Refer to the illustration below and to the accompanying instructions to ascertain how iLand
must be positioned and mounted on the cartop.
Guide Wheels
iLand Base
Mounting Pedestal
3-3
Inspection Mode
If the pedestal bends or moves, the encoder information might become inaccurate or be inter-
rupted causing the controller to receive inaccurate information about the cars position, speed,
and direction of travel. Figure 2 below provides the mounting footprint for the iLand chassis on
the pedestal. The slots should provide clearance for 1/2 bolts.
Figure 2. Typical Pedestal for mounting iLand
0
2.
3.0
4.
0
Installing iLand
1. Attach the mounting pedestal securely to the elevator crosshead beam.
2. Place the iLand Compact on the mounting pedestal and slide it into position so that the
Position Encoder Wheel is touching the front face of the rail. If necessary, loosen the
screws that adjust the position of the Leveling Sensor Bracket(s) and slide the brackets
back away from the rail.
3. Move the base of the iLand Compact forward until the Parallel Arms are approximately
vertical and fasten it to the pedestal using four 1/2 (or 3/8) bolts, flat washers, lock
washers, and nuts.
4. Caution! Leveling sensors can be damaged by collision with rail clamps and bolts, etc.
Move the car cautiously until adequate clearance is verified. Damage due to mechan-
ical contact is NOT covered by warranty! See Caution below.
Figure 3.
Caution: Loosen screws and slide the Leveling Sensor
Bracket(s) back away from the rail. At points where the
rails are attached or where rail sections meet, the
clearance may be reduced by clamps, bolts and other
hardware. Check initial floor leveling sensor adjustments
at the worst of these points to make certain the sensors
or other landing system hardware will not be damaged
when the car runs past these points. Check along the
entire rail to ensure adequate clearance. Damage due to
mechanical contact is NOT covered by warranty!
3-5
Inspection Mode
5. Place a magnet on the rail as shown in Figures 4 and 5. below. iLand Compact must be
adjusted so that the Leveling Sensors are centered on the magnet with the face of the
sensor board 1/4 inch (K 1/16 inch) from the surface of the magnet. Magnets may be
stacked to increase height if needed.
Figure 4. Magnet position on the rail (side view)
3-7
Inspection Mode
Note
Blind Hatch - False Floors - Floor leveling magnets must also be positioned in the approxi-
mate location of all false floors. Check the Hall Fixture Location section on the Hoistway &
Machine Room Wiring (MRW1) page in the job prints. Information regarding false floor set-
tings can also be found on the iView Floor data tab (Controller > View > Configuration > Gen-
eral > Floor data). False floors are considered to have only front doors. False floor magnets
should be installed only on the front door side.
There are three important dimensions to keep in mind when attaching the floor magnets:
The magnet must be positioned so that, when the car is level with a floor, the magnet is
lengthwise between the Up Leveling and Down Leveling sensors (see Magnet position on
the rail (side view) on page 3-6) and centered on the Door Zone sensor with the South
pole surface facing out.
The magnet must be attached at an angle of about 12 degrees from the rail hollow (see
Magnet position on the rail (top view) on page 3-6). (This aligns the face of the magnet
with the leveling sensors. 3
The thickness of the magnet strips (the distance from the outer magnet face to the rail
behind the magnet) must be considered so that some magnets do not stick out farther
than others. (This ensures that the gap between the sensors and the magnet face will
remain consistent at different floor levels.) The iLand assembly automatically compen-
sates for some rail distortion using the Position Encoder wheel and the two guide rollers.
Caution
At points where the rails are attached or where rail sections meet, the clearance for the sen-
sors may be reduced by clamps, bolts, and other hardware. Check your initial floor leveling
sensor adjustments at the worst of these points to make certain the sensors or other landing
system hardware will not be damaged when the car runs past these points. Check along the
entire rail to ensure that the clearance between the face of the sensor board and the magnets
is 1/4 inch (K 1/16 inch). Magnets may be stacked to increase height if needed.
Warning! Damage due to mechanical contact is NOT covered by warranty.
3-9
Inspection Mode
3. Move the car down one to two feet. Clean the hollow of the rail where the magnet will be
attached to remove all grease and dirt. (Acetone, alcohol, or another industrial solvent
may be used.)
4. Center the magnet vertically between the marks with the South pole facing outwards.
(Magnets supplied by MCE have an adhesive strip and paper on the North face. If neces-
sary, use a compass to check North/South polarity.)
5. Move the car back into position and verify that the face of the sensor board is within 1/4
(6 mm) K 1/16 (1.5 mm) from the face of the magnet and the sensors are centered on
the magnet. If the iLand Landing System is powered (connected to a working iLink), the
ULM, DLM, and DZ LEDs will all be lighted if the magnet is positioned properly. If not,
adjust the magnet and re-test. Note: If the magnet is less than six inches long, only the
DZ sensor may be lighted when the magnet is positioned properly.
6. When ready, attach the magnet to the rail using a good quality construction glue. Then
move to the next landing, etc. (Some installers prefer to temporarily attach the magnets
and, after adjusting the sensors and learning the hoistway, test their placement. Then go
back and make adjustments before using a permanent glue.)
Cabling Connections
The Position Encoder and Leveling Sensors connect to the iLand Signal board (LS-IPH)
through short, factory-assembled cables with an RJ45 connector at each end. These cables
should already be in place and connected. If they have been removed, they need to be recon-
nected. Refer to Figure 7 for guidance.
Position Encoder
iLand to
iLink Cartop iLand to
Processor iLink Cartop Pro-
Front Door cessor Rear Door
(optional)
3
The cables from the iLand Landing System (LS-IPH board) to the iLink Cartop Processor (ICE-
CTP board) are supplied (C-ETHERENET-BGE-XX). They should be routed through flexible
conduit from the iLand connectors shown in Figure 7 to the iLand Front Door and, if applicable,
iLand Rear Door connectors on the ICE-CTP board in the iLink Cartop Box as shown in Figure
8 (see also iLink Wiring on page 3-15).
Signal Board
(LS-IPH)
Serial Car Call Serial Link
3-11
Inspection Mode
Installing iLink
iLink provides an efficient, one-stop interconnect point between car and hoistway wiring and
iControl. The serial link between iLink and iControl allows the bulk of the travelling cable to be
reduced. The illustration below shows a view of iLink circuitry with the cover removed.
3
This section describes:
iLink enclosure installation
Door signal wiring
Cartop inspection wiring
Cartop safety wiring
Loadweigher wiring
Door operator wiring
The wiring between the iLand landing system and iLink was described earlier. (Please refer to
Cabling Connections on page 3-11.)
3-13
Inspection Mode
Vertical mounting, as shown, is preferred. Mounting the iLink horizontally is acceptable only if
it is well protected from metal filings or other debris that might accumulate and damage electri-
cal components. The dimensions of the iLink enclosure depend upon how many input and/or
output boards are required for a particular job.
iLink Wiring
Like iControl, the iLink cartop box has an always-present, processor board (ICE-CTP) con-
nected through a pluggable bus to input (ICE-MIAC), output (ICE-MOR), and other optional
boards as required by the installation. A typical layout is shown below.
Note
3-15
Inspection Mode
A terminal strip is mounted in the enclosure. The job prints provide details of terminal strip
wiring. A typical terminal strip is shown below.
Note
These instructions assume that the door operator has been installed in accordance with the
manufacturer documentation.
Leveling Signals
1. Refer to the -CT job print drawings.
2. Connect the DZ, DLM, and ULM signals between the iLink CTP board and iControl/
iBox for front and rear (if present) doors as shown.
Level signals, Rear Level signals, Front
Cartop Safety
Caution
The cartop safety relay may have been temporarily bypassed to run the car on Construction
Mode without the iLink cartop box. If so, YOU MUST UNDO this bypass and wire the CTS
contact as part of the safety string at SCT1 and SCT2. Refer to your job prints.
1. Locate SCT1 and SCT2. Refer to the -CT drawings in the job prints.
2. Connect the cartop safety switches as shown:
Cartop Emergency Stop switch
Emergency Exit contact
Safety Clamp
Note
DP1 and DP2 are the quadrature signal from the iLand system that tells the controller the pre-
cise position of the elevator car in the hoistway.
3-17
Inspection Mode
Circuit Board
edge
#1 #17
Note
Each job is different. The job prints accurately reflect the survey information and are the pri-
mary source for installation and wiring information. Review them carefully.
Note
After Terminal Switches (UNT5/DNT5) are installed, verify Inspection Low Speed (iView/Pat-
3
tern/Inspection) is set to 25 fpm and is enabled. UNT and DNT 5 switches are always used in
iControl installations.
Additional information regarding load weigher selection and threshold settings are provided in
Section 4. Please refer to Load Weigher Adjustment for Dispatching on page 4-34.
3-19
Inspection Mode
The brake monitoring contact provides a path between the iBox 110VDC (#3) bus and the SP2D
or Brake Switch input. If the brake fails to pick (or drop) at the proper time, this signal will
cause the controller to generate a Brake Pick Fault (see Brake Pick Fault, BRAKE PICK
FAULT on page 6-16) or Brake Drop Fault (see Brake Drop Fault, BRAKE DROP FAULT on
page 6-15). The fault message is shown on the iBox LCD display, on the iView Operational Sta-
tus tab and in the iView Event Log.
Note
Danger
When installing the switch, take all necessary precautions not to interfere with normal
brake design or operation.
Insulator
CW2
iBox Connections
CW1 3
Car
+24VDC,
uninsulated If the counterweight moves excessively, one or both
wire of the (grounded) rings surrounding the +24VDC
wire will cause that voltage to short, pulling the
CW1/CW2 circuit low and causing the elevator to
enter Earthquake (operating) Mode.
Counterweight
Insulator
3-21
Inspection Mode
Note
For cars operating as part of a Group, the hall call driver is located in the Group cabinet. From
the iCentral cabinet, calls are distributed to car controllers through the MCE System Ethernet
network. Refer to your job prints and the iCue User Guide for installation and cabling instruc-
tions.
Instructions for installing the Serial COP system can be found in Section 5. Please refer to
Serial COP on page 5-48.
1. Refer to job print drawings - Cartop Details (-CTx).
2. The Serial COP inputs and outputs are programmed on the iView Configuration > I/O
Board > Configuration tab. Please refer to Configuration - I/O Boards on page 9-113.
3-23
Inspection Mode
You must then re-learn the Safety Configuration. Please refer to Learning the Safety Configura-
tion on page 2-46.
3-25
Inspection Mode
3-27
Inspection Mode
Door Operator
The door operator must be working properly before final adjustment.
1. Verify that the door fuses are properly installed.
2. Verify that the iBox Car Door Bypass and Hoistway Door Bypass switches are OFF.
3. Check that all door equipment clutches, rollers, etc. are properly adjusted to correct run-
ning clearances.
4. Check the controller prints to make sure any door operator diode installation instruc-
tions have been followed (especially for G.A.L. door operators).
5. Verify that all hoistway and car doors are closed and locked.
6. Run the car through the hoistway on inspection mode to make sure the hoistway is com-
pletely clear.
5. If Not ready is lighted, follow the instructions in the message window until Ready is
lighted.
6. With Ready lighted, click the Learn button.
The controller will learn the car/counterweight position and the Done indicator will light. The
learned Counterweight position is displayed on the Setup > Counterweight tab.
7. Set the iBox Learn switch to OFF and the iBox Inspection switch to NORM.
Counterweight Balancing
On modernizations, the weight of the car is often changed but compensating adjustments to the
counterweight are sometimes overlooked. This adjustment is important for achieving desired
performance and ride characteristics. The following are two ways in which the car / counter-
weight balance can be verified:
Option 2
1. Place a balanced load in the car (specified percentage of full load; typically 40%).
2. On Inspection, run the car to the middle of the hoistway to the position learned by per-
forming the Counterweight Learn Procedure (see Counterweight Learn Procedure on
page 3-28). Verify the position using the Actual Position displayed on the Operational
Status tab.
3. On the iView Virtual Oscilloscope, set Test point 1 to Armature Current signal. You can
view the value displayed on the Virtual Oscilloscope, or connect a multi-meter to test
points STP1 and GND on the right side of the iBox.
4. Starting from the middle of the hoistway each time, run the car up and then down and
note the current amplitude. If the currents are equal, the counterweight is close to the
correct value.
If more current is required to run the car up, add weight to the counterweight or
remove weight from the car and repeat the balancing procedure.
If more current is required to run the car down, remove weight from the counterweight
or add weight to the car and repeat the balancing procedure.
For a drum machine, follow the manufacturer counterweighting recommendations
and test the drum machine limit switches.
5. When the car and counterweight are balanced, record the actual weight in the car for
future reference. Balanced load = _____________lbs.
3-29
Inspection Mode
Run Testing
1. Verify all landing system magnets are installed according to job prints and instructions.
2. On Inspection mode, run the car to the midpoint of the hoistway.
3. Set the iBox Test switch to the ON position.
4. Place the car on Machine Room Inspection, with Cartop Inspection OFF.
At this point, the car should be on Inspection operation and running without oscillation. There
may be substantial rollback when the car first starts.
5. In the iBox Controller Setup/Brake parameters, or on the iView Virtual Oscilloscope, set
Test 1oint 1 to Pattern (Command).
6. Use a digital voltmeter to check the pattern voltage on iBox test point STP1 with respect
to the Common terminal.
7. Verify that Pattern scaling is at 100% (Configuration > Pattern > Common) and that the
Inspection - High speed parameter is at 10% of contract speed (Configuration > Pattern
> Modes tab) or iBox Controller Setup/Pattern Profile). Maximum value for Inspection -
High speed is 150fpm. Verify that the Reduced inspection speed option is enabled and
that Inspection - Low speed is set to 25 fpm.
8. Run the car on Machine Room Inspection and check iBox test point STP1 voltage. If
8.0VDC is equal to Contract Speed, then the reading at 10% should be 0.8VDC (+/- 5%).
9. Set Inspection - High speed to 50fpm.
10. On Inspection, run the car to, or near, the bottom landing. Use test weights to load the
car to 125% of full load in preparation for checking the ability of the brake to hold this
weight.
Danger
If the brake does not hold, the car may slide into the pit. Use extreme caution.
11. On Machine Room Inspection, run the car up the hoistway sufficiently to allow a down
direction run.
12. On Machine Room Inspection, run the car down the hoistway. While the car is moving,
set the iBox Controller Stop switch to STOP to force the brake to apply while the car is
moving. If necessary, adjust the brake to hold the load.
13. Remove the weights from the car.
1. On the iView Virtual Oscilloscope, set Test point 1 to Speed Feedback. Adjust the Virtual
Oscilloscope for greater sensitivity and shorter time period. Please refer to Controller -
Layouts on page 9-173. If you are using a storage oscilloscope, monitor Test point STP1
(lower right side of the iBox) with respect to GND.
The empty car will probably drift up due to the counterweight, even when an attempt is made to
move it down. Perform the following:
2. Adjust brake Pick delay and Speed pick delay 1 on the iView Configuration > Brake >
Timers tab to coordinate the application of the speed pattern with the picking of the
brake to avoid movement of the car under the brake or rollback of the car.
3. Experiment with improving response. A little rollback at this point is not critical as later
adjustments will compensate for it.
4. Verify that Pattern scaling is 100% (Configuration > Pattern > Common tab).
5. Using Speed/Actual on the iView Operational Status tab or a hand held tachometer, ver-
ify that the car speed, while operating on Machine Room Inspection, matches the
Inspection/High Speed setting (Configuration > Pattern > Modes tab) and is 10% of the
Standard/High Speed setting. Please refer to Calibrating Actual Car Speed on page 2-
62 if necessary.
3
Danger
At this point, the iBox Fault/Function Bypass switch should be in the OFF position. Fix all
faults so that no fault is bypassed before proceeding. If this is not possible, exercise
EXTREME CAUTION while making final adjustments.
3-31
Inspection Mode
Final Adjustment
In This Section
This section describes final adjustments to, and complete final inspection of, the
elevator system. At this point, all steps in Sections 2 and 3 should have been com-
pleted.
Learning the Floor Heights (see page 4-2).
4
Verifying One-Floor Run Operation (see page 4-3).
Reaching Contract Speed (see page 4-7).
Learning Normal & Emergency Terminal Limit Switches (see page 4-11).
Synthetic Speed Calibration (see page 4-13).
Feed Forward Gain Calibration (see page 4-15).
Shaping the Speed Profile (see page 4-17).
Controlling the Start of Car Motion (see page 4-20).
Calibrating the Floor Offsets (see page 4-27).
Adjusting Leveling and Final Stop (see page 4-30).
Load Weigher Adjustment for Dispatching (see page 4-34).
Pre-Start Sequence (see page 4-39).
Calibration and Verification of Safety Functions (see page 4-45).
Safety Tests (see page 4-48).
Terminal Switch Faults (see page 4-55).
4-1
Final Adjustment
Note
This is one of the procedures that must be successfully completed before running the elevator
on Test or Passenger (NORM.) operation. Before proceeding, be certain you have verified the
landing system quadrature pulse sequence. Please refer to Verifying Quadrature Pulse
Sequence and Encoder Resolution on page 3-27.
6. If Not Ready is lighted, perform the instructions shown in the message window.
The Ready indicator lights when the car is placed in Inspection mode (with the
Learn switch ON and the ULM sensor is ON without DLM).
7. When Ready is lighted, click Learn. The In Progress indicator lights when the Learn
button is clicked.
If Manual learn type was selected, you are prompted to press and hold the iBox
Enable and Up buttons. The elevator will move up the hoistway at Inspection speed.
You may click Abort at any time to abort the procedure. If the learn process is
aborted, the last saved complete set of values is retained.
8. The procedure is complete when the up normal limit switch (UNTD) is activated (if
Manual learn type, you are prompted to release the Enable and Up buttons) and Done
is lighted.
9. Set the iBox Learn switch to the OFF position.
10. Click the screen refresh button ( ) to update the learned floor height information.
11. On the Hoistway pane, verify that the learned floor heights appear accurate. Also check
the iBox Safety OK status. (Occasionally, the Final Limit Switch may open at the end of
a Learn run.)
For more information about the Floor Heights Learn procedure and the Status messages see
Setup - Floor Heights - Learn Tab on page 9-161.
Note
If a Limits Switches Checksum Fault is generated when the car is removed from Inspection
operation, it will be necessary to set the terminal switches to default values before proceeding
(View > Setup > Terminal Switches tab). Perform the procedure shown in the Terminal Learn
message window titled To default terminal switches, please do the following:.
7. If the car corrects and stops properly, proceed to Initiating a One Floor Run later in this
section.
4-3
Final Adjustment
Note
Because we have not yet learned the speeds and positions of the Normal and Emergency Termi-
nal Limit switches, stay away from the terminals to avoid tripping faults. Remember that Fault
Bypasses are on a 15-minute time limit. If you need more time, set Fault Bypass quickly to OFF,
then back to ON (within two seconds).
The car should now be at a floor. Avoid running the car close to a terminal landing. To initiate a
one-floor run:
1. Register a car call one floor above or below the current
car position:
The car will continue until it reaches a point 3" (76.2 mm) before the floor, then the Door
Zone input will activate. The Door Zone Rear input will be active if the floor has rear doors.
The elevator will continue to level into the floor and stop. The final leveling speed should
be set from 2 to 8 fpm (0.01 to 0.04 m/s). Your actual speed will be a fraction of that since
Pattern scaling is set to 50% at this time.
1. On the iView Virtual Oscilloscope:
Set Test point 1 to Pattern Command
Set Test point 2 to Speed Feedback
(8-volts equals contract speed)
2. Run the car between floors to any intermediate landings (avoid activating terminal
switches). 4
3. Observe that the car starts, accelerates, then decelerates into the floor and stops. If the
car overruns a floor, the relevel function will be activated. The Leveling Speed on the
first approach to a floor and the Releveling Speed (if releveling is necessary) are two sep-
arately programmable values. These values are set on the Configuration > Pattern >
Common tab.
4-5
Final Adjustment
Verify Releveling
1. When the car is at a floor, simulate overrunning by temporarily changing the floor
height Offset (Configuration > Floor Heights > Floor Offsets tab) to 0.50 and pressing
the Send button.
2. Observe the releveling operation. (Return Offset to the proper setting and press Send.)
3. Monitor the brake voltage on terminals B1 to B2 (located just below the iBox). Make
sure that a relevel brake voltage exists to avert stalling or excessive current draw by the
DC Drive during a relevel operation. Gearless machines are intended to drag the brake
during a relevel, so a partial pick is appropriate. Note, however, that if the brake did not
drop fully before the relevel, the reduced brake voltage may still hold the brake fully
picked.
Note
Do not spend a lot of time here working on the brake, just be sure the brake does not stall the
motor on a relevel. Final brake adjustment is a later topic in this section. (Please refer to Brake
Parameter Adjustments on page 4-24.)
Note
Be sure to read this entire section before performing the following procedure. The car must be
on Test operation (iBox Test switch to ON) throughout the setup procedure. This prevents the
doors from operating during adjustment.
4-7
Final Adjustment
For example, if your drive maximum full load output current rating is 180 Amps DC and you
wish to limit the full load amperage to 140 Amps DC, with a 250% acceleration capability, you
must set Armature current limit to 194% (140/180 x 250 = 194%).
Make the calculation and set the Armature current limit accordingly. (If the setting is cor-
rect, you should not see the SCR drive Current Limit indicator LED turn on during nor-
mal operation. You may see the Current Limit LED light during emergency
deceleration, especially during testing.)
Note
In some cases, where the voltage limiting mechanism (as determined by Armature voltage
limit) is severely exercised, the Current Limit LED on the SCR drive may light. This may indi-
cate excessive voltage limiting as well as current limiting. Be aware that a low value for Arma-
ture current limit may result in oscillation at high speeds. Once stable operation is achieved, be
sure to increase Armature current limit to at least 200%.
Pattern Scaling
1. Using Pattern scaling on the
Configuration > Pattern > 4
Common tab, increase con-
tract speed in 10% increments
until the car is running at
80% of contract speed. Moni-
tor performance on the iView
Virtual Oscilloscope. Set:
Test point 1 to Pattern Command (8V equals contract speed at 100% scaling)
Test point 2 to Speed Feedback (8V equals contract speed at 100% scaling)
2. Check for severe overshoot by monitoring Speed/Actual
on the Operational Status tab. Excessive overshoot can
trip the governor. If severe overshoot does not occur, con-
tinue to increase car speed in 10% increments by increas-
ing Pattern scaling incrementally up to a maximum of
100%. Verify that car speed is peaking at no more than 3%
over contract speed (10 fpm @ 350 fpm, 15 fpm @ 500
fpm, etc.).
3. If overshoot occurs, reducing Standard/Low roll jerk (Configuration > Pattern > Modes
tab) may help, however, a Safety A (or B) Contract Overspeed Fault will occur if Stan-
dard/Low roll jerk is reduced too much.
4-9
Final Adjustment
Armature Voltage
While running the car, observe armature voltage by setting Virtual Oscilloscope Test point 1 to
Armature Voltage Synthetic Feedback.
Note
The value show on the Virtual Oscilloscope Test point 1 and output to iBox test point STP1 is
scaled. A value of 8 volts is equal to the System 12 SCR Drive header voltage value shown on
page D1 of the job prints. To calculate the actual value of the reading on the Virtual Oscilloscope
Test point 1 and iBox test point STP1, use the formula: Header value I 8 x Test point 1 value,
e.g. if the header value is 240 volts, a reading of 6 volts on Test point 1 indicates an actual value
of 180 volts (240 I 8 x 6 = 180).
As you approach contract speed, see that hoist motor armature voltage does not severely over-
shoot the desired value of the Armature voltage limit parameter (Configuration > Drive > Safety
tab). Any lighting of the Current Limit LED on the SCR drive at low speeds indicates current
limiting and may indicate voltage limiting if the Current Limit LED lights as you approach high
speeds. Also be sure armature voltage is reaching the desired value as you approach contract
speed. If it is too low (full load up/empty car down), the Field running voltage (Configuration >
Motor Field > Control tab) is too low.
Caution
Before learning the terminal switches, you can trip on terminal position and/or velocity
faults when the terminal switches (UNT1, DNT1, etc.) are activated. Avoid activating the ter-
minal switches until they have been learned.
Note
The Terminal Switches Learn procedure must be repeated whenever Pattern profile parameters
are modified, since the speed at which the car passes these switches will be different.
To Learn the speeds and positions associated with each NTS and ETS switch:
1. Place the iBox Test switch in the ON position.
2. Place the iBox Inspection switch in the INSP position.
3. In iView, display the Terminal Switches layout (View > Layout > Terminal Switches)
4-11
Final Adjustment
4. Refer to the job prints to determine which Normal Terminal Limit switches (UNTn and
DNTn) are required for this installation and where they should be positioned in the
hoistway. Verify that the Learned position on the Diagnostics > Terminal Switches Sta-
tus tab corresponds to the job prints. If not, refer to the Setup > Terminal Switches tab
and perform the procedure titled To default terminal switches, please do the follow-
ing:.
5. Move the car to the bottom landing (on Inspection).
6. Place the iBox Inspection switch in the NORM position to allow the car to synchronize to
a floor.
7. Place the iBox Learn switch in the ON position.
8. If the Not Ready indicator is lighted (Setup > Terminal Switches tab), perform any
instructions shown in the message window.
9. When the Ready indicator is lighted, click Learn. The In Progress indicator will light.
10. You may click Abort at any time to abort the procedure. If the learn process is aborted,
the last saved complete set of values is retained.
11. Place a call to the top terminal landing using the Call Registration panel.
12. When the car stops at the top landing, place a call to the bottom terminal landing.
13. When the procedure is complete, the Done indicator lights and you are prompted to
return the Learn switch to the OFF position. The new NT and ETS switch speeds and
positions are automatically saved to the controller.
14. The learned NT and ETS values are displayed on the Diagnostics > Terminal Switches
Status tab. Verify that all of the switches required for this job have reasonable values dis-
played. If only UNT1 and DNT1 switches are used in addition to UNT5 and DNT5
(always present), the UNT1 and DNT1 values must be 95% of contract speed or less. If
more NT switches are used, UNT1 and DNT1 may have learned speeds equal to contract
speed, but all other NT switches must have learned speeds 95% of contract speed or less.
If some limit switches have learn speeds in excess of their maximum, those switches
must be moved closer to the terminal landings. Alternately, if reduced performance can
be tolerated, the Standard/Deceleration parameter can be reduced.
15. Make several full hatch runs. After each run, on the Diagnostics > Terminal Switches
Status tab, verify that there is a comfortable margin between the last pass speeds and
the Over speed 1 tripping thresholds for the terminal switches used on this job. Also ver-
ify that there is a comfortable margin between the last pass positions and the Upper and
Lower limit position thresholds.
Danger
This procedure must be successfully performed before any passengers are allowed to use the
elevator.
The calibration process requires the elevator to move in both directions and to reach at least
50% of contract speed in each direction. Reaching contract speed, however, will yield the best
results. Even though there is no restriction on the destination landings for the calibration,
movement to both terminal landings will also yield the best results. In other words, reach the
highest speed possible and move as close to the terminal landings as the situation allows.
The result of this calibration process can be verified using the Virtual Oscilloscope by observing
the synthetic speed signal (Synthetic Signal) on one test point in comparison to the speed feed-
back signal (Speed Feedback) on the other test point. When calibrated, the shape and amplitude
of these signals should be similar.
The Setup > Synthetic Speed tab displays the outputs that represent the result of the calibration
process (Gains - Voltage and Current). If these parameters were saved, the Voltage safety cali-
bration and Current safety calibration parameters (Configuration > Drive > Safety tab) should
be equal to these output values.
4-13
Final Adjustment
Note
A manual version of this calibration process is described in Section 2. Please refer to Tach Fail-
ure Calibration on page 2-69.
The calibration process requires the elevator to move in both directions and to reach at least
50% of contract speed in each direction. Reaching contract speed, however, will yield the best
results. Even though there is no restriction on the destination landings for the calibration,
movement to both terminal landings will also yield the best results. In other words, reach the
highest speed possible and move as close to the terminal landings as the situation allows.
Depending on the adjustments made, the physical characteristics of the hoist-motor, and the
physical characteristics of the installation, the optimum value for error compensation may gen-
erally be between 100% and 150% of the calibration value. In other words, overcompensation
may yield the optimum results in some applications. There should, however, be no reason for a
value below the calibration value.
The result of this calibration process can be verified using the Virtual Oscilloscope by observing
the acceleration feed forward command signal (Acceleration (Command)), on one test point in
comparison to the composite armature command signal (Armature Composite Control) on the
other test point. When calibrated, the shape and amplitude of these signals should be similar.
The only discrepancy between the two signals may be a DC offset if pre-torque is not used.
The Setup > Feed Forward Gain tab displays an output that represents the result of the calibra-
tion process (Gain). If this parameter was saved, the Error compensation parameter (Configu-
ration > Drive > Control tab) should equal this output value.
4-15
Final Adjustment
Velocity Pattern
High Velocity
Deceleration
High Roll Flare Jerk Flare Jerk
Jerk Approach Jerk Approach Jerk
Leveling Leveling
Initial Approach Velocity Approach Velocity
Jerk Deceleration Deceleration
Leveling Leveling
Time Distance Distance
Profile Parameters
Initial jerk - defines the transition from zero speed to full acceleration. As Initial jerk
increases, the profile transitions more quickly from starting to maximum acceleration.
4
Values typically range from 4.0 to 8.0 ft/s3 (1.219 to 2.438 m/s3) with higher values result-
ing in a sharper start.
Acceleration - determines the maximum acceleration for the profile. Determines the
maximum current delivered by the SCR Drive during acceleration. The maximum value is
typically 4.0 ft/s2 (1.219 m/s2) and the minimum is usually not less than 2.5 ft/s2 (0.762
m/s2). Values higher than 4.0 ft/s2 (1.219 m/s2) are possible but do not yield significant
improvements in performance.
High roll jerk - is used on short runs where the car is not able to reach High speed before
deceleration must begin. High roll jerk determines how quickly the profile transitions
from maximum to zero acceleration and zero to maximum deceleration. As High roll jerk
increases, the profile transitions more quickly. Lower values provide greater comfort but
are harder to fit into the shortest one-floor-runs. We recommend that you identify the
shortest full height floor and use it when testing parameter values. Typical values range
from a minimum of 4.0 ft/s3 to a maximum of 8.0 ft/s3.
4-17
Final Adjustment
Low roll jerk - is used on runs where the car is able to reach High speed before decelera-
tion must begin. Low roll jerk determines how quickly the profile transitions from maxi-
mum to zero acceleration (High speed) and zero to maximum deceleration. As Low roll
jerk increases, the profile transitions more quickly. Lower values provide greater comfort.
Typical values range from a minimum of 4.0 ft/s3 to a maximum of 8.0 ft/s3.
High speed - determines the maximum speed for this profile. For the Standard profile
this is usually contract speed (ft/min).
Deceleration - determines the maximum deceleration for this profile. The maximum
value is typically 4.0 ft/s2 and the minimum is usually not less than 2.0 ft/s2 with more
common values ranging from 2.75 ft/s2 to 3.75 ft/s2 (0.838 to 1.143 m/s2). The value of
Deceleration is usually slightly less than the value of Acceleration (by 0.25 to 0.5).
Flare jerk - defines the transition from maximum deceleration to near zero speed or to
Approach deceleration. As Flare jerk increases, the profile transitions more quickly from
maximum deceleration to Approach deceleration. Reduction of this parameter is often
used to reduce the tendency to spot or stall near the end of deceleration, and/or to reduce
any tendency for the deceleration rate, as experienced in the car, to bunch up (increase as
the car approaches the floor). The limiting factor in reducing the value of Flare jerk is
inability to fit the profile into the shortest normal one-floor-run.
Approach deceleration - determines the deceleration rate for the transition from Flare
jerk to Approach jerk.
Approach jerk - defines the transition from approach deceleration to Leveling speed. As
Approach jerk increases, the profile transitions more quickly from Approach deceleration
to Leveling speed.
Leveling speed - determines the speed at which the elevator will level into the floor.
Leveling distance - determines the stabilized distance the elevator will travel before
arriving at the destination floor.
Profiles
There are eight programmable profiles addressed on the Pattern Screen:
Standard - used under normal operating conditions. Unless otherwise specified, sug-
gested profile parameter adjustments are assumed to be referring to Standard profile
parameters.
Earthquake - used if an earthquake is sensed by the elevator system during normal oper-
ation (EQI input activated). If you have earthquake operation, you will verify proper oper-
ation during testing.
Emergency power - used when the Emergency power input (EPI) is activated, indicat-
ing a loss of commercial power and that the car is running on generator power.
Emergency slowdown - used when the system requires faster than normal decelera-
tion. It is used in response to situations such as the normal terminal stopping device being
activated or loss of the quadrature signal (positioning signal). Note that the Emergency
rate limited stop parameter (Configuration > Drive > General tab) will limit how fast this
profile can slow down the car. Increasing this parameter will allow higher deceleration
rates to be used for the Emergency Slowdown Profile.
Correction - used when the system is not confident of the car position in the hoistway.
The car proceeds to a known position using the Correction profile parameters in order to
synchronize its position information.
Inspection - used when the system is placed on Inspection/Access operation. The
Inspection profile is also used when the system is learning the building floor heights.
Alternate 1 - used when the Alternate Speed Profile One input (ASP1) is activated.
Alternate 2 - used when the Alternate Speed Profile Two input (ASP2) is activated.
Note
Initial Values for Pattern Parameters - Pattern shape preset can be used to enter
preset values for the Standard profile parameters based on the high speed (contract speed)
of the elevator and the selected shape type (Slow, Moderate or Fast). This provides an
excellent starting point. Please refer to Pattern shape preset on page 9-149.
Contract Speed Overshoot and Current Limiting -To prevent contract speed over-
shoot and/or current limiting from the drive, the Acceleration and Low roll jerk parame- 4
ters can be reduced. The Low roll jerk rate has a slightly greater effect on overshoot at high
speed than does Acceleration. The Acceleration parameter has the most effect on current
limiting. Observe actual car response on iBox test point STP2 and GND (with the Test
point 2 parameter set to Speed Feedback) to verify that there is no overshoot.
Slope of Acceleration / Deceleration - Ideally, the slope of acceleration in volts per
second should be equal to or slightly greater than the slope of deceleration as viewed on an
oscilloscope connected to iBox test point STP1 and COM (Virtual Oscilloscope Test point 1
set to Speed Feedback Filtered). To get approximately equal acceleration and deceleration
speeds in a system where tracking accuracy is very good, Acceleration can be equal to
Deceleration. If tracking is less accurate, set Acceleration greater than Deceleration to get
the same effective rate of deceleration as acceleration.
Final Approach to the Floor -
Final approach to the floor can be
customized in many different ways.
If tracking accuracy is very good, you
can probably program as follows on
the iView Pattern > Common tab:
Leveling speed = Your desired
leveling speed. A typical number
is from 2 to 4.
4-19
Final Adjustment
Pre-torque Adjustments
For installations using an analog load weigher, load information can be used to provide hoist
motor pre-torque as necessary to accommodate load changes at a floor and prevent sagging or
rollback.
Note
Performing safety and buffer tests described later in this section will probably require that you
repeat the pre-torque adjustment described here.
4-21
Final Adjustment
5. On the Configuration > Drive > Pre-Torque tab, adjust the Pretorque balance adjust-
ment parameter until the digital readout for Test point 1, Load Weigher Balanced, is
equal to or as close to zero (0.0) as possible.
6. If Error compensation, on the Configuration > Drive > Control tab, was increased to
compensate for rollback, you may lower the value now.
7. Verify that Pretorque position compensation, on the Drive > Pre-torque tab is set to 0.0.
If necessary, set it to 0.0 and Send it to the controller.
8. Verify that Pretorque gain, on the Drive > Pre-torque tab, is 0.0. If necessary, set it to
0.0 and Send it to the controller.
9. On the Configuration > Brake > Control tab, increase the value of Speed Pick Delay 1 to
2.0 seconds so that any rollback is easily detected.
10. Remove the weights from the car and move the car to one floor below the top landing.
11. Make a one-floor-run down. Check for rollback by either watching the motor or by mon-
itoring the Speed Feedback signal on the Virtual Oscilloscope.
12. If rollback is detected, adjust the Pretorque gain parameter on the Drive > Pre-Torque
tab, and again make a one-floor run down from one floor below the top landing. Repeat
until rollback is no longer noticeable. Then verify that there is no rollback on a one-floor
run going up from one floor below the top landing.
13. Run the car to the bottom landing. Make one-floor runs up and then down, checking for
rollback.
14. If rollback is detected, decrease the value (less positive or more negative) of Pretorque
position compensation, on the Drive > Pre-Torque tab. Repeat until no rollback is
detected on one-floor runs up or down in the lower hoistway. If pull-though is detected,
increase the value (more positive or less negative). Pretorque position compensation has
a range of -5.00o to +5.000.
15. With the car empty, check throughout the hoistway and verify that rollback is not
detected.
16. Place full load weights in the car and check for rollback throughout the hoistway. Verify
that rollback is not detected. Adjust Pretorque gain, on the Drive Pre-Torque tab, if nec-
essary.
17. Again remove all weights from the car. Check for rollback throughout the hoistway and
verify that no rollback is detected. If some rollback has been introduced by adjusting the
Pretorque gain for a full load, optimize the setting for an empty car, since this is the
most frequent condition.
18. Reduce Speed Pick Delay 1, on the Configuration > Brake > Control tab, to the mini-
mum value which still allows the brake to lift fully before motion starts. You should not
feel the car pulling out from under the brake. The brake should lift fully before motion
starts, but avoid unnecessary delay in starting movement.
Note
If this car will be using the load weigher for dispatching functions, e.g. Light load anti-nuisance,
etc., you may want to set the parameters and learn the load values at this time. Please refer to
Load Weigher Adjustment for Dispatching on page 4-34.
Gains 5
Initial
Normal
10
Pattern
0
Time
1. On the Drive > Control tab, enable Options /
Start gain (normal).
2. Set PID-Start (normal) / Proportional to twice
the value of PID-Standard / Proportional.
3. Set PID-Start (normal) /Integral to twice the
value of PID-Standard / Integral.
4
4. Set PID-Start (normal) /Differential to twice
the value of PID-Standard / Differential.
5. Set PID-Start (normal) / Transition Time to 1.0 seconds.
6. Make a one floor run and look for rollback or oscillation at the start of motion.
Rollback
7. If you see rollback, but no oscillation, increase PID-Start (normal) / Proportional, Inte-
gral, and Differential by 25% each.
8. Make a one floor run and again look for rollback or oscillation. If rollback is still a prob-
lem, again increase PID-Start (normal) / Proportional, Integral, and Differential set-
tings by 25% each.
9. Continue testing and adjusting gains as necessary until rollback is controlled but before
oscillation from too much Start (normal) gain becomes a problem.
Oscillation
10. Refer to steps 7, 8, and 9, except begin by reducing Start (normal) / Proportional, Inte-
gral, and Differential by 25%.
11. If oscillation persists, try reducing only the Start (normal) / Differential gain setting.
4-23
Final Adjustment
12. You may also try keeping Proportional and Differential gain as high as possible but
reduce Transition Time in 0.1 second increments until oscillation is diminished but roll-
back remains under control.
Voltage (volts)
T1 = Weakening Delay
T2 = Repick Time
Vp T3 = Hold Delay
Vw
Time (seconds)
T1 T2 T3
2. Display the Configuration > Brake > Control tab and record the original parameters
before making any changes. Verify the following settings:
Weakening delay = 0.00
Repick time = 0.00
3. Set the Pick voltage and the Hold voltage to of the original value of Pick voltage.
4. Slowly increase both Pick and Hold voltages until the brake picks completely. The idea is
to increase or decrease both Pick voltage and Hold voltage identically until the brake
just barely picks all the way. Then, add 5 or 10 volts and verify that the brake still has a
very slow, smooth picking motion (taking 1 to 1.5 seconds to pick). The goal is to find a
brake voltage that allows the brake to transition slowly through the pressure-releasing
part of the movement.
5. Set the Weakening voltage to the same value as Pick Voltage and Hold Voltage. For
geared applications, if the brake holding voltage is not specified, set Weakening voltage
and Hold voltage = Pick voltage.
6. Apply a maximum value of brake voltage, very briefly, at the start of movement. This
gets the brake quickly to the point in the lifting process where a substantial amount of
tension is released. This is done as follows:
Set Pick voltage back to the original value to allow a high initial value of brake voltage.
Set Repick time to 1.00 second to allow a slow transition through the pressure-releas-
ing part of movement, after which the brake voltage briefly returns to a high value to
ensure that the brake fully picks. (See the following note.)
Increase the value of Weakening delay in 0.05 second increments until you see the
brake move more quickly in the first part of its movement so it can reach the stage
where the pressure is starting to be released. Typical values are between 0.10 to 0.45
seconds. The final result will often look as if the brake is lifting at a fairly constant rate,
even though the initial voltage is high. This overcomes the natural tendency for a gear-
less brake to start lifting slowly and then faster the further it lifts.
Note
It is important to realize that full brake Pick voltage is automatically applied for about a second
at the end of the brake Weakening delay, just after the brake has cleared the braking surface,
thereby guaranteeing full lifting after a smooth transition through the zone of pressure release.
After the brief return to full brake voltage, the brake voltage will automatically drop to the Hold
voltage, but must not allow the brake to sag back onto the braking surface.
Verify the manufacturers recommended value for brake holding voltage and set Hold
voltage to that value. If this information is not available, experiment with Hold voltage
to determine the voltage necessary to hold the brake up, and then add a little extra
margin.
7. At this point, a storage oscilloscope is suggested to get the best results from adjustment. 4
Connect the scope to iBox test points STP2 and GND (with the iView Virtual Oscillo-
scope Test point 2 parameter set to Speed Feedback) to view car speed response.
8. Set the horizontal sweep to about 0.5 to 0.2 second per division and increase vertical
gain until you see a microscopic view of the breakaway at the start of movement. A
rough start is characterized by jaggedness at the beginning of the curve; a smooth start
by a smooth transition from the horizontal line to the acceleration curve. Using this
method, you can touch up parameters such as Speed pick delay 1 in the next step.
9. On the Configuration > Pattern > Common tab, set Pattern scaling to 100%.
10. Coordinate the start of the car with brake operation by increasing Speed pick delay 1
(Configuration > Brake > Control tab) until you begin to see rollback at the start of an
empty car DOWN run at the top floor. Then, decrease Speed pick delay 1 until rollback
just disappears.
It may be helpful to reduce the Initial jerk parameter to 5.00 or 4.00 to help provide a
smooth start. Remember that any change in the brake parameters, Initial jerk, or any of
the gain parameters relating to the speed loop will probably affect the coordination of
the starts. Therefore, you must readjust Speed pick delay 1 after any such changes.
4-25
Final Adjustment
Figure 4.4 Effect of Speed pick delay on the start of car motion
Volts
Speed Pick Delay just right
Not enough
Speed Pick Delay
Time
Brake Lifts
Become familiar with the correlation between what is seen on the scope and what is felt in the
car at the start of motion. Use the scope to adjust brake parameters to provide smooth starts. If
the car has sleeve bearings, be sure to evaluate starts without letting too much time pass
between runs to get accurate rollback information. Once you see the effect of the various param-
eter adjustments on car operation, you will see how important it is to have the brake properly
adjusted.
The value of Repick time (Configuration > Brake > Control tab) can be reduced but doing so will
reduce the time that the brake spends accomplishing a slow lift with Weakening voltage
applied. This will eventually cause the brake to start lifting rapidly. Typically, Repick delay
should not be less than 0.50 seconds.
Floor offset calibration can be performed by one or two persons. You will move the car to each
floor that you want to calibrate, and the distance between the car sill and landing sill must be
measured. You can use the form provided to record your measurements (See Floor Offset Cali-
bration Record on page 4-29). You need not perform the calibration for all floors each time the
procedure is performed.
The measured values, in decimal inches, will be entered into iView on the Setup > Floor Heights 4
> Floor Offsets tab). You can make the measurement using a fractional inch square and then
use the conversion table provided to determine the decimal value. But the better way is to use a
machinist square which is marked in decimal inches.
Once the floor offsets have been entered, iControl is able to calculate the exact location of each
hoistway landing sill using the known exact position of the car, known exact position of the tar-
get magnet and the measured distance from the car sill to the hoistway sill. Then, once the car is
adjusted to stop smoothly and consistently, iControl can stop the car spot on at every landing.
4-27
Final Adjustment
1. Display the Floor Offsets Setup tab by selecting Floor Heights from the View > Layouts
menu and then clicking the Setup > Floor Offsets tab.
2. Move the car to the desired starting landing (e.g. top or bottom terminal landing). The
Ready indicator should light. Follow the instructions provided in the text box.
3. Verify that the machine room INSPECTION switch is in the NORM position. It is recom-
mended to place the car on Independent service while performing this calibration.
4. Click Calibrate to begin making offset measurements. The In progress indicator lights.
5. Run the car to each floor where you want to calibrate the floor offset and perform step
#6. It is not necessary to calibrate all floors each time this procedure is performed.
6. Upon arrival at each floor, wait about 10 seconds to allow the car to settle and for iCon-
trol to acquire the cars exact position (Acquired light turns on). Measure and record the
distance the car sill is above or below the hoistway landing sill, and record the direction
(car sill above or below). If the sills are not parallel, record the average measurement.
7. Return to the starting floor and measure its offset last. The Done indicator lights indi-
cating that the measurement portion of the offset calibration procedure is completed.
8. Enter the measured value (decimal inches) in the Measured in column (Offsets table on
the Setup> Floor Heights > Floor Offsets tab). If the car sill was above the landing sill,
enter a plus (+) value. If the car sill was below the landing sill, enter a minus (-) value.
9. Click Send to send the new offset values to the iController.
.
Table 4.1 Floor Offset Calibration Record
4-29
Final Adjustment
Final Stop
There are many items to consider for a smooth and accurate stop. Each contributes to the final
result:
Brake drop delay - First adjust Brake drop delay on the Configuration > Brake > Con-
trol tab to provide too much delay in dropping the brake so you can clearly see the com-
plete electrical stopping characteristics of the hoist motor. Keep these characteristics in
mind as adjustments are made. It may be necessary to change Brake drop delay more than
once to clearly see the results. It is most important to never drop the brake on a moving
motor.
Normal rate limited stop - Adjusting Normal rate limited stop (Configuration > Drive
> General tab) will also determine how harshly the stop is felt (higher values yield harsher
stops). Lower values may require a larger dead zone. To prevent the car from pulling
through under the brake, do NOT set this parameter to 0.0.
Voltage decay time - Adjusting Voltage decay time (Configuration > Brake > Voltages
tab) determines how softly the brake drops (higher values yield softer drop). If Voltage
decay time is set too high, there will be loss of control during the time between the drive
disconnecting and the brake setting firmly.
Leveling Speed - If this speed is too high, a quick transition to zero speed will occur. This
results in a bump at the stop or possible overshoot at the floor resulting in a releveling
operation. If the leveling speed is too slow, the car will stop very close to the edge of the
dead zone, which will cause the system to relevel frequently. Reasonable values of Leveling
speed (Configuration > Pattern > Common tab) range from 3 to 6 fpm. Before setting the
Dead zone distance, the selection of Leveling speed must be completed so that you are sat-
isfied with the complete final approach to the floor. If overshoot occurs frequently, adjust
Dead zone distance.
Dead zone - The purpose of the dead zone is to ensure that the elevator stops at the same
point whether approaching a particular floor from above or below. The dead zone is a soft-
ware-defined area at a floor, typically 0.25 inches (6 mm) to 0.75 inches (18 mm) in
height. Ideally, the elevator stops in the center of the dead zone.
Because of the mass of the elevator system, it will not stop as soon as it is commanded to
stop. It will slide slightly before stopping. The Dead zone distance should be adjusted so
that the elevator stops consistently at the same position relative to the floor level from
both directions. Dead zone adjustment need only be adjusted for one floor. All other floors
will react in the same way.
Note
Dead zone distance should be adjusted before fine tuning floor height offset.
1. Choose a floor in the middle of the hoistway that allows the car to reach Contract Speed
when approaching from either direction.
2. Start with the default Dead zone distance (Configuration > Pattern > Common tab).
3. Put the car on Test Operation. Verify that the iBox Inspection switch is in the NORM
position. Verify that the iBox Test switch is in the ON position.
4. Run the car to the chosen floor from the top and make sure the car achieves Contract
Speed. Note the position of the car when it stops at the floor (i.e., 1/4 above the floor or
1/8 below the floor, etc.).
5. Run the car to the chosen floor from the bottom and make sure the car achieves Con-
tract Speed. Note the position of the car when it stops at the floor.
6. If the car consistently stops at the same position, (for example, 1/8 above the floor
approaching from above or below), then Dead zone distance is properly adjusted. (Floor
Offset can be adjusted later so that the car stops perfectly level with the floor.) 4
7. If the car overshoots and relevels, the Dead zone distance is too tight. Increase Dead
zone distance and repeat steps 4 and 5.
8. Otherwise, the Dead zone distance is too wide. Decrease Dead zone distance until the
car stops consistently at the same position relative to the floor, repeating steps 4 and 5.
4-31
Final Adjustment
Brake Coordination for Smooth Stops - Proper operation and setting of the brake is
very important to achieve a smooth stop:
1. Before starting, the brake must be operating properly. Geared machine brakes are usu-
ally very simple, however, the brake on a gearless machine requires detailed adjustment
to obtain proper operation. For now, be sure to adjust brake tension to hold 125% of a
rated load (or the value required by your local code authorities). To establish a holding
voltage for a brake in a geared installation, refer to the manufacturers recommended
value. If this information is not available, experiment with the Hold Voltage (Brake Con-
figuration/Voltage tab) to find the voltage necessary to hold the brake and then add a lit-
tle extra margin.
2. If you have already adjusted the brake to the correct mechanical clearances and the
brake is still clunking down too hard when the car stops, increase Voltage Decay Time
(Configuration > Brake > Control tab (iField module, high current braking only). For
low current brakes, decrease the RB resistance inside the iPower Box.
3. Next, adjust Drop Delay (Configuration > Brake > Control tab) so that the brake drops
the instant hoist motor motion stops. The primary means of coordinating brake drop
with motion stop is adjusting Brake Drop Delay. The initial setting should be 0.00 sec-
onds. Increase Drop Delay in increments of 0.10 second until the motor is clearly at zero
speed when the brake drops. The goal is to avoid dropping the brake on a moving motor,
but also to avoid holding the brake up longer than necessary.
4. Adjust Voltage Decay Time to determine how softly the brake drops (higher values yield
softer drop). If Voltage Decay Time is set too high, there will be loss of control during the
time between the drive disconnecting and the brake setting firmly.
Figure 4.5 Effect of Brake Drop Delay on Stopping
Speed Feedback
Releveling Operation
Relevel dead zone distance The Relevel dead zone distance is similar to Dead zone
distance except that the Relevel dead zone distance applies only while the car is releveling.
During releveling, the brake is partially set and the speed is very slow (usually 4 to 8 feet
per minute). Therefore, the car does not slide as much. As a result, Relevel dead zone dis-
tance should be tighter than Dead zone distance. Relevel dead zone adjustment need only
be adjusted for one floor. All other floors will react in the same way. Brake Relevel voltage
(Configuration > Brake > Voltages tab) should be adjusted properly before adjusting the
Relevel dead zone distance. In general, Relevel dead zone must be less than Relevel dis-
tance.
1. Verify that the iBox Test switch is in the ON position. Verify that the iBox Inspection
switch is in the NORM position.
2. Move the car to a floor away from the terminal landing to allow releveling to the floor
from both directions.
3. Put the car on Machine Room Inspection.
4. On Machine Room Inspection, move the car up about 3 inches above the floor. Turn off
Machine Room Inspection to allow the car to relevel down to the floor. Note the position
of the car when it stops at the floor (i.e., 1/4 inch above the floor or 1/8 inch below the
floor, etc.).
5. On Machine Room Inspection, move the car down about 3 inches below the floor. Turn
off Machine Room Inspection to allow the car to relevel up to the floor. Note the position
of the car when it stops at the floor (i.e., 1/4 inch above the floor or 1/8 inch below the
floor, etc.).
6. If the car consistently stops at the same position, (for example, 1/8 inch above the floor
approaching from above or below), then Relevel dead zone distance is properly
adjusted. (Floor Offset can be adjusted later so that the car stops perfectly level with the
floor.) 4
7. If the car overshoots the floor during releveling, the Relevel dead zone distance is too
tight. Increase Relevel dead zone distance and repeat steps 4 and 5.
8. Otherwise, the Relevel dead zone distance is too wide. Decrease Relevel dead zone dis-
tance until the car stops consistently at the same position relative to the floor, repeating
steps 4 and 5.
Rope stretch releveling On high-rise applications, when the car is very low in the
building with hundreds of feet of cable between the machine and the elevator, substantial
movement can occur when elevator load changes, thereby causing releveling. To make the
system more tolerant of this movement, the Relevel distance parameter adjusts the
amount by which the elevator must be away from the floor before the releveling operation
is engaged. The range of adjustment is from 0.00 to 1.00 inch, with a typical value being
0.72 inches.
4-33
Final Adjustment
Ride Quality
If you are experiencing a ride sensation that is not exactly oscillation, but might be described as
a rough texture, it might be due to:
The encoder, attached to the motor shaft, may not be mounted securely, which may cause
bouncing or a slight variation in the speed feedback signal once every revolution. On a
geared machine, the coupling used between the tach or encoder and the motor can also be
a source of vibration. In both cases, the problem is observed by looking at the AC-coupled
encoder speed signal on iBox test point STP2 (with the Virtual Oscilloscope Test point 2
set to Speed Feedback). You may see the vibration frequency increase and decrease with
car speed. This is absolute proof of a mechanical problem with the speed transducer. Elec-
trically induced oscillations will be characterized by a frequency of oscillation that is con-
stant (does not change significantly with speed).
If the above steps do not resolve the vibration, the motor may not have been trimmed to
the machine properly. Use a dial indicator to check alignment of motor and machine.
The car is weighed only when stopped at a landing with doors open. (This is the only time to
anticipate a change in load.) Additionally, if the car were weighed when running, acceleration
and deceleration would be interpreted as weight change.
Rope Tension Load Weigher - Load cells sense the tension of the wire ropes. The load
weigher provides a calibrated analog signal that accurately tracks the loading of the car. Due to
the dynamics of the elevator system, the load represented by the traveling cable and compensa-
tion cables will vary with the position of the car in the hoistway. iControl must learn the empty
and full car load value at each floor. The load in the car can then be determined by reading the
value at a given floor and subtracting the learned empty value for that floor.
Crosshead Deflection Load Weigher - The signal generated by the load sensor represents
the perceived load at the crosshead, which includes the weight of the car, the load inside the
car, the traveling cable, and any compensation cables that might be attached to the car. Due to
the dynamics of the elevator system, the load represented by the traveling cable and compensa-
tion cables will vary with the position of the car in the hoistway. iControl must learn the empty
and full car load value at each floor. The load in the car can then be determined by reading the
value at a given floor and subtracting the learned empty value for that floor.
Isolated Platform Load Weigher - The isolated platform load weigher measures only the
weight within the car. The value is not affected by hoistway position so empty and full values
can be learned without moving the car from floor to floor.
Over load threshold (% of full load): Used to define the load at which it is unsafe to
move the elevator (iView Configuration > Load Weigher tab). If this threshold is exceeded,
the car will remain at the floor with doors open. Typically some type of visual and/or audi-
ble indicator is used to alert passengers that the car is overloaded. (This operation is over-
ridden during Fire Service operation.)
Heavy load threshold (% of full load): Used to define the load value at which hall
calls will be bypassed or reassigned (iView Configuration > Load Weigher tab).
Light load threshold (% of full load): Used to define the load at which a limited num-
ber of car calls may be registered. If the programmed number of car calls is exceeded, all
car calls will be canceled.
Example: Light Load Threshold=20%. If the measured load in the car is less than 20%,
the controller will only allow a certain number of car calls to be registered (number of
calls is set on the iView Configuration > Car Operation > Passenger tab/Anti-Nuisance
controls shown below). If the allowed car value is set to three, only three calls may be
registered if the load is less than 20%. If a fourth call is entered, all car calls will be can-
celed.
Empty load threshold (% of full load): Used to determine when the car is empty. If
the load falls below the threshold the car is considered to be empty. This can be used for
CFSS (Commandeer for Special Services) calls where it is desired that the commandeered
car be empty. Please refer to Car Operation - CFSS Tab on page 9-76.
Note
Setting a threshold value to 00% will disable the corresponding function (anti-nuisance, hall
call bypass or overload). Example: setting the Heavy Load Threshold to 00% will disable the
hall call bypass function.
Load weighing logical functions such as Anti-Nuisance, Heavy Load, and Overload will be inac-
tive until both the full and empty load values have been learned and saved.
4-35
Final Adjustment
Device configuration
3. Select the load weigher device type:
No load weigher: Select if no load
weigher is used.
Discrete contact closure: Select if a
discrete contact closure weigher is
used
Analog Signal: Select if an analog
signal load weigher is used (rope
tension, isolated platform or cross-
head deflection load weigher).
Light load threshold (% of full load): Enter the percentage of full load weight below
which the controller should consider the car to be in a light load condition. Typically
set below 20% of full load. A setting of 00% = OFF. See Load Thresholds on page 4-
35.
Empty load threshold (% of full load): Enter the percentage of full load weight below
which the controller should consider the car to be empty. See Load Thresholds on
page 4-35.
6. When ready, press the SEND button to send the changed values to the controller.
The test weights must be equal to full load value. The learn process must be performed twice,
once for empty car load and once for full car load. In order to learn load weigher values, the ele-
vator must be in normal Passenger operation. The car will not be moved from the starting floor
if the load weigher is an isolated platform displacement sensing type. However, if the load
weigher is the rope tensions sensing or cross-head deflection sensing type, the car must
travel the hoistway, stopping to learn the load values at each floor.
Caution
The load weigher sensor must be calibrated prior learning the load values. Please refer to
Load Weigher Sensor Adjustment on page 4-21. If you are preparing to do safety testing,
including governor and buffer tests, you might want to do them first and then adjust the 4
load weigher sensor and learn the load values, because re-calibrating the load weigher is
recommended following buffer tests.
4-37
Final Adjustment
Clear Learned Values Lighted Empty and Full Learned indicators mean that the pro-
cesses have been successfully run and values stored. Clicking the Clear button will immediately
erase the stored values. You must then repeat the learning process to learn and store new val-
ues.
Pre-Start Sequence
If the car is properly adjusted and running well, but the floor to floor times are not as quick as
you would like, the Pre-Start Sequence parameters (Configuration > Drive > General tab) can
be used to allow the brake and/or motor to be energized while the doors are closing, thereby
allowing the elevator to leave the floor as soon after the doors are locked as possible.
The parameters that affect the Pre-Start Sequence options are found on the Configuration >
Brake > Control tab
The following pages include descriptions of each Pre-Start Sequence option and diagrams
showing the parameters that affect each option and the resulting sequence of operation.
Caution
Do not use Pre-Start Sequence options until drive control parameters have
been adjusted for no rollback and good control at zero speed.
4-39
Final Adjustment
Smooth Pick
Brake Pick Voltage
80% of Pick
Voltage Hold Voltage
Weakening Voltage
Pick Delay
Delay
Weakening
Repick
Time
Hold Delay
For a detailed description of the brake parameters associated with smooth picking and
instructions for adjusting them, see Brake Parameter Adjustments on page 4-24.
Smooth Pick
Brake Pick Voltage
80% of Pick
Voltage Hold Voltage
Weakening Voltage
Pick Delay
Delay
Weakening
Repick
Time
4
Hold Delay
4-41
Final Adjustment
Motor
Door Open Contactor/ Doors Brake Pattern
Limit High Drive Enable Locked High Contactor Applied Pattern
Smooth Pick
Brake Pick Voltage
80%
of Pick Volgage Hold Voltage
Weakening
Voltage
Prestart
Sequence
Delay Pick Delay
Delay
Weakening
Repick
Time
Hold Delay
For a DC control, Pick Delay can be set to zero so long as the Pre-Start Sequence Delay is
adjusted so that the motor is energized and able to hold the car at zero speed when the doors
become locked.
For an AC control, some Pick delay may be required because it takes time for the drive to mag-
netize the motor once the contactor is picked and the drive enabled. A Drive Ready On Fault is
generated if Pick delay is too short.
Motor
Door Open Contactor/ Brake Doors Pattern
Limit High Drive Enable Contactor Locked High Applied Pattern
Prestart Sequence
Delay
Pick Delay Hold Delay
Speed Pick
Delay 2
4
4-43
Final Adjustment
Motor
Door Open Contactor/ Brake
Limit High Drive Enable Contactor Doors Locked High Pattern
Smooth Pick
Brake Pick Voltage
80% of Pick Hold Voltage
Voltage
Weakening
Voltage
Pattern
Applied
Prestart Sequence
Delay
Pick Delay
Delay
Weakening
Repick
Time
Hold Delay
4-45
Final Adjustment
Adjustment Procedure Use the following procedure to adjust the parameters on the
Configuration > Drive > Safety tab used to generate the SCR Loop Over Current Fault.
Note
Full load up is preferable, but if not possible, run empty car down.
2. Set Rated loop over-current (Drive > Safety tab) 5 to 10 amps greater than the observed
steady speed Armature current.
Loop over-current fault time
1. On the Virtual Oscilloscope, set Test point 1 = Over Current Power and Test point 2 =
Over Current Power Threshold.
2. Set Loop over-current fault time (Drive > Safety tab) = 30 seconds.
3. With a full load in the car, run the car up (see Note above). It is best to make runs that
just reach Contract speed momentarily before decelerating and stopping. Observe the
oscilloscope. The objective is to adjust the Loop over-current fault time parameter until
the maximum Over Current Power is 50% to 75% of the Over Current Power Threshold.
4. Adjust the Loop over-current fault time parameter and repeat step 3. Decreasing the
Loop over-current fault time decreases the Over Current Power Threshold and vice
versa.
5. As a final test, make a full hatch run up and down.
4
4-47
Final Adjustment
Safety Tests
iControl provides highly automated safety testing. Before running any tests, the car must be
properly balanced and adjusted. From the iView Safety Tests screen (View > Safety Tests), the
following tests may be run:
Car/Counterweight Safety Test
Electrical Governor Test
Car/Counterweight Buffer Test
Inspection Overspeed Test
Contract Overspeed Test
Emergency Brake Test - Unintended Motion
Normal Terminal Switch Overspeed Tests - Level 1
Normal Terminal Switch Overspeed Tests - Level 2
Normal Terminal Switch Position Tests
Emergency Terminal Switch Overspeed Test
Running a Test
1. Place the iBox in Test mode.
2. Select the desired test on the Safety Tests screen.
3. Set the speed which the car must attain to trigger the condition being tested. (All tests
except Emergency Brake Test/Unintended Motion require a speed input.)
4. Click the Select button. (Sends data to the controller and sets test conditions, including
operating mode and active fault bypasses. Updates instructional display for specific
test.)
5. Visually check on-screen operating mode and fault bypass status displays.
6. Perform instructions displayed in test screen text box.
7. Click the Arm Test button.
8. Place a car call as required to run the car up or down the hoistway (Call Registration
panel).
9. Check Operational Status tab and Event Log (Diagnostics > Event Log) for fault verifica-
tion.
10. Use the iBox Stop switch to stop the test and bring the elevator to an emergency stop if
necessary.
Note
When running a test, you are allowed only one motion cycle of the car. If the test is not satis-
factory, you will have to re-select that test to begin again. Remember that fault bypasses set for
the test will time-out after 15 minutes. If you are delayed in completing a test, you may have to
cycle the Fault Bypass switch to reset the fault bypasses.
Results Faults triggered by the tests are reported on the Operational Status tab and the
4
Event Log. Non-latching (self-clearing) faults will only appear on the Operational Status tab for
a few moments. Check the Event Log if the triggered faults have already disappeared from the
Operational Status tab.
Danger
Be prepared to stop a runaway car if necessary, using the iBox Stop switch. During testing,
normal system safeties are disabled. Exercise extreme caution. Be prepared to take control
and stop the elevator if necessary. Only QUALIFIED PERSONNEL, with adequate experi-
ence and knowledge of elevator equipment should attempt elevator adjustment and testing.
4-49
Final Adjustment
Caution
If necessary, you may end the test and bring the car to an emergency stop using the iBox
Stop switch.
7. Check the hoistway ropes to make sure they are still in their proper grooves before
attempting to move the car.
8. Use whatever method is required to reset the safeties. For flexible quick-clamp safeties,
move the car on Inspection (UP and ENABLE buttons) to release the safety and restore
the safety string.
Counterweight Safety Test - The counterweight safety test verifies operation of the counter-
weight safeties. For this test, position the empty car near the bottom landing and arrange to
over-speed in the up direction. The test is comparable to the car safety test but performed in the
opposite direction. If the counterweight has a governor, remember to jumper it out. Remember
to remove jumpers when tests are complete.
Caution
If necessary, you may end the test and bring the car to an emergency stop using the iBox
Stop switch.
8. Check the hoistway ropes to make sure they are still in their proper grooves before
attempting to move the car.
9. Lift the car off the buffer at inspection speed. (Normally accomplished after the inspec-
tor enters the pit to observe.) The buffer must return to full extension. 4
Counterweight Buffer Test - The counterweight buffer test verifies that the counterweight
striking the buffer will cause the hoist motor to break traction and that the counterweight buffer
will automatically return to its fully-extended state after having been fully compressed. The
empty car is positioned near the bottom landing and arranged to reach contract speed in the up
direction. The test is comparable to the car buffer test but performed in the opposite direction.
If the counterweight has a governor, remember to jumper it out. Remember to remove jumpers
when tests are complete.
4-51
Final Adjustment
Danger
The Emergency Brake test allows the car to leave the floor with doors open. Station person-
nel or use a positive means to make certain there is NO ONE in the car.
4-53
Final Adjustment
Overspeed level 1 - During passenger (NORM) operation, if car speed exceeds the Overspeed
Level 1 threshold at the time a Normal Terminal switch is activated, an Up (or Down) Normal
Terminal Switch (1-5) Level 1 Speed Fault is detected and an immediate slowdown is initiated
using Emergency slowdown profile parameters. For each Normal Terminal switch, the Over-
speed Level 1 threshold is calculated by increasing the learned speed by a percentage of the
learned speed, e.g. learned speed plus 10% of learned speed. The percentage used in the calcula-
tion is determined by the Overspeed 1 margin parameter. You may adjust the Overspeed Level 1
threshold by changing the Overspeed 1 margin parameter (Configuration > Terminal Switches
tab). The default setting is 8%. Normally, you should not have to adjust this setting.
Note
Sometimes short runs to a terminal, especially one-floor runs, will exceed tightly set overspeed
margins. After you learn terminal switches, it is a good practice to try a few short runs to each
terminal and check the Last pass speeds against the Learned speeds for each switch (Diagnos-
tics > Terminal Switches Status tab). If necessary, you can then adjust the Overspeed 1 margin
to accommodate (possibly) higher short run switch speeds. (Overspeed level 1 faults cause an
emergency slowdown into the terminal landing but the fault is automatically cleared so it is pos-
sible to miss the fact that this is occurring.)
Overspeed level 2 - During passenger (NORM) operation, if car speed exceeds the Overspeed
Level 2 threshold at the time a Normal Terminal switch is activated, an Up (or Down) Normal
Terminal Switch (1-5) Level 2 Speed Fault is detected and an emergency stop is initiated (motor
and brake contactors immediately dropped). The Overspeed Level 2 threshold is calculated as
4
105% of the Overspeed Level 1 threshold.
Position - During passenger (NORM) operation, if car position varies from the learned posi-
tion by more than the Position Margin at the time a Normal Terminal or Emergency Terminal
switch is activated, an Up (or Down) Normal Terminal Switch (1-5) Position Fault or an Up (or
Down) Emergency Terminal Switch Position Fault is detected and an immediate slowdown is
initiated using the Emergency slowdown profile parameters. The Position Margin for each Nor-
mal Terminal or Emergency Terminal switch is displayed and may be adjusted on the Configu-
ration > Terminal Switches tab. The default value is 2.0 feet.
Caution
Emergency Terminal (switches) Overspeed is hard-coded at 95% of Contract Speed. Be cer-
tain that the car is traveling well below this speed when an Emergency Terminal switch is
opened to avoid an emergency stop. In some instances, it may be necessary to re-position an
Emergency Terminal switch to achieve this. This value is NOT affected by the Overspeed 1
margin setting.
4-55
Final Adjustment
The following illustration shows the car reaction to overspeed conditions at Normal and Emer-
gency Terminal switches in the down direction.
Hoistway
Car
Emergency Terminal Switch
Car trips Emergency Switch
Normal Stop
Normal Deceleration Parameter
Matching Learned Speeds
Speed
Speed Definitions
95% of Contract Speed: Hard-coded value for Emergency Terminal Switch
Level 1 Overspeed threshold: Learned speed value at switch plus the Limit
One Margin (set on the iView Safety Screen)
Danger
Before the elevator can be turned over to normal passenger use, it is important that no
safety function or circuit remains bypassed. Items to check include, but are not limited to:
All safety switches set to the OFF position
No jumper between SB and 3 (iBox)
No jumper between SAFH and 3 (iBox)
Learn and Fault/Function switches set to OFF (iBox)
No jumper between Gov and 3 (iBox)
Pattern Scaling set to 100% (Pattern screen/Common tab)
Note
If this is a local car (part of a group), the Car identifier parameter, on the Configuration >
General > General tab, must be set so that the Group controller can identify the car to which it is
communicating, see Configuration - General on page 9-108. Initially the Car identifier is
defaulted to 1. The Car Identifier range is from 1 to 20. The Car identifier for each car in a Group
must be unique (no duplicates).
4-57
Final Adjustment
System Options
5-1
System Options
Note
Before using iView to change iCue settings, you must request and be granted write permission.
When you request write permission, you must immediately switch to the iCue PC and grant per-
mission in the pop-up dialog that appears. (This prevents remote iView connections from
changing settings without the permission of machine room personnel.)
iControllers
iCue
iView PC connected
though internet or LAN
iView iCue
Internet System
LAN
User-defined Inputs/Outputs
5-3
System Options
System Interconnect
It can be helpful to have a general understanding of the way the entire iControl system is inter-
connected. This section contains high-level interconnection drawings for:
System Interconnection: Basic car control and dispatcher interconnections.
Dispatcher Interconnection: More detail for dispatcher interconnections.
iControl Interconnection: More detail for car controller interconnections.
Cartop Interconnection: More detail for cartop interconnections.
Figure 5.2 iControl System Interconnection
DISPATCHER
LAN: iView,
iMonitor,
iReport CAR CONTROL CAR CONTROL CAR CONTROL
iView
Car Car Car
Calls Calls Calls
Ethernet
LAN: iView, iMonitor, iReport Connectivity
Other
LAN
Switch
Keyboard To Cars
LAN: iView, iMonitor, iReport
SC- iCue connectivity.
General Field Inputs
to Dispatcher ION
SYSTEM
Ethernet
Other
Safeties iBox
Limits OBD
Cartop
Motor
Module
Serial Bus
Ethernet
LAN Direct Connect (iView)
Other
SYSTEM
Signal Board
(LS-IPH)
Serial Car Call Serial Link
5-5
System Options
Cabinet Installation
Installation of the iCentral cabinet is similar to the installation of an iController cabinet. Please
refer to Machine Room Preparation on page 2-4.
MCE Job Prints MCE job print drawing numbers use the format Job Number Car
Number Drawing Identifier. Thus they are specifically keyed to particular installations. It
makes using and understanding job prints much easier if you take some time to review the job
prints package before beginning controller installation. Drawing identifiers and the information
you can expect to find on that job print drawing are listed below:
N: Nomenclature drawing schematic symbols, wire gauge information, circuit board
names and symbols.
INT: iLink cartop wiring interconnect box to controller connections.
CVR: iBox controls and indicators.
1: AC power connections, power bus information.
2 through nn: iBox/controller wiring.
CC: Contact Count drawing System contact/relay information.
SH: Serial Hall Call wiring.
Note
Depending on your particular installation, you may have extra sheets of particular drawings.
Extra sheets are indicated by an x following the drawing identifier. You may also have differ-
ent or additional equipment in your installation accompanied by different or additional draw-
ings in your job prints. In any case, take the time to become familiar with the job prints before
beginning work. Also, It is very important that you review the wiring guidelines in this section
before bringing wires into the cabinet. When drilling or cutting access holes or during other
machining, do not allow any metal chips to fall into the electronics.
Danger
Be certain that power is OFF at the main disconnect(s) before proceeding.
Note
Caution
All 2 bus power from cars to the iCue cabinet must be in phase. Connecting out-of-phase
power WILL cause damage.
2b. A separate conduit or trough must be provided for the System (group-to-car)
Ethernet network. Wiring details in the job prints must be followed exactly.
5-7
System Options
2c. If applicable, also wire according to the Group Interconnects to Individual Car
Cabinets print. Be sure to ground all cabinets according to instructions.
2d. Refer to the Group Supervisor Field Wiring Print for iCentral field wiring instruc-
tions.
Figure 5.6 Elevator Controller to iCue Cabinet Wiring
MF1
MF2
MF1
MF2
MF1
MF2
L1P
L2P
L3P
L1P
L2P
L3P
L1P
L2P
L3P
L1P
L2P
L3P
B1
B2
B1
B2
B1
B2
B1
B2
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
1
1
1
2
2
2
3
3
3
1
1
1
2
2
2
3
3
3
1
1
1
2
2
2
3
3
3
1
1
1
2
2
2
3
3
3
1 ST2 1 ST2 1 ST2 1 ST2
MF1
MF2
L1P
1
L2P
L3P
B1
B2
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
xx
1
1
1
2
2
2
3
3
3
ST2A, ST2B, ST2C, ST2D, etc. iCue
Caution
This procedure assumes that no field wiring has yet been connected. If field wiring has been
connected, it must be disconnected before beginning this procedure. Before applying power,
physically check all components in the cabinet. Components loosened during shipment may
cause damage.
Note
iCentral is powered from the individual car controllers so that, when any one or more of the car
controllers are powered, iCentral is also powered.
5-9
System Options
,OCAL I6IEW
3#
)/. &IELD )NPUT/UTPUT #ONNECTION $ATA CONVERSION TOFROM SERIAL PROTOCOL
)NPUTS
,!. 2EMOTE I6IEW
3YSTEM (UB 0ERIPHERAL Internet 2EMOTE I-ONITOR
(UB
XXX
XXX
XXX
3ERIAL TO 4#0)0
I#UE
/UTPUTS
3ERIAL
$RIVER
XXX
XXX
I"OX #AR
3ERIAL "US
XXX
I"OX #AR
XXX
3ERIAL (ALL #ALLS
System TCP/IP
iCue uses the System TCP/IP bus to communicate with other MCE components, including:
SC-ION I/O: SC-ION boards provide field inputs and outputs for iCue. Customers may use
these inputs and outputs for a variety of purposes. Typically, an input might be used to
detect a switch closure while an associated output might drive an indicator lamp for the
switch. Normally, one or two SC-ION boards, each providing 16 inputs and 16 outputs are
used. If I/O demands are greater, more may be used. SC-ION boards are connected to the
iCue system bus.
Serial Hall Call: MCE Serial Hall Call greatly reduces the amount of hall call wiring typical
of most elevator installations. The MCE Serial Hall Call bus is a simple, twisted-pair of
16AWG wires along which as many as 980 device addresses may be supported. Power and
communication are both delivered by the serial bus. If current requirements are high, as
many as four serial hall call drivers may be used to support the bus.
Serial Driver: The current demands of the serial bus may be significant if many devices are
simultaneously active. To meet these demands, each bus leg has its own Serial Driver.
Serial to TCP/IP: The Serial Driver communicates with hall call nodes and ION boards
over the two-wire serial bus. The serial output of the Driver is converted to TCP/IP (Ether-
net) and routed through the System hub to the iCue PC. TCP/IP from the iCue PC is like-
wise routed through the System hub and then converted to serial data for the Driver.
System Hub: The System hub is a standard Ethernet hub. The hub routes data so that
TCP/IP communications between connected devices are correctly connected.
iControls: Each car in the group is under the primary direction of its own iBox/iControl.
iCue communicates with all the iControls in its group through the System TCP/IP bus.
LAN TCP/IP
The LAN hub allows local and remote personal computers running iView software to connect to
iCue and all group iControls. The iView application is a user-friendly, graphical user interface
that allows you to easily configure iCue and all the individual iControls in the group.
5
5-11
System Options
System Hub
The System hub connects iCue to the iControls in its
group, to Serial Hall Call drivers through SC-HCE-ME
modules, and to SC-ION input/output expansion
boards. The Serial Hall Call and input/output expansion
board connections are completed at the factory before
the system is shipped and need only be checked to make
certain they are in place. Orange Ethernet cables are
used for connections to the System hub. (The LAN hub
cables are blue.) The cables have a shielded RJ-45 con-
nector at each end.
iCue (typical*) 2 2 2 2
LAN Hub
1. Connect the group and car controllers and the iView PC to the LAN hub as shown in the
illustration below and in the MCE job prints. The job prints are the controlling docu-
ment. Use the blue Ethernet cables provided.
Figure 5.9 Typical LAN (iView) Ethernet Connections
iCue (typical)*
1 1 1 1
iView PC
5-13
System Options
External Connections
As indicated in the LAN hub connection illustration, the elevator group may be connected to
larger area networks in the building or, through T1, DSL, or dial-up modems, to remote sites via
phone lines or the Internet. These kinds of connections are necessary if remote iView or iMoni-
tor access is required.
Unless you are familiar with the technology, you will probably want to contact a networking
specialist or consultant to help. When connecting outside the local elevator group, the installa-
tion is exposed to attempted access by unauthorized personnel. There are several different secu-
rity measures that can be implemented to protect the elevator network. Additionally, if you
connect the iCue LAN hub network to another Local Area Network or to the internet, you may
need to change the factory-default IP addresses for the LAN connections.
Ethernet Addresses
Ethernet (TCP/IP) addresses are assigned to each device communicating on a network. Very
generally, each address is a set of four, number groups separated by decimal points/periods (.).
For example, 192.168.192.20. In order to see one another on a common network, the first three
digits need to match for each device (192 in our example). In order to be able to tell one device
from another, the last three digits need to be different. In our example, 20, so a second device
would have to be any value between 1 and 254 EXCEPT 20 (already in use).
If Ethernet addresses are not properly set, the iControls and iCue will not be able to communi-
cate. The addresses are set and tested at the factory before the system is shipped and should not
need to be changed unless you are making external connections or adding new equipment.
TCP/IP Reference
An Ethernet network is basically several computers (or smart equipment with a computer
inside like the iBox or iCue) all connected together at a single point (the hub) so they can
communicate with each other. In order for a message from one computer to reach the computer
(or iCue/iBox) it wants to talk to, all the computers connected to the network have to have their
own unique address. The address is called a TCP/IP number.
IP Address: #3 iBox 192.168.193.001, factory default.
IP Address: #2 iBox, System see table and following illustration.
IP Address: #1 iBox, LAN see table and following illustration.
IP Address: iCue System port see table and following illustration.
IP Address: iCue LAN port see table and following illustration.
The iCue Group ID (System Configuration screen, page 6-5) must always be set to 1. (See Note
following table.) The table lists the typical addresses used for iCue elevator groups. As many as
five groups can be on a single LAN provided their Group and Car LAN addresses are all unique.
If desired, this is usually accomplished by connecting each of the Group LAN hubs to a sixth,
user-provided hub. You can choose Group and Car LAN addresses. Car System addresses are
controlled by the Car ID setting. The table provides the factory recommended addresses for
each of up to five groups. Your job prints provide specific instructions as to how all of
your IP addresses are set.
Table 5.1 System, LAN, & #3=PC TCP/IP Addresses
Note
The Group ID setting in iView determines the iCue System IP address at which iCue will accept
messages. DO NOT set the Group ID to a setting other than 1 unless instructed to do so
by MCE. The Group ID is reserved for future use. Setting it to a value other than 1 will cause
group-to-car communication to fail. If you need advanced System addressing information,
please contact MCE.
5-15
System Options
Swing Car Additional System Hub Connections for Serial Hall Call
Hall Calls
Group 1
Serial Hall Call
SYSTEM HUB
1 2
Serial
Hall Hall Hall Hall
Call Call Call Call
Driver Driver Driver Driver
iView, Direct
PC used for Direct Connection
192.168.193.2
255.255.255.0 Subnet Mask iCue Group Controller
0.0.0.0 ( . . . ) Gateway
iCue LAN
192.168.191.201
255.255.255.0 Subnet Mask
192.168.191.254 Gateway
iCue SYSTEM
192.168.192.201
255.255.255.0 Subnet Mask
0.0.0.0 ( . . . ) Gateway
iView, LAN
PC used for LAN Connection
192.168.191.101
255.255.255.0 Subnet Mask
5
192.168.192.214
Serial
to
Ethernet
Hall
Call
Driver
5-17
System Options
LAN Ethernet
The iCue PC or iBox and the elevator controller iBoxes are also connected to the LAN hub. The
LAN hub is provided so that you can connect a PC running iView, which will then be able to
access all the iCue and iControl hardware connected to the hub. The TCP/IP addresses for the
LAN network (iView connection) are set at the factory. If your iView PC was provided by MCE,
you can simply connect the iBoxes, the iCue, and the iView PC to the hub and they are ready to
communicate. However, if you provided the PC, you will need to set its IP address properly to
communicate through the hub.
5-19
System Options
9. Set the IP Address to match the iCue LAN EXCEPT FOR the last set of numbers. Typi-
cally, you can set your PCs IP address to 192.168.191.101.
Note
When you open your iCue PC Network Connections, you will see two local area connections.
The LAN Ethernet controls the iCue LAN connection (iView); the System Ethernet controls
the iCue System connection to iBoxes, Serial Hall Calls, and I/O boards and SHOULD NOT
BE CHANGED WITHOUT CONSULTING MCE.
5-21
System Options
9. Set IP address, Subnet Mask, and Default Gateway accord as required to reside on the
new LAN. The values shown below are the factory values.
10. Click OK and follow any instructions to save the changes you made.
5-23
System Options
Pinging
If you suspect that one or more of the devices is still not communicating, you can ping them
from the iView PC. Pinging just lets you send a message manually that just asks for a reply if the
other device can hear you.
To ping:
1. Select Start/Programs/Accessories/Command Prompt from the Windows Start menu.
2. Type in ping and the IP address of the device you want to check. For example:
ping 192.168.191.201
3. If the device is visible and responding, you will see four messages saying Reply from...
4. If not, the IP address for the PC or for the device may not be correctly set.
Group Info
Group ID: The Group ID (1) cannot be changed. All other IDs are reserved for future
use. If you need advanced System addressing information please contact MCE.
5-25
System Options
Write Permission
When some one working in iView wants to change an iCue setting, they have to request permis-
sion by selecting Acquire from the Write Privileges menu. When they do, a pop-up dialog will
appear on the iCue screen in which you can approve or deny the request. This prevents remote
iView connections from making changes without the permission of machine room personnel.
If you request permission from the iCentral iView PC, immediately switch to the iCue PC by
pressing <scroll lock> twice and approve the request in the pop-up dialog. Then switch back to
the iView PC to make the changes.
iCue Watchdog
When iCue is running, there is a utility called iCue Watchdog running in the background. The
watchdog monitors iCue and makes certain that it continues to run as it should.
The watchdog is a Windows Service, which means that it will not show up on the task bar or
icon tray. It runs under the name iCueWatchdogService.exe. Some attributes of the watchdog
include:
The watchdog's purpose is to make sure iCue is running. If iCue is closed through the task
manager, crashes, or locks up, the watchdog will restart it.
The watchdog will also monitor the iCue GUI. It will restart the GUI if it crashes for some
reason. This should have no effect on iCue or system dispatching.
The watchdog should always be running whether iCue is running or not. It gets started in a
batch file that is put into the startup directory.
If you close the iCue GUI (by right-clicking it in the icon bar and selecting exit) the watch-
dog assumes that is done intentionally and will not restart icue.
Starting the iCue GUI after it has been closed will trigger the watchdog to start monitoring
the applications again.
The watchdog has a config file for setting the directory paths of iCue and iCue GUI and
timers (in msec) that it uses to monitor the applications.
Caution
Watchdog information is provided to help you understand how iCue works. Never attempt
to modify Watchdog configuration. Incorrect settings can corrupt the functionality of the
iCue group control software.
5-27
System Options
Fuses
Ethernet Switches
SC-HCE-ME Serial to
Ethernet Adapter
LAN
To Cars
LAN: iView, iMonitor, iReport
SC- connectivity.
General Field Inputs
to Dispatcher ION
SYSTEM
Ethernet
Other
For systems that use the Local/Dispatcher option, the Comm-Connect Cabinet is where the
serial and Ethernet communication equipment is housed and where the connections are made.
Ethernet Switches: The Ethernet switches are the main connection / distribution point for
the Local Area Network (LAN) and System Ethernet networks.
SC-HC-ME Serial to Ethernet Adapter: This component converts the serial signals from
the SC-HCDA Serial Hall Call Driver Assembly to the Ethernet protocol for transmission
on the System Ethernet network. 5
SC-HCDA Serial Hall Call Driver Assembly: This assembly provides power and communi-
cation to the Serial Hall Call Node boards located in each hall fixture box. Power and com-
munication is transmitted on the two wire Serial Bus. Two SC-HCDA assemblies may be
housed in the Comm-connect cabinet. For more information about the Serial Hall Call
option see Serial Hall Call on page 5-30.
SC-ION Serial Control I/O Board: This board is used for serial communication of signals
other than hall call signal (see Checking Serial to IP Connections on page 5-35).
5-29
System Options
The serial bus uses a +/- 15-volt square wave, sampled for both amplitude and duty cycle, for
communication between devices. The positive-going signal actually reaches +40-volts and is
regulated to +24-volts to drive hall call lamps or other loads.
A bus driver is required to provide the output capability necessary to carry the load of multi-
ple, simultaneously lighted lamps. A single controller can have up to four drivers/serial buses
with each bus addressing as many as 980 devices. The photograph below shows a serial hall call
bus driver installed in an iCentral Controller cabinet.
Serial to TCP/IP
conversion for
connection to
System hub
Serial output
from driver
Figure 5.15 Typical Serial Hall Call Connections for a Simplex or Swing Car
iController
I"OX
V'.$
Open power box
5
3ERIAL (ALL
3ERIAL (ALL
#ALL 0ORT
7IRING 6ENT
3#
(#$!
)3/
(ALL #ALL $RIVER
2IBBON CABLE TO )SOLATION "OARD
3#
(#$!
)3/ BOARD
CONNECTS HERE 3#
(#$!
3#
(#$! 3ERIAL (ALL #ALL $RIVER !SSEMBLY
USUALLY MOUNTED INSIDE THE I0OWER
"OX ON 3IMPLEX AND 3WING #ARS 3ERIAL (ALL #ALL "US
(ALL #ALL &IXTURES 3# (#. 3ERIAL (ALL #ALL .ODE "OARDS
5-31
System Options
In a typical installation, a node (SC-HCNT) board is mounted in each hall call receptacle. The
blue and orange wires of the serial bus connect to one end of the board, the hall call buttons and
lamps or LEDs connect to the other end (as shown in the job prints depending upon lamp or
LED connection). During installation, it is easiest to set jumpers on each node board so that it is
uniquely identified for floor ID and call type before you mount the board in the enclosure.
DN
UP
Unused
Floor/PI Address,
10's place Floor/PI Address, Subaddress,
1's place Hall Call Type
Floor number or first digits of serial address* Call type or last digit
of serial address*
* This example sets the Down (DN) input/output to address 124 and the UP address to 126.
The first two digits represent the floor number, in this example, 12.
JP3 JP2
Jumper 3 sets the first digit for the floor (or serial address).
Jumper 2 sets the second digit for the floor (or serial address).
The example shown above would set the Floor number to 12.
Because building floors are not consistently numbered and because a riser may not serve
all floors in a building, MCE creates a table of values for these jumpers according to the
building survey for the job. Refer to your job prints for precise information about setting
these jumpers for your installation.
5-33
System Options
9 8 7 6 5 4 3 2 1 0
DN
UP
JP1
Note
Only the Sub-address jumper, JP1, can have more than one jumper inserted. (It can have a max-
imum of two one to complete the DN address, the other to complete the UP address.) All
other node board jumpers can have ONLY ONE jumper inserted. If more than one jumper is
inserted in JP2 or JP3, the system will not work.
Wiring the Nodes Each serial bus consists of a twisted pair of wires, one orange and
one blue. Each node on the bus (i.e., a hall call button/lantern pair), has a connection to the
orange wire and a connection to the blue wire in addition to button and indicator lamp connec-
tions. See the job prints and instructions accompanying the hall call kits for details.
Serial-to-Ethernet converter
(physically different model
may be used)
Serial communication to
serial-to-Ethernet converter
1. Verify an orange Ethernet cable from the Serial-to-Ethernet converter to the System
hub.
The Serial-to-Ethernet converters each have their own IP address. The IP address is preset at
the factory and should not need to be changed.
Caution
Always power down the serial hall call driver and wait at least one minute before installing,
replacing, disconnecting, or connecting an SC-HCME-EM or -ME serial to Ethernet board
to avoid potential damage to the board PLD from a high voltage spike.
5-35
System Options
Troubleshooting
This section describes some basic troubleshooting techniques for the serial/Ethernet transla-
tion units (Digi boards) and the Serial Hall Call Driver Assembly (SC-HCDA).
Serial/Ethernet Translation
The serial I/O protocol used for MCE serial hall call and serial I/O board connections is trans-
lated to and from Ethernet bus protocol for system level communication over the iControl Sys-
tem network. (System hub in iCentral dispatcher. Orange TCP/IP cables.) One of two
assemblies is used:
SC-HCE-ME
SC-HCE-EM
The base circuit board is the same for both units. The Ethernet port module used is different.
These assemblies are mechanically configured, then programmed using a special utility pro-
gram running on a Windows 2000 or XP personal computer.
SC-HCE Assemblies
The SC-HCE-ME assembly is shown in the illustration below.
Programming header
Status LEDs:
FHCE OK (fuse),
Bus Error
Serial port
activity (green) Network link
(green)
Diagnostics Reserved
(Red) (yellow)
Serial port activity green Indicates activity on Off: serial channel idle.
the serial port Blinking: Active connection.
Network Activity/ green Network Activity: On when network traffic detected; off when no
Diagnostic traffic detected.
Diagnostic: Flashes three times in even duration during power up
or reset, indicating successful startup.
5-37
System Options
Jumpers JP1, JP2, JP3: These jumpers are used to set board options, e.g. the commu-
nications rate of the serial bus. Refer to the label on U2, the FPGA IC (see SC-HCE-ME
Serial/Ethernet Translation Assembly on page 5-36), to determine the software version
and thereby the jumper schedule to use.
Table 5.5 SC-HCE-ME Board Jumper Schedule for FPGA software V6.4.0 45BC0A
Table 5.6 SC-HCE-ME Board Jumper Schedule for FPGA software V6.5.0 1DB38F
Ribbon Cable Connection Point of connection for ribbon cable to serial driver assem-
bly.
Fuse The FHCE OK LED indicates power presence after fuse. The fuse is 1/2A, 250V,
AGC type.
Caution
Always power down the serial hall call driver and wait at least one minute before installing,
replacing, disconnecting, or connecting an SC-HCME-EM or -ME serial to Ethernet board
to avoid potential damage to the board PLD from a high voltage spike.
Trouble Indications
Hall Call buttons do not work
Do building Hall Call buttons light when pressed?
Do building Hall Call buttons stay on until elevator arrives?
Elevator reported to be in Wild Operation (stopping at every floor)
Does the iBox LCD display indicate Emergency Dispatch?
LEDs not lighted on the base board of the serial/Ethernet assembly.
EM: Serial Port and Reserved LEDs lighted solidly. Network Link Status and Diagnostics
OFF.
ME: Both Network Link and Network Activity LEDs OFF.
Hall Call LEDs or lamps flashing or not operating normally.
Quick Check
During power up:
Two red SC-HCE board LEDs (FHCE and Bus Error) should remain on for 30-40 sec-
onds after the Hall Call Driver is powered-up.
After solid-on, LEDs will cycle through a period of start up activity then indicate nor-
mal operation as described below.
Normal operation indication:
Network Link Status LED on solidly (EM top left, green; ME left, yellow).
Network/Serial Port Activity LED flashes once every five seconds (EM top right, green;
ME right, green) when communicating with iCue.
Network/Serial Port Activity LED should flash once when a Hall Call button is pressed.
FHCE (red) LED on SC-HCE board solidly on.
Bus Error (red) LED on SC-HCE board off.
Auto Reset
With no jumper across JP3 on the SC-HCE board, the assembly PLD will initiate a 5
reset every 60 seconds if it does not see communication from iCue.
Check that the iCue software is running properly on the PC. If not, restart iCue by
clicking the Windows Start button and selecting Start/Programs/Startup/iCue.
Recheck.
General Check
1. Check all power and data cable connections.
Port status LED on System hub should light when the Ethernet cable is plugged in
between the hub and the serial/Ethernet board.
Ribbon cable seated properly on the hall call driver and the serial/Ethernet board.
Use a voltmeter to measure between each of the three DC voltages (3.3V, 5V, 9V) on
the serial/Ethernet (SC-HCE) board to ground. Voltages should read the provided
level, +/- 10%.
2. Check the SC-HCE board to see that there are no jumpers across JP1, JP2, or JP3.
5-39
System Options
iView Check Use the iView System I/O Configuration screen, Bus tab to see if trouble is
indicated and to check that hall calls are addressed as specified in your job prints.
1. Launch iView and connect to the group.
2. Open the System I/O Configuration screen and select the Bus tab.
3. Verify the state of the indicator LEDs and that the addresses are as defined in the group
job prints (inputs as expected per serial address and Labels mapped to correct floor).
TCP Address Check The Digi Device Discovery utility may be used to check and, if nec-
essary, reset the TCP/IP address of the serial/Ethernet assembly (SC-HCE-EM or ME). This
utility is available from MCE.
1. Start the Digi Device Discovery utility. The utility will launch, and check the System net-
work for any connected SC-HCE-EM or -ME.
5-41
System Options
3. In the Configure Network Settings dialog that appears, select Manually configure net-
work settings.
4. Check the drawing package for the dispatcher or the Ethernet Address examples draw-
ing in the manual. Please refer to Example of Ethernet Addresses and Connection on
page 5-16.
5. If the IP address of the device is incorrect, set it appropriately.
Note
When entering the IP address, do not enter leading zeros. For example, in the address
192.168.192.056, 056 is entered as 56, with no leading zero.
7. Wait for ten to fifteen seconds (until the Diagnostic LED on the serial/Ethernet assem-
bly blinks for eight to ten seconds and then goes off), then click OK.
8. Restart the iCue PC.
AC power
Quick Test You can do a basic functionality test on the hall call driver. 5
With power applied:
1. Verify 120VAC power to the driver.
2. Unplug the Serial Bus connection (orange/blue wires).
3. Use a voltmeter to check the voltage between SHCS and SHCC. You should see approxi-
mately 30V, + or - 10%. (This voltage will only be present if the SC-HCE-ME or EM is
working properly as verified in preceding troubleshooting steps.)
If this voltage is present, the driver is probably operating properly.
5-43
System Options
Driver Voltages Test The hall call driver can be more thoroughly tested if necessary.
The test is relatively simple on iCentral units shipped after July, 2005 because a female, test
connector has been installed in the middle of the ribbon cable connecting the driver to the SC-
HCE (Digi board) assembly. Earlier units do not have the test connector.
Note
1. Cut three pieces of 22 AWG solid wire 2 in length. Strip insulation off each end.
These will be used as jumpers and test probes during the test.
2. At the SC-HCE board end, disconnect the
ribbon cable connected to the hall call
driver. Note the test connector in the middle
of the cable. Its pinout is as shown.
Note
Flexible I/O
iCue makes extensive use of a serial bus to handle a range of communication and control needs.
The serial bus is used to service the MCE Serial Hall Call System and to control I/O through one
or more SC-ION boards (input/output expansion boards). Each SC-ION board provides 16
user-configurable inputs and 16 user-configurable outputs. Input and output configuration,
using the MCE iView graphical user interface, is described in Section 6 of this guide. This sec-
tion describes physical I/O connections.
5-45
System Options
SC-ION Boards
The number of SC-ION boards in an iCue system will vary depending upon system configura-
tion and the number of additional inputs and outputs required for the job. A typical job might
have one SC-ION board, providing 16 additional inputs and 16 additional outputs.
I/O Connections
Connect inputs and outputs as shown in your job prints. SC-ION board inputs are always
120VAC. Outputs may be configured (in specific groups) to provide either a path to ground or
current to drive indicator lamps/LEDs.
Output State Selection The outputs are divided into three groups. Each group shares
a common. The common may be wired to provide a current source or a path to ground. The
groups are:
Relays 1 4
Relays 5 8
Relays 9 16
The commons for the groups are determined by the connections made to board connector J4.
The appropriate connections are determined during the job survey. Each system is configured
before shipment. You need only connect the inputs and outputs as shown on the job prints.
Board Addresses Each of the 16 inputs and 16 outputs on the board has an address on
the system bus. The addresses are assigned as indicated by the job survey before the system is
shipped. A software tool, running on a Windows platform, is used to set individual addresses
and also to set the address range (10-488 or 10-988) used for the job. To configure the board, a
Windows PC running the software tool must be connected to the board serial port.
Board Programming
Addresses are programmed for each SC-ION
board input and output at the factory using a tool
called SCION Configuration.exe. You should
never have to use this tool without factory techni-
cal support. A typical programming screen from
SCION Configuration is shown for informational
purposes:
5
5-47
System Options
Serial COP
With the Serial Car Operating Panel system, car call buttons connect directly to a serializing
board located in the car station enclosure. Multiple Serial COP boards daisy-chain together to
accommodate high-rise installations with a lot of call buttons.
CAR CALL
BUTTON
+24V
Caution
This system is designed for 24 VDC COM
circuits maximum. Connecting +24V SIGNAL
120VAC or DC will open the input
fuses.
Connection Example:
Universal 4-pin inputs COM
Wiring from the Serial COP board(s) to the iLink cartop box is a short length of shielded cable
with a telephone-style RJ-11 connector at each end. The iLink cartop box supports up to four
serial control panel connections. Communication between iLink and the controller is also serial,
thereby reducing the traveler and hoistway cabling.
5-49
System Options
ICE-COP-2 Board Diagnostics The DIP switches and LEDs in the upper right corner
of the ICE-COP board provide diagnostic information. Please refer to ICE-COP-2 Serial Car
Operating Panel Board QR on page 6-84.
5-51
System Options
Three sets of wires must be connected to the EMCO VK-3v control unit:
1. a. For iControl, EMCO control unit output to ICE-CTP board in the iLink Cartop box:
connect CTP board terminal LW- to EMCO control terminal Com.
connect CTP board terminal LW+ to EMCO control terminal 0-10v.
connect CTP board terminal SHLD to the cable shield (do not connect the shield to the
EMCO control unit. 5
1. b. For IMC or Performa, EMCO control unit output, through the traveler, to the control-
ler.
connect SCR-RI (or SCR-RIX) board terminal LW- to EMCO control terminal Com.
connect SCR-RI (or SCR-RIX) board terminal LW+ to EMCO control terminal 0-10v.
2. 115Vac power, connected to the terminals labeled 115Vac.
3. Sensor wires, connect the control unit as indicated on the sensor wire:
red wired to terminal EXC+
Terminal tool/key
black wire to terminal EXC-
green wire to terminal IN+
white wire to terminal IN-
shield wire to terminal MALLA
Use the Terminal tool/key (wire insertion tool), or
a narrow flat blade screwdriver to open the detent
in the terminal connector to allow insertion of the
tinned wires.
5-53
System Options
Description of Operation
The purpose of the EMCO Load Weigher system is to measure the load in the elevator and pro-
vide usable information about the load to the elevator controller. This information is used for
pre-torquing and for dispatching decisions, e.g. light load anti nuisance, heavy load and over-
load.
The system usually consists of a sensor or group of sensors mounted on the elevators wire
ropes and a control unit. The sensor(s) provide a signal to the control directly related to the
amount of load in the cab. The load weigher control accepts this signal and provides usable data
to the elevator controller in the form of an analog signal.
Press the menu button until the display shows the desired parameter to be changed.
Press the button to select the digit to be modified (digit blinks when selected).
Press the button to change the digit.
Press the menu button twice to save the new value. Once a value is saved the control
will display the next parameter.
If you do not press the menu button twice the changes will not be stored and the con-
trol display will continue to show the parameter you were modifying.
Menu/Programming Order
Installation Menu
Pressing the menu button will scroll through the Installation Menu in the following order:
Calibration
Manual Calibration with Weights
The Calibration with Weights procedure is the most accurate and recommended method of cal-
ibrating the EMCO Load Weigher. This procedure allows the EMCO control unit to do the fol-
lowing:
Learn the empty weight of the car and set this weight as the zero reference (the analog
voltage output from the control unit will be about zero volts at this weight).
Learn a known weight. You place a known weight in the car and enter the actual value of
the weight, in kilograms, into the control unit. The load weigher will then learn this weight
You will also enter the value of the cars overload weight into the control unit.
The EMCO control unit will use this information to scale the analog output so that when
the sensors detect the overload weight, the output voltage is about 10 volts. The analog
output for the weights between empty car weight and overload weight will then be linear
from about 0.0 volts to 10 volts.
Calibration procedure:
5-55
System Options
Press the menu button twice. The control units display begins to count down. Exit
the cartop before the countdown finishes. When the full load weight has been learned,
will be displayed. You can press the menu button until the weight is shown
on control unit display. The weight displayed should be the value of the weights in the
car, in kilograms.
7. Enter the overload weight into the control unit:
Press the menu button until is displayed.
Enter the value of the overload weight, in kilograms (1lb = .45359Kg). Press the
button to select a digit (blinks when selected) and press the button to set the value.
Press the menu button three times. (Note that when the menu button is pressed
once, it displays On to allow you to set the AL C relay to normally open or normally
closed. MCE does not use this relay, so just continue pressing the menu button two
more times to save the value).
8. With the full load of weights in the car, using a digital multimeter, measure the voltage
at terminals 0-10v and Com on the control unit. It should be approximately 8 volts.
Note the exact value.
9. Proceed to Final Calibration with iControl on page 5-57 and Additional iControl Set-
tings and Procedures on page 5-58.
Auto-zero Calibration
The EMCO load weigher has an auto-zero calibration option which can be used if needed. Typi-
cally this option is recommended for 2 to 1 roping or where guide shoes, rather than guide roll-
ers, are used.
2. To view the voltage values from the load weigher using the iView Virtual Oscilloscope: 5
Using iView, connect to the controller
Display the Virtual Oscilloscope (View > Virtual Oscilloscope)
Select Load Weigher (Raw) for Test point 1
Observe the Load Weigher voltage values on the digital display.
3. To verify the linearity of the load weigher, place weights in the car that represent the fol-
lowing and observe the voltage values:
Empty car - about 0.0 volts
25% of overload weight - about 2.5 volts
50% of overload weight - about 5.0 volts
75% of overload - about 7.5 volts
Full load weight - about 8 volts
Overload weight - about 10 volts
5-57
System Options
It is recommended that
the EMCO control unit be
mounted in the controller
cabinet.
For an iControl installation, the output signal from the EMCO control unit must be routed
through the traveler to the to the LW+, LW- and SHLD terminals on the ICE-CTP board located
inside the iLink Cartop box.
5-59
System Options
1. When working with new ropes, the calibration may change slightly as the ropes settle.
After the first 30 days of operation it is recommended to check the empty car weight,
with the car in the middle of the hoistway, using the display on the EMCO Load
Weigher. If the empty car weight has changed (no longer zero), at a minimum the empty
car weight should be re-learned (steps 1 through 5 of the calibration procedure).
2. If the car experiences violent motion, e.g. emergency stop or car / counterweight con-
tacts the buffers, it is recommended to check the empty car weight, with the car in the
middle of the hoistway, using the display on the EMCO Load Weigher. If the empty car
weight has changed (no longer zero), at a minimum the empty car weight should be re-
learned (steps 1 through 5 of the calibration procedure).
Troubleshooting
1. Check for Err codes on the display.
= Bad load cell connection or damaged load cell. Verify that the load cells are
connected to the control unit per the wiring diagram. Inspect the cables for cuts or bro-
ken wires.
= Negative load cell flow. Verify that the load cell connections to the control unit
are per the wiring diagram.
= Positive load cell flow. Load cells are to small for the application and must be
replaced with proper units.
= Polarity error. Verify that the load cell connections to the control unit are per
the wiring diagram. Reprogram the control.
= MB-D display short. Locate the short. Disconnect MB-D display, turn off the
control and reconnect the MB-D display.
= Loss of data in memory. Reprogram the control.
2. Verify that proper voltage is being supplied to the control unit.
3. Check all of the connections to the control unit.
4. Check the fuse. To check fuse: Disconnect power to the control unit. Open the control
unit by removing the five (5) screws that hold the cover. Remove fuse from vertical free
mounting (black) fuse holder next to controller transformer and replace with new fuse if
necessary.
FOR FURTHER ASSISTANCE CONTACT:
MCE Technical Support
Caution
Increasing the weight in the car must always increase clearance between the proximity sen-
sor and the target for proper operation.
LW-SA-1
Sensor
Assembly 40-02-0094
Target Bracket (2 pcs)
DNAI4225 R2
5-61
System Options
Door operator
Floor Plan
(Top View)
Front of Front of
elevator elevator
Distance A
To measure the compression of the rubber pads and not the sagging of the floor attach a
structural piece such as a 1 by 1 angle to the outside edges of the floor.
Figure 5.3 Sensing the Edges of the Floor (compensation for floor sag)
Target bracket
Figure 5.4 Target Bracket and Sensor mounted on Support Assembly and Car frame
FLOOR
Conduit to iLink
Support Assy
2 short pieces of
angle and 1 long
piece of angle
Target
Bracket
(2 pieces)
Proximity sensor
Note
The position sensed is where the support assembly for the target bracket is attached to the floor,
NOT where the sensor is located.
5
5-63
System Options
If the distance between where the target bracket attaches to the floor and the center of the floor
is greater than 20% of distance A (see Figure 8.2), an alternate mounting method may pro-
duce better results.
Example: If distance A is 10'
Then 20% of 10' is 2'
Therefore, if the target bracket attaches to floor more than 2' from the center of the chan-
nel, an alternate method of mounting is suggested (see Figure 8.5).
Figure 5.5 Alternate Mounting Location for Sensor and Target
When mounting inside the channel is too great a percentage (+20%) of Distance A
try mounting sensor outside the channel.
3/8
5-65
System Options
Verify Performance
1. Check the voltages measured between test points LW+ and LW- with the following
loads. This information is used to verify rubber pad resilience for the isolation platform.
Document the data below.
The variation between voltage increase entries should be linear. If voltage increase is more than
25% different from the entry just above it, check the following:
Condition of rubber pads
Voltage variance when weight is in center of car vs. on edge of car (sagging problem)
Adjust iControl Parameters The load weigher is now installed and properly
adjusted. However, the parameter adjustments for the load weigher must be completed. Please
refer to Load Weigher Configuration on page 4-36.
Recommended Maintenance Once a month, check the voltage between LW+ and
LW-. It should be within 0.3V and 1.0VDC when the car is empty. If the voltage is outside
the 0.3 to 1.0VDC range, adjust the target bracket.
Additionally, periodic checks of the voltage increase with varying load conditions will help diag-
nose when the rubber pads begin to lose elasticity.
Installation Method # 2
1. Re-use pre-existing holes or brackets to mount sensor and target.
2. When using supports created for other load weighers, be sure to arrange sensor and tar-
get so that increasing the weight in the car increases the clearance between the proxim-
ity sensor and the target.
3. Always use the target bracket for the target as it will flex slightly and not damage the
sensor during any rebound while doing a buffer test, etc.
4. If the voltage between LW+ and LW- varies depending on where the weight is in the
car, use Installation Method #1 instead.
Installation Method # 3
Mount the sensor on the top of the car. This has the advantage of being the most conve-
nient location, both for installation and for later adjustment. However, there are disadvan-
tages to this approach as well.
The first is that the sensor and target bracket are usually more exposed to accidental
physical damage (critical because the system depends on precise clearances between
the sensor and target).
Second, since the inclination of most installers would be to mount the target directly to
the top of the cab, the extra weight of an elevator adjuster on the cartop often creates
problems during adjustment or if they happen to be riding there temporarily during
normal operation, especially since the top of the cab is not as structurally rigid as the
floor.
Note
If locating the load weigher on the car top is necessary, better results can be obtained by making 5
up a target bracket assembly similar to Figure 8.6 and attaching it to the edges of the elevator
cab, making it less sensitive to cab top flexing. Then, mount the sensor so it is supported by the
crosshead. This can give a very good result, but requires additional expertise on the part of the
installer.
Caution
When mounting the sensor on top of the car, be sure to arrange the sensor and target
bracket so that increasing the weight in the car increases the clearance between the proxim-
ity sensor and the target.
5-67
System Options
Troubleshooting
About Troubleshooting
This section contains general troubleshooting related information and tabled infor-
mation to help you diagnose and correct iControl problems. If you are viewing this
on a computer, click the page number to jump to the appropriate section.
Replacing Circuit Boards and Instructions for removing and replacing circuit boards or
page 6-80
Assemblies the iBox.
COP Board Diagnostics Use to diagnose problems with Serial COP boards. page 6-85
iLink Cartop Diagnostics Use to diagnose problems with iLink. page 6-89
6-1
Troubleshooting
Troubleshooting Tools
The iBox provides status and trouble shooting information:
The status line of the iBox display scrolls messages about system operation. Please refer to
LCD Display and Keypad on page 7-3.
The iBox Event Log captures a FIFO file of the last 50 system events by event number and
name, and provides additional data for each event captured. Press softkey (1) beneath the
Car label, scroll down to View Event Log and press Enter. To view event details, scroll to
the desired event and press Enter. Scroll down to see all of the data, including the event
name. A description and troubleshooting suggestions for each event can be found in iView
online Help (Help > iView Help > Messages Reference) and in the iControl Messages table
in this user guide. Please refer to iControl Messages on page 6-13.
iView provides an extensive toolset to help you diagnose problems, including:
Hoistway: The Hoistway window (Controller > View > Hoistway) shows the current posi-
tion of the car in the hoistway, the calls registered, the car speed and the current operating
mode. Please refer to Hoistway window on page 9-4.
Operational Status tab: The Operational Status tab shows the current speed, position, pat-
tern, and motion of the car. Also, the status of the Safety and Cartop processors, safety cir-
cuits, leveling sensors and door locks is shown. The Faults and Car status text boxes show
general and car operation faults and car status so that you can monitor them easily while
viewing hoistway information and running the car. A description and troubleshooting sug-
gestions for each fault or status message can be found in iView online Help (Help > iView
Help > Messages Reference) and in the iControl Messages table in this user guide. Please
refer to iControl Messages on page 6-13.
Event Log: The Event Log tab (View > Diagnostics > Event Log) monitors and records sys-
tem events. You can easily save event log information to a file on your iView PC for archi-
val and future reference. A description and troubleshooting suggestions for each event can
be found in iView online Help (Help > iView Help > Messages Reference) and in the iCon-
trol Messages table in this user guide. Please refer to iControl Messages on page 6-13.
Fault Bypass: The Fault Bypass tab (View > Diagnostics > Fault Bypass) allows you to
bypass over 50 system faults. The Fault Bypass switch on the iBox must be ON and each
fault bypass times out after fifteen minutes to prevent the possibility of unintended, long
term bypassing of a critical faults. To bypass faults, the car must be on Machine Room
Inspection or Test Operation. Please refer to Diagnostics - Fault Bypass on page 9-18.
Diagnostic Flags: The Diagnostic Flags tab (View > Diagnostics > Diagnostic Flags) allows
you to view system diagnostic flags and car statuses in four classifications (Operation,
Motion, Safety, Drive). Please refer to Diagnostics - Diagnostic Flags on page 9-12.
Terminal Switches Status: The Terminal Switches Status tab (View > Diagnostics > Termi-
nal Switches Status) shows information about the speed and position of the car when each
Normal and Emergency Terminal Switch opened. Please refer to Diagnostics - Terminal
Switches Status on page 9-20.
Diagnostic Outputs: Diagnostic Outputs (View > Diagnostics > Diagnostic Outputs win-
dow) allows you to choose and simultaneously monitor up to 16 system outputs on screen.
Please refer to Diagnostics - Diagnostic Outputs on page 9-14.
Virtual Oscilloscope: The oscilloscope (View > Diagnostics > Virtual Oscilloscope) allows
you to select and view two system outputs simultaneously on a virtual oscilloscope.
Please refer to Diagnostics - Virtual Oscilloscope on page 9-22.
The safety string bypass location for iControl is accessed through ports on the front cover of the
iBox. The ports are sized so that a jumper wire (16AWG minimum) with insulated clips on each
end can be used to short the SB and 3 terminals to bypass the safety string.
Danger
You are jumpering 110VDC. Place the jumper with caution, being certain that you are insu-
lated from the possibility of electrical shock.
The safety bypass circuitry is intelligent. The jumper will have no effect if it is put in place with
the safety string intact (other than to generate a time out after 15 minutes pass). The jumper will
bypass the string and allow the car to be moved only if it is placed after the safety string has
opened. If the jumper is in place when the string opens, you must remove the
jumper, then replace it before it will bypass the string.
The jumper is monitored by a timer. If the jumper is in place for longer than 15 minutes, the
timer will expire, drop the brake and motor contactors and generate a Safety Bypass Jumper
Time Out. To clear the fault and restart the car, you must remove the bypass jumper. If more
time is needed, re-install the jumper and the fifteen-minute timer will restart.
The table below specifies what is and is not bypassed by the jumper.
6-3
Troubleshooting
Message Tables
Almost all troubleshooting begins with examining system messages. System outputs are dis-
played alternating with other messages on the iBox LCD. Status, Fault, and Event messages are
displayed by iView. (iBox maintains an Event Log as well.) This section contains two tables.
Table 6.2 provides a cross-reference from iBox ID numbers to the associated iControl message
name. Table 6.3 lists system messages in alphabetical order and describes the cause and recom-
mended troubleshooting procedures if appropriate.
Table 6.2 Cross Reference: iBox Event Log ID Numbers to iControl Messages
ID # iControl Message (iBox Event Log and iView Controller Event Log)
1 Drive On Fault (was Drive Ready On Fault)
2 Brake Enable Fault
4 Insufficient Brake Feedback Fault
5 Brake Voltage Not On Fault
6 Excessive Brake Feedback Fault
7 Brake Pick Fault
8 Brake Module Over Temperature Fault
9 Heat Sensor Fault 2
10 Heat Sensor Fault 3
11 Heat Sensor Fault 4
12 Power Supply Fault 1
13 Power Supply Fault 2
14 Power Supply Fault 3
15 Power Supply Fault 4
16 Drive At-Speed Fault
17 Drive Fault
18 Drive Ready Fault
19 Front Door Close Time-out
20 Front Door Close Fault
21 Front Door Open Time-out
22 Front Door Open Fault
23 Rear Door Close Time-out
24 Rear Door Close Fault
25 Rear Door Open Time-out
26 Rear Door Open Fault
27 Earthquake Operation (Seismic Switch)
28 Earthquake Operation (Counterweight)
29 Earthquake Run
30 Earthquake Operation Activated
31 Earthquake Operation Deactivated
32 Earthquake Emergency Stop
33 Fire Service Recall Main
34 Fire Service Recall Alternate
35 Fire Service In-car Activated
36 Elevator Recall Operation (Switch 1)
37 Elevator Recall Operation (Switch 2)
38 Elevator Recall Operation (Switch 3)
39 Elevator Recall Operation (Switch 4)
40 Elevator Recall Operation (Switch 5)
41 Elevator Recall Operation (Switch 6)
42 Emergency Power Recall
43 Emergency Power Shutdown
ID # iControl Message (iBox Event Log and iView Controller Event Log)
44 Emergency Power Run
45 Front Door Contact Fault
46 Rear Door Contact Fault
47 Front Photo Eye Failure
48 Front Safe Edge Failure
49 Rear Photo Eye Failure
50 Rear Safe Edge Failure
51 Cartop Inspection Operation
53 Hoistway Access Operation
54 Machine Room Inspection Operation
55 Test Mode
56 Capture Mode
57 Independent Service
60 Attendant Service
61 Passenger Operation
62 Up Normal Terminal Switch 1 Position Fault
63 Up Normal Terminal Switch 2 Position Fault
64 Up Normal Terminal Switch 3 Position Fault
65 Up Normal Terminal Switch 4 Position Fault
66 Up Normal Terminal Switch 5 Position Fault
67 Up Emergency Terminal Switch Position Fault
68 Down Normal Terminal Switch 1 Position Fault
69 Down Normal Terminal Switch 2 Position Fault
70 Down Normal Terminal Switch 3 Position Fault
71 Down Normal Terminal Switch 4 Position Fault
72 Down Normal Terminal Switch 5 Position Fault
73 Down Emergency Terminal Switch Position Fault
74 Position Quadrature Fault
75 Position Speed Threshold Fault
76 Position Speed Deviation Fault
77 Motion Start Fault
78 User code accessing an invalid logical indicator (internal event)
79 Car shut down due to emergency power operation with no supervisor (Activated)
80 Car shut down due to emergency power operation with no supervisor (Deactivated)
81 Car delayed with doors open
82 Car delayed with doors closed 6
83 Car out of service with doors open
84 Car out of service with doors closed
85 Earthquake board power supply ON
86 Earthquake board power supply OFF
87 Earthquake reset button stuck ON
88 Earthquake reset button OK
89 Fire Service In-car Hold Operation
90 Fire Service In-car Recall Operation
91 Load learn process activated
92 Load learn process deactivated
93 Car Heavy Load Activated - Hall Calls Bypassed
94 Car Over Load Activated
95 Fire Service Recall Deactivated
96 Fire Service In-car Deactivated
97 Emergency Power Activated
98 Emergency Power Deactivated
6-5
Troubleshooting
ID # iControl Message (iBox Event Log and iView Controller Event Log)
100 Car Dispatch Load
102 Car Heavy Load - Deactivated
104 Car Over Load Deactivated
105 Photo Eye Antinuisance
106 Light Load Antinuisance
107 Nudging Operation
108 Front Photo Eye Bypassed
109 Rear Photo Eye Bypassed
110 Front Safe Edge Bypassed
111 Rear Safe Edge Bypassed
118 Inspection Overspeed Fault
119 Tach Error Fault
120 Drive Enable Feedback Fault
121 Safety A Inspection Overspeed Fault
122 IO Map Compare Fault
123 IO Map Toggle Compare Fault
124 Fault Bypass Switch Timed Out
125 Safety Bypass Jumper Timed Out
126 Learn Switch Timed Out Fault
127 Safety A SIB Device Fault
128 Safety B SIB Device Fault
129 QPRAM Device Error
130 EEPROM Device Error
131 Front Door Open Button Bypassed
132 Rear Door Open Button Bypassed
135 Door Lock Clipped Greater than 200fpm
136 Safety String Open
137 Motion stopped due to IO toggle test
138 Safety Configuration Mismatch
139 Safety Configuration Learn Fault
140 IO Map Compare Alert
141 Safety A Contract Overspeed Fault
142 Safety A Inspection Leveling Overspeed Fault
143 Safety Inventory Checksum Fault
144 Safety Configuration Checksum Fault
145 Limit Switches Checksum Fault
146 Safety Configuration Inventory Cross Check Fault
147 Safety Inventory Learn Fault
148 Limit Switches Learn Fault
149 Dual Channel QUAD Fault
150 Single Channel QUAD Fault
151 Loss of Position or Speed Indicators
152 Safety Inventory Comparison Fault
153 Safety Inventory Creation Fault
154 Position Quadrature Reversed Fault
155 Down Normal Terminal Switch 1 Level 1 Speed Fault
156 Down Normal Terminal Switch 2 Level 1 Speed Fault
157 Down Normal Terminal Switch 3 Level 1 Speed Fault
158 Down Normal Terminal Switch 4 Level 1 Speed Fault
159 Down Normal Terminal Switch 5 Level 1 Speed Fault
160 Down Normal Terminal Switch 1 Level 2 Speed Fault
161 Down Normal Terminal Switch 2 Level 2 Speed Fault
ID # iControl Message (iBox Event Log and iView Controller Event Log)
162 Down Normal Terminal Switch 3 Level 2 Speed Fault
163 Down Normal Terminal Switch 4 Level 2 Speed Fault
164 Down Normal Terminal Switch 5 Level 2 Speed Fault
165 Up Normal Terminal Switch 1 Level 1 Speed Fault
166 Up Normal Terminal Switch 2 Level 1 Speed Fault
167 Up Normal Terminal Switch 3 Level 1 Speed Fault
168 Up Normal Terminal Switch 4 Level 1 Speed Fault
169 Up Normal Terminal Switch 5 Level 1 Speed Fault
170 Up Normal Terminal Switch 1 Level 2 Speed Fault
171 Up Normal Terminal Switch 2 Level 2 Speed Fault
172 Up Normal Terminal Switch 3 Level 2 Speed Fault
173 Up Normal Terminal Switch 4 Level 2 Speed Fault
174 Up Normal Terminal Switch 5 Level 2 Speed Fault
175 Safety A DETS Level 2 Speed Fault
176 Safety A UETS Level 2 Speed Fault
177 Excessive Faults Shutdown
178 Safety A Unintended Motion Fault
179 Ascending Car Overspeed Fault
180 Position Synchronization Required at Terminal
181 Position Synchronized at Terminal
182 Position Synchronization Required at Floor
183 Position Synchronized at Floor
184 Cartop Communication Fault
185 Cartop Inspection Unintended Motion Fault
186 Cartop Automatic Unintended Motion Fault
187 Motor Limit Timed Out
188 Safety B Fault Bypass Switch Timed Out
189 Safety B Safety Bypass Jumper Timed Out
190 IO Map Compare Long Term Alert
191 IO Map Compare Long Term Fault
192 Position Location Error Fault
193 Position Cartop Offset Fault
194 Motor Contactor Driver Proofing Fault
195 Motor Contactor Proofing Fault
196 Brake Contactor Driver Proofing Fault
197 Brake Contactor Proofing Fault 6
198 Safety B UETS Level 2 Speed Fault
199 Safety B DETS Level 2 Speed Fault
200 Safety B Inspection Overspeed Fault
201 Safety B Inspection Leveling Overspeed Fault
202 Safety B Contract Overspeed Fault
203 Excessive Relevels Fault
204 Excessive Restarts Fault
205 Cartop Emergency Stop
206 Cartop Power Loss
207 Up Direction Limit Open
208 Down Direction Limit Open
209 Floor Location Fault
210 Floor Sensor Fault
211 Power Transfer Input Activated
212 Power Transfer Input Deactivated
213 Invalid Front Door Position
6-7
Troubleshooting
ID # iControl Message (iBox Event Log and iView Controller Event Log)
214 Invalid Rear Door Position
215 Earthquake Reduce Speed
216 Cartop Inspection Operation
217 Car Panel Inspection Operation
218 Hoistway Access Inspection Operation
219 Machine Room Inspection Operation
220 Inspection Operation
221 Construction Cartop Inspection Operation
222 Construction Car Panel Inspection Operation
223 Construction Hoistway Access Inspection Operation
224 Construction Machine Room Inspection Operation
225 Construction Inspection Operation
226 Door Lock Clipped Less than 200fpm
227 Invalid Input
228 Emergency Medical Service Recall Activated (Switch 1)
229 Emergency Medical Service In-Car Activated (Switch 1)
230 Emergency Medical Service Deactivated
231 Emergency Medical Service Bypassed
232 SCR Power Supply Fault
233 SCR AC Phase Fault
234 SCR Contactor Fuse Fault
235 SCR Phase Lock Loop Fault
236 SCR Phase Lock Loop Warning
237 SCR Dynamic Brake Fault
238 SCR Instantaneous Over Current
239 SCR Armature Voltage On
240 SCR High Temperature Fault
241 SCR Loop Over Current
243 SCR Insufficient Armature Current
244 SCR Excessive Armature Current
245 SCR Excessive Current Command, Drive Enabled
246 SCR Excessive Current Command, Drive Disabled
247 Insufficient Motor Field Forcing Feedback Fault
248 Insufficient Motor Field Feedback Fault
249 Swing Operation Activated
250 Swing Operation Deactivated
251 Field Module Over Temperature Fault
252 Speed Limit, MF Forcing
253 Tach Failure
254 Sabbath Operation Activated
255 Sabbath Operation Deactivated
256 Emergency Brake Tripped
257 Landing System Sensor Fault
258 Emergency Brake Leg 1 Short Fault
259 Emergency Brake Leg 2 Short Fault
260 Alternate Speed Profile 1 Activated
261 Alternate Speed Profile 1 Deactivated
262 Alternate Speed Profile 2 Activated
263 Alternate Speed Profile 2 Deactivated
264 Motor Field Forcing Timed Out
265 iView Logged On
266 iView Logged Off
ID # iControl Message (iBox Event Log and iView Controller Event Log)
267 iView Timed Out
268 iView Lost Connection
269 Balanced Mode
270 Lobby Peak Mode
271 Demand Up Peak Mode
272 Demand Down Peak Mode
273 CFSS Mode 1 Recall Activated
274 CFSS Mode 1 at Floor Activated
275 CFSS Mode 1 In-car Activated
276 CFSS Mode 2 Recall Activated
277 CFSS Mode 2 at Floor Activated
278 CFSS Mode 2 In-car Activated
279 Emergency Alarm Acknowledged
280 Emergency Alarm Activated (Safety opened)
281 Emergency Alarm Activated (Car delayed with doors closed)
282 Emergency Alarm Activated (Alarm button)
283 Emergency Alarm Activated (In-car stop switch)
284 Emergency Brake OK open
285 Cartop Exit Open
286 Governor open
287 Safety H String Open
288 Safety C String Open
289 Machine Room Stop Switch Open
290 Car Stop Switch Open
291 Controller Main Computer Startup
292 Floor Synchronization Fault
293 Terminal Synchronization Fault
294 Position Synchronization Fault
296 Up Emergency Terminal Switch Shutdown
297 Down Emergency Terminal Switch Shutdown
298 Power Up Position Synchronization Required at Terminal
299 Learn U/DNT1-5 and U/DETS Speeds
300 Learn U/DNT1-5 and U/DETS Positions
301 Excessive Motor Field Feedback Fault
302 Brake Output Circuit Failure
303 Group Communication Lost 6
304 Group Communication Established
305 Flood Operation Activated
306 Flood Operation Deactivated
307 Emergency Brake UIM Reset Button Stuck
308 Exercise Operation Activated
309 Exercise Operation Deactivated
310 SCR Low Line Fault
311 SCR Low Line Caution Activated
312 SCR Low Line Caution Deactivated
313 SCR Low Line Test Fault
314 Excessive Restarts Warning
315 Governor Speed Reduction Switch Fault
316 Software Recall Switch Activated
317 SCR Drive Ready Fault
318 Retiring Cam Door Lock Fault Activated
319 Retiring Cam Door Lock Fault Deactivated
6-9
Troubleshooting
ID # iControl Message (iBox Event Log and iView Controller Event Log)
320 Retiring Cam Protection Fault Activated
321 Retiring Cam Protection Fault Deactivated
322 Watchdog Ordered Control Stop Before Reset
323 Front Hall Door Open Button Bypassed
324 Rear Hall Door Open Button Bypassed
327 Bus 2 Fuse Open
328 Bus 2D Fuse Open
329 Bus 2MC Fuse Open
330 Bus 2PI Fuse Open
331 Bus 3 Fuse Open
332 Bus 3HA Fuse Open
333 Watchdog Ordered Emergency Stop Before Reset
334 Local Dispatcher Activated
335 Local Dispatcher Deactivated
336 Drive Start Failure
337 Emergency Medical Service Recall Activated (Switch 2)
338 Emergency Medical Service In-Car Activated (Switch 2)
339 Pre-start Door Lock Fault
340 Emergency Alarm Deactivated without Acknowledgement
341 Cartop Exit no Counterweight Configuration Error
342 Front Door Close Fault Recovery Failure
343 Rear Door Close Fault Recovery Failure
344 Sheave Brake Pick Fault
345 Sheave Brake Drop Fault
346 Serial COP Buss 1 Comm Fault
347 Serial COP Buss 2 Comm Fault
348 Serial COP Buss 3 Comm Fault
349 Serial COP Buss 4 Comm Fault
350 Serial COP Bus 1 Inventory Fault
351 Serial COP Bus 2 Inventory Fault
352 Serial COP Bus 3 Inventory Fault
353 Serial COP Bus 4 Inventory Fault
354 User Defined Event 1 On
355 User Defined Event 1 Off
356 User Defined Event 2 On
357 User Defined Event 2 Off
358 User Defined Event 3 On
359 User Defined Event 3 Off
360 User Defined Event 4 On
361 User Defined Event 4 Off
362 User Defined Event 5 On
363 User Defined Event 5 Off
364 User Defined Event 6 On
365 User Defined Event 6 Off
366 User Defined Event 7 On
367 User Defined Event 7 Off
368 User Defined Event 8 On
369 User Defined Event 8 Off
370 User Defined Event 9 On
371 User Defined Event 9 Off
372 User Defined Event 10 On
373 User Defined Event 10 Off
ID # iControl Message (iBox Event Log and iView Controller Event Log)
374 Drive Communication Fault
375 Drive Communication Warning
376 Motor Limit Protection Timer Elapsed
377 Shuttle Service Activated
378 Shuttle Service Deactivated
379 Event Log Cleared
380 Front Auxiliary Door Open Button Bypassed
381 Rear Auxiliary Door Open Button Bypassed
382 Backup Power Unit Failure Activated
383 Backup Power Unit Failure Deactivated
384 Backup Power Direction Reversal
385 Backup Power Recall ON
386 Backup Power Recall OFF
387 Machine Room Heat Detectors Activated
388 Machine Room Heat Detectors Deactivated
389 Hoistway Heat Detectors Activated
390 Hoistway Heat Detectors Deactivated
391 Floor Heat Detectors Activated
392 Floor Heat Detectors Deactivated
393 Heat Detectors Recall Activated
394 Heat Detectors Recall Deactivated
395 Heat Detectors Recall Complete
396 Brake Drop Fault
397 Cartop Communication Established
398 Hall Call Service Disabled
399 Hall Call Service Enabled
400 Nudging Front
401 Nudging Rear
402 Emergency Dispatch On
403 Emergency Dispatch Off
404 Safety B Unintended Motion Fault
405 SPA Spare Event 1
406 SPA Spare Event 2
407 SPA Spare Event 3
408 SPA Spare Event 4
409 SPA Spare Event 5 6
410 SPA Spare Event 6
411 SPA Spare Event 7
412 SPA Spare Event 8
413 LCD Fault
414 Battery Voltage Low - IMP
415 Emergency Brake OK open Off
416 Safety H String Open Off
417 Safety C String Open Off
418 Cartop Exit Open Off
419 Brake Pick Switch Fault Off
420 IO Map Compare Fault Off
421 IO map Toggle Compare Fault Off
422 Safety A SIB Device Fault Off
423 Safety B SIB Device Fault Off
424 Invalid Configuration Input Off
425 Invalid Configuration Input DLMS
6-11
Troubleshooting
ID # iControl Message (iBox Event Log and iView Controller Event Log)
426 Invalid Configuration Input DLAT
427 Invalid Configuration Input DLAB
428 Invalid Configuration Input DCMS
429 Invalid Configuration Input DCAT
430 Invalid Configuration Input DCAB
431 Invalid Configuration Input DPM
432 Invalid Configuration Input CTEX
433 Invalid Configuration Input DLMSR
434 Invalid Configuration Input DCMSR
435 Invalid Configuration Input DPMR
436 Safety String Closed
437 IMP Switch Fault - Emergency Stop
438 IMP Switch Fault - Fault Bypass
439 IMP Switch Fault - Inspection DOWN
440 IMP Switch Fault - Inspection UP
441 IMP Switch Fault - Inspection Enable
442 IMP Switch Fault - Inspection
443 IMP Switch Fault - Learn
444 IMP Switch Fault - Test
445 IMP Switch Fault - Write Enable
446 IMP Switch Fault - Hoistway Door Bypass
447 IMP Switch Fault - Car Door Bypass
448 IMP Switch Fault - None
451 Excessive Faults Warning
452 Stuck Cartop Inspection Input
453 Cartop Inspection Inputs OK
454 Stuck Car Panel Inspection Input
455 Car Panel Inspection Inputs OK
456 Cartop Inspection Disabled
457 Cartop Inspection Enabled
458 Hoistway Access Disabled
459 Hoistway Access Enabled
460 Car Panel Inspection Disabled
461 Car Panel Inspection Enabled
462 Machine Room Inspection Disabled
463 Machine Room Inspection Enabled
464 Stuck Inspection Input Fault
465 DBD Mode Activated (not used)
466 ETA Mode Activated (not used)
467 Hall Call Bypass Input ON
468 Hall Call Bypass Input OFF
469 Capture Input ON
470 Capture Input OFF
475 Emergency Stop Input Activated
476 Emergency Stop Input Deactivated
479 Safety B Fault Activated
480 Safety B Fault Deactivated
iControl Messages
Table 6.3 iControl Messages
iControl Messages
Alternate Floor Smoke Sensor Recall, ALTERNATE FLOOR SMOKE
Description: Recall to the main fire floor due to active or latched smoke detector input(s) from floors other
than the main recall floor.
Car Reaction: Car proceeds to the user-defined main fire recall floor. Once at the recall floor, door operation
is according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. If in error, inspect the sensor input and connections.
2. Related Inputs:
Smoke and fire sensors as indicated in job prints.
Alternate Speed Profile 1 Activated, Alternate Speed Profile 1, ALT SPEED PROFILE 1
Description: Indicates that the Alternate Speed Profile has been enabled via a keyed or switched input. When
so configured, Alternate Speed Profiles 1 and 2 use Alternate 1 and Alternate 2 performance patterns respec-
tively. (Pattern Configuration/Alternate n.)
Car Reaction: Car uses assigned pattern (Alternate 1 or 2).
Alternate Speed Profile 1 Deactivated
Alternate Speed Profile 2 Activated. Alternate Speed Profile 2, ALT SPEED PROFILE 2. See Alternate
Speed Profile 1 Activated.
Alternate Speed Profile 2 Deactivated
Ascending Car Overspeed Fault, ASCND CAR OVR SPD FLT
Description: Ascending Car Overspeed Fault. This fault is tripped if the elevator is traveling in the up direc-
tion, the Governor contact opens, and the Rope Gripper option is selected on the Safety Configuration
screen. You will also see a Governor Open fault.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. The rope brake
drops if installed. If you do not have a RG (Rope Gripper) or EB (Emergency Brake) board in your controller,
this fault will not appear.
Troubleshooting:
1. Check the iView event log for related events.
2. Identify and correct any operational problems. Check for proper governor operation.
3. Resetting the Governor switch will automatically clear this fault.
Attendant Service, Attendant Svc
Description: Indicates that the elevator is operating under Attendant Service mode of operation. Generally 6
initiated via an input (switch or button) at the car operating panel.
Car Reaction: Car operates under attendant mode.
Troubleshooting:
1. Related input: Attendant service as indicated on the job prints.
Automatic Stop
Description: The Automatic Stop feature has been enabled.
Car Reaction: The car will stop at a user-defined floor whenever it passes that floor in a user-defined direc-
tion and the doors will open and remain open for a user-defined time.
Troubleshooting:
1. Check the parameters on the Configuration > Car Operation > Auto Stop tab for proper configuration.
6-13
Troubleshooting
iControl Messages
Backup Power Direction Reversal
Description: The Backup power recall reverse direction input has been activated (signal from the TAPS Trac-
tion Auxiliary Power Supply).
Car Reaction: The car direction of travel is reversed unless the car is on Earthquake operation and the CW1/
CW2 inputs (Counterweight movement sensor) are active and reversal would move the car in the direction
towards the counter weight.
Backup Power Recall OFF
Description: The Backup power recall input has been deactivated.
Backup Power Recall ON, BACKUP POWER RECALL
Description: The Backup power recall input has been activated (signal from the TAPS Traction Auxiliary
Power Supply).
Car Reaction: If the car is not currently at a floor, it will move to a floor and cycle the doors. If no load
weigher is used, the car will move to the closest floor. If a load weigher is used, direction is dependent on the
car load and the Counterweight percentage parameter. If load weight is greater than Counterweight percent-
age, car moves down and vice versa.
Backup Power Unit Failure Activated, Backup power unit failure, BACKUP POWER FAILURE
Description: The Backup power unit failure input is low.
Car Reaction: None. The event is displayed and logged.
Troubleshooting:
1. Check the UPS unit for faults.
2. Check the connection to the Backup power unit failure input.
3. It may be necessary to replace the battery
Backup Power Unit Failure Deactivated
Description: The Backup power unit failure input has changed back to its normally high state.
Balanced Mode
Description: Passenger operation. Up and Down traffic treated equally. Assigned by group controller.
Battery Voltage Low-IMP, BATTERY VLTG LOW-IMP
Description: The voltage on Battery B1 on the IMP board has dropped below 2.22 VDC and the battery must
be replaced. Otherwise the BBRAM will be unable to retain the data stored during a power loss or shut down.
Blocking New Remote Connections, BLOCKING REMOTE UIS
Description: When a car switches from Local to Local Dispatcher, many parameters and connections to other
cars must be stabilized. During this time the new Local Dispatcher will not accept any new remote connec-
tions for 30 seconds.
Car Reaction: iView will remain connected if it was already connected. Any new iMonitor, iReport, Liftnet,
BMS, etc. connections will be denied for 30 seconds while the car is syncing up and stabilizing data.
Troubleshooting:
1. If this message is persistent for more than 30 seconds or if it seems to come and go for extended periods
of time, the car may be confused as to if it should be the Local Dispatcher. Check the Alternate Dis-
patcher settings (System Configuration > Building tab), and Car ID (Controller > General > General tab)
parameters. This has been an issue when upgrading a car designated as Alternate Dispatcher with a Car
ID not = 1. A reboot was necessary to fix it, but is also necessary after an upgrade anyway.
Brake Contactor Driver Proofing Fault, BRAKE CNT DRV PRF FLT
Description: Fault signal for brake contactor driver proofing.
Car Reaction: None
Troubleshooting:
1. Verify brake contactor driver proofing circuits.
iControl Messages
Brake Contactor Proofing Fault, BRAKE CONT PRF FAULT
Description: Fault signal for brake contactor proofing.
Car Reaction: None
Troubleshooting:
1. Verify brake contactor proofing circuits.
Brake Drop Fault, BRAKE DROP FAULT
Description: Indicates that the brake contact input (SP2D or Brake Switch) was not in the state required by
the Brake is picked when SP2D or Brake Switch terminal is high (low) parameter, indicating that the brake
was not fully dropped for more than one second after the car has stopped. This fault may be bypassed on the
Controller > Diagnostics > Fault Bypass tab by setting Brake Switch.
Car Reaction: Car is removed from service.
Troubleshooting:
1. On the Controller > Configuration > Brake > Control tab, check Brake is picked when SP2D or Brake
Switch terminal is high (low) to determine the proper state of terminal SP2D or Brake Switch when the
brake is dropped (see Configuration - Brake Tab on page 9-25).
2. Verify proper operation of the brake and brake switch (open or closed, see step 1) when the brake is fully
dropped.
3. With the brake dropped, verify the state of input SP2D or Brake Switch (low or high, see step 1). Please
refer to Installing Brake Monitoring on page 3-20.
4. Use the iBox Fault reset button to clear the fault.
Brake Enable Fault
Description: When the brake module is enabled, a feedback signal is generated for the iBox. If the feedback
signal is not detected, this fault is generated.
Car Reaction: Emergency stop: Motor and brake contactors immediately dropped.
Troubleshooting:
1. Check the Brake Voltage Feedback test point on the iView Oscilloscope screen.
2. Check the iField Brake Module connections.
3. Check the brake and brake connections.
4. If brake feedback voltage is actually present, the iBox Safety board may be defective.
Brake Module Over Temperature Fault, BRAKE OVER TEMP FAULT
Description: Temperature sensor in the brake module detected an overheat condition.
Car Reaction: If the car is running, it will continue to answer current call. After the car is stopped at a floor,
the car will not be allowed to run until the overheat condition clears.
6
Troubleshooting:
1. Check for excessive machine room ambient temperature. (Should not exceed 104 degrees F or 40C.)
2. Verify that air enters through the bottom of the power box and is only expelled via the fan at the top of
the power box.
3. Check the running temperature inside the power box (should not exceed 105 degrees F).
4. Check for insufficient air circulation through the power box.
5. Check for improperly picking brake.
6. Check for faulty brake module.
7. Check for faulty connection between brake module and iBox.
6-15
Troubleshooting
iControl Messages
Brake Output Circuit Failure, BRAKE OUTPUT FAILURE
Description: The flywheel brake IGBT has failed or the fuse has opened.
Car Reaction: Normal stop.
Troubleshooting:
1. Verify proper operation of the brake module while running on machine room inspection:
Does the brake pick voltage match the setting on the Configuration > Brake tab?
Does the brake hold voltage match the setting on the Configuration > Brake tab?
2. Verify proper operation of the brake module while performing the Brake Calibration:
Does the voltage max out and then slowly ramp down to about 10% of maximum supply voltage?
Does the current max out and then slowly ramp down to about 10% of maximum supply current?
If the brake module is constantly outputting maximum voltage and current based on the testing in steps 1
and 2, the main IGBT on the module is most likely damaged. The module must be replaced.
CAUTION: An open or damaged RB resistor can cause the IGBT to fail. Check the resistor by removing the
center tap and measuring the value of the entire resistor. It is strongly recommended to do this before
installing another brake module.
Brake Pick Fault, BRAKE PICK FAULT
Description: Indicates that the brake contact input (SP2D or Brake Switch) was not in the state required by
the Brake is picked when SP2D or Brake Switch terminal is high (low) parameter, indicating that the brake
was not fully picked during one entire run or was late going low (or high) indicating a slow picking brake dur-
ing three consecutive runs. This fault may be bypassed on the Controller > Diagnostics > Fault Bypass tab
by setting Brake Switch.
Car Reaction: Car completes its nearest run and is removed from service.
Troubleshooting:
1. On the Controller > Configuration > Brake > Control tab, check Brake is picked when SP2D or Brake
Switch terminal is high (low) to determine the proper state of terminal SP2D or Brake Switch when the
brake is picked (see Configuration - Brake Tab on page 9-25).
2. Verify proper operation of the brake and brake pick switch (open or closed, see step 1) when the brake is
fully picked.
3. With the brake picked, verify the state of input SP2D or Brake Switch (low or high, see step 1). Please
refer to Installing Brake Monitoring on page 3-20.
4. Use the iBox Fault reset button to clear the fault.
Brake Pick Fault Off (See: Brake Pick Fault)
Brake Voltage Not On Fault, BRAKE V NOT ON FAULT
Description: After brake contactors are picked and controller did not receive more than 30% of the picking
voltage after 1 second, this fault is generated. May be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. Fault will self
clear and car will attempt to run again.
Troubleshooting:
1. Verify Brake AC input voltage at FB1 and FB2.
2. Verify FB1 and FB2 fuses are good.
3. Verify J2 connector on right side of iBox is seated properly.
4. Verify brake output voltage with multimeter on terminals B1 and B2.
5. Recalibrate brake module if applicable.
Bus 2 Fuse Open, BUS 2 FUSE OPEN
Description: The bus 2 fuse is open.
Car Reaction: Emergency stop. Cancel demand and open doors. No further movement is allowed.
Troubleshooting: Check bus 2 fuse located at bottom of iBox.
Bus 2D Fuse Open, BUS 2D FUSE OPEN
Description: The bus 2D fuse is open.
Car Reaction: Emergency stop. Cancel demand and open doors. No further movement is allowed.
iControl Messages
Troubleshooting: Check bus 2D fuse located at bottom of iBox.
Bus 2MC Fuse Open, BUS 2MC FUSE OPEN
Description: The bus 2MC fuse is open.
Car Reaction: Emergency stop. Cancel demand and open doors. No further movement is allowed.
Troubleshooting: Check bus 2MC fuse located at bottom of iBox.
Bus 2PI Fuse Open, BUS 2PI FUSE OPEN
Description: The bus 2PI fuse is open.
Car Reaction: None. The PI signals will not be active.
Troubleshooting: Check bus 2PI fuse located at bottom of iBox.
Bus 3 Fuse Open, BUS 3 FUSE OPEN
Description: The bus 3 fuse is open.
Car Reaction: Emergency stop. Cancel demand and open doors. No further movement is allowed.
Troubleshooting: Check bus 3 fuse located at bottom of iBox.
Bus 3HA Fuse Open, BUS 3HA FUSE OPEN
Description: The bus 3HA fuse is open.
Car Reaction: None. No further movement is allowed when on Access operation.
Troubleshooting: Check bus 3HA fuse located at bottom of iBox.
Capture Input OFF (see Capture Input ON)
Capture Input ON
Description: Discrete input used to capture the car. This input will activate Capture mode, similar to the iBox
Capture switch (see also: Capture Mode).
Car Reaction: The car takes itself out of hall call service. Hall calls are canceled if no other car is available for
hall call service. The car is also not eligible for parking.
Troubleshooting: Check the related discrete inputs.
Capture Mode, Capture
Description: Indicates the Capture mode switch on the iBox has been placed in the ON position.
Car Reaction: Car enters capture mode, removing itself from group operation (hall calls assigned to it will be
reassigned to another elevator if possible). The car answers registered car calls but does not respond to hall
call demand. Intended to allow maintenance personnel access to the car.
Car delayed with doors closed, CAR DEL DOORS CLOSED
6
Description: Indicates that a car, with doors fully closed, has been delayed in reaching an assigned destina-
tion.
Car Reaction: Assigned hall calls will be reassigned to other available cars.
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
Car delayed with doors closing, CAR DEL DOORS CLOSING
Description: Indicates that a car, with doors closing, has been delayed in reaching an assigned destination.
Car Reaction: Assigned hall calls will be reassigned to other available cars.
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
6-17
Troubleshooting
iControl Messages
Car delayed with doors open, CAR DEL DOORS OPEN
Description: Indicates that a car, with doors fully open, has been delayed in reaching an assigned destina-
tion.
Car Reaction: Assigned hall calls will be reassigned to other available cars.
Troubleshooting:
1. Determine what is keeping the doors open or inhibiting them from closing.
2. Check the event log for any faults that may have prevented the doors from closing.
Car delayed with doors opening, CAR DEL DOORS OPENING
Description: Indicates that a car, with doors opening, has been delayed in reaching an assigned destination.
Car Reaction: Assigned hall calls will be reassigned to other available cars.
Troubleshooting:
1. Determine what is inhibiting the doors from opening.
2. Check the event log for any faults that may have prevented the doors from opening.
Car delayed with doors stalled, CAR DEL DOORS STALLED
Description: Indicates that a car, with doors stalled, has been delayed in reaching an assigned destination.
Car Reaction: Assigned hall calls will be reassigned to other available cars.
Troubleshooting:
1. Determine what is inhibiting the doors from closing.
2. Check the event log for any faults that may have prevented the doors from closing.
Car delayed with unknown door position, CAR DEL DOORS UNKNOWN
Description: Indicates that a car, with unknown door position, has been delayed in reaching an assigned des-
tination.
Car Reaction: Assigned hall calls will be reassigned to other available cars.
Troubleshooting:
1. Determine what is causing the doors to be reported in an invalid condition.
Car Dispatch Load. Not currently used.
Car Door Bypass, CAR DOOR BYPASS
Description: The Car Door Bypass switch on the iBox is in the Bypass position. (View-only on iView Safety
screen, enabled/disabled by MCE according to safety jurisdiction.)
Car Reaction: The car is placed in Inspection mode. To move the car, you must place it in either cartop or car
panel inspection mode. No other modes of operation are allowed.
Car Heavy Load Activated - Hall Calls Bypassed, CAR HEAVY LOAD
Description: The load in the car has exceeded the Heavy Load Threshold setting.
Car Reaction: Hall calls are bypassed until the heavy load condition is cleared. Hall calls assigned to this car
are reassigned to other cars if possible.
Troubleshooting: (If displayed in error)
1. Verify the programmed Heavy Load Threshold value and adjust if needed (Load Weigher Configuration
screen).
2. Evaluate whether or not the load in the car exceeds the Heavy Load Threshold. Calibrate the load
weigher if needed.
3. For discrete input load weighers, check the Heavy Load Input shown on the job prints.
Car Heavy Load - Deactivated
iControl Messages
Car out of service with doors closed, CAR OS DOORS CLOSED
Description: A delayed car with closed doors has remained so for an excessive period of time (as determined
by a user-programmed timer parameter, Car Operation Screen/Passenger tab.
Car Reaction: The car removes itself from car and hall call service (car calls are canceled and hall calls are
canceled or reassigned).
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
Car out of service with doors closing, CAR OS DOORS CLOSING
Description: A delayed car with closing doors has remained so for an excessive period of time (as determined
by a user-programmed timer parameter, Car Operation Screen/Passenger tab.
Car Reaction: The car removes itself from car and hall call service (car calls are canceled and hall calls are
canceled or reassigned).
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
Car out of service with unknown door position, CAR OS DOORS UNKNOWN
Description: A delayed car with invalid doors has remained so for an excessive period of time (as determined
by a user-programmed timer parameter, Car Operation Screen/Passenger tab.
Car Reaction: The car removes itself from car and hall call service (car calls are canceled and hall calls are
canceled or reassigned).
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
Car out of service with doors open, CAR OS DOORS OPEN
Description: A delayed car with open doors has remained so for an excessive period of time (as determined
by a user-programmed timer parameter, Car Operation Screen/Passenger tab.
Car Reaction: The car removes itself from car and hall call service (car calls are canceled and hall calls are
canceled or reassigned).
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
Car out of service with doors opening, CAR OS DOORS OPENING 6
Description: A delayed car with opening doors has remained so for an excessive period of time (as deter-
mined by a user-programmed timer parameter, Car Operation Screen/Passenger tab.
Car Reaction: The car removes itself from car and hall call service (car calls are canceled and hall calls are
canceled or reassigned).
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
Car out of service with doors stalled, CAR OS DOORS STALLED
Description: A delayed car with stalled doors has remained so for an excessive period of time (as determined
by a user-programmed timer parameter, Car Operation Screen/Passenger tab.
Car Reaction: The car removes itself from car and hall call service (car calls are canceled and hall calls are
canceled or reassigned).
Troubleshooting:
1. Determine what is inhibiting the car from reaching its destination.
2. Check the event log for any faults that may have prevented the car from moving.
6-19
Troubleshooting
iControl Messages
Car Over Load Activated, CAR OVERLOAD
Description: The load in the car has exceeded the Overload Threshold setting.
Car Reaction: The car is held at the floor with doors open. Over load indicators, if present, will be activated.
Troubleshooting:
1. If this message appears to be displayed in error, verify the programmed Over Load Threshold value and
adjust if needed. Please refer to Configuration - Load weigher on page 9-140.
2. Evaluate whether or not the load in the car exceeds the Over Load Threshold value. Calibrate the load
weigher if necessary.
3. For discrete input load weighers, check the Over Load input shown on the job prints.
Car Over Load Deactivated
Car Panel Inspection Disabled, CP INSP. DISABLED
Description: Car Panel inspection operation has been disabled.
Car Reaction: The car cannot be run on car panel inspection operation.
Troubleshooting:
1. Check for any car status that might prevent car panel inspection operation, e.g. earthquake.
2. Check for the Stuck Inspection Input Fault.
3. Check all inspection buttons (Enable, Up, Down) and verify that none are stuck in the ON position.
Car Panel Inspection Enabled
Description: Car Panel inspection operation which was previously disabled is now enabled.
Car Panel Inspection Inputs OK
Description: One or more previously stuck cartop inspection inputs (Enable, Up, Down) have been deacti-
vated (see Stuck Car Panel Inspection Input message).
Car Panel Inspection Operation, Car Panel Inspection, Car Panel Insp.
Description: The car has been placed in inspection mode using a (typically) keyed switch on the car opera-
tion panel.
Car Reaction: If running, the car makes and emergency stop and is taken out of passenger service. The car
uses the inspection pattern settings and can only be moved using the car panel inspection key switches.
Troubleshooting:
1. Check the car panel inspection switch and related inputs.
2. The Car Panel Inspection input is Normally High.
Car shut down due to emergency power operation with no supervisor (Activated)
Description: iControl has detected that an emergency power condition exists and it has not established com-
munication with the emergency power supervisor (typically a group controller).
Car Reaction: The car is not allowed to move to prevent overloading the emergency power generator. If the
car is moving when the event occurs, the car will make an emergency stop. motor contactor and brake con-
tactor are immediately dropped. The car is also shut down (calls and all other demands are canceled).
Troubleshooting:
1. If this condition exists and the system is NOT operating under emergency power, refer to the job prints
and verify wiring to the controller Emergency Power status input.
2. Verify correct input state (high/low) on iView/Car Operation/Emergency Power/EPI Input setting.
3. Check group to car communication.
Car shut down due to emergency power operation with no supervisor (Deactivated)
Description: Emergency power condition, without established communication with group supervisor, has
been resolved. Either communication with the supervisor has been established or the emergency power con-
dition has been removed.
Car Reaction: While emergency power is in effect, the car is allowed to move as determined by the group
controller (iCue). Car selection for recall and emergency power operation is user -determined (iView/Car
Operation/Emergency Power and iCue iView/Emergency Power Configuration screens).
iControl Messages
Car Stop Switch Open, CAR STOP SWITCH OPEN
Description: The car panel stop switch input has dropped (in-car stop switch has been activated). This switch
may be bypassed during special modes of operation such as fire, CFSS, or EMS.
Car Reaction: Emergency stop if running. The car is not allowed to run again until the car panel stop switch
is moved to the RUN position.
Troubleshooting:
1. Check the in-car stop switch and switch connections.
2. Check current mode of operation and verify that the stop switch operation is as expected.
Cartop Automatic Unintended Motion Fault, CARTOP AUTO UIM FLT
Description: An unintended motion fault has been detected while the car was running under Passenger oper-
ation.
Car Reaction: Emergency Stop. Cancel all calls. This fault will self reset.
Troubleshooting:
1. Check the iView Event Log for preceding activity.
2. Correct initiating problem, if any.
Cartop Communication Established
Description: Communication between iControl (iBox) and the iLink ICE-CTP board has been established. This
communication is through twisted-pair, shielded cabling in the traveler cable.
Cartop Communication Fault, CARTOP COMM FAULT
Description: Communication between iControl and iLink have failed. This communication is through twisted-
pair, shielded cabling in the traveler cable.
Car Reaction: Emergency Stop. Cancel all calls.
Troubleshooting:
1. Check the connections at the iBox and iLink ends of the connection. Refer to -CW job print drawing.
2. If the connections are clean and tight, use an oscilloscope to check the TX and RX signals themselves.
Or, if practical, connect the iBox end of the connection to another iControl in the machine room and see
if that controller can communicate with the iLink box.
3. If required, replace the iLink Cartop board or the iBox as appropriate.
Cartop Emergency Stop
Description: The cartop processor has detected a fault and initiated an emergency stop. The Cartop Safety
relay has opened in response to an unsafe condition.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. Cancel all calls.
Troubleshooting: 6
1. Check the iView Event Log for related preceding events.
2. Troubleshoot and correct any initiating problem.
3. Restore safety string and test.
Cartop Exit Open, CARTOP EXIT OPEN
Description: The Cartop Exit Switch input has dropped. The input is normally on when the configuration
states that the switch is installed. The input may be bypassed by: 1) the car being on car top or car panel
inspection while on earthquake, and 2) the safety bypass jumper being installed.
Car Reaction: Emergency stop if running. The car is not allowed to run until the problem is corrected.
Troubleshooting:
1. Check the switch status and configuration (Safety screen).
2. Check elements related to bypassing.
Cartop Exit Open Off (see: Cartop Exit Open)
6-21
Troubleshooting
iControl Messages
Cartop Exit no Counterweight Configuration Error, CTEX NO CWI CFG ERROR
Description: Car Top Exit, on the Safety tab, has been checked but Counter weight displacement detection,
on the Car Operation - Earthquake tab, has not been checked. A car equipped with both Earthquake Opera-
tion and Cartop Exit must have a counterweight derailment device.
Car Reaction: The car is not allowed to run until the problem is corrected.
Troubleshooting:
1. Verify the status of the Car Top Exit parameter (Safety tab).
2. Verify the status of the Counter weight displacement detection parameter (Car Operation - Earthquake
tab).
Cartop Firmware Update Mode, CARTOP FW UPDATE MODE
Description: The cartop processor is not running the cartop application firmware but is instead either waiting
for or processing the firmware update (iView > File > Firmware update).
Car Reaction: The car is not allowed to run until the procedure is completed.
Cartop Inspection Disabled, CT INSP. DISABLED
Description: Cartop inspection operation has been disabled.
Car Reaction: The car cannot be run on cartop inspection operation.
1. Check for any car status that might prevent cartop inspection operation, e.g. earthquake.
2. Check for the Stuck Inspection Input Fault.
3. Check all inspection buttons (Enable, Up, Down) and verify that none are stuck in the ON position.
Cartop Inspection Enabled
Description: Cartop inspection operation which was previously disabled is now enabled.
Cartop Inspection Inputs OK
Description: One or more previously stuck cartop inspection inputs (Enable, Up, Down) have been deacti-
vated (see Stuck Cartop Inspection Input message).
Cartop Inspection Operation, Cartop Inspection, Cartop Insp
Description: The car has been placed in Inspection mode using the cartop inspection switch.
Car Reaction: The car enters inspection mode and uses the Inspection pattern settings.
Cartop Inspection Unintended Motion Fault, CARTOP INSP UIM FLT
Description: An unintended motion fault was detected while the car was being operated on Cartop Inspection
Operation.
Car Reaction: Car motion stopped after 24 inches of travel. The safety circuit is opened.
Troubleshooting:
1. Check the iView Event Log for related events.
2. Troubleshoot and correct any initiating problems.
3. Press iBox Fault Reset.
4. Test.
Cartop Power Loss
Description: A loss of power was detected by the iLink processor.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check 1, 2, and 3 bus terminal voltages from iControl, through traveler, to car terminal strip.
2. Refer to job print drawing CT, check strip to iLink connections.
3. Check iLink fuses F1 and FCT1.
CFSS Mode 1 at Floor Activated, CFSS 1 at Floor. See CFSS Mode 1 In-car Activated.
iControl Messages
CFSS Mode 1 In-car Activated, CFSS 1 In-car.
Description: Commandeer For Special Services is a special operating mode. When activated by a (typically)
keyed hall switch the car recalls to that floor. Two CFSS operating modes may be configured on the Car
Operations screen/CFSS tab (Mode 1, Mode 2). Typically, one of the two is used for Hospital Operation, the
second as the user determines. Once recall is activated, the car disposes of existing calls as configured on
the CFSS tab, then moves to the recall floor. At the recall floor, In-Car CFSS is activated by an in-car switch
or as configured on the CFSS tab (In-Car).
Car Reaction: As configured on the Car Operations screen/CFSS tab.
CFSS Mode 1 Recall Activated, CFSS 1 Recall. See CFSS Mode 1 In-car Activated.
CFSS Mode 2 at Floor Activated, CFSS 2 at Floor. See CFSS Mode 1 In-car Activated.
CFSS Mode 2 In-car Activated, CFSS 2 In-car. See CFSS Mode 1 In-car Activated.
CFSS Mode 2 Recall Activated, CFSS 2 Recall. See CFSS Mode 1 In-car Activated.
Construction Car Panel Inspection Operation, Cnstr Car Panel Insp, Cnstr CP Insp
Description: The car is on Construction mode and car panel inspection.
Car Reaction: Car is out of service and cannot be moved using the car panel inspection key switches.
Troubleshooting: When Construction mode is active, car panel operation switches are ignored. The car can
only be moved using Machine Room or Cartop Inspection switches. Place the car on Machine Room or Cartop
Inspection and use the appropriate switches to move the car.
Construction Cartop Inspection Operation, Cnstr Cartop Insp, Cnstr CT Insp
Description: Car is on Construction mode and Cartop Inspection. When the iBox is in construction mode, it is
always on inspection. It will only operate in Cartop or Machine Room inspection. Car top has precedence
over Machine Room, just as in Passenger operation. If neither of these two modes of operation are selected,
the controller goes into a non-specific inspection mode. It will not run for any inspection direction input.
Car Reaction: The car can be moved using the cartop inspection key switches.
Troubleshooting:
1. If it appears that the car is on Cartop Inspection operation in error, verify wiring to the iBox INCT input.
If no voltage exists on this input, the car will operate under Cartop Inspection operation.
Construction Hoistway Access Inspection Operation, Cnstr HA Inspection, Cnstr HA Insp
Description: Car is on construction mode and hoistway access.
Car Reaction: Car is out of service and cannot be moved using the hoistway access Up or Down switches.
Troubleshooting: When Construction mode is active, hoistway access switches are ignored. The car can only
be moved using Machine Room or Cartop Inspection switches. Place the car on Machine Room or Cartop
Inspection and use the appropriate switches to move the car.
6
Construction Inspection Operation, Cnstr Inspection
Description: The car is operating in Inspection mode and the Construction setting on the Safety Configura-
tion screen is selected.
Car Reaction: The car will operate using the Inspection performance pattern using Cartop or machine room
inspection modes only.
Construction Machine Room Inspection Operation, Cnstr Mach Room Insp, Cnstr MR Insp
Description: Car is on inspection mode using the iBox inspection switch while on construction mode.
Car Reaction: Car begins operating in Inspection mode. If running, the car will make an emergency stop and
is taken out of normal service. Under this mode of operation, the car can be moved using the iBox Inspection
Up and Down switches.
Troubleshooting:
1. Related inputs:
MachineRoomInspection: Normally high
Controller Main Computer Startup
Description: iBox main processor booting up.
6-23
Troubleshooting
iControl Messages
Demand Down Peak Mode, DEMAND DOWN PEAK MODE
Description: The car is running in Demand Down Peak mode, favoring traffic in the down direction as config-
ured on the group control screens.
Demand Up Peak Mode, DEMAND UP PEAK MODE
Description: The car is running in Demand Up Peak mode, favoring traffic in the up direction as configured on
the group control screens.
Dispatcher = Car n, DISPATCHER = CARn (n = 1 to 20)
Description: Communication with the main iCue dispatcher has been lost or not established. This car is com-
municating with Car 'n' (n = 1 to 20) which is acting as the backup dispatcher.
Troubleshooting: Check the group to car communication related connections and parameters.
Door Lock Clipped Greater than 200fpm, DOOR LK CLIPPED G200
Description: The door lock signal (DLAT, DLMS, DLAB, or GS) went low for over 300mS while the car was
moving at over 200 fpm.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Use the Event Log to determine where the fault occurred. Examine the locks in that area of the hoistway
first.
2. Usually caused by a misadjusted door, where the pickup rollers do not have adequate running clearance
from the door clutch.
3. Because this fault must persist for over 300mS, a slight bumping of the door lock will not set it off. If
the door clutch/pickup roller clearance is adequate, make sure the door contacts are clean and the door
lock mechanism drops cleanly without friction or binding.
Door Lock Clipped Less than 200fpm, DOOR LK CLIPPED L200
Description: The door lock signal (DLAT, DLMS, DLAB, or GS) went low while the car was moving at under
200 fpm.
Car Reaction: ASAP stop.
Troubleshooting:
1. Usually caused by a misadjusted or damaged door. Because it only occurs at speeds under 200 fpm, it is
usually seen when the car leaves the floor where the problem door is located.
DOOR LOCK OPENED
Description: This is a status message indicating that the safety processor has detected that the door lock is
open. A fault is generated if the car is moving or attempts to move while the door lock is open.
Down Direction Limit Open, DOWN DIR LIMIT OPEN
Description: Down normal terminal direction limit switch is open.
Car Reaction: Initiate an immediate stop if moving. Further down direction movement is prevented.
Troubleshooting:
1. Verify that the switch is operating properly.
2. Verify correct state of the iBox DNTD input.
3. Verify that DNTD switch is activating/deactivating at the appropriate location (normally 2 below the bot-
tom terminal landing - see prints).
iControl Messages
Down Emergency Terminal Switch Position Fault, DN ETS POSITION FAULT
Description: The reported position upon encountering the Terminal Switch differed from the learned switch
position by more than the set position margin. This fault may be bypassed on the Diagnostics > Fault Bypass
tab.
Car Reaction: Emergency Stop: Motor contactor and brake contactor immediately dropped. All hall and car
calls are cancelled. After the car is stopped, it will run at Correction speed to the next available floor and
cycle the door. Door Open button will remain operational. If fault generated when car is moving, fault will
stay latched and the Fault Reset button must be pushed to clear it. If generated when the car is not moving,
fault will self clear when condition no longer exists.
Troubleshooting:
1. Physically check the integrity of the switch and wiring.
2. Check the iBox input for the switch.
3. On the Diagnostics > Terminal Switches Status tab, compare the last pass position against the learned
position for this switch. Verify that Position Margin is within a reasonable range. Relearn the NTS and ETS
switches. Please refer to Learning Normal & Emergency Terminal Limit Switches on page 4-11.
Down Emergency Terminal Switch Shutdown, DOWN ETS SHUTDOWN
Description: The Down Emergency Terminal switch opened at a speed or position exceeding its specified
threshold. The fault stays latched and the Fault Reset button must be pushed to clear it. If generated when
the car is stopped, the fault will self clear when the condition no longer exists.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. This fault is logged in conjunction with either a speed or position fault at DETS. Check the Event Log and
follow the troubleshooting recommended for the Down Emergency Terminal Switch Position Fault or
Safety A (or B) DETS Level 2 Speed Fault.
2. Press iBox Fault Reset to reset the fault.
Down Normal Terminal n Level 1 Speed Fault, DN NTSn L1 SPEED FLT (n = 1 to 5)
Description: A Level 1 Overspeed fault has been detected at Down Normal Terminal switch n (1 to 5). When
the switch opened, the car was traveling faster than defined by level 1 overspeed settings (sum of learned
speed plus Overspeed 1 Margin percentage on Configuration > Terminal Switches tab) but not fast enough to
trigger the Level 2 overspeed fault. This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Controlled stop using Emergency Slowdown pattern parameters.
Troubleshooting:
1. On the Diagnostics > Terminal Switches Status tab, compare the last pass and the Learned speeds for
this switch. If appropriate, increase the Overspeed 1 Margin on the Configuration > Terminal Switches
tab.
6
2. May be caused by a change in the Pattern parameters. Always re-learn the terminal switches after any
changes to Pattern parameters.
3. One or two floor runs can sometimes come in hotter than multi-floor runs. (Remember that the
switches are learned making full hatch runs.) If short runs are causing this, you may have to increase
the Overspeed 1 Margin or lower the Standard profile - High Roll Jerk parameter.
4. Can also be caused by a car that is following the pattern poorly, possibly due to heavy load or poor speed
loop performance. In this case, adjust the speed loop to follow pattern as well as possible and/or alter
the pattern parameters to produce a gentler deceleration and approach to the floor (then re-learn the
switches). Please refer to Terminal Switch Overspeed and Position Faults on page 4-55.
6-25
Troubleshooting
iControl Messages
Down Normal Terminal n Level 2 Speed Fault, DN NTSn L2 SPEED FLT (n = 1 to 5)
Description: A Level 2 Overspeed fault has been detected at Down Normal Terminal switch n (1 to 5). When
the switch opened, the car was traveling faster than defined by Level 2 overspeed settings (105% of the sum
of the learned speed plus the Overspeed 1 Margin percentage setting on the Configuration > Terminal
Switches tab). This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. On the Diagnostics > Terminal Switches Status tab, compare the Last pass and Learn speeds for this
switch. If appropriate, increase the Overspeed 1 Margin on the Configuration > Terminal Switches tab.
2. May be caused by a change in the Pattern parameters. Always re-learn the terminal switches after any
changes to Pattern parameters.
3. One or two floor runs can sometimes come in hotter than multi-floor runs. (Remember that the
switches are learned making full hatch runs.) If short runs are causing this, you may have to increase
the Overspeed 1 Margin or lower the Standard profile - High Roll Jerk parameter.
4. Can also be caused by a car that is following the pattern poorly, possibly due to heavy load or poor speed
loop performance. In this case, adjust the speed loop to follow pattern as well as possible and/or alter
the pattern parameters to produce a gentler deceleration and approach to the floor (then re-learn the
switches). Please refer to Terminal Switch Overspeed and Position Faults on page 4-55.
Down Normal Terminal n Position Fault, DN NTSn POSITION FLT (n = 1 to 5)
Description: When the switch opened or closed, the cars reported position was different from the learned
position by an amount exceeding the margin set on the Configuration > Terminal Switches tab. This may
mean that the switch opened early, late or not at all on approach to the terminal. It may also mean that the
switch closed early, late, or not at all on departure from the terminal. Finally, the switch can go open while
standing at a floor where its learned position is closed, or go closed at a floor where its learned position is
open. This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: If traveling down, the car executes an emergency slowdown, then continues at low speed until
it encounters a floor. The car stops at the floor, opens its doors, and performs a floor sync operation. If the
fault persists, the car goes out of service. If traveling up, the car continues normally to the first stop, opens
its doors and performs a floor sync operation. If the fault persists, the car goes out of service. If stopped at
a floor, the car opens its doors, does a floor sync, and, if the fault persists, takes itself out of service.
Troubleshooting:
1. On the Diagnostics > Terminal Switches Status tab, compare the Last pass position to the Learned posi-
tion for this switch.
2. If the fault is mechanical (switch movement, magnet movement, or bad traveler cable), the fault will
tend to repeat at the same position every time.
3. A stuck switch is easy to spot by running the car on inspection and observing the input LEDs on the iBox.
4. Perform a Terminal Sync operation (Terminal button on the Configuration > Pattern > Common tab).
Drive At-Speed Fault, DRIVE AT-SPEED FAULT
Description: Detected by the drive, this fault indicates that the motor speed is outside threshold limits
defined by the drive parameter. AC controls only. (This fault is not monitored for the TORQMAX F5 drive).
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. If the job has a TORQMAX F5 drive and this fault occurs, verify that wires AT and GND (from iBox J46)
are connected to drive terminal X2A-26 (Common).
iControl Messages
Drive Communication Fault, DRIVE COMM FAULT
Description: Indicates that the iBox is unable to communicate with the AC drive. It can only be generated if
Drive interface and Reference type are set to Serial (Controller > Configuration > Drive > General tab).
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped and the car will
not move until communication is established.
Troubleshooting:
1. Verify that a proper and functional serial cable (not an off-the-shelf serial cable) is connected between
the iBox (MODEM) and the drive (operator serial port - bottom).
2. Verify that the drive is configured for control signals via serial communication (LF.02 Signal/operating
mode is set to SErSP Serial Comm. Speed Control).
Drive Communication Warning, DRIVE COMM WARNING
Description: Not currently used.
Drive Enable Feedback Fault, DRIVE ENABLE FDBK FLT
Description: iControl failed to send the Drive Enable signal to the drive or the drive failed to respond to the
Drive Enable signal. (applies to both AC and DC drives).
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. Followed by nor-
mal run. Fault will self clear and car is able to run again.
Troubleshooting:
1. This fault may indicate a problem with the Gate Switch, or one of the door locks, opening up during the
initial start of car motion. Verify that the inputs (GS, DLAT, DLAB, DLMS) remain high.
2. Verify that Safety Processors A and B are looping (iBox status LEDs).
3. Verify that there are no faults active on Safety Processors A and B that would prevent motion.
4. Check the iBox power supply.
5. Verify that all drive connections match wiring prints.
Drive Fault, DRIVE FAULT
Description: Detected by the drive, this fault indicates that the motor speed is outside threshold limits
defined by the drive parameter. (TORQMAX drive only.)
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify encoder wiring and polarities.
2. Check F5 drive terminals X2A-29 (Drive Fault) to X2A-26 (Common). The value should be high during
normal operation and low during a fault condition.
3. Verify that the brake is working correctly.
4. Verify drive gains, Proportional Gain (LF.31) and Integral Gain (LF.32). 6
5. Check drive parameters, Speed Following Error (LF.57), Speed Difference (LF.58), and Following Error
Timer (LF.59). Refer to the TORQMAX manual.
Drive Inspection Overspeed Fault, DRIVE IOS FAULT
Description: Inspection Overspeed fault. (TORQMAX drive only.)
Car Reaction: Emergency stop.
Troubleshooting:
1. Check Inspection speed.
2. Check safety configuration.
3. Calibrate car speed with a hand-held tachometer.
6-27
Troubleshooting
iControl Messages
Drive On Fault, DRIVE ON FAULT (was Drive Ready On Fault)
Description: When the SCR drive receives Direction (UP/DN), Run Enable (RE) and M Contactor (M1/M2 side
mount auxiliaries) it must activate the DRO signal within 0.250 seconds. If not, this fault is generated. (DC
drive only)
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check M1 & M2 Contactor side-mount auxiliaries. N.O. contact may not be making.
2. Check the 26 pin connector J5 on SCR-LGA board for proper seating at both ends (46 pin D-sub on the
right side of the PowerBox).
3. Then verify that the cable that extends to the iBox (AC/DC Drive jack) is properly seated. If the cable
inside the PowerBox is suspect, temporarily connect directly from the drive into the iBox.
4. Check the RJ45 serial drive cable (J8 on the SCR-LGA board) to the Serial Drive jack on the iBox.
5. On iView, display the Controller > Diagnostics > Diagnostic Outputs > Drive screen and verify that the
commands are being sent from the iBox to the System 12 drive.
6. Check M1 and M2 side mount auxiliaries again.
7. Verify that Speed Pick Delay 1 is 0.2 or higher.
Drive Ready Fault, DRIVE READY FAULT
Description: AC drive ready signal is low. (TORQMAX drive only.)
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check F5 drive terminal X2A-24 to X2A-26 (Common). X2A-24 should be low during normal operation
and high during fault.
2. Check connection from AC drive to iPower Box and J46 connector on ICE-SAF board.
Drive Start Failure
Description: The drive control logic has not responded to a movement request from the motion control logic
for more than ten seconds.
Car Reaction: The motion control logic will continue to request movement from the drive logic for up to ten
seconds before declaring a Motion Start Failure fault.
Troubleshooting: Verify that no drive or motor faults exist.
Dual Channel QUAD Fault, DUAL CHANNEL QUAD FLT
Description: The Safety system did not detect movement of the car even though the iBox processor reported
car movement, or the Safety system reported car movement while the processor did not.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Press the Fault Reset button.
2. Check the wiring for the DP1 and DP2 encoder signals from the landing system to the iBox.
3. Check the motor encoder or tachometer (whichever is present).
4. Compare Pattern Command and Speed Feedback on the iView oscilloscope screen to make certain they
track one another.
5. Check reported speed accuracy using a hand-held tachometer.
Earthquake board power supply OFF
Description: The controller has detected a failure of the earthquake board power supply.
Car Reaction: The car behaves as if the counterweight derailment detector has been triggered (car generally
makes an emergency stop, and is removed from service at the next available landing).
Troubleshooting:
1. Check board connections.
2. Replace the EQ board.
iControl Messages
Earthquake board power supply ON
Description: The earthquake board (ICE-EQ) power supply is operational.
Car Reaction: Car is no longer prevented from operating due to a loss of the earthquake board power supply.
Earthquake Emergency Stop
Description: Earthquake operation has been activated by the seismic or counterweight displacement
switches and the car has performed an emergency stop as specified by the earthquake user settings.
Car Reaction: The car will perform an emergency stop. After a pause, the car will react as directed by user
settings on the Car Operation screen Earthquake tab.
Troubleshooting:
1. Check the wiring for the seismic and counterweight displacement inputs.
2. Check the earthquake user settings on the Car Operation screen Earthquake tab.
Earthquake Operation Activated
Description: The car is on earthquake operation.
Car Reaction: Car behavior is according to the user settings on the Car Operation screen Earthquake tab.
This operation is latched until the EQ reset button is pressed on the ICE-EQ board.
Troubleshooting: NA. See also Earthquake Operation (Seismic Switch) and Earthquake Operation (Coun-
terweight).
Earthquake Operation Deactivated
Earthquake Operation (Counterweight)
Description: The Counterweight Derailment Detector has been activated, indicating an earthquake condition.
Car Reaction: The car will typically make an emergency stop, then move slowly to the next available floor in
a direction away from the counterweight. The fault is latched until the EQ reset button (ICE-EQ board) is
pressed.
Troubleshooting:
1. If it is suspected that this event happened in error, check the counterweight derailment detector opera-
tion and associated wiring to the ICE-EQ board.
Earthquake Operation (Seismic Switch)
Description: The Seismic Switch has been activated (input has gone low), indicating an earthquake condi-
tion.
Car Reaction: The car will react as determined by user configuration. (iView/Car Operation/Earthquake) The
car will either make an emergency stop and then move slowly to the next available floor or it will stop nor-
mally at the next available floor in the direction of travel. The fault is latched until the EQ reset button (ICE-
EQ board) is pressed.
6
Troubleshooting:
1. If it is suspected that this event happened in error check the seismic switch input and the associated wir-
ing to the ICE-EQ board. The seismic input is normally on.
Earthquake Reduce Speed
Description: An earthquake event (seismic switch) has initiated a car speed reduction (150 fpm or less) as
required by some code jurisdictions.
Car Reaction: Control stop.
Earthquake reset button OK
Description: A previously declared failure of the earthquake reset button has been resolved.
Car Reaction: Previous failure is no longer a reason to keep the car out of service.
6-29
Troubleshooting
iControl Messages
Earthquake reset button stuck ON
Description: The controller has detected that the earthquake reset button (located on the ICE-EQ board) has
failed in the on state.
Car Reaction: If moving, the car will complete its run. Once stopped, the car is removed from service.
Troubleshooting:
1. It is likely that the reset button (or related circuitry) on the ICE-EQ board is faulty.
2. Replace the ICE-EQ board.
Earthquake Run, EARTHQUAKE RUN
Description: Some code jurisdictions allow the car to run normally (at a speed no greater than 150 fpm)
under earthquake conditions. This event indicates that the car is being allowed to run in this manner.
Car Reaction: Car operates normally at reduced speed.
Troubleshooting:
1. Check the wiring for the seismic and counterweight displacement inputs.
2. Check the earthquake user settings on the Car Operation screen Earthquake tab.
Earthquake Shutdown, EARTHQUAKE SHUTDOWN. See Earthquake Operation Activated.
EEPROM Device Error, EEPROM DEVICE ERROR
Description: Safety Processor A EEPROM fault.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify Safety Processor A EEPROM - board test. Contact MCE.
Elevator Recall Operation (Switch n), ELEVATOR RECALL SWn (n = 1 to 6)
Description: Elevator Recall Operation has been initiated by the switch identified.
Car Reaction: In most usages, the car immediately removes itself from hall call service, answers remaining
car calls, then proceeds to the recall floor and cycles its doors. (The disposition of car calls, recall floor, and
door operation are user-programmable. iView/Car Operation/Elevator Recall.)
Emergency Alarm Acknowledged
Description: This message indicates that the emergency alarm has been acknowledged and reset by the
Emergency Alarm Reset input.
Car Reaction: The Distress Light and the Distress Buzzer outputs will be extinguished.
Troubleshooting: NA
Emergency Alarm Activated (Alarm button), Emergency Alarm Activated, EMERG ALARM ACTI-
VATED
Description: The Emergency Alarm input has been activated. Typically used to sound an alarm and/or illumi-
nate an indicator light to alert security personnel.
Car Reaction: The Distress Light will be illuminated until it is acknowledged by the Emergency Alarm Reset
input. The Distress Buzzer output will either pulsate or is continuously activated as long as the car remains in
this condition.
Troubleshooting:
1. Attend to the car and verify the distress signal.
2. To reset the alarm, verify that the alarm button is restored to normal condition and activate the Emer-
gency Alarm Reset input.
iControl Messages
Emergency Alarm Activated (Car delayed with doors closed)
Description: This message indicates that the emergency alarm has been activated due to the car being
delayed with its doors closed. This is an optional emergency alarm monitor specified by the user.
Car Reaction: The Distress Light will be illuminated until it is acknowledged by the Emergency Alarm Reset
input. The Distress Buzzer output will be active as long as the car remains in this condition.
Troubleshooting:
1. Attend to the car and verify the distress signal.
2. To reset the alarm, verify that the car condition is restored to normal and activate the Emergency Alarm
Reset input.
Emergency Alarm Activated (In-car stop switch)
Description: This message indicates that the emergency alarm has been activated due to the in-car emer-
gency stop switch being pulled.
Car Reaction: The Distress Light will be illuminated until it is acknowledged by the Emergency Alarm Reset
input. The Distress Buzzer output will be active as long as the switch remains active.
Troubleshooting:
1. Attend to the car and verify the distress signal.
2. To reset the alarm, verify that the car emergency stop switch is restored to normal position and activate
the Emergency Alarm Reset input.
Emergency Alarm Activated (Safety opened)
Description: This message indicates that the emergency alarm has been activated due to the safety circuit
being opened (excluding the in-car emergency stop switch). This is an optional emergency alarm monitor
specified by the user.
Car Reaction: The Distress Light will be illuminated until it is acknowledged by the Emergency Alarm Reset
input. The Distress Buzzer output will be active as long as the car remains in this condition.
Troubleshooting:
1. Attend to the car and verify the distress signal.
2. To reset the alarm, verify that the car condition is restored to normal and activate the Emergency Alarm
Reset input.
Emergency Alarm Deactivated without Acknowledgment
Description: This message indicates that the emergency alarm has been deactivated because all signals that
would activate it are now off and the Require Acknowledgment parameter is not checked.
Car Reaction: The Distress Light and Distress Buzzer outputs are deactivated.
Emergency Brake Leg 1 Short Fault, EMERG BRK LEG 1 SHORT 6
Description: Emergency brake board (ICE RB or ICE EB) verification failed after a stop or as a result of a
fault reset. During these scenarios, the emergency brake circuitry is verified by transitioning between leg 1
and leg 2. One of the legs must be active to prevent the emergency brake from deploying.
Car Reaction: Emergency stop.
Troubleshooting:
1. Verify system configured for emergency brake board (ICE-RG or ICE EB).
2. Make sure the emergency brake board is physically present and correctly connected.
Emergency Brake Leg 2 Short Fault, EMERG BRK LEG 2 SHORT. See Emergency Brake Leg 1 Short
Fault.
Emergency Brake OK open, EMERG BRAKE OK OPEN
Description: The Emergency Brake OK input has dropped (off) when the configuration states that the brake
is installed and therefore the input should be picked (on).
Car Reaction: Emergency stop if running. The car is not allowed to run until the problem is corrected.
Troubleshooting:
1. Verify that the Rope Gripper board is properly installed, connected, and powered.
2. If this job has a sheave brake, verify that the associated circuitry is per the job prints.
6-31
Troubleshooting
iControl Messages
Emergency Brake OK open Off (See: Emergency Brake OK open)
Emergency Brake Tripped, EMERG BRAKE TRIPPED
Description: The emergency brake output (ICE RG or ICE-EB board) has gone low, causing the emergency
brake to set.
Car Reaction: Emergency stop.
Troubleshooting:
1. Check that the output did not go low in error and is properly connected.
2. Check the elevator for underlying causes.
Emergency Brake UIM Reset Button Stuck, EM BK UIM RESET STUCK
Description: The reset button on the Rope Gripper board (ICE-RG) or Emergency Brake board (ICE-EB) has
been activated for more than 15 seconds.
Car Reaction: The car is not allowed to move. If in motion, the car is allowed to finish the run.
Troubleshooting: Check the reset button on the ICE-RG or ICE-EB board.
Emergency Dispatch On, Emergency Dispatch, EMERGENCY DISPATCH
Description: The car is automatically servicing the building in a pre-defined pattern. This operation is
invoked when a failure of the hall calls bus or group communication is detected. This operation may also be
activated using a key switch input.
Car Reaction: The car automatically moves to every floor in the building in a predefined pattern and cycles
its doors.
Troubleshooting:
1. Check group/car communications.
2. Check the hall call bus drivers.
3. Check the Emergency Dispatch input.
Emergency Dispatch Off (see Emergency Dispatch On)
Emergency Medical Service Bypassed
Description: EMS is active but has been bypassed by another mode of operation.
Car Reaction: EMS service is bypassed and the car operates under the new mode of operation.
Troubleshooting:
1. Check the current mode of operation and the EMS user settings.
Emergency Medical Service Deactivated
Description: EMS has been deactivated.
Car Reaction: Car is returned to prevailing mode of operation.
Troubleshooting: NA
Emergency Medical Service In-Car Activated (Switch n), EMS In-car (Switch n) (n = 1 or 2)
Description: EMS In-Car service is activated via the in-car EMS key-switch. This is also referred to as the
EMS Phase II operation.
Car Reaction: The car remains out of hall call service. Car calls are enabled again and the car can be dis-
patched from inside the car with car calls only. After answering a car call, doors will open automatically and
close with constant pressure on the Door Close Button only.
Troubleshooting:
1. The EMS In-Car can be terminated by taking the car to the EMS recall floor by registering a car call then
deactivating the in-car EMS switch.
2. The In-Car operation can also be terminated by simply removing the in-car EMS switch from the pre-pro-
grammed IO configuration.
3. Related inputs:
EMSCarSwitch0: Normally low
EMSCarSwitch1: Normally low
iControl Messages
Emergency Medical Service Recall Activated (Switch n), EMS Recall (Switch n) (n = 1 or 2)
Description: EMS recall is activated via one of the EMS recall key-switches located next to the designated
EMS elevator. This is also referred to as the EMS Phase I operation.
Car Reaction: Momentary activation of the EMS recall switch will initiate a recall to the user-defined EMS
Recall floor. The car removes itself from car and hall call service. Once at the EMS recall floor, the door oper-
ation is in accordance to the user-defined door operation under EMS recall operation. The car will remain on
EMS Phase I as long as the hall switch is activated. Once the hall switch is deactivated, the car will return to
normal operation upon expiration of a user-defined timer if the in-car switch is not activated within that time.
Troubleshooting:
1. Verify that none of the hall EMS recall switches is activated.
2. The EMS Recall operation can also be terminated by simply removing the in-car EMS switch from the pre-
programmed IO configuration.
3. Related inputs:
EMSHallSwitch0: Normally low
EMSHallSwitch1: Normally low
Emergency Power Activated
Description: Commercial power has been lost and power is now supplied by an emergency power generator.
Car Reaction: The car will make an emergency stop due to the momentary loss of power and will remain shut
down until commanded to either lower to a pre-determined floor or proceed to the next available floor. Once
all cars have reached a floor, one or more cars will be selected to run under the emergency power generator.
Troubleshooting:
1. Related inputs:
EPI: Active level field adjustable.
Emergency Power and no communication with group, EMERG PWR NO COMM
Description: iControl has detected that an emergency power condition exists and it has not established com-
munication with the emergency power supervisor (typically a group controller).
Car Reaction: The car is not allowed to move to prevent overloading the emergency power generator. If the
car is moving when the event occurs, the car will make an emergency stop. motor contactor and brake con-
tactor are immediately dropped. The car is also shut down (calls and all other demands are canceled).
Troubleshooting:
1. If this condition exists and the system is NOT operating under emergency power, refer to the job prints
and verify wiring to the controller Emergency Power status input.
2. Verify correct input state (high/low) on iView/Car Operation/Emergency Power/EPI Input setting.
3. Check group to car communication. 6
Emergency Power Deactivated. See Emergency Power Activated.
Description: This event is logged when commercial power is restored.
Troubleshooting:
1. Related inputs:
EPI: Active level field adjustable.
Emergency Power Recall, EMERG POWER RECALL. See Emergency Power Activated.
Description: This event is logged when the elevator has been commanded to lower to the emergency power
recall floor.
Car Reaction: The elevator proceeds to the user-defined emergency power recall floor. Door operation at the
recall floor is in accordance with the user defined door operation under emergency power recall conditions.
Troubleshooting:
1. Related inputs:
EPR: Normally low (high to lower the car)
PTR: Normally low (low to lower the car)
6-33
Troubleshooting
iControl Messages
Emergency Power Run, EMERG POWER RUN. See Emergency Power Activated.
Description: This elevator is allowed to respond to calls during emergency power operation.
Troubleshooting:
1. Related inputs (only on elevators with emergency power overlay operation)
EPR: Normally low (low to run the car)
PTR: Normally low (low to run the car)
Emergency Power Shutdown, EMERG POWER SHUTDOWN. See Emergency Power Activated.
Description: This event is logged when emergency power is initially activated or if communication with the
emergency power supervisor has been lost while on emergency power.
Car Reaction: Emergency stop. Car removed from service.
Troubleshooting:
1. Related inputs:
EPI: Active level field adjustable.
Emergency Stop Input Activated, EMERGENCY STOP INPUT
Description: The events are logged and related car status messages displayed on the OBD and iView to
reflect the status of the Emergency Stop Input.
Car Reaction: When the Emergency Stop Input is activated, the car makes an emergency stop and cancels
all calls. This input has priority over all modes of operation including Fire Service.
Troubleshooting: Check the status of the Emergency Stop Input.
Emergency Stop Input Deactivated see Emergency Stop Input Activated.
Event Log Cleared
Description: Indicates that all of the events previously logged in the event log were removed using the Clear
all button (iView Controller > View > Diagnostics > Event Log tab).
Excessive Brake Feedback Fault, EXCESS BRAKE FDBK FLT
Description: After each brake activity, the controller checks to see that brake current is bleeding off properly.
(After 1 second, brake voltage should be at or below 85% of the voltage applied by the last command.) This
fault is issued if brake voltage remains too high when checked by the controller.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. From the factory, RB (brake resistor circuit value) is set 3 to 5 times the brake coil resistance. Reduce RB
to allow current to bleed off more quickly. (Do not reduce RB below 3 times brake coil resistance.) Please
refer to Verifying Brake Current Resistance on page 2-22.
2. On the iView Brake screen, Timers tab, reduce Voltage Decay Time (minimum, 0.0 seconds).
3. Check Brake Voltage Feedback test point on iView Oscilloscope screen.
4. Check iField Brake Module connections.
5. Check brake and brake connections.
6. If you continue to see this fault after taking the above steps, you may have a defective brake module or
iBox Safety board.
Excessive Faults Shutdown, EXCESSIVE FAULTS
Description: When there are five faults that resulted in an Emergency, Control, or ASAP stop within ten nor-
mal runs, this fault is generated.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. This is a latching
fault. The Fault Reset button on the iBox must be pressed to clear it.
Troubleshooting:
1. Check Event Log to see what drive faults were generated before this fault was triggered. Refer to those
drive faults for troubleshooting information.
iControl Messages
Excessive Motor Field Feedback Fault, EXCESS MF FDBK FAULT
Description: Excessive current was detected flowing through the motor field. Threshold is set to 85% of forc-
ing current for more than 4 seconds. If the fault is recurring, excessive faults will be generated and the
motor field module will be disabled.
Car Reaction: Emergency Stop.
Troubleshooting: Problem may be related to faulty motor field module, faulty iBox, or invalid motor field cal-
ibration.
1. If excessive faults (fault) has been generated, the module is disabled and should not be outputting any
voltage. If this is not the case, there may be a problem with the motor field module.
2. Calibrate the motor field. During calibration, the current and voltage should start at their maximum value
and decrease as calibration proceeds. If this is not the case, there may be a problem with the iBox.
Excessive Relevels Fault, EXCESS RELEVELS FAULT
Description: The car has failed to relevel after ten attempts.
Car Reaction: Cancel all calls and shutdown. The doors are cycled and the car remains shutdown until the
fault is reset by pressing the iBox Fault Reset button, toggling Inspection or cycling power to the controller.
Troubleshooting:
1. Check for mechanical or other failure preventing proper releveling.
2. Adjust brake and motor control during releveling with a full load in the car.
Excessive Restarts Fault, EXCESS RESTARTS FAULT
Description: The elevator has attempted to start movement from the same floor successively for an exces-
sive number of times. This fault is issued after twenty-five attempts. The counter is reset if the car makes
one successful run.
Car Reaction: Cancel all calls and shutdown. The doors are cycled and the car remains shutdown for five
minutes after the first fault or until the fault is reset by pressing the iBox Fault Reset button, toggling Inspec-
tion or cycling power to the controller.
Troubleshooting:
1. Check for mechanical or other failure preventing car from moving away from floor the floor.
Excessive Restarts Warning
Description: The elevator has attempted to start movement from the same floor successively for an exces-
sive number of times. This fault is issued after ten attempts. The counter is reset if the car makes one suc-
cessful run.
Car Reaction: None.
Troubleshooting: 6
1. Check for mechanical or other failure preventing car from moving away from the floor.
Exercise Operation Activated, EXERCISE OPERATION
Description: The car has been idle for a predetermined user-defined time and is now performing a user-
defined number of Exercise operation runs.
Car Reaction: The car lowers to the bottom landing, then proceeds to the top landing and back down to the
bottom landing without cycling the doors. Moving the car to the top landing and then back down to the bot-
tom landing is considered one exercise run. The user defines the number of exercise runs.
Exercise Operation Deactivated
Description: The car has completed all of the exercise runs or Exercise operation has been terminated due to
change in mode of operation or calls being entered into the system.
Fault Bypass Switch On, FAULT BYPASS SW ON
Description: The iBox Fault Bypass switch is in the ON position.
Car Reaction: None.
6-35
Troubleshooting
iControl Messages
Fault Bypass Switch Timed Out, FLT BYP SW TIMED OUT
Description: Indicates that a fault bypass has timed out. (Bypasses are allowed for 15 minutes with the iBox
Fault/Function Bypass switch in the ON position.)
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. To clear this fault, place the Fault/Function Bypass switch to the OFF position.
F DPM OPEN-GS CLOSED. See Front DPM Open - GS Closed.
F DR CLS FLT REC FAIL. See Front Door Close Fault Recovery Failure
Field Module Over Temperature Fault, FIELD MODULE OVR TEMP
Description: The temperature of the Motor Field module heat sink is excessive (DC only).
Car Reaction: Stop at the next floor. Restart not permitted.
Troubleshooting:
1. Check machine room ambient temperature (should not exceed 104 degrees F or 40 degrees C).
2. Verify that air enters through the bottom of the power box and is only expelled via the fan at the top of
the power box.
3. Check for insufficient air circulation through the power box.
4. Check the running temperature inside the power box (should not exceed 105 degrees F).
5. Check for faulty field module.
6. Check for faulty iBox.
7. Check for faulty connection between motor field module and iBox.
Fire Service In-car Activated, Fire Service In-car, Fire Svc In-car
Description: In-car firefighters service has been activated via the in-car fire service key-switch.
Car Reaction: Car and Door operation is in accordance to the user-defined fire code. (iView/Car Operation/
Fire Service.)
Troubleshooting:
1. Related inputs:
FireIIOn: Normally low
FireIIOff: Normally high
FireIIHold: Normally low
Fire Service In-Car Deactivated
Description: In-car firefighters service has been deactivated.
Car Reaction: Car is returned to prevailing mode of operation.
Fire Service In-car Hold Operation
Description: Car is on in-car firefighter hold operation.
Car Reaction: Car is held at a floor, typically with doors open. Car calls and door close buttons are disabled.
Troubleshooting:
1. Check the in-car firefighter switch status and Fire II hold operation user settings.
Fire Service In-car Recall Operation
Description: A car on in-car firefighter operation is being recalled to the designated fire recall floor.
Car Reaction: Car proceeds to the designated fire recall floor. Once at the recall floor, door operation is
according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. Check the in-car firefighter switch status and Fire II operation user settings.
iControl Messages
Fire Service Recall Alternate, Fire Recall Alternate, Fire Recall Alt.
Description: Fire recall to the alternate fire floor has been initiated.
Car Reaction: Car proceeds to the user-defined alternate fire recall floor. Once at the recall floor, door oper-
ation is according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. If in error, inspect the fire sensor and switch inputs and connections.
2. Related Inputs: Smoke sensors and fire recall switches as indicated on the job prints.
Fire Service Recall Main, Fire Recall Main, Fire Recall Main
Description: Fire recall to the main fire floor has been initiated.
Car Reaction: Car proceeds to the user-defined main fire recall floor. Once at the recall floor, door operation
is according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. If in error, inspect the fire sensor and switch inputs and connections.
2. Related Inputs: Smoke sensors and fire recall switches as indicated on the job prints.
Fire Service Recall Deactivated
Description: Fire service recall operation has been deactivated.
Car Reaction: Car returns to its prevailing mode of operation.
Troubleshooting: NA
Flood Operation Activated, FLOOD OPERATION
Description: Flood operation has been activated via system command or hardware switch.
Car Reaction: A car in the flood zone area moves immediately to a floor outside the flood zone. The car will
no longer service the floors in the flood zone until Flood Operation is deactivated.
Troubleshooting: Check the flood zone switch and the user interface command.
Flood Operation Deactivated
Description: Flood operation has been deactivated.
Car Reaction: The car will service all eligible floors.
Floor Heat Detectors Activated, FLOOR HEAT DETECTORS
Description: One or more floor heat detector inputs are activated. The fire warning light will flash until all
heat detectors have been reset. The fire-warning buzzer will sound until the car is shutdown at a floor.
Car Reaction: A car that is parked at a floor will open its doors and shut down. A car in motion will proceed in
the current direction to the next available floor where the heat detector is not tripped. If all heat detectors in
the current direction are tripped, the car will reverse direction and proceed to the first floor where the heat
6
detector is not tripped. If again all heat detectors are tripped, the car will proceed to the main fire recall floor
unless the car is also on Fire Service, in which case the car will proceed to the appropriate fire recall floor.
Once the car is stopped at a floor it will automatically open its doors and shut down. Then, if the machine
room or hoistway heat detectors are active, a signal is provided to disconnect the main power line and/or
activate the sprinklers where available. Please refer to Car Operation - Heat Detectors on page 9-89.
Floor Heat Detectors Deactivated
Description: All floor heat detector inputs are deactivated.
Car Reaction: The car is allowed to run.
6-37
Troubleshooting
iControl Messages
Floor Location Fault, FLOOR LOCATION FAULT
Description: Floor magnet location is recorded during the floor height learn procedure. The on and off posi-
tions for both the ULM and DLM sensors are recorded, for a total of four pieces of data for every floor mag-
net, front and rear. The controller watches for the floor magnets constantly and checks to see that each is in
its learned location.
Car Reaction: Run to next stop, then shut down.
Troubleshooting:
1. Usually, a magnet has shifted position or fallen off.
2. Check the clearance between the floor sensor board and the magnets. Set if necessary. (Sometimes this
clearance will be off just enough to make some magnets fail to register properly.)
3. Re-learn floor heights.
4. Perform a Terminal synchronization.
Floor Sensor Fault, FLOOR SENSOR FAULT
Description: The system did not detect a floor sensor while performing floor synchronization. Terminal syn-
chronization will be performed as a result.
Car Reaction: Normal stop.
Troubleshooting: Indicates that the elevator location in the hoistway is not where the system expected or the
door zone sensor is not being detected.
1. Fault will be generated if the car was moved while the controller was not powered. The system will detect
movement of the elevator for only ten seconds after power is removed. This will be sufficient to accom-
modate the time required for an elevator to stop after power is removed when running at contract speed.
2. On Inspection, verify that the system is detecting the LU, DZ, and LD signals when the elevator passes a
floor. The signals can be observed on the iView Floor Heights Configuration screen.
Floor Synchronization Fault
Description: While performing floor synchronization, the system either did not receive edge position data
from the cartop or did not detect a floor position magnet where expected.
Car Reaction: The car will stop and initiate terminal synchronization.
Troubleshooting:
1. Verify that the car was not moved after power was shut off.
2. Move the car past floors around the vicinity of the fault and verify the proper activation of the LU and LD
sensors.
3. Verify that the system is communicating with the cartop (no Cartop Communication Fault).
4. Verify that the absolute and cartop positions change by the same amount and in the same direction while
moving the car.
5. Verify that a magnet has not fallen off.
6. Check the clearance between the floor sensor board and the magnets. Sometimes this clearance will be
off just enough to make some magnets fail to register properly. Adjust clearance if necessary.
7. Re-learn the floor heights.
8. The iLink, iLand or iBox may be faulty.
Front Auxiliary Door Open Button Bypassed, FRONT AUX DOB BYP
Description: The front auxiliary door open button has been continuously activated for a user-defined time
and is now bypassed according to the user-defined setting. (iView Controller > Configuration > Car Opera-
tion > Doors)
Car Reaction: The front auxiliary door open button is rendered inoperative.
Troubleshooting:
1. Check the corresponding input: Front Auxiliary Door - Open Button (Normally low).
2. The operation of the door open button can also be restored by setting the Door open button bypass
option to off (unchecked) (iView Controller > Configuration > Car Operation > Doors).
iControl Messages
Front Door Close Fault, FRONT DOOR CLOSE FLT
Description: One or more front door failures to close have been detected. The controller will attempt to close
the doors as defined by user parameters (door close protection timer and number of attempts) before
declaring this fault. (iView Controller > Configuration > Car Operation > Doors)
Car Reaction: The doors will reopen fully. All car calls are canceled and car removes itself from hall call ser-
vice (hall calls assigned to this car are canceled or reassigned to other cars if available). Doors may be closed
using constant pressure on the front door close button.
Troubleshooting:
1. Door closed status is determined by the front door close limit and by the front door position monitor con-
tact if applicable. Check the wiring of these signals.
2. Check the door close protection timer and number of closing attempts on the Car Operation - Doors tab.
Front Door Close Fault Recovery Failure, F DR CLS FLT REC FAIL
Description: The Door Close Fault Recovery timer starts when a Door Close Fault is generated. When the
timer expires, the Door Close Fault is cleared to allow the doors to again attempt to close (see Front Door
Close Fault). This is repeated the number of times specified by the Door Close Fault Recovery Attempts
parameter. If the doors have failed to close when the number of attempts equals the recovery attempts
parameter setting, the Front Door Close Fault Recovery Failure is generated.
Car Reaction: The car is not allowed to run until a mode change is detected or the doors are successfully
closed via constant pressure on the Door Close Button.
Troubleshooting:
1. Door closed status is determined by the front door close limit and by the front door position monitor con-
tact if applicable. Check the wiring of these signals.
2. Check the door close protection timer and number of closing attempts on the Car Operation - Doors tab.
Front Door Close Time-out
Description: A failure of the front door to close has been detected. The controller will attempt to close the
doors for a period of time defined by the Closing protection timer parameter (Door Motor Protection Timers).
If the timer elapses prior to the doors closing fully, this event is generated.
Car Reaction: Doors reopen fully and again attempt to close.
Troubleshooting:
1. Door closed status is determined by the front door close limit and by the front door position monitor con-
tact if applicable.
2. Check the wiring of these signals.
3. Check the Closing protection timer (iView Car Operation Configuration/Doors Tab/General Tab/Door
Motor Protection Timers). 6
Front Door Contact Fault, FRONT DOOR CNTCT FLT
Description: A faulty front door contact (gate switch, door lock) has been detected. This is detected when the
doors are in their fully open position and either the gate switch contact is closed or the doors appear to be
locked.
Car Reaction: All car calls are canceled and the car removes itself from hall call service. The front doors are
not allowed to close and the car is not allowed to run.
Troubleshooting:
1. Check the front door gate switch and door lock contact at the floor at which the car is located.
2. Check associated wiring for these signals.
6-39
Troubleshooting
iControl Messages
Front Door Open Button Bypassed, FRONT DOB BYPASSED
Description: The front door open button has been continuously activated for a user-defined time and is now
bypassed according to the user-defined setting. (iView Controller > Configuration > Car Operation > Doors)
Car Reaction: The front door open button is rendered inoperative.
Troubleshooting:
1. Check the corresponding input: Front Door - Open Button (Normally low).
2. The operation of the door open button can also be restored by setting the Door open button bypass
option to off (unchecked) (iView Controller > Configuration > Car Operation > Doors)
Front Door Open Fault, FRONT DOOR OPEN FAULT
Description: One or more front door failures to open fully have been detected. After repeated attempts to
open the door (as specified by user parameters), a door open failure is declared. The amount of time allowed
for the door to open and the number of attempts made are user parameters. iView Car Operation/Doors tab,
plus Advanced dialog.
Car Reaction: The door stalls at its last position. Car calls are canceled and the car removes itself from hall
call service (hall calls assigned to this car are canceled or reassigned to other cars if available). Doors may
be moved via constant pressure on the door open and door close buttons.
Troubleshooting:
1. The door open status is determined by the front door open limit status.
2. Check the wiring of this signal.
3. Check the door open protection timer and number of open attempts on the Operation screen Doors tab
and associated Advanced dialog.
Front Door Open Time-out
Description: A failure of the front door to open has been detected. The controller will attempt to open the
doors for a period of time defined by the Opening protection timer parameter (Door Motor Protection Tim-
ers). If the timer elapses prior to the doors opening fully, this event is generated.
Car Reaction: The door open cycle is halted and the door is allowed to reclose. If so configured, repeated
attempts will be made to open the door. Otherwise, the car is allowed to leave the landing once the doors are
closed.
Troubleshooting:
1. Door open status is determined by the front door open limit and by the front door position monitor con-
tact if applicable.
2. Check the wiring of these signals.
3. Check the Opening protection timer (iView Car Operation Configuration/Doors Tab/Door Motor Protection
Timers).
Front Doors Stopped, FRONT DOORS STOPPED
Description: The Door Stop button or Emergency Stop switch was activated causing the doors to be pre-
vented from moving.
Car Reaction: The car is not allowed to move unless the doors are fully closed.
Troubleshooting: This condition can be cleared by activation of the Door Open button, Door Close button or if
the car goes into Inspection or Fire Service mode, provided that the Door Stop input is off.
Front DPM Open - GS Closed, F DPM OPEN-GS CLOSED
Description: The front door position monitoring contact is open while the gate switch is closed.
Car Reaction: None.
Troubleshooting: Check the front door position monitoring contact, gate switch and all related circuitry.
iControl Messages
Front Hall Door Open Button Bypassed, FRONT HALL DOB BYP
Description: The front hall door open button has been continuously activated for a user-defined time (Door
open bypass timer) and is now bypassed in accordance with the user-defined setting (iView Controller >
Configuration > Car Operation > Doors)
Car Reaction: The front hall door open button is rendered inoperative.
Troubleshooting:
1. Check the corresponding input, Front Door - Hall Door Open Button: Normally low.
2. The operation of the hall door open button can also be restored by setting the Door open button bypass
option to off (unchecked) (iView Controller > Configuration > Car Operation > Doors)
Front Photo Eye Bypassed, FRONT PHOTO EYE BYP
Description: The front photo eye device has been continuously activated for a user-defined time and is now
bypassed in accordance to the user-defined setting. (iView/Car Operation/Passenger/Anti Nuisance.)
Car Reaction: The front photo eye device is rendered inoperative.
Troubleshooting:
1. To restore the operation of the photo eye device, check the corresponding input.
2. Related inputs:
PhotoEyeFront: Normally low
Front Photo Eye Failure, FRONT PHOTO EYE FAIL
Description: This event is logged when the photo eye is continuously activated for a predetermined time (4
seconds) while the front doors are fully closed.
Car Reaction: The front photo eye is rendered inoperative.
Troubleshooting:
1. Check for abnormal blockage or failure of the front optical device.
2. Related inputs:
FrontPhotoEye: Normally low
Front Safe Edge Bypassed, FRONT SAFE EDGE BYP
Description: The front door safe edge has been continuously activated for a user-defined time and is now
bypassed according to the user-defined setting. (iView Controller > Configuration > Car Operation > Doors)
Car Reaction: The front safe edge is rendered inoperative.
Troubleshooting:
1. Check the state of the front safe edge input.
2. Related inputs:
SafeEdgeFront: Normally low 6
Front Safe Edge Failure, FRONT SAFE EDGE FAIL
Description: This event is logged when the front door safe edge is continuously activated for a predetermined
time (4 seconds) while the front doors are fully closed.
Car Reaction: The front door safe edge is rendered inoperative.
Troubleshooting:
1. Check for abnormal blockage or failure of the front door mechanical reopening device.
2. Related inputs:
FrontSafeEdge: Normally low
Global Parameter Update, Reset Controller, PARAM CHNG-RESET CAR
Description: This message indicates that all of the controller parameters have been updated and it is neces-
sary to reset the controller once the update is completed (press the iBox COMPUTER RESET button).
Car Reaction: The car is not allowed to run until the parameter update has been completed and the computer
has been reset.
6-41
Troubleshooting
iControl Messages
Governor open, GOVERNOR OPEN
Description: The Gov input has dropped. Will also cause an Ascending Car Overspeed Fault and set the rope
gripper if running up.
Car Reaction: Emergency stop if running. The car is not allowed to run again until the problem is corrected.
Troubleshooting:
1. Check the GOV (Governor) input, connection, and function.
Governor Speed Reduction Switch Fault, GOV SPEED SWITCH FLT
Description: This fault is generated if the elevator is moving and the Governor Speed Reduction Switch input
goes low (expansion input assigned via iView under Motor and Drive).
Car Reaction: Emergency Stop
Troubleshooting: Verify the state of the Governor Speed Reduction Switch and input.
Group Communication Established
Description: The car has established communication with the main iCue dispatcher.
Group Communication Lost
Description: Communication with the main iCue dispatcher has been lost.
Car Reaction: The car establishes communication with the backup dispatcher car if one has been selected.
Otherwise the car goes into emergency dispatch mode if that operation is not bypassed via the hardware
override switch.
Troubleshooting: Check the group to car communication related connections and parameters.
Hall Call Bus n Failure, HALL CALL BUS n FAIL (n = 1 to 4)
Description: There is no power to the named hall call bus.
Car Reaction: No response to calls from the affected floor.
Troubleshooting:
1. Check bus fuses and connections.
2. Test associated hall call bus driver.
Hall Call Bypass Input OFF (see Hall Call Bypass Input ON)
Hall Call Bypass Input ON, HALL CALL BYPASS INP.
Description: Discrete input used to bypass hall calls.
Car Reaction: The car takes itself out of hall call service. Hall calls remain registered until answered. The car
is also not eligible for parking
Troubleshooting: Check the related discrete inputs.
Hall Call Service Disabled
Description: The car is rejecting hall calls (iBox IN GROUP indicator is Off and the Hall call reject status LED
on the iView Diagnostics > Diagnostic Outputs > Car Operation tab is On) either because of the current
mode of operation (Inspection, Test, Independent service, all Call) or because of a fault condition.
Car Reaction: Hall calls are rejected.
Troubleshooting:
1. Verify that the car is not on a mode of operation in which hall calls are not accepted.
2. Check the iView Faults text box and Event Log for faults that would cause the car to reject hall calls.
3. If the car is not responding to hall calls, but neither 1 or 2 apply, the problem could be due to loss of
communication with the dispatcher, security settings, heavy load status or hall call system malfunction.
Hall Call Service Enabled
Description: The car is accepting hall calls (iBox IN GROUP indicator is On). See also, Hall Call Service Dis-
abled.
iControl Messages
Heat Detectors Recall Activated, HEAT DETECTORS RECALL
Description: A heat detector input has been activated.
Car Reaction: A car that is parked at a floor will open its doors and shut down. A car in motion will proceed in
the current direction to the next available floor where the heat detector is not tripped. If all heat detectors in
the current direction are tripped, the car will reverse direction and proceed to the first floor where the heat
detector is not tripped. If again all heat detectors are tripped, the car shall proceed to the main fire recall
floor. Once the car is stopped at a floor it shall automatically open its doors and shut down. Please refer to
Car Operation - Heat Detectors on page 9-89.
Heat Detectors Recall Complete
Description: Indicates that the car has completed the Heat Detectors Recall operation (reached a floor and
doors are fully open).
Car Reaction: The car remains shut down until all heat detector inputs have been deactivated (see Heat
Detectors Recall Deactivated).
Heat Detectors Recall Deactivated
Description: All heat detector inputs are deactivated.
Car Reaction: The car is allowed to run.
Heat Sensor Fault n (n = 2 to 4)
Description: Not currently used.
Hoistway Access Disabled, HA INSP. DISABLED
Description: Hoistway access inspection operation has been disabled.
Car Reaction: The car cannot be run on hoistway access inspection operation.
Troubleshooting:
1. Check for any car status that might prevent hoistway access operation, e.g. earthquake.
2. Check for the Stuck Inspection Input Fault.
3. Check all inspection buttons (Enable, Up, Down) and verify that none are stuck in the ON position.
Hoistway Access Enabled
Description: Hoistway access inspection operation which was previously disabled is now enabled.
Hoistway Access Inspection Operation, Hoistway Access Operation, Hoistway Access
Description: Car is on Hoistway access (enabled by the Hoistway access switch).
Car Reaction: If running, the car will make an emergency stop and is taken out of normal service. Under this
mode of operation, car can only be moved manually using the access key switches.
Troubleshooting: 6
1. Related inputs:
HoistwayAccess: Normally high
Hoistway Door Bypass, HOISTWAY DOOR BYPASS
The Hoistway Door Bypass switch on the iBox is in the Bypass position. (View-only on iView Safety screen,
enabled/disabled by MCE according to safety jurisdiction.) The ability to set this bypass must be enabled at
the factory and is only available if allowed by safety regulations in your area. Check the iView Safety Config-
uration screen to see if the feature is enabled in your installation.
Description:
Car Reaction: The car is placed in Inspection mode. To move the car, you must place it in either cartop or
car panel inspection mode. No other modes of operation are allowed.
6-43
Troubleshooting
iControl Messages
Hoistway Heat Detectors Activated, HOIST HEAT DETECTORS
Description: The hoistway heat detector input is activated. The fire warning light will flash until all heat
detectors have been reset. The fire-warning buzzer will sound until the car is shutdown at a floor.
Car Reaction: A car that is parked at a floor will open its doors and shut down. A car in motion will proceed in
the current direction to the next available floor where the heat detector is not tripped. If all heat detectors in
the current direction are tripped, the car will reverse direction and proceed to the first floor where the heat
detector is not tripped. If again all heat detectors are tripped, the car will proceed to the main fire recall floor
unless the car is also on Fire Service, in which case the car will proceed to the appropriate fire recall floor.
Once the car is stopped at a floor it will automatically open its doors and shut down. Then, if the machine
room or hoistway heat detectors are active, a signal is provided to disconnect the main power line and/or
activate the sprinklers where available. Please refer to Car Operation - Heat Detectors on page 9-89.
Car Reaction:
Hoistway Heat Detectors Deactivated
Description: The hoistway heat detector input is deactivated.
Car Reaction: The car is allowed to run.
HOISTWAY LEARN ON
Description: This status message, on the iBox display, indicates that the system is ready to perform the
hoistway learn operation.
IMP Switch Fault - Car Door Bypass, IMP SW FLT:C DOOR BP
Description: There is a problem with the iBox CAR DOOR BYPASS switch. Both poles must activate.
Car Reaction: None
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
IMP Switch Fault - Emergency Stop, IMP SW FAULT: EM STOP
Description: There is a problem with the iBox CONTROLLER STOP switch. Both poles must activate.
Car Reaction: If stopped, the car is immediately shut down and taken out of service for all types of demands,
including fire and medical emergencies. If the switch fault is detected while running, the car is allowed to
reach its next destination before shutting down.
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
IMP Switch Fault - Fault Bypass, IMP SW FAULT: FLT BYP
Description: There is a problem with the iBox FAULT/FUNCTION BYPASS switch. Both poles must activate.
Car Reaction: None
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
IMP Switch Fault - Hoistway Door Bypass, IMP SW FLT: H DOOR BP
Description: There is a problem with the iBox HOISTWAY DOOR BYPASS switch. Both poles must activate.
Car Reaction: None
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
iControl Messages
IMP Switch Fault - Inspection, IMP SW FAULT: INSP
Description: There is a problem with the iBox INSPECTION switch. Both poles must activate.
Car Reaction: If stopped, the car is immediately shut down and taken out of service for all types of demands,
including fire and medical emergencies. If the switch fault is detected while running, the car is allowed to
reach its next destination before shutting down.
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
IMP Switch Fault - Inspection DOWN, IMP SW FAULT: INSP DN
Description: There is a problem with the iBox Inspection DOWN switch. Both poles must activate.
Car Reaction: None
IMP Switch Fault - Inspection Enable, IMP SW FAULT: INSP EN
Description: There is a problem with the iBox Inspection ENABLE switch. Both poles must activate.
Car Reaction: None
IMP Switch Fault - Inspection UP, IMP SW FAULT: INSP UP
Description: There is a problem with the iBox Inspection UP switch. Both poles must activate.
Car Reaction: None
IMP Switch Fault - Learn, IMP SW FAULT: LEARN
Description: There is a problem with the iBox LEARN switch. Both poles must activate.
Car Reaction: None
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
IMP Switch Fault - None
Description: This message is generated when an IMP switch fault has occurred and is then cleared. If multi-
ple switch faults occur at the same time, the message is generated when all faults have been cleared.
Car Reaction: If the car had been shut down due to the IMP switch faults, it is cleared to run again.
IMP Switch Fault - Test, IMP SW FAULT: TEST
Description: There is a problem with the iBox TEST switch. Both poles of this switch must activate.
Car Reaction: None
Troubleshooting: 6
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
IMP Switch Fault - Write Enable, IMP SW FLT: WRITE EN
Description: There is a problem with the iBox WRITE ENABLE switch. Both poles must activate.
Car Reaction: None
Troubleshooting:
1. Sometimes the switch fault can be temporarily cleared by toggling the switch multiple times.
2. The iBox slide switches can be repaired using MCE part: IMP-SW-JUMPER-KIT.
Independent Service, Independent Svc
Description: Indicates that the Independent Service switch has been activated.
Car Reaction: Car and door operation in accordance to user-defined settings for independent service. (iView/
Car Operation/Independent Service.) Car does not respond to hall calls.
Troubleshooting:
1. If reported in error, check the Independent Service switch and wiring.
6-45
Troubleshooting
iControl Messages
Inspection Operation, Inspection
Description: The car is operating in Inspection mode.
Car Reaction: One of the inspection modes (in-car, machine room, or cartop) is active. The car will operate
using the Inspection performance pattern.
Inspection Overspeed Fault
Description: While operating in Inspection mode, the car exceeded the Inspection Overspeed setting on the
iView Safety Configuration screen.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. If reported in error, check the Inspection Overspeed setting on the Safety Configuration screen.
3. Check the iView event log for any events immediately preceding the overspeed fault.
4. Determine and correct the cause of the overspeed.
Insufficient Brake Feedback Fault, INSFCNT BRK FDBK FLT
Description: Brake current feedback is abnormally low.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check DB-25 connector from iField module to iBox is seated properly.
2. Check power supply on brake iField module.
3. Verify all wiring connections on the brake (BK) contactors are properly terminated and conducting.
4. Verify brake voltage parameters.
5. Verify iField Module setting for terminals FMCI and FMHC. Please refer to IFIELD-MODULE Terminals on
the ICE-FMP Board (Brake Module) on page 6-95.
6. Verify that the brake is properly calibrated. Please refer to Brake Calibration on page 2-57. Please refer
to Brake Parameter Adjustments on page 4-24.
7. Check Brake voltage on the Operational Status tab. If the value goes below 0.00 volts, and/or the drive
offset (Input ADC) was recently calibrated or adjusted, verify / set the Input ADC = 0.0 on the Configu-
ration > Drive > Calibration tab.
Insufficient Motor Field Feedback Fault, INSFCNT MF FDBK FLT
Description: Indicates that Motor Current Feedback signal is less than 50% of the commanded field current.
Car Reaction: If detected four times over seven runs the car will shut down.
Troubleshooting:
1. Check motor field AC supply off isolation transformer.
2. Check connections from controller to motor.
3. Check connections to iField motor module.
4. Check for open fuses.
5. Recalibrate motor field.
Insufficient Motor Field Forcing Feedback Fault, INSFCNT MF FORCNG FLT
Description: Motor field voltage is inadequate. DC motors only.
Troubleshooting:
1. Verify motor field voltage parameters.
2. The motor field may be improperly calibrated. Check settings (iView Motor Configuration screen).
3. Recalibrate motor field if necessary.
Invalid Configuration BALRQ, INVALID CNFG BALRQ
Description: Bottom Access Landing Rear Qualifier. The safety system has detected the improper use of
BALRQ option on the iView safety configuration screen.
Car Reaction: Safety OK status remains off.
Troubleshooting:
1. Check that the Safety Configuration, Bottom Access Landing Rear option is properly set.
iControl Messages
Invalid Configuration Input, INVALID CNFG INPUT
Description: An invalid input was discovered when cross checking safety inputs against safety configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check car setup/wiring against Safety Screen configuration.
2. Press Fault Reset to clear.
3. Re-learn Safety Configuration. Please refer to Setup - Safety - Configuration Tab on page 9-166.
Invalid Configuration Input Off (See: Invalid Configuration Input)
Invalid Configuration Input CTEX, INVLD CNFG INPUT CTEX
Description: Cartop Emergency Exit. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DCAB, INVLD CNFG INPUT DCAB
Description: Door Close Access Bottom. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DCAT, INVLD CNFG INPUT DCAT
Description: Door Close Access Top. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DCMS, INVLD CNFG INPUT DCMS 6
Description: Door Close Main String. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DCMS R, INV CNFG INPUT DCMS R
Description: Door Close Main String Rear. The safety system detected an input/safety setting difference
when cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
6-47
Troubleshooting
iControl Messages
Invalid Configuration Input DLAB, INVLD CNFG INPUT DLAB
Description: Door Lock Access Bottom. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DLAT, INVLD CNFG INPUT DLAT
Description: Door Lock Access Top. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DLMS, INVLD CNFG INPUT DLMS
Description: Door Lock Main String. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DLMS R, INV CNFG INPUT DLMS R
Description: Door Lock Main String Rear. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DPM, INVLD CNFG INPUT DPM
Description: Door Position Monitoring. The safety system detected an input/safety setting difference when
cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Input DPM_R, INV CNFG INPUT DPM_R
Description: Door Position Monitoring Rear. The safety system detected an input/safety setting difference
when cross checking inputs against configuration.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
iControl Messages
Invalid Configuration TALRQ, INVALID CNFG TALRQ
Description: Top Access Landing Rear Qualifier. The safety system detected an input/safety setting differ-
ence when cross checking inputs against configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify car setup/wiring matches the Safety screen setting for the option.
2. Press Fault Reset to clear.
3. Re-learn the Safety Configuration.
Invalid Configuration Inventory Cross Check BALRQ,INV INVTRY XCHK BALRQ
Description: Bottom Access Landing Rear Qualifier. The safety system detected a configuration/inventory
(board complement) difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any rear door options require a rear door board be attached to the safety expansion bus. Like-
wise, a rear door board attached to the safety expansion bus requires at least one rear door option be
selected on the Safety Configuration (Setup > Safety > Configuration tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
Invalid Configuration Inventory Cross Check DCCOR, INV INVTRY XCHK DCCOR
Description: Door Close Contact Rear. The safety system detected a configuration/inventory (board comple-
ment) difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any rear door options require a rear door board be attached to the safety expansion bus. Like-
wise, a rear door board attached to the safety expansion bus requires at least one rear door option be
selected on the Safety Configuration (Setup > Safety > Configuration tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
6
4. Reset the fault (press the iBox FAULT RESET button).
Invalid Configuration Inventory Cross Check NMS R, INV INVTRY XCHK NMS R
Description: No Main String Rear. The safety system detected a configuration/inventory (board complement)
difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any rear door options require a rear door board be attached to the safety expansion bus. Like-
wise, a rear door board attached to the safety expansion bus requires at least one rear door option be
selected on the Safety Configuration (Setup > Safety > Configuration tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
6-49
Troubleshooting
iControl Messages
Invalid Configuration Inventory Cross Check RD Board, INV INVTRY XCHK RD BD
Description: Rear Door board. The safety system detected a configuration/inventory (board complement)
difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any rear door options require a rear door board be attached to the safety expansion bus. Like-
wise, a rear door board attached to the safety expansion bus requires at least one rear door option be
selected on the Safety Configuration (Setup > Safety > Configuration tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
Invalid Configuration Inventory Cross Check RDOPT, INV INVTRY XCHK RDOPT
Description: Rear Door Option. The safety system detected a configuration/inventory (board complement)
difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any rear door options require a rear door board be attached to the safety expansion bus. Like-
wise, a rear door board attached to the safety expansion bus requires at least one rear door option be
selected on the Safety Configuration (Setup > Safety > Configuration tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
Invalid Configuration Inventory Cross Check RG Board, INV INVTRY XCHK RG BD
Description: Rope Gripper board. The safety system detected a configuration/inventory (board complement)
difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any emergency brake options require an emergency brake board be attached to the safety
expansion bus. Likewise, a emergency brake board attached to the safety expansion bus requires at
least one emergency brake option be selected on the Safety Configuration (Setup > Safety > Configura-
tion tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
iControl Messages
Invalid Configuration Inventory Cross Check RGOPT, INV INVTRY XCHK RGOPT
Description: Rope Gripper Option. The safety system detected a configuration/inventory (board comple-
ment) difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any emergency brake options require an emergency brake board be attached to the safety
expansion bus. Likewise, a emergency brake board attached to the safety expansion bus requires at
least one emergency brake option be selected on the Safety Configuration (Setup > Safety > Configura-
tion tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
Invalid Configuration Inventory Cross Check TALRQ, INV INVTRY XCHK TALRQ
Description: Top Access Landing Rear Qualifier. The safety system detected a configuration/inventory (board
complement) difference when cross checking board complement against system configuration.
Car Reaction: Safety OK remains off.
Troubleshooting:
1. Verify that the Configuration settings on the Setup > Safety > Configuration tab match the car options/
wiring. Any rear door options require a rear door board be attached to the safety expansion bus. Like-
wise, a rear door board attached to the safety expansion bus requires at least one rear door option be
selected on the Safety Configuration (Setup > Safety > Configuration tab).
2. If the safety configuration is incorrect, make appropriate changes and re-learn the new configuration
using the Learn operation on the Setup > Safety > Configuration tab.
3. Re-learn the inventory of boards using the Inventory Learn procedure on the Setup > Safety > Inventory
tab.
4. Reset the fault (press the iBox FAULT RESET button).
Invalid Destination, INVALID DESTINATION
Description: The car has been assigned to a destination floor that does not have an opening.
Car Reaction: Car ignores the demand.
Troubleshooting: Check the current mode of operation and check the corresponding recall floor and verify
that the floor is set to a floor with an opening. 6
Invalid Front Door Position, INVLD FRONT DOOR PSTN
Description: The front door inputs are in an invalid state (i.e.: doors open and closed at the same time).
Car Reaction: Car is taken out of service and doors will stall.
Troubleshooting:
1. Check all the front door inputs and wiring.
2. Related inputs:
FrontDoorCloseLimit: Low when the doors are fully closed
FrontDoorPositionMonitoring: High when the doors are fully closed
FrontDoorOpenLimit: Low when doors are fully open
FrontCarGate: High when doors are fully closed
Invalid Input (See: Invalid Configuration Input)
6-51
Troubleshooting
iControl Messages
Invalid Rear Door Position, INVLD REAR DOOR PSTN
Description: The rear door inputs are in an invalid state (i.e., doors open and closed at the same time).
Car Reaction: Car is taken out of service and doors will stall.
Troubleshooting:
1. Check all the rear door inputs and wiring.
2. Related inputs:
RearDoorCloseLimit: Low when the doors are fully closed
RearDoorPositionMonitoring: High when the doors are fully closed
RearDoorOpenLimit: Low when doors are fully open
RearCarGate: High when doors are fully closed
IO Map Compare Fault, IO MAP COMPARE FAULT
Description: Safety A IO Map did not match Safety B IO Map.
Car Reaction: If running, car makes an emergency stop. Car is not allowed to run.
Troubleshooting:
1. Press the Fault Reset button to clear the fault.
2. If problem persists it is an indication that the iBox may need to be replaced. Consult MCE Technical Sup-
port for instructions.
IO Map Compare Fault Off (See: IO Map Compare Fault)
IO Map Compare Long Term Fault, IO MAP COMPARE LT FLT
Description: Safety A long term products did not match Safety B long term products for 1.2 seconds.
Car Reaction: If running, car makes an emergency stop. Car is not allowed to run.
Troubleshooting:
1. Press the Fault Reset button to clear the fault.
2. If problem persists it is an indication that the iBox may need to be replaced. Consult MCE Technical Sup-
port for instructions.
IO Map Toggle Compare Fault, IO MAP TOGLE COMP FLT
Description: The failure of a safety input was detected during the input toggle test (performed at the end of
each run). This test verifies the proper operation of safety system inputs that normally remain unchanged
during the course of elevator operation.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Press the Fault Reset button to clear the fault.
2. If problem persists it is an indication that the iBox may need to be replaced. Consult MCE Technical Sup-
port for instructions.
IO Map Toggle Compare Fault Off (See: IO Map Toggle Compare Fault)
iView Logged Off. Passenger operation. A previously active iView connection to the controller has logged
off.
iView Logged On. Passenger operation. An iView user has logged on to the controller.
iView Lost Connection. An iView connection has been dropped.
iView Timed Out. An iView connection was inactive for a period of time beyond the idle time-out and has
been disconnected.
iControl Messages
Landing System Sensor Fault, LAND SYS SENSOR FAULT
Description: This fault is generated when a ULM or DLM sensor is activated while the car is running and is
away from a floor. It can also be generated if the M contactor is ON (car is commanded to run) and the safety
system sees a door zone magnet for more than 16 inches of single direction travel.
Car Reaction: Emergency Stop. Motor and brake contactors immediately dropped.
Troubleshooting:
1. Press Fault Reset to clear.
2. If allowed, set Contactor Drop Delay Time to 0.9 seconds.
3. Check for stuck door zone sensor input (front or rear).
LCD Fault
Description: This fault is generated if the controller gets a not ready state from the LCD. This can happen if
the iBox LCD is not connected properly or, with some LCD models, if the contrast is set to far to an extreme.
Car Reaction: None. The fault is simply an indication to adjust or replace the iBox LCD.
Troubleshooting:
1. Check the iBox Onboard Display LCD. If the LCD is blank or frozen, adjust the contrast dial to midpoint.
2. If the display looks corrupted, press the iBox Computer Reset button.
Learn Switch Timed Out Fault, LEARN SW TIMED OUT
Description: When the Learn Switch is ON for more than 15 minutes, the car will shut down.
Car Reaction: The car is not allowed to restart after the current run is completed.
Troubleshooting:
1. Turn OFF the iBox Learn switch.
2. If more time is needed in the Learn mode, then turn the Learn switch back ON to reset the fifteen minute
timer.
Learn U/DNT1-5 and U/DETS Positions, LEARN U/DTS POSITIONS
Description: The positions for the normal and emergency terminal limit switches have not been learned.
Car Reaction: The elevator can only be run on Inspection or Test modes.
Troubleshooting: Perform the normal and emergency terminal limit switches learn operation (Learn tab on
the iView Terminal Switches Configuration screen)
Learn U/DNT1-5 and U/DETS Speeds, LEARN U/DTS SPEEDS
Description: The speeds for the normal and emergency terminal limit switches have not been learned.
Car Reaction: The elevator can only be run on Inspection or Test modes.
Troubleshooting: Perform the normal and emergency terminal limit switches learn operation (Learn tab on 6
the iView Terminal Switches Configuration screen)
Learning empty load values, LEARNING EMPTY LOAD
Description: Empty car load learn calibration has been initiated.
Car Reaction: Car will start load learn process.
Learning full load values, LEARNING FULL LOAD
Description: Full car load learn calibration has been initiated.
Car Reaction: Car will start load learn process.
6-53
Troubleshooting
iControl Messages
Light Load Anti-nuisance
Description: Light load anti-nuisance operation. The load in the car is less than the programmed Light Load
Threshold value.
Car Reaction: Under these conditions, an anti-nuisance feature (if enabled) will limit the number of car calls
registered. Should the number of registered car calls exceed the programmed limit, all car calls will be can-
celed.
Troubleshooting:
1. If this message appears to be displayed in error, verify the programmed Light Load Threshold value.
(Adjust if needed on the Load Weigher Configuration screen.)
2. Verify the user-defined number of car calls allowed if the car load is less than the Light Load Threshold.
Please refer to Car Operation - Passenger Tab on page 9-40.
3. Evaluate whether or not the load in the car is less than the Light Load Threshold value. Calibrate the load
weigher if necessary.
4. For discrete input load weighers, check the Light Load input shown on the job prints.
Limit Switches Checksum Fault, LIMIT SW CHKSUM FAULT
Description: The learned ETS and NTS limit switch speed values have an Invalid Checksum in nonvolatile
memory. A checksum is a means of validating data that has been stored in nonvolatile memory. An invalid
checksum means that the data stored may not be reliable.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Relearn the Hoistway limit switches.
2. Use the Default option on the Terminal Switch learning screen.
Limit Switches Learn Fault, LIMIT SW LEARN FAULT
Description: Safety Processor A experienced a failure when storing learned limit switch speed values to non-
volatile memory.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Press the Fault Reset button to clear the fault.
2. If problem persists, consult MCE Technical Support.
Load calibration on, LOAD CALIBRATION ON
Description: Load learn calibration has been initiated.
Car Reaction: Car will start load learn process.
Load learn process activated. See Load Calibration On.
Load learn process deactivated
Lobby Peak Mode, LOBBY PEAK MODE
Description: The elevator is operating in lobby peak mode, favoring traffic coming from the lobby.
Local / Dispatcher Activated, LOCAL DISPATCHER
Description: Communication with the central or local dispatcher has been lost or not established. This car
controller is acting as the Local / Dispatcher.
Car Reaction: The car establishes communication with all of the other cars in the group and starts perform-
ing the dispatching functions.
Troubleshooting: Check the system communication related connections and parameters.
Local / Dispatcher Deactivated
Description: This car is no longer performing the dispatching functions.
iControl Messages
Loss of Position or Speed Indicators, LOSS OF POS/SPD IND
Description: The speed feedback signal used to compare with the position feedback signal is not being seen
properly or is not properly calibrated. This can be caused by a loss of traction.
Car Reaction: Emergency Stop. Latched fault.
Troubleshooting:
1. If this is an iControl with DC Drive using an encoder for speed feedback, this fault could indicate a mal-
functioning encoder.
2. On the iView oscilloscope (or a DVM connected between STP1 and STP2), compare Pattern Command
and Speed Feedback readouts. They must match within 0.050 VDC while the car is running at steady
state speed. If not, adjust the TACH ADJ trimpot. Please refer to Calibrating Actual Car Speed on
page 2-62.
3. Use a hand-held tachometer to verify car speed.
4. Run the car on inspection and check the speed displayed on the iBox display.
Mac Address Error, MAC ADDRESS ERROR
Description: The iBox has detected that one of its three MAC addresses has been defaulted or set to zero.
This could lead to multiple cars having the same MAC address, which will cause network problems.
Car Reaction: None.
Troubleshooting: Remove the iBox front cover. On the iBox OBD select Car > View Factory Data > MAC
Addresses. Verify that the MAC addresses displayed on the LCD match the addresses on the barcode stickers
on the ICE-IMP board. Make corrections if necessary.
Machine Room Heat Detectors Activated, MR HEAT DETECTORS
Description: The machine room heat detector input is activated. The fire warning light will flash until all heat
detectors have been reset. The fire-warning buzzer will sound until the car is shutdown at a floor.
Car Reaction: A car that is parked at a floor will open its doors and shut down. A car in motion will proceed in
the current direction to the next available floor where the heat detector is not tripped. If all heat detectors in
the current direction are tripped, the car will reverse direction and proceed to the first floor where the heat
detector is not tripped. If again all heat detectors are tripped, the car will proceed to the main fire recall floor
unless the car is also on Fire Service, in which case the car will proceed to the appropriate fire recall floor.
Once the car is stopped at a floor it will automatically open its doors and shut down. Then, if the machine
room or hoistway heat detectors are active, a signal is provided to disconnect the main power line and/or
activate the sprinklers where available. Please refer to Car Operation - Heat Detectors on page 9-89.
Car Reaction:
Machine Room Heat Detectors Deactivated
Description: The machine room heat detector input is deactivated. 6
Car Reaction: The car is allowed to run.
Machine Room Inspection Disabled, MR INSP. DISABLED
Description: Machine room inspection operation has been disabled.
Car Reaction: The car cannot be run on machine room inspection operation.
Troubleshooting:
1. Check for any car status that might prevent machine room inspection operation, e.g. earthquake.
2. Check for the Stuck Inspection Input Fault.
3. Check all inspection buttons (Enable, Up, Down) and verify that none are stuck in the ON position.
Machine Room Inspection Enabled
Description: Machine room inspection operation which was previously disabled is now enabled.
6-55
Troubleshooting
iControl Messages
Machine Room Inspection Operation, Machine Rm Inspection, Mach Rm Insp
Description: Car placed in Machine Room Inspection operation using the iBox Inspection switch.
Car Reaction: Car begins operating in Inspection mode. If running, the car will make an emergency stop and
is taken out of normal service. Under this mode of operation, car can only be moved manually using the iBox
Inspection Up and Down switches.
Troubleshooting:
1. Related inputs:
MachineRoomInspection: Normally high
Machine Room Stop Switch Open, MR STOP SWITCH OPEN
Description: The machine room stop switch input has dropped.
Car Reaction: Emergency stop if running. The car is not allowed to run until the problem is corrected.
Troubleshooting:
1. Check the Machine Room stop switch on the front panel of the iBox.
Main Floor Smoke Sensor Recall, MAIN FLOOR SMOKE
Description: Recall to the alternate fire floor due to active or latched smoke detector inputs from the main
floor.
Car Reaction: Car proceeds to the user-defined alternate fire recall floor. Once at the recall floor, door opera-
tion is according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. If in error, inspect the sensor input and connections.
2. Related Inputs: Main floor smoke and fire sensors as indicated on job print drawing(s) -1.
Motion Start Fault, MOTION START FAULT
Description: Car initiated movement but was unable to start for more than ten seconds.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Determine mechanical or other reason car is unable to start.
Motion stopped due to IO toggle test, MOTION STOPPED-IO TST
Description: iBox requested start of motion while a toggle test was being performed.
Car Reaction: None. iBox will resend request.
Troubleshooting: NA
Motor Contactor Driver Proofing Fault, MOTR CNTR DRV PRF FLT
Description: Fault signal for motor contactor driver proofing circuits.
Car Reaction: None
Troubleshooting:
1. Verify motor contactor driver proofing circuits.
2. Check the coil of the motor contactor.
Motor Contactor Proofing Fault, MOTOR CNTR PROOF FLT
Description: Fault signal for motor contactor proofing circuits.
Car Reaction: None
Troubleshooting:
1. Verify motor contactor proofing circuits.
Motor Field Forcing Timed Out, MF FORCING TIMED OUT
Description: DC motors only. The motor field was being forced for over 1 minute.
Car Reaction: Stop the run. Restart.
Troubleshooting:
1. The motor field starts forcing if there is a demand and the doors are closing. Check that the doors are
not obstructed and/or that passengers are not holding the doors open past the 1 minute limit.
iControl Messages
Motor Limit Protection Timer Elapsed, MOTOR LMT TIMED OUT 2
Description: A fault is generated is the system requests movement for more than ten minutes but no move-
ment is detected.
Car Reaction: Currently for informational purposes only.
Motor Limit Timed Out, MOTOR LIMIT TIMED OUT
Description: Generated if no other fault has been generated and the system has attempted to move the car
for three minutes with no movement detected or has detected only minimum movement for ten minutes.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. Cancel all calls.
Troubleshooting:
1. Check that Pattern Scaling is not set to 0.0.
2. Check Contract Speed is correctly set.
3. Check pattern voltage to drive (0 - 10V) with meter.
Nudging Front, NUDGING FRONT
Description: This event is logged when front door nudging operation is invoked.
Car Reaction: Front doors start closing at reduced speed and torque.
Nudging Operation
Description: The doors are operating in Nudging mode. (Passenger operation).
Nudging Rear, NUDGING REAR
Description: This event is logged when rear door nudging operation is invoked.
Car Reaction: Rear doors start closing at reduced speed and torque.
Other Cars Alternate Fire Sensor Recall, OTHER CARS ALT FIRE
Description: Alternate fire recall due to active or latched smoke detector input(s) from the hoistway or
machine room of other cars in the system.
Car Reaction: Car proceeds to the user-defined alternate fire recall floor. Once at the recall floor, door opera-
tion is according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. If in error, inspect the sensors, inputs, and connections.
2. Related Inputs: Other Cars Alt Recall sensor inputs as indicated on job prints.
Other Cars Main Fire Sensor Recall, OTHER CARS MAIN FIRE
Description: Main fire recall due to active or latched smoke detector input(s) from the hoistway or machine
room of other cars in the system.
Car Reaction: Car proceeds to the user-defined main fire recall floor. Once at the recall floor, door operation
6
is according to the user-defined door operation under fire recall operation.
Troubleshooting:
1. If in error, inspect the sensors, inputs, and connections.
2. Related Inputs: Other Cars Main Recall sensor inputs as indicated on job prints.
PARAM CHNG-RESET CAR, see Global Parameter Update, Reset Controller
Passenger Operation, Passenger. Normal operation status message.
Photo Eye Antinuisance
Description: This event is logged when car calls are canceled due to a user-defined number of car calls being
registered without interruption of the photo eye device.
Car Reaction: All car calls are cancelled.
Troubleshooting:
1. Check the user defined options related to the operation. (iView/Car Operation/Passenger/Anti Nuisance.)
2. Check the photo eye device and related inputs.
6-57
Troubleshooting
iControl Messages
Position Cartop Offset Fault, POSTN CARTP OFFST FLT
Description: Each time the car stops, it obtains position information from the cartop position encoder. If the
reported position varies from the position last reported at this location by more than two feet, this fault is
generated.
Car Reaction: Emergency stop. Motor and brake contactors immediately dropped.
Troubleshooting: Perform a Terminal Synchronization (Pattern Configuration screen>Common tab>Position
Synchronization.
Position Location Error Fault, POSTN LCTN ERROR FLT
Description: If the difference between the learned position of a floor (magnet) and the currently indicated
position of that floor (magnet) is greater than 2 feet, this fault is generated.
Car Reaction: Car will perform a terminal synchronization.
Troubleshooting:
1. Check that the iLand landing system is properly installed and adjusted. (Refer to Section 3 of this guide.)
Position Quadrature Fault, POSITION QUAD FAULT
Description: The quadrature signal from iLand is not being detected (one or both streams). When moving
above 30 fpm, the system expects to see proper transitions on both quadrature signals.This fault may be
bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop.
Troubleshooting:
1. Verify that both quadrature channels are arriving at the iBox.
2. On the Hoistway screen, verify that the absolute position increments when moving up and decrements
when moving down (on inspection). If absolute position does not change, there may be a problem with
the iBox.
Position Quadrature Reversed Fault, POSITN QUAD RVRSD FLT
Description: The arrival sequence of the quadrature pulse streams indicates travel in the opposite direction
of that requested by the system.
Car Reaction: None.
Troubleshooting:
1. Verify that the elevator moves in the requested direction.
2. On the Hoistway screen, verify that the cartop position increments when moving up and decrements
when moving down (on inspection).
3. On the Hoistway screen, verify that the absolute position increments when moving up and decrements
when moving down (on inspection).
Position Speed Deviation Fault, POSITN SPEED DVTN FLT
Description: The safety processor compares the distance travelled reported by the position quadrature with
the distance travelled according to motor rotation. If the quadrature reports 48 travelled but the motor
reports less than 32 travelled, this fault is generated. This fault may be bypassed on the Diagnostics > Fault
Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check velocity feedback from drive.
2. Check that Pattern Configuration/General tab Position Encoder Resolution is set to 256.
3. Check calibration of speed feedback signal.
iControl Messages
Position Speed Threshold Fault, POSTN SPD THRSHLD FLT
Description: The quadrature synthesized speed exceeds 115% of contract speed. This fault may be bypassed
on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. On the iView oscilloscope, compare Pattern Command and Speed Feedback to see that they match.
2. Use a hand-held tachometer to verify car speed.
3. Run the car on inspection and check the speed displayed on the iBox display.
4. For SCR drives, verify that the programmed running motor field is close to the actual motor field value
when running at contract speed. If the value is higher, the system will have to weaken the motor field as
the elevator reaches contract speed. If the motor field is very inductive, this may cause an overshoot. If
the value is too low, excessive current may flow through the armature. Note that load will affect this
value. Running in the up direction with a full load in the car will yield the worst-case scenario. For an
empty elevator, running in the down direction produces the worst-case scenario (the value will be higher
than for the fully loaded car.)
5. For highly inductive motor fields, begin motor field weakening earlier and end motor field weakening ear-
lier. If the begin weakening percentage is too low, poor control will result when the elevator is approach-
ing the destination floor (spotting). If this is the case, reduce the end weaken percentage without
modifying (by much) the begin weakening percentage. Generally, begin is recommended around 50%
while end is recommended around 90% for normal motor fields.
6. Reduce high roll jerk.
Position Synchronization Fault
Description: The system was not able to read the position correction value stored in battery backed RAM
when the controller powered up. This fault usually results in a floor sensor fault or a position location fault.
Car Reaction: None.
Troubleshooting:
1. Verify iBox battery connection and charge (lower left side of ICE-IMP board - iBox cover removed).
Battery type: 1/2 AA, 3.6V Lithium. Manufacturer: SAFT, part # LS14250. MCE part # 30-05-0001.
Position Synchronization Required at Floor, POSITION SYNC-FLOOR
Description: The elevator needs to verify position by crossing a door zone sensor.
Car Reaction: Cancel all existing calls, synchronize to floor.
Position Synchronization Required at Terminal, POSITION SYNC-TERMINAL
Description: The elevator does not know where it is. It needs to locate a terminal door zone sensor to estab-
lish position. 6
Car Reaction: Cancel all existing calls, synchronize to terminal.
Position Synchronized at Floor
Description: The elevator has completed synchronizing its position using a door zone sensor. See Position
Synchronization Required at Floor.
Car Reaction: Return to normal service.
Position Synchronized at Terminal
Description: The elevator has completed synchronizing its position using a terminal door zone sensor. See
Position Synchronization Required at Terminal.
Car Reaction: Return to normal operation.
Power Transfer Input Activated, Power Transfer, POWER TRANSFER
Description: Power transfer input activated. Power is being transferred from the emergency generator to
commercial service.
Car Reaction: Cancel existing calls. Stop at next floor and open doors.
Troubleshooting: Check the Power Transfer input.
Power Transfer Input Deactivated
6-59
Troubleshooting
iControl Messages
Power Up Position Synchronization Required at Terminal
Description: Position synchronization at a terminal landing required after power-up/reset. Terminal synchro-
nization after power-up will occur if the elevator was required to synchronize before power was lost or the
controller was reset, or if synchronization information in battery backed SRAM is invalid.
Car Reaction: The elevator will synchronize at a terminal landing.
Troubleshooting:
1. Battery may need to be changed.
2. Check for faulty SRAM.
3. Check for SRAM not correctly inserted in socket.
4. Check for faulty iBox.
Pre-start Door Lock Fault
Description: Once the decision to move the elevator has been made, three acknowledgments (motion start,
door lock and drive start) must be received before physical movement is allowed. However, if the system is
so configured, pre-start sequencing will begin while the doors are closing. If the door lock acknowledgement
is not received within 15 seconds (after the pre-start sequence is begun), this fault is generated.
Car Reaction: The pre-start sequence will stop and the sequence will repeat. If the fault persists, an exces-
sive restarts fault will occur.
Troubleshooting:
1. Verify that the doors (front and/or rear) become locked within the prescribed time.
2. Verify, via the iView Diagnostics - Motion tab, that the system sees the doors closing and becoming
locked within the prescribed time. The information reflects front and rear door status combined.
3. Verify, via the Diagnostics - Car Operation - Front/Rear tabs, that the system sees the front/rear doors
closing and becoming locked within the prescribed time.
Primary Fire Switch Bypass, PRI FIRE SWITCH BYP
Description: The primary fire switch is in the Bypass position.
Car Reaction: According to selected Fire Code.
Troubleshooting:
1. Check the primary fire recall switch inputs.
Primary Fire Switch On, PRI FIRE SWITCH ON
Description: The primary fire switch is in the On position.
Car Reaction: The car will recall to the Main fire recall floor, position its doors as directed on the Car Opera-
tion/Fire/Modify/Fire Recall screen, and wait for activation of the in-car firefighter switch.
Troubleshooting: If in error, check the Primary Fire Recall Switch input.
QPRAM Device Error, QPRAM DEVICE ERROR
Description: Safety Processor A problem writing to QPRAM device.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Replace QPRAM on Safety Processor A. Contact MCE.
Rear Auxiliary Door Open Button Bypassed, REAR AUX DOB BYP
Description: The rear auxiliary door open button has been continuously activated for a user-defined time and
is now bypassed according to the user defined setting (iView Controller > Configuration > Car Operation >
Doors).
Car Reaction: The rear auxiliary door open button is rendered inoperative.
Troubleshooting:
1. Check the corresponding input: Rear Auxiliary Door - Open Button (Normally low).
2. The operation of the door open button can also be restored by setting the Door open button bypass
option to off (unchecked) (iView Controller > Configuration > Car Operation > Doors).
iControl Messages
Rear Door Close Fault, REAR DOOR CLOSE FAULT
Description: One or more rear door failures to close have been detected. The controller will attempt to close
the doors as defined by user parameters (door close protection timer and number of attempts) before
declaring this fault. (iView Controller > Configuration > Car Operation > Doors).
Car Reaction: The doors will reopen fully. All car calls are canceled and car removes itself from hall call ser-
vice (hall calls assigned to this car are canceled or reassigned to other cars if available). Doors may be closed
using constant pressure on the rear door close button.
Troubleshooting:
1. Door closed status is determined by the rear door close limit and by the rear door position monitor con-
tact if applicable.
2. Check the wiring of these signals.
3. Check the door close protection timer and number of closing attempts on the Operation/Doors tab.
Rear Door Close Fault Recovery Failure, R DR CLS FLT REC FAIL
Description: The Door Close Fault Recovery timer starts when a Door Close Fault is generated. When the
timer expires, the Door Close Fault is cleared to allow the doors to again attempt to close (see Rear Door
Close Fault). This is repeated the number of times specified by the Door Close Fault Recovery Attempts
parameter. If the doors have failed to close when the number of attempts equals the recovery attempts
parameter setting, the Rear Door Close Fault Recovery Failure is generated.
Car Reaction: The car is not allowed to run until a mode change is detected or the doors are successfully
closed via constant pressure on the Door Close Button.
Troubleshooting:
1. Door closed status is determined by the rear door close limit and by the rear door position monitor con-
tact if applicable. Check the wiring of these signals.
2. Check the door close protection timer and number of closing attempts on the Car Operation - Doors tab.
Rear Door Close Time-out
Description: A failure of the rear door to close has been detected. The controller will attempt to close the
doors for a period of time defined by the Closing protection timer parameter (Door Motor Protection Timers).
If the timer elapses prior to the doors closing fully, this event is generated.
Car Reaction: Doors reopen fully and again attempt to close.
Troubleshooting:
1. Door closed status is determined by the rear door close limit and by the rear door position monitor con-
tact if applicable.
2. Check the wiring of these signals.
3. Check the Closing protection timer (iView Controller > Configuration > Car Operation > Doors). 6
Rear Door Contact Fault, REAR DOOR CONTCT FLT
Description: A faulty rear door contact (gate switch, door lock) has been detected. This is detected when the
doors are in their fully open position and either the gate switch contact is closed or the doors appear to be
locked.
Car Reaction: All car calls are canceled and the car removes itself from hall call service. The rear doors are
not allowed to close and the car is not allowed to run.
Troubleshooting:
1. Check the rear door gate switch and door lock contact at the floor at which the car is located.
2. Check associated wiring for these signals.
6-61
Troubleshooting
iControl Messages
Rear Door Open Button Bypassed, REAR DOB BYPASSED
Description: The rear door open button has been continuously activated for a user-defined time and is now
bypassed according to the user defined setting. (iView Controller > Configuration > Car Operation > Doors).
Car Reaction: The rear door open button is rendered inoperative.
Troubleshooting:
1. Check the corresponding input: Rear Door - Open Button (Normally low).
2. The operation of the door open button can also be restored by setting the Door open button bypass
option to off (unchecked) (iView Controller > Configuration > Car Operation > Doors).
Rear Door Open Fault, REAR DOOR OPEN FAULT
Description: One or more rear door failures to open fully have been detected. After repeated attempts to
open the door (as specified by user parameters), a door open failure is declared. The amount of time allowed
for the door to open and the number of attempts made are user parameters.(iView Controller > Configura-
tion > Car Operation > Doors).
Car Reaction: The door stalls at its last position. Car calls are canceled and the car removes itself from hall
call service (hall calls assigned to this car are canceled or reassigned to other cars if available). Doors may
be moved via constant pressure on the door open and door close buttons.
Troubleshooting:
1. The door open status is determined by the rear door open limit status.
2. Check the wiring of this signal.
3. Check the door open protection timer and number of open attempts (iView Controller > Configuration >
Car Operation > Doors).
Rear Door Open Time-out
Description: A failure of the rear door to open has been detected. The controller will attempt to open the
doors for a period of time defined by the Opening protection timer parameter (Door Motor Protection Tim-
ers). If the timer elapses prior to the doors opening fully, this event is generated.
Car Reaction: The door open cycle is halted and the door is allowed to reclose. If so configured, repeated
attempts will be made to open the door. Otherwise, the car is allowed to leave the landing once the doors are
closed.
Troubleshooting:
1. Door open status is determined by the rear door open limit and by the rear door position monitor contact
if applicable.
2. Check the wiring of these signals.
3. Check the Opening protection timer (iView Controller > Configuration > Car Operation > Doors).
Rear Doors Stopped, REAR DOORS STOPPED
Description: The Door Stop button or Emergency Stop switch was activated causing the doors to be pre-
vented from moving.
Car Reaction: The car is not allowed to move unless the doors are fully closed.
Troubleshooting: This condition can be cleared by activation of the Door Open button, Door Close button or if
the car goes into Inspection or Fire Service mode, provided that the Door Stop input is off.
Rear DPM Open-GS Closed, R DPM OPEN-GS CLOSED
Description: The rear door position monitoring contact is open while the gate switch is closed.
Car Reaction: None.
Troubleshooting: Check the rear door position monitoring contact, gate switch and all related circuitry.
iControl Messages
Rear Hall Door Open Button Bypassed, REAR HALL DOB BYP
Description: The rear hall door open button has been continuously activated for a user-defined time (Door
open bypass timer) and is now bypassed in accordance with the user-defined setting (iView Controller >
Configuration > Car Operation > Doors).
Car Reaction: The rear hall door open button is rendered inoperative.
Troubleshooting:
1. Check the corresponding input, Rear Door - Hall Door Open Button: Normally low.
2. The operation of the hall door open button can also be restored by setting the Door open button bypass
option to off (unchecked) (iView Controller > Configuration > Car Operation > Doors).
Rear Photo Eye Bypassed, REAR PHOTO EYE BYP
Description: The rear photo eye device has been continuously activated for a user-defined time and is now
bypassed in accordance to the user-defined setting. (iView/Car Operation/Passenger/Anti Nuisance.)
Car Reaction: The rear photo eye device is rendered inoperative.
Troubleshooting:
1. To restore the operation of the photo eye device, check the corresponding input.
2. Related inputs:
PhotoEyeRear: Normally low.
Rear Photo Eye Failure, REAR PHOTO EYE FAIL
Description: This event is logged when the photo eye is continuously activated for a predetermined time (4
seconds) while the rear doors are fully closed.
Car Reaction: The rear photo eye is rendered inoperative.
Troubleshooting:
1. Check for abnormal blockage or failure of the rear optical device.
2. Related inputs:
RearPhotoEye: Normally low.
Rear Safe Edge Bypassed, REAR SAFE EDGE BYP
Description: The rear door safe edge has been continuously activated for a user-defined time and is now
bypassed according to the user-defined setting. (iView Controller > Configuration > Car Operation > Doors).
Car Reaction: The rear safe edge is rendered inoperative.
Troubleshooting:
1. Check the state of the rear safe edge input.
2. Related inputs:
SafeEdgeRear: Normally low. 6
Rear Safe Edge Failure, REAR SAFE EDGE FAIL
Description: This event is logged when the rear door safe edge is continuously activated for a predetermined
time (4 seconds) while the rear doors are fully closed.
Car Reaction: The rear door safe edge is rendered inoperative.
Troubleshooting:
1. Check for abnormal blockage or failure of the rear door mechanical reopening device.
2. Related inputs:
RearSafeEdge: Normally low.
Receive Sys Params
Description: Indicates that this controller is receiving system parameters from the Central or Local / Dis-
patcher. (DO NOT RESET THE CONTROLLER).
6-63
Troubleshooting
iControl Messages
Restricted, RESTRICTED
Description: Indicates that this controller has been shipped with Restricted Mode enabled. The controller will
run in all modes of operation, but will not accept hall call assignments. Restricted mode can be terminated at
any time by entering the Restricted Mode Key as described in document 42-IS-0144, Restricted Mode
Instruction for iControl Users. Obtain the Restricted Mode Key by calling MCEs Credit Department at (916)
463-9582. When calling, please provide the controllers job number and car identifier.
R DR CLS FLT REC FAIL. See Rear Door Close Fault Recovery Failure
Retiring Cam Door Lock Fault Activated, Retiring Cam Door Lock Fault, RETIRING CAM DLK FLT
Description: The door locks have failed to make up within a pre-determined user-adjustable time after a user
adjustable number of attempts to lock the doors. This fault is detected on cars equipped with a retiring cam
door lock mechanism.
Car Reaction: Car is taken out of service and doors re-open fully. The doors can be closed with constant pres-
sure on the door close button.
Troubleshooting:
1. Check the door locks and the retiring cam circuitry.
2. Verify that the related user-defined parameters are correct.
3. This fault is cleared by any mode of operation change or if the doors are closed with constant pressure
on the door closed button.
Retiring Cam Door Lock Fault Deactivated. See Retiring Cam Door Lock Fault Activated
Retiring Cam Protection Fault Activated, Retiring Cam Protection Fault, RET CAM PROTECTIN FLT
Description: The retiring cam output has been activated for a pre-determined user-adjustable time after the
doors have successfully been locked. This fault is monitored in the event the car fails to reach its destination.
Car Reaction: Emergency stop if the car is traveling when the fault is detected. The car is taken out of ser-
vice. If the car is at a landing, the doors shall re-open fully.
Troubleshooting:
1. Check the door locks and the retiring cam circuitry.
2. Verify that the related parameters are correct.
3. This fault is cleared by any mode of operation change or by the iBox Fault Reset button.
Retiring Cam Protection Fault Deactivated. See Retiring Cam Protection Fault Activated
Sabbath Operation Activated, Sabbath Operation, SABBATH OPERATION. The elevator is operating in
Sabbath mode initiated by a software command, switched input or timer. Sabbath mode allows the elevator
to operate, serving the building without requiring buttons to be pressed for hall calls or car calls. Car behav-
ior is determined by parameters located on the Car Operation Configuration > Sabbath tab.
Sabbath Operation Deactivated. See Sabbath Operation Activated.
Safety A Contract Overspeed Fault, SPA COS FAULT
Description: The car has exceeded the Contract Overspeed setting (iView, Safety Configuration screen). This
fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency Stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. Check the contract overspeed parameter for proper setting (iView/Safety Configuration/General).
Safety A DETS Level 2 Speed Fault, SPA DETS L2 SPEED FLT
Description: The car contacted the Down Emergency Terminal Switch while traveling at over 95% of contract
speed. This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. Check for the proper positioning of the DETS switch in the hoistway.
iControl Messages
Safety A IMP Configuration Mismatch
Description: The parameters saved in the Safety system do not match the values saved in the main proces-
sor. When Safety screen parameters are changed, this message appears after the Send button is pressed.
Complete a Safety learn operation as directed on the iView Safety Configuration screen to learn the new
safety configuration.
Car Reaction: Car will not run.
Troubleshooting:
1. Using iView, check the values programmed under the Safety Configuration screen. Verify that they are
correct.
2. Download correct values to the Safety system by executing the learn process from the Safety screen.
Safety A Inspection Leveling Overspeed Fault, SPA LOS FAULT
Description: The car exceeded the leveling overspeed limit (detected by safety processor A). This fault may
be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to move again.
2. Check the leveling overspeed parameter for proper setting (iView/Safety Config/General).
Safety A Inspection Overspeed Fault, SPA IOS FAULT
Description: The car has exceeded the inspection overspeed limit of 150 fpm (detected by safety processor
A). This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to move again.
Safety A SIB Device Fault, SPA SIB DEVICE FAULT
Description: Safety Processor A has a problem writing Safety Ice Bus.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Replace iBox. SAF Board damaged. Contact MCE.
Safety A SIB Device Fault Off (See: Safety A SIB Device Fault)
Safety A UETS Level 2 Speed Fault, SPA UETS L2 SPD FLT
Description: The car contacted the Up Emergency Terminal Switch while traveling at over 95% of contract
speed.This fault may be bypassed on the Diagnostics > Fault Bypass tab. 6
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. Check for the proper positioning of the UETS switch in the hoistway.
Safety A Unintended Motion Fault, SPA UNTD MOTION FLT
Description: Safety processor A has detected that both hoistway doors and car gate doors were open as the
car moved away from the floor without a command from the iControl main processor (IMP board) to move.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. If applicable, the
rope brake drops.
Troubleshooting:
1. Check for proper door operation and control.
2. Close the hoistway doors and close the car gate.
3. Press the Fault Reset button. Test.
6-65
Troubleshooting
iControl Messages
Safety B Contract Overspeed Fault, SPB COS FAULT
Description: The car has exceeded the Contract Overspeed setting. This fault may be bypassed on the Diag-
nostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. Check the contract overspeed parameter for proper setting. (iView/Safety Config/General)
Safety B DETS Level 2 Speed Fault, SPB DETS L2 SPEED FLT
Description: The car contacted the Down Emergency Terminal Switch while traveling at over 95% of contract
speed. This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. Check for the proper positioning of the DETS switch in the hoistway.
Safety B Fault Activated, SAFETY B FAULT
Description: This event is logged and related car status messages displayed on the OBD and iView if a fault
is detected by safety processor B but not by safety processor A.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. All calls are
immediately cancelled.
Troubleshooting:
1. Check the Event Log for other faults and information related to this fault.
Safety B Fault Deactivated (See: Safety B Fault Activated)
Safety B Fault Bypass Switch Timed Out
Description: Indicates that a fault bypass has timed out. (Bypasses are allowed for 15 minutes with the iBox
Fault/Function Bypass switch in the ON position.) On Inspection mode, this fault is bypassed indefinitely.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. To clear this fault, place the Fault/Function Bypass switch to the OFF position.
Safety B Inspection Leveling Overspeed Fault, SPB LOS FAULT
Description: The car exceeded the leveling overspeed limit (detected by safety processor B). This fault may
be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to move again.
2. Check the leveling overspeed parameter for proper setting (iView/Safety Config/General).
Safety B Inspection Overspeed Fault, SPB IOS FAULT
Description: The car has exceeded the inspection overspeed limit of 150 fpm (detected by safety processor
B).
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to move again.
Safety B SIB Device Fault, SPB SIB DEVICE FAULT
Description: Safety Processor B has a problem writing Safety Ice Bus.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Replace iBox. SAF Board damaged. Contact MCE.
Safety B SIB Device Fault Off (See: Safety B SIB Device Fault)
iControl Messages
Safety B Safety Bypass Jumper Timed Out
Description: Safety Processor B has detected that the Safety Bypass Jumper has been on for more than 15
minutes.
Car Reaction: The car will not be allowed to restart after the end of the current run.
Troubleshooting:
1. Remove the iBox Safety Bypass Jumper.
2. If more time is needed in the Safety Bypass mode, then reinstall Safety Bypass Jumper and the 15 min-
ute timer will restart.
Safety B UETS Level 2 Speed Fault, SPB UETS L2 SPD FLT
Description: The car contacted the Up Emergency Terminal Switch while traveling at over 95% of contract
speed. This fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. The fault will automatically clear 5 seconds after the car stops. The car is then allowed to run again.
2. Check for the proper positioning of the UETS switch in the hoistway.
Safety B Unintended Motion Fault, SPB UNTD MOTION FLT
Description: Safety processor B has detected that both hoistway doors and car gate doors were open as the
car moved away from the floor without a command from the iControl main processor (IMP board) to move.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. If applicable, the
rope brake drops.
Troubleshooting:
1. Check for proper door operation and control.
2. Close the hoistway doors and close the car gate.
3. Press the Fault Reset button. Test.
Safety Bypass Jumper On
Description: Indicates that the Safety Bypass Jumper is in place.
Safety Bypass Jumper Timed Out, SFTY BYP JMPR TMD OUT
Description: Safety Processor A has detected that the Safety Bypass Jumper has been on for more than 15
minutes.
Car Reaction: The car will not be allowed to restart after the end of the current run.
Troubleshooting:
1. Remove the iBox Safety Bypass Jumper.
2. If more time is needed in the Safety Bypass mode, then reinstall Safety Bypass Jumper and the 15 min- 6
ute timer will restart.
Safety C String Open, SAFETY C STRING OPEN
Description: The input has dropped.Input does not come on when bypassed, but the bypass will allow it to
run on Test and Machine Room Inspection.
Car Reaction: Emergency stop if running. The car is not allowed to run until the problem is corrected.
Troubleshooting:
1. Check the car safety string elements and finally the actual input to the iBox.
Safety C String Open Off (See: Safety C String Open)
Safety Configuration Checksum Fault, SFTY CONFIG CHKSM FLT
Description: Safety configuration parameters stored in nonvolatile memory are corrupt or missing.
Car Reaction: The car is not allowed to move.
Troubleshooting:
1. Learn the Safety Configuration. Please refer to Setup - Safety - Configuration Tab on page 9-166.
6-67
Troubleshooting
iControl Messages
Safety Configuration Learn Fault, SFTY CONFIG LEARN FLT
Description: Safety Processor A had a failure when storing configuration values to nonvolatile memory.
Car Reaction: Car will not run until fault is cleared.
Troubleshooting:
1. Make sure the car is on Machine Room Inspection before learning the safety configuration.
2. Check that the installed safety configuration matches the selections on the Safety Configuration screen
and that no bypasses are in place.
3. Repeat the learn process. Please refer to Setup - Safety - Configuration Tab on page 9-166.
4. If unsuccessful, contact MCE Technical Support. (Possible iBox failure.)
Safety Configuration Mismatch, SFTY CONFIG MISMATCH
Description: The parameters saved in the Safety system do not match the values saved in the main proces-
sor.
Car Reaction: Car will not run.
Troubleshooting:
1. Using iView, check the values programmed under the Safety Configuration screen. Verify that they are
correct.
2. Download correct values to the Safety system by executing the learn process from the Safety screen.
Please refer to Setup - Safety - Configuration Tab on page 9-166.
Safety Configuration Inventory Cross Check Fault, SFTY VCTR XCHK FLT
Description: The safety-related boards in the controller do not match the learned configuration.
Car Reaction: The car is not allowed to move.
Troubleshooting:
1. Verify safety bus inventory against the safety configuration. If changes are made, re-learn the safety
configuration. Please refer to Setup - Safety - Configuration Tab on page 9-166.
2. Re-learn the board complement (inventory). Please refer to Setup - Safety - Inventory Tab on page 9-
169.
Safety H String Open, SAFETY H STRING OPEN
Description: The input has dropped.Input does not come on when bypassed, but the bypass will allow it to
run on Test and Machine Room Inspection.
Car Reaction: Emergency stop if running. The car is not allowed to run until the problem is corrected.
Troubleshooting:
1. Check the car safety string elements and finally the actual input to the iBox.
Safety H String Open Off (See: Safety H String Open)
Safety Inventory Checksum Fault, SFTY INVTRY CHKSUM FLT
Description: The Safety Ice bus board inventory stored in nonvolatile memory is corrupt or missing.
Car Reaction: The car will not run.
Troubleshooting:
1. Relearn the inventory of boards using the Learn operation on the Setup > Safety > Inventory tab.
2. Reset the fault (press the iBox FAULT RESET button).
Safety Inventory Comparison Fault, SFTY INVTRY COMPARE FLT
Description: The Safety boards attached to the iBox do not match the safety board inventory kept in the
safety system.
Car Reaction: The car will not run.
Troubleshooting:
1. Relearn the inventory of boards using the Learn operation on the Setup > Safety > Inventory tab.
2. Reset the fault (press the iBox FAULT RESET button).
iControl Messages
Safety Inventory Creation Fault, SFTY INVTRY CREATION FLT
Description: During a relearn of the Safety board inventory, the safety system had a problem creating a list
of boards in non-volatile storage.
Car Reaction: Car will not run.
Troubleshooting:
1. Relearn the inventory of boards using the Learn operation on the Setup > Safety > Inventory tab.
2. Reset the fault (press the iBox FAULT RESET button).
3. If the fault does not clear, cycle power to the controller. Repeat the first two steps if the fault reoccurs.
4. If the previous steps are unsuccessful, iBox replacement may be indicated.
Safety Inventory Learn Fault, SFTY INVTRY LEARN FLT
Description: Safety Processor A failed to store inventory values to nonvolatile memory.
Car Reaction: None
Troubleshooting:
1. Relearn the inventory of boards using the Learn operation on the Setup > Safety > Inventory tab.
2. Reset the fault (press the iBox FAULT RESET button).
3. If the fault does not clear, cycle power to the controller. Repeat the first two steps if the fault reoccurs.
4. If the previous steps are unsuccessful, iBox replacement may be indicated.
Safety String Open
Description: Contact in safety circuit is open.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Refer to the job prints. Verify all safety string switches and wiring.
2. Verify the following have power: SAFC, SAFH, GOV, ESM, and ESC (if the car stop switch bypass is off).
Note that SAFC and SAFH can be bypassed by installing the Safety Bypass Jumper on the IRB board if
the car needs to be moved off the final limits for example).
3. If a rope gripper is installed and the rope gripper option is selected, check RGOK is equal to 1.
4. If a cartop exit is present and the cartop exit option is selected, check that CTEX input is equal to 1.
5. If Unintended Motion was tripped, clear the Unintended Motion fault.
6. Clear any faults left on the iBox display.
7. When the problem is fixed, the fault will automatically clear after 5 seconds.
Safety String Closed (See: Safety String Open)
SCR AC Phase Fault, SCR AC PHASE FAULT
Description: This fault indicates that the 6 feed wires to the M-contactor at the bottom of the System 12
Drive are incorrectly connected. When incorrectly connected, the 30-degree phase angle between X and Y
6
inputs is lost. DC controls only.
Car Reaction: Emergency Stop.
Troubleshooting:
1. Check for a defective or disconnected 32-pin ribbon cable between SCR_LGA board and iBox.
2. Check if the SCR Drive Diagnostic indicators WYE PR, DELTA PR, or 30-Degree PR are ON.
SCR Armature Voltage On, SCR ARM VOLTAGE ON
Description: Indicates presence of a DC voltage between armature terminals A1 and A2 in excess of 0.7VDC
before RE relay is enabled. DC controls only.
Car Reaction: Failure prevents a normal run.
Troubleshooting:
1. Verify test point TP1 on SCR-LGA board (see SCR-LGA Board Layout on page 6-126) is 0.0mv when no
direction is commanded. Adjust R2 if needed.
2. Check for defective serial cable between iBox and drive.
3. Check SCR-LGA board (see Section 6).
6-69
Troubleshooting
iControl Messages
SCR Contactor Fuse Fault, SCR CNTACTR FUSE FLT
Description: Indicates that either the semiconductor fuse has blown or one or more of the 6 contacts within
the two contactors has failed. DC controls only.
Car Reaction: Emergency Stop.
Troubleshooting:
1. Check secondary wires of drive isolation transformer.
2. Check primary voltage on each of the primary terminals of the drive isolation transformer.
3. Check for harsh motor control, vibration, or humming.
4. Check for motor mechanical defect such as interpole (partially shorted).
5. Set an oscilloscope to 2msec/div, 500mv/div, AC coupling. Verify that the 12 drive pulses have equal
amplitudes and periods.
6. Check M1 and M2 contacts.
7. Check semiconductor fuses. (see Semiconductor Fuses on page 6-128)
SCR Drive Ready Fault, SCR DRIVE READY FAULT
Description: Ready signal from the System 12 SCR Drive is inactive. This signal is inactive when the System
12 Drive detects a fault or is being reset (about 5 seconds). DC controls only.
Car Reaction: The elevator is prevented from moving while this signal is inactive.
Troubleshooting: Check the Event Calendar, Hoistway display or iBox display for active SCR drive faults and
follow the recommended troubleshooting for those faults.
SCR Dynamic Brake Fault, SCR DYN BRAKE FAULT
Description: This fault indicates that there is either more than 18-volts across the dynamic braking resistor
or the dynamic brake input from the SCR drive is active. DC controls only.
Car Reaction: Emergency Stop.
Troubleshooting:
1. If this fault occurs with no other SCR Drive faults in the Event Log, it is likely that a different failure such
as an AC Phase Failure has occurred. However, that failure occurred too quickly to be captured.
2. If other SCR drive faults are present, indicates a possible defective dynamic brake SCR or SCR-LGA)
board (see System 12 SCR Drive on page 6-123).
SCR Excessive Armature Current, SCR EXS ARM CURRENT
Description: Armature feedback current exceeded 200% of rated armature current within 250 milliseconds
after run enabled. Triggers a Drive Forced fault if encountered 4 times within 7 run attempts. DC controls
only.
Car Reaction: Car will not run.
Troubleshooting:
1. Run the car on inspection while monitoring armature current versus command current. Verify both val-
ues are approximately equal.
2. Check interpole feedback, filter capacitors (SCR page of job prints), any component in the loop feedback
from the SCR drive out to the motor and back to the drive.
3. Verify drive header current and voltage. Please refer to Brake Calibration on page 2-57.
4. Check serial cable between iBox and drive.
5. Check SCR-LGA board (see System 12 SCR Drive on page 6-123).
SCR Excessive Current Command, Drive Disabled, SCR EXS CURRENT CMD DD
Description: Current command output greater than 200mV before run enable. DC controls only.
Car Reaction: Car will not run.
Troubleshooting:
1. Verify standard control gains (proportional, integral) on drive screens.
iControl Messages
SCR Excessive Current Command, Drive Enabled, SCR EXS CURRENT CMD DE
Description: Current command output greater than 7VDC within 300mS after enabling the run enable relay,
drive enabled. DC controls only.
Car Reaction: Car will not run.
Troubleshooting:
1. Check serial cable between iBox and drive.
2. Check SCR-LGA board (see System 12 SCR Drive on page 6-123).
SCR High Temperature Fault, SCR HIGH TEMP FAULT
Description: This fault indicates that either the ambient temperature inside the System 12 drive has
exceeded 170 degrees F or there is a bad or failing SCR. iControl will attempt to bring the car to the nearest
floor before shutting down. The fault clears when the temperature drops below tripping threshold. DC con-
trols only.
Car Reaction: Stop at nearest floor. Car out of service until fault cleared.
Troubleshooting:
1. Check for excessive ambient temperature.
2. Check for insufficient air flow through the drive, especially if the fault is generated when the car is run-
ning and clears when the car is stopped. Verify that the fan is operating properly. Check the fan fuse.
3. Check for bad or failing SCR.
4. Check for defective fault-generating thermostat. There are two heat sensors, one on each heat sink.
Check the integrity of the heat sensors normally closed contacts.
5. Check the drives rated armature current to determine if it is operating close to the limit threshold.
Please refer to Current Limit Adjustments on page 2-63.
SCR Instantaneous Over Current, SCR INST OVER CURRENT
Description: This fault indicates that the System 12 SCR Drive detected excessive armature current. DC con-
trols only.
Car Reaction: Emergency Stop.
Troubleshooting:
1. Check that the main supply is being shut off during regeneration.
2. Check for a clipped door lock.
3. Check for a motor connection problem.
4. Possible failure of an SCR in the System 12 Drive.
SCR Insufficient Armature Current, SCR INSF ARM CURRENT
Description: This fault indicates that insufficient armature feedback current has been detected. This fault is
generated if the requested current is at least 20% of the rated armature current yet the detected feedback 6
remains below 10% of the rated armature current. Automatically resets if detected four or fewer times in
seven consecutive runs. DC controls only.
Car Reaction: Emergency Stop.
Troubleshooting:
1. Check Armature Voltage Limit and Armature Current Limit settings on iView/Drive/Safety. Please refer to
Armature Voltage on page 4-10.
2. If this fault occurs when the car is running at speed, adjust Motor Field so that armature voltage is within
rated motor armature voltage.
3. Verify current sensor connection on SCR-LGA board (see System 12 SCR Drive on page 6-123). Check
SCR-LGA board.
4. Check serial cable from drive to iBox.
5. Monitor the Up and Down direction inputs on the SCR-LGA board (bottom of R14 down, bottom of R22
up). If there is a momentary drop in the direction signal before the run is complete, use jumpers to
determine if a section of the safety string is failing. WARNING: The car must be on Independent Service
before performing this test.
6. If the failure persists from the beginning of the run, make sure the current signal on SCR-LGA board test
point TP3 is not dropping out.
6-71
Troubleshooting
iControl Messages
SCR Loop Over Current, SCR LOOP OVER CURRENT
Description: DC loop current has grossly exceeded the reference value. DC controls only.
Car Reaction: Emergency Stop.
Troubleshooting:
1. Verify that the brake is completely lifting.
2. Check that the load in the car is not in excess of full load.
SCR Low Line Caution Activated, SCR Low Line Caution, SCR LOW LINE CAUTION
Description: The iBox has determined that the line voltage to the System 12 Drive is between 80% and 95%
of rated armature voltage. The line voltage test occurs every time the elevator stops. The detected percent-
age is based on the Rated Armature Voltage parameter setting on the iView Drive Configuration
screen>General tab. DC controls only.
Car Reaction: None. Elevator speed is limited to the detected line voltage percentage.
Troubleshooting:
1. Verify that the Rated Armature Voltage parameter value is correct. The RMS value (AC phase measure-
ment on a voltmeter) at TP4 on the System 12 SCR-LGA board reflects the line voltage divided by one
hundred (The RMS values of the line-to-line voltages at the wye and delta connections of the drive or
secondary isolation transformer).
2. Verify the voltage into the primary of the Drive Isolation Transformer is not sagging.
3. Check the drive header rating against the voltage on the isolation transformer secondary. Please refer to
Current Limit Adjustments on page 2-63.
SCR Low Line Caution Deactivated
Description: The iBox has determined that the line voltage to the System 12 Drive is above 90% of rated
armature voltage (see SCR Low Line Caution (Activated)). DC controls only.
SCR Low Line Fault, SCR LOW LINE FAULT
Description: Indicates that AC line voltage to the System 12 Drive has dropped below 95% of the SCR-LGA
header value. DC controls only.
Car Reaction: Car will not move.
Troubleshooting:
1. Verify that the Rated Armature Voltage parameter value is correct. The RMS value (AC phase measure-
ment on a voltmeter) at TP4 on the System 12 SCR-LGA board reflects the line voltage divided by one
hundred (The RMS values of the line-to-line voltages at the wye and delta connections of the drive or
secondary isolation transformer).
2. Verify the voltage into the primary of the Drive Isolation Transformer is not sagging.
3. Check the drive header rating against the voltage on the isolation transformer secondary. Please refer to
Current Limit Adjustments on page 2-63.
SCR Low Line Test Fault
Description: The test to determine the line voltage to the System 12 drive has failed to determine the line
voltage (see SCR Low Line Caution Activated). DC controls only.
Car Reaction: None. Previous line voltage test values are used.
Troubleshooting: Possible internal hardware error on iBox trying to update System 12 drives MDAC.
SCR Phase Lock Loop Fault, SCR PHASE LCK LP FLT
Description: This fault indicates that the phase lock loop circuit PLL LED is ON in the SCR-LGA and that the
System 12 SCR Drive was unable to lock onto the incoming line frequency. The PLL LED is normally on for a
few seconds during power up. DC controls only.
Car Reaction: Car will not move.
Troubleshooting:
1. Contact MCE technical support.
iControl Messages
SCR Phase Lock Loop Warning
Description: This fault indicates that the phase lock loop circuit PLL LED is ON in the SCR-LGA and that the
System 12 SCR Drive was unable to lock onto the incoming line frequency. The PLL LED is normally on for a
few seconds during power up. Detected while the car is not moving. DC controls only.
Car Reaction: Car will not move.
Troubleshooting:
1. Verify that the PLL indicator is active on the SCR-LGA board.
2. Verify that the iBox is not resetting the SCR drive. If it is, the PLL indicator will be active for a short inter-
val. For a recurring drive fault, the iBox should reset the SCR drive every 15 seconds. If so, there is
probably an underlying fault that the iBox is trying to clear.
3. Contact MCE technical support.
SCR Power Supply Fault, SCR POWER SUPPLY FLT
Description: Indicates that power supplied to the System 12 SCR Drive is insufficient. DC controls only.
Car Reaction: Car will not run.
Troubleshooting:
1. Check all supply voltages on the SCR-PS board (see System 12 SCR Drive on page 6-123).
2. Check the F2D fuse.
3. Verify voltages inside the drive are within 1%. Please refer to Brake Calibration on page 2-57.
4. If voltages are correct, check the drive cable from the iBox to the drive. Check the SCR-LGA board (see
System 12 SCR Drive on page 6-123).
Secondary Fire Switch On, SEC FIRE SWITCH ON
Description: The Secondary Fire Recall Switch is in the ON position.
Car Reaction: The car will recall to the Main fire recall floor, position its doors as indicated on the Car Oper-
ation/Fire/Modify/Fire Recall screen, and await activation of the in-car firefighter switch.
Troubleshooting: If in error, check the Secondary Fire Recall switch input.
Security On
Description: Indicates that system security is On.
Security Config n (n = 1 - 8)
Description: Indicates the security configuration that is being used.
Send Sys Params to n (n = 1 - 20)
Description: Indicates that this controller (iCentral or Local/Dispatcher) is sending system parameters to car
n (n = 1 - 20). (DO NOT RESET CAR n).
Serial COP Bus n Comm Fault, SCOP BUS n COMM FAULT (n = 1 - 4)
6
Description: Indicates lost communication between the ICE-CTP (cartop processor) board and the ICE-COP
(serial COP) board for at least 1.5 seconds.
Car Reaction: none
Troubleshooting:
1. Check for a bad cable between the ICE-CTP and ICE-COP boards.
2. Check for a bad ICE-COP board.
3. Check for high electrical noise interference.
4. Check for proper shielding of the cables (board to board and board to controller).
6-73
Troubleshooting
iControl Messages
Serial COP Bus n Inventory Fault, SCOP BUS n INVENTORY FLT (n = 1 - 4)
Description: Can indicate lost communication between the ICE-COP (serial COP) board and one or more ICE-
COP-x boards. Could also indicate that an ICE-COP-x board was connected or disconnected after the system
was powered up (I/O inventory changed).
Car Reaction: none
Troubleshooting:
1. Check for bad cable(s) between the ICE-COP and ICE-COP-x boards.
2. Check for a bad ICE-COP-x board.
3. Press the RESET button on the ICE-COP board (takes a new inventory).
Sheave Brake Drop Fault, SHEAVE BRAKE DROP FLT
Description: The sheave brake was disabled via Sheave Brake Enable output, but the Sheave Brake Monitor
input was high. There is a five second delay before fault is generated.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. All calls are can-
celled. The doors will cycle.
Troubleshooting:
1. Verify that the Sheave Brake Monitor input and Sheave Brake Enable output have been programmed
(Configuration > I/O Boards > Configuration tab).
2. Check the voltage at the Sheave Brake Monitor input and the internal representation via the View button
on the Configuration > I/O Boards > Configuration tab.
3. Check the voltage at the Sheave Brake Enable output and the internal representation via the View button
on the Configuration > I/O Boards > Configuration tab.
4. Check the sheave brake mechanism and circuitry.
Sheave Brake Pick Fault, SHEAVE BRAKE PICK FLT
Description: The sheave brake was enabled via Sheave Brake Enable output, but the Sheave Brake Monitor
input was low. There is a five second delay before a fault is generated.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. All calls are can-
celled. The doors will cycle.
Troubleshooting:
1. Verify that the Sheave Brake Monitor input and Sheave Brake Enable output have been programmed
(Configuration > I/O Boards > Configuration tab).
2. Check the voltage at the Sheave Brake Monitor input and the internal representation via the View button
on the Configuration > I/O Boards > Configuration tab.
3. Check the voltage at the Sheave Brake Enable output and the internal representation via the View button
on the Configuration > I/O Boards > Configuration tab.
4. Check the sheave brake mechanism and circuitry.
Shuttle Service Activated, SHUTTLE SERVICE ON
Description: Indicates that Shuttle service has been activated via key-switch/input, software command or
timer.
Shuttle Service Deactivated, SHUTTLE SERVICE OFF (see Shuttle Service Activated).
Single Channel QUAD Fault, SNG CHANNEL QUAD FLT
Description: This fault indicates the failure of one of the two landing system quadrature signals (DP1 or
DP2).
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check DP1 and DP2 wiring from the landing system to the iBox.
iControl Messages
Software Recall Switch Activated, SOFTWARE RECALL ON
Description: The software recall command has been activated via iMonitor.
Car Reaction: The car recalls to the specified floor. Car calls and doors operate as specified by the software
recall command parameters.
Troubleshooting: Check the status of the recall command and related parameters.
SPA Spare Event n (n = 1 to 8)
Description: SPA Spare Events 1 through 8 are used for testing.
Speed Limit, MF Forcing, SPD LMT MF FORCING
Description: The system detected armature current without the armature current command. (The motor field
is forced to help dynamic braking slow the car.) DC controls only.
Car Reaction:
Troubleshooting:
1. Check that the brake is setting properly.
Stuck Cartop Inspection Input, STUCK CT INSP. INPUT
Description: Stuck inspection monitoring is enabled by the Monitor cartop and car panel inspection inputs
option (Setup > Safety > Configuration tab). During passenger (automatic) operation, this message is gen-
erated if any of the cartop inspection inputs (CTEN, ICTU, ICTD) remain high for more than 250msec. During
inspection operation, this message is generated if any combination of cartop inspection inputs remain high
for more than five seconds, except for the following two, Enable plus Up (CTEN + ICTU) and Enable plus
Down (CTEN + ICTD).
Car Reaction: None
Troubleshooting: Check and fix the car panel inspection buttons and related circuitry (Enable, Up, Down).
Stuck Car Panel Inspection Input, STUCK CP INSP. INPUT
Description: Stuck inspection monitoring is enabled by the Monitor cartop and car panel inspection inputs
option (Setup > Safety > Configuration tab). During passenger (automatic) operation, this message is gen-
erated if any of the car panel inspection inputs (ICEN, ICPU, ICPD) remain high for more than 250msec. Dur-
ing inspection operation, this message is generated if any combination of car panel inspection inputs remain
high for more than five seconds, except for the following two, Enable plus Up (ICEN + ICPU) and Enable plus
Down (ICEN + ICPD).
Car Reaction: None
Troubleshooting: Check and fix the cartop inspection buttons and related circuitry (Enable, Up, Down).
Stuck Inspection Input Fault, STUCK IN. INPUT FLT 6
Description: This fault is generated when a stuck inspection input is detected during passenger (automatic)
operation (see Stuck Cartop / Car Panel Inspection Input message). The fault is not generated if the car was
on inspection operation. To avoid entrapment, the fault is not generated until the car has reached a floor.
Car Reaction: All hall calls are reassigned or canceled. The car will complete its run. When the car is at a
floor, doors are cycled to let the passengers out and all car calls are canceled. The car is shut down and
remains out-of-service until the fault is cleared.
Troubleshooting: Check and fix all inspection inputs/buttons. Then press the iBox Fault reset button.
Swing Operation Activated, Swing Operation, SWING OPERATION
Description: Indicates that the car is in swing car operation, independent of the Group Controller. The car
should be servicing a riser of hall calls dedicated to the car. The car will use settings from the Simplex Hall
Call and Parking related settings from the car Simplex supervisor screens.
Swing Operation Deactivated. See Swing Operation Activated.
SYSTEM SYNC
Description: The iBox is establishing communication with the cartop and acquiring position data.
6-75
Troubleshooting
iControl Messages
Tach Error Fault, TACH ERROR FAULT
Description: Indicates that the difference between the intended speed and the speed feedback signal has
exceeded the Following Error parameter.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. Followed by nor-
mal run.
Troubleshooting:
1. Please refer to Tach Error Tripping Threshold Adjustment on page 4-45.
Tach Failure, TACH FAILURE
Description: Indicates that the difference between the synthetic tach signal and the external speed feedback
signal has exceeded the tolerance value.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped. Cancel all calls.
Troubleshooting:
1. Check velocity encoder and recalibrate tach failure and synthetic speed. Please refer to Tach Failure Cal-
ibration on page 2-69 and see Synthetic Speed Calibration on page 4-13
TERMINAL LEARN ON
Description: This status message, on the iBox display, indicates that the system is prepared to learn the
speed and position values for the normal (UNT1-5/DNT1-5) and emergency (UETS/DETS) terminal switches.
Terminal Synchronization Fault, TERMINAL SYNC FAULT
Description: The system either did not receive edge position data from the cartop or the system did not
detect a floor position magnet where expected.
Car Reaction: The car stops after crossing the floor magnet at the top or bottom terminal landing and is not
allowed to move.
Troubleshooting:
1. Verify that the car was not moved after power was shut off.
2. Verify that the up/down normal terminal switch #5 opens at the appropriate location. When the up/down
switch opens, no LU or LD sensor should be active. Also, only one floor magnet should be encountered in
the direction of travel after the up/down switch opens.
3. Move the car past floors around the vicinity of the fault and verify the proper activation of the LU and LD
sensors.
4. Verify that the system is communicating with the cartop (no Cartop Communication Fault).
5. Verify that the absolute and cartop positions change by the same amount and same direction while mov-
ing the car.
6. Verify that the terminal magnet has not fallen off.
7. Check the clearance between the floor sensor board and the magnets. Sometimes this clearance will be
off just enough to make some magnets fail to register properly. Adjust the clearance if necessary.
8. Re-learn the floor heights.
9. The iLink, iLand or iBox may be faulty.
Test Mode, Test
Description: Indicates that the elevator is in the Test mode of operation. iBox Test switch in Test position.
Car Reaction: Door operation is disabled. This setting is used to adjust or test the elevator.
This Car Alternate Fire Sensor Recall, THIS CAR ALT FIRE
Description: Recall to the alternate fire floor due to active or latched smoke detector input(s) from the cars
hoistway or machine room.
Car Reaction: Car proceeds to the user-defined alternate fire recall floor. Once at the recall floor, door opera-
tion is according to the user-defined door operation under fire recall operation. The fire warning indicator
light will flash.
Troubleshooting:
1. If in error, inspect the sensors, inputs, and connections.
2. Related Inputs: This Car Alt Recall sensor inputs as shown on the job prints.
iControl Messages
This Car Main Fire Sensor Recall, THIS CAR MAIN FIRE
Description: Recall to the main fire floor due to active or latched smoke detector input(s) from the cars hoist-
way or machine room.
Car Reaction: Car proceeds to the user-defined main fire recall floor. Once at the recall floor, door operation
is according to the user-defined door operation under fire recall operation. The fire warning indicator light will
flash.
Troubleshooting:
1. If in error, inspect the sensors, inputs, and connections.
2. Related Inputs: This Car Main Recall sensor inputs as shown on the job prints.
Unintended Motion Fault (see Safety A Unintended Motion Fault)
Up Direction Limit Open, UP DIR LIMIT OPEN
Description: The up normal terminal direction switch is open
Car Reaction: Immediate stop if moving. Further up direction movement is prevented.
Troubleshooting:
1. Verify that the switch is operating properly.
2. Verify correct state of the iBox UNTD input.
3. Verify UNTD switch activating/deactivating at the appropriate location (normally 2 below the bottom
terminal landing - see prints).
Up Emergency Terminal Switch Position Fault, UP ETS POSITION FAULT
Description: The reported position upon encountering the Terminal Switch differed from the learned switch
position by more than the set position margin. This fault may be bypassed on the Diagnostics > Fault Bypass
tab.
Car Reaction: Emergency Stop: Motor contactor and brake contactor immediately dropped. All hall and car
calls are cancelled. After the car is stopped, it will run at Correction speed to the next available floor and
cycle the door. Door Open button will remain operational. If generated when car is moving, fault will stay
latched and the Fault Reset button must be pushed to clear it. If generated when the car is not moving, fault
will self clear when condition no longer exists.
Troubleshooting:
1. Physically check the integrity of the switch and wiring.
2. Check the iBox input for the switch.
3. On the Diagnostics > Terminal Switches Status tab, compare the Last pass position to the Learned posi-
tion for this switch. Verify that Position Margin is within a reasonable range (Configuration > Terminal
Switches tab). If appropriate, move the switch closer to the terminal landing.
4. Relearn the NTS and ETS switches. Please refer to Learning Normal & Emergency Terminal Limit 6
Switches on page 4-11.
Up Emergency Terminal Switch Shutdown, UP ETS SHUTDOWN
Description: The Up Emergency Terminal Switch opened at a speed or position exceeding its specified
threshold. The fault stays latched and the Fault Reset button must be pushed to clear it. If generated when
the car is stopped, the fault will self clear when the condition no longer exists.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. This fault is logged in conjunction with either a speed or position fault at UETS. Check the Event Log and
follow the troubleshooting recommended for the Up Emergency Terminal Switch Position Fault or Safety
A (or B) UETS Level 2 Speed Fault.
2. Press iBox Fault Reset to clear the fault.
6-77
Troubleshooting
iControl Messages
Up Normal Terminal Switch n Level 1 Speed Fault, UP NTSn L1 SPEED FLT (n = 1 to 5)
Description: A Level 1 Overspeed fault has been detected at Up Normal Terminal switch 'n' (1 to 5). When
the switch opened, the car was traveling faster than defined by Level 1 overspeed settings (sum of learned
speed plus Overspeed 1 Margin percentage setting on Configuration > Terminal Switches tab) but not fast
enough to trigger the Level 2 overspeed fault. This fault may be bypassed on the Diagnostics > Fault Bypass
tab.
Car Reaction: Controlled stop using Emergency Slowdown pattern parameters.
Troubleshooting:
1. On the Diagnostics > Terminal Switches Status tab, compare the Last pass and Learned speeds for this
switch. If appropriate, increase the Overspeed 1 Margin on the Configuration > Terminal Switches tab.
2. May be caused by a change in the Pattern parameters. Always re-learn the terminal switches after any
changes to Pattern parameters.
3. One or two floor runs can sometimes come in hotter than multi-floor runs.(the switches are learned
making full hatch runs). If short runs are causing the problem, increase the Overspeed 1 Margin (Config-
uration > Terminal Switches tab) or lower the Standard profile - High Roll Jerk parameter (Configuration
> Pattern > Modes tab.
4. Can also be caused by a car that is following the pattern poorly, possibly due to heavy load or poor speed
loop performance. In this case, adjust the speed loop to follow pattern as well as possible and/or alter
the pattern parameters to produce a gentler deceleration and approach to the floor (then re-learn the
switches). Please refer to Terminal Switch Overspeed and Position Faults on page 4-55.
Up Normal Terminal Switch n Level 2 Speed Fault, UP NTSn L2 SPEED FLT (n = 1 to 5)
Description: A Level 2 Overspeed fault has been detected at Up Normal Terminal switch 'n' (1 to 5). The car
was traveling faster than defined by Level 2 overspeed settings (105% of sum of learned speed plus Over-
speed 1 Margin percentage setting on Configuration > Terminal Switches tab). This fault may be bypassed
on the Diagnostics > Fault Bypass tab.
Car Reaction: Emergency stop: Motor contactor and brake contactor immediately dropped.
Troubleshooting:
1. Check the Diagnostics > Terminal Switches Status tab to see how fast the car was traveling on the Last
pass by this switch. Check this value against the Learned speed for the switch. If appropriate, increase
the Overspeed 1 Margin on the Configuration > Terminal Switches tab.
2. May be caused by a change in the Pattern parameters. Always re-learn the terminal switches after any
changes to Pattern parameters.
3. One or two floor runs can sometimes come in hotter than multi-floor runs. (Remember that the
switches are learned making full hatch runs.) If short runs are causing this, you may have to increase
the Overspeed 1 Margin or lower the Standard profile - High Roll Jerk parameter.
4. Can also be caused by a car that is following the pattern poorly, possibly due to heavy load or poor speed
loop performance. In this case, you need to get the speed loop adjusted to follow pattern as well as pos-
sible and/or alter the pattern parameters to produce a gentler deceleration and approach to the floor
(then re-learn the switches). Please refer to Terminal Switch Overspeed and Position Faults on page 4-
55.
iControl Messages
Up Normal Terminal Switch n Position Fault, UP NTSn POSITION FLT (n = 1 to 6)
Description: When the switch opened or closed, the cars reported position was different from the learned
position by a value exceeding the margin set on the Configuration > Terminal Switches tab. This may mean
that the switch opened early, late or not at all on approach to the terminal. It may also mean that the switch
closed early, late, or not at all on departure from the terminal. Finally, the switch can go open while standing
at a floor where its learned position is closed, or go closed at a floor where its learned position is open. This
fault may be bypassed on the Diagnostics > Fault Bypass tab.
Car Reaction: If traveling up, the car executes an emergency slowdown, then continue at low speed until it
encounters a floor. The car stops at the floor, opens its doors, and performs a floor sync operation. If the
fault persists, the car goes out of service. If traveling down, the car continues normally to the first stop,
opens its doors and performs a floor sync operation. If the fault persists, the car goes out of service. If
stopped at a floor, the car opens its doors, does a floor sync, and, if the fault persists, goes out of service.
Troubleshooting:
1. On the Diagnostics > Terminal Switches Status tab, compare the Last pass position to the Learned posi-
tion for this switch.
2. If the fault is mechanical (switch movement, magnet movement, or bad traveler cable), the fault will
tend to repeat at the same position every time.
3. A stuck switch is easy to spot by running the car on inspection and observing the input LEDs on the iBox.
4. Perform a Terminal Sync operation (Terminal button on the Configuration > Pattern > Common tab).
User code accessing an invalid logical indicator (internal event)
User Event n Off (n = 1- 10) (see User Defined Event n On)
User Event n On (n = 1 - 10),
Description: Indicates that User Event x (1 - 10) has been activated via User Input n (1 - 10)
Car Reaction: Determined by user programming (Configuration > Advanced > User Inputs tab)
Troubleshooting: Determined by user programming (Configuration > Advanced > User Inputs tab)
Vector Checksum Fault (see Safety Inventory Checksum Fault)
Vector Comparison Fault (see Safety Inventory Comparison Fault)
Vector Creation Fault (see Safety Inventory Creation Fault)
Vector Learn Fault (see Safety Inventory Learn Fault)
Watchdog Ordered Control Stop Before Reset
Description: A critical component in the system has locked up.
Car Reaction: The car will come to a controlled stop and the system will reboot automatically.
Troubleshooting: 6
Watchdog Ordered Emergency Stop Before Reset
Description: A critical component in the system has locked up.
Car Reaction: The car will perform an emergency stop and the system will reboot automatically.
Troubleshooting:
6-79
Troubleshooting
Board retaining
screws: Loosen to
slide board
Pluggable central
bus connectors
Note
Before using iView to assign or reassign inputs or outputs to I/O boards, consult MCE so that
your job prints can be corrected. Remember that reassigning an input or output will also
require appropriate re-routing of the wiring.
iBox Removal
1. Shut off power at the main disconnect.
2. Open the iControl cabinet.
6
3. Loosen the iBox cover retaining screws and remove the cover.
4. Unplug all connections to the body of the iBox. You can leave the connections to the rail-
mounted circuit boards above and below the iBox connected.
5. Slightly loosen the retaining screws for the rail-mounted circuit boards and slide them
away from the iBox (disconnecting the pluggable central bus).
6. Loosen the four captive, retaining screws that secure the iBox to the circuit board rails.
7. Remove the iBox.
6-81
Troubleshooting
iBox Installation
1. Verify that power is off at the main disconnect.
2. Open the iControl cabinet.
3. Remove the cover (bezel) from the new iBox.
4. Secure the new iBox in position between the rail-mounted circuit boards.
5. Slide the rail-mounted circuit boards above and below the iBox back into position so
that the central bus is plugged back in.
6. Tighten the board retaining screws.
7. Reconnect all cabling to the body of the iBox.
The circuit boards are listed in the table below. If you are viewing this file on a computer, click
the page number to jump to the appropriate section.
ICE-COP Serial Car Operating Panel Board Car Operating Panels page 6-84
ICE-CTP Car Top Processor Board iLink Car Top Interconnect page 6-86
ICE-MOR Multiple Output Relay Board iControl AC, DC, iCentral Group, iLink page 6-107
SC-HCDA-ISO Serial Hall Call Driver Isolation Board iControl AC, DC Simplex / Swing Car page 6-117
6
SC-HCE-ME Serial Hall Call Ethernet - Digi Board iCentral Group page 6-118
SC-HCNT Serial Hall Call Node Board Hall Call Fixture Enclosures page 6-119
SC-ION Serial Control I/O Node Board iCentral Group page 6-116
SCR-LGA SCR Drive Logic Board System 12 SCR Drive page 6-123
6-83
Troubleshooting
Normal Operation
During normal operation, I/O LEDs will be lighted when the associated I/O is active (dimmer
when the output is active; brighter when the input is active). The SPA processor LED will be
continuously lighted. If I/O LEDs remain in a static condition or the SPA processor LED is not
continuously on:
Press the RST button on the board. The I/O LEDs will all cycle and the board will resume
operation.
Board Diagnostics
Two DIP switches and the I/O status LEDs provide diagnostic information.
Set the two bottom DIP switches (1 and 2) to the ON position.
I/O 1 and 2 LEDs will flash if RS485 with the cartop is good. LED1 monitors received
data; LED 2 monitors transmitted data. If an LED is not flashing, that phase of com-
munication has failed.
I/O 4 and 5 LEDs will flash if SPI communication with the preceding board in the
chain is good. LED 4 monitors received data; LED 5 monitors transmitted data. If an
LED is not flashing, that phase of communication has failed.
I/O 7 and 8 LEDs will flash if SPI communication with the next board in the chain is
good. LED 7 monitors received data; LED 8 monitors transmitted data. If an LED is
not flashing, that phase of communication has failed.
8-position DIP
I/O Status LEDs switch package
Test point,+3.3v
Caution
This system is designed for 24 VDC
circuits maximum. Connecting
COM
120VAC or DC will open the input
fuses. +24V SIGNAL
COM
6-85
Troubleshooting
LED, Computer On
Ground Testpoint
Ground testpoint
TP_LW testpoint
+2.5V testpoint
Terminal Description
1 Common
DLSP Door Logic Supply (See job prints for source level)
2 120VAC
DOF Door Open Function output (active level =DLSP)
DBF Door Boost Function output (active level =DLSP)
DCF Door Close Function output (active level =DLSP)
NUDG Door Nudge output (active level =DLSP)
SP1 Spare Input (120VAC signal level)
SP2 Spare Input (120VAC signal level)
SP3 Spare Input (120VAC signal level)
SP4 Spare Input (120VAC signal level)
SE (Door) Safe Edge Input (120VAC signal level)
PHE Photo Eye input (120VAC signal level)
DOL Door Open Limit input (120VAC signal level)
DCL Door Close Limit input (120VAC signal level)
DPM Door Position Monitor input (120VAC signal level)
ICTD Cartop inspection down button (110VDC= switch closed)
ICTU Cartop inspection up button (110VDC= switch closed)
INCT Cartop inspection switch active (110VDC= switch closed)
GS Gate Switch input (110VDC= switch closed)
GSR Gate Switch Rear (110VDC= switch closed)
ULMR Up Level Marker Rear output (110VDC= output active)
DZR Door Zone Rear (110VDC= output active)
DLMR Down Level Marker Rear (110VDC= output active)
ULM Up Level Marker (110VDC= output active)
DZ Door Zone (110VDC= output active)
DLM Down Level Marker (110VDC= output active)
1 Common
2 120VAC
3 110VDC
6
SCT1 Cartop Safety Contact 1 (110VDC= contact closed)
SCT2 Cartop Safety Contact 2 (110VDC= contact closed)
6-87
Troubleshooting
Terminal Description
SHLD Shield: Common
26V 26V output to load weigher
LW- Input from Load Weigher (analog voltage)
LW+ Input from Load Weigher (analog voltage)
DP2- Position input from iLand (balanced pair with DP2+)
DP2+ Position input from iLand (balanced pair with DP2-)
SHLD Shield: Common
DP1- Position input from iLand (balanced pair with DP1+)
DP1+ Position input from iLand (balanced pair with DP1-)
SHLD Shield: Common
TX+ Transmit to iBox (connect to iBox terminal RX+)
TX- Transmit to iBox (connect to iBox terminal RX-)
SHLD Shield: Common
RX+ Receive from iBox (connect to iBox terminal TX+)
RX- Receive from iBox (connect to iBox terminal TX-)
SHLD Shield: Common
Note
If there is a problem with communication between the iBox and the CTP board after initial
installation, verify that the iBox TX+ and TX- terminals are connected to the CTP board RX+
and RX- terminals, and the iBox RX+ and RX- terminals are connected to the CTP board TX+
and TX- terminals (see ICE-CTP Board Connections on page 6-88).
Manual Reset Regardless of switch settings, the LEDs have the same meaning during
reset and startup.
When the reset button is release, the LEDs will light up one at a time in the following
sequence - (1, 2, 3, 4, 5, 6, 7, 8, 7, 6, 5, 4, 3, 2, 1). Normal operation should commence
immediately following the reset sequence.
If the reset sequence consists of three iterations of all LEDs on at the same time followed by all
LEDs off, the board has been programmed with a non-production version of firmware. The
board should be reprogrammed.
6-89
Troubleshooting
Normal Operation The normal operating condition is with all DIP switches OFF. This
gives the normal operation display as follows:
Table 6.9 Diagnostic Indicators (Normal Operation - All DIP Switches OFF)
LED Description
1 Represents message input from iBox to iLink. With proper communication, toggles approx-
imately every 80mS. Goes OFF and stays OFF if input is lost.
2 Indicates that the cartop detected an unintended motion safety fault. With the car on Pas-
senger operation, after the car had reached a landing, the car moved at a speed greater
than 150 feet-per-minute.
3 Indicates that the cartop detected an unintended motion safety fault. With the car on
Inspection, after the car had reached a landing, the car moved with doors open.
4 Message output from iLink to iBox. With proper communication, toggles approximately
every 80mS. Goes OFF and stays OFF if output is lost.
5 This is the alive indicator. It toggles every 80mS during normal operation.
7 Unused.
8 Indicates that an interrupt is being serviced. If it goes off and stays off, the board is not
functioning normally and should be reset (press the RESET button).
When the iBox is not active, only LED 5 will toggle. When the iBox is active and normal opera-
tions are in progress, LEDs 1, 4 and 5 will toggle regularly.
Firmware Download Firmware updates can be downloaded via iView. Please refer to
Updating Controller Firmware on page 8-41. Normally, no manual intervention is needed at
the cartop. However, if a problem does develop, the following may be of use in recovering:
1. Set the S1 DIP switches 1, 6 and 8 = ON.
2. Press the manual Reset button on the ICE-CTP board. This tells the cartop firmware to
wait for a firmware download without attempting to run the normal cartop application
first.
3. Perform the firmware update using iView (File > Firmware Update).
Board Version The version and revision of the ICE-CTP board can be determined using
the DIP switches and LEDs 1 through 6 (ignore LEDs 7 and 8) The values are in hexadecimal,
with LED1 bring the 20 bit. For example, if the number were 01, LED 1 would be ON and LEDs
2 through 6 would be OFF (LEDs 7 and 8 are not part of the value and must be ignored).
DIP switch 3 = ON, all others = OFF: Major version number displayed on LEDs.
DIP switch 2 = ON, all others = OFF: Minor version number displayed on LEDs.
DIP switch 1 = ON, all others = OFF: Revision number displayed on LEDs.
Receive Serial Data There are five serial connections on the cartop - one to the iBox
and up to four to Serial COP boards. Each connection can be monitored by setting the S1 DIP
switches as described below:
To monitor data received from iBox, set DIP switches 1 and 4 = ON.
To monitor data received from COP1, set DIP switches 1, 2 and 4 = ON.
To monitor data received from COP2, set DIP switches 1, 3 and 4 = ON.
To monitor data received from COP3, set DIP switches 1, 2, 3 and 4 = ON.
To monitor data received from COP4, set DIP switches 1, and 5 = ON.
When the LEDs are ON they indicate the following:
LED1: A non-STX character has been detected when an STX character was expected.
LED2: An STX character has been received from the cartop.
LED3: Data characters are being received from the cartop.
LED4: A CRC character has been received.
LED5: The CRC check indicates that good data was received.
LED6: The CRC check indicates that bad data was received.
In normal operation, LEDs 2, 3, and 5 will glow faintly and LED 4 will blink roughly once every
40ms. If LED 1 or 6 is bright, bad data is being received from the cartop. This suggests that
there is a serial line quality problem.
If LEDs turn on and stay on, the board is not functioning normally and should be reset (press
the RESET button). If the condition persists, there is likely a hardware problem on the board.
6-91
Troubleshooting
Unintended Motion
Fault indicator
Signal presence Unintended Motion
indicators Fault reset button
The user makes no direct connections to this board. Refer to job prints for circuit information.
IFIELD-MODULE Specifications
Inputs: 70 VAC min, 300 VAC max, 1 Phase, 50/60Hz, 42 AMPS Maximum
Terminals
Indicators 1
+15ISO OK 2
F. BAD Fan
+15 OK Fan2
HI TEMP Temp1
TP +15 IGBT FLT Temp2
Terminals on
FMP board
FMO+
TP GND FMO-
TP ISO GND FMSI
TP +15 ISO FMCI
FMHC
FMS1
FMS2
FMLD 6
FMSO
FMX1
FMX2
TP BT1
TP BT2
To SAF
board
TP VI1
TP 60Hz Ref
To ICE-FMP TP VI2
TP -15
board
R74
6-93
Troubleshooting
Indicators Description
+15 ISO OK LED indicator for isolated +15V power supply, measured with respect to isolated
Ground, GND-ISO. Normally ON. Turns OFF when module loses +15 ISO voltage.
F. BAD LED indicator for AC input on FMX1 and FMX2 terminals (on FMP board). Normally
OFF. Turns ON when any input side AC fuse opens.
+15 OK LED indicator for +15V power supply, measured with respect to Ground. Normally
ON. Turns OFF when module looses +15V.
HI TEMP LED turns ON to indicate high temperature on the heatsink. Normally OFF. Turns
ON when the temperature of the main IGBT raises above 85oC (185oF).
IGBT FLT LED turns ON to indicate that the AUX IGBT has failed open.
Terminal Description
Terminal Description
FMSI Field Module Safety Input: Jumpered to FMSO. FMSI and FMSO are always jump-
ered together unless there is a requirement for a mechanical safety contact to
break between the load and the field module.
FMCI Field Module Current Input: When load current is higher than 10A, jumper FMCI to
FMHC. For load current less than 10A, leave both FMCI and FMHC open.
FMS1 Field Module Snubber 1: When used as a Brake Module, a shunt RC parallel net-
work (RB & CB) is connected between FMS1 and FMLD.
FMLD Field Module Load Diode: FMLD is connected to the cathode of a diode on the ICE-
FMP board. FMLD is also connected to RC network RB & CB (see FMS1).
FMX1 AC power input to Field Module from brake contacts (70 VAC min, 300 VAC max)
FMX2 AC power input to Field Module from brake contacts (70 VAC min, 300 VAC max)
Table 6.14 IFIELD-MODULE Terminals on the ICE-FMP Board (Motor Field Module)
Terminal Description
FMSI Field Module Safety Input: Jumpered to FMSO. FMSI and FMSO are always jump-
ered together unless there is a requirement for a mechanical safety contact to 6
break between the load and the field module.
FMCI Field Module Current Input: When load current is higher than 10A, jumper FMCI to
FMHC. For load current less than 10A, leave both FMCI and FMHC open.
FMS1 Field Module Snubber 1: When used as a Motor Field Module, an RC filter network
(RM & CM) is connected between FMS1 and FMS2. FMS1 is also jumper to FMLD.
FMLD Field Module Load Diode: FMLD is connected to the cathode of a diode on the ICE-
FMP board. FMLD is also jumpered to FMS1.
FMX1 AC power input to Field Module (70 VAC min, 300 VAC max)
FMX2 AC power input to Field Module (70 VAC min, 300 VAC max)
6-95
Troubleshooting
Testpoints
GND, On = EQ sensor tripped
+5V,
+3.3V Board Query LED
EQ Board Reset
Fuse FCW
EQSP LED 1/4A, 250V, MDQ
On = EQ fault
Off = No EQ fault
ESS LED
On = Normal
Off = Seismic device tripped
+24VDC Testpoint
CW2 LED, On = CW String OK
CW1 LED, On = CW String OK
6-97
Troubleshooting
JP1
Test Points:
+1.5V TorqMax
+2.5V Interface
+3.3 B
+5V
DGND
RS 232 PC
Ethernet
3 = PC
Programming
port, factory
use only Ethernet
2 = SYSTEM
Ribbon cable to
Onboard Display Ethernet
1 = LAN
Internal CAN
IMP Flash
JP6
Internal CAN
CAN Trmnate
External CAN
AC 18V
Battery:
1/2 AA, 3.6V
Lithium Serial Hall
Call 1
Switches:
INSPECTION
UP
ENABLE
DOWN Serial Hall
CONTRLR. STOP Call 2
CAPTURE
TEST
FAULT BYPASS
WRITE ENABLE
LEARN Magnetek
C.DOOR BYPASS Interface
H.DOOR BYPASS
The ICE-IMP Main Processor Board provides central processing, data storage, control switches
and communication. The Onboard display and ICE-SAF boards plug into the ICE-IMP board.
6-99
Troubleshooting
6-101
Troubleshooting
Note
These faults do not necessarily mean that the problem is with the TM Triac. It is recommended
to first consult the iControl Messages table in the Troubleshooting section and follow the trou-
bleshooting tips for the message(s) displayed.
6-103
Troubleshooting
Signal Use
BKX1, BKX2 110VAC (typical) inputs to Low Current Brake Board rectifier.
Caution!
Blue terminals indicate low voltage (24V AC or DC) input.
Connecting 120VAC to these inputs will damage the board.
ICE-MIAC-24V
6-105
Troubleshooting
LST 670
8.2K
2.21K
LST 670
Output Connections
Connect outputs as shown in your job prints. Outputs may be configured (in specific groups) to
provide either a path to ground or current to drive indicator lamps/LEDs.
Output State Selection The outputs are divided into five groups. Each group shares a
common. The common may be wired to provide a current source or a path to ground. The
groups are:
Relays 1 4
Relays 5 8
Relays 9 16
Relays 17 - 24
Relays 25 - 32
The commons for the groups are determined by the connections made to board connector J5.
The appropriate connections are determined during the job survey. Each system is configured
before shipment. You need only connect outputs as shown on the job prints.
Common 25 - 32
Common 9 - 16 6
Common 5 - 8
Common 17 - 24
Common 25 - 32
1: Common
6-107
Troubleshooting
FMOR Fuse
6/10A, 250V, MDQ
+5V Testpoint
+24V Testpoint 18VAC
Board Query LED
24V OK LED 1 bus
On when iBox queries board
Active = Open
Active = Closed
Determined by iView settings
according to user requirements.
6-109
Troubleshooting
Rope Gripper
120VAC
RG1 Rope Gripper Power Supply
RG2
RG5 RG OK Safety A
120VAC
RG7 RG OK Safety B
Manual switch:
Open = manual operation, rope gripper disabled Closed = Rope Gripper Retracted
Closed = normal operation, rope gripper enabled Open = Rope Gripper Actuated
TACH ADJ.
trimpot
Power Input
1
-15VDC
+15VDC
GND
+5VDC
Motor Field
connections
Brake
connections
FIELD WIRING
AC/DC Drive
connections
DCC Filter
OFF
ON 6
J3 AC Drive
Encoder Output
Test Points
STP1
STP2
GND
To ICE-IRB Board
JP1
6-111
Troubleshooting
Switch Description
SW1 Serial Port switch: Setting for the Drive Serial Port (AC Drive / DC Drive). DC Drive set-
ting hard wired.
SW2 Encoder / Tach:
Encoder = AC drive with velocity encoder connected to AC drive.
Tach = DC drive or AC drive with velocity encoder connected to iBox VELOCITY inputs.
SW4 DCC Filter (ON / OFF) Default = ON, adds filtering to Drive Current Command output.
.
Table 6.26 iBox Field Connections on ICE-SAF Board
DP1- Negative going, -15V, digital pulse stream from iLand to iLink to iBox.
SHLD Shield connection for twisted-pair DP1+/DP1-
DP2+ Positive going, +15V, digital pulse stream from iLand to iLink to iBox
(DP2 leads DP1 when car moves down)
DP2- Negative going, -15V, digital pulse stream from iLand to iLink to iBox
SHLD Shield connection for twisted-pair DP2+/DP2-
A+ Positive going, +12V, digital pulse from motor velocity encoder. Please
refer to Tachometer or Encoder Installation and Wiring on page 2-23.
VELOCITY ENCODER
TX- iBox transmit, negative going serial communication stream from iBox to
iLink. Connects to iLink ICE-CTP Board terminal RX-.
SHLD Shield connection for twisted-pair TX+/TX-
RX+ iBox receive, positive going serial communication stream from iLink to
iBox. Connects to iLink ICE-CTP board terminal TX+. RX+ and RX-
comprise a differential communications pair.
RX- iBox receive, negative going serial communication stream from iLink to
iBox. Connects to iLink ICE-CTP board terminal TX-.
SHLD Shield connection for twisted-pair RX+/RX-
DZ Door Zone Sensor input. Activated = 110 VDC.
ULM Up Leveling Marker Sensor input. Activated = 110 VDC.
DLM Down Leveling Marker Sensor input. Activated = 110 VDC.
INCT Cartop Inspection Station INSP/AUTO Switch input. Activated = 110
VDC.
ICTU Cartop Inspection Station UP Button input (includes SAF button). Acti-
vated = 110 VDC.
ICTD Cartop Inspection Station DN Button input (includes SAF button). Acti-
vated = 110 VDC.
INCP COP Inspection Station INSP/AUTO Switch input. Activated = 110 VDC.
CAR
6-113
Troubleshooting
switch is made, there will be 110 VDC on this input. When the switch is
open, there will be 0 VDC on this input and the car will not run unless
INA is active and then only in response to the ABU or ABD input.
DCAT Door Contact Access Top input. When a top hoistway access is provided
(see INA, ATU, ATD, and DLAT), the hoistway door contact associated
with that landing is connected between the #3 bus and this input. When
the switch is made, there will be 110 VDC on this input. When the switch
is open, there will be 0 VDC on this input and the car will not run unless
INA is active and then only in response to the ATU or ATD input.
DCMS Door Contact Main String input. If top and bottom hoistway access (see
INA, ATU, ATD, ABU, and ADB) is not provided, all hoistway door con-
tacts are wired in series between the #3 bus and DCMS. When the
switches are made, there will be 110 VDC on this input. When any switch
is open, there will be 0 VDC on this input and the car will not run.
DCAB Door Contact Access Bottom input. When a bottom hoistway access is 6
provided (see INA, ABU, ABD, and DLAB), the hoistway door contact
associated with that landing is connected between the #3 bus and this
input. When the switch is made, there will be 110 VDC on this input.
When the switch is open, there will be 0 VDC on this input and the car
will not run unless INA is active and then only in response to the ABU or
ABD input.
GOV Governor input. The governor is connected between the #3 bus and this
input. When the governor switch is made, there is 110 VDC on this input.
It the governor switch trips/opens, there is 0 VDC on this input and the
car will not run.
SP 1 Spare input 1. If used, connect as shown in the job prints.
6-115
Troubleshooting
DIP Switches
+5V Testpoint Reset button
Ground Testpoint
Board Query LED
4-Character Display
of transmitted data
DIP Switches and Display The DIP switches and 4-character display are used for fac-
tory testing and diagnostics. For normal operation, all of the DIP switches are set to OFF
(down). The 4-character display shows direction and ascii floor number.
6-117
Troubleshooting
Bus Error
TP +9V indicator
FHCE OK
indicator
Fuse:
250V, 1/2A,
TP +5V AGC
TP +3.3V Network
Activity
indicator
Link Status
TP GND indicator
Digi Connect ME module
Ethernet cable connects here
.
Indicator Description
Bus Error ON = Communication problem
FHCE OK ON = Power to the board and fuse OK
Link Status Yellow indicator, ON = Network link is operational.
Network Activity Green indicator, ON = Network traffic detected.
Up / Down
buttons
Up / Down
indicators
Figure 6.20
For more information on setting the node board addresses, see Setting Node Board Addresses
on page 5-33.
6-119
Troubleshooting
I/O Connections
Connect inputs and outputs as shown in your job prints. SC-ION board inputs are always
117VAC. Outputs may be configured (in specific groups) to provide either a path to ground or
current to drive indicator lamps/LEDs.
Output State Selection The outputs are divided into three groups. Each group shares
a common. The common may be wired to provide a current source or a path to ground. The
groups are:
Relays 1 4
Relays 5 8
Relays 9 16
The commons for the groups are determined by the connections made to board connector J4.
The appropriate connections are determined during the job survey. Each system is configured
before shipment. You need only connect the inputs and outputs as shown on the job prints.
Board Addresses Each of the 16 inputs and 16 outputs on the board has an address on
the system bus. The addresses are assigned as indicated by the job survey before the system is
shipped. A software tool, running on a Windows platform, is used to set individual addresses
and also to set the address range (10-489 or 10-989) used for the job. To configure the board, a
Windows PC running the software tool must be connected to the board serial port.
COMP ON:
On = Computer on
Off = Computer resetting
6-121
Troubleshooting
Indicator Description
Drive Ready There are no faults and the drive is ready to run.
The drive has reached either the current or voltage limit set by the drive
Current Limit header and software parameters Armature current limit or Armature volt-
age limit (Configuration > Safety tab).
Low Line - WYE The voltage at the Wye connection of the drive isolation transformer sec-
Secondary ondary is below 30% of the rated value.
Low Line - Delta The voltage at the Delta connection of the drive isolation transformer sec- 6
Secondary ondary is below 30% of the rated value.
WYE P.R. The phase relationship of the Wye connection (Y1, Y2, Y3) is incorrect.
Delta P.R. The phase relationship of the Delta connection (X1, X2, X3) is incorrect.
300 P.R. The phase relationship between the Wye and Delta connections is incorrect.
Contactor or High The main contactor is not picked, or one or more of the high current fuses
Current Fuse Failure is open when the drive is enabled.
(SCR-LGA board) The PLL circuit has a problem of synchronization with the
PLL No Lock Delta connection from the AC line. This indicator will also turn on while the
controller is powering up and when the SCR-LGA board is being reset.
6-123
Troubleshooting
IZO Integrator Reset Status: Used to adjust the zero offset for the Current Loop Inte-
grator or the Voltage Loop Integrator.
TP1 Armature Differential: Hoist motor armature voltage = TPI volts x 100.
TP2 Armature Voltage (scaled): 10VDC = 100% of Drive armature voltage rating.
Actual armature voltage = Drive voltage rating x voltage at TP2 I 10 volts.
TP3 Armature Current (scaled): Measured in volts, 1.8 volts = 100% of Drive armature
current rating. Actual armature current = Drive current rating x voltage at TP3 I 1.8
volts.
TP3F Pure DC Armature Current: 1.8 volts = 100% of Drive current rating.
TP4 Line Frequency: Sine wave with frequency = line frequency (50 Hz or greater).
TP5 Direction of Current Flow: When drive is enabled, +15VDC = current flow from A2
to A1 and 0 VDC = current flow from A1 to A2. When drive is disabled, test point
indicates previous direction of armature current flow.
TP6 Current Loop integrator Output: 0.0 VDC when drive is disabled. Voltage at TP6
should not drift when the Pattern scaling parameter (Configuration > Pattern >
Common tab) = 0 and the drive is enabled.
TP17 Burst Enable: 720 Hz square wave with on-time of 300 microseconds A10%.
TP19 Fault Bus: 15 VDC = normal, 0 VDC = fault condition in the SCR drive.
TP20 Drive reset: 0.0 VDC = normal (Ready is ON), -15 VDC = drive is being reset.
Table 6.33 SCR-LGA Board Jumper Settings for use with iControl
JP7 A A = Low gain for current loop. B = High gain for current loop.
JP12 N/C N/C = Normal operation. Always use N/C setting for iControl.
JP17 A A = iControl setting. Loss of power at the Emergency Power Input causes a
signal to be sent to the drive which causes the drive to modify the PLL feed-
back gain so that the PLL circuit can tolerate frequency shift for faster
response.
6
6-125
Troubleshooting
Replacing Fuses
The 12-pulse drive has a total of 9 fuses. Of the 9, 6 are semiconductor fuses (FL1 - FL6, one on
each input line terminal for a 6 phase transformer). These semiconductor fuses are located
above the contactors, under the drive cover. The 12-Pulse Drive also has 2 fuses (FD1, FD2) pro-
tecting the 120VAC line. FD1 and FD2 are located on the left side of the controller in panel
mounted fuse holders. Fuse FD3 protects the commutation circuit. FD3 is located near the top
of the drive under the cover.
Caution
The fuse ratings for the 12-Pulse Drive have been calculated to provide the best protection.
DO NOT replace fuses with a higher rated fuse than the one specified in this manual.
NEVER bypass a fuse with a direct short.
6-127
Troubleshooting
The semiconductor fuses (FL1 - FL6) are rated at 200 Amps, 500 Volts. Before removing or
replacing a fuse, ensure that all power is OFF. The cover of the 12Pulse SCR Drive must be
removed to access the semiconductor fuses.
1. Remove the two screws that hold the fuse in place (see the illustration). When removing
screws, make sure that no loose parts (bolts, screws, or washers) fall into the drive.
2. Install the replacement semiconductor fuse. Replace the screws.
3. On the SCR side of the fuse, torque the screw to 22-30 inch pounds. On the Contactor
side of the fuse, torque the screw to 140-150 inch pounds. Ensure that no loose parts are
left in the drive enclosure.
FD1 protects the power supply and the trigger transformer. FD2 protects the two fans. Both
fuses are 1 Amp, 250VAC Slow Blow. Do not use a fuse with a different rating. The fuses are
located on the left side of the drive enclosure.
1. Press in and turn the cap counter-clockwise to remove the fuse. Replace if necessary.
Continual failure of a fuse may indicate an underlying problem.
6-129
Troubleshooting
Fuse (FD3) protects the commutation circuit. The cover of the drive must be removed. FD3 is
located on the top of the drive above the swing tray. The fuse is a KLKD type rated at 30 Amps
DC at 600VAC. Do not use a fuse that has a different rating.
Replacing Contactors
The 12-Pulse Drive has two main contactors located at the bottom of the enclosure. The left con-
tactor is used to terminate Delta phases (X1, X2, X3) from the 6 phase transformer. The right
contactor is used to terminate Wye phases (Y1, Y2, Y3).
Replacing Auxiliary Contactors There are two auxiliary contactors on each main
contactor. The auxiliary contacts open or close 120VAC lines when the main contactor is picked.
The auxiliary contactors are attached to the right and left sides of the contactor. Mark wires for
identification before removing them. It is VERY IMPORTANT that the wires are reconnected
to the correct terminals.
Danger
Before working on the 12-Pulse Drive, ensure that all power going to the drive is OFF. Be
sure that power to the Drive Isolation Transformer is OFF at the main disconnect.
6-131
Troubleshooting
2. Loosen the two screws on the right and left side of the auxiliary contactor and remove it
by pulling out and away from the main contactor.
3. Install the new auxiliary contactor. Make sure that the auxiliary contactor pin is inserted
into the body of the main contactor.
4. Replace the mounting screws (torque to 4 IN LBS.).
5. Reconnect the wires. Note: Load the outer-most terminals first.
6-133
Troubleshooting
Replacing the 12 Pulse Bridge SCRs (SCR1 - SCR6) Be sure to mark all
wires for identification before removing them. They must be correctly replaced.
1. Remove the semiconductor fuse attached to the SCR device being replaced.
2. Remove bus bars G and H.
3. Loosen and remove the screws in terminals 2 and 3 on SCR1 - SCR6. (The terminal
number is on top near the left side of the SCR pack.)
4. Remove bus bars A and B and the connecting wires from the SCR-SN board.
5. Remove the mounting screws and the leads that go to the Firing board (SCR-DS)
6. Remove the heatsink gasket.
7. Clean the surface of the heatsink where the SCR device is to be placed. There cannot be
any foreign matter between the SCR and the heatsink.
8. Install the SCR device, heatsink gasket, and mounting screws. Torque the mounting
screws to 40-48 inch pounds.
9. Install the standoff (M6 x 16MM, 41-04-0036) and the split washer (1/4", 19-04-0013).
Torque the standoff to 22-30 inch pounds. Note: Over-torquing will damage the stand-
off.
10. Reinstall bus bars A and B and the connecting wires.
11. Torque the screws to 40-48 inch pounds. Ensure that the shaft of the ring lug stays over
the bus bar it is attached to. The ring lug should not touch the other bus bar. To main-
tain clearance, the ring lug cannot pass the edge of the bus bar.
12. Reinstall semiconductor fuses and bus bars G and H.
6-135
Troubleshooting
1. Remove the bolts on terminals 1, 2, and 3 of the SCR being replaced. Place the bus bars
that connect to the SCR so that they will not obstruct removal and replacement.
2. Remove the SCR.
3. Clean the area where the SCR will be placed. Spray a thin layer (0.001 approximately) of
Thermal compound to the component surface contact area.
4. Install the SCR. Torque the mounting screws to 2230 inch pounds.
5. Reconnect all wires and bus bars to the correct terminals. Torque bolts 1, 2, and 3 on the
SCR to 106132 inch pounds.
Table 6.39 Replacement Parts for Direction Bridge and Dynamic Braking
Commutation SCR/Diode and Dual Diode Device To gain access to the Com-
mutation SCR/Diode and Dual Diode Device, the SCRDS board must be partially removed.
We suggest you leave the connections on the bottom of the board connected and remove only
the mounting screws.
1. The SCR-DS board is directly over the Commutation SCR. This means that the SCR-DS 6
board must be moved into a position that will not interfere with the removal or installa-
tion of the commutation SCR. Refer to Replacing the SCR-DS board.
2. Label all the wires connected to the device being removed before disconnecting them.
3. Note the orientation of the device, then remove it and clean the surface of the SCR
mounting plate.
4. Install the new device. Torque the mounting screws to 22-30 inch pounds.
5. Reconnect all wires. Torque the terminal screws to 22-30 inch pounds.
6. Reinstall the SCR-DS board.
6-137
Troubleshooting
Table 6.40 Replacement Parts for Commutation SCR/Diode and Dual Diode Device
Replacing PC Boards
There are a total of 6 boards (SCR-LGD, SCR-LGA, SCR-PS, SCR-SN, SCR-DS and SCR-CC) in
the System 12 SCR Drive. While replacing boards, other parts may require removal. Ensure that
all power is OFF at the main disconnect before removing boards.
Replacing the SCR-LGD Logic Display Board The SCR-LGD board displays the
status of the System 12 Drive.
Replacing the SCR-LGA SCR Drive Logic Board When replacing the SCR-LGA
board, the SCR-LGD board must be transferred from the old SCR-LGA board to the new board.
This is best done when both boards are detached from the drive. The transfer includes installing
the standoffs needed to hold the SCR-LGD. The standoffs are loaded from the back of the SCR-
LGA board.
Figure 6.32 Replacing the SCR-LGA Board
6-139
Troubleshooting
1. Disconnect all connections to the board (J1-J10 and the ribbon cable ground wire
attached to the bottom right corner mounting screw).
2. Remove the mounting screws and the board. Ensure that no loose parts fall into the
drive.
3. Install the new board and torque the mounting screws to 15-20 inch pounds. Please
refer to SCR-LGA Board Jumper Settings for use with iControl on page 6-125 and see
SCR-LGA Board Layout on page 6-126.
4. Reinstall the board connectors (J1-J10 and the ground wire). Ensure that the bottom
right corner mounting screw is torqued to 15-20 inch pounds.
Replacing the SCR-PS Board Only The SCR-PS board supplies DC power to the
SCR-LGA board. Ensure that the new SCR-PS board is generating the correct DC voltage before
connecting it to the SCR-LGA board. Please refer to Replacing the SCR-LGA SCR Drive Logic
Board on page 6-139 for an illustration.
1. Disconnect the ribbon cable from SCR-LGA board J9 and remove the 6 position IDC
from J1 on the SCR-PS board.
2. Remove the mounting screws and remove the board.
3. Install the board and torque the screws to 15-20 inch pounds.
4. Connect the ribbon cable from the SCR-PS board to J9 on the SCR-LGA board. Recon-
nect the 6 position IDC to J1 on the SCR-PS board.
5. Test the SCR-PS board for the correct voltage:
Disconnect the ribbon cable from J9 on the SCR-LGA board.
Turn ON power to the enclosure at the main disconnect. Ensure that the controller is
on Inspection.
Using a DC voltmeter, verify +5V, -5V, +15V, and -15V on the test points on the SCR-
PS board. If the voltages are not within 1% of the correct value, adjust the following
on the SCR-PS board: R16 for +5V, R2 for -5V, R13 for +15V, or R5 for -15V.
Turn power OFF at the main disconnect. Reconnect the ribbon cable to J9 on the SCR-
LGA board and turn power ON at the main disconnect.
Replacing the SCR-SN Board Removing the SCR-SN board requires that a few wires
be disconnected. Label the wires to ensure they can be reconnected correctly. The right angle
copper brackets and the insulator on the SCR-SN board must be transferred to the new board.
This is best done when both boards are detached from the drive. The swing tray that holds the
SCR-LGA and the SCR-PS board must be removed to make it simpler to remove the SCR-SN
board. Do not disconnect the boards from the tray; remove the tray with the board on it.
6-141
Troubleshooting
1. Remove the semiconductor fuses and the ribbon cable from J2 on the SCR-LGA board.
2. Disconnect the wires attached to terminals 2 and 3 on SCR1 through 6 in the drive.
3. Remove the three mounting screws on top of the SCR-SN board and remove the board.
Transfer the angle brackets (35-30-0009) to the new board. Lightly tighten the screws.
4. Install the new SCR-SN board and install the mounting screws (19-01-0012) and flat
washer (19-04-0004). Torque the mounting screws to 15-20 inch pounds.
5. Connect the wires as indicated below. Torque the M6 machine screws to 40-48 inch
pounds. Ensure that the ring lug does not cross the outer limits of the bus bar. To ensure
proper clearance, the space between bus bars A and B must be maintained.
Note: The terminal number is on the top left side of the SCR pack near the terminal.
Wire from E1 to SCR1 terminal 2
Wire from E3 to SCR2 terminal 2
Wire from E5 to SCR3 terminal 2
Wire from E7 to SCR4 terminal 3
Wire from E9 to SCR5 terminal 2
Wire from E11 to SCR6 terminal 2
Wire from E2 to SCR1 terminal 3
Wire from E4 to SCR2 terminal 3
Wire from E6 to SCR3 terminal 3
Wire from E8 to SCR4 terminal 2
Wire from E10 to SCR5 terminal 3
Wire from E12 to SCR6 terminal 3
6. Install the semiconductor fuses (see Replacing the Semiconductor Fuses) and tighten
the screws that attach the copper bracket to the SCR-SN board.
7. Reinstall the swing tray that holds the SCR-LGA and SCR-PS board.
M6 Mach. Screw (M6 x 16MM Mach. Screw) 35-74-A5FT Set (30 EA.)
Replacing the SCR-DS Board The SCR-DS board contains the SCR firing leads that
attach to the SCR devices. Handle these wires with care. In some cases, the SCR-DS board does
not require complete removal. Partial removal consists of removing all of the items stated below
except the cathode and gate connectors on the bottom of the SCR-DS board, the 6 phase wires,
and the A2 wire.
6-143
Troubleshooting
Replacing the SCR-CC H/L Board To gain access to the SCR-CC-H/L board, the
SCR-DS board must be removed. Label the wires you disconnect so they can be reconnected
correctly. The three studs (X1, A, AX) on the board should be torqued with care.
1. Label and disconnect the wires on the studs (X1, A, AK) and J1 of the SCR-CC-H/L
board.
2. Remove the mounting screws and the board.
3. Install the new SCR-CC board and torque the mounting screws to 15-20 inch pounds.
4. Install all the wires that connect to J1.
5. Reconnect the wires to the studs (X1, A, AK). Torque the nuts to 22-30 inch pounds.
6. Reinstall the SCR-DS board.
6-145
Troubleshooting
7-1
iBox Front Panel Controls
1 2 3 4
ENTER
COMPUTER UP SAFETY OK
SAFETY A DRIVE ON DOORS LOCKED
SAFETY B DOWN INSPECTION
CARTOP RUN IN GROUP
CONTROLLER FAULT/FUNCTION
System Control Switches
INSPECTION STOP BYPASS
F3 F3HA F2MC
Typically, when you need to view or change parameters in an iControl, you connect to the iBox
through the PC or LAN ethernet port and use the iView graphical user interface running on a
Windows OS PC to easily access, view, or edit any desired parameter. However, during initial
system setup when setting the parameters that allow PC access to your system, or when a PC is
not available, some parameters can be directly accessed and edited through the keypad and
LCD display located on the front panel of every iBox.
LCD Display
Directional Arrows /
1 2 3 4 Value Incrementers
Select Parameter /
Enter Value
ENTER
7-3
iBox Front Panel Controls
Keypad Controls
Keypad controls include:
Display Contrast adjusts the LCD display
Computer Reset resets the iBox computers
Fault Reset initializes the fault list
Softkeys selects the associated topic across the bottom of the LCD display
Up Arrow moves the selection bar up or increases a parameter value
Down Arrow moves the selection bar down or decreases a parameter value
Left Arrow moves the cursor left (digit selection)
Right Arrow moves the cursor right (digit selection)
ENTER confirms a selection or enters a parameter value
LCD Display
The LCD display allows you to view iBox parameters. The @003 s 015 FG RO L03
top line of each display screen provides a status snap- Passenger
shot for the car associated with the controller. In our
example: Ofpm
2:26:22AM
@ (door zone)
11/30/2003
@: in door zone
: below door zone Car Mgmt
+: above door zone
003 current floor
s or t (direction arrows)
015 next floor
F (front doors)
G Open
OClosed
Opening/Closing
Invalid door position
R (rear doors)
G Open
O Closed
Opening/Closing
Invalid door position
S or L (Simplex or Local)
03 (Car ID)
The second line of the display shows the mode of operation (Passenger in the example) dis-
played in rotation with any active status or error messages.If a soft key is pressed (Car or Mgmt)
the remaining display lines change to display appropriate information. The labels in the bottom
line change to indicate the function of their associated soft key.
Parameter Entry
To edit or view a parameter, you select a broad topic by pressing the Enter soft key, then select
and view or edit a parameter. For example, to change or edit a Car-associated parameter.
1. Press the soft key (1) beneath the Car label. The @003 s 015 FG RO L03
LCD will change as shown to the right. Passenger
2. Use the arrow keys to scroll to a topic. Network Setup
3. With the topic selected (Network Setup in our View Event Log
example), press ENTER. View/Register Calls
Set Time/Date
Note that the soft key labels have changed: Fiew Factory Data
Home Back PgUp PgDn
Home Returns you to the home screen.
Back Takes you back one screen.
PgUp When there are more topics than can be listed on a single screen, PgUp moves you
up the list a full screen at a time.
PgDn When there are more topics than can be listed on a single screen, PgDn moves you
down the list a full screen at a time.
4. Use the arrow keys to scroll to a topic.
5. With the topic selected, press ENTER.
When you press ENTER, the display updates. The cursor/arrow indicates a parameter can be
edited.
8. Use the left/right arrow keys to position the arrow below the number to be changed.
9. Use the up/down arrow keys to increment or decrement the value.
10. Repeat positioning and incrementing/decrementing as necessary. Press ENTER to enter
the new value.
11. The soft key labels will indicate Save and Cancel. Press Save to save your changes after a
yes or no acknowledgement.
or,
7
12. Press Cancel to leave the screen without saving your changes (after a yes or no acknowl-
edgement).
7-5
iBox Front Panel Controls
Car Mgmt
Network Setup
There are three Ethernet ports on the iBox.
#1 is the Local Area Network connection used to connect Group and Elevator controllers to your
Local Area Network.
#2 is the MCE equipment connection used to interconnect Group and Elevator controllers for
equipment control purposes.
#3 is the PC Direct connection used to connect a PC directly to a Controller for immediate access.
Network setup parameters allow the IP information to be set for each of the three ports. Addition-
ally, an FTP User Name and Password must be set here without which the File Transfer Protocol
server may not be accessed.
There are many websites that are helpful in learning about TCP/IP.
7-7
iBox Front Panel Controls
View/Register Calls
The View/Register Calls dialog allows you to send transport commands to the controller.
To View/Register Calls:
Allows you to enter car and hall calls for Front or Rear Car Operating Panels.
Set Time/Date
This parameter sets the real time clock for the controller.
MAC Addresses:
A six-byte, unique, identifying code used by LANs to positively identify communicating equipment.
This parameter allows you to view the MAC address for each of the three Ethernet ports.
Manufacturing Info:
View the controller serial number, revision, and ICE-IMP information.
Version Info
Version Info provides version information for the software currently installed on your controller.
Version Info:
View the software version information for the controller and car top processors.
Note
The Group ID setting in iView determines the iCue System IP address at which iCue will accept
messages. NO NOT set the Group ID to a setting other than 1 unless instructed to do so
by MCE. Group IDs other than 1 are reserved for future use and will cause group-to-car commu-
nication to fail. If you need advanced System addressing information, please contact MCE.
7-9
iBox Front Panel Controls
IP Address Verification/Setting
You should not need to change the factory-set IP information. If you are having problems con-
necting to an iBox Ethernet port, verify that IP information is correct as described here. If you
find an incorrectly set port, these instructions will help you correct it. These instructions are for
Port 1 but the procedure is the same for all iBox ports.
1. Press the soft key (1) beneath the Car label. The @003 s 015 FG RO L03
LCD will change as shown to the right. Passenger
2. With Network Setup selected, press ENTER. Network Setup
3. Scroll down to IP Address 1, press ENTER. View Event Log
View/Register Calls
4. Verify that the Address displayed is correct (see
Set Time/Date
preceding table). For example, Car A of Group 1
View Factory Data
should be 192.168.191.001. Home Back PgUp PgDn
5. If you are using the default addresses, and the
address displayed is incorrect, set it according to
the table using Left and Right arrow keys to select a number and Up and Down arrow
keys to change the value. Continue until the address is correct, then press ENTER. Press
SAVE to save your changes (if any).
6. Scroll down to IP Gateway 1. The default for the #1 Port is 192.168.191.254. (The default
for the #2 and #3 Ports is 000.000.000.000) If necessary, change it as described above.
7. Scroll down to IP Subnet Mask 1. The default is 255.255.255.000. If necessary, change
as described above.
8. Continue as above to verify the IP information for the #2 and #3 Ports respectively.
Check the preceding table for factory default addresses.
COMPUTER UP SAFETY OK
SAFETY A DRIVE ON DOORS LOCKED
Note
These displays are frequently used when the elevator controller is being configured. Please refer
to Sections 3 and 4 of this guide for use descriptions.
7-11
iBox Front Panel Controls
Car Mgmt
Hoistway Door Bypass: Switch used to bypass the hoistway door electric contacts (Bypass
position). When set to Bypass, the car will run only on Inspection mode. The ability to set
this bypass must be enabled at the factory and is only available if allowed by safety regula-
tions in your area. Check the iView Safety Configuration screen to see if the feature is
enabled in your installation.
CONTROLLER FAULT/FUNCTION
INSPECTION STOP BYPASS
INSP RUN ON
OFF OFF
OFF OFF
OFF OFF
Note
These control switches are used when the elevator controller is being configured. Please refer to
Sections 3 and 4 of this guide for use descriptions.
When installed, the Safety Bypass jumper electrically connects the SB and 3 terminals on the 7
IRB Relay Board. Information about the Safety Bypass jumper is in Section 6 of this guide (see
Safety String Bypass Jumper on page 6-3).
Danger
The fuses and the bypass jumper expose dangerous high voltages that can cause bodily
harm or death. ONLY TRAINED, AUTHORIZED PERSONNEL should have access to these
areas.
7-13
iBox Front Panel Controls
Using iView
About iView
iView is a graphical user interface running on a Windows PC or laptop computer.
The computer may be connected directly to the iBox PC Ethernet port or, through a
Local Area Network, to the iBox LAN ethernet port. Using iView, you can quickly
and easily:
View and adjust all user-configurable controller parameters (see page 8-17).
Diagnose performance issues on location, from a remote site, or both.
Work in an offline file, then upload data to a controller (seepage 8-23).
This section provides a detailed description of iView. iView on-line Help provides even greater
detail and is updated whenever a software revision is released. This section contains:
How iView Works (see page 8-2)
Getting Started (see page 8-4)
LAN Connections (see page 8-13)
Working Online (see page 8-17)
8
Saving Parameters to a Configuration File (see page 8-20)
Saving Default Parameters to a Configuration File (see page 8-21)
Loading Parameters from a Configuration File (see page 8-22)
Working Offline (see page 8-23)
Accessing Online Help (see page 8-24)
iView Windows and Tabs (see page 8-25)
Resizing Windows & Docking/Undocking Windows (see page 8-34 & page 8-35).
Updating Controller Firmware (see page 8-41).
8-1
Using iView
Because iView communicates with elevator controllers through an Ethernet connection, a single
PC can be used to administer multiple elevators or even multiple groups of elevators (with each
group operating under the direction of a group dispatcher). Elevator adjusters who service mul-
tiple sites will find it convenient to connect directly to a controller, then easily upload proven
settings from a file on their hard drive to the controller. The diagram below illustrates just a few
of the ways Ethernet connectivity allows iView to communicate with elevator controllers.
iBox elevator controllers
Hub or Router
Hub or Router
PC
PC to local modem, through phone lines to site
modem, through Local Area Network (LAN).
PC
Directly to the iBox PC Ethernet port (3).
Installing iView
If you purchased your iView PC from MCE, iView was installed at the factory. If not, you will
need to install iView from a CD-ROM or other source. Minimum requirements for the iView PC
are:
At least 1GB free hard drive space for installation
Minimum 256MB RAM
Windows 2000 or XP operating system
CD-ROM drive
10/100 Ethernet capable
Simple text or comparable text editing software
8-3
Using iView
Getting Started
There are two ways to connect the iBox to a PC:
Direct Connection: Connect the PC directly to the iBox through the iBox 3 = PC port.
Peripheral LAN Connection: Connect the PC to the LAN hub supporting one or more iBox
controllers (iBox 1 = LAN port). (This hub is part of the iCue/iCentral installation.)
Connections are stored in the iControl Connections folder. To make a LAN connection, you
launch iView, click File > Connection > Open and double-click the connection you wish to open.
If the connection has not yet been created, you will need to create it as described in this section
before you can connect to the controller. Please refer to Creating a New LAN Connection on
page 8-13 if you need to create a connection. When entering addresses on a PC, do not use lead-
ing zeros, i.e., .020 is entered as .20. (When entering IP addresses through the iBox keypad,
leading zeros are required.)
About LANs: LAN stands for Local Area Network. A LAN is basically several computers
(or smart equipment with a computer inside like the iBox or iCue) all connected at a common
point (the hub) so they can communicate with each other. In order for a message from one com-
puter to reach the computer (or iCue/iBox) it wants to talk to, all the computers connected to
the LAN have to have their own unique address. The address is called a TCP/IP number. The
table below lists iControl default IP addresses. Your job prints provide specific instructions as to
how all of your IP addresses are set.
Note
The Group ID setting in iView determines the iCue System IP address at which iCue will accept
messages. NO NOT set the Group ID to a setting other than 1 unless instructed to do so by MCE.
Group IDs other than 1 are reserved for future use and will cause group-to-car communication
to fail. If you need advanced System addressing information, please contact MCE.
Direct Connections
Unless a Local Area Network (Ethernet) hub has already been installed, you will find it easiest
to connect a PC to the iBox using the 3 = PC port on the iBox (direct connection). To make a
direct connection:
1. Connect the iView PC to the controller 3 = PC port using only a standard Ethernet cable.
(Do not connect the #3 port through a hub or router.)
Figure 8.1 Ethernet Cable and iBox Ethernet Ports
1 = LAN 2 = System 3 = PC
Direct (no hub) connection to
PC only
Note
The iBox 3 = PC Ethernet port address, gateway, and mask are set to default values by MCE. If
you have used your PC to connect to other iBoxes, you probably only need to connect the cable,
launch iView, and select the connection with the appropriate IP information and use that to
connect. When creating direct connections in the iView connections folder, it is a good practice
to name them clearly so they are easy to distinguish (i.e., CarA Direct). The instructions here
are intended to help a first-time user make a direct Ethernet connection between a PC and the
iBox.Please refer to System and LAN Ethernet on page 11-15 for more detail.
8-5
Using iView
Note
8. In the Local Area Connection Properties dialog, select Internet Protocol (TCP/IP).
9. Click Properties to open the Internet Protocol (TCP/IP) Properties dialog.
8-7
Using iView
10. Set the IP Address to match the iBox EXCEPT FOR the last set of numbers. The #3 iBox
port is defaulted to 192.168.193.1. Typically, you can set your PCs IP address to
192.168.193.2.
Note
Note
It is important that the PC have only one IP address assigned. Click the Advanced button and
verify that the PC is configured for only a single IP Address (192.168.193.2). If there is more
than one IP Address, highlight the additional IP Address and then click Remove.
Creating a Direct Connection in iView Once you have set your computer TCP/IP
as described previously, you need to create a connection in iView.
1. Double-click on the iView icon on your computer screen to launch iView.
2. Click File on the menu bar.
3. Select Connection and click New to open the Connection dialog.
8-9
Using iView
Connecting to the iBox Once the connection is created and saved, you are ready to
connect.
3. To connect to a controller, double click the desired connection or select the connection
and click Open.
8-11
Using iView
LAN Connections
In most installations, there will be at least one iView PC continuously connected to the Local
Area Network on which the iBox controllers reside. LAN TCP/IP addresses and associated set-
tings for any hubs, routers, or other equipment involved are resolved when network equipment
is installed. In these instances, the iView PC is already connected through the network to the
controllers.
Creating a New LAN Connection
A controller connection must be created before it appears in the iView Connections folder. This
is typically completed at the factory, before the system is shipped (if your PC was purchased
through MCE). Creating a new LAN connection is similar to creating a new Direct connection.
To create a LAN connection:
1. Double-click on the iView icon on your computer screen to launch iView.
2. Click File on the menu bar.
3. Select Connection and click New to open the Connection dialog.
8-13
Using iView
8. Enter a File name for this connection in the Save As dialog (the Connection automati-
cally suggested).
9. The suggested (default) location for connections is the Connections folder (My Docu-
ments > Motion Control Engineering > iView > Connections). You may choose another
location using standard windows methods. You may also create sub-folders inside the
iController Connections folder in which groups of connections can be stored.
10. Click Save to save the connection.
Connecting to the iBox Once the connection is created and saved, you are ready to
connect.
3. To connect to a controller, double click the desired connection. The connection will take
a moment or two to establish, then a main screen will appear.
Note
8
The default location for connection (.conn) files is the Connections folder (My Documents >
Motion Control Engineering > iView > Connections). The default location for configuration
(.cfg) files is the Configuration folder (My Documents > Motion Control Engineering > iView >
Configuration). If you want to work online, connected to a controller, select Connection > Open
from the File menu. Connection (.conn) files will be displayed in the Open dialog. If you want to
work in an offline configuration file, select Configuration File > Edit from the File menu. Con-
figuration (.cfg) files will be displayed in the Open Configuration File dialog. Refer to the Work-
ing Online and Working Offline topics later in this section for more information.
8-15
Using iView
Editing an Existing LAN Connection You can edit existing LAN connections:
1. Click Edit on the File > Connection
menu.
2. The Open dialog is displayed. Double
click the connection you wish to edit.The
connection dialog is displayed. Click in
any field and correct the information you
wish to edit.
3. Click OK.
Delete an Existing LAN Connection You can delete an existing connection from the
iControl Connections folder:
1. Select Edit on the File > Connection menu.
2. The Open dialog is displayed. Right-click on the connection you wish to delete.
3. Select Delete from the popup menu.
4. A warning dialog will appear. Click Yes to delete the connection or No to cancel without
deleting.
Working Online
Working Online means that you are connected to an iController and are viewing or adjusting its
parameters. To work online, select Open from File > Connection menu and double click the
desired connection in the Open dialog.
When the connection is established, the Operational Status tab and Hoistway window are dis-
played with the Controllers connection name on the top left side of the title bar.
8
When working online, you may:
8-17
Using iView
8-19
Using iView
Using configuration files to store settings on a hard drive, USB Flash Drive or other storage
media provides some great capabilities:
Working Offline: Using iView, you can open a file and work with its settings without neces-
sarily having access to the controller itself.
File Uploading: When connected to a controller, you can choose to get some or all of the
settings in a configuration file and send them to the controller.
Adjuster Portability/Flexibility: Elevator adjusters can store configuration files associated
with all the controllers they service on their laptop PC. They can edit values offline, then
coordinate with on site, machine room personnel to connect and upload those changes to
the controller through the elevator Local Area Network or, through modems, DSL, T1 or
other internet connections, from virtually anyplace in the world.
Archiving controller data for future use.
You create configuration files by saving controller parameters to a file while you are working
online.
Save to File
While connected to a controller, you can easily save all controller parameters to a configuration
(.cfg) file.
8-21
Using iView
Working Offline
Working offline means that you are not connected to a controller but are working with a config-
uration (.cfg) file. You must have previously created the configuration file by saving it while
working on line with a controller. Please refer to Saving Parameters to a Configuration File on
page 8-20. To work offline:
1. Launch iView.
2. Select Edit from the File > Configuration menu.
3. The Open Configuration File dialog opens. Double-click or select the desired configura-
tion file and click Open. The .cfg extension indicates that this is a configuration file used
when working off-line.
4. A top level screen resembling the controller screen will appear. The title bar of the
screen displays the path and file name. You access the parameter screens and edit
parameters just as you do online. However, you cannot send parameters to a controller
while offline. Please refer to Loading Parameters from a Configuration File on page 8-
22.
Note
While working offline you will not be able to view some real-time data screens such as Hoistway
and Floor Heights.
To copy a configuration file: You may not want to modify the original configuration
file. Instead, you can make a copy of the original and then edit the copy.
1. Click the Start button.
2. Click My Documents.
3. Double click the Motion Control Engineering folder.
4. Double click the iView folder.
5. Double click the Configurations folder.
6. Select the configuration file and click Copy this file in the File and Folder Tasks list.
7. Select a location from the Copy Items dialog and click Copy.
8. Right click the copied file and select Rename.
9. Type the new name and press Enter.
10. From the File menu in iView, select Configuration > Edit. 8
11. Select the file from the Open Configuration File dialog and click Open.
12. Edit and Save the file.
8-23
Using iView
Context Sensitive Help You can view On-line Help information about any screen or
tab by pressing function-key one (F1) while a screen or tab has focus. Do the following:
Click the title bar of a window, e.g., the Hoistway window, to bring focus to the window.
The background color of the windows title bar darkens indicating that the window has focus.
Then press the F1 key. iView Help will display the topic that describes the window.
Click a tab (title). An outline will appear around the tab title indicating that the tab has
focus. Then press the F1 key. iView Help will display the topic that describes the tab.
Context Sensitive Event Help The Controller logs status and error information in
the Event Log (see Diagnostics - Diagnostic Outputs on page 9-14). To view the Event Log,
Event Properties and Context Sensitive Event Help:
1. In the Controller view, click View > Diagnostics > Event Log to display the Event Log.
2. Double click an event in the Event Log to display the Event Properties dialog.
3. Click the Help button in the Event Properties dialog to display the Troubleshooting Tips
dialog which provides a description of the event, an indication of what action is taken,
and troubleshooting tips if appropriate.
Help Viewer iView On-line Help provides three additional ways of locating information.
The Contents and Index tabs let you find general information. The Search tab lets you look up
specific words or phrases.
To start iView On-line Help:
1. On the iView menu bar, click Help.
2. On the Help menu, click iView Help. The help viewer is displayed. Use the Contents,
Index or Search tabs to locate the desired information.
1. While in Controller view (see Selecting Controller View on page 9-1), select the desired
tab from the View > Configuration menu.
2. Display all of the Configuration tabs by selecting Configuration from the View > Layouts
menu. Then click the desired configuration tab.
1. Select the desired tab from the View > Diagnostics menu.
2. Display all of the Diagnostic tabs by selecting Diagnostics from the View > Layouts
menu. Then click the desired diagnostics tab.
Additional Windows
8
Additional windows can be accessed from the View menu. They include:
Data Trap
Hoistway
Outputs
Safety Tests
Virtual Oscilloscope
8-25
Using iView
Specific contents will vary depending on the hardware installed at your site and on the revision
level of your iView and iBox software. Always refer first to the online help available within
iView. Online help contains the most detailed and current information about your iView soft-
ware. For detailed parameter or display descriptions, refer also to Section 9 of this manual.
Table 5.2 lists the items on the View menu and tables 5.3 through 5.5 list the tabs found on the
Configuration, Diagnostics and Setup menus. Click the see page links to jump to that page.
Window Content
Configuration Parameter settings are displayed and may be changed on the Configuration tabs.
The tabs include Brake, Car Operation, Drive, General, I/O Board, Load Weigher,
Motor Field, Pattern, Safety, Serial I/O Simplex Configuration, Simplex Security,
Terminal Switches and Timer Tables (see page 9-25).
Diagnostics The Diagnostic tabs contain information about the status and condition of the con-
troller. The tabs include Diagnostic Outputs, Event Log, Fault Bypass, Operational
Status and Terminal Switches Status. Three additional diagnostic screens, Data
Trap, Diagnostic Outputs and Virtual Oscilloscope, are displayed each in their own
window. This allows them to be used with other windows (see page 9-11).
Setup The Setup tabs are used to perform the automatic and semi-automatic setup pro-
cedures. The tabs include Brake, Counterweight, Drive, Feed Forward Gain, Floor
Heights, Floor Offsets, Load Weigher, Motor Field, Safety, Synthetic Speed and
Terminal Switches (see page 9-157).
Hoistway A graphical representation of the car in the hoistway, including assigned car and
hall calls. Shows the current mode of operation, direction preference, speed and
actual floor height information (see page 9-4).
Safety Tests Automated control of acceptance test procedures (see page 9-172).
Layouts Pre-programmed screen layouts can be displayed. Custom screen layouts can be
created and saved and displayed (see page 9-173).
8-27
Using iView
Tab Content
Brake Calibrate the brake voltage settings (see page 2-57 and page 9-157).
Counterweight Learn the position where counterweight is adjacent to the car (see page 3-28 and
page 9-158).
Drive Learn the values for the Drive Offsets (see page 2-49 and page 9-159).
Feed Forward Gain Determine a starting value for the Error Compensation parameter on the Configuration
> Drive > Control tab. The objective is to determine the minimum value that should be
used. The optimum value will be between 100% and 150% of calibrated value
(see page 4-15 and page 9-160).
Floor Heights Learn the absolute floor positions (distance to each floor from the lowest landing). Also
used to assist in measuring and entering the floor offsets (deviation of floor magnet
position from actual floor stopping position) (see page 4-2, page 4-27, page 9-161
and page 9-164).
Load Weigher Learn the car empty and full load weights (see page 4-37 and page 9-165).
Motor Field Calibrate the motor field voltages (see page 2-53 and page 9-165).
Safety Verify that the configurations of the main and safety processors match. Perform the
Inventory learn procedure (see page 9-166 and page 9-169).
Synthetic Speed Determine the values for the Voltage safety calibration and Current safety calibration
parameters (Calibration > Drive > Safety tab) which, in conjunction with the Following
error and Tach failure parameters and Speed feedback, are used to determine when a
Tach Failure fault should be generated (see page 4-13 and page 9-170).
Terminal Switches Learn the speeds and positions of the normal and emergency terminal switches (see
page 4-11 and page 9-171).
Tab Content
Call Allows you to register car and hall calls. This control is accessed by clicking the Call
Registration Registration button on the button bar (see page 9-174).
Firmware Update Guides you through the process of updating iControl firmware. This control is accessed
by selecting Firmware Update from the File menu (see page 8-41).
Refresh Updates the information displayed on iView windows and tabs. This control is accessed
by clicking the Refresh button on the button bar.
8-29
Using iView
Controller - Layouts
With iView, you can move and size tabs to suit the task to be performed. When you find a partic-
ular arrangement to be useful, you can save it as a custom layout (View > Layouts > Save as).
You can then display that layout at any time by selecting your custom lay0ut from the View >
Layouts > Custom menu.
Some useful layouts have been pre-programmed and are supplied with iView. They include:
Configuration: This layout displays all of the configuration tabs for easy selection.
1. While in System view (see Selecting System View on page 10-1), select the desired tab
from the View > Configuration menu.
2. Display all of the Configuration tabs by selecting Configuration from the View > Layouts
menu. Then click the desired configuration tab.
1. Select the desired tab from the View > Diagnostics menu.
2. Display all of the Diagnostic tabs by selecting Diagnostics from the View > Layouts
menu. Then click the desired diagnostics tab.
Additional Windows
Additional windows can be accessed from the View menu. They include:
Hoistway
System Performance
Layouts
Window Content
Configuration System parameter settings are displayed and may be changed on the Configura-
tion tabs. The tabs include Emergency Power, System Configuration, Legacy
Group Interface, Security, System I/O, Timer Tables, User Inputs and User Out- 8
puts (see page 10-2).
Diagnostics The System Diagnostic tabs contain information about the status and condition of
the system. The tabs include Event Log (see page 10-68).
System Performance Graphical representation of system performance statistics (see page 10-74).
Layouts Use to load Configuration, Diagnostic or Custom layouts (see page 10-75).
8-31
Using iView
Tab Content
Tab Content
Call Allows you to register car and hall calls. This control is accessed by clicking the Call
Registration Registration button on the button bar (see page 10-73).
Refresh Updates the information displayed on iView windows and tabs. This control is accessed
by clicking the Refresh button on the button bar.
If you click the pin icon, it points to the left and a but-
ton, labeled Hoistway, appears to the right of the win-
dow.
The window remains in view if the window has focus
(click the window title bar) or as long as the mouse cur-
sor remains on the window or button.
8-33
Using iView
Resizing Windows
iView windows can be resize so that you see just the data you need to perform a test or task.
To resize a window:
Cursor
2. When the cursor changes to a double line with arrows, you can click and drag
(hold the left mouse button down while moving the mouse) the window boundary and
resize the window.
1. Notice that the Diagnostics window is positioned at the bottom of the screen (connec-
tion arrows at bottom left corner). Double click the window title bar.
2. The title bar and frame around the Diagnostics window change to a solid blue line indi-
cating that the window is now undocked and can be moved.
3. Click the title bar and drag (hold down the left mouse button while moving the mouse)
the window to a new location. 8
4. Release the mouse button. The undocked window will appear in the new location, on top
of what ever is in that location. You can tell that it is undocked because the solid blue
frame remains.
5. You can quickly return the window to its original docked location by double-clicking in
the windows title bar.
8-35
Using iView
1. Notice that while moving an undocked window, docking controls appear near the center
and at the top, bottom and sides of the screen. As you slide the cursor over the controls,
a light blue highlight indicates the position to which the window will be moved. Release
the mouse button and the window docks in the new location.
2. An alternate method of moving a window is to right click the title bar of the window. In
the drop down list that appears, select Dock to and click the desired location. In the
example below, the Diagnostics window has been moved to the top of the screen.
3. If you like this arrangement and would like to be able to easily display this arrangement
in the future, you can save it as a Custom Layout. Please refer to Controller - Layouts
on page 8-30. 8
8-37
Using iView
Printing Screens
1. With the screen displayed, press the Print Screen key to send the entire screen to the
clipboard (PC memory).
2. To send only the selected item (widow or dialog) to the clipboard, press and hold the Alt
key, then press the Print Screen key.
Items sent to the clipboard can be pasted into any of several applications. One that you should
definitely have on your PC is Wordpad.
3. Open the Wordpad application (Start > All Programs > Accessories > Wordpad).
4. Select Paste from the Edit menu or press and hold the Ctrl key while pressing and
releasing the v key to paste the captured screen into Wordpad.
5. Select Print from the File menu to print the screen.
6. Save the file if you want to keep a record of the screen on the PC hard drive.
3. Use the controls to set the date and/or time and click Apply or OK. The date and time
will be updated on all controllers communicating with the dispatcher.
Note
The iView PCs time, which is displayed at the very bottom-right corner of the screen, is not the
same as the iControl systems date and time. The iControl systems date and time are displayed
on the iView status bar and are set using the Date / Time Configuration dialog shown above.
To edit a display:
1. Right-click on the graph or on one of the scales
to reveal a popup menu. Select Edit from the
menu.
8-39
Using iView
2. Experiment with modifying the display to find the combinations that suit the signal
types you are currently examining. The Edit menu is extensive:
3. Several different editors are available depending on where you click in the graphic dis-
play.
8-41
Using iView
6. Follow instructions 1 through 4 in the Firmware Update dialog and then click Con-
tinue. The Firmware Update dialog will change to:
7. Update the Bootrom first. Double click the () in the Bootrom row.
8. Use the Open dialog to navigate to the computers Desktop and double click the
Bootrom.mce file. The bootrom file will load and the version will be indicated in the
Upgrade version column.
9. Click Start upgrade. The upgrade progress will be indicated in the text window. When
the upgrade is completed you will be instructed to close iView and press the iBox Com-
puter Reset button.
Note
Note: If an FrmFtp Login dialog appears asking for a User and Password, click OK. The user
name and password are not used for this operation at this time.
10. Use iView to connect to the iBox when it finishes the re-boot.
11. Repeat steps 4, 5 and 6.
12. Click the check box to Delete the paramf and constf files on the controller
after IMP upgrade
13. Double click the () in the Imp row.
14. Use the Open dialog to navigate to the computers Desktop and double click the
vxworks.mce file. The IMP application file will load and the version will be indicated
in the Upgrade version column.
15. Click Start upgrade. The upgrade progress will be indicated in the text window. When
the upgrade is completed you will be instructed to close iView and press the iBox Com-
puter Reset button.
16. Use iView to connect to the iBox when it finishes the re-boot.
17. Select About iView from the Help menu and verify the version numbers for the IMP
Application and IMP Bootrom.
18. If you want to restore the original parameter settings which were saved in step #3, first
acquire write privilege and then select Load from the File > Configuration file menu.
Please refer to Loading Parameters from a Configuration File on page 8-22.
19. Select and Open or double click the desired file from the Open Configuration File dialog.
20. Select All screens or the Selected screens for which you wish to restore the original
parameter settings, and click OK.
Upgrade Options
When upgrading firmware from a pre-December 2005 release to a later release, in the event
that the Upgrade Wizard fails to properly load the parameters file, iView may not be able to con-
nect to the upgraded controller. The Upgrade Options Dialog (File > Upgrade Options) can be
used to enable iView to connect to the controller or iCue and complete the upgrade.
8-43
Using iView
Continue holding in the ENTER button until the Boot Boot Menu:
Menu is displayed.
1: Change IP Address
Change IP Address - Use this option to change the IP 2: Default Boot Prms
address of the LAN Network port before bootup (see 3: Start FTP server
Default Boot Params). This is helpful if the boot parame- 4: Boot
ters have been corrupted or the IP is not correct and you
need to FTP into the iBox.
With the Boot Menu displayed, press soft switch #1: Use IP Address
the left/right arrow keys to select the digit and the up/ 010.010.052.041
down arrows to make the correction. Press Enter to save ^
the changed IP address. Mask:
FFFF0000
Default Boot Params - This option allows the com-
puter to reset all parameters to standard settings. With Use Arrows To Edit
the Boot Menu displayed, press soft switch #2: Press Enter to Save
Boot - This option causes the boot process to continue. Press soft switch #4.
9-1
iView - Controller View
Connection Status Connected arrows, shown above, indicate that iView is communi-
cating with the controller. Broken arrows indicate that the connection has been broken.
Controller Type Indicates the type of controller to which iView is connected. For a
description of each type see An Overview of System Options on page 10-4 The controller types
include:
Simplex - a single car that is not part of a group.
Local - a car that is part of a group.
Local (Swing) - a local car that can swing away (detach from the group). 9
Swing - a local car that is currently detached from the group and is acting like a simplex.
Local (Alternate Dispatcher) - a local car that can assume dispatching responsibilities.
Local / Dispatcher - a local car that is also currently the dispatcher. iCue dispatching soft-
ware is running on the local cars iBox.
iCentral - a central dispatcher with iCue dispatching software running on a dedicated PC
or embedded micro controller.
9-3
iView - Controller View
Hoistway window
Mode of Operation
Direction
Current Car Position
Destination floor
Car Speed
Load in Car
Manual / automatic scrolling
Car Position
Mode of Operation
Hoistway window
The top line of the Hoistway pane shows the current car operation mode:
Attendant Service: The car is operating in Attendant service mode. Usually initiated by a
key-operated switch inside the car to allow the elevator to be operated by an in-car Atten-
dant. While on Attendant service, hall and car call buttons remain active. The elevator will
respond to car calls that have been enabled via different settings as specified by the car call
eligibility and card reader options. During Attendant service, the Attendant inside the car
controls direction of travel using the Attendant service Up and Down switches. The Atten-
dant can also bypass hall calls using the Attendant service Non-Stop switch. Door opera-
tion is typically automatic open with constant pressure on the door close button required
to close the doors. However, user settings are available to modify door operation if desired.
The parameters and descriptions are the same as for the Independent Service > Front /
Rear tabs. Please refer to Car Operation - Independent Service Tab on page 9-62.
Capture: The car has been placed in Capture mode using the Capture switch on the iBox or
by activating the Capture Input. When placed in Capture mode the car is taken out of
public service. It will not respond to hall call demand or parking instructions. It will con-
tinue to service car call demand so that current passengers are not inconvenienced. The
intent is to allow the car to service current passengers and then remain empty at the last
serviced floor so that it may be captured for test, adjustment, or other non-passenger use.
Car Panel Inspection: The car has been placed on Inspection mode using the car operating
panel switch. Use the car panel inspection switches to move the car.
Cartop Inspection: The car has been placed on Inspection mode using the cartop switch.
Use the cartop Up, Down and Safe switches to move the car.
CFSS Mode 1 (2) at Floor: Commandeer for Special Services - The car has recalled to the
CFSS floor and is waiting for a person to commandeer it according to the settings selected
on the Configuration > Car Operation > CFSS > Mode 1 (2) tab. Please refer to Car Oper-
ation - CFSS Tab on page 9-76.
CFSS Mode 1 (2) In-car: Commandeer for Special Services - The in-car switch has been
activated (or the car is at the recall floor if no switch). Car behavior is determined by the
In-car settings on the Configuration > Car Operation > CFSS > Mode 1 (2) tab. Please refer
to Car Operation - CFSS Tab on page 9-76.
CFSS Mode 1 (2) Recall: Commandeer for Special Services - A CFSS call has been initiated
via a hall switch. Any other hall calls will be un-assigned from the car. Any existing car
calls will be disposed of according to the Recall settings selected on the Configuration >
Car Operation > CFSS > Mode 1 (2) tab and the car will then recall to the floor at which the
CFSS call was latched. Please refer to Car Operation - CFSS Tab on page 9-76.
Construction Car Panel Inspection: Construction mode is enabled (Configuration > Safety
tab), and the car operation panel inspection switch has been activated. However, while in
Construction mode, the car panel inspection switches are ignored. The car can only be
operated via the machine room or cartop inspection switches while in Construction mode. 9
Construction Cartop Inspection: Construction mode is enabled (Configuration > Safety
tab), allowing the car to be run on Inspection with a bare minimum of field wiring
installed, and the cartop Inspection switch has been activated. Use the cartop Up, Down
and Safe switches to move the car. Place the car on machine room or cartop inspection and
operate the car with the appropriate switches.
9-5
iView - Controller View
Hoistway window
inside the car to allow the elevator to be operated by an in-car Attendant. While on Inde-
pendent service, hall call buttons and lamps for the elevator are disabled. The elevator will
respond only to car calls that have been enabled via different settings as specified by the
car call eligibility and card reader options. Door operation is typically automatic open with
constant pressure on the door close button required to close the doors. However, user set-
tings are available to modify door operation if desired. Please refer to Car Operation -
Independent Service Tab on page 9-62.
Inspection: One of the inspection modes (in-car, machine room or cartop) is active and the
car is operating in Inspection mode. The Inspection profile parameters are used.
Machine Room Inspection: The car has been placed on Machine Room Inspection mode
using the iBox Inspection switch. (All other Inspection modes must be inactive before
Machine Room Inspection may be enabled.)
Passenger: The car is operating in normal passenger mode, responding to dispatching and
parking instructions and to hall and car call demands. Car and door operation are deter-
mined by settings on the Configuration > Car Operation > Passenger tab. Please refer to
Car Operation - Passenger Tab on page 9-40.
Sabbath Operation: The elevator is operating in Sabbath mode initiated by a software
command, switched input or timer. Sabbath mode allows the elevator to operate, serving
the building without requiring buttons to be pressed for hall calls or car calls. Car behavior
is determined by parameters located on the Configuration > Car Operation > Sabbath
operation tab. Please refer to Car Operation - Sabbath Tab on page 9-84.
Shuttle service: The elevator is operating in Shuttle service mode initiated by a key-switch/
input, software command or timer. This option allows the car to be used to provide
express service for a subset of the buildings floors. Car behavior is determined by parame-
ters located on the Configuration > Car Operation > Shuttle service tab. Please refer to
Car Operation - Shuttle Service on page 9-87.
Test: Indicates that the iBox Test switch is in the Test position and the elevator is in Test
mode, generally used to adjust or test the elevator. The elevator operates the same as in
normal passenger mode except that the doors are disabled and no hall calls are registered.
9-7
iView - Controller View
Speed
Commanded: The speed commanded by the control system
Actual: The actual car speed determined by the landing system encoder.
Motor: Speed determined by the motor encoder/tachometer.
Processor health
Safety A: Indicates that Safety processor A is ok.
Safety B: Indicates that Safety processor B is ok.
Cartop: Indicates that the Cartop processor is ok.
In-service
Safety OK: Indicates that the safety string is made up.
System communication: Indicates that system communication is ok.
In group: Indicates that the car is operating under group dispatcher control.
Motion
Hoistway window
Cmd direction (Commanded direction): Indicates the cars commanded direction of travel.
Actual direction: Indicates the cars actual direction of travel.
Category: (Note: Insp = Inspection mode, all others = Automatic (Passenger) mode.)
AutoHalt: An emergency stop has been initiated.
AutoIdle: Waiting for a request to move to a different floor or relevel at current floor.
AutoWait: Waiting for the actual speed to indicate that the car has stopped moving.
InspHalt: An emergency stop has been initiated.
InspIdle: Waiting for a request to move.
InspMove: Received permission to move and movement initiated.
InspStart: Received a request to move and determined it is safe to do so.
InspStop: A normal stop has been initiated.
InspWait: Waiting for the actual speed to indicate that the car has stopped moving.
LevMove: Received permission to relevel and movement initiated.
LevStart: Received a request to relevel and determined it is safe to do so.
LevStop: While releveling, a normal stop has been initiated.
RunMove: Received permission to move and movement initiated.
Run Slow: Slowdown has been initiated.
RunStart: Received a request to move and determined it is safe to do so.
RunStop: A normal stop has been initiated.
Position
Logical: The idealized position of the car. Indicates where the car would stop if so com-
manded, taking into account current speed and deceleration rate.
Actual: The true position of the car reported by the position encoder.
Cartop: Raw position from cartop, no offset included.
Machine
Mode:
Brake Contact Enable: The contactor for the brake subsystem has been energized.
Voltage is available at the input of the brake subsystem.
Brake Electric Enable: The brake subsystem has been enabled. Along with an ener-
gized brake contactor, the brake subsystem is able to produce brake output voltage.
Drive Electric Enable: The drive subsystem has been enabled. Along with an energized
motor contactor, the drive system is able to produce output voltage (armature voltage).
Motor Contact Enabled: The contactor for the drive subsystem has been energized.
Voltage is available at the input of the drive subsystem. 9
Run: The system has received permission to energize the motor and has done so.
Start: The system has received a request to energize the motor and determined that it
is safe to do so.
Stop: The system has begun the process to de-energize the motor.
Arm voltage (Armature voltage): Voltage applied to the armature.
Arm current (Armature current): Armature current expressed as a function of voltage.
9-9
iView - Controller View
Door lock
Front and Rear: Indicates when the front and rear door locks are made up.
Leveling sensor
Up leveling marker (Front and Rear): Indicates when front and rear Up leveling markers
sensors are On.
Door zone (Front and Rear): Indicates when front and rear door zone sensors are On.
Down leveling marker (Front and Rear): Indicates when front and rear down leveling
marker sensors are On.
Pattern
Profile:
Alternate 1 Emergency Power Idle
Alternate 2 Earthquake Inspection
Correction Emergency slowdown Standard
Phase: (Please see the graphic below)
Idle Begin Decel
Begin Accel Deceleration
Acceleration Flare
End Accel Approach
High Speed Leveling
Faults
All active fault messages are displayed in the Faults list box. A complete listing of fault
messages is provided in Section 6. Please refer to iControl Messages on page 6-13.
Car status
All active car status messages are displayed in the Car status list box. A complete listing of
status messages is provided in Section 6. Please refer to iControl Messages on page 6-13.
Diagnostics Tabs
Four other diagnostic screens, Call Generator, Data Trap, Diagnostic Outputs and Virtual Oscil-
loscope, are displayed each in their own window. This allows them to be used simultaneously
with other windows.
9-11
iView - Controller View
ON/OFF buttons: Click the ON button to turn the data trap ON. The Data trap status
changes to Running. Click the OFF button to turn the data trap OFF. The Data trap status
changes to Disabled.
Data trap status: Indicates the status of the data trap, Disabled or Running.
Data sample time: Sets the duration of the data sample.
Select Data Trap Triggering Event: Select from the list of signals and events and then Send
to the controller.
Save button: Once the data trap has been triggered, the Data trap status changes to Dis-
abled (OFF and no further samples are taken. Click the Save icon to display the Save dia-
log box. Choose a name and a location for the file and click Save. The saved files (.csv) can
be viewed using a spreadsheet program such as Microsoft Excel.
real-time, graphical display of system diagnostic flags. LEDs indicating currently active flags
The tree in the left pane allows you to view the status of input and output flags arranged into
four groups:
Car Operation: Active car and hall calls, direction of travel, recall status, parking status
flags, OK to start status, etc.
Motion: Operational flags that determine whether or not the elevator is allowed to move.
Drive: Run state flags for drive and motor.
Safety: Safety flags.
9-13
iView - Controller View
Click an output in the table on the left and drag it into the title bar of one of the sixteen
output monitors. The value of that output will appear in the window below the title bar.
Click the X next to the outputs name in the title bar of the monitor.
Save event log / Open event log The Event Log can be saved to a file for future ref-
erence. To save a Controller Event Log to a file:
Click the Save button on the Controller > Diagnostics > Event Log tab.
Navigate to the folder you want to save the file in.
Name the file and click Save.
The Event Log file can be viewed using iView. To view a previously saved Event Log file:
Click the Open file button on the Controller > Diagnostics > Event Log tab.
Navigate to the file you want to view and double-click it.
Print / Print Preview To print the event log or to view a print preview and/or print the
event log from the print preview dialog: 9
Click the Print button , choose a printer from the Print dialog and click Print.
Click the Print Preview button and use the controls to display and/or print the desired
pages.
Clear All Click the Clear All button to delete all of the events in the Event Log.
9-15
iView - Controller View
Event Filter The Event Filter controls which events will be displayed in iView.
Events Received Shown at the bottom of the Event Log window, this indicates the
number of events that have been received from the controller. 9
Events Displaying This indicates the number of events that are being displayed. By
comparing the Events Received versus the Events Displaying, you can determine how many
events are being filtered out by the Event Filter.
9-17
iView - Controller View
To bypass faults:
1. In iView, display the Diagnostics > Fault Bypass tab. The message window provides
instructions.
2. Set the iBox INSPECTION switch to the INSP position (or set the TEST switch to ON).
3. Set the iBox FAULT/ FUNCTION BYPASS switch to ON. (see Time remaining below)
4. When the message window indicates ABLE TO BYPASS FAULTS click the button(s)
for the fault(s) you wish to bypass. The LEDs on the buttons turn on when the bypass is
active, off when a bypass is inactive and the buttons are grayed out when a bypass is
unavailable.
System status
Bypass status
Active bypasses - indicates the number of active bypasses.
Time remaining - the bypass remains active for fifteen minutes from the time the iBox
Fault/ Function Bypass switch is turned ON. This display indicates the remaining time.
When the time elapses, the message window indicates FAULT BYPASS SWITCH TIMED
OUT. If you need additional time, turning the Fault/Function Bypass switch to OFF and
then back to ON within one second will reset the selected bypasses.
Message window - shows instructional information.
Fault Bypasses The following bypasses are provided. When enabled, the fault will be
ignored and the system will not respond to the fault as programmed.
9-19
iView - Controller View
Switch Data
Note
Emergency Terminal Overspeed is hard-coded at 95% of Contract Speed. Be certain that the car
is traveling well below this speed when an Emergency Terminal switch is opened to avoid an
emergency stop. In some instances, it may be necessary to re-position an Emergency Terminal
switch to achieve this. Contact MCE Technical Support if needed.
Position of the car in the hoistway at various speed transition points measured during the
last run. These position values can be useful, especially if the last run was to a terminal
landing.
9
9-21
iView - Controller View
Acquire write privileges (select Acquire from the Write privilege menu).
Using the drop down list, select the Test point 1 signal. This signal will be tracked in green
on the oscilloscope, displayed numerically in the Test point 1 window and output to iBox
test point STP1.
Using the drop down list, select the Test point 2 signal. This signal will be tracked in blue
on the oscilloscope, displayed numerically in the Test point 2 window and output to iBox
test point STP2.
You can freeze and reposition the display by clicking and dragging.
Note
Some signals are scaled, e.g. motor field and brake voltage are scaled by a factor of 100. Other
signals are scaled based on parameter values, e.g. pattern High speed (contract speed).
Display Editing
Tracking Enable Tracking from the popup (right-click) menu to track a signal over time.
Disable tracking if you want to drag the horizontal scale to look at a particular moment in time.
Click on a scale, then press the keyboard <Home> to decrement the scale one full screen.
Click on a scale, then press the keyboard <End> key to increment the scale one full screen.
Click on a scale, then press the keyboard right or left arrow keys to increment or decre-
ment by units.
While tracking, clicking on any keyboard key will stop tracking. 9
9-23
iView - Controller View
Scale One typical modification you might want to make is to the scale of a display. For
example, if you wanted to change the scale of the Test point 2 vertical display (Y axis):
1. Right-click on the Test point 2 display scale and select edit.
2. Set the Minimum value for the scale (Min = zero in our example).
3. Set the Span, number of units to display (Span = one in our example).
4. Close the Plot Axis Editor dialog.
Zoom to Fit Zoom to Fit is another very useful tool. If you are
monitoring two signals, and they diverge so that both are not visible,
use Zoom to Fit to instantly bring each back into view (vertical scale).
Conversely, if two signals are very close together in the display, use
Zoom to Fit to expand the display and see fine changes in the signal.
Right-click on the scale display then select Zoom to Fit.
For the horizontal scale, Zoom to Fit resets the left margin to zero time and scales the display to
include total elapsed time at that point. In other words, if you are tracking a signal over time,
then want to see all its transitions since you began tracking, use Zoom to Fit on the (lower) hor-
izontal scale.
Configuration Tabs
9-25
iView - Controller View
9
Weakening Voltage
Pick Delay
Delay
Weakening
Repick
Time Hold Delay
9-27
iView - Controller View
Danger
Warning! Possibility of losing control of the car at the end of the run if Drop
Delay and Voltage Decay time exceed Contactor Drop Delay!
Caution
The parameters on this tab are set automati-
cally during brake calibration. Do not modify
these parameters unless advised to do so by
an MCE representative.
9-29
iView - Controller View
Doors Door device bypass timers, door motor protection timers, page 9-31
and door closing delay parameters.
Devices Arrival fixture, CE Electronics fixture and voice communicator page 9-35
parameters.
Passenger Door opening and closing, photo eye, dwell timers, load page 9-40
weigher, car delayed timer, and call cancel parameters.
Fire Service Applicable code Fire Service Recall and In-Car Firefighter's page 9-47
Service parameters.
Flood Operation Determines car behavior during flood operation. page 9-79
General
Non-interference timer: Determines the number of seconds a car with non-automatic door
operation waits at a floor in response to a call before proceeding to answer other demands.
Door Open delay timer to reverse closing doors: This timer is used to delay the door open
command on closing doors.
Door close delay timer: This timer is used to delay the door close command.
Relevel door open inhibit timer: 0 (OFF) = disabled. When enabled, closed doors shall not
be opened while the car is releveling, but must wait until releveling is complete or the
timer elapses. However, this feature does not prevent preopening. 9
Door Device
Mechanical Safe Edge: Check Front and/or Rear to indicate that the doors have a mechan-
ical safe edge. If, after a period of time, an active safe edge input should be bypassed and
the doors closed, enable bypass (check Bypass after timeout) and set the timer (Device
timeout) to the desired time. This option works in conjunction with Nudging (see Nudg-
ing on page 9-40).
9-31
iView - Controller View
Photo Eye: Check Front and/or Rear to indicate that the doors have a photo eye. If, after a
period of time, an active photo eye input should be bypassed and the doors closed, enable
bypass (check Bypass after timeout) and set the timer (Device timeout) to the desired
time. This option works in conjunction with Nudging (see Nudging on page 9-40).
Door Open Button: If, after a period of time, an active door open button input should be
bypassed and the doors closed, enable bypass (check Bypass after timeout) and set the
timer (Device timeout) to the desired time. This option works in conjunction with Nudging
(see Nudging on page 9-40).
Door Open Button At Security Floor:
Remains operative at a secured opening: When checked, the Door Open Button will
remain operative for the side that has opened at a secured/locked floor (meaning that
someone has access to that side via a car call or hall call). Otherwise the DOB will only
be enabled as long as the doors are not fully closed.
9-33
iView - Controller View
Closing warning light timer: Upon door close intent, if the Door Closing Delay parame-
ter calls for a delay, the Front (Rear) Closing Warning Light output is turned ON. This
timer determines the amount of delay after the Front (Rear) Closing Warning Light
output is turned ON before the Front (Rear) Closing Warning Buzzer output is turned
ON.
Closing warning buzzer timer: This timer determines the amount of delay after the
Front (Rear) Closing Warning Buzzer output is turned ON before automatic closing of
the front or rear doors begins.
Door closing delay time: Total door closing delay is the sum of the closing warning
light and buzzer timers.
Door close button bypasses closing delay: If checked, pressing the door close button
will bypass the door closing delay timer and clear all related warning signals.
Door closing delay on passenger mode only: If checked, the door closing delay and
related warning signals will only be enabled during Passenger mode.
Door open power latch: If checked, the controller will sustain the door open command to
the door operator, preventing the possibility of doors drifting closed when the command is
dropped.
Door close power latch: If checked, the controller will sustain the door close command to
the door operator, preventing the possibility of doors drifting open when the command is
dropped.
Disable door contact monitoring: If checked, door contact monitoring is disabled.
Arrival Fixtures
Hall Mounted: Enable if hall-mounted arrival notification devices are used for this car.
Double Strike on Down Direction: Sound hall-mounted arrival fixtures twice when
announcing down direction. If the fixtures themselves support double-striking, this
feature should not be enabled.
Set the On Timer for the amount of time the gong output should be active. Set the Off
Timer to establish the pause between first and second gongs.
Car Riding: Enable if car-riding arrival notification devices are used for this car.
Double Strike on Down Direction: Sound car-riding arrival fixtures twice when
announcing down direction arrival. If the fixtures themselves support double-striking,
this feature should not be enabled.
9
Set the On Timer for the amount of time the gong output should be active. Set the Off
Timer to establish the pause between first and second gongs.
Passing Floor Gong: Set the On Timer for the amount of time the gong output should be
active. Set the Off Timer to establish the minimum pause between gongs.
9-35
iView - Controller View
Note
Alarm Light: Typically, the Alarm Light is placed where it will be visible to security personnel.
The output remains latched until acknowledged by activation or the Alarm Reset input (typi-
cally a keyed switch).
Note
Alarm Buzzer: Typically, the Alarm Buzzer is placed where it will be audible to security person-
nel. The standard (in-car stop or alarm open) output is constant and causes a constant tone. The
additional (delayed with doors closed or other open safety condition) output is pulsating and
causes a pulsating tone. This output does not latch but remains active only so long as the moni-
tored condition exists (switch, contact, or relay remains open).
Serial Fixture Tab If the installation uses CE Electronics serial fixtures, configure them
Start Floor Arrival Announcement: Select the time at which you want the voice arrival
announcement to occur As the car slows during approach, At the end of the run, or
When the door is fully open.
Flash direction arrow while running: Specifies that the direction arrow will flash while
the car is running.
Serial Messages: This control box allows you to configure announcements to be dis-
played or annunciated by the CE fixtures. Serial Messages are text or audible messages
pre-programmed into the serial fixture (character display or talking) and triggered
by the elevator controller. Configuring a message requires providing a number
(matched to a fixture message number to display or announce the correct message), a 9
node qualifier (determines which fixtures will display or annunciate the message), and
if appropriate, three ASCII characters (letters A-Z, numbers 0-9: used by character
displays to show an abbreviated message, e.g., FSA for Fire Service Alternate).
Up and Down Buttons: Some fixtures display only one message at a time. If two or
more messages are valid, the message highest on the list is displayed. To move a mes-
9-37
iView - Controller View
sage up or down on the list, click the message to select it, click the up or down button to
move the message, and click Send to send the change to the controller.
9-39
iView - Controller View
General
Lobby floor: This setting determines which floor will use the lobby dwell timer. If the car is
part of a group, the group dispatcher settings for primary and alternate lobby floors super-
sede this selection.
Egress floor: The Egress Floor Gong output will activate for 500 ms when the car arrives
at this floor in resp0nse to a car or hall call. This output is used to activate an audible indi-
cator to alert the visually impaired that the car has arrived at the main egress floor.
Nudging Nudging is intended to discourage passengers from holding the doors open for
excessive lengths of time. These options work in conjunction with the Door Device settings (see
Door Device on page 9-31). The nudging options are:
None: Nudging is disabled.
Buzzer only: When the reopening device bypass timer expires, only the buzzer will sound.
Reduced speed and torque: An open door will attempt to close at reduced speed and
torque if it is held open for an extended period of time. This time is determined by the
reopening device bypass timer.
Stop doors due to reopening device activated during nudging: If enabled, activation of
a safe edge during nudging will stop the doors from closing. Otherwise they will fully
reopen.
To see how the Nudge and Buzzer outputs and Door operation after device timeout are affected
by the various nudging and do0r device settings, see Table 9.7 Nudging Operation Table.
Allow hall call button to reverse doors on a departing car: (Not implemented on this
screen) Please refer to the System> System Configuration > Dispatching > Options Allow
same floor hall calls to reverse doors on a departing car parameter.
Allow direction arrow to reverse with doors open: If the car is at a destination floor and the
next demand is in the opposite direction of the last run, determines whether the direction
arrow is allowed to reverse while the elevator doors are open. Enable if the direction arrow
is allowed to reverse with the elevator doors open.
Cancel calls at slow down: By default, when a answering a call, the call is canceled when
the car reaches door zone. This option specifies that calls are to be canceled when the car
begins slow down when approaching the floor.
Car delayed timer (seconds) - If a car is delayed in satisfying a demand an amount of time
in excess of this timer setting, it will be taken out of hall call service. All calls remain regis-
tered. Hall calls are reassigned if the car is in a group.
Car out of service timer (minutes) - This timer starts once the Car delayed timer (above)
expires. If the Car delayed condition persists for this amount of time, the car is taken out of
service and all calls are cancelled.
Car fan and light timer (minutes): Set the number of minutes the car fan and light should
remain on when the car is parked before automatically shutting off. The fan and light will
become active again when the car responds to a demand.
Anti-Nuisance Anti-nuisance functions help the controller recognize and avoid nuisance
operation, for example, a passenger intentionally interfering with elevator operations by unnec-
essarily selecting multiple stops, etc.
Photo eye: All remaining car calls are canceled if the photo eye has not been activated and
the number of car call stops exceeds the Allowed number of car call stops without photo
eye activation parameter.
Light load: All car calls are canceled if the number of registered calls exceeds the Number
of car calls allowed parameter and the car weight (percentage of full load), as measured
by the load weigher, is less than the Light Load Threshold parameter. 9
Cancel car calls behind car: If enabled, car calls entered in the opposite direction to cur-
rent or upcoming direction of travel are not allowed.
Cancel remaining car calls with direction reversal: If enabled, when the car reverses direc-
tion of travel, any remaining calls in the previous direction are cancelled. For example, an
up travelling car has car calls registered below it. Those calls will be cancelled when the car
switches direction to down.
9-41
iView - Controller View
Exercise Operation This option is used to cause the elevator to perform a number of
full hatch runs after being idle (on normal passenger service) for a number of hours. Once exer-
cised, the car returns to normal operation.
Enable: Check to enable exercise operation.
Idle timer: The exercise operation will be performed when the car has been idle (on
normal passenger operation) for more than the set number of hours.
Number of run cycles: Sets the number of run cycles to be performed. One cycle is a
full hatch run up and down.
Automatic Swing Operation Swing operation removes a car from some aspects of
central dispatcher or Local/Dispatcher control. During Swing operation the car responds to hall
call demand from a dedicated set of hall calls (a Swing riser).
Enable: If enabled, the car will automatically enter Swing operation when a hall call is
received from the Swing riser. Automatic Swing operation assumes an always active
Swing riser. This option will override the Swing Automatic Operation input.
Disabled, or enabled with input: This option allows Automatic Swing operation to be
enabled by activation of the Swing Automatic Operation input. The car will automati-
cally enter Swing operation when a hall call is received from the Swing riser.
Idle swing car timer: Automatic Swing operation is monitored. An idle Swing car will
return to normal service if no Swing riser inputs are activated for the period of time set
by this control. Idle is defined as a car with no assigned calls, parking demand, or door
dwell times.
While Swing operation is active:
The car does not use the dispatching and security parameter settings from the central or
local dispatcher. It uses parameter settings stored on its own iBox. With Swing operation
enabled either by enabling Automatic Swing Operation or by assigning the Swing Opera-
tion Switch input to an I/O board terminal, these parameters must be programmed using
iView connected to the Swing cars iBox.
The Swing car does not service group hall calls. Any existing group hall calls for the car are
canceled or reassigned. Hall call eligibility for the swing car must be programmed using
the Swing cars System View > System Configuration > Hall Call Eligibility tab.
The car parks at the floor assigned on the Swing cars System Configuration > Parking tab.
Existing car calls are not affected unless an alternate car call eligibility set is assigned by
activation of a constant closure switch, in which case car calls are disposed of according to
settings for that eligibility set. Up to eight alternate car call eligibility sets may be defined.
Please refer to General - Car Call Eligibility Tab on page 9-110.
The Swing car uses normal passenger settings pertaining to door operation, door dwell
9-43
iView - Controller View
General
Sequential Door Operation
Open both doors simultaneously: Both doors are allowed to open at the same time.
Open front doors first: Front doors will be opened first.
Open rear doors first: Rear doors will be opened first.
Open egress doors first: Doors on the side of the first registered car call to that floor
open first.
Open ingress doors first: Doors on the side of the first registered active hall call from
that floor open first.
Open offset timer: This timer allows you to set a duration in seconds which the second
opening set of doors will wait to open, based on the open or closed status of the first
opening set of doors. (Active only when a sequential opening mode is selected; changes
to suit the selection.)
Open rear/front/egress/ingress doors XX (0 to 3600) sec after the front/rear/
ingress/egress doors have fully opened/closed.
Door Dwell Timers These timers set the door dwell times.
Reopen: The amount of time that the doors are to remain open (dwell) when a door
reopening device or open button has been activated.
Door hold: The amount of time that the doors are to remain open when reopened by the
activation of the Door Hold button.
ADA car call: The minimum amount of time that the doors are to remain open after arriv-
ing at a floor selected by a car call per ADA requirements. Door dwell is not shortened by
activation of a button or door reopening device (call or door close button, etc.). Timer
starts when doors are fully open.
ADA hall call: The minimum notification time from activation of the hall gong to when the
door is about to close as required by the Americans with Disabilities Act. This dwell is not
shortened by activation of a car call or door close button.
Car Call
Dwell time: The amount of time that the doors are to remain open when responding to
a car call. Any of the following may be specified to cancel car call dwell time:
Door close button: Pressing the door close button will cancel car call dwell time.
Car call button: Pressing a car call button will cancel car call dwell time.
Photo eye: Activation of the photo eye detector will cancel car call dwell time.
Hall Call
Dwell time: The amount of time that the doors are to remain open when responding to
a hall call. Any of the following may be specified to cancel hall call dwell time.
Door close button: Pressing the door close button will cancel hall call dwell time.
Car call button: Pressing a car call button will cancel hall call dwell time.
Photo eye: Activation of the photo eye detector will cancel hall call dwell time.
Lobby Call
Dwell time: The amount of time that the doors are to remain open when responding to
a call at the lobby floor. Any of the following may be specified to cancel lobby call dwell
time:
Door close button: Pressing the door close button will cancel lobby call dwell time.
Car call button: Pressing a car call button will cancel lobby call dwell time.
Photo eye: Activation of the photo eye detector will cancel lobby call dwell time.
General
Open doors for idle car: The car will park with doors open. If the parking option is not set,
the car will remain at the last floor answered with doors open.
Open car gate if hoistway door open: The car gate will open if the hoistway door is open.
DCF on between floors: Specifies that the door close function shall be on when the car is
not at a floor in non-inspection modes.
Opening When MCE Controlled is checked, the following parameters determine what
action will cause the doors to open when the car arrives at a floor.
Mechanism: 9
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Momentary pressure on door open button: Doors shall not open automatically upon
arrival at a floor. Momentary activation of the door open button initiates door opening.
9-45
iView - Controller View
Closing When MCE Controlled is checked, the following parameters determine what
action will cause the doors to close.
Mechanism:
Automatic: With the absence of door open intent, the doors shall close automatically upon
dwell time expiration.
Passenger initiated: Doors shall not close automatically. The passenger initiated action
selected below shall be required to cause the door to close.
Door close button:
Does not close doors: Doors shall not respond to door close button.
Constant pressure: Doors shall close with constant pressure on door close button. If
the door close button is released before the doors are fully closed, the doors shall
reopen and stand open.
Momentary pressure: Doors shall close with momentary pressure on door close
button. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Momentary pressure if a car call is registered: Doors shall close with momentary
pressure on door close button if a car call is registered. Operational door reopening
devices shall initiate door reopening, and once fully open the doors shall stand open
until the door close button is again activated.
Car Call Button:
Does not close doors: Doors shall not close in response to car call button.
Constant pressure: Doors will close with constant pressure on car call button. Oper-
ational door reopening devices shall initiate door reopening, and once fully open
the doors shall stand open until the door close button is again activated.
Momentary pressure: Doors shall close with momentary pressure on car call but-
ton. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Car call registration closes doors: Doors will close if a car call is registered.
Once cars arrive at the recall floor, they are taken out of service and will not respond to hall calls
or car calls until the In Car Firefighter switch is activated. In this second stage of Fire Service,
the car behaves as determined by the Fire Code selected and by any user modifications to the
selected Fire Code made using tabs accessed through the Configuration > Car Operation > Fire
Service > Fire code tab. During Fire Phase 2, car speed and performance may be controlled by
Standard Pattern or by Alternate 2 Pattern parameters Configuration > Pattern tab).
9-47
iView - Controller View
All parameters are in default state: Indicates that all of the fire service parameters
are set as specified by the selected code. If this is not the case, One or more parameters
has been changed. is displayed.
Name: Select the appropriate code from the drop down list.
Year: Select the appropriate version (year) of the code.
Default button: Sets the fire service parameters to the values specified by the selected
code, e.g. A17.1 - 2000.
Latch the fire hat flashing: Flashing the fire hat is required by certain jurisdictions
whenever the hoistway or machine room smoke sensors are tripped. When these sensors
are reset, the fire hat continues to flash if this option is set. Otherwise the fire hat will
remain illuminated until fire service is deactivated.
Caution
Changing Fire Code parameter settings may cause you to be out of compliance with the
selected code and may require a variance. Parameter settings that are in compliance with
the selected code are shown with an underline. If a setting is changed to one that does not
comply with the selected code, it will appear in RED.
Firefighters car
No in-car firefighters switch: Check if the car does not have an in-car firefighters
switch (Required for British Fire Code EN 81-72).
Designated firefighters car: Check if the car does not have an in-car firefighters
switch, but is a designated firefighters car. Upon completion of Fire Phase I it will then
automatically go to Fire Phase II.
Fire Recall
Fire recall door cycle time: Sets the door cycle time for the Fire Recall Door Cycle
option. When the car reaches the recall floor and doors are opened, the doors will then
close after the Fire Recall Door Cycle time expires (used for pressurised hoistway).
9-49
iView - Controller View
9-51
iView - Controller View
Recall Not Completed - Recall Completed Determine how the doors shall open
and close before recall has been completed and after recall has been completed. The parameters
and descriptions are the same for both Recall Not Completed and Recall Completed and for
both Front and Rear tabs.
Opening When MCE Controlled is checked, the following parameters determine what
action will cause the doors to open when the car arrives at a floor.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Constant pressure on door open button: Doors shall not open automatically upon arrival
at a floor. Constant pressure activation of the door open button is required to open the
doors. If the door open button is released before the doors are fully open, the doors shall 9
re-close.
Momentary pressure on door open button: Doors shall not open automatically upon
arrival at a floor. Momentary activation of the door open button shall initiate opening the
doors.
9-53
iView - Controller View
Closing When MCE Controlled is checked, the following parameters determine what
action will cause the doors to close.
Mechanism:
Automatic: With the absence of door open intent, the doors shall close automatically upon
fire service activation.
Passenger initiated: Doors shall not close automatically. The passenger initiated action
selected below shall be required to cause the door to close.
Door close button:
Does not close doors: Doors shall not respond to door close button.
Constant pressure: Doors shall close with constant pressure on door close button. If
the door close button is released before the doors are fully closed, the doors shall
reopen and stand open.
Momentary pressure: Doors shall close with momentary pressure on door close
button. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Momentary pressure if a car call is registered: Doors shall close with momentary
pressure on door close button if a car call is registered. Operational door reopening
devices shall initiate door reopening, and once fully open the doors shall stand open
until the door close button is again activated. (Not applicable to Fire Service Recall
operation)
Car Call Button:
Does not close doors: Doors shall not close in response to car call button.
Constant pressure: Doors will close with constant pressure on car call button. Oper-
ational door reopening devices shall initiate door reopening, and once fully open
the doors shall stand open until the door close button is again activated.
Momentary pressure: Doors shall close with momentary pressure on car call but-
ton. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Fire Phase II Recall Conditions: One of the following conditions is necessary to initiate
Fire Phase II recall when the Fire Phase II switch is deactivated.
No recall: Never recall.
Recall: Always initiate recall.
Doors open or closed: Initiate recall only if the doors are fully open or closed.
Phase 1 and doors open: Initiate recall only if Phase I is still active and the doors are
fully open. 9
Phase I and doors open or closed: Initiate recall only if Phase I is still active and the
doors are fully open or closed.
Phase I and doors opened once: Initiate recall only if Phase I is active and the doors
have been opened at least once at the floor.
Doors open: Initiate recall only if the doors are fully open.
9-55
iView - Controller View
Fire Phase II hold conditions: One of the following conditions is required to put the car on
Fire Phase II Hold when the switch is turned to the Hold position.
Never: Never put the car on Fire Phase II Hold.
Not on Phase I: Initiate Fire Phase II Hold if Fire Phase I is not active.
Not on Phase I and doors open: Initiate Fire Phase II Hold if Fire Phase I is not active
and the elevator doors are fully open.
Unconditional hold: Put the car on Fire Phase II Hold unconditionally.
Doors open hold: Initiate Fire Phase II Hold only if doors are fully open.
Phase I and doors open: Put the car on Fire Phase II Hold if Fire Phase I is active and
the doors are fully open.
Put car on Fire Phase II when: One of the following conditions is required to activate in-
car firefighter operation when the in-car fire fighter switch is activated
Unqualified: Put the car on Fire Phase II unconditionally.
Recall completes: Put the car on Fire Phase II when the recall is complete.
Recall completes and Primary ON: Put the car on Fire Phase II when the recall is com-
plete and the Primary Fire recall switch is in the ON position.
Take car off Fire Phase II when: One of the following conditions is required to take the car
off in-car firefighter operation.
Unqualified: Take car off Fire Phase II when the in-car switch is deactivated.
Recall completes: Take car off Fire Phase II when the recall is complete and the in-car
switch is deactivated.
Recall completes and Primary ON: Take the car off Fire Phase II when the recall is
complete, the in-car switch is deactivated and the Primary Fire Recall switch is in the
ON position.
Primary OFF: Take the car off Fire Phase II when the Primary Fire Recall switch is in
the OFF position.
Put car on Fire Phase II during Fire Phase II recall when: One of the following conditions
is required to put car on Phase II during Phase II recall if the Phase II Switch is reacti-
vated.
None: Never re-initiate Phase II once Phase II recall has been activated.
Unconditional: Phase II will be re-activated unconditionally.
Doors are not closed: Phase II will be re-activated only if the doors are not closed.
Doors not closed away from recall floor: Phase II will be re-activated only if the car is
away from the recall floor and the doors are not closed.
Put car on Phase II hold when: One of the following conditions is required to activate Fire
Phase II Hold when.
Never: Never activate Phase II Hold.
Not on Phase I: Initiate Phase II Hold if Phase I is not activated.
Not on Phase I and doors open: Initiate Phase II Hold if Phase I is not activated and
the doors are fully open.
Unconditional hold: Phase II Hold will be activated unconditionally.
Doors open hold: Phase II Hold will be activated only if the doors are fully open.
Phase I and doors open: Phase II Hold will be activated only if Phase I is active and the
doors are fully open.
9-57
iView - Controller View
At Recall Floor - Away from Recall Floor Determine how the doors shall open
and close when the car is at the recall floor and when the car is away from the recall floor. The
parameters and descriptions are the same for both At Recall Floor and Away From Recall Floor
and for both Front and Rear tabs.
Opening When MCE Controlled is checked, the following parameters determine what
action will cause the doors to open when the car arrives at a floor.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Constant pressure on door open button: Doors shall not open automatically upon arrival
at a floor. Constant pressure activation of the door open button is required to open the
doors. If the door open button is released before the doors are fully open, the doors shall
re-close.
Momentary pressure on door open button: Doors shall not open automatically upon
arrival at a floor. Momentary activation of the door open button shall initiate opening the
doors.
Closing When MCE Controlled is checked, the following parameters determine what
9-59
iView - Controller View
Opening When MCE controlled is checked, the following parameters determine what
action will cause the doors to open when the car arrives at a floor.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Constant pressure on door open button: Doors shall not open automatically upon arrival
at a floor. Constant pressure activation of the door open button is required to open the
doors. If the door open button is released before the doors are fully open, the doors shall
re-close.
Momentary pressure on door open button: Doors shall not open automatically upon
arrival at a floor. Momentary activation of the door open button initiates door opening.
Closing When MCE controlled is checked, the following parameters determine what
Note
For elevators that must comply with the ASME A17.1-2000 and later code, if the door is power-
operated and vertically sliding, the Closing Mechanism parameter (Fire Code > In-Car Recall >
Front / Rear) must be set to Passenger initiated and the Door close button parameter must be
set to Constant Pressure.
9-61
iView - Controller View
General
Open front doors: If the doors are closed when the car is placed on Independent Service,
the front doors shall be opened.
Open rear doors: If the doors are closed when the car is placed on Independent Service,
the rear doors shall be opened.
Cancel all car calls at next car call stop: Specifies that all car calls be canceled after the ele-
vator completes the first car call stop
Independent Service - Front / Rear Tabs Determine how the doors shall open
and close during Independent Service operation. The parameters and descriptions are the same
for both Front and Rear tabs.
Opening When MCE controlled is checked, the following parameters determine what
Closing When MCE controlled is checked, the following parameters determine what
action will cause the doors to close.
Mechanism:
Automatic: This option is not available on Independent service.
Passenger initiated: Doors shall not close automatically. The passenger initiated action
selected below shall be required to cause the door to close.
Door close button:
Does not close doors: Doors shall not respond to door close button.
Constant pressure: Doors shall close with constant pressure on door close button. If
the door close button is released before the doors are fully closed, the doors shall
reopen and stand open.
Momentary pressure: Doors shall close with momentary pressure on door close
button. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Momentary pressure if a car call is registered: Doors shall close with momentary
pressure on door close button if a car call is registered. Operational door reopening
devices shall initiate door reopening, and once fully open the doors shall stand open
until the door close button is again activated.
Car Call Button:
Does not close doors: Doors shall not close in response to car call button.
Constant pressure: Doors will close with constant pressure on car call button. Oper-
ational door reopening devices shall initiate door reopening, and once fully open
the doors shall stand open until the door close button is again activated.
Momentary pressure: Doors shall close with momentary pressure on car call but-
ton. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Car call registration closes doors: Doors will close if a car call is registered.
9-63
iView - Controller View
General
Recall floor: Specifies the floor to which the elevator is recalled.
Next available floor - Causes the car to stop at the next available floor in the direction
of travel if Car call disposition is set to Cancel immediately. If car calls are allowed
to remain registered, the elevator will remain at the floor at which the last registered
car call was answered.
Floor label - Specifies the floor to which the elevator shall be recalled.
Switch priority: Determines which switch has priority if more than one Elevator Recall
Switch is activated simultaneously. (#1 is highest priority.)
Car call disposition: Determines how existing car calls are handled when the Elevator
Recall Switch is activated.
Service existing car calls: All previously registered car calls remain registered and the
elevator is allowed to answer the car calls.
Cancel immediately: All previously registered car calls are immediately canceled.
Cancel at the next car call stop: All previously registered car calls remain registered.
When the elevator answers its next car call, all remaining car calls are canceled.
Allow new car call registration: Determines if new car calls shall be registered during the
Door Operation Front Determines how the elevator front doors shall operate once the
elevator has arrived at the recall floor (after all car calls have been answered).
Keep closed: The front doors shall remain closed.
Keep open: The front doors shall open and remain open.
Open doors for xx sec: The front doors shall open for the time specified, then close.
Respond to door open button: Specifies that the front doors shall respond to activation of
the front door open button (once the car has arrived at the recall floor). If this option is
selected, the front door open button remains operative at all times. If not selected, the
front door open button will be rendered inoperative when the front doors are closed at the
recall floor. (Note: The door open button will always remain operative when the associated
doors are open).
9
9-65
iView - Controller View
Door Operation Rear Determines how the elevator rear doors shall operate once the
elevator has arrived at the recall floor (after all car calls have been answered).
Keep closed: The rear doors shall remain closed.
Keep open: The rear doors shall open and remain open.
Open doors for xx sec: The rear doors shall open for the amount of time specified, then
close.
Respond to door open button: Specifies that the rear doors shall respond to activation of
the rear door open button (once the car has arrived at the recall floor). If this option is
selected, the rear door open button remains operative at all times. If not selected, the rear
door open button will be rendered inoperative when the rear doors are closed at the recall
floor. (Note: The door open button will always remain operative when the associated doors
are open).
Hoistway Access Recall This control allows the recall operation, based on the param-
eter settings for the selected recall switch (1 - 6), to be activated by one of the Hoistway Access
direction switches. This allows the mechanic to recall the car prior to placing it on access opera-
tion.
Assign this recall to the following hoistway access input:
No access recall:
ATU - Access Top Up: Activation of the ATU switch/input shall cause the car to recall
per the selected recall switch (1 - 6) parameter settings.
ATD - Access Top Down: Activation of the ATD switch/input shall cause the car to
recall per the selected recall switch (1 - 6) parameter settings.
ABU - Access Bottom Up: Activation of the ABU switch/input shall cause the car to
recall per the selected recall switch (1 - 6) parameter settings.
ABD - Access Bottom Down: Activation of the ABD switch/input shall cause the car to
recall per the selected recall switch (1 - 6) parameter settings.
Earthquake Code Select the earthquake code and version/year being used.
Caution
Changing earthquake parameter settings may cause you to be out of compliance with the
selected code and may require a variance. Note that some parameter settings are under-
lined, indicating that the setting is in compliance with the selected code. If a setting is
changed to one that does not comply with the selected code, it will appear in RED.
9-67
iView - Controller View
Earthquake run mode: Specifies when the elevator should be allowed to run while under
Earthquake mode of operation. The elevator is allowed to run at a reduced speed (not to
exceed 150 fpm) as long as the counterweight has not been displaced from its guide rails.
None: The car is not allowed to run in earthquake mode.
Delay: The car is allowed to run after a delay.
Fire only: The car is allowed to run only during fire service. The car is also allowed to
run with the counterweight derailed if the car is below the counterweight.
Reaction to Seismic Device: Determines how the elevator should react to the activation of
a seismic switch.
Emergency Stop: Perform an Emergency stop then, after a brief delay, proceed to next
available floor in a direction away from the counterweight.
Stop at Next Floor: Stop at next available floor in direction of travel.
Freeze Car During Earthquake: Stop the car immediately during earthquake activity and
keep it shut down as long as the earthquake remains active. (Title 8 earthquake compli-
ance.)
Allow all inspection modes during earthquake operation if the counterweight derailment
device is not tripped: Specifies that the elevator should be allowed to run under all inspec-
tion modes of operation if the counterweight has not been displaced from its guide rails. If
the counterweight is derailed, only Cartop Inspection is allowed to run during earthquake
operation.
Drum Machine Defaults button: Sets the earthquake parameters to the code specified
default values for a drum machine installation.
Default button: Sets the earthquake parameters to the code specified default values.
Miscellaneous:
Counterweight displacement detection: If the job has a device to detect displacement
of the counterweight, enable this check box.
General
Recall Floor: Determines the recall floor for EMS service.
Phase 1 Timeout: Allows a time period to be set after which EMS Phase 1 service will time
out without activation of Phase 2 (in-car switch).
Bypasses Attendant in XX Seconds: Allows a time period to be set after which EMS service
will bypass Attendant service.
Fire service and heat detector operation bypass EMS: If enabled, Fire Service or Heat
Detector operation will immediately bypass EMS service.
Recall Switch Location (Front or Rear): Indicates the location of the EMS recall switch
(front riser or rear riser).
9-69
iView - Controller View
EMS Switch n - Front / Rear Tabs The EMS - Front and Rear parameters deter-
mine how the front and rear doors will operate during EMS Operation. The parameters and
descriptions are the same for both Switch 1 and 2 and for both Front and Rear tabs.
Opening - After Car Arrives At Recall Floor When MCE controlled is checked,
the following parameters determine what action will cause the doors to open when the car
arrives at a floor.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Constant pressure on door open button: Doors shall not open automatically upon arrival
at a floor. Constant pressure activation of the door open button is required to open the
doors. If the door open button is released before the doors are fully open, the doors shall
re-close.
Momentary pressure on door open button: Doors shall not open automatically upon
arrival at a floor. Momentary activation of the door open button initiates door opening.
In-car Opening When MCE controlled is checked, the following parameters deter-
9-71
iView - Controller View
In-car Closing When MCE controlled is checked, the following parameters determine
what action will cause the doors to close.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Passenger initiated: Doors shall not close automatically. The passenger initiated action
selected below shall be required to cause the door to close.
Door close button:
Does not close doors: Doors shall not respond to door close button.
Constant pressure: Doors shall close with constant pressure on door close button. If
the door close button is released before the doors are fully closed, the doors shall
reopen and stand open.
Momentary pressure: Doors shall close with momentary pressure on door close
button. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Momentary pressure if a car call is registered: Doors shall close with momentary
pressure on door close button if a car call is registered. Operational door reopening
devices shall initiate door reopening, and once fully open the doors shall stand open
until the door close button is again activated.
Car Call Button:
Does not close doors: Doors shall not close in response to car call button.
Constant pressure: Doors will close with constant pressure on car call button. Oper-
ational door reopening devices shall initiate door reopening, and once fully open
the doors shall stand open until the door close button is again activated.
Momentary pressure: Doors shall close with momentary pressure on car call but-
ton. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Car call registration closes doors: Doors will close if a car call is registered.
General
Emergency power type:
Group/Simplex: Select this option for a simplex or for a car that is part of a group that
controls the car during emergency power generator operation.
Overlay: Select this option if the car is controlled via discrete inputs from a remote
emergency power overlay controller during emergency power generator operation.
Backup power: Select this option if the car is using a battery backup unit, e.g. the Trac-
tion Auxiliary Power Supply (TAPS) from MCE.
Emergency power input: (does not apply to Backup power option)
Active low: Low (ground) voltage at the EPI input will cause emergency power to
become active.
Active high: High (110VDC) voltage at the EPI input will cause emergency power to
become active.
Recall Floor: Set the recall floor for this car (does not apply to Backup power option).
Recall Timeout: Defines the period of time after which the controller will stop attempting
to recall this car after a power failure has occurred (does not apply to Backup power
option).
Counterweight percentage: The weight of the counterweight divided by the sum of the full
load weight plus the weight of the cab. (applies only to Backup power option).
9
Apply emergency power door operation during in-car fire service: The emergency power
door operation settings shall be used, instead of the in-car fire service door operation set-
tings, when the car is on in-car fire service (applies only to Backup power option).
Disable fire warning light during backup power recall: The fire warning light and buzzer
shall be disabled during backup power recall operation (applies only to Backup power
option).
9-73
iView - Controller View
Emergency Power - Front / Rear Tabs The Front and Rear door parameters
determine how the front and rear doors will operate during Emergency Power 0peration. The
parameter descriptions are the same for both Front and Rear tabs.
Opening When MCE controlled is checked, the following parameters determine what
action will cause the doors to open when the car arrives at a floor.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically
upon arrival at the floor. When the car is sitting idle, the doors will open and remain
open.
Momentary pressure on door open button: Doors shall not open automatically upon
arrival at a floor. Momentary activation of the door open button initiates door opening.
Front door operation after recall: After Emergency Power Recall is completed, the doors
shall open as follows:
Open doors (and leave them open): Open the doors and leave them open.
Open doors for xx sec: Open the doors for the time designated and then close them.
Do not open doors: The doors shall remain closed.
Per the elevator code, the Front /Rear door operation after recall parameter (Emergency
Power > Front / Rear > Opening) must be set to Do not open doors if:
the car has a backup power source, e.g., MCEs TAPS, and
door closing is not automatic, e.g., the door Mechanism parameter (Emergency Power >
Front / Rear > Closing) is set to Passenger initiated.
Closing When MCE controlled is checked, the following parameters determine what
action will cause the doors to close.
Mechanism:
Automatic: With the presence of door open intent, doors shall open automatically upon
arrival at the floor. When the car is sitting idle, the doors will open and remain open.
Passenger initiated: Doors shall not close automatically. The passenger initiated action
selected below shall be required to cause the door to close.
Door close button:
Does not close doors: Doors shall not respond to door close button.
Constant pressure: Doors shall close with constant pressure on door close button. If
the door close button is released before the doors are fully closed, the doors shall
reopen and stand open.
Momentary pressure: Doors shall close with momentary pressure on door close
button. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Car Call Button:
Does not close doors: Doors shall not close in response to car call button.
Constant pressure: Doors will close with constant pressure on car call button. Oper-
ational door reopening devices shall initiate door reopening, and once fully open
the doors shall stand open until the door close button is again activated.
Momentary pressure: Doors shall close with momentary pressure on car call but-
ton. Operational door reopening devices shall initiate door reopening, and once
fully open the doors shall stand open until the door close button is again activated.
Car call registration closes doors: Doors will close if a car call is registered.
9-75
iView - Controller View
General
Fire service and heat detector operation bypass CFSS: Specifies that CFSS will be bypassed
when the car is in Fire Service operation and Heat Detector operation.
Recall When a CFSS mode is activated, the affected car is recalled to the activation floor
9-77
iView - Controller View
In-car When a CFSS mode is selected, and after the recall is complete, these settings
determine how in-car operation is invoked and how the car behaves during in-car CFSS opera-
tion.
In-car visual indicator behavior while in-car CFSS is active. This setting defines how the
in-car visual indicator (light, etc.) will behave while in-car CFSS is active.
Off: Indicator will remain off.
Solid: Indicator will light solidly.
Flash: Indicator will light intermittently (flash).
In-car switch to activate CFSS:
No switch: Select if there is no switch in the car to activate CFSS. If selected, set the
Resume normal service xx seconds after answering last call timer so that, after the
period of inactivity it defines has passed, the car will automatically exit CFSS opera-
tion.
Constant Pressure (2-position switch): Select if there is a key or other constant-contact
switch in the car to invoke in-car CFSS operation.
Momentary pressure (momentary switch): Select if there is a momentary-contact
switch (spring-loaded key or other) in the car to invoke in-car CFSS operation. If
selected, set the Resume normal service xx seconds after answering last call timer so
that, after the period of inactivity it defines has passed, the car will automatically exit
CFSS operation.
Resume normal service after xx seconds after answering last call: This determines how
long a recalled car will wait after answering the last call before timing-out and returning to
normal service.
Permit in-car activation without recall first: If selected, in-car CFSS may be activated by an
in-car switch without first initiating and completing a recall phase.
Cancel remaining car calls after answering a car call: If enabled, after the first CFSS car
call is answered, remaining calls are automatically canceled. Limits CFSS calls to one-at-a-
time.
Cancel car calls if doors are not fully closed: If enabled, during in-car CFSS operation, if
the doors are not fully closed, new car calls may not be registered and existing car calls will
be canceled.
Retain status during power loss: If enabled, the car will retain its in-car CFSS status after
recovering from a power loss.
CFSS Mode n - Front / Rear Tabs The CFSS Mode 1 and 2 > Front and Rear tabs
determine how the front and rear doors will operate during CFSS operation. The parame-
ters and descriptions are the same as those for EMS Switch 1 and 2 > Front and Rear tabs.
Please refer to EMS Switch n - Front / Rear Tabs on page 9-70
Enable In areas where flood operation is not required, this option may be left unchecked.
If enabled, the flood condition selections on the screen become active.
Flood Floors During flood operation, floors in danger of flooding shall be avoided. The
topography and construction at each job site will determine which and how many floors are
affected.
Click in the Flood floors column, the floors that should not be serviced during flood opera-
tion. A check mark will appear next to each selected floor.
9-79
iView - Controller View
Flood Operation Shall Override Depending upon code requirements, flood opera-
tion interaction with other operating modes is user selectable. For the mode(s) of operation
selected, where the requirements of Flood operation are not in agreement with those of the
selected mode, the requirements of Flood operation will take precedence.
During Flood operation, cars shall avoid the flood zones. If inside the flood zones, cars shall
proceed to the nearest floor outside the flood zone immediately unless the doors are open, in
which case the timer (if any) must first elapse.
Firefighters service: Select if flood operation requirements should override In-car fire-
fighter operation requirements.
In-car CFSS mode 1: Select if flood operation requirements should override In-car CFSS
mode 1 requirements.
If doors are open, after (timer) sec. If the car is inside the flood zone and doors are
open, this timer must elapse before the car proceeds to the nearest floor outside the
flood zones.
In-car CFSS mode 2: Select if flood operation requirements should override In-car CFSS
mode 2 requirements.
If doors are open, after (timer) sec. If the car is inside the flood zone and doors are
open, this timer must elapse before the car proceeds to the nearest floor outside the
flood zones.
Emergency medical service (EMS): Select if flood operation requirements should override
the requirements of EMS service.
If doors are open, after (timer) sec. If the car is inside the flood zone and doors are
open, this timer must elapse before the car proceeds to the nearest floor outside the
flood zones.
Independent Service: Select if flood operation requirements should override Independent
and Service operation requirements.
Attendant Service: Select if flood operation requirements should override Attendant Ser-
vice operation requirements.
Independent and Attendant service if doors are open, after (timer) sec. If the car is
inside the flood zone and doors are open, this timer must elapse before the car pro-
ceeds to the nearest floor outside the flood zones.
Substitute recall floor during flood operation Substitute floors can be desig-
nated for Emergency Power recall and Fire recall:
Emergency Power recall: Select the recall floor the elevator is to use during emergency
power operation under flood conditions.
Fire recall floor: Select if flood operation should modify fire recall operation. If so, set the
recall floor to be used if fire recall is activated during flood conditions.
General These parameters specify which doors to open if both doors are closed when the
car is placed on Attendant operation.
Open front doors: If the doors are closed when a car call is placed on Attendant Service,
the front doors shall be opened.
Open rear doors: If the doors are closed when a car call is placed on Attendant Service, the
rear doors shall be opened.
Cancel all car calls at next car call stop: Specifies that all car calls be canceled after the ele-
vator completes the first car call stop.
Enable arrival lanterns and gongs (on attendant service).
Attendant Service - Front / Rear Tabs The Front and Rear parameters determine
how the front and rear doors will operate during Attendant Service 0peration. The parameters
and descriptions are the same as for the Independent Service > Front and Rear tabs. Please
refer to Independent Service - Front / Rear Tabs on page 9-62.
9-81
iView - Controller View
Enable: Allows automatic stop controls to become active and arms the feature. The ele-
vator will not actually begin obeying automatic stop settings until the Automatic Stop
hardware input is activated, a timer is programmed or the Activate button and Send but-
ton are clicked.
General
Stop floor: The floor at which the car should pause and cycle doors.
Direction: Determines if the car will pause when travelling up, down, or both.
Door operation: Determines whether front, rear, or both doors will cycle.
Stop during Independent service: Allows Automatic Stop to take effect during Inde-
pendent service. Otherwise, a car on Independent service will not obey automatic stop.
Stop during Attendant service: Allows Automatic Stop to take effect during Attendant
service. Otherwise, a car on Attendant service will not obey automatic stop.
Door Dwell
Note
When Automatic Stop is enabled (Enable is checked), it may be turned On or Off using the fol-
lowing:
9-83
iView - Controller View
9-85
iView - Controller View
Sabbath trip interval timer: Specifies the interval between Sabbath operation trips. During
the time between trips, the car operates in Passenger mode. A value of Non-stop = contin-
uous Sabbath operation.
Sabbath door open timer: Specifies the amount of time the doors shall remain open at
each floor during Sabbath operation.
Sabbath operation status LED: LED lights green when Sabbath operation is activated.
Activate/Deactivate button: Sabbath operation can be activated/deactivated using this
button. When Sabbath operation has been activated, the button caption changes to Deac-
tivate. Sabbath operation can also be activated/deactivated via a key switch-input, iMoni-
tor command or a timer.
Sabbath Operation Floors: Specifies the floors (front, rear or both openings) that are to be
serviced during Sabbath operation.
To add or remove the check mark in an individual cell, click the cell.
To add or remove check marks from a group of cells, click and drag to select the cells,
then click Select or Deselect.
To add or remove check marks from a whole column, click the column label, then click
Select or Deselect.
Enable shuttle service: Indicates that the job has shuttle service and enables the shut-
tle service controls.
Enable shuttle hall call service: Determines if hall call service is enabled while on
Shuttle service.
Car Call 9
Dwell time: Sets the door dwell time when the car is responding to a car call.
Canceled by - Car call dwell time is canceled by any of the following that are checked.
Door close button: Activation of the door close button cancels car call dwell time.
Car call button: Activation of a car call button cancels car call dwell time.
Photo eye: Activation of the photo eye cancels car call dwell time.
9-87
iView - Controller View
Home floor doors close when When the car is parked at the home floor, the doors
are closed when the conditions of any of the following (that are checked) are met.
Door Close Timer: The doors are closed when the door close timer expires. The timer
starts when the first car call is registered.
Number of registered car calls: The doors are closed when the number of registered
car calls reaches this value.
Door close button pressed: If calls are registered, momentary activation of the door
close button causes the doors to close.
Heavy load status reached: The doors are closed when the car reaches heavy load sta-
tus.
When heat detectors are activated, the fire warning light will flash until all heat detectors have
been reset. The fire-warning buzzer will sound until the car is shutdown at a floor. A car that is
parked at a floor will open its doors and shut down. A car in motion will proceed in the current
direction to the next available floor where the heat detector is not tripped. If all heat detectors in
the current direction are tripped, the car will reverse direction and proceed to the first floor
where the heat detector is not tripped. If again all heat detectors are tripped, the car will pro-
ceed to the main fire recall floor unless the car is also on Fire Service, in which case the car will
proceed to the appropriate fire recall floor. Once the car is stopped at a floor it will automati-
cally open its doors and shut down. Then, if the machine room or hoistway heat detectors are
active, a signal is provided to disconnect the main power line and/or activate the sprinklers
where available.
Heat detectors operation overrides fire recall operation: If checked, heat detec-
tors operation will override fire recall operation even if fire recall is already in progress
when the heat detector(s) are activated. If not checked, fire recall operation will take pre-
cedence unless heat detectors operation is already in progress or has completed and the 9
car has been shut down when fire service is activated.
9-89
iView - Controller View
Configuration - Drive
The Drive Configuration tab allows you to set and view user adjustable drive parameters.
Pre-Start Sequence These parameters define the conditions under which the
machine may be energized and/or the brake lifted prior to the default After doors are locked
state. Warning! Do not use Pre-Start Sequence options until drive control parame-
ters have been adjusted for no rollback and good control at zero speed.
Allow machine to be energized: Defines the state of the doors required before the machine
is allowed to be energized:
After doors are locked: Doors must be locked before the machine may be energized
(the motor is energized and brake is fully picked). Any soft lift brake adjustment is
applied.
After door position monitor is activated: The door position monitor or doors locked
sensors must be activated before the machine may be energized (the motor is ener-
gized and brake is fully picked). If this option is selected, but the job doesnt have a
door position monitor, the machine is energized when the doors are locked. Any soft
lift brake adjustment is applied.
While door are closing: Doors must be closing, then the machine may be energized as
follows:
with motor and fully picked brake: The motor is energized and the brake is fully
picked. Any soft lift brake adjustment is applied.
with motor and partially picked brake: The motor is energized and brake is partially
picked. The Speed pick delay 1 must expire and the doors must be locked before the
brake is fully picked. After the brake is fully picked, Speed pick delay 2 must expire
before the elevator is allowed to move. No soft lift brake adjustment is applied.
with motor only: The motor is energized after the prescribed delay from doors clos-
ing. After the doors lock, the brake is fully picked, and Speed pick delay 1 must
expire before the elevator is allowed to move. Any soft pick brake adjustment is
applied.
Pre-Start Sequence Delay: After the doors have begun to close, wait the specified time
before energizing the machine as defined as defined in While doors are closing.
Note 9
Regardless of the selection above, the elevator is not allowed to move away from the landing
until the doors are locked and the Speed pick delay 1 timer has elapsed.
9-91
iView - Controller View
Speed Reference More detailed settings related to the speed reference mechanism.
Please refer to Calibrating Actual Car Speed on page 2-62.
Reference type: Tachometer, Encoder, Internal or Serial.
Resolution: This parameter affects elevator speed only for an encoder configuration.
Increasing this parameter will increase car speed.
Rotational coupling ratio: This parameter affects elevator speed only for an encoder con-
figuration. Increasing this parameter will increase car speed. If the encoder is shaft
mounted, this is normally set to 1. If the encoder is sheave or brake drum mounted, this
value must be calculated:
Motor Rated RPM x Sheave (Brake) Diameter
Coupling Rotational Ratio =
Encoder Follower Wheel Diameter
OR
Rated motor RPM: This parameter affects elevator speed for an encoder or serial configu-
ration. Increasing this parameter will increase car speed.
Rotational direction: Sets the encoder pulse stream order recognized by the controller as
indicating up or down travel. This parameter is used by all configurations except Internal.
Scaling: This parameter affects elevator speed only for a tachometer configuration.
Increasing this parameter will reduce car speed.
Current safety calibration: This is a duplicate of the Current safety calibration parameter
on the Drive > Safety tab. Please refer to Speed Reference on page 9-93.
Voltage safety calibration: This is a duplicate of the Voltage safety calibration parameter
on the Drive > Safety tab. Please refer to Speed Reference on page 9-93.
System
Rated line voltage: Line voltage being supplied to the drive.
Drive header voltage: Header voltage from -SCR page of job prints. Set Rated armature
voltage equal to the SCR drive header voltage. Please refer to Current Limit Adjustments
on page 2-63.
Drive header current: Header current from -SCR page of job prints. Please refer to Cur-
rent Limit Adjustments on page 2-63. Set Rated armature current equal to the SCR drive
header current. Please refer to Final Adjustment Before Running at Contract Speed on
page 4-7.
Normal rate limited stop: Determines the deceleration from leveling/releveling to zero
speed when the elevator stops normally at a floor. Please refer to Final Adjustment Before
Running at Contract Speed on page 4-7.
Emergency rate limited stop: Determines the deceleration from this speed at this instant
to zero speed when the elevator makes an emergency stop.
9-93
iView - Controller View
Synthetic armature current low-pass frequency: Compensates for loop circuit loss in creat-
ing the synthetic speed signal from the armature current. Increase to increase DC loop
current to the synthetic speed signal.
Over Current
Armature voltage limit: Determines the armature voltage limit. A value of 100% will allow
rated armature voltage. Lower values limit it according to the set percentage. Refer to your
job prints for SCR voltage and current ratings.) Please refer to Determine the Armature
Voltage Limit on page 4-7. Please refer to Armature Voltage Limit on page 2-64.
Armature current limit: Should not be set above 275%. Determines armature current limit.
Set so that, at full load, the Current Limit LED on the System 12 SCR drive will not light
when the car is accelerating (up) or decelerating (down). Please refer to Determine the
Armature Current Limit on page 4-7. Please refer to Armature Current Limit on page 2-
64.
Rated loop over-current: Determines the threshold current used for Loop Over Current
Safety monitoring. Should equal full load current of the hoist motor. Please refer to
Armature Overcurrent Overload Protection Adjustment on page 4-46.
Loop over-current fault time: Determines the amount of time the elevator will be allowed
to run before generating a fault when the machine draws 200% of Rated Loop Over-cur-
rent. Please refer to Armature Overcurrent Overload Protection Adjustment on page 4-
46.
Options
Start Gain (normal): Enables/Disables the PID Start (normal) screen controls. These
affect gain during initial run acceleration.
Start Gain (relevel): Enables/Disables the PID Start (relevel) screen controls. These gain
parameters are used for gearless machines with problems releveling into the floor to apply
higher gains during releveling. 9
Steady-State Gain (normal): Enables/Disables the PID Steady-State (normal) screen con-
trols. These parameters are used to reduce gains to correct oscillation that might occur at
steady state speed but not during acceleration and deceleration.
Stop Gain (normal): Enables/Disables the PID Stop (normal) screen controls. Used to
adjust drive gain during normal run deceleration.
9-95
iView - Controller View
Armature Test: Allows current loop testing at a set percentage of drive header value.
Please refer to Armature Current Test Procedure: on page 9-96.
Armature Current Test Procedure: Among other things, the armature current test
feature provides a means to troubleshoot the current command signal path and SCR drive cur-
rent producing capability. During the test, up to 300% of rated current can be commanded to
the drive. To prevent the motor from rotating and the elevator from drifting, no voltage will be
applied to the motor field and brake during the test.
PID - Standard Speed loop parameters. Refer also to any optional gains that may be
enabled to determine how they might interact with Standard gain settings. Please refer to Car
Response and Speed Loop Gain on page 2-65.
Proportional: Increase to provide faster response and tighter speed regulation. Excessive
values may result in oscillation and instability.
Integral: Adjusts accumulated error between the Pattern and Tach/Encoder. Adjust after
Proportional parameter. Increase to reduce steady speed error and improve tracking.
Excessive values may result in oscillation, speed overshoot, and/or instability.
Differential: Usually set to 0.0. Adjust after adjusting Proportional and Integral parame-
PID - Start (normal) Enabled/Disabled by the Start Gain (normal) Options selection.
These parameters are used to control rollback.
Proportional: If there is no rollback, set to equal Standard Proportional. If there is roll-
back, set to a greater value than Standard Proportional. Start Proportional Error gradually
decreases to Standard Proportional Error over the time period determined by the Transi-
tion Time setting below.
Integral: If there is no rollback, set to equal Standard Integral. If there is rollback, set to a
greater value than Standard Integral. Start Integral Error gradually decreases to Standard
Integral Error over the time period determined by the Transition Time setting below.
Differential: Usually set to 0.0. If there is no rollback set to equal Standard Differential. If
there is rollback, set to a greater value than Standard Differential. Start Differential Error
gradually decreases to Standard Differential Error over the time period determined by the
Transition Time setting below.
Transition Time: Determines the transition time from Start (Normal) to Standard gain set-
tings as described above. Usually set to 0.25 seconds.
PID - Stop (normal) Enabled/Disabled by the Stop Gain (normal) Options selection.
Integral: If elevator spots while approaching floor, increasing Stop Integral may help.
9-97
iView - Controller View
PID - Start (relevel) Enabled/Disabled by the Start Gain (relevel) Options selection.
Used for gearless machines with problems releveling into the floor to apply higher gains during
releveling. Please refer to Motor Control Adjustments on page 4-23.
Proportional: If the car has problems releveling into the floor, set equal to or greater than
Standard Proportional. After the car has stabilized at leveling speed, this value will
decrease to the Standard value.
Integral: Adjust after adjusting Proportional Error above. If the car has problems relevel-
ing into the floor, set equal to or greater than Standard Integral. After the car has stabi-
lized at leveling speed, this value will decrease to the Standard value. Excessive values may
cause oscillation.
Differential: Adjust after adjusting Integral Error above. If the car has problems releveling
into the floor, set equal to or greater than Standard Differential. After the car has stabilized
at leveling speed, this value will decrease to the Standard value.
Transition Time: Determines the transition time from Start (Relevel) to Standard gain set-
tings. Default is 1.0 seconds.
Miscellaneous
Error Compensation: Feed-forward gain. Increase to provide better tracking speed regula-
tion. Excessive values may result in oscillation. May also be adjusted to help with a spot-
ting problem. This is a key parameter for accurate tracking. Please refer to Error
Compensation on page 2-66.
Caution
Incorrect filter settings may result in oscillation (not enough high frequency filtering) or in
unresponsive, erratic control of car speed (too much high frequency filtering). Consult MCE
Technical Support if you are not familiar with adjusting filters. Always work with gain set-
tings (Drive Configuration/Control tab) before changing filter default settings.
9-99
iView - Controller View
Note
The Differential Low-pass Frequency filter affects all differential frequency settings made on
the Drive Configuration/Control tab. If a differential adjustment is set to 0.0, it is unused and is
not affected by this filter setting.
Process low-pass frequency: Filters higher frequency signals in the output of the speed
control loop. If the value is too high, oscillation may occur but the system is more respon-
sive. If the value is too low, control may become unresponsive. The typical, recommended
value is 999Hz.
Notch Filter Enables the current notch filter for the System 12 SCR drive. When enabled,
Bandwidth
-10
-20
Gain (dB)
-50
-60
0 100
Frequency (Hz)
9-101
iView - Controller View
Notch Settings When setting the notch filter, you can determine the center frequency
of the oscillation using an oscilloscope. This frequency is what you enter as the Process Notch
Frequency. The other two settings (Bandwidth and Depth) are more subjective and you will
need to experiment to find the best setting.
Caution
Notch Filtering removes a center frequency and some surrounding frequencies (depend-
ing on the bandwidth or Q setting) from the speed command to the drive. If improperly
used, notch filtering may remove a legitimate control frequency, resulting in poor system
control.
Use an oscilloscope to monitor the Speed Feedback signal. (See the following illustration.)
Adjust the oscilloscope to determine the Time it takes the oscillation frequency to com-
plete one full cycle. (It may be easier to determine the time for n cycles. If so, use the for-
mula T1 = Tn / n.)
Use the formula 1/T1 (single cycle time) = Frequency.
Set Process Notch Frequency to the calculated frequency
Determine and set Q value. The frequency of the oscillation might vary a little. If you can
determine bandwidth (range) of the frequencies to be blocked, you may use the formula
Q=Frequency/Bandwidth to calculate a beginning point for the bandwidth (Q) value. The
object is to use the highest Q value possible (the narrowest possible notch). It is important
to keep the notch as narrow as possible to avoid blocking legitimate control frequencies
and making car operation unstable.
Set Process Notch Depth. The range is from 1 to 100,000. Start out using the maximum
setting for the most complete suppression of the selected frequency. You may have to
experiment with reducing the setting in fixed increments to achieve the best results.
Monitor the signal and modify Q and Notch in defined increments until you reach the best
possible balance between system control and reduced oscillation.
Figure 9.3 Determine Frequency of Oscillation
Time (T)
Amplitude
Time
Frequency = 1/T
Q = Frequency/Bandwidth
9-103
iView - Controller View
Speed Control
Armature Voltage: Input PID.
Dampening speed: Increase to remove oscillation by dampening speed loop voltage.
Excessive values may impact system performance. Adjust after adjusting PID - Stan-
dard, Proportional and Integral parameters on the Control tab. Please refer to Car
Response and Speed Loop Gain on page 2-65.
Dampening torque: Usually set to 0.0. Increase to remove oscillation by providing
voltage dampening for the current loop. Armature Voltage, Dampening Speed is more
effective and should be adjusted first.
Low-pass frequency: Determines how much variation will be allowed in the signal
received from the armature voltage. Recommended range 40 - 99 Hz.
High-pass frequency: Determines how much of the DC component will be removed
from the armature feedback voltage before the signal is used in the speed loop calcula-
tion. Increase to reduce the dampening effect on the system (Dampening Speed and
Dampening Torque become less effective).
Armature Current: Input current loop.
Dampening speed: Increase to remove oscillation by providing current dampening for
the speed loop. Excessive values may impact system performance.
Dampening torque: Usually set to 0.0. Increase to remove oscillation by providing cur-
rent dampening for the current loop. Armature Voltage, Dampening Speed is more
effective.
Low-pass frequency: Determines armature current signal smoothing.
High-pass frequency: Determines how much of the DC component will be removed
from the armature feedback current before this signal is used in the velocity loop cal-
culation. Increase to reduce the dampening effect on the system (Dampening Torque
becomes less effective).
Current Control
Dampening current: Dampens any oscillation caused by speed loop gain adjustments.
Dampening current adjustment will only be effective if other system parameters are also
adjusted. Contact MCE Technical Support before adjusting this parameter.
9-105
iView - Controller View
Note
System 12 Drive trim pot R376 and test point IZO are used to set the zero crossing point if
necessary. R376 is set and locked at the factory and should not require adjustment. If, when
adjusting ride quality of the car, you notice a sharp bump when transitioning from acceleration
to steady speed or from steady speed to deceleration, you may need to adjust zero crossing.
Output DAC: Adjust to nullify the Output offset when adjusting initial System 12 drive out-
puts. Adjust while monitoring SCR-LGA board jumper JP3.
Input ADC: The Input ADC offset values are determined when the drive setup procedure is
performed (Controller > Setup > Drive tab).
Level Up Top: The learned distance from the bottom floor to the top of the floor magnet as
determined by the Level Up sensor.
Level Up Bottom: The learned distance from the bottom floor to the bottom of the floor
magnet as determined by the Level Up sensor.
Level Down Top: The learned distance from the bottom floor to the top of the floor magnet
determined by the Level Down sensor.
Level Down Bottom: The learned distance from the bottom floor to the bottom of the floor
magnet determined by the Level Down sensor.
9-107
iView - Controller View
Configuration - General
The Configuration > General tab supports general building parameters. The tabs include:
General: Car label, Car identifier and Simplex car parameters.
Floor Data: Floor specific data including openings, false floors, door boost (see page 9-
109).
Car Call Eligibility: Car call permission/restriction for each opening (see page 9-110).
General Tab
Car label: Assigned by building management.
Car identifier: Used by the iCUE Central or Local Dispatcher for communication with the
car in group systems. Set from 1 to 20.
Caution! The car identifier must be unique for every car within a group of elevators (no to
cars assigned the same car identifier).
Group identifier: The Group ID (1) cannot be changed. All other IDs are reserved for
future use. If you need advanced System addressing information please contact MCE.
Simplex car: This car is not part of a group.
Note
Rather than proceeding floor-by-floor, column-by-column, you may choose to select a column
head or multiple cells and use the system wide Select/Deselect controls to set all floors the
same for that topic (where appropriate). You can also move from field to field using the Tab key.
9-109
iView - Controller View
System wide operations: For high- or mid-rise buildings, use the system wide controls to speed
the configuration process:
Note
The existence of front and/or rear openings is determined by your selections on the preced-
ing, Floor Data tab. If an opening is not recognized to exist, it will not be selectable.
9-111
iView - Controller View
Configuration Settings These controls allow you to select the active or default car call
eligibility configuration and to select the same configuration or any of the other configurations
to be active if one of the following special operating modes is activated.
Sequential step scan car calls This option allows compliance with the ICC/ANSI
A117.1-2003 requirement to accommodate passengers who are short or are using a wheel chair
in buildings where the car control buttons are more than 48 inches above the floor. Scan Up and
Scan Down buttons are used. When Scan Up is pressed, the car call buttons above the current
floor are scanned. When Scan Down is pressed, the car call buttons below the current floor are
scanned. When the button is released for more than 2 seconds, a call is registered for the last
floor selected. This option is enabled when the Sequential Step Scan inputs are programmed
(see Configuration - I/O Boards on page 9-113).
Front inputs scan front and rear car call buttons: This option allows a single Scan Up and
Scan Down button to be used to scan both front and rear car call buttons.
The circuit board complement of the iController (IMP), iLink (CTP) and Serial Car Operating
Panel (COP 1 - 4)) can be changed if required. When boards are added or connections are
changed, this tab allows you to reassign inputs and outputs accordingly.
IMP / CTP In the window shown below (Configuration > I/O Boards > Configuration
tab), a Multiple Input AC (ICE-MIAC) board connected to the iBox Main Processor (ICE-IMP)
board is selected for editing. When the edit button is clicked, the Terminal Configuration (IMP -
MIAC) dialog, shown on the following page, is displayed.
9-113
iView - Controller View
Using the I/O Board Configuration Tab This tab is used to program I/O Board
inputs and outputs, should you desire to make changes.
To add a board:
1. Select IMP / CTP or COP 1 - 4. Note: COP 4 is not available on Cartop software version
1.1.15 or greater.
2. Locate the board in the Boards box on the right of the Configuration tab.
3. Drag the board into the ICE-IMP (iControl), ICE-CTP (iLink cartop box) or COP 1 - 4
(Car Operating Panel) enclosure as appropriate. Release the mouse button.
4. To rearrange a board along the bus representation, highlight it and click on the associ-
ated up/down controls. The board will move accordingly.
5. To remove a board, select and click Delete.
To add or change the input or output assignment to a board terminal:
1. Click to select the desired board and click Edit.
2. Select a signal group from the drop down list in the Signals box.
3. Select a signal from the list and drag it to the desired pin in the Terminals box.
4. To remove a signal from a pin, drag it into the trash or right click and then click Remove
signal. To remove all signals, click the Clear all button.
5. Click OK to approve your configuration.
6. Click Send to send your changes to the controller.
7. Or, click Cancel to close the dialog without saving any changes.
Each input or output may be assigned to only a single terminal.
Terminal Configuration (IMP - MIAC)
I/O Assert The I/O Assert feature allows the user to bypass the current state of a termi-
To use IO Assertion:
1. Acquire write privilege (select Acquire from the iView Write privilege menu).
2. Set the iBox FAULT/FUNCTION BYPASS switch to ON.
3. Click the Assert Session Start button
(Configuration > I/O Boards > Con-
figuration tab). The assert session
begins and a 15 minute timer begins
counting down the time remaining for
this session.
4. Select an I/O board (Configuration > I/O Board > Configuration tab) and click View.
Notice that the state for all terminals, shown in the drop down list next to the indicator
LED, is Pass, meaning that the current (default) state of the terminals is not bypassed.
Terminal Output dialog (view terminal status and set I/O assertions)
9-115
iView - Controller View
5. For the desired terminal, select On or Off from the drop down list next to the indicator
LED to bypass the current state and assert the desired state.
6. You may set the state for additional terminals on this board or select a different board
on which to set terminal assertions.
7. The Assert Session will end when one of the following occurs; the timer elapses, the
FAULT/FUNCTION BYPASS switch is set to OFF or the Assert Session Cancel button is
clicked. When the session has ended, all I/O are returned to the default Pass state.
Serial COPs - COP1 thru COP4 In the window shown below, a Serial Car Operating
Panel (ICE-COP) board is selected for editing. Note: COP4 is not available on Cartop software
version 1.1.15 of greater.
Edit button: When the edit button is clicked, the Terminal Configuration (CTP - SERIAL
COP) dialog is displayed (see page 9-117).
View button: Use this button to view the current state (On or Off) of the inputs and out-
puts and to assert a specific state (see I/O Assert on page 9-115).
Reset COP button: This button causes the processor on the ICE-COP board to reset.
The method of assigning inputs and outputs to terminals is the same for Serial COP boards as
Caution
The Terminal Configuration dialog reassigns the signal assignments to circuit board pins in
controller SOFTWARE. You must also make the correct hard connections to avoid damage
or incorrect operation. 9
9-117
iView - Controller View
Disable Door Enable Output: A check specifies that the Door Enable Output is to be dis-
abled under the selected condition(s).
Disable Hall Door Button Output: A check specifies that the Hall Doors Button Output is
to be disabled under the selected condition(s).
Disable Automatic Closing Output: A check specifies that the Hall Doors Button Output is
to be disabled under the selected condition(s).
Toggle Output: The Toggle Output (MOR board > Custom Outputs signal) can be used to
convert a steady state Custom Output to a toggled output. Use this control to Enable the
Toggle Output and to set the On time and Off time of the toggle.
9-119
iView - Controller View
Car Call Enable 1 Override input: Input that allows Car Call Enable Operation 1 to be
overridden, setting car call eligibility to the currently active configuration.
Car Call Enable 2 Override input: Input that allows Car Call Enable Operation 2 to be
overridden, setting car call eligibility to the currently active configuration.
Car Not Empty Sensor Input: Input from a sensor that detects the presence of passen-
gers in the car. Used with the CFSS Recall empty car feature to determine when the
car is empty (see Car Operation - CFSS Tab on page 9-76).
CC Eligibility Config (1 through 8): One of eight inputs used to manually select a par-
ticular car call eligibility configuration configured on the General > Car call eligibility
tab. If more than one input is active, the lower-numbered input will have control.
Please refer to General - Car Call Eligibility Tab on page 9-110.
CFSS In Car Switch 1: Input from an in-car switch that initiates in-car Commandeer
For Special Services mode 1 as specified on the Configuration > Car Operation > CFSS
tab. Please refer to Car Operation - CFSS Tab on page 9-76.
CFSS In Car Switch 2: Input from an in-car switch that initiates in-car Commandeer
For Special Services mode 2 as specified on the Configuration > Car Operation > CFSS
tab.
Emerg. Pwr. Auto Car Select: Input from a key switch, if so set by the user, may be
required before the car is automatically selected to run on emergency power. Condi-
tions that affect this operation are specified on the Configuration > Car Operation >
Emergency power tab. Please refer to Car Operation - Emergency Power Tab on
page 9-73.
Emerg. Pwr. Auto Recall: Input from a key switch, if so set by the user, may be
required before the car will recall on emergency power. Conditions that affect this
operation are specified on the Configuration > Car Operation > Emergency power tab.
Emerg. Pwr. Manual Car Select: Input from a key switch used to manually select the
car to run on emergency power.
Emergency Dispatch: Input from a key switch used to force the car to automatically
service the building in a pre-defined pattern, cycling the doors when stopping at floors.
Emergency Dispatch Override: Input from a key switch used to override Emergency
Dispatch operation usually manually invoked via the Emergency Dispatch key switch
or automatically upon detection of a failure of the hall call bus.
Emergency Power: Input from a contact closure that indicates whether the system is
running on commercial or generator power. Emergency power operation proceeds first
in a recall phase, where cars are recalled to a floor and then in a Run phase where one
or more cars are selected to run under the emergency power generator using the emer-
gency power performance pattern.
Emergency Power Manual Override: Input from a key switch or contact closure used to
bypass the emergency power recall operation.
Emergency Power Permission to Run: Input from a contact closure that allows the car
to run under the emergency power generator.
Emergency Power Return: Input from a contact closure that initiates emergency power
recall.
Emergency Stop Input: When this input is activated, the car makes an emergency stop
and all calls are canceled. This input has priority over all modes of operation including
Fire Service.
EMS Car Switch: Input from a key switch located inside the car that initiates in-car
9-121
iView - Controller View
pattern, and has car call restrictions according to the car call eligibility set selected on
the Configuration > General > Call Eligibility tab. Please refer to General - Car Call
Eligibility Tab on page 9-110.
Light Load Input: Input from a discrete load weigher light load output.
Main Floor Smoke: Input from the smoke sensors located at the main recall floor. Acti-
vation of these sensors will initiate recall to the alternate recall floor.
Other Cars Alternate: Input from other car (in the same system) smoke sensors located
in the hoistway or machine room if the machine room is located at the main recall
floor. Activation of these sensors will initiate recall to the alternate recall floor.
Other Cars Main: Input from other car (in same system) smoke sensors located in the
hoistway or machine room if the machine room is located at any floor other than the
main recall floor. Activation of these sensors will initiate recall to the main recall floor.
Over Load Input: Input from a discrete load weigher over load output.
Passing Floor Gong Enabled: Input, from a key switch, that enables the audible pass-
ing floor gong in the elevator car.
Power Transfer: Input from a key switch or contact closure used to force the car to stop
at the next available floor and open its doors. This input is usually used right before
power is transferred from the emergency power generator to commercial power.
Primary Fire Switch BYPASS: Input from a keyed switch in the building lobby, that
allows a Fire Phase I initiating device (smoke detector, fire alarm, etc.) to be bypassed
or unlatched as specified per code.
Primary Fire Switch OFF: Input from a keyed switch in the building lobby, that termi-
nates Fire Phase I if appropriate (as specified per code).
Primary Fire Switch ON: Input from a keyed switch in the building lobby, that initiates
Fire Phase I and recalls the car to the main fire recall floor. Recall particulars are fire
code specific. Code is selected on the Configuration > Car Operation > Fire Service tab
and particulars may be modified on the Fire code tabs.
Recall Switch x: (x = 1 - 6) One of six switches that places a car in Recall mode, recall-
ing it to an assigned floor. Switch priority, door operation, car call disposition, and
more are configured on the Configuration > Car Operation > Elevator recall tab. Please
refer to Car Operation - Elevator Recall Tab on page 9-64.
Recall Switch x Unlatch: (x = 1 - 6) A car that has been or is being recalled after
momentary activation of the elevator recall switch shall immediately resume normal
operation when this input is activated (regardless of the value of the Resume normal
operation after --- sec timer).
Sabbath Operation Switch: Input from a key switch used to force the car to automati-
cally service the building based on the selected floor eligibility so that the passengers
can travel from floor to floor without having to press any buttons.
Sabbath Override Input: When this input is activated, the Sabbath Operation Switch
input is ignored and, if already activated, Sabbath Operation is cancelled.
Secondary Fire Switch ON: Input from a keyed switch in a different location than the
Primary Fire Switch, that initiates Fire Phase I and recalls the car to the alternate fire
recall floor. Recall particulars are fire code specific.
Shuttle Service: Input from a key switch used to turn Shuttle service On and Off.
Shuttle Service Override: Input from a key switch used to override Shuttle service.
Swing Automatic Operation: When activated, the car will automatically enter Swing
Front Door
Disable Front Hall Door Buttons: Input used to disable the front hall door buttons.
Front COP2 Door Close Button: Input from the front auxiliary door close button:
Front COP2 Door Hold Button: Input from the front auxiliary door hold button.
Front COP2 Door Open Button: Input from the front auxiliary door open button.
Front COP2 Door Stop Button: Input from the front auxiliary door stop button (active
low).
Front Constant Pressure Close: Activation overrides front door close software settings.
Front Constant Pressure Open: Activation overrides front door open software settings.
Front Door Close Button (COP1): Input from the front main door close button.
Front Door Hold Button (COP1): Input from the front main door hold button.
Front Door Open Button (COP1): Input from the front main door open button.
Front Door Stop Button (COP1): Input from front main door stop button (active low).
Front Hall Door Close Button: Input from a front hall door close button.
Front Hall Door Hold Button: Input from a front hall door hold button.
Front Hall Door Open Button: Input from a front hall door open button.
Front Hall Door Stop Button: Input from a front hall door stop button (active low).
Front Momentary Pressure Close: Overrides front door close software setting.
Front Momentary Pressure Open: Overrides front door open software setting.
Front Photo Eye Cut Out: Input from a front key switch - disables photo eye operation
Rear Door 9
Disable Rear Hall Door Buttons: Input used to disable the rear hall door buttons.
Rear COP2 Door Close Button: Input from the rear auxiliary door close button:
Rear COP2 Door Hold Button: Input from the rear auxiliary door hold button.
Rear COP2 Door Open Button: Input from the rear auxiliary door open button.
Rear COP2 Door Stop Button: Input from the rear auxiliary door stop button (active
low).
9-123
iView - Controller View
Rear Constant Pressure Close: Activation overrides rear door close software settings.
Rear Constant Pressure Open: Activation overrides rear door open software settings.
Rear Door Close Button (COP1): Input from the rear main door close button.
Rear Door Close Limit: Input from rear Door Close Limit switch.
Rear Door Hold Button (COP1): Input from the rear main door hold button.
Rear Door Open Button (COP1): Input from the rear main door open button.
Rear Door Open Limit: Input from rear Door Open Limit switch.
Rear Door Photo Eye: Input from rear door photo eye.
Rear door safe edge: Input from rear door safe edge.
Rear Door Stop Button (COP1): Input from rear main door stop button (active low).
Rear Hall Door Close Button: Input from a rear hall door close button.
Rear Hall Door Hold Button: Input from a rear hall door hold button.
Rear Hall Door Open Button: Input from a rear hall door open button.
Rear Hall Door Stop Button: Input from a rear hall door stop button (active low).
Rear Momentary Pressure Close: Activation overrides rear door close software setting.
Rear Momentary Pressure Open: Activation overrides rear door open software setting.
Rear Photo Eye Cut Out: Input from the rear key switch that disables rear door photo
eye operation.
9-125
iView - Controller View
9-127
iView - Controller View
Car Call Enable 1 (2) Override output: These respective outputs are active when the
9-129
iView - Controller View
Direction arrow up 2: (see Direction Arrow Up) This output is disabled during Fire ser-
vice to accommodate the ASME A17.1 code requirement to disable hall fixtures at all
floors except the lobby during Fire service.
Earthquake Buzzer: Active when the car is on Earthquake operation (earthquake sen-
sor or counterweight derailment inputs active).
Earthquake Light: Active when the car is on Earthquake operation (earthquake sensor
or counterweight derailment inputs active).
Egress Floor Gong: This output will activate for 300 msec. when the car arrives at the
egress floor and opens the doors in response to a hall or car call. This output is used
to activate an audible indicator to inform visually impaired passengers that the eleva-
tor has arrived a the main egress floor of the building. The egress floor is selected on
the Configuration > Car Operation > Passenger tab.
Emerg. Pwr. Car Selected to Recall: Active when this car is selected to lower the recall
floor on emergency power.
Emerg. Pwr. Car Selected to Run: Active when this car is selected to run on emergency
power (see Configuration > Car Operation > Emergency power tab).
Emergency Power Car Done Recall: Active when the car has completed the recall on
Emergency Power operation.
Emergency Power Phase I (Simplex): Activated when the Emergency Power input is
activated and remains on until all cars have returned to the recall floor.
Emergency Power Phase II (Simplex): Activated when all car have reached the recall
floor and remains on until normal power is reinstated.
Emergency Power Priority Status: Activated when the car is on EMS phase 2, CFSS
phase 2 and Fire Service Phase II.
Emergency Power Recall Complete: Activated when the car is on Emergency Power
and is at the recall floor with the doors fully open.
Emergency Power Service (Simplex): Active when the car is on Emergency Power
(Emergency Power input active). Configure using Configuration > Car Operation >
Emergency power tab.
EMS Car Buzzer: This output comes on when the EMS 1 or EMS2 hall switch is acti-
vated and turns off when the car reaches the EMS floor (phase 1 return). It is used to
activate an in-car audible buzzer to alert passengers that the car is being comman-
deered for Emergency Medical Service.
EMS Car Light: This output comes on when the EMS 1 or EMS2 hall switch is activated
and stays on until the car returns to normal service. It is used to activate a visual indi-
cator to alert passengers that the car is on Emergency Medical Service.
EMS Hall Light 1 (2): These respective outputs come on when the EMS1 (or 2) hall
switch is activated and turns off when the in-car switch is activated. It is used to acti-
vate a visual indicator to alert EMS personnel that the EMS1 or EMS2 signal has been
registered. EMS settings and configured on the iView Configuration > Car Operation >
EMS tab.
Empty Car Output: This output is active when one or more of the following are true:
Empty Load Input = On, Car Not Empty Sensor Input = Off or the car weight is below
the Empty load threshold setting on the Configuration > Load Weigher tab.
Empty Load: This output is active when the car weight from an analog load weigher is
9-131
iView - Controller View
Heavy Load: This output is activated when the load in the elevator exceeds the thresh-
old set for hall call bypass on the Configuration > Load Weigher tab. The load sta-
tus will only change once the car has stopped at a landing and has opened its doors.
Hoistway Inspection: Active when the car is on Hoistway-Access Inspection operation.
In-Car Fire Door Operation: This output is typically used by the freight door controller
to adjust the door operation per the code requirements for in-car fire service and in-
car fire service recall operations. This output is ON during in-car fire service and also
during in-car fire service recall until the doors are fully closed.
In-Car Fire Hold: This output is ON during In-car fire service hold operation.
In-Car Fire Recall: Typically used to re-enable the hall door buttons station during in-
car fire service recall, this output is ON during In-car fire service recall operation.
In-Car Inspection: Active when the car is on in-car inspection operation.
In Use Light: This output turns on when the car doors a not fully closed or there is a
demand to move the car.
Independent Service Indicator: Active when the car is on Independent service.
Inspection Output: Active when the car is on any Inspection operation.
Light Load: Activated when the Light Load Input is active or when the weight in the
car, detected by an analog load weigher, is less than the Light load threshold.
Machine Room Inspection: Active when the car is on machine room inspection opera-
tion.
Mechanically In Service: This output is normally active (when the car is running nor-
mally), but is turned off when the car appears to be mechanically out of service. Only
two statuses are checked for clearing this output: Safety String and Motor Limit Timer.
Overload: This output is on when the overload threshold, value at which it may be con-
sidered unsafe to move the elevator, has been reached. The car will remain at the floor
with doors open (overridden by fire phase II). Typically a visual and/or audible indica-
tor is used to alert passengers that the car is overloaded.
Pass Code Failure: Activated momentarily when the time limit expires prior to a cor-
rect pass code having been entered on the Car Operating Panel.
Pass Code Success: Activated momentarily when a correct pass code is entered at the
Car Operating Panel.
Passing Floor Gong: This output is on whenever the car passes a floor. Timer options
are located on the iView Configuration > Car Operation > Devices tab.
Passing Floor Gong Enabled: This output comes on whenever the car passes a floor
and the passing floor gong enable button has been pushed. Timer options are located
on the iView Configuration > Car Operation > Devices tab.
Recall Switch 1 through 6: One of six outputs indicating that its respective switch has
been activated and has placed a car in Recall mode, recalling it to an assigned floor.
Switch priority, door operation, car call disposition and more are configured on the
iView Configuration > Car Operation > Elevator recall tab.
Retiring Cam: This output is turned ON to lock the hoistway doors if all doors (front
and rear) are fully closed and there is a demand to move the car. Otherwise it is OFF.
This output is turned OFF if the car is stopped in between floors.
Sabbath Operation Indicator: This output is on when the car is on Sabbath operation
(Configuration > Car Operation > Sabbath operation tab).
Seismic Switch: Activated when the seismic switch circuitry on the Earth Quake (ICE-
9-133
iView - Controller View
Front (Rear) Door Enable: Used to cut power to front/rear doors, these outputs are
normally ON and can be configured, on the Configuration > I/O Board > Configurable
outputs tab, to turn OFF during any combination of the following modes and/or condi-
tions: Test mode, Inspection operation, In-car stop switch activated and doors are fully
open, Door stop input activated.
Front (Rear) Door Hold End: This output turns on five seconds prior to expiration of
the Door hold timer (see Front (Rear) Door Hold Function).
Front (Rear) Door Hold Function: This output is active during the time the doors are
being held by the Door hold timer (Configuration > Car Operation > Passenger >
Door Operation - Door Dwell Timers).
Front (Rear) Door Left Open: This output is used for non-automatic front/rear doors
and shall be ON if the front/rear doors are open and a hall call button is pressed. Oth-
erwise it shall be OFF.
Front (Rear) Door Lock Power: This output is activated when the doors are closed and
locked and is used for door operators that need a separate signal to hold the doors
closed.
Front (Rear) Down Car Lantern: This output is activated (usually a double ding: on-
off-on) to announce the elevator's intention to go down after the doors start to open by
operating the front or rear in-car gong/lantern assembly. This will happen when a
down hall call has been entered and the car has reached the floor from which that call
originated, or the doors are open and a car call is entered for a floor below. Timer
options are located on the Configuration > Car Operation > Devices tab.
Front (Rear) Nudging Audible: This output is activated when door nudging has been
activated. Options located on Configuration > Car Operation > Passenger tab.
Front (Rear) Door This Car Up: This output is active when the car is at the lobby floor
and has been selected as the next car to go in the UP direction.
Front (Rear) Up Car Lantern: This output is activated (usually a single ding) to
announce the elevator's intention to go up after the doors start to open by operating
the front or rear in-car gong/lantern assembly. This will happen when an up hall call
has been entered and the car has reached the floor from which that call originated, or
the doors are open and a car call is entered for a floor above. Timer options are located
on the Configuration > Car Operation > Devices tab.
Car Calls - Front COP 1
Car Call - Front COP 1 light, Floor 1150: Outputs to the front Car Operating Panel 1
lights.
Car Calls - Rear COP 1
Car Call - Rear COP 1 light, Floor 1150: Outputs to the rear Car Operating Panel 1
lights.
Car Calls - Front COP 2
Car Call - Front COP 2 light, Floor 1150: Outputs to the front Car Operating Panel 2
lights.
Car Calls - Rear COP 2
Car Call - Rear COP 2 light, Floor 1150: Outputs to the rear Car Operating Panel 2
lights.
9-135
iView - Controller View
Active Mode - Demand Down Peak: Output is active when the current dispatching
9-137
iView - Controller View
Mac Addresses: Unique hardware address for each of the iBox Ethernet ports.
Version: iBox and iView version information.
Miscellaneous: Boot flags are used during internal test. Time zone indicates the time zone
where the equipment is installed and is used primarily for a monitoring reference.
Network Information: Ethernet information for each of the iBox ports.
9-139
iView - Controller View
Device configuration
9-141
iView - Controller View
Control Tab - Options The control tab provides access to motor control settings.
Field operation: Selects between open loop and closed loop motor field operation. Closed
loop uses current feedback in motor field control while open loop uses internal references.
Caution
Perform field calibration before setting Field Operation to closed loop (View > Layouts >
Motor Field). Please refer to Motor Field Calibration on page 2-53
PID
Field proportional: Controls the response of the motor field voltage. Increasing this gain
provides faster response and tighter regulation but high values may cause oscillation and
instability in the motor field. Options - Field Operation must be set to Closed to enable this
control.
Field integral: Adjust field proportional first. Field integral reduces the accumulated error
between the desired and actual motor field voltage. Higher values may cause oscillation.
Options - Field Operation must be set to Closed to enable this control.
Field forcing delay: Determines the delay between when the door begins to close and the
start of forcing motor field. This may help reduce heating of the motor field by minimizing
the amount of time the motor field voltage is at field forcing voltage.
Filter
Field current low pass frequency: This parameter adjusts the amount of filtering (smooth-
ing) that is applied to the analog motor field current feedback. Generally the default value
does not need to be modified. If a change is required, a reduction of the default value will
most likely be needed. Since closed-loop motor field control is based upon the detected
motor field current, proper operation can be affected if insufficient or excessive filtering is
performed.
Field voltage low pass frequency: This parameter adjusts the amount of filtering (smooth-
ing) that is applied to the analog motor field voltage feedback. Generally the default value
does not need to be modified. If a change is required, a reduction of the default value will 9
most likely be needed.
9-143
iView - Controller View
Motor Field - Configuration Tab This tab displays learned values of motor voltage,
output timer, and current reference information across the motor output range. THESE VAL-
UES SHOULD NOT BE CHANGED WITHOUT CONSULTING MCE TECHNICAL SUPPORT.
Configuration - Pattern
From the Configuration > Pattern tab, you can adjust parameters that determine the profile of
the patterns used by the system in its various operating modes. The illustration below shows a
pattern with adjustment points called out.
High Speed
Deceleration
Acceleration
Approach Deceleration
Approach Jerk
Initial Jerk
The Pattern > Common tab, sets parameters that apply to all profiles. The parameters that
shape the various patterns are adjusted on the Pattern > Modes tab.
9-145
iView - Controller View
General
Dead zone These parameters define a zone in which, or a distance from a floor at which,
an action may occur. Please refer to Final Stop on page 4-30
Dead zone distance: The distance from the final floor position where the stop command is
issued (transition from leveling speed to normal rate limited stop) on the initial run to the
floor (i.e., leveling operation).
Re-level dead zone distance: The distance from the final floor position where the stop
command is issued (transition from re-level speed to normal rate limited stop) during a
relevel operation. Please refer to Releveling Operation on page 4-33.
Position encoder resolution This parameter defines the number of pulses per foot of
travel reported by the landing system.
Select the landing system in use, then click the associated apply button. 9
If using MRDF (Machine Room Distance Feedback):
Enter pulses per revolution.
Enter governor sheave diameter in FEET (example: 30 inches = 2.5 [feet]).
Click the Calculate button.
Click the associated Apply button.
9-147
iView - Controller View
Typical Common Tab Settings The settings in the table below are typical for a 500
feet per minute installation.
Pattern shape preset Pattern shape preset can be used to enter preset values for the
profile parameters based on the high speed (contract speed) of the elevator and the selected
shape type.
9-149
iView - Controller View
To edit parameters
Typical Pattern Values Typical values for a 500 feet per minute installation are shown
in the following table. Alternate 1 and 2 values depend completely on the behavior desired when
the elevator is operating under control of those patterns (there really are no typical settings
for Alt 1 and Alt 2).
9-151
iView - Controller View
Note
System timer tables can be used to determine the currently active configuration for Hall Call
Eligibility, Parking, Parking Eligibility, Mode of Operation, Security and the state for User Out-
puts 1 through 4. Please refer to Configuration Tabs - Timer Tables on page 10-62.
Features
The timers associated with the type of operation selected in Features are displayed in the Tim-
ers list. For example, in the screen above, Auto Stop is selected and the timers that automati-
cally determine the state of Auto Stop are displayed. Timers may be displayed for:
Auto Stop
Sabbath Operation
Swing
Timer Details
Timers
Timers are displayed in the Timers list. If timers overlap (manage the same period of time), the
timer appearing higher in the list will have priority (control). To move a timer within the list,
click to select it, then click Move Up or Move Down.
2. From the Configurations list, select the configuration(s) and/or feature(s) that should
be active when this timer is valid (timer day and time are the present day and time).
3. Select the repeat frequency (Recurrence type) of the timer:
Daily: This timer is active every day during the specified time period.
9
Weekly (Day of the week): This timer is active each week on the specified day or days
(i.e., Mondays or Mondays and Tuesdays) or can be set to span days (i.e., Monday
through Wednesday).
Monthly (Day of week): This timer is active each month on the specified week days
(i.e., first Monday, third Sunday, etc.) or can be set to span days (i.e., second Sunday
through third Saturday, etc.).
9-153
iView - Controller View
Monthly (Day of month): This timer is active each month during the specified time
period, on the specified date or dates or may be set to span dates.
Yearly (Day of week): This timer is active each year during the specified time period,
during the specified month or months, on the specified day or days or may be set to
span days across multiple months.
Yearly (Day of month): This timer is active each year during the specified time period,
during the specified month or months, on the specified date or dates or may be set to
span dates across multiple months.
4. Enter the timer details using the Recurrence pattern controls. (These controls change
depending on the Recurrence type selected.)
Enter a descriptive name for the timer (up to 25 characters).
Select the start and end time, day(s) or date information required.
5. Click OK.
6. Click Send to send new or changed timer information to iControl.
To remove a timer
To edit a timer
To move a timer A timers position in the list determines its priority. If two timers are
attempting to control the same configuration at the same time, the timer higher in the list
(lower Priority number) will have control. To move a timer:
Note
No valid timer: For a particular configuration/feature, i.e., Auto Stop, Sabbath Operation, etc.,
if Timed is selected and there is no valid timer (current date and time falls within the timers
date(s) and times), those configurations/features will default to their #1 configuration or
default state.
1. Display the User Events tab (Controller > Configuration > Advanced > User Events tab).
2. Enter the desired Input / Event Name, up to 40 characters.
3. Send the Input / Event name to the controller. The name will then appear under User-
Defined Events on the list of inputs used to configure the I/O Boards.
4. Assign the event to a terminal on an ICE-MIAC Multiple Input AC Board using the Con-
troller > Configuration > I/O Board tab (see Configuration - I/O Boards on page 9-113
User Events can also be assigned to terminals on an ICE-COP Serial Car Operating
Panel Board. 9
9-155
iView - Controller View
In the simple example above, the Earthquake Buzzer, Attendant Buzzer, Fire Warning Buzzer
and Nudging Audible outputs are ORed into one Combined Buzzer Output, which is then
assigned to a terminal on an ICE-MOR board.
Indicators: The Calibrating, Waiting, and progress indicators track and report progress
through Brake Calibration phases.
Message window: Provides feedback and instructions during Brake Calibration.
Default button: Sets brake parameters to the default values.
Calibrate button: Starts the Brake Calibration procedure using voltage and timer values
entered.
Abort button: Aborts the Brake Calibration procedure.
Continue button: Restarts the Brake Calibration procedure if it has paused to allow com-
pletion of an instruction displayed in the message window.
The brake calibration procedure is described in Section 2 of this manual. Please refer to Brake
Calibration on page 2-57.
9-157
iView - Controller View
Counterweight Position: The distance, in feet, between the car and the lowest floor served
by the elevator when the counterweight learn operation was accomplished. The learn oper-
ation is performed with the car and counterweight at the same height in the hoistway
(adjacent to one another). Please refer to Counterweight Learn Procedure on page 3-28.
9-159
iView - Controller View
9-161
iView - Controller View
Configuration data Learned and actual (previously saved) data detected by the Floor
Heights Learn procedure.
Floors - the top floor configured on the Configuration > General > Floor data tab.
Front markers - the number of front landing magnets detected.
Landings - the number of floors where a front and/or rear landing magnet was detected
(includes false floors).
Rear markers - the number of rear landing magnets detected.
Openings - the number of floors with eligible openings (front and/or rear) per the Config-
uration > General > Floor data tab.
Edge data For diagnosing possible problems with floor magnets or magnet detection.
Error - the error is displayed in feet and indicates the difference between the height
learned by the Floor Heights Learn procedure and the height currently detected by the Top
level up, Top level down, Bottom level up and Bottom level down sensors for the front
and/or rear landing magnets. A typical error reading is 0.02083 (1/4 inch) to 0.01041 (1/8
inch) or less. If the error is greater than 0.04166 (1/2 inch), it is recommended to re-do the
placement of the magnets and then re-learn the floor heights.
Top level up - The ULM sensor has detected the top edge of a landing magnet. The ele-
vator is roughly aligned with the center of the landing magnets.
Top level down - The DLM sensor has detected the top edge of a landing magnet. The
elevator is roughly six inches above the center of the landing magnet.
Bottom level up - The ULM sensor has detected the bottom edge of a landing magnet.
The elevator is roughly six inches below the center of the landing magnet.
Bottom level down - The DLM sensor has detected the bottom edge of a landing mag-
net. The elevator is roughly aligned with the center of the landing magnet.
Count - the number of times each landing system leveling sensor has detected the top or
bottom of a front or rear landing magnet at the floor. These values will return to zero when
power is cycled or the controller is reset.
Learn metrics
Floor - during the Floor Heights Learn operation, indicates the most recently learned
floor.
Height - the learned height for the most recently learned floor.
Last floor height - the incremental distance to the previously learned floor (difference
between the heights learned for the previous and most recently learned floors).
Leveling Sensor Indicates the current state (activated or deactivated) of the front and
rear Up leveling marker, Door zone and Down leveling marker sensors.
Outer level
Velocity - the car speed at the time the last landing magnet edge was detected.
Error - the difference between the learned and most recent car position when the last land-
ing magnet edge was detected.
Learn The following controls and messages pertain to the Floor Heights Learn procedure.
Click the Refresh button ( ) to update the learned floor height information on the Controller
view > Configuration > Floor Heights > Configurations tab.
9-163
iView - Controller View
Offsets
Detected in: The detected variance between the cars current location (position in the
hoistway) and the learned position of the landing magnet.
Measured in: The measured distance in decimal inches between the hoistway landing sill
and the car sill. Enter a minus (-) value if the car sill was above the landing sill or a plus (+)
value if the car sill was below the landing sill.
Actual in: The calculated floor offset. Once the measured values are entered and sent to the
iController, this value will appear on the Configuration > Floor Heights > Floor Offset tab.
Acquired light: Lights to indicate that the Detected in value has been acquired and it is OK
to measure and record the distance between the landing sill and the car sill.
9-165
iView - Controller View
Configuration
9-167
iView - Controller View
allows the car to operate with this hatch open during earthquake operation (e.g., ASME
A17.1 allows this). Otherwise, the top emergency hatch should be wired in series with
other car-mounted safety device contacts, and this option should not be selected.
Construction mode: Select if the car is to operate in construction mode only. Please refer
to Overview of Construction Mode on page 2-2 for important information about fault
generation and required connections unique to construction mode operation.
Door position monitor: Select if the car has a door position monitor contact wired to the
iBox DPM input.
In car panel inspection: Select if the car has an in-car inspection switch wired to the iBox
INCP input.
Bypass switch option: Factory-enabled/disabled only. Enables/disables the Car and Hoist-
way Door Bypass switches on the iBox. This option is factory-set in accordance with appli-
cable jurisdictional requirements.
Emergency Brake Use these parameters if the car has an emergency brake to indicate
the type of brake and other brake related parameter settings.
Monitor cartop and car panel inspection inputs: Provides monitoring of cartop and car
panel inspection inputs required for TSSA certification.
Learn
Used to perform the safety comparison. The safety configuration of the job is stored in two loca-
tions in iControl. iControl constantly checks current safety information against stored data and
also compares the data in the two stored locations to make certain they continue to match. If
you make a change on the Safety screen, you will need to do a learn operation to write the new
data to iControl. The controller is set to match the installation safety configuration, according to
the job survey, before being shipped. By default, Construction Mode is enabled before the con-
troller is shipped. You should not have to make changes to the Safety tab until taking the car out
of Construction Mode. Please refer to Learning the Safety Configuration on page 2-46.
Status The status section provides fault indicators and a list of known safety boards
attached to the iBox.
Inventory checksum fault indicator: Indicates that the previously learned value of
the inventory checksum does not match the value currently being reported by the safety
processors. The inventory learn procedure must be performed before the car can run.
Inventory comparison fault indicator: The Safety boards attached to the iBox do not
match the safety board inventory in the safety system. The inventory learn procedure must
be performed before the car can run.
Set button: This function is primarily for factory use or for use as instructed by MCE.
Learn These controls are used to perform the safety inventory learn operation. The indica-
tors on the left show the status of the learn operation and the text window provides information
and instructions.
Learn button: Learning the inventory causes the safety processors to take an inventory 9
of the boards attached below the ICE-SAF board. When performing the inventory learn
procedure, the car must be placed on Inspection mode. Follow the instructions in the dis-
play window. When the indicators show Ready, click the Learn button.
Erase button: Causes the values currently stored in the Safety EEPROMS to be erased.
This should be used as a last resort when troubleshooting inventory faults. Afterwards, the
safety inventory, limit switches and safety configuration must be relearned.
9-169
iView - Controller View
Learn operation indicators: Show progress through the various phases of the Terminal
Learn operation.
Message window: Provides feedback and instructions as required during the Learn opera-
tion.
Learn button: Starts the Learn operation.
Abort button: Aborts the Learn operation.
Default button: Sets the switch Learned Values to values that allow the car to run without
activating limit switch faults as long as the car remains in Test operation. The car is not
allowed to run on passenger operation until real switch data is learned
9-171
iView - Controller View
Please refer to Safety Tests on page 4-48 for details about running tests from this screen.
Controller - Layouts
Some useful layouts have been pre-programmed and are supplied with iView. They include:
Configuration: This layout displays all of the configuration tabs for easy selection.
9-173
iView - Controller View
Call Registration
The Call Registration panel is available while working on any screen in iView.
1. Click the Front or Rear tab (or Hall tab if the car has only
front doors).
2. Click the Up Main, Down Main, Up Auxiliary, Down Aux-
iliary, CFSS1 or CFSS2 call button.
3. Click the desired floor button(s).
4. To close the dialog, click the X in the upper right corner.
10
10-1
iView - System View
Button Bar
Table 9.2 lists the locations where the functions of the buttons are explained.
Connection Status Connected arrows, shown above, indicate that iView is communi-
cating with the controller. Broken arrows indicate that the connection has been broken.
Write Privilege Status An unlocked lock, shown above, indicates that this connection
does not have write privilege. A locked lock indicates that write privilege has been granted.
Controller Type Indicates the type of controller to which iView is connected. For a
description of each type see An Overview of System Options on page 10-4 The controller types
include:
Simplex - a single car that is not part of a group.
Local - a car that is part of a group.
Local (Swing) - a local car that can swing away (detach from the group).
Swing - a local car that is currently detached from the group and is acting like a simplex.
Local (Alternate Dispatcher) - a local car that can assume dispatching responsibilities.
Local / Dispatcher - a local car that is also currently the dispatcher. iCue dispatching soft-
ware is running on the local cars iBox.
iCentral - a central dispatcher with iCue dispatching software running on a dedicated PC
or embedded microcontroller.
10
10-3
iView - System View
The following are brief descriptions of the various ways in which iControl can be configured.
Please refer to iControl System Options on page 10-5 for additional information.
Simplex An elevator operating alone, not connected to a group, is called a Simplex. The
parameters which control the Hall Call Eligibility, Parking, Parking Eligibility, etc. are pro-
grammed on the car controllers System View tabs. Simplex operation is enabled via the Sim-
plex car parameter on the Controller > Configuration > General > General tab (see
Configuration - General on page 9-108).
Local MCE uses the term Local to refer to an individual car that is part of a group of eleva-
tors. Dispatching and parking functions for a Local are performed by either a Local / Dispatcher
or a Central Dispatcher. The only System parameter used by a Local car is the Car label on the
System Configuration > Building tab.
Swing - Local (Swing) Local (Swing) is displayed on the iView status bar when a
Local car has been configured so that it can, on command, operate independent of the group
using an auxiliary hall call riser. Swing is displayed when the car is actually on swing operation.
The parameters which control the Hall Call Eligibility, Parking, Parking Eligibility and (if appli-
cable) CFSS and Security while the car is on Swing operation, are programmed on the Swing
cars System View tabs and stored on the Swing car controller. Automatic Swing operation, is
enabled via the Automatic Swing Operation Enable parameter on the Controller > Configura-
tion > Passenger tab (see Car Operation - Passenger Tab on page 9-40). Swing operation can
also be initiated using the Swing Operation Switch input which can be programmed using the
Controller > Configuration > I/O Boards tab (see Configuration - I/O Boards on page 9-113).
iCentral A central dispatcher (iCentral) can be used to perform the dispatching functions
for a group of iControllers. The iCue dispatching software runs on a dedicated PC or embedded
microcontroller. This solution is used for the most demanding iControl systems. When iView
connects to a central dispatcher, iCentral is displayed on the status bar and iView displays only
the System view windows and tabs. The Dispatching, Hall Call Eligibility, Parking, etc. parame-
ters are programmed on the central dispatchers System tabs and are automatically copied to all
cars designated as Alternate Dispatcher.
group management System Control: Can be configured as a Simplex, Local, Swing, or Local /Dispatcher.
functions for an elevator
group Connect to iController using a unique iView connection.
Connect to iCue PC Controller
using a unique iView System parameters
An iController can be configured as one of the following parameters
connection.
Dispatching System parameters used on this car are not used. Dispatcher using the capabilities). I/O Boards
Building configuration
Building Configuration parameters set on the iBox configuration
Hall call eligibility
Hall call eligibility, System parameters used iCentral or Local / All system parameters Load Weigher
Parking
Parking eligibility Building configuration Dispatcher. are set on the current Motor Field
Parking eligibility
Parking configurations (car labels) Local / Dispatcher and Pattern
Mode of Operation
CFSS When the car is on Swing passed to designated Terminal Switches
CFSS
operation the following Alternate Dispatchers. Timer Tables
Split Bank
Emergency Power parameters set and Custom Outputs
Security stored on the Swing car System parameters used User Inputs
Group Management System I/O are used: Building configuration
Emergency Power Hall call eligibility Diagnostics
Security System parameters used Parking Diagnostic Outputs
System I/O Building configuration Parking eligibility Event Log
Timer Tables Hall call eligibility, Mode of Operation Fault Bypass
User Inputs Parking eligibility CFSS Terminal Switches
User Outputs Parking configurations
CFSS Emergency Power
System Performance Setups
Security
System Event Log Security System I/O
Data Trap
System I/O Timer Tables
Legacy Group Interface Hoistway
User Inputs
Cross cancellation Outputs
User Outputs
Cross registration Safety Tests
Virtual Oscilloscope
System Performance
Layouts
Event Log
System View Windows and Tabs
10-5
An Overview of System Options
10
iView - System View
Through the tree on the left side of this tab, you can access:
Building: Set the highest floor served, number of cars, floor
and car labels, etc. (see page 10-7).
CFSS: Set recall-to-floor eligibility when operating in a Com-
mandeer for Special Service mode (see page 10-9).
Dispatching: General dispatching controls (see page 10-11).
Hall Call Eligibility: On a per-floor, per-configuration basis
(1 8), select the hall calls to which the car(s) may respond
(see page 10-13).
Mode of Operation: Setup the dispatching mode of opera-
tion parameters and configurations (see page 10-14).
Parking: Set parking options and floors for Parking configu-
rations (see page 10-20).
Parking Eligibility: On per-configuration basis (1 8), set
the parking eligibility parameters for the car (see page 10-27).
Split Bank: Split Bank operation is available only on the
Central Dispatcher (see page 10-29).
Management: Provides access to the following:
Remote Monitoring Authorization: Use to authorize a
third party remote monitoring tool to connect to iControl
(see page 10-31).
Local Dispatcher: Use to force the system to resend the
system parameters to all connected cars (see page 10-32).
Building
Building
The Building page is used to set the highest floor served, number of cars, floor and car labels,
job name and number, and to program Local / Dispatcher selection parameters.
Floors
Floors: Indicates the highest floor served by this car.
Floor label: If desired, provide a label, up to three characters, for any or all floors. High-
light the default floor label (number) and type a new label. Click Send when you have fin-
ished setting parameters on this page.
Cars
Cars: Indicates the number of cars in the group. If this is a Simplex the default is 1 and the
parameter is read only.
Car label: If desired provide a label for the car(s), up to three characters.
Job Information 10
Job name: Indicates the name of the job.
MCE job number: Indicates the job number assigned by MCE.
10-7
iView - System View
Dispatcher Displays a car identifier of the car that is currently the Local/Dispatcher or
iCentral to indicate the that the central dispatcher is doing the dispatching.
Alternate Dispatcher Use these controls to designate which car(s) can be the Local/
Dispatcher and to manually select or auto-select a different car to be the Local/Dispatcher.
Manual Select button: When iView is connected to the Local/Dispatcher, this button
can be used to manually select any car on the Alternate Dispatcher list to be the Local/Dis-
patcher. Choose the desired car from the Cars drop down list. When iView is connected to
any other car in the Alternate Dispatcher list (not the Local/Dispatcher), only the car to
which iView is connected can be manually selected to be the Local/Dispatcher.
Auto Select button: When iView is connected to the Local/Dispatcher, this button can
be used to request that another car on the Alternate Dispatcher list be auto-selected to be
the Local/Dispatcher.
Auto-select Preference Order: This control is used to designate which cars can
become the Local/Dispatcher and the order in which they are to be selected. Initially all
cars are shown in the Local Cars list.
1. Click to select cars in the Local Cars list and use the right arrow to move them into the
Alternate Dispatcher list.
2. Click to select cars in the Alternate Dispatcher list and use the Up and Down buttons to
place them in the desired order. The highest on the list is selected first. If the first on
the list is not available, the next on the list is selected, and so fourth. Once a car has
assumed the Local Dispatcher roll it continues in that roll even if a car that is higher on
the list becomes available.
3. To remove a car from the Alternate Dispatcher list, click to select the car and use the
left arrow to move it to the Local Cars list.
Caution
The Auto-select Preference Order settings must be identical for every car within a group of
elevators. Please refer to Before connecting the System ethernet cable to the iBox: on
page 2-31.
Group ID: The Group ID (1) cannot be changed. All other IDs are reserved for future use.
If you need advanced System addressing information please contact MCE.
10-9
iView - System View
Making Settings Per-Car Verify the Select a car to configure (1) drop-down box.
(There must also be a CFSS recall switch physically at the eligible Front or Rear door locations
on a floor selected to be eligible to initiate CFSS recall.)
Enable individual floor/recall location eligibility. You can make a selection in a few different
ways:
Click in the door/hall call column in the desired floor row to enable or disable.
Click and drag in a column to select multiple floors, then click the Select control to allow
calls or the Deselect control to restrict calls.
Click in the column head (i.e., Front) to highlight the entire column (all floors), then use
the system-wide Select calls or Deselect calls controls.
Auto-select Preference Order This list defines the order in which CFSS calls are
assigned. The dispatcher selects the first available car in the priority list to assign a new call. If
there are no cars from the Priority Cars list available for a new CFSS call, the best available car
from the Non-priority Cars list shall be assigned the call. Initially, all cars are shown in the Non-
priority Cars list.
1. To move cars to the Priority Cars list, click to select cars in the Non-priority Cars list
and use the right arrow to move them to the Priority Cars list, as desired.
2. Click to select cars in the Priority Cars list and use the Up and Down buttons to place
them in the desired order. The highest on the list is selected first. If the first on the list
is not available, the next on the list is selected, and so fourth.
3. To remove a car from the Priority Cars list, click to select the car and use the left arrow
to move it to the Non-priority Cars list.
Dispatching - Options
Dispatching - Options
Dispatching options allow you to set up conditions that favor the assignment of one car or
another.
When assigning hall calls to cars, iControl determines which car can respond in the least time
considering where each car is, its direction of travel, parking assignment and status (moving or
idle). By adding bonus or penalty seconds to the response time under certain conditions, you
can influence dispatching assignments.
Car at same floor bonus: If a car is at the same floor as a newly-registered hall call, credit
its response time (favor its assignment) by the set number of seconds.
Coincidence call bonus: If a car is on its way to a floor when a hall call is registered from
that same floor, credit its response time (favor its assignment) by the set time in seconds.
Retask penalty: When considering reassigning a call from one car to another to improve
response time, debit the response time of all cars except the one to which the call is cur-
rently assigned (penalize reassignment) by the set number of seconds.
Move lobby parked car penalty: When making a hall call assignment or reassignment,
debit the response time of any car parked at a lobby (penalize its assignment) by the set
number of seconds. (This allows you to skew the decision in favor of keeping the lobby
parked cars available at the lobby.)
Move non-lobby parked car penalty: When making a hall call assignment or reassignment,
debit the response time of any car parked at non-lobby floors (penalize its assignment) by
the set number of seconds. (This allows you to skew the decision in favor of keeping
parked cars available at their parking floor.)
Move idle car penalty: When making a hall call assignment or reassignment, debit the
response time of any idle car (penalize its assignment) by the set number of seconds.
10
Allow same floor hall calls to reverse doors on a departing car: If enabled, a hall call placed
at the floor/riser where a car is preparing to depart (closing its doors) will cause the doors
to reopen.
10-11
iView - System View
Dispatching - Configurations
These controls determine how four types of pre-programmed dispatching configurations are
selected to be the active configuration. Up to eight configurations of each type can be pro-
grammed.
Dispatching configuration: The currently active configuration can be selected manually
(Manual) or by a timer schedule (Timed).
Configurations:
Manual: When Dispatching configuration is set to manual, you can select which con-
figuration is active in the Manual column. When a setting is changed, it becomes active
after you Send it to the controller.
Timed: Select Timed to have the currently active configurations determined via timer
table. Please refer to Configuration Tabs - Timer Tables on page 10-62.
Active: The dispatching configurations that are currently active are shown in the
Active column. The four types of dispatching configurations are:
Hall Call Eligibility Parking
Parking Eligibility Mode of Operation
The configurations you are selecting here are configured on the screen tabs of the same name.
Hall Call Eligibility Configurations Parking Configurations Parking Eligibility Configurations Mode of Operation Configurations
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 5 7 3
Dispatching Configuration
The following controls are found on the Hall Call Eligibility tab.
Select the Hall Call Eligibility configuration (1 - 8) you want to create or edit.
Convert Front (Rear) Auxiliary Hall Call Riser to Front (Rear) Main Hall Call Riser: If,
when this configuration is active, you want one or both of the auxiliary hall risers to func-
tion as additional sets of main risers, enable the appropriate choice.
Select car to configure: For a Simplex this will default to 1.
Eligibility Table For each floor (listed in the left-most column), a check mark in any of
the remaining columns indicates that the associated hall call is eligible to be registered at that
floor. You can make a selection in a few different ways:
1. Click in individual cells to enable or disable, or
2. Click and drag in a column to select multiple floors, then click to Select allow calls or
Deselect to restrict calls, or 10
3. Click in the column head (i.e., Front Main Up) to highlight the entire column (all floors),
then use the Select or Deselect buttons.
4. When you are satisfied with your settings, click Send to send the data to the iBox.
5. Continue to create configurations (up to eight) as needed.
10-13
iView - System View
Mode of Operation
Use these controls to create or edit up to eight Mode of operation configurations. Each configu-
ration, when active, determines and defines the dispatching mode. The currently active configu-
ration can be selected manually (Dispatching > Configuration tab) or by timer table.
Select a Configuration
Select a mode of operation configuration to edit/create (1 8). Screen information will
automatically update when a configuration is selected.
Mode of Operation
Specifies the dispatching mode to be used when the selected configuration is active. The options
are:
Automatic: The dispatching mode (Balanced, Demand Up Peak, or Demand down peak) is
automatically selected depending on building demands.
Balanced: Selects balanced dispatching, favoring neither up nor down traffic.
Lobby Peak: Favors lobby traffic (not applicable to simplex operation).
Demand up peak: Typically used during morning arrival when demand is predominantly
in the up direction. The controller keeps track of bypassed call demands, which occur
when the car becomes heavily loaded, and manages call assignments to ensure that no
calls are ignored due to heavy loads.
Demand down peak: Typically used during afternoon departure when demand is predom-
inantly in the down direction. The controller keeps track of bypassed call demands, which
occur when the car becomes heavily loaded, and manages call assignments to ensure that
no calls are ignored due to heavy loads.
Mode of Operation
1. Select the mode of operation configuration number.
2. Select the mode of operation you want enabled when the configuration is active:
Automatic
Balanced
Lobby peak
Demand Up Peak
Demand Down Peak
Automatic
iControl will automatically determine which operating mode to use at any one time. The Auto-
matic sub controls allow you to fine tune the selection criteria. The hysteresis timer set here
affects every mode change made automatically for the selected configuration. The timer says
that, after changing modes, it cannot change again for X minutes. This prevents rapid changes
in traffic data from forcing operating modes to change constantly (which would disrupt service
efficiency).
Lobby Peak Detection Criteria Lets you fine tune the criteria that will cause iCon-
trol to detect a need to select Lobby Peak operation.
Allow lobby peak detection: If you want iControl to detect the need to switch to lobby peak
operation, enable this check box.
Lobby peak loaded car detection method:
Load weigher: iControl will automatically engage Lobby Peak mode as determined by
factoring the number of successive heavy load cars leaving the lobby with the interval
between when a car leaves the lobby and when the next lobby hall call is registered.
Uses the Number of loaded cars to initiate lobby peak setting.
Car calls: iControl will automatically engage Lobby Peak based on successive cars
departing the lobby with a car call quantity equal to or greater than that set here. Uses
the Number of car calls to consider car loaded setting.
10
10-15
iView - System View
Lobby Peak Options Allows you to fine tune system behavior when Lobby Peak is
automatically selected by the group control.
Always keep at least car(s) in balanced mode: If you want to hold one or more cars in bal-
anced service mode (non lobby peak) when lobby peak is active, set that number of cars
here.
1. Set lobby door dwell time. (The time the doors stand open before attempting to close.)
2. During busy conditions, you can choose to employ load weigher monitoring or car call
monitoring to decrease door dwell time and prepare the car to leave the lobby:
Use load weigher monitoring...: If you want the load weigher used to determine when
door dwell should be shortened. When the car weight reaches the heavy load setting
(car controller Load Weigher screen setting), the doors will begin closing in prepara-
tion to leave the lobby.
Use car call monitoring...: If you want to monitor the number of calls placed in the car
to determine when door dwell should be shortened. When the number of car calls
placed reaches the quantity set here, the doors will begin closing in preparation to
leave the lobby.
3. If desired, you can set a (dynamic) percentage of the in-use cars to use for lobby peak
service at this lobby floor. (For example, this is useful if the group is split between two
lobbies and you want 50% of the available cars servicing one and 50% of the available
cars servicing the other.)
4. Choose to use only specific cars for lobby peak service and even set the priority in which
you want them used. (Higher position in list = use first.)
Demand Peak Detection Criteria Sets the conditions under which iControl will
Mode of Operation
automatically enable demand peak operation.
Allow demand up peak detection: Enable to allow iControl to detect demand up peak con-
ditions.
Allow demand down peak detection: Enable to allow iControl to detect demand down peak
conditions.
Peak detection hall call percentage volume: When the percentage of hall calls in one direc-
tion (up or down), equals or exceeds this percentage of total hall calls, iControl will select
demand peak operation in that direction. A typical setting is 75 to 80%.
Number of floors with peak direction hall calls: When the number of floors with hall calls
in one direction (up or down) exceeds this number, iControl will select demand peak oper-
ation in that direction.
Demand Peak Options Fine tunes system behavior when demand peak is active.
Non-peak hall call assignment penalty: When demand peak operation is active, hall calls
in the non-peak direction (i.e., up calls during Demand Down operation), receive lower
priority service. If both peak and non-peak direction hall calls are active, the dispatcher
compares how long each has been registered when deciding which will be assigned the
next available car. The time entered here is subtracted from the non-peak direction call
registered time, causing the peak direction call to be favored.
Balanced
Balanced mode provides equal treatment for up and down calls, favoring neither up nor down
traffic.
10
10-17
iView - System View
Lobby Peak
When active by manual or timer selection, operates group cars in Lobby Peak mode.
5. If desired, you can set a (dynamic) percentage of the in-use cars to use for lobby peak
Mode of Operation
service at this lobby floor. (For example, this is useful if the group is split between two
lobbies and you want 50% of the available cars servicing one and 50% of the available
cars servicing the other.)
6. Select the direction of peak traffic from this lobby (Up or Down).
7. Select the call types available in the lobby.
8. Finally, you can choose to use only specific cars for lobby peak service and even set the
priority in which you want them used. (Higher position in list = use first.)
Demand Up Peak
Demand Up Peak is generally used during hours when traffic demand in the building is largely
in the up direction.
Main exit floor: If much of the traffic is exiting at a particular floor (i.e., the main employer
in an office building), setting that floor number here will allow the system to assign calls so
that floor receives the best possible service.
Non-peak hall call assignment penalty: Favors demand up peak calls by adding the num-
ber of seconds entered here to their time of registration, making them appear to have been
registered sooner and thus have more priority.
Peak hall call types: If appropriate, allows you to select those risers on which up hall calls
will be identified as demand up peak calls.
10
Main exit floor: If much of the traffic is exiting at a particular floor (i.e., the lobby), setting
that floor number here will allow the system to assign calls so that floor receives the best
possible service.
10-19
iView - System View
Non-peak hall call assignment penalty: Favors demand down peak calls by adding the
number of seconds entered here to their time of registration, making them appear to have
been registered sooner and thus have more priority.
Peak hall call types: If appropriate, allows you to select those risers on which down hall
calls will be identified as demand down peak calls.
Parking
Create up to eight different Parking configurations. Each configuration tells iControl how and
where to park the car when it is idle and how long to wait before parking an idle car at a lobby or
non-lobby floor. Parking configurations are selected manually (Dispatching tab) or by timer
table. The car will park only when idle and eligible to park, will re-park only if eligibility or park-
ing configuration changes, and will un-park only if there is a change of status (i.e., hall call
demand, car call demand, out-of-service, inspection, etc.).
For each Parking configuration, users may choose to allow iControl to determine the optimal
Parking
parking configuration at any given time or to manually define a parking floor (lobby or non-
lobby for each configuration):
User setting: On a per-configuration basis, the user defines priority (lobby or non-lobby)
and car door behavior at the selected parking floor.
Dynamic: iControl predicts building hall call demand and parks the car accordingly, deter-
mining optimal parking configuration on an ongoing basis
Combination: The user programs essential floors only, leaving other floor entries blank.
When acting as the Backup Dispatcher, once user-defined parking floors are served, iCon-
trol will park the remaining idle cars automatically.
Parking Configurations
1. Select a Parking configuration to edit/create (1 8). Screen information will automati-
cally update when a configuration is selected.
2. Select a Parking method:
Per floor parking: Parking is assigned on a per floor basis.
Sector parking: The building is divided into a number of user-defined sectors (contigu-
ous group of floors) and parking assignments are based on those sectors rather than
upon individual floors. The Parking floors pane will change to indicate floors or sectors
depending on the method selected. The user may also choose to enable Sector dis-
patching, causing the dispatcher to consider parking assignments and through-sector
travel when making call assignments.
10-21
iView - System View
Note
Dynamic Door Times Edit door behavior for cars parking at lobby and non-lobby
floors:
1. With dynamic parking enabled, select
either the Lobby or the Non Lobby row.
2. Click Edit.
Per Floor Parking - User Defined Priority, Floor, and Door Times To select
Parking
priority, parking floor, and door times manually when the Parking method is set to Per floor
parking:
1. Select an entry row in the list and click Edit, or click Add if you are adding a new entry to
an unfilled table. (You may assign as many parking/floor sets as you have cars in the
group. If you want multiple cars to park at the same floor, set up multiple, identical
entries for that floor.)
2. Assign a priority of 1 through 4 to the floor if you want it recognized as the lobby floor
for this configuration.
Note
Priorities 1 through 4 are treated as lobby parking floors (use lobby delay timers). Remaining
priorities are treated as non-lobby floors. Start and End floor selections are active only when
Sector parking has been chosen.
10-23
iView - System View
Sector Parking - User Defined Priority, Floor, and Door Times To define
sectors, select priority, parking floor within the sector, and door times manually when Parking
method is set to Sector parking:
1. Select an entry row in the list and click Edit, or click Add if you are adding a new entry to
an unfilled table. (You may assign as many parking/floor sets as you have cars in the
group. If you want multiple cars to park at the same floor, set up multiple, identical
entries for that floor.)
2. Select a Priority. The higher the priority, the more iControl will attempt to maintain a
parked car in the sector. One (1) is the highest priority.
Note
Priorities 1 through 4 are treated as lobby parking sectors (use lobby delay timers). Remaining
priorities are treated as non-lobby sectors.
Parking
Overlapping start and/or end floors are allowed.
Cars without car or hall call demands will be immediately parked. If the idle car is in a sec-
tor that already has a parked car, it will move to the nearest unoccupied sector.
Only one car may be parked in a sector at any one time.
If a car-call demand stops a car in an unoccupied sector, and it is assigned to park, it will
park at the floor of the demand (rather than moving to the preferred floor within the sec-
tor).
If the dispatcher assigns a car to park in an unoccupied sector, but then detects a car-call
registered to that sector for another car, the first car will not be moved (or will be stopped
if already moving).
If sector parking is selected for a parking configuration but the user does not define sec-
tors, or defines fewer sectors than might be accommodated by the number of cars in the
group or available landings, the dispatcher will make sector parking assignments dynami-
cally using artificial intelligence. Under these conditions:
The number of landings assigned to a sector will vary according to traffic demands. For
example, during up peak operation, the upper sector will be extended so that any down
demand may be more effectively met by the car assigned to park in the sector, while up
demand is met by other cars in the group.
The dispatcher will adjust behavior depending upon traffic data collected from previ-
ous experience during the same timer periods. For example, if hall call demand at a
particular floor has been historically heavy during certain times, a car or cars will be
moved to or near those floors in anticipation of the demand.
If previous experience during a particular time so indicates, the dispatcher will antici-
pate the destination of hall call demand from a particular floor or floors and will reas-
sign parking for idle cars at anticipated destination floors accordingly.
Sector Dispatching
When the parking method is set to Sector, and Sector dispatching is enabled, the dispatcher will
consider user-defined and/or dynamically assigned parking sectors when making dispatching
decisions (refer to sector parking conditions above).
Enable sector dispatching is only suitable for Group dispatching and is not applied on Simplex
operation. For a Simplex car, when Sector dispatching is enabled and used in conjunction with
Sector parking, this option will cause the simplex car to park in the nearest available sector
rather than in the highest priority sector.
10
10-25
iView - System View
4. If necessary, remove any unneeded user-defined entries from the table because all user-
defined parking floors must be satisfied before the dynamic parking will begin to park
cars.
Note
Parking configurations interact with and respond to choices made in Parking Eligibility config-
urations. Please refer to Parking Eligibility on page 10-27.
Parking Eligibility
Parking Eligibility
For a Simplex car, Swing car or Local/Dispatcher, create up to eight Parking Eligibility configu-
rations. Each configuration determines how the car is allowed to park: Not park at all/local
park/or park according to the Parking configurations.
Note
Parking configurations determine how the car is parked according to demand and priority.
Parking Eligibility configurations determine parking restrictions and behavior as they apply to
the car.
If a car is ineligible to park at a particular floor, it will not be moved to that floor to satisfy a
parking demand. However, if a car is at a normally ineligible floor in response to a car or hall
call, it may remain at that floor. If a car is parked at an eligible floor when the Parking Eligibility
configuration is changed manually or via automated timer such that the car is no longer eligible
to park at that floor, the cars parked status is removed but the car itself will not be moved
except by car call, hall call, or other parking demand (active under the new configuration).
10
10-27
iView - System View
Note
If a car is set to be eligible to be parked according to the Parking configurations, it must be made
eligible to park at some floor in the building (by selection in the table). It cannot be ineligible to
park at every floor and yet be included in Parking configurations. Please refer to Parking on
page 10-20.
When Split Bank operation is enabled and active, the elevator group is effectively split into two
separate groups, each called a bank. Hall call eligibility, per car and per hall call eligibility
configuration for each bank, is separately configurable. When split bank operation is enabled
and active, split bank cars use the Bank B hall call eligibility. (Please refer to Hall Call Eligibil-
ity on page 10-13.) During split bank operation, Bank B car risers may also be reassigned.
Emergency power and Security settings are not affected by Split Bank selection. When Split
Bank operation is deactivated, all group cars return to using the Bank A hall call eligibility
assignments.
Split Bank operation may be activated through iView manually by selecting manual
assignment and the appropriate hall call eligibility configuration on the Dispatching
screen Configuration tab. Split bank must be enabled.
Split Bank operation may be activated by timer selection of a hall call eligibility configura-
tion when split bank is enabled.
Split Bank operation may be activated manually by switch input. (Highest activation prior-
ity rests with this switch.) Split bank must be enabled.
Split Bank operation may be deactivated manually by switch input. (Highest deactivation
priority rests with this switch. When this switch is active, regardless of how Split Bank
activation was invoked, it will be shut off.)
Enable split bank operation: When this box is checked, Split Bank operation is enabled.
Though enabled, it may or may not be active. It can be made active as described above.
10
10-29
iView - System View
Select Hall Call Configuration (1 thru 8): Select a Hall call configuration here, then click on
the Hall Call Riser tab to modify hall call riser assignments when split bank operation is
active and this hall call configuration is in use.
Convert xxx riser to: In the selection boxes, pick the risers to be emulated as appro-
priate to your installation when the displayed hall call configuration is active.
Management
Management
Provides access to Remote Monitoring Authorization and Local Dispatcher.
Note
10-31
iView - System View
Local Dispatcher
Normally the system parameters are passed automatically to all cars designated as Alternate
Dispatcher. This tool is used to command the system to resend the parameters.
System parameters Click the Resend button to command the system to resend the
system parameters to all cars designated as Alternate Dispatcher. Any cars which are not in
operation will receive the updated system parameters when they are powered up and communi-
cation with the dispatcher is reestablished.
Management
The Local Dispatcher can manage emergency power from one or two emergency generators.
Use these controls to indicate which cars are connected to each generator and to define how
switching to and from emergency power is handled. The sequence of Emergency Power Opera-
tion is as follows:
1. Upon loss of commercial power, as indicated by the Emergency power input, no cars
are permitted to run until power from the emergency generator is established and the
After emergency power comes on, time to wait before running the cars time has
elapsed.
2. Emergency Power Recall - During recall, cars are powered and returned to their
recall floor (set on Controller > Configuration > Car Operation > Emergency power tab)
as defined by the Emergency Power Recall parameters. (Cars on Fire Service, Test or
Earthquake operation may be recalled to other floors per code requirements).
3. Emergency Power Run - When recall is completed, cars are allowed to run on emer-
gency power as defined by the Emergency Power Run parameters.
4. Power Transfer - Activation of the Power transfer input indicates that commercial
power is about to be restored. All cars are commanded to stop and/or not move until
transfer to commercial power is completed.
10
10-33
iView - System View
Assign Cars To Using the controls at the top of the screen, select cars and use the arrow
buttons to place them in the Generator 1 or Generator 2 column. The cars must be physically
wired to receive their emergency power from the selected generator.
Emergency Power Recall Based on the Number of cars that can be recalled at the
same time parameter, cars are selected to recall as follows:
1. Cars with a Priority Recall Request status, e.g. heavily loaded cars, are recalled in the
order they appear on the Recall sequence list.
2. All remaining cars are recalled in the order they appear on the Recall sequence list.
3. A second attempt is made to recall any cars unsuccessfully recalled.
These parameters define Emergency Power Recall behavior.
Activate recall by the Auto recall selection switch input: If this option is
selected, Emergency Power Recall will be activated if the Auto recall selection switch
input is active when the After emergency power comes on, time to wait before run-
ning the cars time elapses. Otherwise, Emergency Power Recall will be skipped.
Always recall: Emergency Power Recall will always be activated when the After
Emergency power comes on, time to wait before running the cars time elapses.
Never recall: The Recall phase is always skipped.
Note
Some Fire codes require a car that is on Fire Service to be recalled on Emergency Power regard-
less of the options selected.
Recall Sequence: Cars are recalled in the order in which they appear in this list. Select a
car and use the Up/Down buttons to order the list.
Number of cars that can be recalled at the same time: Set the number of cars that
may be recalled at the same time, considering generator capabilities and elevator car and
other building power demands.
Recall Timeout: If a car fails to respond to a recall signal within this time, the car will be
placed Out of Service.
At a minimum, recall to next floor: This option permits cars to be recalled to the
nearest floor to prevent entrapments if the Recall phase would instead be bypassed. The
Recall phase is bypassed if one of the cars is manually selected to run, Activate recall by
the Auto recall selection switch is selected but the Auto recall selection switch input is not
active, or Never recall is selected.
Emergency Power Run Based on the Number of cars that can be run at the same
Power Transfer This phase, initiated by the activation of the Power transfer input,
indicates that commercial power is about to be restored. Cars that are moving on emergency
power are commanded to stop at the next available floor to avoid an emergency stop. No cars
are permitted to move until transfer to commercial power is completed.
If the Power transfer input is deactivated, and commercial power has not been restored, the sys-
tem will return to the Emergency Power phase it was operating in prior to the Power transfer
input being activated.
10
10-35
iView - System View
Select legacy group interface: Use this control to select the legacy group interface
option being used, Cross-cancellation, Cross-registration or None.
Cross-registration
With Cross-registration, the iControl central dispatcher (iCentral) receives the hall calls and
manages the dispatching based on the following:
1. If an iControl car is available and can answer the call within the user adjustable ETA
threshold time, the hall call is assigned to an iControl car.
2. All other hall calls are passed to the legacy dispatcher provided that a legacy car that can
answer the call, per the eligibility map, is in service.
Select cars to be cross-registered: Indicates which cars are MCE iControl and which
are legacy cars. Select those legacy cars that are to be cross-registered and use the right
arrow to place them in the Legacy list.
ETA threshold: If an iControl car is available and can answer a call within the ETS
Cross-cancellation
threshold time, the call is assigned to the iControl car. Otherwise the call is passed to the
legacy dispatcher.
Note
When using cross-registration, care must be taken to ensure that the hall call eligibility (System
> Configuration > Hall Call Eligibility) for the legacy cars is correct so that the iControl central
dispatcher knows whether the car has proper access privileges.
Cross-cancellation
With cross-cancellation, the legacy dispatcher receives the hall calls and assignees them to leg-
acy cars. The legacy dispatcher also passes the calls, via a relay closure corresponding to the
riser and direction of the call, to the iControl central dispatcher (iCentral) which assigns the
calls to iControl cars. If the iControl car is first to answer the call, the central dispatcher signals
the legacy dispatcher to cancel the call, and vice versa.
Cross-cancellation output timer: (de-bounce for the call answered output) When
the legacy dispatcher sees the relay closure indicating that an iControl car has answered a
call, it takes some finite time to recognize and process the signal, at which point it cancels
the hall call demand. iControl then waits for the duration set in this timer before dropping
its call answered closure. This delay prevents the legacy system from misinterpreting the
relay state change as call not yet satisfied.
10
10-37
iView - System View
When you select System > Security, the General > Status tab is displayed. Access to security set-
tings beyond viewing the general status is restricted to authorized users. There are two user
classes, manager and technician. The manager is allowed to set up and edit passwords, the tech-
nician is not. To log on:
General - Status
General - Configuration
Master security:
Active: Lights if any security mode is active.
Hardware override: Lights if security has been overridden by a switch input.
Software override: Lights if security has been overridden by a software selection.
Activate Override button: Activates software security override. Button caption changes
to Deactivate Override when override is activated.
Active configuration:
Display: Indicates the currently active security configuration.
Hardware configuration: Lights if configuration was activated by a hardware switch.
Software configuration: Lights if configuration activated by software setting.
Timed configuration: Lights if configuration activated by system timer created using
the Configuration > Timer Tables tab.
Hall call security overrides:
Enable 1: Lights if hall call enable 1 input is activated by a card reader or keypad, etc.
(System View > Configuration > System I/O - System tab - Hall call enable 1 inputs).
Enable 2: Lights if hall call enable 2 input is activated by a card reader or keypad, etc.
(System View > Configuration > System I/O > System tab - Hall call enable 2 inputs).
Car call security override:
Enable 1: Lights if a Car call enable 1 input is activated by a card reader or keypad, etc.
(Controller > Configuration > I/O Boards > MIAC or COP - Car call enable 1 inputs).
Enable 2: Lights if a Car call enable 2 input is activated by a card reader or keypad, etc.
(Controller > Configuration > I/O Boards > MIAC or COP - Car call enable 2 inputs).
General - Configuration
This tab allows you to set the active security configuration manually or by timed assignment
and to Enable Hardware Override.
10-39
iView - System View
Enable Hardware Override: The Security override - Master security override input is
ignored unless this control is activated.
1. Logon using the managers password. If you are changing the passwords from their ini-
tial settings, logon using the default password manager.
2. Display the Manage Passwords tab (General > Manage Passwords).
3. Click the Set Pwd button. The Change password dialog is displayed.
Note
If you forget the password, locate the job number and/or serial number of the controller and
contact MCE Technical Support at 916-463-9200.
Note
In order to activate security, physical device (card reader, key switch, etc.) inputs must be prop-
erly configured and wired. Please refer to Configuration - I/O Boards on page 9-113.
General
General
The Security Level is set on the System > Configuration > Security > General screen.
10
10-41
iView - System View
Hall Calls
iControl security provides two types of hall call restrictions:
Per-Floor Security: Places restrictions on hall call riser access on a per-floor basis.
Per-Car Lock Out: Specifies which cars may stop at particular floors.
Per-Floor Security
Hall calls may be Unlocked, Locked or Secured:
Unlocked: Unrestricted access. Calls may be registered.
Locked: No access. Calls may not be registered.
Secured: Access is restricted to authorized passengers. Calls may be registered after proper
authorization (i.e., card reader, key switch, or code entry).
To set hall call security restrictions:
1. Select Per-Floor Security (System > Security > Hall Calls > Per-Floor Security).
2. Configuration: Select the security Configuration (1 - 8) to which the hall call security
restrictions apply.
3. For the hall call type (i.e., Main, Auxiliary, etc.) and location (Front/Rear), click in the
table at the floor and direction (up/down) to be set.
4. In the selection list that appears, select the desired security condition (Unlock/ Lock/
Hall Calls
Secure), and click OK.
5. If Secure is selected, chose the desired enable method(s)
that will allow calls to be registered, and click OK.
Enable 1: Hall call enable 1 input activation.
Enable 2: Hall call enable 2 input activation.
Enable 1 AND Enable 2: Activation of both Hall call
enable 1 and Hall call enable 2 inputs.
Enable 1 OR Enable 2: Activation of either Hall call
enable 1 or Hall call. enable 2 input.
Click in a floor label in the Floor column to select all call types for that floor.
Click a column heading, e.g. Main, Main Front or Main Front Up to select that type of
call for all floors.
Click and drag to select multiple floors and/or multiple columns (call types).
Once the floor(s) and call type(s) are selected, click
the Set Selection button. The Input Setup dialog is
displayed.
Select the desired security condition as described in
steps 4 and 5 and click OK.
6. When you have the hall call security settings as
desired, click Send to send the settings to iControl.
Security input latch time: Hall call enable inputs can be activated by a card reader or
key switch, etc. Card readers typically hold the enable input activated for a period of time
so that the user has time to enter the desired call. However, if a momentary switch or key
switch is used to activate the hall call enable input, this control allows you to set the length
of time that the user has to enter the call, after the hall call enable input has been deacti-
vated.
Hall call enable 1 (or 2) inputs active high: These controls allow you to program the
hall call enable inputs to activate on either a low or high going signal.
Allow parking at secured hall call: Cars are not allowed to park at a floor that is
secured for hall calls unless this control is checked.
Allow parking at a partially locked floor: Cars may park at a floor where some hall
calls are locked, e.g. down hall calls locked but up hall calls are allowed.
10
10-43
iView - System View
Per-Car Lockout
On a per-car, per-floor, per-direction basis, this control determines which cars may respond to
the various hall call types.
1. Select Per-Car Lock Out (System > Security > Hall Calls > Per-Car Lock Out).
Note: Any calls that have been locked by Per-Floor Security settings will be indicated
by light gray locks. Any calls that are also locked by Per-Car Lock Out settings will have
a second dark gray lock added indicating the per-car settings.
2. Call type: Select a call type, Main, AUX or CFSS.
3. Floor, Car, Front/Rear, Up/Down: The car numbers are at the top of the columns.
Click in the row and column that selects the floor, car, front/rear, up/down hall call
desired.
4. Click Lock or Unlock and OK in the dialog that appears.
2. Select the security Configuration (1 - 8) to which the car call security restrictions apply.
3. For the car call type (front/rear), click in the table at the floor and car panel location
(front/rear) to be set.
4. In the selection list that appears, select the desired security condition (Unlock/Lock or
Secure.
5. If Secure is selected, choose the desired enable method or methods that will allow car
calls to be registered.
Enable 1: Car call enable 1 input activation.
10
Enable 2: Car call enable 2 input activation.
COP Passcode: Passcode entered via the Car Operating Panel buttons.
A combination of the above (see Security Symbols on the next page).
10-45
iView - System View
Security Symbols This illustration explains the car call security symbols
Enable 1 input
Enable 2 input
COP Passcode
No line between symbols
means AND (all are
required)
Click in a floor label in the Floor column to select all call types for that floor.
Click a column heading, e.g. Front, Rear or both to select that type of call for all floors.
Click and drag to select multiple floors and/or multiple columns (call types).
Once the floor(s) and call type(s) are selected, click the Set Selection button. The Input
Setup dialog (similar to the list shown above) is displayed.
Select the desired security condition as described in steps 4 and 5 and click OK.
6. When you have the car call security settings as desired, click Send to send the settings to
iControl.
Other controls
Security input latch timer: Car call enable inputs can be activated by a card reader, key
switch, etc. Card readers typically hold the enable input activated for a period of time so
that the user has time to enter the desired call. However, if a momentary switch or key
switch is used to activate the hall call enable input, this control allows you to set the length
of time, after the hall call enable input has been deactivated, that the user has to enter the
call.
3. Selection: Select floors, and calls singly or in blocks as described previously (Please refer
to Car Calls - Configuration on page 10-45).
4. Choose the sources /operating mode(s) that will override (ignore) the car call security
restriction at the selected floor/riser.
All: Car calls from all of the following sources and modes.
OBD calls: Calls placed using the iBox On-board Display.
Remote calls: Calls placed using iView or iMonitor.
Automatic calls: Calls placed automatically by iControl, e.g.
Automatic door open: Under certain conditions, including certain fault conditions
and emergency power transfer periods, the elevator doors may need to automati- 10
cally open or cycle open/closed at floors. Activating this override, allows the doors
to open or cycle even at a secured opening.
Emergency dispatch: Calls generated as a result of emergency dispatching.
10-47
iView - System View
2. Select the floor(s) and call types as previously described (Please refer to Car Calls - Con-
10
Enter the Name.
Enter the Destinations Allowed by clicking the desired floors, front and/or rear. Or
click and drag to select multiple floors and then click Select or Deselect.
10-49
iView - System View
Enter the Pass Code by clicking the desired call buttons and front or rear
Modes Allowed: Authorizes the passenger to use the COP passcode while the car is oper-
ating on the selected mode(s) in addition to Passenger mode.
Security - COP Passcode operation For the elevator passenger, using the COP
passcode to register call a call to a secured floor works as follows:
1. Press a floor selection on the COP as usual. The panel buttons will flash to indicate that a
passcode must be entered.
2. Press floor buttons to enter the passcode.
3. Correct entry of the passcode will register the call. The panel buttons will return to nor-
mal.
An incorrect or timed-out entry will not register the call. The user may repeat the pro-
cess if the entry was incorrect or timed out.
Note
If both a passcode entry and an enable input (card reader or switch) are required to register a
particular call, the enable input must be completed before the COP passcode is entered.
System Tab
System I/O allows iControl to use a simple, two-wire serial bus for external communication. For
local cars (part of a group) the hall call assignments are made on the central dispatcher (iCen-
tral) or Local/Dispatcher. For a simplex or swing car the hall call assignments are made using
this tab on each car. Normally these assignments are made at the factory. You should only need
to verify that the inputs and outputs are assigned correctly according to the job prints.
System Tab
This tab allows you to set the polling range for I/O addresses and to assign individual inputs
and outputs to the desired functions.
Address Range Each serial bus will accommodate addresses from 10 to 488 or from 10
to 988. If your bus is not populated beyond 488 inputs and outputs, the smaller range should be
10
used to speed up control response efficiency. The address range is preset at the factory accord-
ing to the job survey. You should not need to change these settings if they are connected as
shown in your job prints.
10-51
iView - System View
Configure Button
This selection allows the system to automatically configure inputs and outputs of a type you
select.
For example:
1. Click in the Starting Node Address column to select the address at which you want auto-
matic assignment to begin.
2. Click in the Input/Output column to select an input or output group you would like to
assign.
3. Set whether you want addresses assigned sequentially from the starting address you
selected or whether you want the addresses assigned to every tenth location.
4. Set whether or not existing programming, if any, for the address range affected should
be overwritten.
5. Click OK to automatically assign the selected input type to the addresses.
As noted in the Auto Configure dialog, we recommend you begin by clicking the Default calls
button. You can then assign calls to addresses, and then run Auto Configure beginning with an
unused input beyond the call assignments.
System Tab
This table allows you to define each input or output on the bus. These settings are pre-
defined at the factory according to the job survey and should not need to be
changed if connected as shown on your job prints.
Node address: The addresses available on this bus.
Input/Output: The type of input or output assigned to this address.
10-53
iView - System View
CFSS - Mode 1 system output: This output becomes active when at least one car has
been assigned to CFSS Mode 1 operation. Typically used to drive an indicator. Associa-
tion column is blank.
CFSS - Mode 2 system output: This output becomes active when at least one car has
been assigned to CFSS Mode 2 operation. Typically used to drive an indicator. Associa-
tion column is blank.
Emergency Power inputs
EP - Emergency power input: iCue will accommodate one or two emergency power
generators. An Emergency power input is used to inform iCue when emergency power
is active (the Association column selected generator is active). Each elevator controller
also has an Emergency power input connected to the generator from which it receives
emergency power. Emergency power inputs may be active high or active low as config-
ured when setting up emergency power parameters for iCue and individual elevator
controllers. On the group Emergency Power screen, elevators are designated as pow-
ered by generator 1 or 2 so that iCue knows which Emergency power input to associate
with the car. Select generator in Association column.
EP - Auto recall selection switch input: Emergency Power operation proceeds in two
phases: Recall - cars are sequentially recalled to their recall floor. Run - cars are
allowed to run, typically one car per building vertical transportation sector (group) at a
time to ensure adequate power is available. When activated, the Auto recall selection
switch input causes iCue to sequentially recall cars to their return floor. If a car is
already actively selected to run on emergency power (see EP - Emergency power auto-
matic run input below), the recall phase is bypassed. Select generator ID in Association
column.
EP - Emergency power automatic run input: When active, this input causes iCue to
automatically select cars to run after considering the status of the EP - Emergency
power run input (see below). Select generator ID in Association column.
EP -Power transfer input: When active, notifies iCue that commercial power has been
restored and transfer from emergency to commercial power is pending. A maximum of
two Power transfer inputs, one for each emergency generator accommodated, can be
configured. Which generator is associated with the input is determined by the (Gener-
ator 1 or Generator 2) selection in the Associations column of this table. Activation of
this input causes iCue to command all cars not already in Freeze Status to stop at the
next available landing and enter Freeze Status. This input must be activated in advance
of the transfer from generator to commercial power to allow all cars to safely make a
normal stop. When commercial power is restored, iCue will return cars to normal
operation. Select generator ID in Association column.
EP -Emergency power run input: When active, designates the specified car to have
power during the run phase. Select Car ID in the Association column. This per car
input overrides the recall phase.
Emergency Power Outputs
EP - Emergency power service output: Activates when the system is not on emergency
power. Select generator ID in Association column.
EP - Emergency power phase I output: Active during Freeze or Recall phase of emer-
gency power operation. Select generator ID in Association column.
EP - Emergency power phase II output: Active during Run phase of emergency power
operation. Select generator ID in Association column.
EP - Car selected for emergency power output: Active when the car is given power dur-
System Tab
ing emergency power operation. Essentially this is the combination of outputs EP - Car
selected to run and EP - Car selected to recall. If the car is given power to operate at
any time during emergency power operation, the output will be activated. Select the
Car ID in the Association column.
EP - Car selected to recall output: Active when the car is given power to Recall during
Emergency Power operation. Select the Car ID in the Association column.
EP - Car selected to run output: Becomes active when the specified car is selected to
operate. The output is always cleared during Freeze and Recall phases and during
Power transfer activation upon stopping at a floor. Select Car ID in Association col-
umn.
Cross Registration: Cross registration is intended for use during modernization projects. It
provides an interface between cars in a newly installed iControl group and cars in an existing
(legacy) group. The iCue dispatcher will preferentially assign hall calls to iControl cars unless
the estimated time of arrival for an iControl car exceeds a limit programmed by the user (Cross
Registration screen). In this case, iCue will assign the call to the legacy group dispatcher. Hall
Call Eligibility for legacy cars must be programmed into iCue, just as they are in the legacy
group, to ensure that only cars that are eligible are dispatched to answer calls.
Cross registration inputs: The following inputs are used for cross-registration of hall calls.
Cross reg - Down aux front input: Select floor in Association column.
Cross reg - Down aux rear input: Select floor in Association column.
Cross reg - Up aux front input: Select floor in Association column.
Cross reg - Up aux rear input: Select floor in Association column.
Cross reg - Down main front input: Select floor in Association column.
Cross reg - Down main rear input: Select floor in Association column.
Cross reg - Up main front input: Select floor in Association column.
Cross reg - Up main rear input: Select floor in Association column.
Cross reg - Car in-service input. Select Car ID in Association column.
Cross registration outputs: Used for cross-registration of hall calls.
Cross reg - Down aux front output: Select floor in Association column.
Cross reg - Down aux rear output: Select floor in Association column.
Cross reg - Up aux front output: Select floor in Association column.
Cross reg - Up aux rear output: Select floor in Association column.
Cross reg - Down main front output: Select floor in Association column.
Cross reg - Down main rear output: Select floor in Association column.
Cross reg - Up main front output: Select floor in Association column.
Cross reg - Up main rear output: Select floor in Association column.
Note
For all the above, the floor selected in the Association column defines the call location for the
iCue software. 10
Cross reg - Emergency dispatch output: (Notifies legacy group that we are unable to
cross-register hall calls because of a serial IO failure or iCue shutdown and that it
should put its cars on emergency dispatch operation.) Association column is blank.
10-55
iView - System View
General outputs
General - Attendant service output: Active when the specified car is on Attendant Ser-
vice operation. Select Car ID in Association column.
General - Fire service phase I output: Active during Fire Recall Phase I. Association
column is blank.
Manual configuration inputs
Manual config - Hall call configuration input: Selects the Hall call eligibility configura-
tion (1 - 8) designated in the Association column to be the currently active configura-
tion.
Manual config - Parking configuration input: Selects the Parking configuration (1 - 8)
designated in the Association column to be the currently active configuration.
Manual config - Parking eligibility configuration input: Selects the Parking eligibility
configuration (1 - 8) designated in the Association column to be the currently active
configuration.
Manual config - Mode of operation configuration input: Selects the Mode of operation
configuration (1 - 8) designated in the Association column to be the currently active
configuration.
Manual config - Security configuration input: Selects the Security configuration (1 - 8)
designated in the Association column to be the currently active configuration.
Active configuration outputs
Active config - Hall call eligibility output: Indicates that the Hall call eligibility configu-
ration (1 - 8) designated in the Association column is the currently active configura-
tion.
Active config - Parking output: Indicates that the Parking configuration (1 - 8) desig-
nated in the Association column is the currently active configuration.
Active config - Parking eligibility output: Indicates that the Parking eligibility configu-
ration (1 - 8) designated in the Association column is the currently active configura-
tion.
Active config - Mode of operation output: Indicates that the Mode of operation config-
uration (1 - 8) designated in the Association column is the currently active configura-
tion.
Active config - Security output: Indicates that the Security configuration (1 - 8) desig-
nated in the Association column is the currently active configuration.
Security: The following inputs control how hall calls to secured floors are handled by the sys-
tem. They are typically activated from switches or buttons at the building security station so
that security personnel can easily and quickly make adjustments to hall call security as a situa-
tion demands. They can also be activated by a card reader or keypad, etc.
Hall call enable 1 (or 2) inputs
Hall call enable 1 (2) - Floor input: When active, a valid call for the secured floor can be
registered. Select floor number in Association column.
Hall call enable 1 (2) - Front input: When active, a valid call for the front opening on
the associated secured floor can be registered. Select floor number in Association col-
umn.
Hall call enable 1 (2) - Rear input: When active, a valid call for the rear opening on the
System Tab
associated floor can be registered. Select floor number in Association column.
Hall call enable 1 (2) - Main front input: When active, valid secured calls at the associ-
ated floor, main front riser, can be registered. Select floor number in Association col-
umn.
Hall call enable 1 (2) - Main rear input: When active, a valid call at the associated
secured floor, main rear riser, can be registered. Select floor number in Association
column.
Hall call enable 1 (2) - Aux front input: When active, a valid call at the associated
secured floor, auxiliary front riser, can be registered. Select floor number in Associa-
tion column.
Hall call enable 1 (2) - Aux rear input: When active, a valid call at the associated
secured floor, auxiliary rear riser, can be registered. Select floor number in Association
column.
Hall call enable 1 (2) - Down aux front input: When active, a valid call at the associated
secured floor, down auxiliary front riser, can be registered. Select floor number in
Association column.
Hall call enable 1 (2) - Down aux rear input: When active, a valid call at the associated
secured floor, down auxiliary rear riser, can be registered. Select floor number in Asso-
ciation column.
Hall call enable 1 (2) - Up aux front input: When active, a valid call at the associated
secured floor, up auxiliary front riser, can be registered. Select floor number in Associ-
ation column.
Hall call enable 1 (2) - Up aux rear input: When active, a valid call at the associated
secured floor, up auxiliary front riser, can be registered. Select floor number in Associ-
ation column.
Hall call enable 1 (2) - Down main front input: When active, a valid call at the associ-
ated secured floor, down main front riser, can be registered. Select floor number in
Association column.
Hall call enable 1 (2) - Down main rear input: When active, a valid call at the associated
secured floor, down main rear riser, can be registered. Select floor number in Associa-
tion column.
Hall call enable 1 (2) - Up main front input: When active, a valid call at the associated
secured floor, up main front riser, can be registered. Select floor number in Association
column.
Hall call enable 1 (2) - Up main rear input: When active, a valid call at the associated
secured floor, up main rear riser, can be registered. Select floor number in Association
column.
NOTE: The inputs above are ORed together with the greater permission exerting control.
10-57
iView - System View
CFSS call enable 1 (2) - CFSS mode 1 front input: When active, a valid CFSS mode 1 call
at the associated secured floor, front opening only, can be registered. Select the floor
number in the Association column. (CFSS mode 1 and 2 are user-assignable operating
modes typically used for medical emergency calls, attendant calls, etc.)
CFSS call enable 1 (2) - CFSS mode 1 rear input: When active, a valid CFSS mode 1 call
at the associated secured floor, rear opening only, can be registered. Select the floor
number in the Association column. (CFSS mode 1 and 2 are user-assignable operating
modes typically used for medical emergency calls, attendant calls, etc.)
CFSS call enable 1 (2) - CFSS mode 2 input: When active, a valid CFSS mode 2 call at
the associated secured floor, can be registered. Select the floor number in the Associa-
tion column. (CFSS mode 1 and 2 are user-assignable operating modes typically used
for medical emergency calls, attendant calls, etc.)
CFSS call enable 1 (2) - CFSS mode 2 front input: When active, a valid CFSS mode 2
call at the associated secured floor, front opening only, can be registered. Select the
floor number in the Association column. (CFSS mode 1 and 2 are user-assignable oper-
ating modes typically used for medical emergency calls, attendant calls, etc.)
CFSS call enable 1 (2) - CFSS mode 2 rear input: When active, a valid CFSS mode 2 call
at the associated secured floor, rear opening only, can be registered. Select the floor
number in the Association column. (CFSS mode 1 and 2 are user-assignable operating
modes typically used for medical emergency calls, attendant calls, etc.)
Security Override
Security override - Master security override input: When active, all secured calls are
enabled. All secured car and hall calls will behave as though unsecured. Locked calls
will remain locked.
Security override - Hall call enable 1 override input: When active, all Enable 1 secured
hall calls are unsecured. Locked calls will remain locked.
Security override - Hall call enable 2 override input: When active, all Enable 2 secured
hall calls are unsecured. Locked calls will remain locked.
Split bank hall calls: When enabled and active, split bank operation allows a single control
group of cars to be controlled as though it were two separate groups. These inputs provide
connection points for the auxiliary and main riser hall call buttons for the cars split from
the group (Bank B).
Bank B hall call - Down aux front
Bank B hall call - Down aux rear
Bank B hall call - Up aux front
Bank B hall call - Up aux rear
Bank B hall call - Down main front
Bank B hall call - Down main rear
Bank B hall call - Up main front
Bank B hall call - Up main rear
R emote User Outputs: Up to 32 outputs may be defined by the user on the Remote Out-
System Tab
puts tab. The first four of these outputs may be included in timer tables and triggered by
the timer. Outputs may also be manually triggered from the Remote Outputs > Trigger
tab. Once defined, the outputs are associated with a physical output address using the Sys-
tem I/O or I/O Boards tab. Outputs may be latching or toggle, active high or low, and are
intended to be used to drive system inputs as required by individual sites.
Remote 01 (- 32)
User Defined Events: Up to 10 inputs may be used to trigger a specific event message to be
posted to the system event log. The user defines the text of the event on the User Events
tab, then assigns a physical address (location) to the input using the System I/O tab.
User Event 1 (- 10)
Active Mode of Operation Outputs:
Balanced: Active when the system is operating in balanced mode, typically to drive a
visual indicator.
Lobby Peak: Active when the system is operating in lobby peak mode, typically to drive
a visual indicator.
Demand Up Peak: Active when the system is operating in demand up peak mode, typi-
cally to drive a visual indicator.
Demand Down Peak: Active when the system is operating in demand down peak
mode, typically to drive a visual indicator.
Association Column:
Choices selectable in this column are dependent on the adjoining Input/Output selection
as follows:
For hall calls, the floor Association selection is presented.
For emergency power related functions, generator assignment is presented (Gen1 or
Gen2).
For recall/car related functions, the car Association selection is presented.
Note
Remember, the above settings are all pre-configured before the controller is shipped from MCE.
You should need only to connect inputs and outputs according to your job prints. These settings
should not be changed or edited unless hardware affecting these settings is being replaced. In
these instances, follow specific instructions provided by MCE.
10
10-59
iView - System View
Wrapback Option When enabled, hall call lamps are lighted immediately when the
associated hall call button is pressed (rather than waiting for a response from the group control-
ler to light the lamp).
Inventory / Test response These controls allow you to create an inventory of input
Note: You must have write privilege to take an Input or Output inventory or perform an
Input or Output test. To acquire write privilege:
1.Select Acquire from the iView Write privilege menu.
2.Press the iBox Yes soft key in response to the request for write privilege.
Input inventory: To run an input inventory, click the Input inventory button when
you are certain all devices are properly connected on the system bus. A check mark
will appear in the Input inventory column for every address location at which the
controller sees a functioning device. Compare this against your physical inventory
to make certain that all devices responded properly.
Output inventory: To run an output inventory, click the Output inventory button. A
check mark will appear in the Output inventory column for every address location
at which the controller sees a functioning device. Note that at this time, outputs
using an SC-ION board will not be recognized by this software inventory or test and
must be observed physically on the board.
When you run an input or output test, the controller compares the responses against the known
quantity of the inventory.
Input test: The Input test sequentially sends a test message to and reads a response from
all input devices on the bus. Click the Input test button to initiate the test.
Output test: The Output test sequentially checks the continuity of the circuit powering
each node lamp, buzzer, or other indicator. Click the Output test button to initiate the test.
Test results: The results of the Input or Output test are displayed in the right hand column
of the table. The column label changes depending on the test, e.g. Input test results or Out-
put test results. The possible results include:
Found : A green LED indicates that the test results match the inventory at this
node address.
Missing : A red LED indicates that the test did not find a working device that
was previously found at this node address by the inventory. This could indicate a
device failure.
New : A yellow LED indicates that a device was found at this node address dur-
ing the test that is not indicated in the inventory. This could indicate a newly installed 10
device or a device programming error.
10-61
iView - System View
Features
The timers associated with the type of configuration or operation selected in Features are dis-
played in the Timers list. For example, in the screen above, Hall Call Eligibility is selected and
the timers that automatically determine the currently active Hall Call Eligibility Configuration
are displayed. (The configurations that the timer tables select are created through the System
Configuration and Security tabs). Timers may be displayed for:
Hall Call Eligibility
Parking
Parking Eligibility
Mode of Operation
Security
Remote 01 - 04
Timer Details
Timer Details
When a timer is selected in the table, details of its settings appear in Timer Details. (You must
select a timer and click Edit to change settings, this display is read only.)
Timers
Timers are displayed in the Timers list. If timers overlap (manage the same period of time), the
timer appearing higher in the list will have priority (control). To move a timer within the list,
click to select it, then click Move Up or Move Down.
2. From the Configurations list, select the configuration(s) and/or feature(s) that should
be active when this timer is valid (timer day and time are the present day and time). 10
3. Select the repeat frequency (Recurrence type) of the timer:
Daily: This timer is active every day during the specified time period.
10-63
iView - System View
Weekly (Day of the week): This timer is active each week on the specified day or days
(i.e., Mondays or Mondays and Tuesdays) or can be set to span days (i.e., Monday
through Wednesday).
Monthly (Day of week): This timer is active each month on the specified week days
(i.e., first Monday, third Sunday, etc.) or can be set to span days (i.e., second Sunday
through third Saturday, etc.).
Monthly (Day of month): This timer is active each month during the specified time
period, on the specified date or dates or may be set to span dates.
Yearly (Day of week): This timer is active each year during the specified time period,
during the specified month or months, on the specified day or days or may be set to
span days across multiple months.
Yearly (Day of month): This timer is active each year during the specified time period,
during the specified month or months, on the specified date or dates or may be set to
span dates across multiple months.
4. Enter the timer details using the Recurrence pattern controls. (These controls change
depending on the Recurrence type selected.)
Enter a descriptive name for the timer (up to 25 characters).
Select the start and end time, day(s) or date information required.
5. Click OK.
6. Click Send to send new or changed timer information to iControl.
To remove a timer
1. Select a configuration/feature type from the Features drop down list.
2. Select a timer from the Timers list.
3. Click Remove.
To edit a timer
1. Select a configuration/feature type from the Features drop down list.
2. Select a timer from the Timers list.
3. Click Edit.
4. Make changes using the Add/Edit Timers dialog.
5. Click OK.
To move a timer A timers position in the list determines its priority. If two timers are
attempting to control the same configuration at the same time, the timer higher in the list
(lower Priority number) will have control. To move a timer:
1. Select the timer from the Timers list.
2. Click Move Up or Move Down.
Note
No valid timer: For a particular configuration/feature, i.e., Parking, Mode of Operation, Auto
Stop, etc., if Timed is selected and there is no valid timer (current date and time falls within the
timers date(s) and times), those configurations/features will default to their #1 configuration
or default state.
Timers
The User Events tab is used to assign a name to an Input / User Event. Up to 10 Input / Event
Names can be programmed. This event name can then be assigned to a hardware input. An
event is logged, on the System Event Log, when the input is activated and again when it is deac-
tivated. System - Input / Event Names are assigned to terminals on an SC-ION Serial Input/
Output Board using the System > Configuration > System I/O tab. For information about Con-
troller User Events see Configuration - Advanced - User Events on page 9-155.
1. Display the User Events tab (System > Configuration > User Events tab).
2. Enter the desired Input / Event Name, up to 40 characters.
3. Send the Input / Event name to the controller. The name will then appear under User-
Defined Events on the list of inputs used to configure the I/O Boards.
4. Assign the event to a terminal on an SC-ION Serial Input/Output Board using the Sys-
tem > Configuration > System I/O tab. Please refer to Configuration Tabs - System I/
O on page 10-51.
10
10-65
iView - System View
Timers
Remote outputs are available on the Central
dispatcher and/or Local/Dispatchers Sys-
tem IO. You can assigned them to terminals
on an SC-ION Serial Input/Output Board
using the System > Configuration > System
I/O tab. Please refer to Configuration Tabs
- System I/O on page 10-51. They can also
be assigned to terminals on an ICE-MOR
Multiple Output Relay Board using the Con-
troller > Configuration > I/O Board tab. The
user assigned output names appear on the
list of outputs available for terminal assign-
ment. Please refer to Configuration - I/O
Boards on page 9-113.
10
10-67
iView - System View
Event Properties To view greater detail about an event, double-click the event.
Save event log / Open event log The System Event Log can be saved to a file for
future reference. To save a System Event Log to a file:
Click the Save button on the System > Diagnostics > Event Log tab.
Navigate to the folder you want to save the file in.
Name the file and click Save.
The Event Log file can be viewed using iView. To view a previously saved System Event Log file:
Click the Open file button on the System > Diagnostics > Event Log tab.
Navigate to the file you want to view and double-click it.
Print / Print Preview To print the event log or to view a print preview and/or print the
Timers
event log from the print preview dialog:
Click the Print button , choose a printer from the Print dialog and click Print.
Click the Print Preview button and use the controls to display and/or print the desired
pages.
Clear All Click the Clear All button to delete all of the events in the Event Log.
10
10-69
iView - System View
System - Hoistway
The hoistway display provides a real time view of all the cars in the group. A typical hoistway
view, with an active call registration panel, is shown below.
Timers
way screen provides traffic mode and
Estimated Time of Arrival informa-
tion for the group.
Traffic Mode: (Balanced in this
example) Displays the current oper-
ating mode. This mode may be
selected manually, by timer, or auto-
matically according to iCue analysis
of real-time traffic conditions.
Balanced: All elevator traffic
within the building is receiving
equal priority from the group.
Lobby Peak: Designated lobby
floors are receiving priority
attention. Generally active dur-
ing morning arrival times when
traffic is heaviest departing the
lobby for other floors.
Demand Up Peak: Upward
bound traffic is given priority. If
assigned dynamically, made
active when approximately 80%
of building traffic is in the up
direction.
Demand Down Peak: Down-
ward bound traffic is given pri-
ority. If assigned dynamically,
made active when approxi-
mately 80% of building traffic is
in the down direction.
Automatic: The traffic mode is
being controlled dynamically by
iCue according to real time traf-
fic analysis and learned build-
ing traffic patterns.
ETA: Estimated Time of Arrival. The time, in whole seconds, in which iCue estimates a regis-
tered hall call will be serviced. ETA counts in the blue zone indicate a rear hall call. ETA counts
in the orange zone indicate a front hall call.
Up / Down Columns: When a hall call is placed, its ETA will be displayed in the Up or
Down (as appropriate) hall column next to the floor from which the car was placed. The
ETA will count down to the arrival of the responding car.
Non-directional: An ETA in the left-most column indicates a non-directional hall call 10
has been placed at this floor. Non-directional calls are calls that do not indicate a
requested direction of travel. For example, CFSS calls, EMS calls, etc.
ETA Filtering: Click the ETA button to set up filtering criteria for displayed calls. (Dialog
shown with supervisor column illustration.)
10-71
iView - System View
Non-directional call
Up car call
Call Registration
Call Registration
Clicking the call registration button opens a dialog that allows you to register car and hall
calls.
Car Calls
After opening the dialog:
1. Click the Car tab.
2. Select the Car from the drop-down list (if applicable).
3. Select Front or Rear car panel if appropriate.
4. Click a floor number button to register a call.
Note
Hall Calls
After opening the dialog:
1. Click the Hall tab.
2. Select the hall call type.
Main (Up): Front up hall call.
Main (Down): Front down
hall call.
CFSS1: Configure for Special
Services. iControls have two customer assignable configura-
tions. Typically they are used for hospital calls, VIP calls, etc.
Auxiliary (Up): Rear up hall call.
Auxiliary (Down): Rear down hall call.
CFSS2: Configure for Special Services. iControls have two cus-
tomer assignable configurations. Typically they are used for
hospital calls, VIP calls, etc.
3. Click a floor number button to register a call.
Multiple calls may be placed if desired. Only hall call types actually
available and configured in the group will be available.
10
10-73
iView - System View
System Performance
This frame captures and graphs elevator performance over the most recent 24-hour period,
including:
Graphical representation of hourly average wait times for up and down hall calls
Number of up and down hall calls answered each hour
Average wait time for up and down hall calls for each hour
Average wait time for up, down, and all hall calls during the last 24 hours
System - Layouts
Call Registration
With iView, you can move and size tabs to suit the task to be performed. When you find a partic-
ularly arrangement to be useful, you can save it as a custom layout (View > Layouts > Save as).
You can then display that layout at any time by selecting your custom lay0ut from the View >
Layouts > Custom menu.
Some useful layouts have been pre-programmed and are supplied with iView. They include:
Configuration: This layout displays all of the configuration tabs for easy selection.
10
10-75
iView - System View
Reference
11
11-1
Reference
iControl DC Specifications
Table 11.1 iControl DC Specifications
Parameter Specification
Car Speed Up to 1800 fpm (9.14 m/s)
Jerk 15 ft/sec3 (7.62 m/sec3) maximum
8 ft/sec3 (2.44 m/sec3) nominal
1 ft/sec3 (0.305 m/sec3) minimum
Acceleration 10 ft/sec2 (3.04 m/sec2) maximum
4 ft/sec2 (1.52 m/sec2) nominal
1 ft/sec2 (0.31 m/sec2) minimum
Number of Stops Up to 150 (60 floors for Simplex)
Number of Cars in Group Up to 20
Floor Leveling Accuracy +/- 0.25 inches (6.35mm) guaranteed
+/- 0.125 inches (3.18mm) typical
Minimum Floor to Floor Time 4.8 seconds for 12-foot (3.66m) floor heights if rotating equipment is
capable of delivering the necessary torque.
Environmental Limits 32 to 104 degrees F (040 degrees C) ambient
12,000 ft (3,658m) altitude
95% relative humidity (non-condensing)
Raw signals are unprocessed signals directly from a source. They are frequently too spikey to
use to read an average value but provide proof of activity and instantaneous reaction to chang-
ing conditions.
Filtered values represent the average, filtered value extrapolated from the raw signal to provide
a viewable, smoothed, signal.
11-3
Reference
11-5
Reference
TS Tach positive signal. Analog. 0 - 30 VDC (15 VDC @ 1000 RPM). Please
refer to Tachometer or Encoder Installation and Wiring on page 2-23.
TACH
DP1+ Positive going, +15V, digital pulse stream from iLand to iLink to iBox
(DP1 leads DP2 when car moves up). Please refer to iLand Landing Sys-
tem on page 3-2.
DP1- Negative going, -15V, digital pulse stream from iLand to iLink to iBox.
POSITION
DP2+ Positive going, +15V, digital pulse stream from iLand to iLink to iBox
(DP2 leads DP1 when car moves down)
DP2- Negative going, -15V, digital pulse stream from iLand to iLink to iBox
A+ Positive going, +12V, digital pulse from motor velocity encoder. Please
refer to Tachometer or Encoder Installation and Wiring on page 2-23.
VELOCITY ENCODER
11
11-7
Reference
TX+ iBox transmit, positive going serial communication stream from iBox to
iLink. Connects to iLink ICE-CTP Board terminal RX+. TX+ and TX-
comprise a differential communications pair. Please refer to Installing
iLink on page 3-13.
TX- iBox transmit, negative going serial communication stream from iBox to
CARTOP LINK
RX+ iBox receive, positive going serial communication stream from iLink to
iBox. Connects to iLink ICE-CTP board terminal TX+. RX+ and RX-
comprise a differential communications pair.
RX- iBox receive, negative going serial communication stream from iLink to
iBox. Connects to iLink ICE-CTP board terminal TX-.
ICTU Cartop Inspection Station UP Button input (includes SAF button). Acti-
vated = 110 VDC.
ICTD Cartop Inspection Station DN Button input (includes SAF button). Acti-
vated = 110 VDC.
INCP COP Inspection Station INSP/AUTO Switch input. Activated = 110 VDC.
CAR
INA Car Panel (Hoistway) Access Enable switch input. 0 VDC active signal
level. Off = 110 VDC.
ESC Car Panel Emergency Stop switch input. 0 VDC active signal level stops
car. Off = 110 VDC.
DCL Door Close Limit input. Door fully closed, input inactive, 0 VAC. Door not
closed signal level, 120 VAC.
DOL Door Open Limit input. Door fully open, input inactive, 0 VAC. Door not
open signal level, 120 VAC.
DPM Door Position Monitor input. Door closed, input inactive, 120 VAC. Door
not closed, 0 VAC.
UNTD Up Normal Limit Direction switch input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
UNT5 Up Slowdown Limit switch #5 input. 110 VDC = input on/switch closed.
0 VDC = input off/switch open.
UNT4 Up Slowdown Limit switch #4 input. 110 VDC = input on/switch closed.
0 VDC = input off/switch open.
UNT3 Up Slowdown Limit switch #3 input. 110 VDC = input on/switch closed.
0 VDC = input off/switch open.
UNT2 Up Slowdown Limit switch #2 input. 110 VDC = input on/switch closed.
0 VDC = input off/switch open.
UETS Up Emergency Terminal Limit switch input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
UNT1 Up Slowdown Limit switch #1 input. 110 VDC = input on/switch closed.
LIMITS
DNT1 Down Slowdown Limit switch #1 input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
DETS Down Emergency Terminal Limit switch input. 110 VDC = input on/
switch closed. 0 VDC = input off/switch open.
DNT2 Down Slowdown Limit switch #2 input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
DNT3 Down Slowdown Limit switch #3 input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
DNT4 Down Slowdown Limit switch #4 input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
DNT5 Down Slowdown Limit switch #5 input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
DNTD Down Normal Limit Direction switch input. 110 VDC = input on/switch
closed. 0 VDC = input off/switch open.
11
11-9
Reference
ATU Hoistway Access Top Up switch input. When the Car Panel Access Enable
switch (INA input) is on, an active input (key switch closure) here (110
VDC) will cause the car to move up the hoistway. A hoistway limit switch
electrically between the ATU input and the activating switch will open
and stop the car after it has moved the required distance up the hoist-
way (if installed). Normal/Off state = 0 VDC. Refer also to the -MRW
drawing in the job prints.
ATD Hoistway Access Top Down switch input. When the Car Panel Access
Enable switch (INA input) is on, an active input (key switch closure) here
(110 VDC) will cause the car to move down the hoistway. A hoistway
limit switch electrically between the ATD input and the activating switch
will open and stop the car after it has moved the required distance down
the hoistway (if installed). Normal/Off state = 0 VDC. Refer also to the -
H/WAY
ABU Hoistway Access Bottom Up switch input. When the Car Panel Access
Enable switch (INA input) is on, an active input (key switch closure) here
(110 VDC) will cause the car to move up the hoistway. A hoistway limit
switch electrically between the ABU input and the activating switch will
open and stop the car after it has moved the required distance up the
hoistway (if installed). Normal/Off state = 0 VDC. Refer also to the -MRW
drawing in the job prints.
ABD Hoistway Access Bottom Down switch input. When the Car Panel Access
Enable switch (INA input) is on, an active input (key switch closure) here
(110 VDC) will cause the car to move down the hoistway. A hoistway
limit switch electrically between the ABD input and the activating switch
will open and stop the car after it has moved the required distance down
the hoistway (if installed). Normal/Off state = 0 VDC. Refer also to the -
MRW drawing in the job prints.
GS Gate Switch input. The gate switch makes up when the elevator doors
close. When the switch is made, there will be 110 VDC on this input.
When the switch is open, there will be 0 VDC on this input. The gate
switch may be wired in series with other switches or locks on the eleva-
tor doors (as shown in the job prints) so that if any of the switches do
not make, the GS input will remain low and the car will not run.
DLAT Door Lock Access Top input. When a top hoistway access is provided (see
INA, ATU, and ATD), the hoistway door lock associated with that landing
is connected between the #3 bus and this input. When the switch is
made, there will be 110 VDC on this input. When the switch is open,
there will be 0 VDC on this input and the car will not run unless INA is
active and then only in response to the ATU or ATD input.
DLMS Door Lock Main String input. If top and bottom hoistway access (see
INA, ATU, ATD, ABU, and ABD) is not provided, all hoistway door locks
are wired in series between the #3 bus and DLMS. When the switches
are made, there will be 110 VDC on this input. When any switch is open,
there will be 0 VDC on this input and the car will not run.
DLAB Door Lock Access Bottom input. When a bottom hoistway access is pro-
vided (see INA, ABU, and ABD), the hoistway door lock associated with
that landing is connected between the #3 bus and this input. When the
LOCKS/CONTACTS
switch is made, there will be 110 VDC on this input. When the switch is
open, there will be 0 VDC on this input and the car will not run unless
INA is active and then only in response to the ABU or ABD input.
DCAT Door Contact Access Top input. When a top hoistway access is provided
(see INA, ATU, ATD, and DLAT), the hoistway door contact associated
with that landing is connected between the #3 bus and this input. When
the switch is made, there will be 110 VDC on this input. When the switch
is open, there will be 0 VDC on this input and the car will not run unless
INA is active and then only in response to the ATU or ATD input.
DCMS Door Contact Main String input. If top and bottom hoistway access (see
INA, ATU, ATD, ABU, and ADB) is not provided, all hoistway door con-
tacts are wired in series between the #3 bus and DCMS. When the
switches are made, there will be 110 VDC on this input. When any switch
is open, there will be 0 VDC on this input and the car will not run.
DCAB Door Contact Access Bottom input. When a bottom hoistway access is
provided (see INA, ABU, ABD, and DLAB), the hoistway door contact
associated with that landing is connected between the #3 bus and this
input. When the switch is made, there will be 110 VDC on this input.
When the switch is open, there will be 0 VDC on this input and the car
will not run unless INA is active and then only in response to the ABU or
ABD input.
GOV Governor input. The governor is connected between the #3 bus and this
input. When the governor switch is made, there is 110 VDC on this input.
It the governor switch trips/opens, there is 0 VDC on this input and the
car will not run.
11-11
Reference
BD Brake Drive relay indicator. When relay BD (iBox IRB board) is closed to
pick the brake, this LED is ON. Monitored by Safety Processor A.
TB Brake Triac active indicator. When the brake triac on the iBox IRB board
is active (completes circuit for BD relay), this LED will light. Monitored by
BRAKE
Safety Processor B.
BRD Brake Redundancy indicator. This LED lights when the main brake con-
tactor drops out.
BDRD Brake Drive Redundancy indicator. This LED lights when the BD relay
drops out.
MD Motor Drive relay indicator. When relay MD (iBox IRB board) is closed to
enable the motor, this LED will light. Monitored by Safety Processor A.
TM Motor Triac active indicator. When the motor triac on the iBox IRB board
is active (completes circuit for MD relay), this LED will light. Monitored
DRIVE
by Safety Processor B.
MRD Motor Redundancy indicator. This LED lights when the main motor con-
tactor drops out.
MDRD Motor Drive Redundancy indicator. This LED lights when the MD relay
drops out.
SAFC Safety Cartop input. Cartop safety relays and switches are wired in
series between SAFH (Safety Hoistway) and SAFC. If any contact in the
safety string opens, there will be 0 VDC on this input and the car will not
run. If all safety contacts in the string are closed, there will be 110 VDC
on this input.
SAFETY
SAFH Safety Hoistway input. Hoistway safety relays and switches are wired in
series between the #3 bus and SAFH. The path also includes the Gover-
nor switch, with the GOV connection providing access to the #3 bus via
the governor switch. (#3 to GOV through governor switch, GOV to SAFH
through hoistway safety relays and switches). The job prints for the job
provide specific wiring instructions. If any contact in the safety string
opens, there will be 0 VDC on this input and the car will not run. If all
safety string contacts are closed, there will be 110 VDC on this input.
SP1 D Optional input. Job prints will show if and how this is used on a per
installation basis.
SP2 D Optional Brake Pick Switch input. The Switch parameters on the Con-
troller > Configuration > Brake > Control tab indicate the state of termi-
nal SP2D (110VDC or 0V) used to indicate that the brake is picked (see
Brake - Control Tab - Switch on page 9-26.
SPARES
SP2 Optional input. Job prints will show if and how this is used on a per
installation basis.
SP3 Optional input. Job prints will show if and how this is used on a per
installation basis.
SP4 Optional input. Job prints will show if and how this is used on a per
installation basis.
MOR Out 1 - Out 32 The MOR (Multiple Output Relay) board provides 32 outputs customers
may use as needed for the particular job. Typical uses include activat-
ing chimes, buzzers, lights, etc. Each MOR board is configured accord-
ing to the job survey for a particular job before the system is shipped.
MOR boards may be installed in the iControl cabinet, in the iLink cartop
box, or in the iCentral cabinet (for elevator group controller use). Out-
put selection instructions are transmitted serially to the board. The 32
outputs are divided into five groups (1-4, 5-8, 9-16, 17-24, and 25-
32). According to need, each group can be connected to provide the
required output. Specific connections and output values are specified in
the job prints.
MIAC In 1 - In 32 The MIAC (Multiple Input AC) board provides 32 inputs customers may
use as needed for the particular job. MIAC boards may be installed in
the iControl cabinet, in the iLink cartop box, or in the iCentral cabinet
(for elevator group controller use). Typical uses include car call but-
tons, operating mode switches, etc. Specific connections are detailed in
the job prints. Please refer to Input Signal Groups on page 9-119.
11-13
Reference
switch opens, 0 VDC. Press reset button on IEQ board to reset (after
clearing any potential problems caused by quake).
IEQ
CW2 Along with CW1, ring and string input from counterweight movement
sensor. Normally at 24 VDC.
CW1 Along with CW2, ring and string input from counterweight movement
sensor. Normally at 24 VDC.
RG5 Rope gripper input. Normally at 120 VAC. If rope gripper manual oper-
ation is selected, or if rope gripper is triggered, 0 V.
Field connections are also made to terminal strips in the iControl cabinet. Terminal connec-
tions provided vary from job to job depending upon need. Power distribution connections,
beyond the basic three system buses, are specified in the job prints and are not included here.
B1, B2 DC power to motor brake. Voltage across terminals will vary depending upon brake
control method (Low Current Brake Board or iField Brake Module). See your job
prints. Significant voltage may be present even when brake is not picked.
MF1, MF2 DC power to motor field. Voltage across terminals will vary. Significant voltage may
be present even if motor is not running.
15A Final Limit switch. Wired as shown in job prints. 110 VDC when switch is made. 0
VDC when switch in string opens.
15B Pit/Final Limit switch. Wired as shown in job prints. 110 VDC when switch is made.
0 VDC when switch in string opens.
1 System common.
The following tables provide in-depth addressing information for the iControl/iCentral system.
MCE Direct-Connect Port (Links one iBox to one Laptop with iView)
IBox Direct Connect Port = same as above
IP Subnet Gateway DNS
Any iBox 192.168.193.1 255.255.255.0 Blank or 0.0.0.0 Blank or 0.0.0.0
Any PC / Laptop 192.168.193.2
(MCE reserved) All other addresses
11
11-15
Reference
= same as above
LAN Network Hub (Blue cables)
* = see Note #1
IP Subnet Gateway DNS
(IEEE reserved) 192.168.191.0 255.255.255.0 192.168.191.254 * 192.168.191.254 *
Group 1 LAN Network (Blue cables)
IP Subnet Gateway DNS
iBox Car 1 192.168.191.1 255.255.255.0 192.168.191.254 * 192.168.191.254 *
iBox Car 2 192.168.191.2
iBox Car 3 192.168.191.3
iBox Car 4 192.168.191.4
iBox Car 5 192.168.191.5
iBox Car 6 192.168.191.6
iBox Car 7 192.168.191.7
iBox Car 8 192.168.191.8
iBox Car 9 192.168.191.9
iBox Car 10 192.168.191.10
iBox Car 11 192.168.191.11
iBox Car 12 192.168.191.12
iBox Car 13 192.168.191.13
iBox Car 14 192.168.191.14
iBox Car 15 192.168.191.15
iBox Car 16 192.168.191.16
iBox Car 17 192.168.191.17
iBox Car 18 192.168.191.18
iBox Car 19 192.168.191.19
iBox Car 20 192.168.191.20
iView 192.168.191.101
192.168.191.102
iCue 192.168.191.201
192.168.191.202
Group 2 LAN Network (Blue cables)
IP Subnet Gateway DNS
iBox Car 1 192.168.191.21 255.255.255.0 192.168.191.254 * 192.168.191.254 *
iBox Car 2 192.168.191.22
iBox Car 3 192.168.191.23
iBox Car 4 192.168.191.24
iBox Car 5 192.168.191.25
iBox Car 6 192.168.191.26
iBox Car 7 192.168.191.27
iBox Car 8 192.168.191.28
iBox Car 9 192.168.191.29
iBox Car 10 192.168.191.30
iBox Car 11 192.168.191.31
iBox Car 12 192.168.191.32
11-17
Reference
iBox Car 20 192.168.191.100
192.168.191.109
iView
192.168.191.110
192.168.191.209
iCue
192.168.191.210
Group 6 LAN Network (Blue cables)
IP Subnet Gateway DNS
iBox Car 1 192.168.191.121 255.255.255.0 192.168.191.254 * 192.168.191.254 *
iBox Car 2 192.168.191.122
iBox Car 3 192.168.191.123
iBox Car 4 192.168.191.124
iBox Car 5 192.168.191.125
iBox Car 6 192.168.191.126
iBox Car 20 192.168.191.140
192.168.191.111
iView
192.168.191.112
192.168.191.211
iCue
192.168.191.212
Group 7 LAN Network (Blue cables)
IP Subnet Gateway DNS
iBox Car 1 192.168.191.141 255.255.255.0 192.168.191.254 * 192.168.191.254 *
iBox Car 2 192.168.191.142
iBox Car 3 192.168.191.143
iBox Car 4 192.168.191.144
iBox Car 5 192.168.191.145
iBox Car 6 192.168.191.146
iBox Car 20 192.168.191.160
192.168.191.113
iView
192.168.191.114
192.168.191.213
iCue
192.168.191.214
Group 8 LAN Network (Blue cables)
IP Subnet Gateway DNS
iBox Car 1 192.168.191.161 255.255.255.0 192.168.191.254 * 192.168.191.254 *
iBox Car 2 192.168.191.162
iBox Car 3 192.168.191.163
iBox Car 4 192.168.191.164
iBox Car 5 192.168.191.165
iBox Car 6 192.168.191.166
iBox Car 20 192.168.191.180
192.168.191.115
iView
192.168.191.116
192.168.191.215
iCue
192.168.191.216
Note
#1: This parameter may have a site-dependant value depending on the unique DSL service or
internet connection details. The default value shown can be used until a new value is identified.
There may be more than one of these values provided.
Summary
This is a summary of the entire LAN IP address space including MCE supplied equipment and
non-MCE supplied equipment.
11-19
Reference
Summary by Group
Group #1 Floors ( ) Machine Room Floor ( )
192.168.192.201
iCue
192.168.192.202
192.168.191.101
iView
192.168.191.102
192.168.191.201
iCue
192.168.191.202
11
11-21
Reference
192.168.191.103
iView
192.168.191.104
192.168.191.203
iCue
192.168.191.204
192.168.191.105
iView
192.168.191.106
192.168.191.205
iCue
192.168.191.206
192.168.191.107
iView
192.168.191.108
192.168.191.207
iCue
192.168.191.208
11
11-23
Reference
192.168.191.109
iView
192.168.191.110
192.168.191.209
iCue
192.168.191.210
192.168.191.111
iView
192.168.191.112
192.168.191.211
iCue
192.168.191.212
192.168.191.113
iView
192.168.191.114
192.168.191.213
iCue
192.168.191.214
192.168.191.115
iView
192.168.191.116
192.168.191.215
iCue
192.168.191.216
11
11-25
Reference
192.168.191.117
iView
192.168.191.118
192.168.191.217
iCue
192.168.191.218
Index-1
ALT SPEED PROFILE 1 message 6-13 High-pass Frequency 9-104
ALT SPEED PROFILE 2 message 6-13 Low-pass Frequency 9-104
Alternate 1 profile 4-19, 9-145 Armature Voltage Dampen Feedback test point, 11-4
Alternate 2 profile 4-19, 9-145 Armature Voltage Limit 4-7
Alternate Dispatcher selection 10-8 Armature Voltage Limit, calculate and set 2-64
Alternate Fire Switch ON input 9-119 Armature Voltage Signal 4-10
Alternate Floor Smoke input 9-119 Armature Voltage Signal test point, description 11-4
ALTERNATE FLOOR SMOKE message 6-13 Armature Voltage Synthetic Feedback test point, 11-4
Alternate Floor Smoke Sensor Recall message 6-13 Arrival Fixtures, parameters 9-35
Alternate Recall floor, Fire service 9-47 Ascending Car Overspeed Fault message 6-13
Alternate Speed Profile 1 Activated message 6-13 ASCND CAR OVR SPD FLT message 6-13
Alternate Speed Profile 1 Deactivated message 6-13 ATD, Hoistway Access Top Down switch input 6-114, 11-10
Alternate Speed Profile 1 input 9-119 Attendant Buzzer output 9-128
Alternate Speed Profile 1 message 6-13 Attendant HC Above output 9-128
Alternate Speed Profile 2 Activated message 6-13 Attendant HC Below output 9-128
Alternate Speed Profile 2 Deactivated message 6-13 Attendant Service Down input 9-119
Alternate Speed Profile 2 input 9-119 Attendant Service Indicator output 9-128
Alternate Speed Profile 2 message 6-13 Attendant Service input 9-119
Anti-nuisance 9-41 Attendant Service message 6-13
Cancel car calls behind car 9-41 Attendant Service mode 9-5
Light load 9-41 Attendant Service Non-Stop input 9-119
Photo Eye 9-41 Attendant Service parameters 9-81
Anti-nuisance controls 4-35 Attendant Service Up input 9-119
Approach deceleration parameter 4-18, 9-149 Attendant Svc message 6-13
Approach jerk parameter 4-18, 9-149 ATU, Hoistway Access Top Up switch input 6-114, 11-10
Armature Active Status test point, description 11-3 Auto Stop parameters 9-82
Armature Command (Control) test point, description 11-3 Automatic 10-71
Armature Command (Damped) test point, description 11-3 Automatic mode, selecting 10-15
Armature Command (Raw) test point, description 11-3 Automatic Stop Input 9-119
Armature Composite Control test point, description 11-3 Automatic Stop message 6-13
Armature Control Set test point, description 11-3 Automatic Swing Operation 9-42
Armature Current 4-7, 9-9 Available for fire service output 9-128
Dampening Speed 9-104 Average wait times 10-74
Dampening Torque 9-104
High-pass frequency 9-104 B
Low-pass frequency 9-104 B-, Velocity Encoder input 6-112, 11-7
Armature Current Dampen Feedback test point, 11-3 B+, Velocity Encoder input 6-112, 11-7
Armature Current Limit 2-61, 4-7, 4-8 B1, B2, DC power to motor brake 11-14
verifying 2-64 Backup Dispatcher, description of 10-4
Armature Current Signal test point, description 11-3 Backup Dispatching 1-21, 10-6
Armature Current Synthetic Feedback test point, 11-3 Backup power direction reversal message 6-14
Armature Current Test 9-96 Backup power recall done output 9-128
Armature Differential Command test point, description 11-3 Backup power recall input 9-119
Armature Differential Gain test point, description 11-3 BACKUP POWER RECALL message 6-14
Armature Error (Damped) test point, description 11-4 Backup power recall OFF message 6-14
Armature Error (Raw) test point, description 11-4 Backup power recall ON message 6-14
Armature Feedforward (Control) test point, description 11-4 Backup power recall reverse direction input 9-119
Armature Feedforward (Raw) test point, description 11-4 Backup power unit failure activated message 6-14
Armature Integral Command test point, description 11-4 Backup power unit failure deactivated message 6-14
Armature Integral Gain test point, description 11-4 Backup power unit failure input 9-119
Armature On Status test point, description 11-4 Backup power unit failure message 6-14
Armature overcurrent overload protection adjustment 4-46 Balanced 10-71
Armature Proportional Command test point, description 11-4 Balanced Mode message 6-14
Armature Proportional Gain test point, description 11-4 Balanced mode, selecting 10-15
Armature Test 9-96 Balancing the Counterweight 3-29
Armature Voltage 4-10, 9-9 BATTERY VLTG LOW-IMP message 6-14
Dampening Speed 9-104 Battery Voltage Low-IMP message 6-14
Dampening Torque 9-104 BD, Brake Drive relay indicator 11-12
Index-3
CAR DEL DOORS STALLED message 6-18 Car Panel Inspection Disabled message 6-20
CAR DEL DOORS UNKNOWN message 6-18 Car Panel Inspection Enabled message 6-20
Car Delayed output 9-129 Car Panel Inspection Inputs OK message 6-20
Car delayed timer 9-41 Car Panel Inspection mode 9-5
Car delayed with doors closed message 6-17 Car Panel Inspection Operation message 6-20
Car delayed with doors closing message 6-17 Car Position
Car delayed with doors open message 6-18 Actual 9-9
Car delayed with doors opening message 6-18 Logical 9-9
Car delayed with doors stalled message 6-18 Car reaction to overspeeding 4-56
Car delayed with unknown door position message 6-18 Car response, adjusting 2-65
Car Door Bypass message 6-18 car runs away 2-61
Car Door Bypass switch, iBox control 7-12 car runs in wrong direction 2-61
Car fan and light timer 9-41 Car shut down due to emergency power operation with no su-
Car Heavy Load - Deactivated message 6-18 pervisor (Activated) message 6-20
Car Heavy Load Activated - Hall Calls Bypassed message 6-18 Car shut down due to emergency power operation with no su-
CAR HEAVY LOAD message 6-18 pervisor (Deactivated) message 6-20
Car identifier parameter 4-57, 9-108 Car Speed 9-8
Car In Service output 9-129 Car Speed Calibration 2-62
Car label parameter 9-108, 10-7 Car Speed specification 11-2
Car Not Empty Sensor Input 9-120 Car Statistics tab 9-11
Car Operating Panel Connections 3-18 Car status messages window 9-10
Car Operation Car Stop Switch Open message 6-21
Attendant Service 9-81 Car Top, iBox status LED 7-11
Auto Stop 9-82 Car/Counterweight Buffer Test 4-51
CFSS 9-76 Car/Counterweight Safety Test 4-50
Configuration parameters 9-309-88 card reader, call enable device 9-125, 9-126, 10-39, 10-56
Devices 9-35 Cars, number of parameter 10-7
diagnostic flags 9-13 CARTOP AUTO UIM FLT message 6-21
Doors 9-31 Cartop Automatic Unintended Motion Fault message 6-21
Earthquake 9-67 CARTOP COMM FAULT message 6-21
Elevator recall 9-64 Cartop Communication Fault message 6-21
Emergency Medical Service 9-69 Cartop Emergency Stop message 6-21
Emergency power 9-73 Cartop Emergency Stop switch 3-17
Fire Service 9-47 Cartop Exit no Counterweight Configuration Error 6-22
Flood Operation 9-79 Cartop Exit Open message 6-21
Independent service 9-62 Cartop Exit Open Off message 6-21
Passenger 9-40 Cartop Firmware Update Mode message 6-22
Sabbath operation 9-84 CARTOP FW UPDATE MODE message 6-22
Shuttle service 9-87 Cartop Insp message 6-22
CAR OS DOORS CLOSED message 6-19 CARTOP INSP UIM FLT message 6-22
CAR OS DOORS CLOSING message 6-19 Cartop Inspection Disabled message 6-22
CAR OS DOORS OPEN message 6-19 Cartop inspection DOWN button 3-17
CAR OS DOORS OPENING message 6-19 Cartop Inspection Enabled message 6-22
CAR OS DOORS STALLED message 6-19 Cartop Inspection Inputs OK message 6-22
CAR OS DOORS UNKNOWN message 6-19 Cartop Inspection message 6-22
Car Out Of Service output 9-129 Cartop Inspection mode 9-5
Car out of service timer 9-41 Cartop Inspection Operation message 6-22
Car out of service unknown door position message 6-19 Cartop Inspection output 9-129
Car out of service with doors closed message 6-19 Cartop Inspection Switches 3-17
Car out of service with doors closing message 6-19 Cartop Inspection Unintended Motion Fault message 6-22
Car out of service with doors open message 6-19 Cartop inspection UP button 3-17
Car out of service with doors opening message 6-19 Cartop Inspection Wiring 2-29
Car out of service with doors stalled message 6-19 Cartop interconnections 1-16
Car Over Load Activated message 6-20 Cartop Link Connections, iBox 6-113, 11-8
Car Over Load Deactivated message 6-20 Cartop Position 9-9
CAR OVERLOAD message 6-20 Cartop Power Loss message 6-22
Car Panel (Hoistway) Access Enable switch input 6-113, 11-8 Cartop Processor Board Quick Reference 6-86
Car Panel Emergency Stop switch input 6-113, 11-8 Cartop Safety Relay 2-28
Index-5
Correction profile 4-19, 9-145 Devices configuration 9-359-39
Counterweight balancing 9-158 Diagnostic flags
Counterweight balancing, preparing for final adjust 3-29 Car Operation 9-13
Counterweight derailment detector 3-21 Drive 9-13
Counterweight Derailment output 9-129 Motion 9-13
counterweight learn operation 9-158 Safety 9-13
Counterweight Learn procedure 3-28 Diagnostic Outputs window 9-14
Counterweight position parameter 9-158 Diagnostics 9-119-24
Coupling rotational ratio 2-45 Car Statistics tab 9-11
Coupling rotational ratio, adjusting car speed 2-62 Data Trap 9-12
CP INSP. DISABLED message 6-20 Diagnostic Flags 9-12
Creating a Configuration file 8-20 Event Log 9-15
creating a direct connection 2-39 Fault Bypass 9-18
Creating a new LAN connection 8-13 Terminal Switches Status 9-20
Cross Registration 10-55 Differential low-pass frequency parameter 9-100
Cross registration serial inputs 10-55 Direct connections 8-58-12
Cross registration serial outputs 10-55 3 = PC port 2-35
Crosshead Deflection Load Weigher 4-34 connecting 8-11
Cross-registration 10-36 creating 2-39, 8-9
CT INSP. DISABLED message 6-22 Direction arrow down 2 output 9-129
CTEX NO CWI CFG ERROR message 6-22 Direction Arrow Down output 9-129
Current Control 9-104 Direction arrow up 2 output 9-130
Dampening Current 9-104 Direction Arrow Up output 9-129
Current Limit LED 2-61, 4-8, 4-10 Disable Front Hall Door Buttons input 9-123
Current Loop Integral, System 12 drive 2-51 Disable Rear Hall Door Buttons input 9-123
Current Sensor, System 12 drive 2-51 Discontinuous Current
Custom Outputs 9-137 Integral 9-98
Custom outputs, configuring 9-156 Proportional 9-98
Dispatcher = Car n message 6-24
D Dispatching
DAC Offset Status test point, description 11-4 Configurations tab, Simplex / Swing / Backup Dispatch-
DAC, verifying DAC conversion 2-49 er 10-12
Dampening parameters 9-103 description of 1-4
Data trap 9-12 Dispatching tab 10-11
Data Trap Triggering Event 9-12 Display contrast, iBox control 7-4
DCAB, Door Contact Access Bottom input 6-115, 11-11 DLAB, Door Lock Access Bottom input 6-115, 11-11
DCAT, Door Contact Access Top input 6-115, 11-11 DLAT, Door Lock Access Top input 6-115, 11-11
DCL, Door Close Limit input 6-113, 11-8 DLM, Down Leveling Marker Sensor input 6-113, 11-8
DCMS, Door Contact Main String input 6-115, 11-11 DLMS, Door Lock Main String input 6-115, 11-11
Dead zone distance parameter 9-147 DN ETS POSITION FAULT message 6-25
Dead zone, adjusting for final stop 4-31 DN NTSn L1 SPEED FLT message 6-25
Deceleration parameter 4-18, 9-149 DN NTSn L2 SPEED FLT message 6-26
Deceleration rate, bunching up of 4-20 DN NTSn POSITION FLT message 6-26
Default IP Addresses 2-34 DNT1, Down Slowdown Limit switch #1 input 6-114, 11-9
iBox settings 7-9 DNT2, Down Slowdown Limit switch #2 input 6-114, 11-9
default parameter settings, saving 8-21 DNT3, Down Slowdown Limit switch #3 input 6-114, 11-9
Delayed Mechanically In Service output 9-129 DNT4, Down Slowdown Limit switch #4 input 6-114, 11-9
Delta P.R. 2-48 DNT5, Down Slowdown Limit switch #5 input 6-114, 11-9
Demand Down Peak 10-71 DNTD, Down Normal Limit Direction switch input 6-114, 11-9
Demand Down Peak Mode message 6-24 docking and undocking windows in iView 8-35
Demand Down Peak mode, selecting 10-15 DOL, Door Open Limit input 6-113, 11-8
demand peak detection parameters 10-17 Door close delay timer 9-31
Demand peak options 10-17 Door Close Protection Timer 9-32
Demand peak parameters 10-19 Door Dwell Timers 9-44
Demand Up Peak 10-71 ADA Car Call 9-44
Demand Up Peak Mode message 6-24 ADA Hall Call 9-44
Demand Up Peak mode, selecting 10-15 Car Call 9-44
DETS, Down Emergency Terminal Limit switch 6-114, 11-9 Hall Call 9-44
Index-7
Editing a configuration file 8-23 Emergency power input 9-73
Editing displays 8-39 Emergency Power Manual Car Select input 9-120
EEPROM Device Error message 6-30 Emergency Power Manual Override input 9-120
Egress floor 9-40 Emergency Power parameters 9-739-75
Egress Floor Gong output 9-130 Emergency Power Permission to Run input 9-120
Electrical Governor Test 4-50 Emergency Power Phase I output 9-130
Elevator code compliance 1-3 Emergency Power Phase II output 9-130
Elevator Recall Operation (Switch n) message 6-30 Emergency Power Priority Status output 9-130
Elevator recall parameters 9-64 Emergency power profile 4-18, 9-145
ELEVATOR RECALL SWn message 6-30 Emergency Power Recall 10-34
EM BK UIM RESET STUCK message 6-32 Emergency Power Recall Complete message 9-130
EMCO Load Weigher Installation 5-51 Emergency Power Recall message 6-33
EMERG ALARM ACTIVATED message 6-30 Emergency Power Return input 9-120
EMERG BRAK LEG 2 SHORT message 6-31 Emergency Power Run 10-35
EMERG BRAKE OK OPEN message 6-31 Emergency Power Run message 6-34
EMERG BRK LEG 1 SHORT message 6-31 Emergency Power serial inputs 10-54
EMERG POWER RECALL message 6-33 Emergency Power serial outputs 10-54
EMERG POWER RUN message 6-34 Emergency Power Service output 9-130
EMERG POWER SHUTDOWN message 6-34 Emergency Power Shutdown message 6-34
EMERG PWR NO COMM message 6-33 Emergency rate limited stop parameter 9-92
Emerg. Pwr. Car Selected to Recall output 9-130 Emergency slowdown profile 4-18, 4-53, 9-145
Emerg. Pwr. Car Selected to Run output 9-130 Emergency Stop Input 9-120
Emergency Alarm Acknowledged message 6-30 Emergency Stop Input Activated message 6-34
Emergency Alarm Activated (Alarm button) message 6-30 Emergency Stop Input Deactivated message 6-34
Emergency Alarm Activated (Car delayed with doors closed) EMERGENCY STOP INPUT message 6-34
message 6-31 Emergency Stop switch 2-29
Emergency Alarm Activated (In-car stop switch) 6-31 Emergency Terminal Limit (ETS) 4-11, 9-21
Emergency Alarm Activated (Safety opened) message 6-31 Emergency Terminal Overspeed 4-55
Emergency Alarm Activated message 6-30 Emergency Terminal Switch Overspeed Tests 4-54
Emerg Alarm Deactivated without Acknowledgment 6-31 Empty Car Output 9-130
Emergency Alarm Monitoring 9-36 Empty Car Tests, preparing for final adjustments 3-31
Emergency Brake Board Quick Reference 6-92 Empty load detection 4-34
Emergency Brake Leg 1 Short Fault message 6-31 Empty load input 9-121
Emergency Brake Leg 2 Short Fault message 6-31 Empty Load output 9-131
Emergency Brake OK open message 6-31 Empty load threshold 4-35, 4-37
Emergency Brake OK open Off message 6-32 EMS Car Buzzer output 9-130
Emergency Brake Test - Unintended Motion 4-52 EMS Car Light output 9-130
Emergency Brake Tripped message 6-32 EMS Car Switch input 9-121
Emergency Brake UIM Reset Button Stuck message 6-32 EMS Hall Light 1 (2) outputs 9-130
Emergency Dispatch input 9-120 EMS Hall Switch 1 input 9-121
Emergency Dispatch message 6-32 EMS Hall Switch 2 input 9-121
Emergency Dispatch Off message 6-32 EMS In-car (Switch n) message 6-32
Emergency Dispatch On message 6-32 EMS In-car (Switch 1) mode 9-6
Emergency Dispatch Override input 9-120 EMS In-car (Switch 2) mode 9-6
Emergency Exit contact 3-17 EMS Recall (Switch n) message 6-33
Emergency Medical Service Bypassed message 6-32 EMS Recall (Switch 1) mode 9-6
Emergency Medical Service Deactivated message 6-32 EMS Recall (Switch 2) mode 9-6
Emerg Medical Service In-Car Activated (Switch n) 6-32 Enable switch, iBox control 7-12
Emergency Medical Service parameters 9-699-72 Encoder Signal test point, description 11-4
Emergency Medical Service Recall Activated (Switch n) 6-33 Encoder. See also Velocity Encoder
Emergency power 5-26, 10-33 Environmental Considerations 2-4
Emergency Power Activated message 6-33 Environmental Limits specification 11-2
Emergency Power and no communication with group 6-33 EP Car Selected to Run or Recall output 9-131
Emergency Power Auto Car Select input 9-120 EPI input 10-34
Emergency Power Auto Recall input 9-120 EQ board, Earthquake sensor 3-21
Emergency Power Car Done Recall output 9-130 EQ Reset 3-21
Emergency Power Deactivated message 6-33 Equipment Location 2-4
Emergency Power input 9-120 Error compensation, adjusting 2-66
Index-9
Fire Service Recall Deactivated message 6-37 Front (Rear) Nudging Audible output 9-134
Fire Service Recall Main message 6-37 Front (Rear) Up Car Lantern output 9-134
Fire Service Recall Main mode 9-6 FRONT AUX DOB BYP message 6-38
Fire Svc In-car message 6-36 Front Auxiliary Door Close Button input 9-123
Fire Switch Settings 9-52 Front Auxiliary Door Open Button Bypassed message 6-38
Fire Warning Buzzer output 9-131 Front Constant Pressure Close (Front Door) input 9-123
Fire Warning Light output 9-131 Front Constant Pressure Open (Front Door) input 9-123
Firefighters Panel Unlock output 9-131 Front COP2 Door Close Button input 9-123
Firmware Update screen 8-41 Front COP2 Door Hold Button input 9-123
Flare jerk parameter 4-18, 9-149 Front COP2 Door Open Button input 9-123
Flare pattern frequency parameter 9-100 Front COP2 Door Stop Button input 9-123
Flood Operation Activated message 6-37 FRONT DOB BYPASSED message 6-40
Flood Operation Buzzer output 9-131 Front Door Close Button (COP1) input 9-123
Flood Operation Deactivated message 6-37 Front Door Close Fault message 6-39
Flood Operation Input 9-121 Front Door Close Fault Recovery Failure message 6-39
FLOOD OPERATION message 6-37 FRONT DOOR CLOSE FLT message 6-39
Flood operation parameters 9-79 Front Door Close Time-out message 6-39
Flood Operation Status output 9-131 FRONT DOOR CNTCT FLT message 6-39
Floor Data Settings 9-109 Front Door Contact Fault message 6-39
Floor Data Tab 9-109 Front Door Hold Button (COP1) input 9-123
Floor Heat Detectors Activated message 6-37 Front Door Open Button (COP1) input 9-123
Floor Heat Detectors Deactivated message 6-37 Front Door Open Button Bypassed message 6-40
FLOOR HEAT DETECTORS message 6-37 Front Door Open Fault message 6-40
Floor Heights Front Door Open Time-out message 6-40
Learn procedure 4-2 Front Door Stop Button (COP1) input 9-123
Learn tab 9-161 FRONT DOORS STOPPED message 6-40
Learning the 4-2 Front Doors Stopped message 6-40
Floor Heights Configuration parameters 9-107 Front DPM Open - GS Closed message 6-40
Floor Heights Learn status message 9-163 FRONT HALL DOB BYP message 6-41
Floor label parameter 10-7 Front Hall Door Close Button input 9-123
Floor Level Sensor Adjustment 3-11 Front Hall Door Hold Button input 9-123
Floor Leveling Accuracy specification 11-2 Front Hall Door Open Button Bypassed message 6-41
Floor Location Fault message 6-38 Front hall door open button input 9-123
Floor Offset Distance parameter 3-2 Front Hall Door Stop Button input 9-123
Floor offsets, calibrating 4-27, 9-164 Front Momentary Pressure Close (Front Door) input 9-123
Floor Override Input 9-121 Front Momentaty Pressure Open (Front Door) input 9-123
Floor Sensor Fault message 6-38 FRONT PHOTO EYE BYP message 6-41
Floor Sub-Address or Call Type Jumper 5-34 Front Photo Eye Bypassed message 6-41
Floor Synchronization 9-146 Front Photo Eye Cut Out input 9-123
Floor Synchronization Fault message 6-38 FRONT PHOTO EYE FAIL message 6-41
Floors, number of parameter 10-7 Front Photo Eye Failure message 6-41
FLT BYP SW TIMED OUT message 6-36 FRONT SAFE EDGE BYP message 6-41
Following error 2-45 Front Safe Edge Bypassed message 6-41
calibrating 2-67 FRONT SAFE EDGE FAIL message 6-41
Front (Rear) Closing Warning Light output 9-133 Front Safe Edge Failure message 6-41
Front (Rear) DCLC Output 9-133 Fuses 2-16, 5-7
Front (Rear) Disable Hall Door Buttons output 9-133 Fuses on the iBox 7-13
Front (Rear) Door Car Gong output 9-133
Front (Rear) Door Close Limit output 9-133 G
Front (Rear) Door Closing Warning Buzzer output 9-133 Gate release Solenoid output 9-131
Front (Rear) Door Disable Automatic Close output 9-133 Gateway 7-9, 8-4
Front (Rear) Door Enable output 9-134 General Configuration parameters 9-1089-112
Front (Rear) Door Hold End output 9-134 Active configuration settings 9-112
Front (Rear) Door Hold Function output 9-134 Car call eligibility 9-110
Front (Rear) Door Left Open output 9-134 Car identifier 9-108
Front (Rear) Door Lock Power output 9-134 Car label 9-108
Front (Rear) Door This Car Up output 9-134 Floor Data tab 9-109
Front (Rear) Down Car Lantern output 9-134 Group identifier 9-108
Index-11
replacing 6-81 accuracy 3-2
Safety bypass jumper 7-13 adjustments 3-7
setting and verifying the IP address 7-10 cartop mounting 3-3
status LEDs 7-11 connections 3-11
status messages 7-12 description 1-1, 1-17, 3-2
view and set parameters 7-5 installation instructions 3-5
View/register calls 7-8 installing floor leveling magnets 3-9, 3-10
viewing factory data 7-8 iView parameter setting 3-12
viewing MAC addresses 7-8 magnet positioning 3-6
viewing serial numbers 7-8 pedistal fabrication and mounting 3-4
viewing the Event log 7-8 Status LEDs 3-12
viewing version info 7-8 Verifying position encoder resolution 3-27
iBox field connections 11-711-13 iLand Mounting on Pedestal 3-4
ICE-COP Board Diagnostics 6-4 iLand Pedestal 3-3
ICE-CTP Cartop Processor Board iLand Status LEDs 3-12
diagnostics 6-89 iLink Cartop Box 3-133-19
Quick Reference 6-86 car operating panel connections 3-18
ICE-EB Emergency Brake Board Quick Reference 6-92 description 1-1
ICE-FML Field Module Logic Board Quick Reference 6-93 description of communication 1-18
ICE-IEQ Earthquake Board Quick Reference 6-96 diagnostics 6-89
ICE-IMP Main Processor Board Quick Reference 6-98 enclosure 3-14
ICE-IRB Relay Board Quick Reference 6-100 installation 3-133-19
ICE-IRD Rear Door Board Quick Reference 6-103 power connections 3-18
ICE-MIAC Multiple Input AC Board Quick Reference 6-105 serial connection to iControl 3-17
ICE-MIAC-24V Multiple Input AC/DC Board Quick Ref 6-105 troubleshooting 6-89
ICE-MOR Multiple Output Relay Board Quick Ref 6-107 iMonitor, description 1-1, 1-21
ICE-RG Rope Gripper Board Quick Reference 6-109 IMP SW FAULT
ICE-SAF Safety Board Quick Reference 6-111 EM STOP message 6-44
ICE-SF Serial Fixtures Board Quick Reference 6-116 FLT BYP message 6-44
iControl INSP DN message 6-45
cartop communication 1-18 INSP EN message 6-45
cartop interconnections 1-16 INSP message 6-45
central monitoring 1-21 LEARN message 6-45
DC specifications 11-2 TEST message 6-45
description 1-1, 1-5 IMP SW FLT
dispatching interconnections 1-19 C DOOR BP message 6-44
layout 1-5 H DOOR BP message 6-44
load weighing 1-23 WRITE EN message 6-45
logging and report generating 1-22 IMP Switch Fault - Car Door Bypass message 6-44
overview 1-2 IMP Switch Fault - Emergency Stop message 6-44
system interconnections 1-15 IMP Switch Fault - Fault Bypass message 6-44
iControl messages 6-13, 6-136-79 IMP Switch Fault - H. Door Bypass message 6-44
iControl wiring connections 2-11 IMP Switch Fault - Inspection DOWN message 6-45
iControllers 5-11 IMP Switch Fault - Inspection Enable message 6-45
ICPD, COP Inspection Station DN Button input 6-113, 11-8 IMP Switch Fault - Inspection message 6-45
ICPU, COP Inspection Station UP Button input 6-113, 11-8 IMP Switch Fault - Inspection UP message 6-45
ICTD, Cartop Inspection Down Button 3-17 IMP Switch Fault - LEARN message 6-45
ICTD, Cartop Inspection Station DN Button input 6-113, 11-8 IMP Switch Fault - None message 6-45
ICTU, Cartop Inspection Station UP Button input 6-113, 11-8 IMP Switch Fault - Write Enable message 6-45
ICTU, Cartop Inspection Up Button 3-17 In Group, iBox status LED 7-11
iCue 5-25 In Use Light output 9-132
Capabilities 5-3 INA, Car Panel (Hoistway) Access Enable switch 6-113, 11-8
Dedicated 5-12 In-car CFSS Operation 9-78
iCue dispatching, description of 1-1, 1-4 In-Car Fire Door Operation output 9-132
iCue GUI 5-25, 5-27 In-Car Fire Hold output 9-132
Idle Swing Car Timer 9-42 In-Car Fire Recall output 9-132
iLand Cable Connections 3-11 In-Car Inspection output 9-132
iLand Landing System 1-17, 3-23-12 INCP, COP Inspection Station INSP/AUTO Switch input 6-
Index-13
diagnostic tabs 8-25, 8-31 Learn Switch Timed Out Fault message 6-53
docking and undocking windows 8-35 Learn switch, iBox control 7-12
editing the virtual oscilloscope display 8-39 Learn U/DNT1-5 and U/DETS Positions message 6-53
installing 8-3 Learn U/DNT1-5 and U/DETS Speeds message 6-53
Layouts 8-30 LEARN U/DTS POSITIONS message 6-53
pinning and unpinning windows 8-33 LEARN U/DTS SPEEDS message 6-53
printing screens 8-38 LEARNING EMPTY LOAD message 6-53
programming 1-11 Learning empty load values message 6-53
resizing windows 8-34 LEARNING FULL LOAD message 6-53
saving parameters to a configuration file 8-20 Learning full load values message 6-53
Send command 8-19 Learning the
sending parameters to the controller 8-19 Building floor heights 4-2
setting parameters 8-18 Counterweight 3-28
setting the systems date and time 8-38 Empty and loaded car weights 4-37
setup tabs 8-25 ETS and NTS Limit Switches 4-11
View menu contents 8-26 Load weights 4-34, 9-165
windows and tabs 8-25 Safety Configuration 2-46
working offline 8-23 Level Down Sensor 3-12, 4-5
working online 8-17 Level Up Sensor 4-5
iView Logged Off message 6-52 Leveling distance parameter 4-18, 9-147
iView Logged On message 6-52 Leveling Overspeed Test 4-52
iView Lost Connection message 6-52 Leveling overspeed, Safety parameter 9-167
iView Status Bar 9-3 Leveling sensor indicators 9-10
iView Timed Out message 6-52 Leveling speed parameter 4-18, 9-147
iView windows and tabs 9-19-139 Leveling speed, adjusting for final stop 4-30
IZO test point 9-106 Light load anti-nuisance 4-34, 9-41
IZO, System 12 drive 2-52 Light Load Anti-nuisance message 6-54
Light Load Input input 9-122
J Light Load output 9-132
Jerk specification 11-2 Light load threshold 4-35, 4-37, 9-141
Job name parameter 10-7 LIMIT SW CHKSUM FAULT message 6-54
Job Prints 2-7 LIMIT SW LEARN FAULT message 6-54
Job prints 5-12, 5-47, 6-107, 6-120 Limit Switches Checksum Fault message 6-54
Limit Switches Learn Fault message 6-54
Load calibration on message 6-54
K Load learn process activated message 6-54
Keypad controls, iBox 7-4 Load learn process deactivated message 6-54
keypad, call enable device 9-125, 9-126, 10-56 Load Weigher 1-23
Cross Head Deflection 1-23, 9-141
L installing 3-19
Lag delay parameter 9-147 Isolated Platform 1-23, 9-141
LAN connections 2-30, 8-138-16 Rope tension sensing 9-141
connecting 8-15 Load weigher
creating 8-13 Crosshead deflection 4-34
deleting 8-16 Empty load threshold 4-35
editing 8-16 Heavy load threshold 4-35
LAND SYS SENSOR FAULT message 6-53 Isolated platform 4-35
Landing system Light load threshold 4-35
See iLand Landing System Overload threshold 4-35
Landing System Sensor Fault message 6-53 Rope tension 4-34
Latch First Smoke Detector Zone 9-51 Load Weigher (Raw) test point, description 11-4
Latch Primary Fire Recall Switch 9-50 Load Weigher adjustment for dispatching 4-34
Latch Secondary Fire Recall Switch 9-51 Load Weigher Balanced test point, description 11-5
Latch the fire hat flashing 9-48 Load Weigher Feedback test point, description 11-5
Layouts, iView screen layouts 8-30 Load weigher installation
LCD display, iBox 1-8, 7-3, 7-4 EMCO Load Weigher 5-51
LCD Fault message 6-53 load weigher learn procedure 9-165
LEARN SW TIMED OUT message 6-53 Load Weigher parameters 9-140
Index-15
MOTOR LIMIT TIMED OUT message 6-57 adjusting on the System 12 drive 2-51
Motor Limit Timed Out message 6-57 Outputs, programming 9-128
MOTOR LMT TIMED OUT 2 message 6-57 Over Current
Motor Noise 4-20 Armature current limit parameter 9-94
Motor Triac active indicator 11-12 Armature voltage limit parameter 9-94
Motor voltage 2-53 Rated loop over-current parameter 9-94
MOTR CNTR DRV PRF FLT message 6-56 Over Current Power Threshold test point, description 11-5
Move idle car penalty 10-11 Over Current test point, description 11-5
Move lobby parked car penalty 10-11 Over Current Threshold test point, description 11-5
Move non-lobby parked car penalty 10-11 Over Load Input 9-122
MR HEAT DETECTORS message 6-55 Over Load Threshold 9-141
MR INSP. DISABLED message 6-55 Overload output 9-132
MR STOP SWITCH OPEN message 6-56 Overload threshold 4-35, 4-36
MRD, Motor Redundancy indicator 11-12 Overloaded car detection 4-34
Multiple Input AC Board Quick Reference 6-105 Overshoot correction, on contract speed runs 4-19
Multiple Output Relay Board Quick Reference 6-107 Overshoot, adjusting for 4-9
Overspeed 1 9-21
N description of 4-55
Network Info 5-26 Overspeed 1 margin, Safety parameter 9-167
Node Control 5-26 Overspeed 2 9-21
Nomenclature 2-8 description of 4-55
Non-interference timer 9-31
Non-lobby parking delay 10-21 P
Non-lobby shuffle delay 10-21 PARAM CHNG-RESET CAR message 6-41
Non-peak hall call assignment penalty 10-17 Parameter adjustment
Normal and Emergency Terminal Switch Position Tests 4-54 using iView 8-18
Normal and EmergencyTerminal Switch Position Tests 4-54 using the iBox 7-5
Normal rate limited stop parameter 9-92 Parameter entry screens 1-13, 8-18
Normal rate limited stop, adjusting for final stop 4-30 parameter settings, verifying initial 2-43
Normal Terminal Slowdown Limit (NTS) 4-11 Parameters, Load from Configuration file 8-22
Normal Terminal Switch Overspeed Tests 4-53 Parameters, Save to File 8-20
Notch Filter parameters 9-101 Parking 10-20
Nudging 9-40 Parking Config inputs 9-125
Nudging Front, NUDGING FRONT message 6-57 Parking Config outputs 9-136
Nudging Operation message 6-57 Parking Configurations 10-21
Nudging Rear, NUDGING REAR message 6-57 Parking Delay Timers 10-21
Number of Cars in Group specification 11-2 Parking Eligibility 10-27
Number of Stops specification 11-2 Parking Eligibility Config inputs 9-125
Parking Eligibility Config outputs 9-136
O Partial pick voltage 9-26
OK Write Privileges 1-13 Pass Code Failure output 9-132
Online help, accessing 8-24 Pass Code Success output 9-132
Open Loop 2-53 Passenger configuration 9-409-46
Operational Status tab 9-8 Passenger mode 9-7
Orange cables 5-12, 5-35 Passenger Operation or Passenger message 6-57
oscillation while running, adjusting for 2-66 Passing Floor Gong Enabled input 9-122
Oscilloscope Passing Floor Gong Enabled output 9-132
editing displays 8-39, 9-23 Passing Floor Gong output 9-132
Enable/Disable Tracking 9-23 Pattern - Common parameters 9-146
Scale 9-24 Pattern (Command) test point, description 11-5
Zoom to Fit 9-24 Pattern (Directional) test point, description 11-5
OTHER CARS ALT FIRE message 6-57 Pattern (Phase) test point, description 11-5
Other Cars Alternate Fire Sensor Recall message 6-57 Pattern (Raw) test point, description 11-5
Other Cars Alternate input 9-122 Pattern (Region) test point, description 11-6
OTHER CARS MAIN FIRE message 6-57 Pattern (Slew Limited) test point, description 11-6
Other Cars Main Fire Sensor Recall message 6-57 Pattern Filtered test point, description 11-5
Other Cars Main input 9-122 Pattern Interpolated test point, description 11-5
Output DAC 9-106 Pattern phase 9-10
Index-17
R REAR PHOTO EYE BYP message 6-63
R DPM OPEN-GS CLOSED message 6-62 Rear Photo Eye Bypassed message 6-63
R DR CLS FLT REC FAIL message 6-61 Rear Photo Eye Cut Out input 9-124
Rated Armature Current 4-7 REAR PHOTO EYE FAIL message 6-63
Rated loop over-current parameter 4-47, 9-94 Rear Photo Eye Failure message 6-63
Rated loop over-current parameter adjustment 4-47 REAR SAFE EDGE BYP message 6-63
Rated motor RPM parameter 9-92 Rear Safe Edge Bypassed message 6-63
Raw pattern frequency parameter 9-100 REAR SAFE EDGE FAIL message 6-63
RB resistor, adjusting 2-22 Rear Safe Edge Failure message 6-63
REAR AUX DOB BYP message 6-60 Rear This Car Up output 9-134
Rear Auxiliary Door Close Button input 9-124 Rear Up Car Lantern output 9-134
Rear Auxiliary Door Open Button Bypassed message 6-60 Recall Switch "x" input (x = 1 - 6) 9-122
Rear Car Calls COP2 inputs 9-125 Recall Switch "x" Unlatch input (x = 1 - 6) 9-122
Rear Constant Pressure Close (Rear Door) input 9-124 Recall Switch x Unlatch input (x = 1 - 6) 9-122
Rear Constant Pressure Open (Rear Door) input 9-124 Recall Switch 1 - 6 output 9-132
Rear COP2 Door Close Button input 9-123 Receive Sys Params message 6-63
Rear COP2 Door Hold Button input 9-123 Reduced Inspection Speed option parameter 9-149
Rear COP2 Door Open Button input 9-123 Register a car call 4-4
Rear COP2 Door Stop Button input 9-123 Relay Board Quick Reference 6-100
REAR DOB BYPASSED message 6-62 Relay output selection 5-47, 6-107, 6-120
Rear Door Board Quick Reference 6-103 Relevel dead zone distance parameter 9-147
Rear Door Car Gong output 9-133 Relevel distance parameter 9-147
Rear Door Close Button i(COP1) nput 9-124 Relevel door open inhibit timer 9-31
REAR DOOR CLOSE FAULT message 6-61 Relevel voltage 9-26
Rear Door Close Fault message 6-61 Relevel, iBox status LED 7-11
Rear Door Close Fault Recovery Failure message 6-61 Relevel, verifying 4-6
Rear Door Close Limit input 9-124 Releveling 4-33
Rear Door Close Limit output 9-133 Releveling speed parameter 9-147
Rear Door Close Time-out message 6-61 Remote Monitoring Authorization 10-31
Rear Door Closing Warning Buzzer output 9-133 Remote Outputs tab 10-66
Rear Door Contact Fault message 6-61 Remote User Outputs 10-59
REAR DOOR CONTCT FLT message 6-61 Repick time 9-27
Rear Door Disable Automatic Close output 9-133 Replacing Fuses in the SCR drive 6-127
Rear Door Disable Hall Door Buttons output 9-133 Reset EQ board 3-21
Rear Door Enable output 9-134 Reset Rope Gripper 2-29
Rear Door Hold Button (COP1) input 9-124 resizing windows in iView 8-34
Rear Door Hold Function output 9-134 RESTRICTED message 6-64
Rear Door Left Open output 9-134 Restricted message 6-64
Rear Door Lock Power output 9-134 RET CAM PROTECTIN FLT message 6-64
Rear Door Open Button (COP1) input 9-124 Retask penalty 10-11
Rear Door Open Button Bypassed message 6-62 RETIRING CAM DLK FLT message 6-64
Rear Door Open Fault message 6-62 Retiring Cam Door Lock Fault Activated message 6-64
Rear Door Open Limit input 9-124 Retiring Cam Door Lock Fault Deactivated message 6-64
Rear Door Open Time-out message 6-62 Retiring Cam Door Lock Fault message 6-64
Rear Door Photo Eye input 9-124 Retiring Cam output 9-132
Rear Door Stop Button (COP1) input 9-124 Retiring Cam Protection Fault Activated message 6-64
REAR DOORS STOPPED message 6-62 Retiring Cam Protection Fault Deactivated message 6-64
Rear Doors Stopped message 6-62 RFI noise, proper grounding 2-14
Rear Down Car Lantern output 9-134 RFI, Radio Frequency Radiation 2-4
Rear DPM Open - GS Closed message 6-62 Ride quality, adjusting 4-34
Rear Hall Door Close Button input 9-124 Ring and String circuit 3-21
Rear Hall Door Hold Button input 9-124 Rollback
Rear Hall Door Open Buton input 9-124 adjustment of Speed pick delay 4-9
Rear Hall Door Open Button Bypassed message 6-63 controlling 4-20
Rear Hall Door Stop Button input 9-124 Rope Gripper 2-29
Rear Momentary Pressure Close (Rear Door) input 9-124 Rope Gripper Board Quick Reference 6-109
Rear Momentaty Pressure Open (Rear Door) input 9-124 Rope Gripper Bypass 2-29
Rear Nudging Audible output 9-134 Rope Gripper Reset 2-29
Index-19
SCR Drive Ready Fault message 6-70 Hall calls - Per-car lock out 10-44
SCR DYN BRAKE FAULT message 6-70 Hall calls, Per-floor security 10-42
SCR Dynamic Brake Fault message 6-70 manage passwords 10-40
SCR Excessive Armature Current message 6-70 Security Config 1 (to 8) message 6-73
SCR Excessive Current Command, Drive Disabled 6-70 Security Config inputs 9-125
SCR Excessive Current Command, Drive Enabled 6-71 Security Config outputs 9-136
SCR EXS ARM CURRENT message 6-70 Security configuration 10-3810-50
SCR EXS CURRENT CMD DD message 6-70 Security On message 6-73
SCR EXS CURRENT CMD DE message 6-71 Security Override inputs 10-58
SCR HIGH TEMP FAULT message 6-71 Security Override serial inputs 10-58
SCR High Temp Fault message 6-71 Security settings 10-38
SCR INSF ARM CURRENT message 6-71 Seismic Switch output 9-133
SCR INST OVER CURRENT message 6-71 Send Sys Params to 1 (-20) message 6-73
SCR Instantaneous Over Current message 6-71 Sending parameter settings to the controller 8-19
SCR Insufficient Armature Current message 6-71 Sequential Step Scan Car Call inputs 9-124
SCR Intg Offset Status test point, description 11-6 Sequential step scan car calls option 9-112
SCR Loop Over Current fault 4-46 Serial bus, wiring 5-32
SCR Loop Over Current message 6-72 Serial Control I/O Board Quick Reference 6-120
SCR Low Line Caution Activated message 6-72 Serial COP 5-48
SCR Low Line Caution Deactivated message 6-72 description of 3-22, 5-48
SCR Low Line Caution, SCR LOW LINE CTN message 6-72 diagnostics 6-84
SCR Low Line Fault message 6-72 installing 5-50
SCR Low Line Test Fault message 6-72 specifications 5-50
SCR PHASE LCK LP FLT message 6-72 Serial COP Bus n Comm Fault message 6-73
SCR Phase Lock Loop Fault message 6-72 Serial COP Bus n Inventory Fault message 6-74
SCR Phase Lock Loop Warning message 6-73 Serial Driver 5-11, 5-35
SCR Power Supply Fault message 6-73 Serial Fixture Addresses 5-33
SCR POWER SUPPLY FLT message 6-73 Serial fixtures 9-37
SCR-CC H/L Board, replacing 6-144 Flash direction arrow while running 9-37
SCR-DS Board, replacing 6-143 programming 9-39
SCR-LGA board 2-51 Serial Messages 9-37
Indicators 6-123 Start Floor Arrival Announcement 9-37
Jumper settings 6-125 Serial Fixtures Board Quick Reference 6-116
Layout drawing 6-126 Serial hall call 5-11
Quick Reference 6-123 Serial Hall Call Driver 5-30
replacing 6-139 Serial Hall Call Driver Isolation Board Quick Reference 6-117
Test points 6-124 Serial Hall Call Driver Testing 5-43
SCR-LGA, SCR Drive Logic Board, replacing 6-140 Serial Hall Call Ethernet - Digi ME Board Quick Ref 6-118
SCR-LGD Logic Display Board, replacing 6-138 Serial Hall Call Node Board Quick Reference 6-119
SCR-PS Board Only, replacing 6-140 Serial Hall Call option 5-305-34
SCR-SN Board, replacing 6-141 Serial Hall Call System 3-22
SCR-SN, SCR Drive Snubber Board, replacing 6-141 Bus Voltages 5-30
SEC FIRE SWITCH ON message 6-73 Serial I/O 10-5110-61
Second Level 5-4, 5-45 configuring I/O 10-53
Secondary Fire Switch ON input 9-122 Input test 10-61
Secondary Fire Switch On message 6-73 Output test 10-61
Sector dispatching 10-25 System tab 10-51
Sector parking 10-21 Wrapback option 10-60
Sector parking conditions 10-25 Serial number, viewing on iBox 7-8
Secured, Security status 10-42, 10-45 Serial to TCP/IP 5-11, 5-35
Security Serial-to-Ethernet converters 5-35
Car call - Mode overrides 10-47 Serviceability, description 1-3
Car Call restrictions 10-45 Set Time/Date 7-8
Car Calls - Passcodes 10-48 Setting PC IP Addresses 5-18
Car Calls - Per-passenger passcodes 10-49 setting the active configuration 9-112
description 10-38 Setting the date and time in iView 8-38
General - Configuration 10-39 Setup 9-1579-171
Hall Call restrictions 10-42 Brake 9-157
Index-21
Swing operation System View 9-1
Enable 9-42 System view 10-2
parameters 9-42
Swing Operation Activated message 6-75 T
Swing Operation Deactivated message 6-75 Tach Adj. trimpot, adjusting car speed 2-62
Swing Operation Indicator output 9-133 Tach Error Fault message 6-76
Swing Operation message 6-75 Tach Error Lower Limit test point, description 11-6
Swing Operation Switch input 9-123 Tach Error tripping threshold adjustment 4-45
Switching between PCs 5-2 Tach Error Upper Limit test point, description 11-6
Switching the monitor 5-2 Tach Failure calibration 2-69
Symbols 2-8 Tach Failure, TACH FAILURE message 6-76
Synthetic Signal test point, description 11-6 Tachometer iBox Connections 2-25, 6-112, 11-7
Synthetic Speed calibration 4-13, 9-170 Tachometer installation 2-23
Sys Comm, iBox status LED 7-11 Tachometer Signal test point, description 11-6
System 12 SCR Drive TB, Brake Triac active indicator 11-12
AC Fuses 6-129 TC, Tach Signal input 6-112, 11-7
Armature voltage limit 2-64 TCP/IP 5-11, 5-14, 5-35
auto offset calibration 2-49 TCP/IP Addresses 2-5, 2-30, 2-34, 5-15, 5-18, 8-4
Commutation Fuse 6-130 setting in iView 9-139
Commutation SCR/Diode 6-137 setting on the iBox 7-9
Contactors 6-131 TCP/IP cables 5-12
current limit adjustments 2-63 Temporary Cartop Wiring 2-29
description of 1-10 Temporary CTS Relay Bypass 2-29
initial settings 2-49 TERMINAL LEARN ON message 6-76
replacing 12 Pulse Bridge 6-134 Terminal Learn procedure 9-171
replacing components 6-123, 6-127, 6-133, 6-140, 6-142, Terminal switches configuration 9-151
6-145 Terminal switches status 9-20
replacing contactors 6-131, 6-133 TERMINAL SYNC FAULT message 6-76
replacing Direction Bridge 6-136 Terminal synchronization 4-3, 9-146
replacing fuses 6-123, 6-127, 6-129 Terminal Synchronization Fault message 6-76
replacing PC boards 6-138, 6-140, 6-142, 6-145 Terminals, input and output wiring 2-13
SCRs and Diodes 6-134 Test mode 9-7
Semiconductor Fuses 6-128 Test Mode output 9-133
System Configurations (Simplex) inputs 9-125 Test Mode, Test message 6-76
System Configurations (Simplex) outputs 9-136 Test point signal descriptions 11-311-6
System Control Switches 1-7 Test switch, iBox control 7-12
System control switches on the iBox 7-12 THIS CAR ALT FIRE message 6-76
System Event Log 10-68 This Car Alternate Fire Sensor Recall message 6-76
open saved file 10-68 This Car Alternate input 9-123
save to file 10-68 THIS CAR MAIN FIRE message 6-77
System Event log, view details 10-68 This Car Main Fire Sensor Recall message 6-77
System Hoistway 10-70 This Car Main input 9-123
System I/O Time, setting 8-38
Input inventory 10-61 Timer tables
Output inventory 10-61 configuration 10-62
System I/O configuration 10-51 configuring 9-152
System I/O Troubleshooting 5-36 examples 9-154, 10-64
System monitoring 1-1 programming 9-152, 10-62
System Options 5-1 TM, Motor Triac active indicator 11-12
MCE Load Weigher 5-615-67 Toggle Output 9-137
Serial COP 5-48 Traveling cable 2-9
Serial Hall Calls 5-305-34 Troubleshooting 6-16-145
System Performance 10-74 Circuit boards 6-836-122
System Status Display 1-7 ICE-COP board diagnostics 6-84
System status, Fault bypass 9-19 ICE-CTP Cartop Processor Board diagnostics 6-89
SYSTEM SYNC message 6-75 ICE-CTP Cartop Processor Board Quick Reference 6-86
System TCP/IP 5-11 ICE-EB Emergency Brake Board Quick Reference 6-92
System User Outputs 9-138 ICE-FML Field Module Logic Board Quick Reference 6-
Index-23
the Hoist Motor 2-21
the serial hall call fixtures 5-32
typical connection locations 2-11
Velocity Encoder 2-27
Working offline, editing a configuration file 8-23
Wrapback, Serial I/O option 10-60
Write Enable switch, iBox control 7-12
Write permission 5-26
Write permission approval 5-26
Write privilege
Acquire 1-13
acquiring 2-30, 2-43
OK 1-13, 2-30, 2-43
Write privilege timeout 5-26
wrong direction, car runs in 2-61
Wye P.R. 2-48
X
X1, X2, X3 terminals, check voltages at 2-47
Y
Y1, Y2, Y3 terminals, check voltages at 2-47
Z
Z-, Velocity Encoder input 6-112, 11-7
Z+, Velocity Encoder input 6-112, 11-7
Zero Crossing, System 12 drive 2-51