Missing information for Mach3 settings

[ZASto]

AFAIK some external motion controllers do not support axis slaving.

So it's not Mach.

[regpye]

AFAIK some external motion controllers do not support axis slaving.

So it's not Mach.

I am starting to think that maybe this board is one of those.
I have checked and double checked the settings, and although I can get each axis to move independently I cannot get them to slave.
I have added some images of my settings. The motors all work with these settings, but no slaving at all.

[JAZZCNC]

It's common for external motion controllers to move these options into the plug-in so have you gone into the config plug-in settings.?

You will find this in Config Menu under Config plugins, then it opens another window showing all the installed plugins, click the yellow config button which relates to your board and it will open the plugin so you can change the settings.

Edit: Note, not all the plugins will open a settings window.

[regpye]

It's common for external motion controllers to move these options into the plug-in so have you gone into the config plug-in settings.?

You will find this in Config Menu under Config plugins, then it opens another window showing all the installed plugins, click the yellow config button which relates to your board and it will open the plugin so you can change the settings.

Edit: Note, not all the plugins will open a settings window.

I have tried that Jazz, the plugin seems to be fixed and not editable. Nothing happens when clicking the yellow button.

[JAZZCNC]

I have tried that Jazz, the plugin seems to be fixed and not editable. Nothing happens when clicking the yellow button.

Ok well you might be screwed then regards proper slaving, you could always just connect both drives to one motor output, it's not the correct way but will get you working. The downside is you can't home each side independent to square the gantry without getting creative.

[regpye]

Ok well you might be screwed then regards proper slaving, you could always just connect both drives to one motor output, it's not the correct way but will get you working. The downside is you can't home each side independent to square the gantry without getting creative.

That was the whole reason for setting this system up. The machine was already working fine using GRBL, USB and no problems from the plasma. The only problem I had was that the gantry was so wide that it didn't stay square, so that is why i wanted to have Y and A slaved together for homing. I know that GRBL 1.1h also has slave options, but wanted a change from using UGCS.

I do have another board that has a parallel port, I might give that a try, maybe it has the same problem?

[dazp1976]

That was the whole reason for setting this system up. The machine was already working fine using GRBL, USB and no problems from the plasma. The only problem I had was that the gantry was so wide that it didn't stay square, so that is why i wanted to have Y and A slaved together for homing. I know that GRBL 1.1h also has slave options, but wanted a change from using UGCS.

I do have another board that has a parallel port, I might give that a try, maybe it has the same problem?

Assuming there are ballscrews on either side of the gantry...... Could it be possible to redisgn it a little?.
Put a timing pulley on the end of each screw, belt them together, mount a single stepper in the center.

Mind you. If considering spending on that, may as well just get a different controller!.

I bet a cheapo parallel card will end up working straight off the bat.



You have to watch what you buy when it comes to controllers. Most of these non brands are rip-offs from others and it's hit and miss, especially some of the usb ones.
The biggest gripe I have is... Why do people still buy nvem / nvum??. Do they NOT read the forums or reviews, or do any research at all??.

Parallel cards are usually fine because the PC does the work and all they do is turn voltage on/off. But it all depends on how many outputs/inputs you need.