Recent Posts

Hello everyone,
I would like to share my new WHB04B solution for Mach4 and MachPro.
The project includes:
•   WHB04B-4 and WHB04B-6 support
•   HID to TCP Bridge
•   Step and Continuous Jog modes
•   MPG support
•   Cycle Start, Feed Hold, Stop and Reset
•   Spindle control
•   HWID licensing system
•   And much more
•   Windows 10 and Windows 11 support
Installation Videos:
Mach4 + MachPro:
https://youtu.be/VhU7JDeXLFo
Mach4:
https://youtu.be/OceMDKB33-c
MachPro:
https://youtu.be/gmYY4G-VAhM
ConfigUI:
https://youtu.be/f42EDeMtrzE
A free 7-day trial license is available on request.
Feedback is welcome.
Regards,
Sergio Couto
E_CNC
e_cnc@outlook.com

General Mach Discussion / MPG Calibration

« Last post by Yorkshire Pudding on June 16, 2026, 09:49:50 AM »

Hi,

I have just fitted my lathe with an MPG, 4 pulses per click, X/Z switch and X1,X10,X100 rotary step selector this is all connected to the second LPT port. Now for the issues:-

I used the calibration screen and it gave me some results, 4 pulses per detent, 3.452 and 2.376 saved and reset. One click send the axis off at some rate and travels about 40mm with the Step/Velocity set. Why?

The X/Z switch works fine.

The step selector is very odd, I have it connected to 3 inputs set as OEMTrig 1,2 and 3, these are configured as OEM codes 191,192 and 193. The gen config is set so the first 3 entries of the steps are 0.01, 0.1 and 1.0

When turning from X1 to X10 to X100 I see 0.01, 0.1, 0.01 in the DRO and when going back I see 0.01, 1.0, 0.01 By my reckoning I should see 0.01, 0.1, 1.0, 0.1, 0.01 Why?

?

Also there is no movement in Step or Multistep mode?

?

Please help its driving me nuts.

All I want is to be able to move 0,01, 0.1 or 1.0 with one detent.

Mach4 General Discussion / Re: Mach4 Loses Z Motion Reference After Idle

« Last post by joeaverage on June 15, 2026, 03:57:18 PM »

Hi,
I've been using Mach4 for ten years and have never had the problem you describe.

I seldom de-power my machine, and Mach4 can stay on for many weeks, and even on occasion months at a time. I rock up to the machine and start work, I usually do not
even re-home, as the machine has not lost reference from its last use, and I can go for weeks like that.

As williamcorlin has posted I think that suggests a problem with the motion controller or its plugin rather than Mach4. After all if it were a Mach4 problem would not all user be subject
to the same bug?

Craig

Mach4 General Discussion / Re: Mach4 Loses Z Motion Reference After Idle

« Last post by williamcorlin on June 15, 2026, 04:43:12 AM »

Quote from: jadongreen on January 29, 2026, 05:33:44 AM

Hi, I’m Jadon and I’m running Mach4 on a CNC router with an external motion controller, and I’m seeing a strange issue that I haven’t been able to track down. If Mach4 is left idle for more than a few minutes with the machine enabled, the Z axis still jogs and homes normally, but the moment I start a G-code job, Mach4 suddenly reports a motion fault and ignores all Z moves in the program while X and Y continue running. There’s no E-stop triggered and no following error shown, but the DRO for Z freezes at the last jog position and the tool just air-cuts. Restarting Mach4 temporarily fixes it, which makes me suspect some kind of state or buffer problem rather than wiring. I’ve checked soft limits, probe settings, and motor tuning, and nothing stands out. Has anyone run into Mach4 losing axis motion control only after sitting idle, and where should I be looking to diagnose this properly?

It does sound more like a motion controller or plugin state issue than a wiring or motor tuning problem, especially since the Z axis can still jog and home correctly after sitting idle. The fact that the DRO freezes when the G-code starts suggests Mach4 may not be receiving proper position feedback or motion confirmation from the controller for that axis. I would check the Mach4 diagnostic and plugin logs immediately after the fault occurs and see if there are any communication or buffer-related messages. It's also worth looking at whether the Z drive or controller has any idle timeout, sleep, or watchdog settings that could affect programmed motion but not manual jogging. Another useful test would be to let the machine sit idle until the issue appears, then run a very simple G-code file containing only Z moves. Also, which external motion controller and plugin version are you using? That information could help identify whether this is a known controller-specific issue.

Probes and Tool Setters / Re: MachPro Probing Wizard

« Last post by cd_edwards on June 14, 2026, 11:04:32 AM »

I should also mention, this change makes it permanently available unlike modifying the screenset which needs to be re-added every update.

Probes and Tool Setters / Re: MachPro Probing Wizard

« Last post by cd_edwards on June 14, 2026, 11:01:23 AM »

Within a UserGUIModule.mcs file, near the bottom you will find a section called UserGUIModule.CreateUserCommands(). You can add the following to into this function. This will create a User command which can then be added to a function button on widget panel. The mcTouchOff.lua module can then be called directly from a button on screen. The version in this thread has heights for EACH probe allowing the use of multiple types of Z probes. For example, a simple XYZ plate, a XHC wireless probe or a 3d touch probe. All of these would need to be wired to a separate probe input. There are four G31, G31.1, G31.2, G31.3

function UserGUIModule.mcTouchOff()
   if (Tframe == nil) then
      -- TouchOff module
      package.loaded.mcTouchOff = nil
      mcTouchOff = require "mcTouchOff"
      Tframe = mcTouchOff.Dialog()
   else
      Tframe:Show()
      Tframe:Raise()
   end
end

function UserGUIModule.CreateUserCommands()
   -----------------------------------------------------------------------------------
   --- Open Touch Off Dialog
   -----------------------------------------------------------------------------------
   w.CreateCommandActionOption("mcTouchOff", function(from_opr_panel) UserGUIModule.mcTouchOff() end)
   w.CreateSimpleCommand("mcTouchOff")

   return true, true, w.FunctionCompleted()
end

then you right click on a button, configure widget and select mcTouchOff from the dropdown. Now when you press the button, it will popup the mcTouchOff wizard and you can run any of the routines. In particular, I needed the two probes with differant heights. The MachPro supplied wizard, does not take into account the height of the probe when doing a Z height probe

Thanks to Paul Stephen for the insight and help with this and Claude AI for the modifications to the original code from Mach4. I do know of one bug in the code but it's not a game changer. When you initially set a height for a probe, the display does not reflect the new height. Only after selecting a new probe and then going back will it display the new height.

Pages: « 1 2 3 4 5 6 7 8 9 10 »