EasyManua.ls Logo

Vertical Express ICON 32 - Page 148

Vertical Express ICON 32
220 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Troubleshooting Guide Troubleshooting Section
©Vertical Express 4-16 Printed in USA April 2020
The CAN node failed
verification. Most likely
the "In Mask" or "Call
Mask" has an error
caused by unstable
communications during
the configure process.
1. Verify the node LEDs: PWR is ON steady, and STAT is flashing slow.
2. Verify the jumper positions. See CAN Node Address Assignment on page 4-4.
If the address jumpers are correct, see Configure the CAN Nodes on page 4-4.
JP14 = position 1-2.
JP8 = OFF.
If jumpers were corrected, press RST.
3. Verify that CE MicroComm Card (THY-02) SW1 position 3, is in the ON position.
4. With power removed from the controller, verify 60 ohms +/-3 ohms between CCH/CCL. See
the CAN Channel Troubleshooting Guide (if needed).
5. Use the DCN command to ensure that the associated node reports as online
6. Issue a TECCR Command (Block Select Startup Wizard > Clear CN Config).
7. Issue a TECC Command (Block Select Startup Wizard > Config CN).
Jack will not resync 1. Verify if BLO is populated in the I/O map, port 8 bit 2. If not, contact ITS Field Engineering.
2. The following are also required for jobs which have a bottom final limit: BLOM and CHKBLO
inputs and a BLO relay.
3. Issue a WJR Command. See when and why the last resync happened.
4. Issue a FJR Command. The car should immediately perform a jack resync.
5. To change the frequency of jack resync, check and adjust the following parameters: O29,
O30, O31, O32, and O44.
Hoistway access not
functioning
Hoistway Access inputs are not checked for conflicts until Hoistway Access is enabled.
1. Verify these adjustments are set per job conditions: Z38, Z39, O21, O11, and O22.
2. Use job prints to troubleshoot hardware/wiring issues related to Hoistway Access switches.
SP/NP/PLD not online 1. Disconnect all CAN channels from the IOF Card.
2. Use VER or Status to check reported software versions for each processor.
3. If still v0r0, then if all are v0r0, replace the CPU.
4. If any one processor (SP/NP/PLD) reports a version/revision, replace the IOF Card.
Controller stuck on
Emergency Power
Operation
The IOF has two inputs, and both inputs have to indicate that Normal Power or Emergency
Power Operation are activated.
IOF CON18, pin 1 has 120 VAC for normal power.
IOE CON39, pin 6 has zero VDC for normal power.
Connection issue between trades and CON39 of IOF Card.
Bad generator contact for EPNP.
If voltages are correct at the IOF Car, a failed IOF Card.
Problem and
Possible Causes (cont.)
Possible Solutions

Table of Contents