ACS 800 Tripping Without Any Indication

Maybe, though it depends on how long you want to wait for the answer. As it's far quicker, I'd get on the phone to ABB myself, then I'm funny that way.

May be the guy is busy with other girls in his nieghborhood, south of heaven i mean.

Logging is never perfect and sometimes faults (internal and external) just plain won't get logged. Never rely totally on the logs, I have seen strange logged drive faults that don't match actual failures.

Narrow down where the problem is first, is it the drive or the motor and cable (partial insulation fault, imbalance, bearing issue, etc). Check the motor and cable or try the drive on a different motor.

Has something changed in the setup or the drive settings? Incorrect settings can potentially cause issues. Is this a new installation, did you install it correctly with the correct filters?

If it all looks fine it could very well be a fault in the drive in which case it goes back to the manufacturer for inspection and repair.

If there is no fault log or fault display, there is likely no fault. That then leaves the greater likely cause to be something in your command and control system that is telling the drive to stop, even though you do not think it is.

An example of a real life experience, I was once called in to troubleshoot some 500HP drives on compressors that were doing something similar. Shutting down, but no faults. After wasting an embarrassing amount of time in troubleshooting, it dawned on me to observe the Run command signal going to the drive. Sure enough, 30 seconds after the drive was told to run, the Run command signal was removed and the drive stopped. Turned out that the Run command was coming from a compressor control panel that was also watching output pressure, but was designed for constant pressure. They added the VFDs afterward. So what was happening was that if the pressure was not satisfied after 30 seconds, the controller shit down the drive. But from the DRIVE standpoint it was NOT a fault condition, it eas "normal".

GA,

In my experience the ACS800 has been very reliable at indicating fault and alarm conditions.

I agree non fault conditions are the most probable cause of the shutdown.

Something making it to stop, input might have been short or open as to whatever the logic mean not 1 or not zero is the trigger stop configured. I respect the 5 star general of drives JRAEF on this. Kudos.

Long distance calling.....

Sure I'll help.....just sign this...

Dear Giri,

Whether the drive is tripping frequently or after some operation about 1-2 min. Please check the wiring physically and tightness of the cable terminations at the terminal block side.

Regards

Dear all,

Thanks for your comments.Before contacting the OEM,I thought of taking help from this site.I would like to add following points though.

1.This is 4 year old drive & this problem is being faced sinece last 2 days.

2.I have no much knowledge about drives & this plant is new to me!

3.The drive is getting stopped intermittenlty without any fixed time interval & its getting reseted automaticaly.(The trip Led lamp is getting reseted)

I'd have rung the OEM first, as it's always the quickest, ridicule-free, route to the solution. Then, I'm funny that way.

If the Trip LED is coming on when the drive shuts down, then even if it is reset before you get a chance to look at the trip screen, the trip, and a host of other parameter values at the TIME immediately and including the trip even, are recorded in the Fault History (Fault Logger). It stores the last 64 faults, along with time and date stamps.

Log is very convenient.

If date and time don't make sense, clear the logs and see what comes new from the time you clear.

Determine if the drive is getting its reset command from the PLC or other circuitry (i.e. from a DCS controls system). Someone may have changed the logic and installed an error in the coding (if it has been worked on prior to this problem). You have not given any indication of the control circuitry, so a good troubleshooting spot to start is determine what controls it in its logical fashion. If the control command to shutdown and reset is coming in as it sounds from your post, simply backtrack the command signal coming in and determine its validity (with respect to your unit's operating procedures - found in the user's manual). If it is shutting down at the wrong time for your system, correct the logic to allow for it to work properly.