Spindle drive not ready

[mike9a]

Hi all,

Please take a look at the attached picture!

"The spindle enable signal [M1SPDL_ENBL] is not on but spindle drive ready [M1SPDL_READY] signal is on. It should not be on at this time.

The spindle enable signal [M1SPDL_ENBL] has been set on, but the spindle drive ready signal [M1SPDL_READY] has not been received"

I am getting this alarm during the align procedure!

Does anyone have solution or suggestion what to do!
I would appreciate any help!

Thank you
MikeD

[mike_Kilroy]

brand? model no? picture?

[mike9a]

Sorry,
Cincinnati Arrow 750 Acramatic 2100
Trying attachment again!

Thanks
MikeD

[maver1ck]

At the risk of stating the obvious, in your picture, it says see cause (2).

This is saying the control is outputting the spindle enable signal, and it expects to see a spindle ready signal back from the drive within a specified amount of time. If it is not seeing this, either the spindle drive is not ready (i.e. faulted), or the drive is outputting the signal, but it is not making it to the control.

I'd start by checking the spindle drive for a fault, and if no fault on the drive, check the wiring between the drive and the input to see where it is being lost. Look in your electrical schematics to find the wire numbers and terminals to check. I don't have prints with me, but I think ther is also a relay in this circuit you may need to check.

[mike_Kilroy]

Mike9a I sent you a PM the other day offering same idea and ways to trouble shoot this - did you receive it?

Like Maverick says, check for fault - it is identified by a RED lite on the front of the VFS5 drive. When good, you have 2 green lites on, when you enable the drive the 3rd green lite comes on. No red. If red, bad.

If all 3 greens on, no reds on, check drive up contact from drive - it is C2 pins 16&17 (called watchdog on cmi print).

[slowlearner]

I sometimes get this fault after a brown out.

[mike_Kilroy]

Mike9a,

Just want to confirm we will repair this for you by replacing the old batt back ram memory chip, reprogram the password program and parameters, and test on a v031 motor.

for others, I will repeat your comments about how/why this happened... you let machine sit for 4-6 weeks w/o power on it and then it would never come back on w/o fault. before that, you did not leave power off so long and you could reset fault by powering up and down a few times and get it to catch and go. these chips were meant to have a 5-6 year life and this is now over 14 years....

[mike9a]

Mike,

Yes, that is exactly what happened!

Connected MotionLink software and got the codes!
Sent you list by email.

Last error detected:
ERR 83 BAD OR OUT OF RANGE

Thank you.
MikeD

[mike_Kilroy]

Sounds like we are on the right track. The only problem is all those OVER CURRENT faults before the bad/out of range.... that is not good. overcurrent usually is for real and is telling you the motor is shorted (25% of the time), the cable to the motor is shorted (24% of the time), or the drive is shorted (50% of the time). You have the remaining 1% chance that it is due to wrong parameters from bad memory chip causing the drive to try to oiutput wrong current out of control. send us the drive and we will let you know which it is.