[JC50]

I've got some problems on a new build. I'm in the testing and adjustment stages. First off, when I jog, my X axis just buzzes a little, then finally starts to move. It's not lead screw binding, because it does the same thing when disconnected from the lead screw. I'm running a G540, so I moved the X connector over to the A axis plug, enabled the A axis in Mach3, and the motor turned correctly. I then tried swapping the A and X modules inside the Gecko, but the problem still remained. So now I'm thinking I may have a problem with the signals and/or voltage coming from X axis Step pin on my parallel port.

So I then try to reassign the A axis pins to the X axis by going into Mach3/Ports and Pins. I change the X axis Step and Dir pins from 2 and 3 to 8 and 9. (which are the default Step and Dir pins for the A axis) and put zeros into the A axis assignments. My thinking was that since the motor turned correctly when connected to the A axis on the Gecko, I could just reassign those two pins to the X and problem solved. But.......now when I jog the X axis, the DRO shows movement, but the motor doesn't actually turn. Is my thinking wrong, or do I need to do other configurations in Mach3 to change the Step and Dir pins from A axis to X Axis?

As a last resort, could I just connect my X axis to the A connector on the Gecko, and change any X movement in the G-code to A movement.

[ger21]

You should be able to assign any of the 4 drives in the G540 to the X axis, by assigning the proper pins, as you did.

Rather than assign pin 0, you should just disable that axis. But it shouldn't matter.

Try setting the step and direction pulse widths to 15. If that doesn't work, try using Sherline mode.

If either of these help, then the problem is with your parallel port. If so, you may want to try a PCI parallel port.

[JC50]

I have a PCI parallel port I'm going to try tomorrow. And I tried many combinations on the A Step and Dir in Config. I tried all zeros, then I tried 2 and 3 (the old setting from the X axis) all the while the A axis was disabled. None of these combinations gave me any motor movement, only DRO movement.

So if the PCI card doesn't do any better, is it feasible to go ahead and connect my X-axis motor to the Gecko's A axis port, and then modify my G-code files changing any X movement to A movement?

For example: G1 X1.00 would become G1 A1.00

this would be simple using a word processor's find and replace routine

[ger21]

So I then try to reassign the A axis pins to the X axis by going into Mach3/Ports and Pins. I change the X axis Step and Dir pins from 2 and 3 to 8 and 9. (which are the default Step and Dir pins for the A axis) and put zeros into the A axis assignments. My thinking was that since the motor turned correctly when connected to the A axis on the Gecko, I could just reassign those two pins to the X and problem solved. But.......now when I jog the X axis, the DRO shows movement, but the motor doesn't actually turn. Is my thinking wrong, or do I need to do other configurations in Mach3 to change the Step and Dir pins from A axis to X Axis?

You did plug the X motor into the A axis plug when you tried this, right?

[JC50]

If I reassign the A axis step and dir pins to the X axis in the Ports and Pins config, then I have those pins assigned to the X axis, not the A axis (A will be disabled). So I should plug the X motor's DB9 into the X axis on the Gecko. But you bring up a good point. When I retry after the ports and pins change, I'll double check to make sure I've got the motor plugged into the proper connector on the Gecko. I could have had a senior moment and had the DB9 plugged into the wrong connector.

[ger21]

So I should plug the X motor's DB9 into the X axis on the Gecko

I'm getting confused, but if the motor is plugged into the X axis DB9, then the X axis pins need to be set to 2,3.

If you set the X axis pins to 8,9, then the motor should be plugged into the A axis DB9.

[JC50]

I'm getting confused, but if the motor is plugged into the X axis DB9, then the X axis pins need to be set to 2,3.

If you set the X axis pins to 8,9, then the motor should be plugged into the A axis DB9.

Being hard headed, old, and senile, I told myself you were wrong and I was right. Meaning if I changed the pins to 8 and 9, even though they originally ran the A axis, that now they should run the X axis on the Gecko. Well, I was wrong and you were right. No movement when connected to the X, but movement when connected to the A. I ended having to run in Sherline mode, but it's cutting correctly. Or close enough for me.

But now my next problem. I'm running the demo version of Mach3, and my self imposed budget is almost maxed out. So I'm going to try Linux/EMC and see how that works out. If it doesn't, then I guess I'll bite the bullet and spring for a licensed copy of Mach.