Temperamental spindle

**mark84** · 26-08-2017

I couldn't find any issues with the wiring, though I've taken the connections out and cleaned them before tightening up again, and it's working, I'm unsure if that's just coincidental but at least it's ok for now.
If the problem keeps happening could I move the connection to the next port across?
Thanks for your help Clive :)

**Clive S** · 26-08-2017

Originally Posted by mark84

I couldn't find any issues with the wiring, though I've taken the connections out and cleaned them before tightening up again, and it's working, I'm unsure if that's just coincidental but at least it's ok for now.
If the problem keeps happening could I move the connection to the next port across?
Thanks for your help Clive :)

Mark Not sure what you mean by "next port across" if you mean the next terminal I would have to look into the manual as I am not familiar with he CS labs board. Let us know if it has been cured after a few hour of use.

**routercnc** · 26-08-2017

Clive
I've just read post #3 and to me it does not sound like joining FOR and DCM is running the spindle all the time. Have a read and see if you agree.

Mark,
When you connected FOR and DCM the spindle briefly accelerated then cut out. It remained stationary until you disconnected FOR and DCM at which point nothing happened until the electronics had 'spooled down' to a low rpm at which point the spindle burst into life and tracked the speed down to zero. As if there is a dead spot above a very low rpm at which the spindle will not turn. Is this what you observed?

If I got this wrong please carry on. If not suggests VFD is faulty or has wrong settings?

**Clive S** · 26-08-2017

I am all ears. I was trying to establish if the the relay contact on the board (or control system) had gone wonky.
shorting FOR and DCM should start the spindle I hope

Problem is it is, always ambiguous when trying to sort problems out at a distance. I would like to know the outcome to the problem that way we all learn and can help one another.
It could well be that the vfd has packed up.

**routercnc** · 27-08-2017

I hear you. Difficult to diagnose over a forum, much quicker if you were there in person.
I'd only just read this thread and had to comment in case Mark messed around with the control cabinet without absolutely confirming FOR and DCM did not run the spindle.
I have a sinking feeling this is a new VFD but lets not get ahead of ourselves.

Mark, if you can confirm the above, the next steps would be to check the settings on the VFD. I'd be surprised if Dean set this up wrong so maybe you accidentally altered one of them? I'm no VFD expert but maybe you set a current limit? Have a read here, post #6, and see how your settings compare:
http://www.mycncuk.com/threads/5814-...nd-Advice-More

**Clive S** · 27-08-2017

I'd only just read this thread and had to comment in case Mark messed around with the control cabinet without absolutely confirming FOR and DCM did not run the spindle.
I have a sinking feeling this is a new VFD but lets not get ahead of ourselves.

I agree but I thought in post #4 I tried to establish that he had just removed the two cables from the vfd end and put a link in place. (to prove if the vfd would run)

I also agree that if it is a new vfd then the settings WILL be the problem.