Steppers work in Stepconf Wizard, but not in EMC2

I've been unable to find the answer to my issue in the forums, so I apologize in advance if I'm resurrecting an old topic.

I'm currently running EMC2 on a computer built with the official EMC2 Ubuntu 10.04 distribution image along with a 3-axis Zen Tool Works 7x7 machine. I'm able to successfully go through the Stepconf Wizard with each stepper motor appearing to respond normally to the manual tests within the utility. I'm able to launch the EMC2 AXIS GUI from the newly created shortcut and it appears to recognize the CNC machine from my saved configuration information. The homing switches respond normally, the spindle toggles power, and no error messages are being displayed in the EMC2 AXIS program. The only problem that I have is that although EMC2 AXIS indicates that it is moving the stepper motors for each axis, there is no physical movement whatsoever observed on the CNC machine itself. The steppers don't physically respond to the jog command either, although the coordinates on the AXIS GUI indicate that the steppers are turning normally. Whenever I go back into the Stepconf Wizard to modify my saved configuration, the steppers once again physically respond to the manual tests & jogs - so it appears that the issue is within EMC2 AXIS itself.

This is my first time working with a CNC machine so any guidance would be greatly appreciated. I'm hoping that I've just overlooked a simple setting with EMC2 AXIS that is preventing the stepper motors from being physically activated.

i'm not conversant with the wiring of the zenbot but here goes ...

so your saying once you pressed the machine on Icon , no steppers move although home switches work
have you try'd homing the machine first , do you get any errors now showing estop etc
any enable signals used , they could be reversed

I'm comfortable with the wiring of my CNC machine. I tested the connections many times during the build process, and it passed my final diagnostics with a multi-meter after the build was complete. I took my time going through the Stepconf Wizard and made sure that all six (min/max) limit switches and E-Stop had the correct trigger settings as well as the stepper motors moving in the correct direction for +/- directions. My CNC machine works perfectly while within the Stepconf Wizard with all three axis stepper motors responding to the corresponding tests.

When I enter EMC2 AXIS and toggle the virtual power button in the program there are no error messages being displayed. E-Stop as well as the limit switches will disable the device correctly. As soon as I entered EMC2 AXIS the first time after configuring my machine I tried to home each axis. It was at this point where I noticed the problem. The program shows the coordinates for each axis moving and will show a homing icon next to the coordinates if I press the associated limit switch however the stepper motor will never physically turn the axis screw during this process. The stepper motors also do not respond to the manual jog commands within the EMC2 AXIS program. I let the homing program run for over 10 minutes once and nothing happened.

I'll have to admit that this issue is very puzzling for me.

Do your drivers need an enable signal?
If so have you tried inverting it?

Rick G

I'm not certain if my driver board requires an enable signal or not. I haven't been able to locate any documentation for the board. I have nema stepper motors with four leads, 2 for direction and the other two for stepper control.

I've looked through the Stepconf Wizard and EMC2 AXIS programs, but don't see where I would toggle the enable signal if needed.

I had tried a basic configuration without using the limit switches and E-Stop but it didn't work. I'll try making another config with only the X axis stepper configured to see if I can get any response from the CNC once I get home. Thanks!

I'll have to check my driver controller board to see if it has any hidden ports/pins for an enable lead.

CNCbasher was kind enough to assist me offline with the configuration process. It appears that Pin 1 needed to be set to "Amplifier Enable" instead of "E-Stop Out" within my Stepconf Wizard, so my problem was due to my own idiotic mistake. Just wanted to say thanks again to everyone for helping me out on this!