Recent Posts

1

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.

2

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.

3

General Mach Discussion / Mach3 Homing Question IN/MM

« Last post by mcporche on June 14, 2026, 10:29:30 AM »

I've got a CNC running Mach3.

When I home the x and y axis with the units set to MM, the gantry moves to the proximity sensor, then it moves away a small amount, and slowly moves in to around 2 mm away from the sensor.

When I home the x and y axis with the units set to INCH, the gantry moves to the proximity sensor, then it moves away much further, and VERY slowly moves to around 3/4 of an inch or more away from the sensor.

Is this normal?  I would think that regardless of the unit setting, the gantry would home right where the sensor triggers.

4

Finished Screens / Re: Simple Mach3mill screen 1920x1080 ??

« Last post by Trebleplink on June 13, 2026, 03:35:49 PM »

Geez.  Thanks.  I don't recall reading that in the manual...

5

Mach4 General Discussion / Re: Mach 4 Hobby Non-Business Use

« Last post by joeaverage on June 12, 2026, 10:25:40 PM »

Hi,

that is calculate the required axis translations on the fly.. and that requires an OS with a deterministic operation.

No it doesn't. It can be calculated in exactly the same manner as the trajectory is, and that is used to fill the motion controllers buffer. It does not require deterministic behaviour
any more than three axis Mach does.

And it should be only utilized with a real closed loop setup..

No it does not. As I've already posted Mach4 does a perfectly excellent job of five axis tool paths, to whit I have several of them myself. WITHOUT RTCP it means that I have to place the material
in strict coincidence with the machine center point about which the Gcode was composed. It does not require closed loop (not just closed loop drives) servos any more than it requires closed
loop servo for three axis.

RTCP is solely to allow you to place the material and/or work holding in a convenient location in the machine and yet still have the tool path run AS IF the material had been placed
in strict coincidence with the assumed machine center.

Without RTCP, you could if you wish, you could translate the machine center in your CAM program to reflect the position of the material/workholding and then re-generate
the Gcode then post and run the Gcode as normal.

To date I've always placed my material carefully to be coincident with the machine center, save having to shag around with Fusion Machining Extensions all the time.

I've determined that Mach4 has some very basic flaws... and the programmers aren't even interested in correcting those... more colors and new screen development tools sell ...

Quite frankly, I think that stuff is a red-herring. Sure you can make it look nice, or maybe more convenient to operate, but Mach will go no faster, nor more accurately, nor anything else that
improves the parts coming out of the machine. RTCP would make five axis more convenient, and that would be nice, nice enough that I'd pay a $500/year subscription for it.

Can't really be bothered with cosmetic changes, what really counts for me is operational capability.....everything else is just 'gilding the lily'.

Craig

6

Mach4 General Discussion / Re: Mach 4 Hobby Non-Business Use

« Last post by cncmagic on June 12, 2026, 09:58:53 PM »

and I would add... I've determined that Mach4 has some very basic flaws... and the programmers aren't even interested in correcting those... more colors and new screen development tools sell ... fixing problems doesn't but still costs $$ they can't recover.  sounds like mach4 does a good job for you however. 

7

Mach4 General Discussion / Re: Mach 4 Hobby Non-Business Use

« Last post by cncmagic on June 12, 2026, 09:52:22 PM »

yes, I was confusing RTCP as it references CNC with something else.... yes, RTCP does what you are looking for ... that is calculate the required axis translations on the fly.. and that requires an OS with a deterministic operation. Its already been done in Linux/CNC so the modules are already available. I doubt that many hobbyists or even general users would require it. And it should be only utilized with a real closed loop setup.. not a 'closed loop servo' as the cpu doesn't know if the servo is actually where its supposed to be in real time. So there goes 99.8% of your users... its most likely too small a target group for that much effort and cost. 

8

Finished Screens / Re: Simple Mach3mill screen 1920x1080 ??

« Last post by ZASto on June 12, 2026, 09:04:07 PM »

Config/General config/Auto screen enlarge then put Mach in full screen and restart it

9

Mach4 General Discussion / Re: Mach 4 Hobby Non-Business Use

« Last post by joeaverage on June 12, 2026, 08:39:43 PM »

Hi,

I'd imagine it has to do with the fact that a rotational axis (and you shouldn't think round here) has at least two ways of getting to a single point.  I ran into something like this with a SCARA robot.. you need to watch and make sure you tell it how to bend and articulate its horizontal... otherwise you will either smack into something or crash in the next move. So how you approach a specific point in space depends on where you are beforehand and how you got there.

Yes, that it it exactly. Further I understand it is very much the concern of robots. Five axis CNC machines are less difficult, but that does not make it easy either.
The matrix formulations I have excerpted do not resolve that issue, and there is I believe yet more to learn about the resolution of those conflicts.

I would imagine that if Linux/CNC is already doing kinematics on the fly, then the equations are already in place. So why don't you simply switch over?

That is a very good question....and the only real answer is momentum. I have been using Mach4 for ten years and daily for at least five years in business. 99.99% of all of that is three axis,
and for that purpose Mach4 has been excellent. My preference would be that Mach4 has RTCP natively, and that would allow seamless extension of my machine to four and five axis tool paths.
I do have twenty or thirty toolpaths that are four and five axis, so its not like Mach4 cannot do simultaneous four and five axis, but it requires a very specific set-up of your material in the machine
in absence of RTCP. RTCP would mean a easier migration to more complex parts, not that its absence precludes those tool paths.

Like any decent free loader/bludger/sloth.....I would like someone to do the heavy lifting for me!

I have plenty of projects on the go already, adding coding my own RTCP module for Mach4 is appealing, but is unrealistic at the moment.

Craig

10

Mach4 General Discussion / Re: Mach 4 Hobby Non-Business Use

« Last post by cncmagic on June 12, 2026, 08:22:34 PM »

while I'm not particularly up on the specific, I'd imagine it has to do with the fact that a rotational axis (and you shouldn't think round here) has at least two ways of getting to a single point.  I ran into something like this with a SCARA robot.. you need to watch and make sure you tell it how to bend and articulate its horizontal... otherwise you will either smack into something or crash in the next move. So how you approach a specific point in space depends on where you are beforehand and how you got there.
I would imagine that if Linux/CNC is already doing kinematics on the fly, then the equations are already in place. So why don't you simply switch over?