ultra 3000 e24 error

We are running an Ultra 3000 drive and it worked okay for some time and has been getting a lot of e24 faults. It run okay for a while and then start faulting for no apparent reason. I am new to the dirve and out AB rep doesn't seem to be that familar with the drive. wants the usaual suport fee to answer quetions. Any advice would be appreciated. hanks in advance. frw312

24: Velocity Error
ON indicates that the velocity error exceeds the Velocity Error Fault Limit for a length of time greater than the Velocity Error Fault Time value.
Velocity error limit exceeded.
Increase Velocity Error Fault Limit or Velocity Error Fault Time value or both.
Reduce Acceleration.

We have been battling an Ultra3k with lots of E24 errors (as well as E18, E19, E20) It ~appears~ that replacing the encoder cable has fixed all of the problems...

We also get the e20 faults. We have relpaced the encoder cable once but that did not help. The encoder cable solution comes up as a common fix. Does AB have a problem with there cables? The cable is not in a harsh location. We have also increased the error limits but but have not tried less acceleraton. We will try that next.

thanks for both the tips.

Series C cables

We had series A cables had E18, E19, E20, and E24 errors, replaced with series C cable no more errors.

"Zip tie trick"

We checked the cable and it was a series "c". After talking with AB techconnnect they had us check cable continuity and after plugging the cable back in the drive has ran for through the weekend continuosly with a test program. Could the soulution be just reseating the cable. That action takes place when replacing the cable. This morning AB asked if we had tried the "zip tie trick" Their explanation of that is to wait until there is a failure and then secure the encoder cable at the motor connection with a zip tie to prevent failures. Has anyone else heard of this?

frw312 said:

We checked the cable and it was a series "c". After talking with AB techconnnect they had us check cable continuity and after plugging the cable back in the drive has ran for through the weekend continuosly with a test program. Could the soulution be just reseating the cable. That action takes place when replacing the cable. This morning AB asked if we had tried the "zip tie trick" Their explanation of that is to wait until there is a failure and then secure the encoder cable at the motor connection with a zip tie to prevent failures. Has anyone else heard of this?

Click to expand...

Few years back (4 or so) we had similar failures. Unplugging and plugging in the cable would work at times.
According to the local AB disrtibutor, turned out to be a bad batch of cables.
I do not remebember the series (A,B,C) though.
And yes, the zip tie will get you out of trouble for a day or two if you are lucky. We tried it as well.
Ultimately, the molded connector pins were the actual problem according to the AB distributor.

there seems to be a pattern here. It's too bad AB wants to charge for techconnect to tlell you that there is a problem with teir cable. Oh well?/ thanks for the feedback, frw