Recent Posts

1

Mach3 and G-Rex / Re: Why is the Auto Tool Zero button not working?

« Last post by claytonclarke on October 04, 2026, 10:17:16 PM »

It looks like the script itself is working correctly when you run it manually, so the issue may be related to how the Auto Tool Zero button is configured or linked to the macro. I would check whether the button is assigned to the correct macro file and whether the controller software supports that function as configured. The “Not Yet Implemented” message may indicate that the button is calling an unimplemented function rather than executing your script. Hopefully, checking the button configuration and macro assignment will help resolve the issue.

2

Mach3 and G-Rex / Re: Mach3 Settings

« Last post by felixandrea on October 01, 2026, 05:49:11 AM »

The encoders are worth understanding before changing the Mach3 settings. If the Gecko drives are using the encoder feedback internally, Mach3 may only need to handle the step/direction signals, but it depends on the exact drive model and wiring. I’d start by identifying the Gecko drive model and confirming how the encoder outputs are connected.

3

General Mach Discussion / Re: Question about MPGs and Encoder?

« Last post by arachnology on October 01, 2026, 02:41:12 AM »

In Mach3, they serve different purposes. An MPG (Manual Pulse Generator) is basically a handwheel used to manually jog an axis. When you turn the wheel, Mach3 reads the pulses and moves the selected axis according to the chosen increment or multiplier.
An encoder is normally used to report position or movement back to Mach3, for example from a spindle or an axis fitted with an encoder. It does not automatically mean Mach3 will use that feedback to control the axis in a closed loop.
So no, you do not need to connect each axis to an encoder or MPG for normal operation. Configure an MPG only if you have a handwheel, and configure encoder inputs only if you actually have encoders whose position you want Mach3 to monitor.

4

MachPro General Discussion / Re: Perfect DRO block.

« Last post by cd_edwards on September 30, 2026, 10:05:14 PM »

Could he create his own screen tab with the features he wants and have MachPro go to that page on startup?

5

Mach4 General Discussion / Re: Mach4 threading TPI problem. Please someone help.

« Last post by daseitz on September 30, 2026, 11:38:09 AM »

OK, much stupidity here. I picked up a 1/2 nut to check the threads with and it turned out to be a 12mm metric nut. Duh, no wander the threads were off. MY BAD  :'(

6

MachPro General Discussion / Re: Perfect DRO block.

« Last post by paul.stephens on September 30, 2026, 09:29:37 AM »

You may also be able to accomplish this through a GMS process, but that would still require some Lua programming and the creation of custom files to load.

The edit-offset controls were placed behind a tab and button to reduce the risk of accidental changes during normal operation. This decision was based on practical experience, not an attempt to remove functionality or limit customization.

I've been using Mach4 for twelve years and it has ALWAYS had a <ZeroAxis> button alongside the DRO. Yes, if you hit it inadvertently it causes trouble, but thats
not a reason to remove the functionality that I, and no doubt many others, have become accustomed to. It is our machines we are operating after all. If we wanted that functionality gone
we could have modified Mach4 to exclude the button in a few ketstrokes.

Most of our design and workflow decisions have evolved through real-world experience. MachMotion, our sister company and the source of many of these changes, has retrofitted, built, or upgraded approximately 80 custom machines per year for the past 20 years. When a change becomes part of our standard process, it is generally because the same issue has occurred often enough to justify addressing it for all users.

The functionality remains available; the additional step is intended to help prevent an unintended offset change that could result in machine damage, a scrapped part, or a safety concern.

7

MachPro General Discussion / Re: Erratic GoTo Part Zero function

« Last post by paul.stephens on September 30, 2026, 09:01:45 AM »

By default, I believe it is set to a rapid to zero. In the GoTo positions screen, you can configure the gcode however you like. I would say it is a little unintuitive at first I am adding a picture for clarities sake.

8

MachPro General Discussion / Re: Homing Offset in Control Plugin

« Last post by paul.stephens on September 30, 2026, 08:44:20 AM »

Is the Y axis on your machine a slave axis?

When I get back to the office, I'll set up a ESS and do some testing to see if I can make sense of what is going on.

Motion controllers should have access to our signals and configurations.

9

Mach4 General Discussion / Mach4 threading TPI problem. Please someone help.

« Last post by daseitz on September 29, 2026, 07:44:21 PM »

Im using Mach4 hobby on a Shopmaster lathe with a smoothstepper ESS.  The problem is when threading to match a standard nut the TPI is off. I was just threading a rod for a 1/2-13 nut. I had the pitch set for .796 as the specs say and the threads were a good bit to coarse. I set it down to .725 and its closer but still too coarse.
All the settings are right, the pulses per unit is correct (1" equals 1" travel) and using one pulse per spindle rotation with a clean scoped pulse.
Can someone please help me find out why this is happening?
Thanks

10

MachPro General Discussion / Re: Perfect DRO block.

« Last post by joeaverage on September 29, 2026, 05:56:19 PM »

Hi Paul,
thanks for that reply.

I'm still reading and trying to digest it all.

Seems like it might take a day or two before I can configure this.....I'll let you know how I get on.

We do it this way to prevent operators from accidentally hitting the a zero when they do not mean to.

I've been using Mach4 for twelve years and it has ALWAYS had a <ZeroAxis> button alongside the DRO. Yes, if you hit it inadvertently it causes trouble, but thats
not a reason to remove the functionality that I, and no doubt many others, have become accustomed to. It is our machines we are operating after all. If we wanted that functionality gone
we could have modified Mach4 to exclude the button in a few ketstrokes.

Craig