10.07.2015 Views

Sigma-II Series SGM*H/SGDH USER'S MANUAL - Esco Drives ...

Sigma-II Series SGM*H/SGDH USER'S MANUAL - Esco Drives ...

Sigma-II Series SGM*H/SGDH USER'S MANUAL - Esco Drives ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10 Inspection, Maintenance, and Troubleshooting10.1.6 Troubleshooting of Alarm and WarningTable 10.6 Alarm Display and Troubleshooting (Cont’d)AlarmDisplayAlarm NameSituation at AlarmOccurrenceCauseCorrective ActionsA.10 Overcurrent(An overcurrentflowed throughthe IGBT) orHeat Sink OverheatedOccurred when thecontrol power supplywas turned ON.Occurred when themain circuit powersupply was turnedON or when anovercurrentoccurred while theservomotor wasrunning.The overload alarm has been reset by turning OFFthe power too many times.The connection is faulty between the SERVOPACKboard and the thermostat switch.The SERVOPACK board fault occurred.The connection between grounding and U, V, or Wis incorrect.The grounding line has contact with other terminals.A short circuit occurred between the grounding andU, V, or W of the servomotor cable.A short circuit occurred between phases U, V, and Wof the servomotor.The wiring of the regenerative resistor is incorrect.Change the method to reset the alarm.Replace the SERVOPACK.Check and then correct the wiring.Repair or replace the servomotor main circuitcable.Check and then correct the wiring.A short circuit occurred between the grounding andU, V, or W of the SERVOPACK.Replace the SERVOPACK.A SERVOPACK fault occurred (current feedbackcircuit, power transistor or board fault).A short circuit occurred between the grounding andU, V, W of the servomotor.Replace the servomotor.A short circuit occurred between phases U, V, and Wof the servomotor.The dynamic brake was activated too frequently, soa DB overload alarm occurred.Replace the SERVOPACK, and reduce the DBoperation frequency.The overload alarm has been reset by turning OFFthe power too many times.Change the method to reset the alarm.The excessive change was given to the position/speed reference.Recheck the reference value.The overload or regenerative power exceeds theregenerative resistor’s capacity.Reconsider the load and operation conditions.The direction or the distance of the SERVOPACK toother devices is incorrect.Heat radiation of the panel or heat around the paneloccurred.The ambient temperature for the SERVOPACKmust be 55°C or less.A SERVOPACK fan fault occurred.Replace the SERVOPACK.A SERVOPACK fault occurred.A.30 RegenerationError Detected(Detected whenthe power to themain circuit wasturned ON.)Occurred when thecontrol power supplywas turned ON.Occurred when themain circuit powersupply was turnedON.A SERVOPACK board fault occurred.An external regenerative resistor is not connectedfor a servomotor of 6.0 kW or more.Pn600 is set to a value other than 0 for a servomotorof 400 W or less, and an external regenerative resistoris not connected.Replace the SERVOPACK.Connect an external regenerative resistor.Connect an external regenerative resistor, or setPn600 to 0 if an external regenerative resistor isnot connected.Check for incorrect wiring or a disconnected wire inthe regenerative resistor.Correct the wiring for the external regenerativeresistor.A SERVOPACK fault occurred, such as regenerativetransistor or a voltage sensor fault.Replace the SERVOPACK.The jumper between B2 and B3 is removed for a servomotorof 500 W or more, and 5.0 kW or less.Correct the wiring.Occurred duringnormal operation.Check for incorrect wiring and disconnection of theregenerative resistor.Correct the wiring for the external regenerativeresistor.The regenerative resistor is disconnected, so theregenerative energy became excessive.Replace the regenerative resistor or replace theSERVOPACK. Reconsider the load and operationconditions.A SERVOPACK fault, such as regenerative transistorand voltage sensor fault, occurred.Replace the SERVOPACK.10-8

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

Saved successfully!

Ooh no, something went wrong!