Hello, I've just built me a TRON-CNC and it seems that it is working, almost anyway! ;-)
Thought that I can use this for my model airplane hobby.

Problem is as follows:
When I run a CAM sequence generated by, in this case, cut2D, the sequence works OK for about halfway through the program.
Then suddenly the X&C axis start to sound terrible, scrambling and rumbling. It also seems that the torque is more or less gone. I can hold the motors with my hand.
The X-motor get slightly warmer than my hand and the C-motor stays cool.

When I switch off the Slider SFX for about 10-20 min. and then start up again the motors have their high pitch sound when running, and they are running just fine until next time I run a program.

I get the impression the the G-code G0 can have something to do with this.

Is there any of you, out there, who hopfully can help me or maybe give me a hint of what's wrong? This is getting into my bones soon! ;-)    

Best regards
Kent Strobel
Sweden
Computer: Windows XP Pro, Pentium 4, 3GHz
Hardware Mechapro Slider SFX+HP-Step (for4:th Axis). 1/4 Steps
Motor: Japan Servo KH56QM2-951
Software: Mach3 Version R3.042.020 full license
CAM Software: Vectric Cut2D

Sounds like it could be the driver getting hot, have you got it mounted to a heatsink? Try setting up a fan to blow cold air onto it to see if it helps.
Hood

Hello Hood,

Thanks for your quick reply. Appreciate that 

There is already a heatsink and a fan. Heatsink does not get warm, even after 30 min.

I tryed to disconnect one motor at the time running a program.
When only X motor was connected everything works great all the time.

Same procedure on C Motor. After just few minutes we have the problem again. Motor sound is terrible. there is no torque can hold it with my hand.
I turn the Slider SFX of for min. 8 min. and then it works again. Until next time.

Also changed from C-axis to A-axis in Mach3 but there is no difference
Also changed from 1/4 step to 1/8 step no change.

Best regards
Kent

Do you have a scope? if you do you could see if the port is putting out a good pulse when things are not working, that would let you know whether its the port or the driver that the problem is coming from.

 Hood

Hi again Hood!

Sorry, have no scope! Any oyher suggestion on how I maybe could find out whats wrong?

//Kent

If you can, swap pin asignment around in Mach for X and A and see if the problem follows the cofig.
Hood