Tandem Motor Free to Turn - Mesa 7i96s

Hi Friends, 

While working on my homing sequence I encountered some strange behaior and didnt find any other posts with similar issues and i figured its a simple fix i just don't know where to start. 

In general, when plug in the power supply that powers the CNC all the motors are not able to be turned by hand as expected (i think) because theirs current to them. However, when i open LinuxCNC all the motors remain not being able turn other than the tandem Y motor. I am currently having issues with the z sequence (separate topic posted) but with the motor unplugged it seems to switch to the Y axis and only one motor turns. So it seems to me like something is turned off in my .hal or .ini.

I've checked the driver and it works and I've also double check all wires are connected. The second Y motor is connected to '4' on the mesa. 


Any advice is appreciated. 

Unless LinuxCNC is controlling the step motor drive enable(s)
(and there is no evidence of this in the hal file),
all motors should all have holding torque when the drives
are powered. Seems more like a drive fault or wiring issue.
 

Can i check if its, "controlling the step motor drive enable(s)"? in Halshow?

I agree that it seems like it would be a wiring issue especially considering that the driver works independently. The only evidence i have to the contrary is that i run a continuity check on the two A leads and the two B leads (at the driver on the wires coming from the motor) and I get expected behavior - > beeps when i touch the first two and the last two together nothing more. Should i just replace that wire anyway?

All of the wiring is correct.

I noticed that the led indicator turns on when i power on the machine but when i start the program it turns off. I try to unplug power to the driver while the machines is on and replace it and that turns the led back on. Seems like a faulty driver yeah?

Hi Friends,

Circling back here, it was a blown driver, I've it replaced and now the motor acts as expected. Thanks for the support, i am no longer having this issue.