Recent Posts

71

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by paul.stephens on March 18, 2026, 12:16:38 PM »

Technically there is, the dashboard is a "Plugin Panel". So you can technically add a Dashboard wherever you want. The issue is that we have not designed a modular dashboard to just be thrown everywhere. So you're stuck with however that particular dashboard is hard coded to be designed as for the moment. We are planning on a resolution for this, but at this moment, that will probably be after we move to a more web based UI.

72

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by tbadger on March 18, 2026, 11:33:24 AM »

Awesome info, thanks.  I've been getting quite comfortable with the Dashboard/Widget/Button setup. By simply adding an output, I've seen how easy it can be to add a button for On/Off or Toggle. Or just finding existing functions that I can easily add as buttons. 

My next feature request is to add a new dashboard component that I can put on the left side of the GCode tab, or any where I want/need one.  I've removed all of the existing lower buttons and moved them to the Side Dashboard. I have a touch screen, and am right handed. So I like all of the functional buttons I use in one place. The Dashboard makes this extremely easy.

73

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by paul.stephens on March 18, 2026, 10:24:18 AM »

Once you have the button logic existing, your Dashboard should have it available once Mach is recompiled or restarted. Just Configure Widget, change your button and find the Button pressed option you just created.

74

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by paul.stephens on March 18, 2026, 10:21:19 AM »

Ahh I see..

To add a button in your dashboard for this, go to Go to Mach\Profile\{Profile name}\ Macros\Scripts.
Here you will make a copy of UserGUIModuleDefault.mcs and rename the copy to UserGUIModule.mcs

In that script, you're going to go to the bottom You'll see some things about CreateUserCommands()

You'll just need something along these lines to add a dashboard button.

Code: [Select]

function UserGUIModule.CreateUserCommands()
    local function RunM(code)
        -- fire and return immediately; the m-code handles any waiting/prompting
        w.api("mcCntlMdiExecute", inst, code)
    end
    w.CreateSimpleCommand("ATC") -- this creates the button and names it
    w.CreateCommandActionOption("ATC", function() RunM("M132") end) -- this gives the button logic
end

There are some other advanced things you can do with it as well like w.CreateCommandFeedbackOption for providing feedback to another function, for example if I wanted 3 different buttons to toggle between eachother, I could use this function to handle the logic for that.
Short parameter example:
w.CreateCommandFeedbackOption("ATC", function() return UserGUIModule.IsM312() end)

Another option is if you want the button to change colors when toggled

w.SetCommandButtonColors("ATC", "#FF0000", "#00FF00")

A third optional function is if you want to change the label name as it toggles.

w.SetCommandButtonLabels("ATC", "M132 off", "M132 on")

75

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by tbadger on March 17, 2026, 11:43:16 PM »

I failed to note that I’m running the Solo ATC on Mach 4 right now, and have already set up a button that will execute the M132 macro. Unless they are creating something specific that follows the MachPro model for ease of configuration for their new macros, this is the likely route to go. I just needed to know where to inject the macro call.

76

Finished Screens / Mach3 DarkScreen Screenset XYZ HOME buttons

« Last post by sture@ingard.se on March 17, 2026, 04:22:43 PM »

How can I activate the XYZ HOME DarkScreen buttons for milling on a touchscreen?

77

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by paul.stephens on March 17, 2026, 03:31:04 PM »

That would be up to the RapidChange team as the ball is currently in their court. I assume they would add logic for all of their current varieties.

78

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by tbadger on March 17, 2026, 03:04:04 PM »

Thanks for the reply Paul. I'm a beta tester, so hope to see the RapidChange ATC code earlier than later. I may watch for it in the Development branch. As there are at least three varieties of ATCs from them (ATC, STC, and MTC), should I expect to see all of them included in the initial release?  Having a Solo, that is what I'm most interested in.

79

MachPro General Discussion / Re: Assign Button to Call M132

« Last post by paul.stephens on March 17, 2026, 02:54:13 PM »

Go to Mach\Profile\{Profile name}\ Macros\Scripts
Here you will make a copy of UserMCodeModuleDefault.mcs and rename the copy to UserMCodeModule.mcs

From here, you can start editing the file.

Add your function in like below

function UserMCodeModule.m132()

    --insert user data here..

end

This will add your macro to your MCodes.

On the side note, we are in the process of adding the RapidChange ATC to our list of Tool Changers in the core of mach. I expect 1-2 weeks for this.

80

Mach4 General Discussion / Re: Mach4 - C82 - PlasmaSensOut - Z axis

« Last post by paul.stephens on March 17, 2026, 02:44:33 PM »

Our THC does something called Axis Override.. It uses a fake or false motor to handle the Jog velocity moves of your Z axis. In rare cases, some may want to have a separate Steps per Unit for their THC. When your THC tells Mach it wants to go up or down, you get this Axis override command to command Z in its stead.  All this logic is handled inside of your M3 macro. So when you call M3, it will start looking for the up or down commands after we have ARC OKAY and we get past to the "Cut" Sequence of the torch.