13.07.2015 Views

User Manual High Performance AC Drive

User Manual High Performance AC Drive

User Manual High Performance AC Drive

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Troubleshooting 4-7No. Name Type (1) Description Action28 VPL/MC Comm Fail ➁ A communication failure has occurred between the VelocityPosition Loop (VPL) processor and the Motor Control (MC)processor on the main control board. Possible causes are:VPL is flashing MC firmware into the MC processor when HIMindicates "Loading Config".•••Cycle powerReflash firmwareReplace Main Controller BoardMC has failed to complete or pass diagnostic tests.MC has not detected VPL handshake activity for over 32 ms.VPL has not detected MC handshake activity for over 32 ms.This is indicated when Fault Test Point 15 or 16 equals 1. Thistest point is viewed in Par 330 [Fault TP Data] when Par 329[Fault TP Select] is set to value 15 or 16.29 PWM Signal short ➁ This fault is detected when ever the actual IGBT gate is differentthan the commanded IGBT states. This fault is detected by theMotor Control (MC) processor.30 MC Firmware ➁ One of the following Motor Control (MC) firmware errors hasoccurred:MC Task Over RunIllegal InterruptSelf Diagnostic FaultData Error• Cycle power• Reflash firmware• Replace Main Controller Board31 Precharge Error ➁ The precharge function has failed to complete within 30seconds (default) of the precharge request. The precharge time• Verify the value in Par 410 [PreChrgTimeOut].out is configurable by Par 410 [PreChrg TimeOut].A precharge request is initiated when the DC Bus voltage isabove the Undervoltage Trip level and the precharge input ishigh (the requirement for the precharge being high can bebypassed by setting Par 411 [PreChrg Control] to 0 “HoldPrChrg”.• Verify the bit value in Par 411 [PreChrgControl] = 1 “Enbl PrChrg”.32 PWM Asynch ➁ The Motor Control Processor is not synchronized withSynchLink.33 +/- 15volt Power ➀ The12V DC control voltage is outside the tolerance range. Thepositive voltage power must be within the band from +15.25 to+11.4V DC. The negative voltage power must be within theband from -16.6 to -10V DC.35 Parameter Chksum ➀ The checksum read from the EEPROM does not match thechecksum calculated38 Brake OL Trip ➀ The calculated temperature of the dynamic braking resistor istoo high. The temperature is calculated by a thermal model.If the resistor is internal, the model uses resistor characteristicstored in the power structure EEPROM memory.If the resistor is external, the model uses values of parameters416 [Brake PulseWatts] and 417 [Brake Watts].39 PowerEE CRC Fail ➁ The Cycling Ring Checksum (CRC) of the data stored in thePower Board EEPROM does not match the stored CRC.• Replace switch mode power supply. Forsmaller frames, replace drive.• Cycle power• Replace Main Controller Board• Verify actual temperature of brake- If hot, wait for brake to cool- If cold, cycle power to the drive• If cold, verify Par 416 [Brake PulseWatts]and Par 417 [Brake Watts] are correct.• Cycle power• If <strong>High</strong> Horse Power units:- Check communication bus lines - 10 pinconnector in Main Control Board, <strong>High</strong>Horse Power interface board, and fiberconnections.40 SLink Mult Oflow ➁ A SynchLink Multiplier Overflow has occurred. Par 927 [SL MultState] displays SynchLink multiplier overflow errors.41 Ridethru Timeout ➁ The drive has been in a bus loss ridethrough condition for more • Verify the <strong>AC</strong> Line.than two seconds (default). The ridethrough timeout isconfigurable by Par 407 [Power Loss Time].• Verify the value in Par 407 [Power LossTime].42 DC Bus Undervolt ➀ Bus voltage has fallen below the level configured by Par 409[Line Undervolts].• Verify the <strong>AC</strong> Line.• In frames 1-4, and 9 - 13 verify theprecharge resistor is present. (With poweroff, there should be a resistance betweenDC+ and BR+).In frames 5 & 6, check the prechargeboard for errors. See the precharge boardLED for fault sequence.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!